Microsoft KB Archive/899608

= SnaBase does not copy the registry values in the HKEY_LOCAL_MACHINE registry subtree when you run an automated sponsor script on a Host Integration Server 2000 End-User Client computer =

Article ID: 899608

Article Last Modified on 6/3/2005

-

APPLIES TO


 * Microsoft Host Integration Server 2000 Standard Edition

-





SYMPTOMS
When you run an automated sponsor script to change the sponsor server list on a Microsoft Host Integration Server 2000 End-User Client computer, SnaBase does not copy the registry values in the  registry subtree to the corresponding keys in the   registry subtree. Therefore, when a new user on the client computer tries to connect to Host Integration Server 2000, the connection is unsuccessful.

The Sponsors registry entry (REG_SZ) is located in the following subkeys:

Note This problem occurs after you install Microsoft Windows XP Service Pack 2 (SP2) on a computer that is running Host Integration Server 2000 End-User Client.



RESOLUTION
To resolve this problem, run the SNA Resource Location Wizard in Administrative mode. To do this, type the following command at a command prompt:

HICLICFG /a

After you run the SNA Resource Location Wizard, the registry values are correctly copied from the  registry subtree when a new user logs on to the computer.



MORE INFORMATION
When you run the SNA Resource Location Wizard in Administrative mode, the following registry entry is updated based on a timestamp:

The FinalXID value is a 64-bit value. If this registry entry is not correctly updated, the registry values from the  registry subtree will not be copied to the corresponding keys in the   registry subtree. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

307750 End-User Client does not connect after configuration change

The following code is an example of an automated sponsor script to update the Sponsors registry entry for the current user. const HKEY_CURRENT_USER = &H80000001

sComputer      = &quot;COMPUTER01&quot; sMethod        = &quot;SetStringValue&quot; hTree          = HKEY_Current_User sKey           = &quot;SOFTWARE\Microsoft\SNABase\Parameters&quot; sValueName     = &quot;Sponsors&quot; sValue         = &quot;SNA-01 SNA-02 SNA-03 SNA-04&quot;

Set oRegistry  = GetObject(&quot;winmgmts:{impersonationLevel=impersonate}//&quot; & sComputer & &quot;/root/default:StdRegProv&quot;)

Set oMethod    = oRegistry.Methods_(sMethod) Set oInParam = oMethod.inParameters.SpawnInstance_

oInParam.hDefKey = hTree oInParam.sSubKeyName = sKey oInParam.sValueName = sValueName oInParam.sValue = sValue

Set oOutParam = oRegistry.ExecMethod_(sMethod, oInParam)

Wscript.echo &quot;This script ran successfully!!&quot; The following code is an example of an automated sponsor script to update the Sponsors registry entry for the local computer. const HKEY_LOCAL_MACHINE = &H80000002

sComputer      = &quot;COMPUTER01&quot; sMethod        = &quot;SetStringValue&quot; hTree          = HKEY_LOCAL_MACHINE sKey           = &quot;SOFTWARE\Microsoft\SNABase\Parameters&quot; sValueName     = &quot;Sponsors&quot; sValue         = &quot;SNA-01 SNA-02 SNA-03 SNA-04&quot;

Set oRegistry  = GetObject(&quot;winmgmts:{impersonationLevel=impersonate}//&quot; & sComputer & &quot;/root/default:StdRegProv&quot;)

Set oMethod    = oRegistry.Methods_(sMethod) Set oInParam = oMethod.inParameters.SpawnInstance_

oInParam.hDefKey = hTree oInParam.sSubKeyName = sKey oInParam.sValueName = sValueName oInParam.sValue = sValue

Set oOutParam = oRegistry.ExecMethod_(sMethod, oInParam)

Wscript.echo &quot;This script ran successfully!!&quot;

