locked
Exchange 2007 Problems - need to restart every morning RRS feed

  • Question

  •  

     

    For the past couple of days, have had a problem with our Exchange 2007 server which requires a reboot when we come in the following morning (trying to restart the information store service will fail)

    Here are the events that log, in order of how they happen from about 1:00 AM (they may or may not be relevant to the issue!)

     

    Event1020 MSExchangeTransport:
    The account 'NT AUTHORITY\ANONYMOUS LOGON' provided valid credentials, but is not authorized to use the server; failing authentication.

    Event 1035:
    Inbound authentication failed with error LogonDenied for Receive connector Default *MYSERVERNAME*. The authentication mechanism is Ntlm. The source IP address of the client who tried to authenticate to Microsoft Exchange is [*.*.*.*].

    Event 1164
    No database session was available to satisfy a request on the mailbox database 'Second Storage Group\Mailbox2 Database'. The number of sessions configured via the Active Directory attribute msExchESEParamMaxSessions on the storage group may be set too low for the level of activity on this storage group.
     The current value for this parameter is 329.

    Event 1107

    Error 0x44c occurred during folder background cleanup on database "Second Storage Group\Mailbox2 Database".

    Event 1164
    No database session was available to satisfy a request on the mailbox database 'Second Storage Group\Mailbox2 Database'. The number of sessions configured via the Active Directory attribute msExchESEParamMaxSessions on the storage group may be set too low for the level of activity on this storage group.
     The current value for this parameter is 329.

    2:00 Event 7200
    Background thread FDoMaintenance halted on database "Second Storage Group\Mailbox2 Database" due to error code 0x44c.

     

    Then, the following error happens hundreds of times, on a variety of mailboxes (which do exist, are not locked out or disabled etc)

    event 1022
    Logon Failure on database "Second Storage Group\Mailbox2 Database" - Windows account NT AUTHORITY\NETWORK SERVICE; mailbox /O=MyOrganisationName/OU=Place/cn=Recipients/cn=RandomAccountName
    Error: 1100
    Client Machine: *MYSERVERNAME*
    Client Process: edgetransport.exe
    Client ProcessId: 0
    Client ApplicationId: Client=Hub Transport

     

    After I restart the server, everything works fine.

     

    I know it is a long shot but any advice gratefully received.


    Thursday, April 21, 2011 7:50 AM

Answers

  • Hi
       event 1020,1035 1022is valueless.
       event 1164. You can read this article.
       The number of available sessions is set by adding these three values together using the following formula; msExchMaxPoolThreads multiplied by the number of processors + msExchBackgroundThreads + msExchMaxThreads multiplied by 3/4.
       Your value seems to be enough. You can try to increase it.
        event 1107.  You can read this article
        If it occurs only once, you needn’t to care for it.
        If it occurs continually, you need to maintain the database.
       event id 7200
        Explanation
        The Information Store runs many tasks and performs maintenance operations in the background. Problems may occur when the maximum size paged or non-paged pool that can be allocated by one process has been limited on the Exchange server.The default value of these registry keys is 0. If a value between 1 and 128 has been specified, no single process can allocate more space in the pool than the specified amount. When the value of these registry keys is set to 0, there are no pool quotas.
       User Action
       Make sure these registry keys are set to the default value of 0.
       According to these events, you should check memory of server and connection with DC/GC.
       My suggestion is to add memory.
       If it doesn’t work, please run eseutil to maintain Second Storage Group\Mailbox2 Database and scan harddisk.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Terence Yu Friday, April 29, 2011 3:12 AM
    Friday, April 22, 2011 2:51 AM
  • Its looking your server is facing resource crunch, have you done proper sizing for memory and processor. Exchange 2007 is very hunger for resource compare to earlier version... (Its all for good, and use all available resource for best response).

    What is page file you have setup, it should be sie of RAM+10 MB .Terence has provided good information above..

     


    Anil
    • Marked as answer by Terence Yu Friday, April 29, 2011 3:12 AM
    Friday, April 22, 2011 8:18 AM

All replies

  • Hi
       event 1020,1035 1022is valueless.
       event 1164. You can read this article.
       The number of available sessions is set by adding these three values together using the following formula; msExchMaxPoolThreads multiplied by the number of processors + msExchBackgroundThreads + msExchMaxThreads multiplied by 3/4.
       Your value seems to be enough. You can try to increase it.
        event 1107.  You can read this article
        If it occurs only once, you needn’t to care for it.
        If it occurs continually, you need to maintain the database.
       event id 7200
        Explanation
        The Information Store runs many tasks and performs maintenance operations in the background. Problems may occur when the maximum size paged or non-paged pool that can be allocated by one process has been limited on the Exchange server.The default value of these registry keys is 0. If a value between 1 and 128 has been specified, no single process can allocate more space in the pool than the specified amount. When the value of these registry keys is set to 0, there are no pool quotas.
       User Action
       Make sure these registry keys are set to the default value of 0.
       According to these events, you should check memory of server and connection with DC/GC.
       My suggestion is to add memory.
       If it doesn’t work, please run eseutil to maintain Second Storage Group\Mailbox2 Database and scan harddisk.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Terence Yu Friday, April 29, 2011 3:12 AM
    Friday, April 22, 2011 2:51 AM
  • Its looking your server is facing resource crunch, have you done proper sizing for memory and processor. Exchange 2007 is very hunger for resource compare to earlier version... (Its all for good, and use all available resource for best response).

    What is page file you have setup, it should be sie of RAM+10 MB .Terence has provided good information above..

     


    Anil
    • Marked as answer by Terence Yu Friday, April 29, 2011 3:12 AM
    Friday, April 22, 2011 8:18 AM