SBL-OMS-00102
Applies to:
Siebel System Software - Version: 7.7.1 [18306] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.7.1 [18306]
Database: Oracle 9i
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: Sun Solaris 9
This document was previously published as Siebel SR 38-1577317551.
Symptoms
SBL-OMS-00102Hi,
we are having problems with our siebel Development environment,
Problem:
-After the siebel service is started "Diccache.dat" file is not getting
created,
-we are not able to Apply changes to any table. Error is "Unable to load dictionary
data."
-we are not able to perform DDLSYNC.
Siebel log file has this
errors.
SBL-OMS-00102 Process exited with error - Error %1 logging in to
the application
(schedule.cpp (905) err=2100096 sys=0) SBL-SMI-00096: The maximum number of
restarts (10) for MinUpTime has been reached. The component SvrTblCleanup will not be restarted
again.
As this is affecting our Development we need a solution for this as soon as
possible.
Cause
Configuration/ Setup
Solution
Message 1
For the benefits of other readers:
The customer was getting an error creating the diccache.dat file.
Technical Support suggested running both dictutl and dbcheck utilities.
In addition a suggestion was made to review the latest changes that had
been checked into the development environment. The customer ran these
utilities and also attempted to review some recent changes made to
support EIM. When attempting to run an EIM job the following error
occurred:
Error 205: Missing temporary column for
S_ORDER_ITEM.X_END_USER_ACCNT_ID from EIM_ORDER_ITEM!
Error 205: Failed to load the application dictionary.
The root cause had been discovered:
"We managed to pull changes on EIM tables done recently. After that,
ddlsync was successful and other functions from development standpoint
were good. Thank you for the assistance."
Applies to:
Siebel Sales Enterprise - Version: 7.7.2 [18325] and later [Release: V7 and later ]
Information in this document applies to any platform.
Symptoms
After the installation and configuration of an additional Siebel
language (DEU - German in this case) for an existing Siebel CRM
application, the newly added language components weren't working as
expected. Errors of the following type were filed in the Siebel workflow
component logs for DEU, for instance:
"Unable to load message 0x568e"
In this case these errors were shown only on one of the two Siebel
servers where this additional language was added. Therefore it was
possible to start troubleshooting this issue comparing the behavior on
the two server instances accordingly.
Here following the sequence of errors starting the DEU Siebel workflow component on one of the Siebel servers:
...
ServerLog LstnObjPrivCreate 3 0 2008-09-10 11:45:25 Port 49188 f�r Workflow Process Manager W DEU erstellt
ObjMgrLog Error 1 0 2008-09-10 11:45:28 (oracon.cpp (3033)) : Unable to load message 0x568e
ObjMgrLog
Error 1 0 2008-09-10 11:45:28 (sslocale.cpp (287)) SBL-UIF-00360: Diese
Operation ist nicht g�ltig, wenn es keine aktive Ansicht gibt.
ObjMgrSessionLog Error 1 0 2008-09-10 11:45:28 (dmsessionlocale.cpp (235)) : Unable to load message 0x5aa7
GenericLog GenericError 1 0 2008-09-10 11:45:28 Objekt-Manager-Fehler: ([0] Unable to load message 0x5aa7() (0x5aa7))
GenericLog
GenericError 1 0 2008-09-10 11:45:28 ( (0) err=4300107 sys=23207)
SBL-OMS-00107: Objekt-Manager-Fehler: ([0] Unable to load message
0x5aa7() (0x5aa7))
GenericLog GenericError 1 0 2008-09-10 11:45:28
(ccfom.cpp (551) err=4300102 sys=0) SBL-OMS-00102: Fehler 23207 bei der
Anmeldung bei der Anwendung
GenericLog GenericError 1 0 2008-09-10
11:45:28 (bsvcmgr.cpp (898) err=4300102 sys=0) SBL-OMS-00102: Fehler
23207 bei der Anmeldung bei der Anwendung
GenericLog GenericError 1 0
2008-09-10 11:45:28 (bsvcmgr.cpp (1015) err=4300102 sys=0)
SBL-OMS-00102: Fehler 23207 bei der Anmeldung bei der Anwendung
GenericLog
GenericError 1 0 2008-09-10 11:45:28 (smimtsrv.cpp (1063) err=4300102
sys=0) SBL-OMS-00102: Fehler 23207 bei der Anmeldung bei der Anwendung
SmiLayerLog Error 1 0 2008-09-10 11:45:28 Terminate process due to unrecoverable error: 4300102. (Main Thread)
Cause
An unclean installation of the affected language dependent
software (DEU here) was at the root of this issue, as a consequence of
this, the language independent APIs couldn't locate the language
dependent (DEU) messages and dll's in the bin/deu and locale/deu
directories on this Siebel server, therefore the "(dmsessionlocale.cpp
(235)) : Unable to load message 0x5aa7" and "(oracon.cpp (3033)) :
Unable to load message 0x568e" messages were thrown and the localized
components weren't working.
Solution
The approach in order to troubleshoot this type of issues would be to
(this assumes we have two Siebel server instances, one working and one
not):
1) Replace the bin\DEU and locale\DEU directories for
non-working Siebel server with the corresponding ones from the
environment where the affected language works as expected.
Note that this approach would only be possible on the assumption that both Siebel Servers are at same Siebel version level.
Instructions:
(a) Stop all Siebel and Web Server services on the environment where we have this issue.
(b)
Take a backup of this environment's bin\DEU and locale\DEU directories
and replace them with the ones as taken from the other environment where
we know this is working (if they are at the same Siebel version level).
2) In case the above approach doesn't work, another way to
troubleshoot this would be to point the non-working Siebel Server
temporarily to the Siebel database for the environment where the
additional languages work as expected.
With 1) we are trying to
exclude issues with the localized software that was added to the
non-working environment. With 2) we are trying to rule out issues with
the localized seed and repository data that should also have been added
to the Siebel schema and repository leveraged by the non-working server.
In most cases, this type of issues can be resolved by implementing the suggestion given at point 1).
An alternative to the suggestion at point 1) would be to re-install
the non-working environment from scratch including the additional
language(s).
Applies to:
Siebel System Software - Version: 7.5.3.8 [16192] to 8.1.1.2[21215] - Release: V7 to V8
HP-UX Itanium
Product Release: V7 (Enterprise)
Version: 7.5.3.8 [16192]
Database: Oracle 9.0.1
Application Server OS: HP-UX 10.0
Database Server OS: HP 9000 Series HP-UX
This document was previously published as Siebel SR 38-2284009791.
*** Checked for relevance on 08-Dec-2010 ***
Symptoms
SBL-DAT-00446, SBL-OMS-00102, SBL-OMS-00107, SBL-SRM-00016In the server.log the following error messages are
generated:
ServerLog ProcessCreate 1 2005-07-18
19:17:25 Created multithreaded server process (OS pid = 2648) for Server
Request Processor with task id
31756
ServerLog ProcessExit 1 2005-07-18
19:17:51 SRBroker
31754 TERMINATED Process was
terminated
ServerLog ProcessExit 1 2005-07-18
19:17:58 SRProc 31756 TERMINATED Process
was
terminated
ServerLog ProcessExit 1 2005-07-18
19:17:58 BusIntBatchMgr
31749 TERMINATED Process was
terminated
ServerLog ProcessExit 1 2005-07-18
19:17:59 WfProcBatchMgr
31747 TERMINATED Process was
terminated
ServerLog ProcessExit 1 2005-07-18
19:17:59 WfProcMgr 31748 TERMINATED Process
was
terminated
ServerLog ProcessExit 1 2005-07-18
19:17:59 BusIntMgr 31750 TERMINATED Process
was terminated
______________________________________________________________
The error
being generated in the SR_BROKER.log
is:
GenericLog GenericError 1 2005-07-18
17:18:23 Unable to verify login name
SIEBEL.
GenericLog GenericError 1 2005-07-18
17:18:23 (srbthrd.cpp 44(3901) err=3200016 sys=0) SBL-SRM-00016: Unable to
initialize the Database environment -- Unable to start common
api
GenericLog GenericError 1 2005-07-18
17:18:23 (srbmtsrv.cpp 39(71) err=3200016 sys=0) SBL-SRM-00016: Unable to
initialize the Database environment --
(null)
_____________________________________________________________
Note: We are able
to log into Siebel through the thin client.
Cause
.
Solution
For the benefits of other users:
There are a lot of error logging in to the application and logon error
reported in various component log files. After setting the User Name and
Password parameter at Site Map > Server Administration >
Enterprise Configuration > Enterprise Parameters, the component start
up properly from Server Administration -> Servers -> Server
Components screens. But the logon error reoccurs whenever restart the
Siebel server.
Solution:
After changing the User Name and Password parameters, select "Start Reconfiguration" then "Commit Reconfiguration".
Thank you,
Siebel Technical Support
Keywords: SBL-SRM-00016, SBL-OMS-00107, SBL-OMS-00102, SBL-DAT-00446,
Error (null) logging in to the application, invalid set of logon
parameters, invalid username/password; logon denied
Applies to:
Siebel Remote - Version: 7.5.2.215 [16076] to 8.0 [20405] - Release: V7 to V8
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (MidMarket)
Version: 7.5.2.100 [15252] MME
Database: Microsoft SQL Server 2000 SP 2
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: Microsoft Windows 2000 Server SP 3
This document was previously published as Siebel SR 38-1480993902.
Symptoms
SBL-DCK-00164, SBL-OMS-00102, SBL-OMS-00107, SBL-SRM-00016Dear Siebel Support Web,
We have just set up a new development environment making a copy
of the database we have in our initial development environment. We can now log in through the web
client both as SADMIN and with a user we have added with the addusr.sql script. We have however
problems with some of the Server Components being unavailable, e.g. the Server Request Broker and
Server Request Processor among others. Server Manager and Call Center OM (ENU) runs fine though.
I have seen from other service requests on support web that this is often because the srf. is not
an exact compile of the repository. However, I can not test this as the full compile always
freezes on "Setting Up: Applets".
The repository in the database we have copied is from a
7.5.2.100 tools version, while the new environment we are currently on is only 7.5.2 so far.
Could this be a reason why the Full Compile freezes? The reason I'm not upgrading to 7.5.2.100
yet is that we will add languages and upgrade to 7.5.3, so I thought there was no need. What do
you think could be the problem ? Any pointers would be highly appreciated.
Solution
Message 1
For the benefit of other readers, the following errors were received by the user:
DCK-00164: Error connecting to datasource (null) ((null))
OMS-00107: Object manager error: ([0] You have entered an invalid set of
logon parameters. Please type in your logon parameters again. (0x7001))
OMS-00102: Error 28673 logging in to the application
GenericLog GenericError 1 2004-09-06 21:23:47 (bsvcmgr.cpp
9(818) err=4300102 sys=0) OMS-00102: Error (null) logging in to the
application
SRM-00016: Unable to initialize the Database environment -- Unable to connect to DB (data ops)
This was resolved by resetting the SADMIN password in the database and
explicitly setting the password parameter for the relevant server
component.
Advice for increasing server side virtual memory and closing down
applications not in use was provided to successfully complete a 'Full
Compile'.
References
NOTE:887914.1 - Where to Find the Siebel Remote and Replication Manager Administration Guide Documentation
תגובות
הוסף רשומת תגובה