The following article deals with solving error c1030af1 when trying to view or modify Public Folder properties in Exchange System Manager.
In some cases, when you open ESM (Exchange System Manager) and try to view or modify any Public Folder‘s properties you might get this error:
Note: This error is usually displayed in Exchange Server 2003 System Manager, and right now I don‘t have any Exchange 2000 machine available to check if this error is also applicable to Exchange 2000.
In some cases, when you open ESM (Exchange System Manager) and try to view or modify any Public Folder‘s properties
you might get this error:
————————— Exchange System Manager ————————— The requested operation is forbidden. ID no: c1030af1 Exchange System Manager ————————— OK —————————
It seems that this error is related to the fact that SSL is enabled on the EXADMIN virtual directory in IIS on the server. If, for any reason, you enabled SSL on the Default Web Site in IIS, and chose to overwrite the sub folders‘ (virtual directories) SSL properties, or, for some reason you chose to specifically enable SSL on the EXADMIN virtual directory under the Default Web Site in IIS, you will get this error.
Note that if you do want to use SSL on the EXCHANGE virtual directory (in order to use SSL on Outlook Web Access – OWA) you do not need to also enable SSL on the EXADMIN virtual directory. Read Configure SSL on OWA and Configure SSL on OMA for more info.
Follow these steps to fix this issue:
- Open IIS Manager from the Administrative Tools folder.
- Expand SERVERNAME, Web Sites, Default Web Site.
- Right-click the EXADMIN virtual directory and select Properties.
- Click on the Directory Security tab. Click on the Edit button in the Secure Communications area of the tab.
- You will probably notice that the Require Secure Channel (SSL) and most likely also the Require 128-Bit Encryption checkboxes are selected.
- Click to un-select both of these checkboxes and then click Ok.
- Restart the IIS Admin service from the Services snap-in from the Administrative Tools folder, or from the SERVERNAME context menu in IIS Manager snap-in.
Now you can go back to the Exchange System Manager (ESM) and click Properties for any of the existing Public Folders. The error should not be there anymore. If you still get the error, close ESM and re-open it.