Daily Dr. Watson Error for IMS

[DefStryk]

Every morning when I login my Exchange 5.5 server to check it there is a Dr. Watson error on screen.

It reads...

An application error has occurred and an application error log is being generated.
MSEXCIMC.exe
Exception: access violation (0xc0000005), Address: 0x0043550a

There are the options "OK" "Cancel" and "Help"
Clicking OK and/or Cancel do nothing but close the window, no error log is generated or displayed.


The server is an NT box with SP3

 

[DefStryk]

also, along with this error, in the services the Microsoft Exchange Internet Mail Service (IMS) has always stopped running and needs to be manually restarted.

 

[Zelandakh]

An NT4 server with SP3? SP4 was a stable service pack about 7 years ago - recommend upgrading. Plus any other windowsupdates not installed.

Exchange 5.5 but which service pack? Any fix ups installed?

Anything else of use in event log?

 

[DefStryk]

sorry, we have NT SP4

and for exchange the current is SP3

 

[zbnet]

Latest NT4 service pack was SP6A - I wouldn't run Exchange 5.5 on anything less.

Latest Exchange 5.5 service pack was SP4, although there was a post-sp4 hotfix rollup (which was the closest thing to being SP5 for Exchange 5.5). I wouldn't run Exchange 5.5 with anything less.

 

[Zelandakh]

Patch your OS to the latest everything using windowsupdate / WSUS / SMS and then install Exchange 5.5 SP4 and the post SP4 hotfix rollup and see if that cures your problem.

 

[DefStryk]

that would probably be the best course of action, unfortunately. if you refer to this post...

http://www.tek-tips.com/viewthread.cfm?qid=1430515&page=1


i'm guessing theres not enough space to update.
unless any of you can verify that the error we're getting is because of the lesser service packs installed (note this problem only started about 2 weeks ago) then we will not be able to update at this time.


we are going to be migrating to Exchange 2003 on a new windows server 2000 machine, but we have other projects that have to be completed prior to that happening, so we're looking for a quick fix to keep the IMS on the 5.5 stable until we're able to migrate.

 

[Zelandakh]

I'd say it isn't helping but I've never seen an IMS break like that. If you don't have enough disk space on your email server I'd say you need to get that fixed urgently, patch your server (you are leaving yourself open to attack without patching it anyway) then upgrade as soon as you can.

You are upgrading to Exchange 2003 when Exchange 2007 has been out long enough for SP1 to be released? And you want to put it on Windows 2000? What is your thinking around that?