[Webinar] Streamline your web hosting managementRegister Today

x
?
Solved

exchange 2007 logon failure after restoring database

Posted on 2015-01-13
5
Medium Priority
?
106 Views
Last Modified: 2015-01-27
I restored Exchange 2007 database yesterday. When I restored I moved it the D drive which has more space. Everything worked yesterday. Today no one can connect to Exchange. The application log is filled with errors. I can see that emails are still coming in to the server but we can't connect to mailboxes

Log Name:      Application
Source:        MSExchangeIS Mailbox Store
Event ID:      1022
Task Category: Logons
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      XXXXX
Description:
Logon Failure on database "First Storage Group\Mailbox Database" - Windows account NT AUTHORITY\SYSTEM; mailbox /o=AXIOMLTD/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=SystemMailbox{CD5B3C93-6B28-400E-AB94-0EF470784982}.
Error: -1069
Client Machine: xxxxxx
Client Process: MSExchangeMailboxAssistants.exe
Client ProcessId: 0
Client ApplicationId: Client=MSExchangeMailboxAssistants;Action=OofAssistant
0
Comment
Question by:ajdratch
  • 3
5 Comments
 
LVL 53

Expert Comment

by:Will Szymkowski
ID: 40546716
These error messages are due to storage quota limits. Check the following link for additional info.

Storage Quotas

Will.
0
 

Author Comment

by:ajdratch
ID: 40546733
There are no limits on the mailbox. This is happening to all users.
0
 
LVL 8

Expert Comment

by:Jessie Gill, CISSP
ID: 40547436
on an individual mailbox does, it have the system, and the user of the mailbox  for full manage rights?

Also here is are technet articels with the event id
http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=8.0&EvtID=1022&EvtSrc=MSExchangeIS+Mailbox+Store
http://support.microsoft.com/kb/555420
0
 

Accepted Solution

by:
ajdratch earned 0 total points
ID: 40548521
I dismounted the database, removed the log files and remounted it. This fixed the problem
0
 

Author Closing Comment

by:ajdratch
ID: 40572365
I dismounted the database, removed the log files and remounted it. This fixed the problem
0

Featured Post

2018 Annual Membership Survey

Here at Experts Exchange, we strive to give members the best experience. Help us improve the site by taking this survey today! (Bonus: Be entered to win a great tech prize for participating!)

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Microsoft Jet database engine errors can crop up out of nowhere to disrupt the working of the Exchange server. Decoding why a particular error occurs goes a long way in determining the right solution for it.
In my humble opinion (IMHO), TouchDown from Symantec is the best in class for this type of application, but Symantec has end-of-lifed it and although one can keep using it, it will no longer be supported or upgraded.  Time to look for alternatives t…
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
Suggested Courses
Course of the Month7 days, 22 hours left to enroll

607 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question