Avatar of mdhaber
mdhaber
 asked on

Exchange 2003 errors locking up server intermittently 0x80004005

I have been getting the below errors for about 2 weeks now. When the error happens the exchange server becomes unavailable for about 10-15 minutes.  I also cannot terminal service in during that time.  I don't know if these errors are the cause or the symptom of something else.  After the period of time the server becomes accessible again and functions normally.

The server is server 2003r2 with sp2

Background thread FDoUpdateCatalog halted on database "First Storage Group\Mailbox Store (FATPAFILE01)" due to error code 0x80004005.

One of the System Attendant's task is blocked.
Function: CMonitoringTask::Work

One of the System Attendant's task is blocked.
Function: CPollDomainExchangeServersGroup::Work

One of the System Attendant's task is blocked.
Function: COffLineABScanTask::Work

Thanks
Windows Server 2003Exchange

Avatar of undefined
Last Comment
mdhaber

8/22/2022 - Mon
Member_2_6492660_1

mdhaber

ASKER
That seems to relate to exchange 2000.  The issue is also not happening every 15minutes.  Full time indexing is already disabled though i went though the procedure detailed anyways.

Thanks
ASKER CERTIFIED SOLUTION
Simon Butler (Sembee)

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
mdhaber

ASKER
I have added all exchange related directors to the exception list of endpoint protection as they were not there.

c:\program files\exbpa\*
c:\program files\exchsrv\*
d:\exchsrvr\*  <----store location

As I said it is very intermittent, hopefully this will help.  Ill report back in a few days if the errors have stopped happening.

I will also run the exchange bpa

Thanks
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck
Raghavendra Radhakrishna

follow these steps:

1. Download the sys internal tools from microsoft website.
2. Use the procmon tool to investigate which file or registry key is used by system attendant and is the AV is culprit to come in the way of system attendant.
3. After narrowing down the issue, disable any Antivirus or any program causing this error.

Alternatively, put some performance counter for the whole day for analyzing all the process.
By doing that you can find out at what time, which process has caused the exchange server to hang.
mdhaber

ASKER
I uninstalled mail security and endpoint security.  The lockups have gone away and the system attendant issues have resolved.  Now to figure out why I am getting a vss security error and i might actually get this thing figured out.