Invalid Page Fault when sending emails with outlook exp 2

[markstangroom]

i have a user who has started getting invalid page faults in module ole32.dll whenever he tries to send an email with OE6.

The microsoft knowledge base article refers to norton scanning software which this user doesn't have installed.

I re-installed ie & oe stopped all the startup programs with msconfig.

They can receive email ok.

what is ole32.dll ?

any pointers would be much appreciated.

 

[mattjurado]

Try the following:

If there are a lot of e-mails, try clearing out the deleted and sent items folders.
Go to File>Folders>Compact All Folders.
Restart OE.

If the problem persists, reinstall the mail account (Tools>Accounts). Try using the IP address of the SMTP server instead of the regular dns name.

Matt

 

[markstangroom]

Matt

i've tried all of the things you suggested and still no luck.


Mark

 

[mattjurado]

I found a few things, by using google, have you searched yet?

Rename the offitems.log file, try again.

One of your mail folders could be corrupt. I think they have .dbx extensions in version 6. Rename them one by one to .old, see if you can track down the culprit. Once you rename them, the program will create new ones in their place. Don't worry, you can always rename them back to retreive your old stuff.

Matt

 

[markstangroom]

sorry Matt tried all your solutions still no luck.

I've set up the user on Outlook 97 hoping to bypass the problem but it's now happening with Outlook.

I've reinstalled the ole32.dll file as this seems to be the root of the problem.


But this hasn't helped.

Don't know if you have any more ideas.


Thanks

Mark

 

[joegz]

Try using Dependency Walker (

http://www.dependencywalker.com)

to see if you can figure out why it doesn't like this file. It is best when you run dependency walker on one machine where it works and then on the machine where it doesn't work and compare the results. A bit tedious but I have solved many DLL issues with this tool.

The problem may not necessarily be the OLE32.DLL file but a file that the library calls that may the problem. Sometimes if one the IE library files get replaced with a different version you can get this kind of problem.

joegz
"Sometimes you just need to find out what it's not first to figure out what it is."