Solved

Client Access and Page Fault in OLE32.DLL

Posted on 1998-11-19
1
243 Views
Last Modified: 2013-12-29
Client Access/400 give an error "Diagsvr.exe caused an invalid page fault in OLE32.DLL.

Any ideas.
0
Comment
Question by:rblackma
1 Comment
 
LVL 7

Accepted Solution

by:
cmcgee earned 200 total points
Comment Utility
Check this page out. Here is the Link and the Contents of it.

http://bsing.com/bo400ng/AS400Q0013.htm

Question:
   I just installed client access for the first time. Version 4. I am using twinax and it connected to the as400 v3.2 just fine. It ran all day long just fine. The next day I started CA95 and now I am getting "This program has performed an illegal operation and will be shut down". DIAGSVR caused an invalid page fault in module OLE32.dll at 014f:19e016b8. I can't get rid of this message. I click on close and it just keeps comming back. Has anyone heard of this message? What do I do to correct it?
 

 


Answer:
   This happened at one of our clients recently, but we are using pure Netsoft 32-bit version 2.2?, so it is probably something in the twinax router. I did the same things you probably tried, checked to make sure some boob hadn't changed a setting, hadn't installed a new software package lately, or been fooling around with registry entries. Sometimes after clicking on "OK" 3 or 4 times(even though it WASN'T OK!!), we would get through, and sometimes it would just lock up the PC. Just for yucks, I tried renaming the diagsvr.exe to diagsvr.old. This time, I got a "Server busy" message, but when I clicked OK on that, it WORKED!! I tried several reboots and it would either work right off, or get a "Server busy", which would actually go away by itself after 10 seconds or so. Anyway, the proper thing to do is call Netsoft tech support, leave a voicemail, spend a day or so playing phone tag with them, and have them tell you to change a setting in some .INI file, or download a patch file, or change some registry entry. Or you can just try renaming diagsvr.exe, and see if it works.
 


Answer:
   Find the file NSDGNS.DGS and delete it. This file apparently gets corrupted and it will be recreated when you try running diagnostics again
 

0

Featured Post

Maximize Your Threat Intelligence Reporting

Reporting is one of the most important and least talked about aspects of a world-class threat intelligence program. Here’s how to do it right.

Join & Write a Comment

A few months ago I had an issue with LaserJet 1020 printer which was installed to XP and Windows 7.  It was installed to XP and working, but when I tried to connect from a Windows 7 PC, it would attempt connection and then fail.  Sometimes the Spool…
Our Group Policy work started with Small Business Server in 2000. Microsoft gave us an excellent OU and GPO model in subsequent SBS editions that utilized WMI filters, OU linking, and VBS scripts. These are some of experiences plus our spending a lo…
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

763 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

9 Experts available now in Live!

Get 1:1 Help Now