OleMainThreadWndName error

Re-apply the latest service pack that you have installed on your NT 4 server.

This seems to be a re-occuring question on several technical problem/answer websites... no clear cut responses as to what fixes the problem. Re-applying the serviccepack and the rebooting seems to "end" most of the treads on that issue...

If you have Arcserve Read the problem/answer below :

Title: "OleMainThrdWndName" or "W" pop-up box on Exchange
Date: 08/13/99
Product: ARCserve 6.5 & ARCserveIT 6.6x for Windows NT
Build: 834
Secondary Product: Exchange Agent
Secondary Product Build: 173/259

PROBLEM: When going to any of the Exchange Hosts and logging out or attempting to shut down, the system displays the message "W" in a pop-up box. Then you see "The Windows application cannot respond to the request, it may be busy, waiting for a response from you, or it may have stopped executing......etc etc." Or the window is headed with "OleMainThrdWndName" with the same message. If "end task" is selected for either one of these messages, then the desktop can be logged out, or the system can be shut down. This error DOES NOT happen to any of these hosts if it has been freshly booted. This only occurs when a backup had been run with the Exchange database agent. If agent is running but idle, doesnt appear. If a backup was ran, then stopping the Backup Agent RPC server service in control panel\services, eliminates the problem.

RESOLUTION: Have the customer change the following registry value:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DbaRpcService\
At the DbaRpcService key, you will see a value named "Type". Set this Reg_Dword value to 0x10. (CORRECT ENTRY)
The default value during installation should have been 0x110. (INCORRECT ENTRY)

This entry affects how the DBARpcServer Service interacts with system services. In order for the changes to take affect the server MUST BE RESTARTED. -To add to this entry, I have seen an issue where NETWORK ASSOCIATES GROUPSHIELD EXCHANGE SERVICES are stopped then this problem seems to go away. It is the interaction between our agent and the NETWORK ASSOCIATES SERVICES that seemed to have generated this problem.