[ Back | Print ]
Technical Information Document
Summary: MPREXE error with Win95 and Client32 - TID2907849 (last modified 19MAR1998)
printer friendly tell a friend
Click here if this does not solve your problem
2907849 2907849

The following errors have been received on a Windows 95 client using the Novell's Client32, usually at the begin or during the login script processing:

     General Protection Fault in MPREXE.EXE

     MPREXE caused invalid page fault

     MPREXE: This application performed an illegal operation and will be shut down.

     MPREXE caused an illegal page fault in module kernel32.dll

The following error was received when dialing out, when the station was docked, or when using the dialup PPP connection:

     MPREXE caused a stack fault error in Kernel32


MPREXE.EXE is a Microsoft file that allows Windows 95 to have more then one client and protocol. MPR stands for Multi (or Multiple) Provider Router. It's primary function is to route incoming and outgoing packet between the adapter and different clients.


The following is a list of known solutions to a MPREXE error:

1. Removing HIMEM.SYS from the CONFIG.SYS file will, in some cases, resolve this error. To do this, restart the computer, press F8 when seeing "Starting Windows 95" on the top of the screen, then select the option "Command prompt only" in the menu. You will then be on a dos prompt. Use EDIT to modify the CONFIG.SYS and reboot the computer.

Two comments concerning this solution:

a. Although HIMEM.SYS has been removed from the CONFIG.SYS, it will still be loaded by Windows 95 (it is needed to access the extended memory), but somehow that prevents the GPF from occurring.

b. After removing HIMEM.SYS, you will not be able to load EMM386.EXE anymore, which means that you will not be able to enable the upper memory area. As a consequence, all device drivers and TSRs will be loaded in conventional memory.

2. Another solution to resolve this error is to delete and recreate all the network printers defined. To do this, remove HIMEM.SYS (see above) and restart the computer. When in Windows 95, go into the printer folder and delete all the network printers. Then, edit the CONFIG.SYS to put back HIMEM.SYS and restart the computer. Then, recreate the network printers. This solution is better than the first one since you will still be able to load device drivers and TSRs into upper memory, if needed.

3. It has been determined that the MPREXE error has occurred when attempting to capture during the Login Script with certain conditions. The two solutions for this situation are:

a. In a NetWare 4.1 environment, login to the Directory Tree instead of a Server by editing the properties for Client 32, Login Tab and selecting "Log in to Tree".

b. Remove the capture statement from the Login Script and capture the print queue using Windows 95 network printer configuration.

4. Using the map change command in a login script could generate a MPREXE error.

For example: map c ins W: s3:

Currently the only solution is to not use the map change command in your login script. This issue will be resolved with the next release of Client32

5.Check the hardware specification of the computer if it ships with Matrox Millennium video cards (MGA) . The shipping version of this driver for the Matrox Millennium video cards (MGA) will cause this error. New drivers that solve the problem can be obtained from Matrox at www.matrox.com/mgaweb/ftp.htm.
The following computers were found with this video card built in:
Gateway P166 machines
Compaq Deskpro 6000

6. In the case of using a dialup adapter and receiving a MPREXE error, removing Microsoft's IPX/SPX compatible protocol and Novell's IPX 32-bit protocol from the dialup adapter bindings resolved the error. In this case, TCP/IP was the only protocol required for the dialup adapter. In other situations, however, other protocols will be required and further research will be needed to resolve the issue.

7. Disable the GUI Login and run it from the startup folder. To disable the Client32 GUI login, create or modify the following registry entry: set 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Network\Real Mode Net\AutoLogon' equal to 000 00. If creating the AutoLogon Key, right click on RealMode Net, choose New and Binary. The value 0000 00 means no login on bootup. 000 01 means Login on bootup.

8. Ensure that the SET PATH statement in the autoexec.bat is less than 80 characters. The path statement can be broken into multiple lines which can be used to append together a statement that is longer then 80 characters.

9. MAP a regular drive to a server in the tree that has the master replica.

10. Gateway P60 machines with bios revision 1.00.03.AF1 will not run with Client32 (Dos/Windows or Windows 95). Updating the bios to revision 1.00.06.AF1 (available form Gateway) will resolve this problem.

11. Remove references in the login script to invalid DS objects. When the DS has been altered, but the login script still references an invalid objects, this has caused this error.

12. Install the latest Client32 for Windows 95 that ships with NetWare 4.11.

In rare cases when nothing else has worked, reinstalling Windows 95 on the workstation has resolved the issue. It is important to recreate the registry files during the reinstallation by completely deleting the existing Windows 95 configuration from the hard drive prior to reinstalling.

13. Spanish version of Client32 for Windows 95.

With the 32 bit Client for Windows 95 in Spanish and the Windows 95 in Spanish version too, you may have to configure the regional configuration in "Spanish from Spain (International Alphabet)"

14. Check and make sure that the Date & Time on the Server is current. If the Server is set to year 2000 or later and every time Client32 connects to the server, the Client will set itself to the year the server is set to and Windows 95 does not handle the year 2000 easily and generate a General Protection Fault error. Check with the latest Service Pack (3 or later) for Windows 95 to see if Microsoft has fixed the problem.

15. If the group name in a group policy is greater than 39 characters, the client will MPREXE upon boot up. The 39 character restriction is a Microsoft limitation, not a Novell problem. Novell's client will request from DS and successfully return the groups that a specific user is a member of. The client will then hand these groups over to mprexe.exe for processing concerning the group policies. Once a group name longer than 39 characters is passed to mprexe.exe, Microsoft's code will blow up. To fix this either do not use group policies, limit the group policy name to 39 characters or less, or talk with Microsoft and ask them to modify their code to allow longer group names to be processed. Users who see this problem either have a group with a long name, or have a group in DS that is several containers down in the tree, thus giving the entire distinguished name of the group a character count greater than 39.

Search String: mprexe mpr mpr.exe mprexe.exe win95 client32 cl32

Document Title: Summary: MPREXE error with Win95 and Client32
Document ID: 2907849
Creation Date: 20MAY1996
Modified Date: 19MAR1998
Document Revision: 24
Novell Product Class: End of Life (EOL)
Management Products
Novell eDirectory
Novell Product and Version: NetWare-EOL
NetWare 4.11
NetWare 5
NetWare for Small Business 4.11
Novell Clients
Z.E.N.works (April 98)
Z.E.N.works 1.1
ZENworks 2
intraNetWare 4.11
NDS for NT 2.0


The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.

Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.

[ Back | Print ]