on 11-18-2015 6:49 PM
Hello
We just migrated SAPGui installation server to 7.40 Compilation 2 with GUI 7.4 SP5
In package installation settings we are using option to use central configuration file:
NwEngine.Shell.SetRegValue "HKEY_LOCAL_MACHINE\SOFTWARE\SAP\SAPLogon\Options\ConfigFileOnServer", "REG_EXPAND_SZ", "\\server\SapLogonTree.xml"
NwEngine.Shell.SetRegValue "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SAP\SAPLogon\Options\ConfigFileOnServer", "REG_EXPAND_SZ", "\\server\SapLogonTree.xml"
but those registry entries are existing only for day or two and next morning disappearing from users workstations.
I've already checked following notes:
2075150 - SAP Logon (Pad) 740: New format of configuration files as of SAP GUI for Windows 7.40
2220930 - How to enable SAP UI Landscape format for SAP GUI for Windows 7.40
but nothing matched ....
We are also using:
NwEngine.Shell.SetRegValue "HKEY_LOCAL_MACHINE\SOFTWARE\SAP\SAPLogon\Options\SapguiNTCmdOpts","REG_SZ","/SUPPORTBIT_OFF=MAX_WSIZE"
NwEngine.Shell.SetRegValue "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SAP\SAPLogon\Options\SapguiNTCmdOpts","REG_SZ","/SUPPORTBIT_OFF=MAX_WSIZE"
and those registry entries are always in place ....
Any hint how to trace this issue or resolve it ?
Regards
Marcin
P.S. Anyone from OSS who really do want to investigate ?
One thing to try...
When using NwEngine.Shell.SetRegValue, don't specify Wow6432Node. The installer will automatically detect if the system is 64 or 32 bit and update the correct registry values.
Thanks,
Roy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well , found some clues. SAP has added configuration parameters to package definition level on SAPGUI Installation Server and ConfigFileOnServer as well as LandscapeFileOnServer are by default set to NONE.
Logs from installation proces:
Attempting to create registry value ConfigFileOnServer: RegValue(REG_EXPAND_SZ, "\\server\SapLogonTree.xml")
10:17:51 NwSapsAtlC 1 Executing script action...
10:17:51 NwSapsAtlC 1 Variable-Script-Action: User input for SapGui.ConfigFileOnServer is: \\server\SapLogonTree.xml
10:17:51 NwSapsAtlC 1 Variable-Script-Action: SapGui.ConfigFileOnServer is not NONE. The key should not be deleted. Writing user input to the registry...
10:17:51 NwSapsEngn 1 Shell : registry value 'HKLM\SOFTWARE\SAP\SAPLogon\Options\ConfigFileOnServer' (32 bit registry) has been successfully set
10:17:51 NwSapsAtlC 1 Variable-Script-Action: Registry value HKLM\SOFTWARE\SAP\SAPLogon\Options\ConfigFileOnServer set successfully to \\server\SapLogonTree.xml.
Logs from update process hour later:
11:36:49 NwSapsAtlC 1 Executing script action...
11:36:49 NwSapsAtlC 1 Variable-Script-Action: User input for SapGui.ConfigFileOnServer is: NONE
11:36:49 NwSapsAtlC 1 Variable-Script-Action: Removing registry value HKLM\SOFTWARE\SAP\SAPLogon\Options\ConfigFileOnServer if it exists because SapGui.ConfigFileOnServer is set to NONE or empty.
11:36:49 NwSapsAtlC 1 Variable-Script-Action: Registry value HKLM\SOFTWARE\SAP\SAPLogon\Options\ConfigFileOnServer exists, deleting...
11:36:49 NwSapsEngn 2 Shell : registry value 'HKLM\SOFTWARE\SAP\SAPLogon\Options\ConfigFileOnServer' (32 bit registry) deleted
11:36:49 NwSapsAtlC 1 Variable-Script-Action: Successfully deleted registry value HKLM\SOFTWARE\SAP\SAPLogon\Options\ConfigFileOnServer.
What is going on here ?
Can someone find in below explanation that leaving default package level registry values untouched will delete your values created by script or manually ?
Page 38:
4. Optional: You can set registry values on package level, for example, for the following
registry keys:
- Registry keys of the Accessibility page
- Path to the SAP GUI branding image
- Path to the Central Configuration File (new and old format)
- Theme Key etc.
You find the whole list on the package configuration tab.
To change a registry key setting for the package, choose
Modify Parameters
. A window
opens where you can choose the variable name and enter the corresponding value
below. You find a description of the registry key values in the SAP GUI Administration
Guide.
Limitation: Later, this setting cannot be changed with the same tool again.
Changes have then to be done via scripting.
Hi Marcin,
Well, if it was supposed to be fixed in sp6, it seems to have been broken again in sp9, as I am observing this same behavior when an existing 7.30 GUI is "auto-upgraded" via AWUS against a 7.40 Installation Server. The AWUS auto-updates the components, not the package, so the package scripts don't run, and somewhere along the way it deletes the existing registry entry for ConfigFileOnServer, so afterwards there's no configuration in the SAP Logon.
Did you find a resolution for this? Or a way to edit the Installation Variables in NwSapSetupAdmin?
Cheers,
Matt
User | Count |
---|---|
89 | |
10 | |
9 | |
9 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.