Installation and Configuration Troubleshooting

From SEPsesam
Revision as of 21:33, 22 July 2019 by Lhu (talk | contribs) (internal formatting)
Jump to: navigation, search
Other languages:
Deutsch • ‎English

Copyright © SEP AG 1999-2019. All rights reserved.

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.

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


Other

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://download.sep.de/ 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 shows up:

N: Das Laden der konfigurierten Datei »main/binary-i386/Packages« wird übersprungen, da das Depot [...] die Architektur »i386« nicht unterstützt.

Solution

Insert [arch=amd64] between the word deb and the URL of the repository like in the following example:

deb [arch=amd64] https://download.sep.de/linux/repositories/debian/ stretch main

See also

Installation