JSI Tip 1765. MSExchangeIS Private event 9037 and MSExchangeIS Public event 9038.

Jerold Schulman

November 1, 1999

1 Min Read
ITPro Today logo in a gray background | ITPro Today


If the Microsoft Exchange Server information store generates:

Event:9037Source:MSExchangeIS PrivateType:ErrorCategory:NoneDescription: No database session was available to satisfy a request. The registry value SYSTEMCurrentControlSetServicesMSExchangeISParametersPrivateSessions may be set too low for the level of activity on this server.

you have exceeded the 60 Sessions (60 JET tables) which are opened during initialization. To increase the number of Sessions, use Regedt32 to navigate to:

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesMSExchangeISParametersPrivate

Edit or Add Value name Sessions, a type REG_DWORD, and in the DWORD Editor, set the data value to Decimal 70. Click OK and restart MSExchangeIS. If event 9037 continues to occur, increase the data value till it ceases.

NOTE: Event 9037 is caused by slow response to the JET calls.

NOTE: Each JET table consumes additional RAM.

If you receive

Event:9038Source:MSExchangeIS PublicType:ErrorCategory:NoneDescription: No database session was available to satisfy  a request. The registry value SYSTEMCurrentControlSetServicesMSExchangeISParametersPublicSessions may be set too low for the level of activity on this server.

Use Regedt32 to navigate to:

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesMSExchangeISParametersPublic

Edit or Add Value name Sessions, a type REG_DWORD, and in the DWORD Editor, set the data value to Decimal 70. Click OK and restart the Public information store. If event 9038 continues to occur, increase the data value till it ceases.

NOTE: Event 9038 is caused by slow response to the JET calls.

NOTE: Each JET table consumes additional RAM.


Sign up for the ITPro Today newsletter
Stay on top of the IT universe with commentary, news analysis, how-to's, and tips delivered to your inbox daily.

You May Also Like