Got a problem with an application that we're running on our server that has me stumped. It's an NT 4.0 box that's also our PDC. The application is a proprietary Human Resources database uses COBOL as the underlying code (yes, I know, I know, but it was purchased WAY before I ever got here and it's not feasible to make a change right now). The usual procedure for setting up a new computer to run this program is to simply set up a shortcut on the desktop that maps to a file called wrun32.exe that starts evrything up.
I've run into a problem, though. I changed out a user, swapping a four-year-old Windows 95 box for a Dell Inspiron 2500 laptop running Windows 2K Pro. The user can get into the program fine, but after a certain amount of time, and afer performing different actions, they get an error message saying that there was a problem with the file wrun32.exe and the application will be terminated. Then a Dr. Watson message is generated in the event view of the workstation, ID 4097:
The application, , generated an application error The error occurred on xx/xx/xx @ xx:xx:xx The exception generated was c0000005 at address 0046AB13.
This error only comes up on this machine. Could there be something about the way W2K is set up that inhibits server-based apps like this? Or is it something else? Help! Me: We need a better backup system.
My boss's boss: Backup? We don't need no stinkin' backup!
I've run into a problem, though. I changed out a user, swapping a four-year-old Windows 95 box for a Dell Inspiron 2500 laptop running Windows 2K Pro. The user can get into the program fine, but after a certain amount of time, and afer performing different actions, they get an error message saying that there was a problem with the file wrun32.exe and the application will be terminated. Then a Dr. Watson message is generated in the event view of the workstation, ID 4097:
The application, , generated an application error The error occurred on xx/xx/xx @ xx:xx:xx The exception generated was c0000005 at address 0046AB13.
This error only comes up on this machine. Could there be something about the way W2K is set up that inhibits server-based apps like this? Or is it something else? Help! Me: We need a better backup system.
My boss's boss: Backup? We don't need no stinkin' backup!
