Unable to open Public folders in Exchange System Manager. c1030af2.

I have a very simple setup.

W2k sp4 server with MS exchange 2000 sp3.  I have removed IIS Lockdown tool.  The Installation is new.

However when I try to expand the Public folders in ESM I get the error.

ESM
The Operation Failed to Start due to an internal server error.
ID no:c1030af2
ESM.

When I restart the server and check out IIS; public, exchange and exadmin are all showing the red error sign.  Status reads the system cannot find the path specified.  If I stop and start the default website the IIS error is resolved. ESM is still giving the same error.

The IP Address and Port for the Default website are correctly assigned. The hostheader name is blank
IIS Lockdown tool has been uninstalled.
This is a single server site.

Ross



dxrmc0Asked:
Who is Participating?
 
moduloConnect With a Mentor Commented:
PAQed with points refunded (500)

modulo
Community Support Moderator
0
 
alshahnazCommented:
According to my experience, you may receive the c1030af2 error when
checking Public Folder properties because the "Manage auditing and security
log" right which is granted to the Exchange Enterprise Servers group during
the domainprep setup of Exchange 2000 may be missing.

This Microsoft Knowledge Base article is for your reference:

322021.IDEA.EN-US XADM: Errors c1030af2 and c10308a8 while accessing Public
Folders
http://support.microsoft.com/defaul...EA;EN-US;322021

I hope the above information can help you solve the problem quickly. Good
Luck!

Shahnaz
0
 
dxrmc0Author Commented:
I also saw that when searching the google for help.  Unfortunatly the link is not active.

0
 
alshahnazCommented:
Hi okay ,
   hmmm  try to re-create the Exadmin virtual server in Internet Information Services (IIS). To re-create the Exadmin virtual server, back up the IIS metabase, remove the Exadmin virtual directory, remove the directory-service-to-metabase-replication component (Ds2mb.dll), and then restart the System Attendant service.

Shahnaz
0
 
dxrmc0Author Commented:
Shahnaz,

Had also tried that.. Decided to reinstall IIS and Reinstall Exchange that worked.. long way round, but effective!

-Removed IIS.. Restarted
-reinstalled IIS.. SP4.. Restart..
-Reinstalled Exchange.. restart
-Exchange SP3

..One healthy server again!!

Ross
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.