Search This Blog

SBL-ADM-01105: Log File Reading: End of file reached

Applies to:

Product Release: V7 (Enterprise)
Version: 7.7.1 [18306]
Database: Oracle 9i
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Sun Solaris 8

This document was previously published as Siebel SR 38-1397569971.

Symptoms

SBL-CSO-01031, SBL-ADM-01105

Two error messages are displayed in the ServerMgr_24650.log

=> SBL-CSO-01031: Internal: the SCR object is not set
=> SBL-ADM-01105: Log File Reading: End of file reached

Solution

Message 1

For the benefit of other users ...

The following error messages could be found in the ServerMgr*.log:

SBL-CSO-01031: Internal: the SCR object is not set
SBL-ADM-01105: Log File Reading: End of file reached

The above error messages are not indicative of any loss of functionality or major discrepancy. They only indicate that the contents of the srvrmgr task log cannot be viewed through the UI. So they are benign errors and can be ignored. A Change Request 12-N2L48T has been raised to address this defect.

Keywords: SBL-CSO-01031 and SBL-ADM-01105 and ServerMgr

Applies to:

Product Release: V7 (Professional)
Version: 7.5.3.5 [16183]
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: Sun Solaris 8

This document was previously published as Siebel SR 38-1382393971.

Symptoms

SBL-CSO-01031, SBL-ADM-01105, SBL-ADM-01108

I work for expert service and i am helping the customer. They get this following error message whenever they go to Server -configuration screen.
Hi All

I am at a customer site and everytime sadmin uses server - configuration the following error message appears in the srvrmgr log.

Log file :

GenericLog GenericError 1 0 2004-07-08 12:18:12 (ss2klogapi.cpp (2362) err=901108 sys=0) SBL-ADM-01108: Log File Reading: End of virtual log reached.
GenericLog GenericError 1 0 2004-07-08 12:18:12 (ss2klogapi.cpp (2080) err=901108 sys=0) SBL-ADM-01108: Log File Reading: End of virtual log reached.
GenericLog GenericError 1 0 2004-07-08 12:18:12 (ss2klogapi.cpp (2362) err=901108 sys=0) SBL-ADM-01108: Log File Reading: End of virtual log reached.
GenericLog GenericError 1 0 2004-07-08 12:18:16 (ss2klogapi.cpp (2080) err=901108 sys=0) SBL-ADM-01108: Log File Reading: End of virtual log reached.
GenericLog GenericError 1 0 2004-07-08 12:18:16 (ss2klogapi.cpp (2362) err=901108 sys=0) SBL-ADM-01108: Log File Reading: End of virtual log reached.
GenericLog GenericError 1 0 2004-07-08 12:18:16 (ss2klogapi.cpp (2080) err=901108 sys=0) SBL-ADM-01108: Log File Reading: End of virtual log reached.
GenericLog GenericError 1 0 2004-07-08 12:18:16 (ss2klogapi.cpp (2362) err=901108 sys=0) SBL-ADM-01108: Log File Reading: End of virtual log reached.
GenericLog GenericError 1 0 2004-07-08 12:18:16 (ss2klogapi.cpp (2080) err=901108 sys=0) SBL-ADM-01108: Log File Reading: End of virtual log reached.
GenericLog GenericError 1 0 2004-07-08 12:18:16 (ss2klogapi.cpp (2362) err=901108 sys=0) SBL-ADM-01108: Log File Reading: End of virtual log reached.
GenericLog GenericError 1 0 2004-07-08 12:18:17 (ss2klogapi.cpp (2080) err=901108 sys=0) SBL-ADM-01108: Log File Reading: End of virtual log reached.
GenericLog GenericError 1 0 2004-07-08 12:18:17 (ss2klogapi.cpp (2362) err=901108 sys=0) SBL-ADM-01108: Log File Reading: End of virtual log reached.
GenericLog GenericError 1 0 ...

Solution

Message 1

For the benefit of other users:

I was able to reproduce this behavior in our internal 7.7.1 [18306] environment. I created a change request (12-N2L48T) to address this behavior. This change request will be appropriately prioritized and addressed in a future release.

I researched on any workaround (e.g: increasing event log levels) that could help eliminate these errors. Unfortunately, these errors do come up with all the event log levels – hence there is no workaround available. However, as SBL-ADM-01108 and SBL-ADM-01105 are benign errors, none of your other functionality would be affected because of these errors. Please continue to ignore these errors and educate your administrators to do the same.

Thank you,

No comments:

Post a Comment