Siebel URL giving "Page Cannot Be Displayed" error SBL-SMI-00107 (Doc ID 498045.1)

Last updated on APRIL 30, 2018

Applies to:

Symptoms

SBL-SMI-00107, SBL-NET-01023, SBL-SSM-00004, SBL-SSM-00003, SBL-SSM-00006

Dear Tech Support,
We are having a serious issue with our Production url.
http://10.190.170.66/erm_enu
When we login to the url for the very first time,
We get a "Page Cannot Be Displayed" error
[Please look at the Screen shot -Error1.jpg]
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.
[Please look at the Screen shot -Error2.jpg]
Now, the ERM object Manager log shows the following data:
"2021 2004-02-06 15:03:07 2004-02-06 15:23:14 +0530 00000009 001 001f 0001 09 ERMObjMgr_enu 43120 2640 3088 D:\sea753\siebsrvr\log\ERMObjMgr_enu_43120.log 7.5.3 [16157] ENUGenericLog    GenericError    1    2004-02-06 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.

Can you Please get back to us as soon as possible because this is seriously affecting our production environment.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.