Search This Blog

SBL-ADM-08102: Registry key: (%1) not found

Applies to:

Siebel System Software - Version: 7.0.4 [14068] - Release: V7
Microsoft Windows 2000
Area(s):System Administration
Release(s):V7 (Enterprise)
Database(s):DB2, Microsoft, Oracle
App Server OS(s):Windows 2000
Latest release tested against:V7 (Enterprise)
Keywords:siebsnap, siebsnap.log, registry key, Siebel Diagnostic Data Collector

This document was previously published as Siebel Alert 816.

Description

The Siebel Diagnostic Data Collector (Siebsnap), introduced in Siebel 7.5.3 captures Siebel application environment information for diagnostic and troubleshooting purposes. When running Siebsnap on a Microsoft Windows operating system, users may receive registry key errors in the siebsnap.log file even though the Registrykeys.txt file generated by Siebsnap indicates that the registry key data was retrieved successfully

Bug <<12-GZE1N7>> has been logged to address this product defect.

Likelihood of Occurrence

This behavior will occur when running Siebsnap on Microsoft Windows to capture Siebel 7.5.3 environment information.

Possible Symptoms

Incorrect information will appear in the siebsnap.log file. When running Siebsnap on Microsoft Windows, users may receive the following error messages in siebsnap.log file:

Error 1:

  • SBL-ADM-08102: Registry key: (HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI) not found
  • Could not read registry key: (HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI)

Error 2:

  • SBL-ADM-08102: Registry key: (HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Microsoft driver for text archive (*.txt; *.csv))
  • Could not read registry key: (HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Microsoft driver for text archive (*.txt; *.csv))

The Registrykeys.txt file generated by Siebsnap, however, indicates that the registry key data was retrieved successfully:

  • [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI]
  • [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ Microsoft driver for text archive (*.txt; *.csv))

Workaround or Resolution

The above error messages shown in siebsnap.log can be safely ignored.


No comments:

Post a Comment