Windows Forum

Ask something
Discussion Locked

OleMainThreadWndName Error

0 helpful
8 replies

by lyle.fast

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

OleMainThreadWndName on Shutdown or logout prevents the server from restarting or shuting down. We have narrowed down the apps that could be causing this error and Crystal Reports Web Component and Page Server. After uninstalling Crystal reports and copying c:\winnt\system32\urlmon.dll and wininet.dll, the system would properly log out and reboot. We reinstalled Crystal Reports 8 and now the error is back. Production application Web Server has Option Pack, SP6a, IIS 4.0, Seagate Crystal Reports 8.0.x.371 (Developer), Sybase SQL 11. A development web server exist with similar software and applications that does not exhibit this problem. I used windiff to compare the servers system32\*.dll, however, many are different.

Has anyone ran into a similar problem?

Short of rebuilding, what can I do?

8 replies

by z

Seen a similar problem on some of our machines that have Sql Anywhere running. The way we got around it was with a kill command that does the end task for you if the app doesn't terminate in a time period specified. you can get the kill.exe from the NT resource kit cd. I know it's not a real solution, but it worked for us since we didn't have a choice in getting rid of sql anywhere.

by lyle.fast

Check your services Startup parameters.
It turned out to be Active PDF Spooler needed to logon as Administrator, not system. Also, the MSDTC Service was started Manual on problem server and both servers had "the Allow Service to Interact with Desktop" box checked.

by muidaq

Lyle is not the only one with this problem. We have it on a few IIS servers, but none of them have Crystal on them.

by lyle.fast

I have found another DLL that is different between the two servers, however, I do not know how to copy it from one server to another. I cannot rename this MSIDLE.DLL (File in use) (5.00.3105.105 maybe bad), so that I can copy the older version (5.00.2919.6304 good).

by muidaq

Check all the services to see which are allowed to interact with the desktop. We had Computer Associates TNG services that had the "Allow Service to Interact with Desktop" setting enabled and when we disabled it and restarted the services, we logout just fine. There are some other possible solutions at http://www.windows-help.net/bbs/Forum4/HTML/000810.html .

by lyle.fast

It turned out to be Active PDF Spooler needed to logon as Administrator, not system. Also, the MSDTC Service was started Manual on problem server and both servers had "the Allow Service to Interact with Desktop" box checked. You lead me to the solution, Thanks!

This discussion is closed to new replies.