Siebel Services not starting Gateway name not defined ErrCode 4597527

Issue:
When starting Siebel services receiving error:

Windows could not start the Siebel Server [SERVER_NAME] on Local Computer. For more information, review the System Event Log. If this is non-Microsoft service, contact the service vendor, and refer to service-specific error code 2555922.

Analysis:
From Siebel Server Logs (UAT_ENT.STG-APP.log) found below error:
1. NSS - ErrCode 4597527 SysErr 0
2. SBL-SMI-00053: Internal: The Siebel Gateway name was not specified (smilobj)

From Gateway Server Logs (NameSrvr.log) found below errors:

DBCLog   DBCLogError   1   0000000262001088:0   2022-02-07 12:28:54   [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'SADMIN'.

GenericLog   GenericError   1   0000000262001088:0   2022-02-07 12:28:54   (secmgr.cpp (2768) err=4597538 sys=127) SBL-SEC-10018: [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'SADMIN'.

GenericLog   GenericError   1   0000000262001088:0   2022-02-07 12:28:54   (secmgr.cpp (2824) err=4597527 sys=0) SBL-SEC-10007: The username or password you have entered is not correct. Enter your username and password again.

Solution:
Reset the SADMIN password from SQL Server (should be same as when configured the Siebel).
Stop the Gateway and start again.
Start the Siebel Services.
Wait for few minutes and open the Siebel Application.

Comments

How to set Profile Attribute in Siebel Workflow

For setting the Profile Attribute in Siebel Workflow, follow below steps: Add Business Service box in workflow. Open Business Service properties. Set SessionAccessService in Business Service Name. Set SetProfileAttr in Method Name. Then click on Business Service and set Input Arguments as below: Against Name argument you will add your profile attribute name and against Value argument you will add value for the new profile attribute, it could be from Process Property or Literal.

How to call Popup Applet through Server Script in Siebel

Background: Based on the requirements you need to show data or reports on a popup applet. You can invoke popup applet using workflow (below business service will be used in business service step), applet server script or browser script and using vanilla method and setting field user properties. Procedure: Below is the script for calling popup applet through server script: if (MethodName == "MethodName") { var oServiceAF = TheApplication().GetService("SLM Save List Service"); var inputPropAF = TheApplication().NewPropertySet(); var outputPropAF = TheApplication().NewPropertySet(); inputPropAF.SetProperty("Applet Name","ABC Popup Applet"); inputPropAF.SetProperty("Applet Mode","6"); inputPropAF.SetProperty("Applet Height", "700"); inputPropAF.SetProperty("Applet Width", "700"); oServiceAF.InvokeMethod("LoadPopupApplet", inputPropAF, outputPropAF) return (CancelOperati...

How to create and publish Inbound Web Service in Siebel based on Workflow

Inbound Web Services: The Inbound Web Service allows an external system to call a Siebel published Web Service. You can publish a business service or a business process as a Web Service and generate a Web Service Definition Language (WSDL) file that an external system can import. The Inbound Web Services can only be published from Siebel C using SOAP-RPC binding. Source: Oracle Docs What Is The Difference Between Web Services and APIs? An API is an interface that allows you to build on the data and functionality of another application, while a web service is a network-based resource that fulfills a specific task. Yes, there’s overlap between the two: all web services are APIs, but not all APIs are web services. Both web services and APIs are — at their core — very useful and very much used today. However, it’s the web services associated with SOAP and/or Service Oriented Architecture which are falling out of favor. Source: NordicApis Process: Prepare the workflow which will serve as Si...

ITCanopy

Search This Blog