But this is what I got, a pop message saying:
No server connect string for Siebel Component SRBroker in Siebel Enterprise <_enterprisename>, Siebel Server <_siebelservername>
I researched for this issue and found something interesting that is worth sharing with you people here.
You will see this error when :
a) You are trying to create a Server Request, no matter it is Synchronous or Asynchronous, from dedicated client.
AND
b) RequestServerName is not correctly mentioned in the Client's cfg file.
SR Broker is the component which is responsible to interact with the various components running on the Siebel Server to assign the respective tasks. So we need to specify the Server Name (Logical) where SR Broker component is running.
So, here is what you need to do :
a) Navigate to "Administration - Server Management -> Enterprises". And in the second applet check for the Server Name under which "Server Request Broker" component is running.b) Copy the Siebel Server name.
a) Open Siebel.cfg file or whichever you are using.b) Search for section : "[InfraObjMgr]"
3. Save the Client cfg file and restart the Siebel dedicated client and it should work fine.
Nice tip, Gaurav!
ReplyDeleteI had the exact same issue once. :-)
... just had this issue 5 minutes ago. the complete hostname was entered here, instead of the logical host name.
ReplyDeleteNow it's fixed - you saved me a lot of searching bookshelf.
Thank you Gaurav, excellent !
Benny
Hello,
ReplyDeleteWhat do you mean by complete host name?