Source:Troubleshooting Installation and Configuration: Difference between revisions

From SEPsesam
(Added Windows client update issue (#28304).)
(Marked this version for translation)
Line 81: Line 81:
*Check if SEP sesam Server services are running. If not, start the SEP sesam services manually and then use the same update for the repair installation. For details, see [[Special:MyLanguage/How_to_Start_and_Stop_SEP_sesam|How to Start and Stop SEP sesam]].
*Check if SEP sesam Server services are running. If not, start the SEP sesam services manually and then use the same update for the repair installation. For details, see [[Special:MyLanguage/How_to_Start_and_Stop_SEP_sesam|How to Start and Stop SEP sesam]].


<!--T:130-->
{{anchor|MSI_update}}'''SEP sesam Windows Client update from v. 4.4.3.64 fails with error'''
{{anchor|MSI_update}}'''SEP sesam Windows Client update from v. 4.4.3.64 fails with error'''


<!--T:131-->
'''Problem'''</translate>
'''Problem'''</translate>
<ul><li><translate>The SEP sesam Windows Client update from SEP sesam v. [[SEP_sesam_Release_Versions|4.4.3.64 ''Grolar'']] to a newer version might fail with the following MSI installer error:</translate></li>  
<ul><li><translate><!--T:132--> The SEP sesam Windows Client update from SEP sesam v. [[SEP_sesam_Release_Versions|4.4.3.64 ''Grolar'']] to a newer version might fail with the following MSI installer error:</translate></li>  
  Unable to create a temp copy of transform"
  Unable to create a temp copy of transform"
</ul>
</ul>


'''<translate>Cause</translate>'''
'''<translate><!--T:133--> Cause</translate>'''
*<translate>This issue occurs if the transform path specified in the registry points to the wrong folder.</translate>
*<translate><!--T:134--> This issue occurs if the transform path specified in the registry points to the wrong folder.</translate>


&rArr; <translate>'''Solution'''
&rArr; <translate><!--T:135-->
'''Solution'''


<!--T:136-->
<ul><li>To resolve this issue, you must rename the transform key.</li>
<ul><li>To resolve this issue, you must rename the transform key.</li>
{{Note|This procedure modifies the Windows registry; modifying Windows Registry incorrectly might crash your operating system and cause data loss. Ensure that you have a valid SEP sesam and operating system backup before proceeding!}}
{{Note|This procedure modifies the Windows registry; modifying Windows Registry incorrectly might crash your operating system and cause data loss. Ensure that you have a valid SEP sesam and operating system backup before proceeding!}}

Revision as of 14:43, 14 April 2021

Other languages:

Template:Copyright SEP AG en

Docs latest icon.png Welcome to the latest SEP sesam documentation version 4.4.3/4.4.3 Beefalo V2. For previous documentation version(s), check documentation archive.


Installation and configuration problems

Installation problems

SEP sesam Server installation on Windows failed

Problem

  • The SEP sesam Server installation on Windows failed with an error.

Cause

  • For SEP sesam Server installation a domain administrator account has been used.

Solution

  • Before starting the SEP sesam installation on Windows, make sure that you are logged in as a local administrator (not domain administrator).

Update problems

SEP sesam Server update failed

Problem

  • The SEP sesam Server update failed with an error.

Cause

  • SEP sesam services on the system that is being updated could not be started, causing SEP sesam Server update to fail.

Solution

  • Check if SEP sesam Server services are running. If not, start the SEP sesam services manually and then use the same update for the repair installation. For details, see How to Start and Stop SEP sesam.

SEP sesam Windows Client update from v. 4.4.3.64 fails with error

Problem

  • The SEP sesam Windows Client update from SEP sesam v. 4.4.3.64 Grolar to a newer version might fail with the following MSI installer error:
  • Unable to create a temp copy of transform"

Cause

  • This issue occurs if the transform path specified in the registry points to the wrong folder.

Solution

  • To resolve this issue, you must rename the transform key.
  • Information sign.png Note
    This procedure modifies the Windows registry; modifying Windows Registry incorrectly might crash your operating system and cause data loss. Ensure that you have a valid SEP sesam and operating system backup before proceeding!

    Proceed as follows:

    1. Open Registry Editor: use Start and type regedit.
    2. Go to the registry key
    3. HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\7737007073521AA4885C03C7AEE4954D and rename Transforms to Transforms_.

Automatic remote update from GUI fails with errors

Problem

  • On Windows, automatic remote update failed with the following error:
  • Windows error: (0x800703FA) Illegal operation attempted on a registry key that has been marked for deletion
  • The sm_msi.log log file on the client system shows the following:
  • InstallShield 11:08:04: Initializing Engine InstallShield 11:08:04: Marshalling the , error = 0x800703fa InstallShield 11:08:04: Open Script operation failed, error is 0x800703fa InstallShield 11:08:04: Failed to invoke __ISWIUnInit, error is 0x80070057 InstallShield 11:08:04: Failed to shutdown script engine for script C:\Users\sepshare\AppData\Local\Temp\{A2C12F7B-F8D3-4D99-8E34-61600D67DBCC}\setup.inx, error is 0x80070057 InstallShield 11:08:04: Initialize() Failure, Failed to Initialize script support, Error = 0x800703fa

Cause

  • Typically, this error occurs when the sesam service is running under a specific user account instead of the default system account. An administrator uses this service user account to log on to the server (SEP sesam RDS or client) for the session and then logs off. This forcibly unloads the registry keys in the account profile and makes the keys unavailable for future use.

Solution

You have to enable the Windows User Profile Service which does not unload the registry keys after logging off:

  1. Open the Group Policy editor (Gpedit.msc) on the respective server.
  2. Open the UserProfiles folder: go to Computer Configuration -> Administrative Templates -> System -> UserProfiles.
  3. Look for the Do not forcefully unload the user registry at user logoff setting and select the option Enabled. For details, see Microsoft support article "800703fa Illegal operation attempted on a registry key" error .

Uninstallation problems

For uninstallation problems, see Uninstalling SEP sesam.

System limits adjustment problem

Problem

  • SEP sesam limits on the system have to be adjusted, however, the settings should not be overwritten by update.

Solution

The best way to adjust SEP sesam limits on the system is to create the Systemd override file. By using this file the settings are not overwritten during the update.

To adjust limits on the system, proceed as follows:

Example

>
> root@cefix:~# systemctl show sepsesam.service | grep ^LimitCORE=
> LimitCORE=2147483648

  1. Create the override file and adjust the value:
  2. > mkdir -p /etc/systemd/system/sepsesam.service.d/ > echo "[Service]" > > /etc/systemd/system/sepsesam.service.d/override.conf echo > "LimitCORE=infinity" >> > /etc/systemd/system/sepsesam.service.d/override.conf
  3. Reload the system by using the command:
  4. > root@cefix:~# systemctl daemon-reload
  5. Then specify:
  6. > root@cefix:~# systemctl show sepsesam.service | grep ^LimitCORE= > LimitCORE=infinity

Windows installer (MSI) installation error

Problem 1

  • You receive the following warning: "An error occurred during the installation of assembly component... HRESULT: 0x80070bc9."

Possible causes

  • MSI locks the database to install new software after Windows updates were installed.

Solution

  • Reboot the host to unlock the database.
Information sign.png Note
The msi log file contains the line 'Transforming table Error' very often. This does not mean that an error occurred. It rather means that the table which is called Error has been transformed. Hence it is only an information not an error message.

Problem 2

  • Installation failed after uninstallation - you receive the following Popup:
    • English: "The SEP sesam server was installed using a server installation package. Please retry the update using a server installation package instead of the server package you are using. Update will be aborted."
    • German: "Der SEP sesam server wurde mit einem server Installationspaket installiert. Bitte wiederholen Sie den Update mit einem server Installationspaket statt des verwendeten server Pakets. Das Update wurde abgebrochen."

Possible causes

  • The uninstallation did not remove HKLM\SOFTWARE\SEP Elektronik GmbH registry key.

Solution

  • Open the MS Windows registry (e.g. call regedit) and remove HKLM\SOFTWARE\SEP Elektronik GmbH.

Red Hat Enterprise Linux

Problem

  • The following warning occurs on a Windows operating system: "ERROR: SMS0004: The specified device does not exist."

Solution

  • Reinstall the CBMR x.x SEP Sesam Version software package.

Powershell script not executed on a target machine

Problem

  • Why is the Powershell script not executed on a target machine?

Possible causes

  • By default, Microsoft installs Windows Powershell with the permission set to Restricted. This setting only allows the execution of commands in Powershell but no scripts.

Solution

  • This can be changed with following command in Powershell:
Set-ExecutionPolicy RemoteSigned

For more information, see About Execution Policies.

IBM DB2

Problem

  • There are problems with SEP sesam operations.

Solution

  • Check contents of db user's $HOME/sqllib/db2dump/db2diag.log log file.
  • Check the messages on SEP sesam Server.
  • Find more information in the sdb2 log. Log filename is set by XBSA LOGFILE=<Full pathname of sdb2.log> and log level by XBSA TRACE=1.
Information sign.png Note
All sesam XBSA messages have the prefix XBSA. You can set XBSA TRACE to 2 to show more details, but then the log files can become quite large.

MacOS

Problem

  • There are problems with SEP sesam operations.

Solution

The Mac installer has its own log messaging system. To view the log files, proceed as follows:

  • Execute the installation/update of the client or GUI package step-by-step until you get to the last installer step Summary.
  • Go to the Installer Menu and click Window -> Installer Log.
  • Select among the following options: Show Errors Only, Show Errors and Progress or Show All Logs.

AIX

Problem

  • After SEP sesam installation, an error occurs: STATUS=ERROR MSG=Some daemons offline

Solution

By default the sesam sshd daemon is not included in the AIX package. Therefore the command:

/opt/sesam/bin/sesam/sm_main status

will report the sshd as offline:

2016-08-27 16:20:05: sshd               : offline
  • Currently, this error can be ignored as only the CTRL access mode is supported for the AIX systems.
  • To disable the sshd daemon, edit the file:
  • /opt/sesam/var/ini/sm.ini and change the option: sshd=on to sshd=off
  • If any other services are not starting up, contact SEP sesam support.

Debian repository

Problem 1

  • After running apt-get update, the following GPG error is shown:
W: GPG error: https://www.sep.de/downloadportal/ jessie InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 68111EBBD273917B

Cause

  • The SEP GPG key is missing in the system keyring.

Solution


Problem 2

  • During package installation the following warning (verification error) occurs:
 WARNING: The following packages cannot be authenticated!
 sesam-<package>
Install these packages without verification? [y/N]

Cause

  • The SEP GPG key is missing in the system keyring.

Solution

Problem 3

  • While running apt-get update, the following message appears:
  • N: Das Laden der konfigurierten Datei »main/binary-i386/Packages« wird übersprungen, da das Depot [...] die Architektur »i386« nicht unterstützt.

Solution

Problem 4

  • While running the command apt-key add, the following message appears:
  • E: gnupg, gnupg2 and gnupg1 do not seem to be installed, but one of them is required for this operation

Solution

  • Install the package gnupg to fulfill the dependency via package manger:
  • apt-get install gnupg

See also

Installation