Outlook Page fault on outllib.dll when I try to send new email 1

[hchman]

I have recently been getting a page fault error on the outllib.dll file when I click on new mail message or try to reply to an existing message. I can view a message with no problem. I tried reinstalling Outlook but I still get the error.

 

[SimonDavis]

What is the actual error message? It could be one of several things.

Have you installed any new software (even if unrelated)? Could it have 'updated' any of your libraries (.dll files).

This problem often happens when you have incompatibilities like language versions - I once tried to install English help files over a Portugese installation of Office, and spend the rest of the day reformatting and installing a very dead computer.

 

[hchman]

Thank you for responding. The message is OUTLOOK caused an invalid page fault in module OUTLLIB.DLL at <memory address>. I do not have the exact address (I didn't write it down). What I did to get around this error is to not log onto the network until Outlook is opened. It askes for a server, domain and password. It works fine this way but I still need to fix it so I can get this user logged onto the network for all other resources. I have not idea at this time. I found the work around by accident. As to your other question I did not install any new software on this machine.

 

[SimonDavis]

Hmm. Works when user not logged on (I guess you're just connecting to the exchange server, not logging on to the domain).

What version of outlook is this? Did you install it from the same disk as the other office components, or from a different disk - if so have you tried replacing just the outlib.dll file you are using with the one from the original Office disk?

Does it happen with all users logged onto that machine?

Are you running other programs at the same time, and have you tried without running them? If you have the time, you could hit ctrl+alt+del before running outlook, to get a list of running apps, and try ending those tasks one by one (don't close mapisp32 though). You will eventually crash your machine doing this, but just fire up again and don't stop that application!

You might also compare the list of running apps on the rogue machine with one that works (logged in as the same user).

You might find out what Outlook is fighting with.

Can't offer a real solution beyond that. If you get any interesting results let us know, it might jog a memory!