Fatal error (2555922): Could not open connection to Siebel Gateway_could not open connection to gateway

Hello 
Thanks for your reply 

Problem is I can't connect to gateway using sadmin user. 
When I'm trying, I received the following error : 
Fatal error (2555922): Could not open connection to Siebel Gateway configuration store (%1:%2)., exiting... 

And I again have the same errors in NameSrvr.log

Thanks for your reply. 
I've tried to connect to the gateway, but I also have errors when doing this : 
Fatal error (2555922): Could not open connection to Siebel Gateway configuration store (%1:%2)., exiting... 

And the same error messages appears in NameSrvr.log

U shuld try to connect gateway with old sadmin password and then change it at enterprise level.

But sadmin password have not been changed. 
And password I use is the correct one defined in database as I can connect using sqlplus and odbcsql

So I'm assuming the gtwserver service is not starting. Since you are using 
8.1, there is a new security feature, to authenticate access to the gateway 
server. 

In windows, for the service to start, you provide the password in the 
windows service level, it should be the same in linux too, i just don't 
recall where. Check and see if the password properly populated. Not sure if 
this is the problem, check and see. Also refer the doc in metalink, *[ID 
784524.1]* 

If that's not the issue, try restoring an older version of the siebns.dat 
file in the gtwsrvr\admin folder, and restart the enterprise. You should 
find a lot of backed up siebens.dat files in that folder. What i foresee, is 
a good chance of that file getting corrupted. 

Let us know how it goes. 

regards, 
Resly

the gateway start correctly on server and process is well present 
siebadm 13228 1 0 08:00 pts/2 00:00:00 siebsvc -s gtwyns -a /f /siebadm/gtwysrvr/sys/siebns.dat /t 2320 /c /siebadm/gtwysrvr/bin/gateway.cfg 

I even tried to restore an old siebns.dat file but problem is still the same. 
When I tried to log on gateway using srvrmgr I have this : 
srvrmgr -g host:2320 -e SBA_ENT -u sadmin -p password 
Fatal error (2555922): Could not open connection to Siebel Gateway configuration store (%1:%2)., exiting... 

and still the same errors in NameSrvr.log 
GenericLog GenericError 1 000000024c5233ac:0 2010-07-30 08:00:54 (secmgr.cpp (2735) err=4597527 sys=0) SBL-SEC-10007: The password you have entered is not correct. Please enter your password again. 
GenericLog GenericError 1 000000024c5233ac:0 2010-07-30 08:00:54 (client.cpp (309) err=4597527 sys=0) SBL-SEC-10007: The password you have entered is not correct. Please enter your password again. 
SisnTcpIp SisnSockError 1 000000024c5233ac:0 2010-07-30 08:00:54 1089338272: [TCPIP-server] recv() failed for sd=-1 (err=9 | Bad file descriptor) 
SisnTcpIp SisnSockError 1 000000024c5233ac:0 2010-07-30 08:00:54 1089338272: [TCPIP-server] send() failed for sd=-1 (err=9 | Bad file descriptor) 

At least, I'm sure of the database password because the error message is different when I try with a bad password 
GenericLog GenericError 1 0000000c4c517e14:0 2010-07-29 11:26:34 (secmgr.cpp (2679) err=4597538 sys=0) SBL-SEC-10018: [DataDirect][ODBC 20101 driver][20101]ORA-01017: invalid username/password; logon denied

If it can help to find a solution, I also have access to repository using Siebel Tools. I hope the gateway password is stored somewhere, but don't really know where it could be. Perhaps some of you have an idea ?

Ok, since the gateway server is running, try connecting to the database from 
the gateway server. This ensures, the connectivity is good between the 
gateway and database server. 

Use \gtwsrvr\bin\odbcsql /u SADMIN /p passwd /s ODBC_data_source 

also check if the value in gtwysrvr/sys/.odbc.ini for the above used 
ODBC_data_source and the parameter DSConnectString in 
gtwysrvr\admin\siebns.dat are the same. 

HTH 
Resly

Please check this. We need to copy the IVSE.LIC file in the Gatwy server root directory from siebsrvr directory. The ODBC will expire after 15 days so we need to copy this file for Siebel services to start.

I am also facing this error but after applying path 8.1.1.3 on my servers 
today. 
On what version is your application??? 
I tried all possible ways but it didn't worked.... you might have to 
reconfigure gateway, enterprise & siebel servers 
Anyway I have raised an SR with Oracle for the same... let's see if they 
give any work around....

After reading your last post Mathews, I've checked again the ODBC connection. 
It seems I had a problem with it as it worked within Siebel server environment but not gateway (using  siebenv.sh) 

So I changed the  siebenv.sh to use the odbc.ini in ${SIEBSRVR}/admin/ 

Now odbcsql is working well, and after restarting the gateway, and siebel server could start. 

Thanks a lot for your replies

Thanks a lot 
It worked for me as well.... 

Nikhil

Cool, glad it helped the two of you. 

-Resly

I'm having the same problem after installing the 8.1.1.3 patch. There must be something that the patch is doing that is causing this. I tried the recommendations listed above, but found that:
1)\gtwsrvr\bin\odbcsql doesn't work as there is no odbcsql in the directory
2)DSConnectString is not in my siebns.dat - the file appears to be binary?
Everything worked fine before applying the patch and running a dev2prod

Why not try to remove the patch to the previous version and see If this
works?
If it works fine install again the latest patch.

Regards.

In .odbc.ini file under sys folder of gateway server you will find some junk
characters starting with Q under enterprise_DSN data source remove that line
and restart your environment.
It should come up fine.

Thanks
Nikhil