Error 9175 and 4319

[creeve2005]

About every 3 months, just like clockwork, Exchange screws up. I really believe malicious code is purposely written in to all Microsoft products just to piss people off. Now each time this happens I have to reinstall Exchange as none of the Microsoft fixes work (surprise, surprise).

Anyway, enough venting, does anyone have an actual fix for these two errors.

9175: This just states that the information store is not running. I know this - but what I don't know is why this happens every three months or so just out of blue. I restart the service and within 1/2 hour it is not running again. MS fixes don't work.

And something new just in........

4319: Something about a duplicate name on the network. Now unless someone hacked in and changed something, there is a different name for each of my machines, and has been for the last year or so......

Any help is appreciated. Next step is to install a non MS mail server and maybe Novell - Get ride of Active Directory and Exchange all together.....

Thanks

 

[paulha]

I would check out the duplicate name business, it could well be the source of your problems, given that you install exchange once a quarter and still get the same problems. A bit more in depth troubleshooting is called for her rather than a reinstall.

9175 - anything in your event logs ?

4319 - is your DNS showing anything obvious ? - do you reset the mailserver name in AD when you rebuild it ? Do you clone PC's ? etc etc

I would suggest that you would still have the same problems with a non MS mailserver until you address the root cause of your problems

Hope this helps

Paul

 

[xmsre]

4319 is a netbios name resolution conflict. You have WINS or master browser issues.

9175 If the host name can't register because of a conflict, that explains why exchange SA won't come up.

"Any help is appreciated. Next step is to install a non MS mail server and maybe Novell - Get ride of Active Directory and Exchange all together....."

You could do that, however it likely won't resolve your issue. You have issues in your network infrastructure that you need to investigate and resolve. Changing out the application servers won't resolve the underlying network issues, you'll have as many or more problems with the new application server. You'll compound the problem by throwing in a migration.

I would:

1. Take a break
2. Have an adult beverage
3. Get a good nigh't sleep
4. Examine your network infrastructure in detail. Pay close attention to name registration - DNS and WINS.

 

[creeve2005]

Thanks for the replies.

This is the actual error I get in my Event Viewer. One about every 3 minutes.

The MAPI call 'OpenMsgStore' failed with the following error:
The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.
The MAPI provider failed.
Microsoft Exchange Server Information Store
ID no: 8004011d-0526-00000000

Like I said, I know the service is down - what I don't know is why.

There are no duplicate names on the network, DNS is fine and has been all along. Ntbstat -n shows no duplicate names. I have gone through my Active Directory and all is as it should be. This error only appeared the once, this morning - the only errors in my event viewer is the one above.

I'm wondering if I create a new message store and move all existing email addresses etc. to it if that will solve the problem.

 

[creeve2005]

Is there some kind of script I can use to monitor the Information Store - and if it stops restart it. Other than reinstalling Exchange which I've now done about 4 times because of this idiotic problem, this is the only thing I can think of. I'm tired of having to reinstall every 3 months.....

I don't know how businesses use this, luckily mine is just a personal server and not critical. Damn annoying none the less.

Thanks

 

[xmsre]

If you're on Windows 2000 Enterprise, Load a single node cluster with a local quorum. Then you can use service restarts. One of the advantages of W2K3/E2K3 is you get the service restarts without loading a cluster.