System Attendant Service failed to create session for virtual machine

I came in this morning to find out that the nighttime help desk rebooted exchange 2003 after they could not send any email.
Email was just sitting in the outbox in outlook.
I did remove antigen for exchange about 6 hours earlier last night.
I did verify that all the permissions for my existing exchange service account did not change in the public folder store or the information store.
I received the following errors in the system evt logs on my Exchange 2003 Server Sp2.
Any other ideas? I need to provide a root cause to management.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Event Type:      Error
Event Source:      MSExchangeFBPublish
Event Category:      General
Event ID:      8213
Date:            2/4/2008
Time:            7:22:22 AM
User:            N/A
Computer:      EXCHANGE
Description:
System Attendant Service failed to create session for virtual machine NJMX1. The error number is 0xc007052e.

For more information, click http://www.microsoft.com/contentredirect.asp.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Event Type:      Warning
Event Source:      MSExchangeIS Public Store
Event Category:      General
Event ID:      9551
Date:            2/4/2008
Time:            7:48:26 AM
User:            N/A
Computer:      EXCHANGE
Description:
An error occurred while upgrading the ACL on folder [Public Folders]/MS Mail Shared Folders (MailServe) located on database "First Storage Group\Public Folder Store (Exchange)".
 The Information Store was unable to convert the security for /O=CIT/OU=NJ/CN=RECIPIENTS/CN=ADMINISTRATOR into a Windows 2000 Security Identifier.
 It is possible that this is caused by latency in the Active Directory Service, if so, wait until the user record is replicated to the Active Directory and attempt to access the folder (it will be upgraded in place). If the specified object does NOT get replicated to the Active Directory, use the Microsoft Exchange System Manager or the Exchange Client to update the ACL on the folder manually.
 The access rights in the ACE for this DN were 0x78.

For more information, click http://www.microsoft.com/contentredirect.asp.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I see this KB but it dosent seem to really help
http://support.microsoft.com/default.aspx?scid=kb;en-us;328931

~~~~~~~~~~~~~~~~~~~~~~~~~
Please note:
I did use the following process outlined by Antigen support to ensure proper removal.

1- Stop all Exchange services and any then Antigen services that might still be running after Exchange is brought down.  Antigen services should have been brought down once Exchange services are stopped.
2- Disassociate the Antigen services from the Exchange services.  To do this:
- Open a DOS-Prompt Session and change to this directory, Program Files\Sybari Software\Antigen for Exchange, then type: antutil /disable
3- Start the Exchange services again.  Now, Antigen will not start up anymore.
4- Go to Add/Remove Programs and uninstall Antigen.
5- Delete the next entries in the Windows Registry (if they exist):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Antigen for Exchange
HKEY_LOCAL_MACHINE\SOFTWARE\Sybari Software
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\AntigenXXXX
Remove Sophos key (if it exists)
Remove Kaspersky Lab key (if it exists)
6- Delete the Antigen folder and its subdirectories (Program Files\Sybari Software).

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
omen1280Asked:
Who is Participating?
 
kevin_uk05Commented:
Have you look at Microsoft for this errror?
0
 
omen1280Author Commented:
yes and i have only found this one KB that dosent really seem to pertain to this situation directly
0
All Courses

From novice to tech pro — start learning today.