SBL-DAT-00144: Could not find '%1' named '%2'. This object is inactive or nonexistent.
(Doc ID 478582.1)
Last updated on NOVEMBER 22, 2019
Applies to:Siebel Tools - Version 7.7.1  and later
Information in this document applies to any platform.
This document is intended to provide cause and corrective action information about Siebel Error Message SBL-DAT-00144: Could not find '%1' named '%2'. This object is inactive or nonexistent.
The error indicates that Siebel is unable to find the named object in the repository.
This error can be seen throughout the application. In general, the error occurs when the Siebel client is trying to use a tools object, which it cannot find. Therefore, there can be many different reasons for this error message. This error can also occur with the standard configuration. That usually indicates a product defect or a set up issue. If the error only happens with the custom srf, that points to a configuration issue. For example, the SBL-DAT-00144 can be displayed when a Find object has a drilldown view that the current user does not have access to that view. The same error message can also be displayed in a Siebel log file and is considered benign if the log indicates it is a warning message.
ObjMgrSRFLog Warning 2 0 2007-03-13 09:15:12 (cdf.cpp (2607)) SBL-DAT-00144: Could not find 'View' named 'Account - SAP Orders View'.
Usually this error will reproduce consistently. It is important to determine if the error occurs with the standard Siebel Repository File (SRF) or with the custom SRF. This is easy to test with the dedicated web client pointing to the server database. The standard srf can be copied in from the Siebel tools installation. Turn on Client Side Logging to level 5 generate a detailed log file. Review the log file and note what parts of the configuration are being used right before the error message. How Should Client Side Logging Be Set? (Doc ID 475587.1) If the cause of the error is not evident from the log file, attach the siebel.log file with the new service request.
This document is informational and intended for any user.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Other documents that are related to this error|