Microsoft KB Archive/252638

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 13:52, 21 July 2020 by X010 (talk | contribs) (Text replacement - """ to """)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base


Problem Using Internet Service Manager from a Terminal Server Client Session

Article ID: 252638

Article Last Modified on 3/1/2007



APPLIES TO

  • Microsoft Windows NT Server 4.0, Terminal Server Edition Service Pack 4
  • Microsoft Windows NT Server 4.0, Terminal Server Edition Service Pack 5
  • Microsoft Internet Information Server 4.0



This article was previously published under Q252638

SYMPTOMS

When you use Internet Service Manager to manage Internet Information Server (IIS) or Microsoft Transaction Server (MTS), you may experience any of the following symptoms:

  • Internet Service Manager reports the error message "Error connecting to Servername."
  • The distributed version of the Component Object Model (DCOM) logs system error event 10010 with the following text:

    The server {A9E69610-B80D-11D0-B9B9-00A0C922E750} did not register with DCOM within the required timeout.

  • You receive error 8008005.


CAUSE

Some of the required COM classes are not registered with the Windows NT Terminal service.

RESOLUTION

NOTE: You must be running Windows NT 4.0 Terminal Server Service Pack 5 or later for this resolution to work.

  1. Create a new text file that contains the following text:

    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\CLSID\{A9E69610-B80D-11d0-B9B9-00A0C922E750}
        fSystemGlobalClass = REG_DWORD 0x00000001
    
    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\{A9E69610-B80D-11d0-B9B9-00A0C922E750}
        fSystemGlobalClass = REG_DWORD 0x00000001
    
    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\{61738644-F196-11D0-9953-00C04FD919C1}
        fSystemGlobalClass = REG_DWORD 0x00000001
    
    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\CLSID\{61738644-F196-11D0-9953-00C04FD919C1}
        fSystemGlobalClass = REG_DWORD 0x00000001
    
    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\CLSID\{182C40F0-32E4-11D0-818B-00A0C9231C29}
        fSystemGlobalClass = REG_DWORD 0x00000001
    
    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\{182C40F0-32E4-11D0-818B-00A0C9231C29}
        fSystemGlobalClass = REG_DWORD 0x00000001
    
    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\{CBD759F3-76AA-11CF-BE3A-00AA00A2FA25}
        fSystemGlobalClass = REG_DWORD 0x00000001
    
    HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Compatibility\CLSID\{CBD759F3-76AA-11CF-BE3A-00AA00A2FA25}
        fSystemGlobalClass = REG_DWORD 0x00000001
                        
  2. Save the file as Reg.ini, and then close the file.
  3. Run the regini reg.ini command to make the necessary registry changes.
  4. Restart the computer.


Keywords: kbenv kberrmsg kbprb KB252638