Merhaba,

İki tane cozum mevcut;

A)

By default, administrators are assigned the right to create public folders. The Default role does not, but can post to folders or to Read items unless those permissions are changed.
You can globally prevent users from creating top-level public folders, which should prevent drag-and-drop duplication at the top level through the following procedure.

To remove the 'Create top-level public folder' permission:


Start Exchange System Manager (ESM).
Navigate to Folders, right-click the Public Folder node and click Properties.
Click the Security tab.
Under Name, click Everyone.
Under Permissions, scroll to 'Create top level public folder.'
In the Allow column, clear the checkbox.
To enable your administrative account to delete the duplicate folders, add your account to the top-level public folder hierarchy and assign yourself full control.

To set the permissions for groups and users to manage individual public folders, navigate to the desired folder through ESM, and click on either Client Permissions and/or Administrative Rights. Client Permissions allow you to select predefined roles that control permissions to create items, read items, create subfolders and establish folder owner, folder contact and folder visible. Groups need to be mail-enabled.

Administrative Rights sets who is an administrator for the folder. In most cases, these are settings don't need to be altered.

B)

Error ID number: 80040e19

Error Message

The object is no longer available. Press F5 to refresh the display, and then try again

Possible Causes

Improper IP address binding in Internet Information Services (IIS).

Host header for the default Web site is incorrect in IIS.

Incorrect path name listed in IIS under the Home Directory tab.

Metabase may be corrupted.

URLScan may be installed on IIS blocking specific extensions or verbs.

Non-working public folder store is selected in ESM.

Invalid folderpathname set for the http public folder in Active Directory® directory service.

Other third-party ISAPI filters installed in IIS.

Public folder hierarchy on the Exchange server is associated with the public folder store on another server.

Troubleshooting

Verify proper IP address, host header, and port in the properties of the Default Web Site. By default, the IP address is set to all unassigned with no host header bound to port 80. Set this back to the default settings for testing purposes. If multiple IP addresses are bound to the network card because of the "All in one" syndrome with running multiple Web sites on an Exchange server, try using the first bound IP address. Add host header if necessary to get around this. Change port if necessary. If this error is occurring on a cluster server, you may need to add a host header for the Exchange cluster virtual name to the Web site to get this working.

Check to make sure that URLScan is not installed on the server. This information can be found by getting the master WWW properties in the Internet Information Services (IIS) Manager and selecting the ISAPI filters tab. If URLScan is listed, the best thing to do to see if URLScan is causing the problem. To see if it is the problem, check the urlscan.log file that is created in the \winnt\system32\inetsrv\urlscan folder. The following is a sample urlscan.log file:
[08-23-2004 - 14:39:36] Client at 192.168.254.67: URL contains extension '.com', which is disallowed. Request will be rejected. Site Instance='1', Raw URL='/ExAdmin/Admin/domain.com/Public%20Folders/'
[08-23-2004 - 14:56:10] Client at 192.168.251.11: URL contains extension '.com', which is disallowed. Request will be rejected. Site Instance='1', Raw URL='/ExAdmin/Admin/domain.com/Public%20Folders/'
[08-23-2004 - 14:57:02] Client at 192.168.251.11: URL contains extension '.com', which is disallowed. Request will be rejected. Site Instance='1', Raw URL='/ExAdmin/Admin/domain.com/Public%20Folders/NON_IPM_SUBTREE/'
As you can see, Urlscan is denying the .com extension when expanding the public folders in the ESM. For more information about this problem, see Microsoft Knowledge Base article 328659, "Error 80040E19 when you try to expand public folders in Exchange 2000 Server."
Additionally, for more information about configuring URLScan on an Exchange server, see Microsoft Knowledge Base article 309508, "IIS lockdown and URLscan configurations in an Exchange environment."

Important:
After a setting in the urlscan.ini file is changed for use with URLScan, the IISAdmin service must be restarted for the change to take effect. Keep in mind that this will stop the Information Store which will affect Microsoft Office Outlook® and Outlook Web Access clients.

Connect to another public folder store, if available, to see if the issue persists. To do this, right click on Public Folders, click Connect to, and then select another public folder store.

Check the properties in IIS on the public and exadmin folders to see whether they are pointing to the proper home directory paths. Be default, exadmin should point to \\.\BackOfficeStorage and public should point to m:\domain.com\public folders. Having incorrect directory paths will cause this issue even if it is off by one letter. For example, if public folders was spelled public folder.

Verify the correct folderpathname is listed for the http public folder. In the Internet Information Services (IIS) Manager, under properties of the actual virtual server object, on the Home Directory tab, the local path may be listed incorrectly, for example, "M:\example.com\MBX" (where example.com is the name of your domain). Change it to "M:\example.com\" and save the changes. Then, use the following procedure to clear the value of the folderPathname attribute.

Caution:
If you incorrectly modify the attributes of Active Directory objects when you use Active Directory Service Interfaces (ADSI) Edit, the LDP (ldp.exe) tool, or another Lightweight Directory Access Protocol (LDAP) version 3 client, you may cause serious problems. These problems may require that you reinstall Microsoft Windows Server™ 2003, Exchange Server 2003, or both. Modify Active Directory object attributes at your own risk.

To clear the value on the folderPathname attribute
Start the ADSI Edit tool from Windows 2000 Support Tools or from Windows Server 2003 Support Tools.

Expand the following nodes:

Configuration Container

Configuration

Services

Microsoft Exchange

Organization_Name

Administrative Groups

Administrative_Group_Name

Servers

Exchange_Server_Name

Protocols

HTTP

Right-click CN=100, and then click Properties.

Click folderPathname in the Attributes list, and then click Edit.

Remove the value that contains the incorrect path of the server by selecting the value and clicking Clear. Click OK two times to apply the change.

Take a netmon trace when the client is attempting to connect to the public folders in the ESM. This trace will tell you what is being returned from IIS. The client, in this case, would ESM on another computer besides the Exchange server itself so that you can see the proper network traffic.

Umarim cozum olur.

Emre AYDIN