[RESOLVED] Cannot log into network, hangs on mprexe.exe

[Xavier]

This has all the sudden happened on like 6 computers in the company. Very strage.

I get to the login screen just fine. When you type the password it just seems to hang. If you CTRL-ALT-DEL it you see that mprexe.exe[not responding]. Close it does nothing.
But if you just wait if it hangs it will pop a message up after about a minute saying "you password is wring or server is not avaible" (or something like that). I KNOW the password is right, so thats not it. So sites say to delete the pwl files but that is not working in this case.

This has happened on pc's that were either new or reconficured for whateve reason. It has happened in both win95 and 98.

HELP!!!

[tregee]

Multi provider router

What type of platform are you running?
Netware priamarily with a little NT maybe?

Let me know

I Have a little something you might want to check out though.
Goto support.novell.com and check out TID 10012061 in the knowledge base

Hope this helps

[This message has been edited by tregee (edited November 16, 2000).]

[kornesque]

check out this kb article...

Windows 95/98 Clients Hang with "Mprexe.exe Not Responding" [crossnet]
ID: Q234647 CREATED: 06-JUN-1999 MODIFIED: 07-MAY-2000
WINDOWS:95; winnt:4.0,7.0
WINDOWS winnt
PUBLIC | kbenv ntdomain

\* Security : PUBLIC
================================================== ====================
-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Windows 98
- Microsoft Windows 95
- Microsoft Windows NT Server version 4.0
- Microsoft SQL Server version 7.0
-------------------------------------------------------------------------------

IMPORTANT: This article contains information about editing the registry.
Before you edit the registry, make sure you understand how to restore it if
a problem occurs. For information about how to do this, view the "Restoring
the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help
topic in Regedt32.exe.

SYMPTOMS
========

Windows 95 clients using Microsoft distributed file system (Dfs) or Windows 98
clients may stop responding (hang) in any of the following situations:

- Windows 95 Dfs clients or Windows 98 clients hang while logging on to a
Windows NT 4.0 domain controller that has a Dfs root share and SQL 7.0
installed.

- After successfully logging on to a domain, Windows 95 Dfs clients and Windows
98 clients hang when trying to connect to or browse a Windows NT 4.0 domain
controller (or member server) that has a Dfs root share and SQL 7.0
installed.

- Windows 95 Dfs clients or Windows 98 clients hang while logging on to a
Windows NT 4.0 domain controller, if the user has a logon script that maps a
drive to a Windows NT 4.0 domain controller (or member server) that has a Dfs
root share and SQL 7.0 installed.

When a user is trying to log on, Windows 98-based computers may display Creating
User Profiles and Loading System Policies dialog boxes, and then hang. If you
press CTRL+ALT+DELETE, you see that Mprexe.exe is not responding.

CAUSE
=====

SQL 7.0 installs the following key on the SQL server, which Windows 98 clients
and Windows 95 Dfs clients cannot process correctly:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\LanManServer\Parameters\MaxMpxCt

This key has a REG_DWORD value of x1FF.

RESOLUTION
==========

WARNING: Using Registry Editor incorrectly can cause serious problems that may
require you to reinstall your operating system. Microsoft cannot guarantee that
problems resulting from the incorrect use of Registry Editor can be solved. Use
Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys and
Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete
Information in the Registry" and "Edit Registry Data" Help topics in
Regedt32.exe. Note that you should back up the registry before you edit it. If
you are running Windows NT or Windows 2000, you should also update your
Emergency Repair Disk (ERD).

1. Start Registry Editor (Regedt32.exe) on the Windows NT 4.0 server that has
the Dfs roots hare and SQL 7.0 installed.

2. Locate the REG_DWORD x1FF value under the following key in the registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\LanManServer\Parameters\MaxMpxCt

3. On the Edit menu, click DWORD, type "1FE" (without the quotation marks),
click Hex, and then click OK.

4. Quit Registry Editor.

STATUS
======

Microsoft has confirmed this to be a problem in the Microsoft products listed at
the beginning of this article.

MORE INFORMATION
================

The problem does not affect Windows NT Workstation or Windows 95 clients that
are not Dfs-aware.

If you click Cancel at the domain logon prompt, you can log on locally.

Other possible solutions include:

- Move the Dfs root share to a member server or domain controller that does not
have SQL 7.0 installed.

- Install the NWLINK protocol on all servers and clients.

- If you stop the Netlogon service on the domain controller that is running Dfs
and SQL 7.0, you should be able to log on to the domain (provided that there
are other domain controllers that can be reached by the client) but unable to
browse the domain controller running Dfs and SQL 7.0.

- Apply SQL Server 7.0 Service Pack 1 (SP1).

This problem has also been observed in environments without SQL or Dfs; the
problem was resolved using the solution listed above. Mprexe.exe may not be
responding for many underlying reasons. This article addresses one possible
solution.


....good luck!
-drew

------------------
I just don't understand stop signs...aren't vehicles made to, well...GO???

[unikey]

We found it to be a corrupt PWL file just delete *.pwl and it should go away

Simon

[tregee]

Originally posted by Xavier:
So sites say to delete the pwl files but that is not working in this case.

HELP!!!

Hey Unlikey He tried that

[Xavier]

Here's an update:
-I am logging onto NT domains, NOT novell
-I can logon to one domain fine, but when I try to login on to their it hangs on mprexe.exe and gives and error.
-this is happening on 2 differnt ip subnets.
- there is no sql or other database stuff loaded on these pc's

Thanks for the replys so far, but I have looked up all the microsoft stuff to no avail.

[unikey]

Originally posted by tregee:
Hey Unlikey He tried that

whoops so he did sorry

Simon

[kornesque]

hmmm....FFR. not implying anything, just felt like making a funny sound here.

------------------
I just don't understand stop signs...aren't vehicles made to, well...GO???

[kornesque]

if making that "FFR" sound doesn't sound appealing to you, try running sfc and setup. it may be one corrupt file. keep us posted.
-drew

------------------
I just don't understand stop signs...aren't vehicles made to, well...GO???

[Gabriel]

A LONG SHOT...
If there is a Mcaffee Anti-Virus on that machine it can be the Update who cause the problem.
I had it once.

[jmlozan]

had this problem myself with a certain sound card, when trying to log onto a novell server. Try to pull out the soud card and see if it goes. If that doesn't work change to a different video card.

[gl993]

Try getting rid of user profiles on the local machine, they cause nothing but trouble if clients use multiple computers.

control panel

passwords

user profiles

[CondoPC]

had that b4
went into msconfig and removed ALL startups (reg, win.ini, .bat, .sys)
rebooted and system was fine
just went back and turned things on til i found the culprit. Don't reember what the things i found were, but it has worked many times for me.

[Xavier]

- SPC did not work
- User profiles are not enabled.

On one pc deleting the pwl file will allow you to login, but you have to delete it every time.

This does not work on another one (win95) it will not let you log into the local domain no matter what but WILL let you log on to a different domain.

[Lia]

We were having this happen on loads of Win95 machines with our company. We log into an NT domain. No pwl files. All profiles saved on the server. If you didn't save your profile to the local pc, you didn't get the error (you also had to set up your email profile every time you logged in - not feasible). If you said yes to save your profile, you got the error mprexe not responding.

Sometimes if you remove the NIC and then reinstall it works. Sometimes removing the user profile completely (from the local pc and from the server) and then rebuilt from scratch, it worked for a while. But eventually with some machines, would get the error again sooner or later. This was a real problem. When it took someone 12 reboots before they could get on the network, they got kind of upset!

No real fix yet though. The SQL fix doesn't apply in our case.