Link to home
Start Free TrialLog in
Avatar of Jim Dettman (EE MVE)
Jim Dettman (EE MVE)Flag for United States of America

asked on

Fault in MSO9.DLL

Wondering if this rings a bell for anyone...
 
 I've got a client that has an Access 2000 program that is randomly generating a fault in MSO9.DLL.  
 
 It always faults at offset 0x0007b9f2 with a 0xc0000094, which is a divide by zero error.
 
 This program has been solid for years and now is faulting for some reason. SQL Server is the backend.
 
 There are numerous apps running on this server (2008 R2) and none are having problems except this one. Nothing new or has been changed that I'm aware of.  Things I have done:
 
1. Rebuilt the DB - fresh MOB, imported tables and queries, did saveastext/loadfromtext for forms and report, and cut and pasted all code from old to new. New DB compiles fine.
2. Compacted and repaired.
3. Turned off name Auto correct.
4. Replaced the MSO9.DLL from another machine
5. Renamed MSO9.DLL and then did a repair on Office 2000.
6. Doesn't appear to be a resource problem; happens with as little as processing a few orders or a hundred and I can turn around and process the batch that just failed and it will go through fine.
 
Any thoughts are welcome.  I've been hacking away at this for about five days now and it's driving me nuts.
 
Jim.
SOLUTION
Avatar of Gustav Brock
Gustav Brock
Flag of Denmark image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Jim Dettman (EE MVE)

ASKER

gustav,

  I've been thinking about a full re-install, but have been hesitant...no other app is having any kind of issue.

  It could be that the Access install is broken and that only this application is hitting something the others do not, but it's a long shot.

  It basically is doing what other programs are doing and there is nothing unique in terms of it's processing except for handling CC processing, which is done with a reference set to Microsoft XML, ver 6.0.  That code however is not being used or called at this point and hasn't been for a few years.  It was in-place before this started to happen.

 Just to be sure though, I think what I'll do is comment out the code and remove the reference.  You also mentioned temp files, which I meant to clear and forgot about.

 Really odd problem.    This will go on my all-time top ten Access problem list.   Never have seen anything like it.

Jim.
OK, seems like commenting out that code is a place to continue testing.

/gustav
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Found answer myself.
So the app runs on the server?

/gustav
Yup.   Since turning off DEP, it hasn't faulted once.   I had turned off DEP for Access when they first moved onto this server and apparently a Microsoft security updated turned it back on.

Jim.
OK.

/gustav