Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 773
  • Last Modified:

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
0
mdhaber
Asked:
mdhaber
1 Solution
 
Thomas GrassiSystems AdministratorCommented:
0
 
mdhaberAuthor Commented:
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
0
 
Simon Butler (Sembee)ConsultantCommented:
Usual cause of that is AV software scanning something it shouldn't be. Ensure that any file level av is not scanning the Exchange directories.

I would also run the Exchange BPA against the system to ensure it doesn't flag anything else.

Simon.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
mdhaberAuthor Commented:
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
0
 
raghavendra2512System AdministratorCommented:
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.
0
 
mdhaberAuthor Commented:
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.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now