SBL-SVC-00213



Applies to:


Siebel eConfigurator - Version 8.1.1 SIA [21111] and later
Information in this document applies to any platform.



Symptoms


Errors with Remote Configurator when using WebServices



ERRORS FROM THE LOG:




  • StpExec Create 4 00000007504f6a50:0 2012-09-11 18:42:25 Creazione istanza della definizione del passo 'Begin Configuration'.

  • GenericLog GenericError 1 00000002504f1e77:0 2012-09-11 18:42:26 ( (0) err=4653064 sys=0) SBL-SCB-00008: Componente ((null)) non disponibile su questo server.

  • GenericLog GenericError 1 00000002504f4126:0 2012-09-11 18:42:26 ( (0) err=4653064 sys=0) SBL-SCB-00008: Componente ((null)) non disponibile su questo server.

  • GenericLog GenericError 1 00000002504f1e82:0 2012-09-11 18:42:26 ( (0) err=4653064 sys=0) SBL-SCB-00008: Componente ((null)) non disponibile su questo server.

  • GenericLog GenericError 1 00000002504f1e82:0 2012-09-11 18:42:26 (ssmsismgr.cpp (626) err=3670020 sys=0) SBL-SSM-00004: Si è verificato un errore relativo a SISNAPI Hello. Il componente server potrebbe non essere disponibile.

  • ObjMgrLog Error 1 00000002504f1e82:0 2012-09-11 18:42:27 (rmodel.cpp (2239)) SBL-SVC-00213: Login fallito.

  • ObjMgrLog Error 1 00000002504f1e82:0 2012-09-11 18:42:27 (rmodel.cpp (2279)) SBL-SVC-00209: Login non riuscito durante il tentativo di connessione a siebel://VirtualServer/ENTPRE81/eProdCfgObjMgr_ITA

  • Error Error 1 00000002504f1e82:0 2012-09-11
    18:42:27 Cfg Server Manager error: unable to connect to server
    eProdCfgObjMgr_ITA for product 1-134L7F using connect string
    siebel://VirtualServer/ENTPRE81/eProdCfgObjMgr_ITA - Login non riuscito
    durante il tentativo di connessione a
    siebel://VirtualServer/ENTPRE81/eProdCfgObjMgr_ITA(SBL-SVC-00209    )

  • ObjMgrBusServiceLog Error 1 00000002504f1e82:0 2012-09-11 18:42:27 (configsvc.cpp (1486)) SBL-CFG-00155: Complex Object Instance Service Internal Error:

  • ObjMgrLog Error 1 00000002504f1e82:0 2012-09-11 18:42:27 (stepexec.cpp (1572)) SBL-BPR-00162: Errore nel richiamo del servizio 'Configurator Web Service', metodo 'BeginConfiguration' al passo 'Begin Configuration'.







STEPS

The issue can be reproduced with the following steps:

1. Enable Remote Configurator

2. Run a WebService like BeginConfiugration

=> Errors





Cause


EAI Object Manager is trying to launch the default Configurator Component: eProdCfgObjMgr_ITA

However, this component was disabled. Instead cloned components have
been enabled like eProdCfgObjMgr2_ita, eProdCfgObjMgr3_ita,
eProdCfgObjMgr4_ita. But the application is not trying to start it.



The EAI didn't follow the routing of the ecfgserver.txt because it was
automatically deployed by Administration Cache view only on the Siebel
File System set at the Enterprise level and not also on the local Siebel
File System indicated on "Product Configurator - FS location" parameter
of the EAI Object Manager.







Solution


"Product Configurator - FS location" parameter of the EAI Object Manager need to be set appropriately.












Applies to:


Siebel Configurator - Version 7.8.2.5 [19227] and later
Siebel eConfigurator - Version 7.8.2 [19213] and later
Information in this document applies to any platform.

eProdCfgObjMgr







Symptoms


Customer wanted to use Component Based Routing from eCommunications
but when trying to customize a product it failed and the following
messages could be seen in the eCommunications log:

SBL-SSM-00040: Internal Error: host name is empty
SBL-SVC-00213: Login failed.
SBL-SVC-00209: Login failed attempting to connect to siebel:// /esblt01/eProdCfgObjMgr_200_enu
Cfg
Server Manager error: unable to connect to server
eProdCfgObjMgr_200_enu for product 2-58FGUR using connect string
siebel:// /esblt01/eProdCfgObjMgr_200_enu - Login failed attempting to
connect to siebel:// /esblt01/eProdCfgObjMgr_200_enu(SBL-SVC-00209)

Normally the connect string should look like this:
siebel://acsv902:2321/esblt01/eprodcfgobjmgr_200_enu

However, the above connect strings show a space instead of a server name like acsv902:2321.



Changes


Parameter "Product Configurator - Remote Server Name" for the
eCommunications object manager had been cleared. This is necessary to
use routing information from ecfgserver.txt.



Cause


Using the Administration - Server Configuration view or the Server
Manager Utility (srvmrgr) does not allow to set a parameter to NULL. So a
space had been inserted.



Solution


To set a parameter to NULL use the srvrcfg utility instead. For more information please refer to the following document:
Component Request will stay in the Queued status after its related Component has been restarted.












Applies to:


Siebel CRM - Version: 7.5.3 [100] and later   [Release: V7 and later ]
Information in this document applies to any platform.

This document was previously published as Siebel Alert 924.



Description


In Siebel eBusiness Applications version 7.5 and higher, the Siebel
Sync application must be installed on each client machine where it
connects to the Object Manager on the Server using a connect string. The
connect string is of the following format:


siebel.TCPIP.None.None://<Gateway host>:2320/<Enterprise>/<ObjMgr>/<Siebel Server>

There are situations, however, when the Gateway and Siebel Server host names need to be succeeded by a domain name such as:


siebel.TCPIP.None.None://ABC.xyz.us.com:2320/<Enterprise>/<ObjMgr>/<Siebel Server>

In this example, xyz.us.com is the domain and ABC is the Gateway
host name. When using this type of connect string, users receive the
following login error when they try to login to the Siebel Sync
application:


Login failed attempting to
connect to
siebel.TCPIP.None.None://ABC.xyz.us.com:2320/<Enterprise>/<ObjMgr>/<Siebel
Server> (SBL-SVC-00209)

Next error:


Login failed.
SBL-SSM-00003:
(rmodel.cpp 92: 2226) error code = 5600003, system error = 0, msg1 =
(null), msg2 = (null), msg3 = (null), msg4 = (null)(SBL-SVC-00213)


Change Request 12-J2NJAS has been logged to address this product defect.


Likelihood of Occurrence


This behavior occurs when there is a requirement to have the Gateway
and Siebel Server host names succeeded by a domain name in the connect
string when running Siebel Sync on version 7.5 and higher.



Possible Symptoms


Users are unable to log into the Siebel Sync Application and receive the errors specified above.



Workaround or Resolution


In situations where the requirement is to have the Gateway and Siebel
Server host names succeeded by a domain name in the connect string, the
domain should be added to the DNS list on the local machine (client)
where Siebel Sync runs to workaround this issue.


To do this in Microsoft Windows 2000 (the procedure is similar in Microsoft Windows XP and in Microsoft Windows NT):




  1. Right click on My Network Places and select Properties.




  2. In the Network and Dial-up Connections window, select the
    connection used (Local Area Connection or your VPN connection), right
    click and select Properties.




  3. In the Local Area Connection Properties window, select Internet Protocol (TCP/IP) and click Properties, then click Advanced.




  4. Select the DNS tab.




  5. In the lower half, check: Append these DNS suffixes (in order) and add your suffix here.


    For example, if the Siebel Server machine's fully qualified name is siebsrvrhostname.domain.comm then add domain.com here.




This setting requires a restart of the machine to become fully
effective. The reason for this is that the Gateway Server will just
return siebsrvrhostname (the hostname of the Siebel Server machine on
which the object manager used for PIMSync is running).


Without the configuration to add the DNS suffix as above, the
client machine will not be able to resolve siebsrvrhostname. With the
added suffix the client should be able to resolve the resulting
siebsrvrhostname.domain.com, which is required for successful PIMSync
communication.


Alternatively, the network administrator can configure the DNS server so that it will resolve the unqualified hostnames.


NOTE: This behavior does not occur in Siebel eBusiness Applications version 7.0.4.x or 7.0.5.x.


Keywords:SBL-SSM-00003, login failed, attempting, connect, string, gateway host name, DNS





תגובות

הוסף רשומת תגובה

פוסטים פופולריים מהבלוג הזה

FINS Data Transfer Utilities

תמונה
The best thing while working on siebel is you are never short of options. Recently we had requirement of updating a Service request from contact. Finally we did that using "EAI Siebel Adapter" business service. However during that time i came across another business service "FINS Data Transfer Utilities" popularly known as DTU business service. As i was not having prior knowledge of it going by the rule of not learning swimming lessons while drowning i decided not to go for it. Lately i have tried to explore this service and trust me it can do wonders. Here is a sample example update of Service Request from contact. We need to follow below steps in order to understand strength of this business service. 1 - Navigate to Site Map. Go to Administration - Application -> Data Map Administration tab. Create a new Record with following options: Name: Service Request Test Source Business Object: Contact Destination Business Object: Service Request Here the source business
המשך לקרוא

SBL-BPR-00191: The rowId of the active row of the primary buscomp '%1', '%2', does not match the Primary Id

Applies to: Product Release: V7 (Enterprise) Version: 7.5.3 [16157] ESN Database: Oracle 9.2.0.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-1386997031. Symptoms SBL-BPR-00191 We have a error with a workflow. This WF is excuted by policy when a particular activity is closed. The WF Business Object is 'Action'. Inside this WF, there is a subprocess that invokes a Business Service that creates a new activity. In a second subprocess, the region Id of this new activity is updated using the standar update method funcionality of Siebel workflow process. Error processing Siebel Operation for: Business Object 'Action' Business Component 'Action' Primary Id ''1-5NEI6' Operation 'Insert'(SBL-BPR-00100) -- The rowId of the active row of the primary buscomp 'Action', '1-4SNCV', does not match the Prima
המשך לקרוא

Profile Attributes and Open UI

תמונה
Yes, Profile Attributes! As the ever attentive, up-to-date Siebel CRM expert that you are when you read this, you know that in Siebel Open UI (since version 15), it is no longer allowed/supported to  set  Profile Attributes from browser-side script. But  getting  them is not a problem, since the  GetProfileAttr  function works perfectly fine. Recently I found a few vanilla Profile Attributes that came quite handy in my work in Open UI JavaScript: Navigation Type : stores the navigation type such as "NAVIGATION_TAB" ActiveViewName : does what it says on the tin IsOpenUI : returns "1" when the application runs in Open UI Is SUI Theme : when "TRUE", the application theme is Synergy (aka SUI) Position:  returns the currently active position Primary Responsibility Name : guess what this one is… Profile Image : returns the URL of the user's profile image Org.Name : returns the name of the user's organization Here's a sample line of
המשך לקרוא