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 (899608)

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 HKEY_LOCAL_MACHINE registry subtree to the corresponding keys in the HKEY_CURRENT_USER 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:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SNABase\Parameters

HKEY_CURRENT_USER\SOFTWARE\Microsoft\SNABase\Parameters

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.

MORE INFORMATION

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

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SNA Server\CurrentVersion\FinalXID

The FinalXID value is a 64-bit value. If this registry entry is not correctly updated, the registry values from the HKEY_LOCAL_MACHINE registry subtree will not be copied to the corresponding keys in the HKEY_CURRENT_USER 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       = "COMPUTER01" 
sMethod         = "SetStringValue" 
hTree           = HKEY_Current_User 
sKey            = "SOFTWARE\Microsoft\SNABase\Parameters" 
sValueName      = "Sponsors" 
sValue          = "SNA-01 SNA-02 SNA-03 SNA-04" 

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

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 "This script ran successfully!!"

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       = "COMPUTER01" 
sMethod         = "SetStringValue" 
hTree           = HKEY_LOCAL_MACHINE 
sKey            = "SOFTWARE\Microsoft\SNABase\Parameters" 
sValueName      = "Sponsors" 
sValue          = "SNA-01 SNA-02 SNA-03 SNA-04" 

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

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 "This script ran successfully!!"

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 (899608)

SYMPTOMS

RESOLUTION

MORE INFORMATION

REFERENCES