Error

Unresolved Error: Server 2012 – Event 1000, Application Error

I came across an issues with my Windows Server 2012 / Exchange 2013 RU2 Server. After an unexpected shutdown message I was able to find out the faulting application which caused the reboot was LSASS.

There was an event message in the system event log of:

The process wininit.exe has initiated the restart of computer EXSERVER on behalf of user for the following reason: No title for this reason could be found
Reason Code: 0x50006
Shutdown Type: restart
Comment: The system process ‘C:Windows\system32\lsass.exe‘ terminated unexpectedly with status code 255. The system will now shut down and restart.

Later found in the application log event 1000 application error::

Faulting application name: lsass.exe, version: 6.2.9200.16384, time stamp: 0x50108ab2
Faulting module name: schannel.DLL, version: 6.2.9200.16384, time stamp: 0x5010892c
Exception code: 0xc0000409
Fault offset: 0x000000000001a73a
Faulting process id: 0x224
Faulting application start time: 0x01ce7f8a27d7e7ff
Faulting application path: C:Windowssystem32lsass.exe
Faulting module path: C:Windowssystem32schannel.DLL
Report Id: c2142447-f4f2-11e2-9404-000c299625b9
Faulting package full name:
Faulting package-relative application ID:

Looking into the Exception code: 0xc0000409 only tells me that the application experienced an event it could not handle and crashed causing windows to reboot.

Another bit of info I will keep in mind is right before this issue there were several Application Events, Event 4002, MSExchangeIS that reads:

Microsoft Exchange Information Store service has promoted the following properties (65F3, 65E9, 0E99, 0E9A) for mailbox (59bfe395-06d4-4407-8d6c-4f763e37e698) and folder (Inbox <hidden>) with session client type (Migration).

This so happens to be during a migration period where I am moving mailboxes from Exchange 2010 to Exchange 2013 RU2. It has me also wondering if items from one of the legacy mailboxes has some form of corruption within them which may be the root cause of this.

For now this is unresolved and I will keep an eye on it.  If you know of this issues please hit me up via email jermsmit ( at ) gmail (dot) (com).

Thanks

SQL Server Database Error: 661

One of my customers had an issue where they failed to open a connection to a particular database they had been testing. The error read: ‘the database e:somepathsomefolderjermsmit.mdf’ cannot be opened because it is version 611. The server supports version 655 and earlier. A downgrade path is not supported.

This issue is caused because you are not permitted to use a database from a later release on an earlier system. i.e they are not backwards compatible

Problem: Databases created under a newer version of SQL Server are not compatible with previous versions of SQL Server

Solution(s) that I am aware of in this case:

  • You need to either upgrade your SQL Server instance to the same version as the database or one newer
  • Or copy out the data in that database into an earlier version (using the data migration wizard perhaps)

If you need to know the version of your source and destination databases use the following query:

SELECT @@VERSION

The destination should be the same level or greater in in version.

Best of luck to ya

Issue: Outlook Address Book Not Updating

Symptoms:

New users added to Exchange 2010 do not show up in global address book

Tests Performed:

1. Searched for new users from Outlook – This failed
2. Searched for new users from OWA – This works
3. Put Outlook in non-cached mode and searched – this worked

Suspected Problem:

Offline Address Book Generation is not happening – Possible cause, resources (memory) on host server, service failure.

Steps Taken: *note* I have seen this before so I know where I am looking first

1. Stop the Microsoft Exchange File Distribution Service

2. Stop the Microsoft Exchange Address Book

3. Clear the files from ‘C:Program FilesMicrosoftExchange ServerV14ExchangeOAB’ putting them into a backup folder of some sort.

4. Restart the services above.

5. To get the OAM to immediately generate run the following command: Update-OfflineAddressbook “name of offline address book”. You may encounter an issue stating that the System Attendant Service is not running or you do not have permission. 1. Make sure you are running the Exchange Management Shell as Administrator and 2. The System Attendant Service is running. *note* The Service is named “Microsoft Exchange System Attendant”.

6. You will now notice that the GUIDS and files have started to populate under ExchangeOAB folder

Follow-up Testing that things now work:

1. Exit Outlook and delete the Offline Address Book cache from ‘C:Users%user profile%AppDataLocalMicrosoftOutlookOffline Address Books’

2. Open outlook again cache should repopulate at this point.

3. Open a new email message or click the Address Book and search for the person(s) who were not showing previously.

Conclusion:

The Outlook Client failed to download an updated copy of the Offline Address Book because the services have stopped functioning. I was unable to obtain errors in the event logs regarding this, however having experienced this in the past it has become suspect

– For Darlene

MapiException: TooManyMountedDatabases when mounting database

I was hit with a nice error when attempting to mount several Exchange databases on my new Exchange 2010 SP2 server that I had setup in a lab envionment for production testing.

The error:

——————————————————–Microsoft Exchange Error——————————————————–
Failed to mount database ‘IJ’.IJFailedError:Couldn’t mount the database that you specified. Specified database: IJ; Error code: An Active Manager operation failed. Error The database action failed. Error: Operation failed with message: MapiExceptionTooManyMountedDatabases: Unable to mount database. (hr=0x8004060e, ec=-2147219954). [Database: IJ, Server: EXCHANGE.JERMSMIT.LOCAL].An Active Manager operation failed. Error The database action failed. Error: Operation failed with message: MapiExceptionTooManyMountedDatabases: Unable to mount database. (hr=0x8004060e, ec=-2147219954). [Database: IJ, Server: EXCHANGE.JERMSMIT.LOCAL]An Active Manager operation failed. Error Operation failed with message: MapiExceptionTooManyMountedDatabases: Unable to mount database. (hr=0x8004060e, ec=-2147219954). [Server: EXCHANGE.JERMSMIT.LOCAL]MapiExceptionTooManyMountedDatabases: Unable to mount database. (hr=0x8004060e, ec=-2147219954)
——————————————————–OK——————————————————–

The cause of this issue is because Unlicensed (trial) of Exchange 2010 servers are limited to 5 databases. In the Application event log I noticed the following message:

Event ID: 9591 – Exceeded the max number of 5 MDBs on this server.

It seems I have exceeded the number of databases that can be mounted during my trail. I will now apply a MSDN license and see how things work out.