Microsoft

Task Manager trip-up: Don't let pcAnywhere hamper XP utilities

Sometimes even the most astute techie must ask for help resolving hidden software conflicts. See how our Technical Q&A solved one member's Task Manager/pcAnywhere bug.


When IT support experience and know-how come up short, the best alternative resource available for solving end user problems often comes in two forms: discussion boards and company Web sites. In regard to discussion boards, thousands of IT pros turn to TechRepublic and its members daily for the latest fixes, quick tips, and informative advice. As for the latter, even more people look to manufacturer Web sites, such as Microsoft's Knowledge Base, for help with specific products.

Armed with an Internet connection, resourceful techies can use these two sources to overcome the most daunting obstacles. One example of this comes from our Technical Q&A.

A tangled Task Manager
TechRepublic member Bev_Tech_Rob can attest to this. Recently, this member posted a problem concerning Windows XP's Task Manager. He wrote, "When I attempt to access Task List in XP Pro, I get the error 'The application failed to initialize properly (0xC0150004). Click OK to terminate the application.'"

Otherwise, his system, a Compaq Diskpro EN 866 Pentium III with 128 MB of RAM and a 15-GB hard drive with 512-MB static swap file, works fine. He dual boots between Windows 98 and XP. Bev_Tech_Rob wonders if running Setup will allow him to repair the existing install.

Quick with an answer
In a speedy response, member DKlippert suggests that pcAnywhere might be causing this problem. He points Bev_Tech_Rob to Symantec's service and support Web site and the following solution.

Symantec describes the problem to a tee. The error occurs when pcAnywhere 10.5 and Novell Client 4.82E XP are installed on a Windows XP system. Any attempt to run Task Manager, either by pressing [Ctrl][Alt][Del] or typing TASKMGR.EXE at the Start | Run command line, will produce the error message detailed by Bev_Tech_Rob.

Another REGEDIT solution
This error, produced by a chaining problem involving Awgina.dll and the Novell Client, is resolved with a simple edit of the system Registry. Symantec notes that this applies only to Windows XP. One should not delete the GinaDLL entry in any other version of Windows.

To resolve the conflict, perform the following:
  1. Uninstall both the Novell Client and pcAnywhere. Reboot after each uninstall. (Refer to Symantec's document "How to uninstall pcAnywhere from Windows NT/2000/XP" for further information.)
  2. Install pcAnywhere 10.5 and reboot.
  3. Click Start | Run.
  4. Type REGEDIT and click OK.
  5. Find the following Registry key:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
  6. In the editor's right pane, right-click on the GinaDLL entry and delete it.
  7. Close the Registry editor and reboot.
  8. Reinstall the Novell Client and reboot.

According to Symantec, the error should no longer occur.

Beware hidden conflicts
Bev_Tech_Rob found an answer to his problem. As thanks for the advice, he happily rewarded DKlippert with a bevy of TechPoints. "That tip worked like a champ! I got kinda spooked when the tech [DKlippert] mentioned I had pcAnywhere, because I didn't mention that point! I actually have version 9.2, but the tip worked great!"

Editor's Picks

Free Newsletters, In your Inbox