Search

AMSEXPW Caused a General Protection Fault in Module VBRUN300.DLL
 

The file C:\WINDOWS\SYSTEM\VBRUN300.DLL may be out of date. The valid date for this file for Express for Windows™ is 8/6/96 and the file size should be 398416.
 

Rename the VBRUN300.DLL file to VBRUN300.OLD and reinstall Express (standalone installations) or rerun the Workstation setup (network installations)
 

There may be multiple copies of VBRUN300.DLL. Search the drive where Windows® is installed - usually C: - for any copies of VBRUN300.DLL that may exist in directories other than C:\WINDOWS\SYSTEM.
 

The problem may be too many un-purged request groups.  Each "batch" of requests entered by each user is saved in a request group.  Once a system contains about 200 request groups, or about 2000 individual requests (not reports), this error can occur.  The solution is usually to purge most of the old request information.

• If on a network, have all users exit from Express. 

• Restart Express on one computer only.

• Select File then Repair Database to repair the database.

• Select File then Compact Database.

• Select File then Purge Database.  

  • Select the Requests option.

  • Select to purge requests for Reports Received.  Enter whatever To: date the users wants, but ideally only the last few weeks should be kept. 

• After the Purge completes, shut down and restart Express

• Repair and Compact the database again. 

• Try again to enter requests.

• If the error still occurs, you may need to go into the individual request groups for all users and manually delete the oldest request groups one at a time. Then proceed through the Repair and Compact steps again.

The error occurred for all users. This was a network installation. This error can also occur on a standalone workstation.
 

The problem was a corruption of some kind in the database. You can test this if you have a copy of Microsoft Access.  Launch Access and attempt to repair the database.  The Express database is located at x:\AMSEXPW\DATA\EXPRESS.MDB or x:\EXPRESSW\DATA\EXPRESS.MDB where x: is the drive containing the Express program.

Do not convert the database if asked!

If Access says that the database is corrupt, repair the file and try Express again.

If Access says the file is not a valid Microsoft Access database, the database is corrupt and must be replaced.  Delete the file EXPRESS.MDB and reinstall Express for Windows.
 

Consider these scenarios:

• In one case, if the user clicked the  Ignore button on the error message several times, the program would start. He then got an error referring to the file MLIST.VBX . We found that the file C:\WINDOWS\SYSTEM\MLIST.VBX had a newer date than our version (which is dated 6/26/94), but the file size was much smaller than ours (which should be 32896 bytes). We renamed MLIST.VBX to MLIST.OLD and then reran the installation. Express worked OK afterwards.

• In another case, Express had just been installed.  The user had not restarted Windows since Express was installed.  We had him reboot and restart Windows.  Express then started successfully.

Error was occurring on a Windows 95 station that was loaded as Standalone. 
 

The solution that finally worked was to:

• Remove Express and delete the AMSEXPW.INI file.

• Reboot the workstation in Safe Mode. To do that:

• Select Start button

• Select Shutdown

• Select Shutdown and restart

• When the message that says: "Starting Windows 95" appears, press the F8 key.

• From the menu that appears, select Safe Mode.

• Windows 95 will start and will not attach to the network ( if one exists ) and will not load special device drivers. The screen may look a little different, i.e. the resolution (icon size) may be larger or smaller than usual. 

• Reinstall Express and then see if it will run successfully.

• If so, Restart Windows 95 in standard mode - i.e. the normal way and see if Express will work.

This page has been viewed 13633 times | Document Rating is  -- / 5.00 | Last Updated on 4/28/2004 7:08:43 AM