Windows Forum

Ask something
Discussion Locked

Dr. Watson: Exception access violation

0 helpful
7 replies

by stergios_nik

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hello,

I have a PC 700 Mhz (web server, mail server) running Exchange 5.5 + Internet Information Server 3.0, Service Pack 6.

I also run an Active Server Page application on the Server thus allowing remote users to retrieve database informationfrom Access 2000, which is also installed on the same PC.

Unfortunately Office 2000 installed the MDM.EXE debugger, and this causes the problem that every time an error is encountered in my ASP page, then the MDM.EXE process calls the debugger and STOPS the IIS 3 services (web, ftp).

I solved this problem by killing the MDM.EXE process but now I am facing another problem. The Internet Information Server inetinfo.exe crashes every 30-48 hours. I checked the logfiles but I did not notice any unusual behavior. The IIS 3 is not crashing because of active server pages but on simple html files.

The error message is:
Dr. Watson for Widnows NT
An application error has occured and an application error log is being generated, inetinfo.exe. Exception: access violation(0xc0000005), Address: 0x77f6954b.

I searched in the Microsoft Knowledge base and found an article and says that I have to remove/install the NETBIOS again.

I am thinking of upgrading to NT option pack 4 hoping that this will solve all my problems but I do not know if this will cause any problems to my Exchange 5.5 configuration.

Any suggestions are welcomed...
Have a nice day!

7 replies

by churdoo

Hmmmmm. Exchange 5.5, Internet Information Server 3.0, Service Pack 6, Active Server Page application, Office 2000.

Besides being a busy little server, if there were a caption "What's wrong with this picture?," It would definitely be the IIS 3.0.

I don't think you can do anything but good installing the IIS 4.0 off of the NT Option Pack and then re-evaluating the situation. The only qualification I can make, is that if I recall correctly, IIS 3.0 to 4.0 isn't an upgrade path ......meaning, that you will need to UNINSTALL IIS 3.0 before you install IIS 4.0.

By doing the uninstall, the site content will remain on the server hard drive, and the IIS 3.0 will be removed. After you install IIS 4.0, and the office 2k extensions, if applicable, and I think there may or may not be a service pack too, you will have to add each of the sites back, pointing them to the appropriate directory of the sites content.

I hope this helps.
--Charlie

by mjervis

Just went through this myself.

In order to upgrade to the option pack 4 you must follow the following procedure.

1. uninstall IIS 3
2. Re-install service pack 6 for NT
3. install the option pack
4. installl option pack service pack

I washaving the same problems and I went to Microsoft for the answer. My $250.00 session with Microsoft produced that fix. So far (fingers crossed) it has worked.

Even without doing anything but just removing IIS 3 you still need to re-install the service pack for NT. No idea why except the fact it is a Microsoft world and they graciously allow us to live in it.

by mckaytech

Upgrading the IIS should not affect the Exchange configuration in any way since you're apparently not using Outlook Web Access. And I certainly agree with the other two answers that IIS 3.0 is beyond it's useful life and should be upgraded.
Just make sure you have a verified backup before you begin and follow the procedure in the answer above and you should be in good shape afterwards.

As far as the re-application of the service pack after the un-install of IIS 3.0, it's actually quite a trick to maintain version syncronization between all the different DLLs that make up the OS. If the un-install removes even one DLL that is necessary to run, things get ugly. Re-running the service pack just ensures that all the necessary DLLs are present and of the correct version before you add the new upgraded software.

Incidentally, it's not much different in the Linux world. I recently upgraded one component of a Linux box and because of library conflicts, ended up having to upgrade another 30 or so interdependent components.

paul

This discussion is closed to new replies.