After the initial login, when clicking on the Mail icon to get to the inbox the following 2 messages appear: Unable to invoke program and Unable to locate program:nwrdaemn.DLLAfter going through and clicking OK on both, I am able to get into the inbox.
Subject: Unable to locate invoke program/Unable to locate program:nwrdaemn.DLL
How bizarre - I’ve literally just had a user with the exact same problem - specifically when trying to replicate. Tried all sorts of uninstalls/reinstalls to no avail but eventually found that something on the machine was hijacking ntaskldr.exe. Couldn’t get into windows task manager to find out what it was - possibly caused by the same thing - but used a product called Process Explorer (post back if you want the url) to kill the process which had taken control of ntaskldr. This allowed the user to work normally. Haven’t yet found out what the offending process is (seems to be an executable called mmeedvnx.exe on this particular machine - anyone know what this is?) but will post back when I do.
Subject: RE: Unable to locate invoke program/Unable to locate program:nwrdaemn.DLL
Here you go:
They do quite a few useful utilities on there so it’s a page worth bookmarking. And I promise that I don’t work for them - this is a genuine testemonial!
I had to do a search on ntaskldr to find out which process was hijacking it - it wasn’t immediately apparent from the first screen. Well, having said that, I was talking a user through doing this over the phone so I couldn’t really say whether it was apparent or not - just thought I’d better mention it!
Subject: RE: Unable to locate invoke program/Unable to locate program:nwrdaemn.DLL
Thanks. I managed to get the Process Explorer program. I ran it and managed to pick up the other application that was using the ntaskldr.exe. I killed the process and was able to get into the mail Inbox without the errors appearing.
Just managed to sort this issue out. The executable causing the problem - mmeedvnx.exe - was located on the user’s hard drive in c:\windows\system32. Got rid of it and restarted the machine and this seemed to sort everything out, including letting the user get into Windows Task Manager and everything.
Haven’t yet determined whether this was caused by a virus, but at least the user is working again now!