[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

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

Exchange 5.5 + NAV Service??

We're currently running an NT4, Exchange 5.5, & Norton Anti-Virus Corporate edition. (All with latest SP's)

On Friday for no apprent reason the NAV for Microsoft service failed to re-start after an offline backup. On examining the event viewer there are two error releated messages.
 1. EventID: 85
     Description: Service can not start since the Auto-Protect could not be started
 2. EventID: 185
     Description: The service will be shutdown due to an unexpected failure initalizing virus protection.

I can't seem to find anything on the EventID's, or any reason for this to happen.

I'm wondering if there might be a corruption in the priv.edb (it's pretty big @ 42GB!) so I'm currently running isinteg on it, but it looks like that going to takes ages.

Anyone got any ideas on what's causing this and how to fix it?
0
njwilkinson
Asked:
njwilkinson
  • 4
  • 3
1 Solution
 
OneHumpCommented:
Is this NAV for Exchange or just NAV on the server?

OneHump
0
 
njwilkinsonAuthor Commented:
NAV for Exchange
0
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

 
njwilkinsonAuthor Commented:
Well, isinteg finally finished and came back with 922 fixed errors, I've also just run the Consistancy Adjustment in the Exchange Admin console and that sorted out a load of things, but I', still getting the Dr Watson on the NAV service after about 10 minutes.

A definitions update could have done it. I didn't manually update it, but Auto Update is set to run (can't specify when on this version, just how many times a month).

I did read an article saying that a possibility could be the .dat files are corrupted. Do you think this might have happened?
0
 
OneHumpCommented:
It's possible.  I've seen McAfee definitions blue screen servers.  That is not necessarily a lot of errors, but any amount of errors is not great.  Keep running Isinteg until you get 0 errors.  That's how it's done.

You may also want to get on the phone with Symantec.  I think it's free and they might have more info for you.  Their KB is pretty limited.

OneHump
0
 
njwilkinsonAuthor Commented:
Running isinteg again seems to have nailed it.

This time it found another four errors and without wanting to leave it another eight hours to do another test I tried to fire up all the services and it all worked! Hurrah!

Still not sure what caused the database corruption in the first place though?

Thanks for your help OneHump.
0
 
OneHumpCommented:
It's my pleasure.  ISInteg doesnt really find database corruption, per say, but it looks for broken links between fields in the database.  For example, you might have a message in your message table with a link to a corresponding field in your folder table that doesnt exist.  If you were to delete a message from your M drive you could break a database link.  It's not terribly uncommon to have errors, but it's not common to run with errors either.

ESEUTIL is what fishes out database corruption.  It looks at the checksum for data stored in the database and delete pages with bad checksums.  That's why it's destructive.  ISINTEG is pretty harmless.  That statement has been debated on this forum, but ISINTEG is not going to break anything that's not already broken.  The readme file could lead someone to believe otherwise though.

OneHump
0

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.

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