Exchange Server Forums

Public Folder Acting wierd

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2000] >> Public Folders >> Public Folder Acting wierd

Page: [1]

Message

<< Older Topic Newer Topic >>

Public Folder Acting wierd - 11.May2006 4:24:19 PM

hamed

Posts: 10
Joined: 28.Sep.2004
From: london
Status: offline

Hi Everyone,
(Please note it was my problem this afternoon after applying a new patch and also change the settings of urlscan)

When you goto exchange managment and then click on folders and select the public folder you then get the following error message
---------------------------------------------------------------------
The Object is no longer available, Press F5 to refresh the display and then try again

ID no: 80040e19
Exchange system Manager
---------------------------------------------------------------------

But you can access your public folder or OWA or Outlook without any problems. The permissions are fine. You can see it in IIS and you have not touch your IIS settings.

Typical IIS Settings for exchange
PUBIC FOLDER: M:\MYSERVER\public folders
EXCHANGE: M:\MYSERVER\MBX
EXADMIN: \\.\backofficestorage It also works with M:\

i did some research and find alots of diffrent solutions
1. problem with Virtual Directories
2. Dependency of startup (As which Services should load first)
3. File parsing in IIS
4. Urlscan
and etc...

You can do your daily maintanance suich as remove add but VIA Outlook
Can access it VIA web

This is how i fix it
Ok I was looking through this form and found many people having the same diffculty.
If you use urlscan and have domain with .com make sure you will not disallow the .com extension
here is the example of my urlscan

;
; Extensions listed here either run code directly on the server,
; are processed as scripts, or are static files that are
; generally not intended to be served out.
;
; Note that these entries are effective if "UseAllowExtensions=0"
; is set in the [Options] section above.
; ; Deny executables that could run on the server
.exe
.bat
.cmd

This is where i had my promlem but after removing the .com and restart the wwp it was fixed the best way of knowing it do the following

http://your server/public folder name

and then check your urlscan log file
if you see this
[05-11-2006 - 14:27:20] Client at 10.0.0.2: URL contains extension '.com', which is disallowed. Request will be rejected. Site Instance='1', Raw URL='/ExAdmin/Admin/**************.COM/Public%20Folders/'

then i can say 99.9 percent it is because of your urlscan settings, the funny part of it is i did change the urlscan settings this morning and then apply the new patch and then after that it starts to happening.

Anyway have a nice day every one and i will be happy to help

< Message edited by hamed -- 11.May2006 5:06:29 PM >

Post #: 1

Featured Links*

RE: Public Folder Acting wierd - 11.May2006 4:57:47 PM

hamed

Posts: 10
Joined: 28.Sep.2004
From: london
Status: offline

This is the link for the following new patch

http://www.microsoft.com/technet/security/bulletin/ms06-019.mspx

< Message edited by hamed -- 11.May2006 5:07:38 PM >

(in reply to hamed)

Post #: 2