SBL-GEN-05043: The specified user does not have the proper privileges to connect to the name server.

Applies to:

Siebel System Software - Version: 8.1 [21039] and later   [Release: V8 and later ]
Information in this document applies to any platform.
Error Message Area:Generic - GEN
Version:Siebel 8.1

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-GEN-05043: The specified user does not have the proper privileges to connect to the name server.

Scope

This document is informational and intended for any user.

SBL-GEN-05043: The specified user does not have the proper privileges to connect to the name server.

Explanation

Need a Siebel administrator username and password to connect to the Siebel gateway server.
For example, "SADMIN" is an example of administative user account.

Corrective Action

Please provide valid administrator username and password to access the gateway server.

Applies to:

Siebel eClinical - Version 8.1.1.5 SIA [21229] and later
Information in this document applies to any platform.

Symptoms

After server reboot unable to start the siebel service.
Observed the below errors in NameServer.log file:
2009-09-18 16:14:49 select T2.NAME from SIEBEL.S_PER_RESP T1, SIEBEL.S_RESP T2, SIEBEL.S_USER T3 where T1.RESP_ID=T2.ROW_ID AND T1.PER_ID=T3.PAR_ROW_ID AND T3.LOGIN='SADMIN'
2009-09-18 16:14:49End 10 Worst Performing Queries ***********
2009-09-18 16:14:49 (SQLFreeEnv) Env Handle: 812926856, Time: 0.004ms
2009-09-18 16:14:49 Invoking SecurityGetRoles for user sadmin.
2009-09-18 16:14:49 user sadmin has 246 responsibilities.
2009-09-18 16:14:49 (client.cpp (325) err=5043 sys=0) SBL-GEN-05043: The specified user does not have the proper privileges to connect to the name server.

Cause

SADMIN user got deleted.

Solution

After restoring the SADMIN user and restarting the gateway along with Siebel server resolved the issue.

References

NOTE:944161.1 - RECEIVING ERROR MESSAGE WHEN STARTING THE SIEBEL SERVER OR SRVRMGR

Symptoms

Siebel 8.1.1 new installation was working fine.
After migrate database from previous Siebel version, gateway was starting, but srvrmgr was not working.

Cause

We have verified SADMIN was correctly connecting to database from Gateway machine.

Solution

We checked all DB2 settings and connection were working from Gateway.
But we still had this error message in the gateway log:

2009-09-18 16:14:49 select T2.NAME from SIEBEL.S_PER_RESP T1, SIEBEL.S_RESP T2, SIEBEL.S_USER T3 where T1.RESP_ID=T2.ROW_ID AND T1.PER_ID=T3.PAR_ROW_ID AND T3.LOGIN='SADMIN'
2009-09-18 16:14:49End 10 Worst Performing Queries ***********
2009-09-18 16:14:49 (SQLFreeEnv) Env Handle: 812926856, Time: 0.004ms
2009-09-18 16:14:49 Invoking SecurityGetRoles for user sadmin.
2009-09-18 16:14:49 user sadmin has 246 responsibilities.
2009-09-18 16:14:49 (client.cpp (325) err=5043 sys=0) SBL-GEN-05043: The specified user does not have the proper privileges to connect to the name server.
2009-09-18 16:14:49 515: [TCPIP-server] recv() failed for sd=-1 (err=9 | Bad file number)
2009-09-18 16:14:49 515: [TCPIP-server] send() failed for sd=-1 (err=9 | Bad file number)


Running the above query against both the custom and vanilla databases showed that the Siebel Administrator Reponsability was missing. It existed for other users but was missing for Sadmin user. After adding the Siebel Administrator to the SADMIN user, the Gateway started correctly and srvrmgr ran correctly.