Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 1024 Source: MSExchangeIS Public Store
|Source: MSExchangeIS Public Store|
<domain>\<user name> was unable to log on as <domain>\<user name> to the Public Folder Store "First Storage Group\Public Folder Store (<server name>)".
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is the role of the Microsoft Exchange Information Store service?
What is an Exchange public folder?
What is an Exchange store?
From a newsgroup post: "In my case, the Exadmin virtual directory in IIS had its permissions altered somehow. I reset back to Integrated Windows Authentication and all goes well again".
Mohammed Athif Khaleel
To resolve this event, check if the mailbox account stated in the event description is enabled. In one such case, the mailbox account was not enabled and enabling the mailbox solved the issue. See ME555422 for more information about this event.
I changed the security template on my Domain Controller, which disabled the account. I simply removed the mailbox, which deleted all mail, and then recreated the account using AD Users and Computers.
This error was given on a “test environment” machine when the default store was renamed almost immediately upon completion of Exchange installation. The information store shut down without warning and could not be accessed, even following a reboot. As soon as the store was renamed to "First Storage Group", the Information Store service could be restarted successfully.
See MSEX2K3DB for details about this error.
This profile does not have the appropriate permissions to log on to this public information store. In System Manager, configure access permissions for the profile of the Information Store. See also ME252543 for another instance of this error.
In one instance, the whole server was affected by a malformed email. The email would cause all email clients to stop responding once they tried to access that particular email. The IMAP and POP3 services would become unresponsive and the only solution was to restart the server.
|Private comment: Subscribers only. See example of private comment|
|Links: ME252543, ME555422, MSEX2K3DB|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated