Siebel URL giving "Page Cannot Be Displayed" error SBL-SMI-00107
(Doc ID 498045.1)
Last updated on NOVEMBER 14, 2019
Applies to:
Siebel System Software - Version 7.5.3 [16157] and laterz*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3 [16157]
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: Microsoft Windows 2000 Advanced Server SP 4
This document was previously published as Siebel SR 38-1183053761.
***Checked for relevance on 02-NOV-2012***
***Checked for relevance on 16-JUL-2014***
Symptoms
SBL-SMI-00107, SBL-NET-01023, SBL-SSM-00004, SBL-SSM-00003, SBL-SSM-00006
When we login to the url for the very first time, we get a "Page Cannot Be Displayed" error
When we look at the ERM Object Manager logs, we dont see any new task triggered for the ERM task.
If we refresh the screen, we get the login box, but with a "Page Cannot be Displayed" above the box.
Now, the ERM object Manager log shows the following data:
15:03:07 Invocation of Applet Menu New Service::NewExpense is not allowed.GenericLog GenericError 1 2004-02-06 15:03:07 Invocation of Applet Menu New Service::NewTimeSheet is not allowed.GenericLog GenericError 1 2004-02-06 15:03:07 Invocation of Applet Menu New Service::NewCommunication is not allowed.GenericLog GenericError 1 2004-02-06 15:03:07 Invocation of Applet Menu New Service::NewCorrespondence is not allowed.GenericLog GenericError 1 2004-02-06 15:03:07 Invocation of Search Client Service::OpenSrchCenter is not allowed.GenericLog GenericError 1 2004-02-06 15:03:07 Invocation of Persistent Customer Dashboard::OpenDashboard is not allowed.GenericLog GenericError 1 2004-02-06 15:03:07 Invocation of Persistent Customer Dashboard::ClearDashboard is not allowed.GenericLog GenericError 1 2004-02-06 15:03:07 Invocation of Persistent Customer Dashboard::CloseDashboard is not allowed.GenericLog GenericError 1 2004-02-06 15:03:07 Invocation of Search Client Service::AutoSearch is not allowed."
If we finally refresh the screen for the third time, we could finally get into the application.
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
Message 1 |