SBL-ADM-02049: There is no connected server targeted for that command.

Applies to:

Siebel System Software - Version: 7.5.3.11 [16199] - Release: V7
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3.11 [16199]
Database: Oracle 8.1.7.4
Application Server OS: Microsoft Windows 2000 Server
Database Server OS: Microsoft Windows 2000 Server

This document was previously published as Siebel SR 38-2053121161.

Symptoms

Hi,

We are setting up a Siebel development environment, A3-ETASK, as our host name.

We took a Production copy of our DB and started installation. After completing the installation and post installation tasks when we go to views in server Administration it looks fine except for Server Server View. When we go to that view we are getting the following error.

SBL-ADM-02049: There is no connected server targeted for that command

I followed the steps that are explained in alert 1067, copied the scm file that is given in the alert but still I am getting above error. Can you please help us in resolving this issue. I am attaching our siebns.dat file for your review.

Note: when I connect to server using servermanger command it gets connected without any problem.

Cause

hypenated hostnames

Solution

Message 1

For the benefit of others:

After implementing the workaround from Alert 1067 regarding hypenated hostnames:

Dedicated client access is successful in navigating and displaying Site Map > Server Administration > Server view

With thin client navigating to this view results in:

SBL-ADM-02049: There is no connected server targeted for that command

Other Server Administration views seen with the same error are: Components and Tasks

Enterprise Operations, Enterprise Configuration and Component Groups are all accessible.

In reviewing the siebns.dat, it was seen the Gateway's hostname included a colon at the end such as    A3-ETASK:

Options are to either
1) remove the colon if the gateway is on the localhost or
2) add the gateway port:     eg. A3-ETASK:2320

*Note: if the gateway exists on another host, you must include the gateway port as in (2)

To correct this via GUI, navigate to the 2 areas below to make the following changes according to options 1 or 2 above:

Site Map > Server Administration > Enterprise Configuration > Enterprise Configuration Profile > GatewayDataSrc > for parameter alias: DSConnectString

Do the same for Enterprise Configuration Profile > ServerDataSrc > for parameter alias DSGatewayAddress

Restart Gateway and Siebel servers.

These changes via srvrmgr command line utility. Refer to BookShelf's System Administration Guide for details.

Keywords: SBL-ADM-02049 , colon , hyphen , server server view

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3.3 [16172]
Database: Oracle 8.1.7.4
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: HP-UX 11.0

This document was previously published as Siebel SR 38-1506249141.

Symptoms

SBL-ADM-02049

Hi,

We are setting up a new Siebel environment ECRM11QA for our 11i release.

We took a Production copy of our DB and started installation. We have Resonate in this environment. After completing the installation and post installation tasks when we go to views in server Administration it looks fine except for Server Server View. When we go to that view we are getting the following error.

SBL-ADM-02049: There is no connected server targeted for that command

We tried to replace the Siebns.dat file with Backup copies. But did not work. I tried uninstalling and then freshly installing the whole Environment. This time after the installation without doing any post installation customisation to the components I tried to log in to the server server view again the same error.

I am attaching the Siebns.dat file.

Please handle this urgently

Thanks,

Solution

Message 1

For the benefit of other readers:

Customer was setting a new Siebel environment for their HP-UX 11i release.
They took a Production copy of their DB and started installation. They had Resonate in that environment. After completing the installation and post installation tasks when they go to views in server Administration it looked fine except for Server Server View. When they went to that view they were getting the following error.

SBL-ADM-02049: There is no connected server targeted for that command

They tried to replace the Siebns.dat file with Backup copies. But did not work. They tried uninstalling and then freshly installing the whole Environment. This time after the installation without doing any post installation customisation to the components they tried to log in to the server server view again the same error.

Customer was using the following host names for their implementation: 11i-rtp-001-d, 11i-rtp-002-d, 11i-rtp-003-d. Siebel server instance names were set as the host names.

As per Alert 1067: "Siebel Server Failures Due To Hyphen Character in Machine Hostname and in the Siebel Server Name", machine hostname and Siebel Server Name should not contain hyphens. The reason why a hyphen or dash character is not allowed is that dash is interpreted as a switch.

-> cont.

Message 2

-> contd.

Customer then removed the hyphens from the Siebel Server names and from machine host name, but the problem persisted. It was due to host names having a numeric as the first character. After renaming the host names to appropriate names, the problem was solved.

The Change Request 12-MCSFLY has been already logged for a Siebel 7.7 environment reporting the same problem, and Change Request 12-PK0UJL was logged to better document on Bookshelf host name convention.

Thanks,
Siebel Technical Support

Keywords: hostname, host names, hyphen, numeric character, 12-MCSFLY, 12-PK0UJL, name convention, SBL-ADM-02049: There is no connected server targeted for that command

Applies to:

Siebel System Software - Version: 7.7.2.4 [18365] to 8.1.1.3[21219] - Release: V7 to V8
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.7.2.4 [18365]
Database: Oracle 9.2.0.6
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: Sun Solaris 9

This document was previously published as Siebel SR 38-3012769871.

***Checked for relevance on 30-Sep-2010***

Symptoms

Hi, we have encountered errors when we migrated to the test environment.

Via the UI, when we navigate to Administration-Server Management->Servers, we see the status of the Server State as "Failed".

Hostname = crmsgws71
NOTE: no hyphen in hostname.

When I navigate to the Sessions tab, I get error "Operation failed, possibly because of "SBL-ADM-02049: There is no connected server targeted for that command."(SBL-SDM-00112) "

When I navigate to Tasks tab, I get error "SBL-NET-00000: (sasess.cpp: 701) error code = 1800000, system error = 901042, msg1 = Login failed., msg2 = (null), msg3 = (null), msg4 = (null)"

I have used a username which is a AD user to access the Admin views. We have not used a db user to access using dedicated client yet.

Please assist.

Cause

Environment issue.

Solution

For the benefits of other users:

When accessing Administration-Server Management related screen from web client, following error reported.

SBL-ADM-02049: There is no connected server targeted for that command."(SBL-SDM-00112)
SBL-NET-00000: (sasess.cpp: 701) error code = 1800000, system error = 901042, msg1 = Login failed., msg2 = (null), msg3 = (null), msg4 = (null)"

As customer is using ADSI authentication, this is an expected behavior as per "Security Guide for Siebel Business Applications" and "User Is Unable To Work in the Server Administration Screen (Doc ID 477143.1)". To perform administration task, customer is suggested to use dedicated client or configure another Object Manager which in each case database authentication used.

Customer then connecting using dedicated client with database authentication but the same error reported.

Solution:

We’ve verified that srvgrmgr command from Siebel Server is working fine and client uagent.cfg looks fine. siebns.dat file has the following setting.

/enterprises/siebtest/servers/crmssrvr/parameters/Host -> crmssrvr
/enterprises/siebtest/named subsystems/ServerDataSrc/parameters/DSGatewayAddress -> crmssrvr.crm.com

Further test done from client machine indicated that they are not able to ping to crmssrvr while ping to crmssrvr.crm.com works fine. We’ve then added crmssrvr to client host file and can access server administration screen. Setting Siebel Server host parameter to crmssrvr.crm.com resolved the issue.

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3.1 [16161] FRA Com/Med
Database: Oracle 8.1.7.4
Application Server OS: Microsoft Windows 2000 Advanced Server SP 2
Database Server OS: Sun Solaris 2.8

This document was previously published as Siebel SR 38-1153129280.

Symptoms

SBL-ADM-02049

Hello,
Sometimes multiple times per day on each of our 2 Administrators, server adminitration GUI crashes and loose connections with the server.
We can up to 6 Siebsess processes (corresponding to this serverMgr task) after multiple crashses on each server.
-------------------------------------------------------------------------------------
Exception 0xc0000005 at 0x05e093ea
Thread: 0x00000a2c, Process 0x00000f74

- CONTEXT -
EIP: 0x05e093ea, EFL: 0x00210207, FS: 0x00000038, GS: 0x00000000
CS: 0x0000001b, DS: 0x00000023, SS: 0x00000023, ES: 0x00000023
EAX: 0x00044f68, EBX: 0x00a5c820, ECX: 0x00a1faf2, EDX: 0x0000cf8f
ESI: 0x00a5c840, EDI: 0x00a5c82c, EBP: 0x0012eb58, ESP: 0x0012eaa0

- CALL STACK -
sslcsa +0x193ea = SS2KLogFileHeader::ReadHeader() +0x12a
sslcsa +0x1a35a = SS2KLogFileReader::StartReading() +0xda
sslcsa +0x1b525 = LogFileReader::OpenCurrFile() +0x95
sslcsa +0x1b00c = LogFileReader::ConstructNextValidFileName() +0x1bc
sslcsa +0x1b73d = LogFileReader::OpenNextFile() +0x4d
sslcsa +0x1b89c = LogFileReader::GetNextLine() +0x4c
sssaadmn +0x17e3f = saAdminSrvrCommand::ReadInfoLog() +0x4cf
sssaadmn +0x3b20 = saAdminSrvrCommand::HandleRequest() +0xf0
-------------------------------------------------------------------------------------


Pilot environment is compose of : (win2k SP3)
    2xweb servers
    1xResonate scheduler
    2xEbusiness App Servers


We have attached for both crashes
- component log file
- crash file


Please help.
Regards

Solution

Message 1

For the benefit of other users:

When using the Server Admin screens through the web client siebsess.exe process was crashing from time to time producing the following call stack in the crash*.txt files:

- CALL STACK -
sslcsa +0x193ea = SS2KLogFileHeader::ReadHeader() +0x12a
sslcsa +0x1a35a = SS2KLogFileReader::StartReading() +0xda
sslcsa +0x1b525 = LogFileReader::OpenCurrFile() +0x95
sslcsa +0x1b00c = LogFileReader::ConstructNextValidFileName() +0x1bc
sslcsa +0x1b73d = LogFileReader::OpenNextFile() +0x4d
sslcsa +0x1b89c = LogFileReader::GetNextLine() +0x4c
sssaadmn +0x17e3f = saAdminSrvrCommand::ReadInfoLog() +0x4cf
sssaadmn +0x3b20 = saAdminSrvrCommand::HandleRequest() +0xf0
sssaadmn +0x1cd1 = saSISAdminSrvrSess::HandleCmd() +0x1f1
sssaadmn +0x13b7 = CompHandleMsg() +0xa7
siebsess +0x1dbd = wmain() +0xdbd
siebsess +0x18c5 = wmain() +0x8c5
siebsess +0x3ab1 = wmainCRTStartup() +0xe3

Change Request 12-IJL3WD has been raised to address this Product Defect. This crash happens when trying to open a log file which is 0 bytes in size.

When this crash happens, it does not affect all users on the Object Manager it only affects the one user that tried to open the 0 byte log file i.e. 1 session. The entire UI doesn't fail the user will just see the following message on screen:

"We detected an Error which may have occurred for one or more of the following reasons:

SBL-ADM-02049: There is no connected server targeted for that command"

Cont...

Message 2

Cont...

Possible work arounds:

1) To recover from the above error the user needs to logout then log back in and navigate back to the server admin screens.
2) Alternatively the log files can always be viewed through Windows Explorer.

Siebel Technical Support

Applies to:

Siebel System Software - Version: 7.5.2.100 [15252] to 8.1.1.1 SIA [21211] - Release: V7 to V8
Generic UNIX
Generic Linux
Product Release: V7 (Enterprise)
Version: 7.5.2.100 [15252]
Database: IBM DB2 8.1 FixPack 6b
Application Server OS: IBM AIX 5L 5.1
Database Server OS: IBM AIX 5L 5.1

This document was previously published as Siebel SR 38-3078571521.

Symptoms

SBL-GEN-00255, SBL-OSD-00220, SBL-OSD-02006, SBL-OSD-02011, SBL-OSD-00204, SBL-ADM-02049, SBL-GEN-00001, OSDmprotect

The Siebel Server was running fine until a few weeks ago. Now we are unable to start the Siebel Server. The Siebel Gateway Name Server is running fine.

When we start the Siebel Server by using start_server all command, the main thread starts (siebsrvr) but when it spawns the child threads (siebmtsh), they are not staying alive.

No Siebel multithreaded server processes are started after running start_server all and no Application Object Manager log files are being generated.

The SiebSrvr.log under siebsrvr/log directory may contain the following error:

    SBL-OSD-00220: Internal: pthread_mutex_trylock () failed with error. (22)

In some situations the following error may also be seen:

   OSDmprotect: mprotect(0xf7400000, 0, 0x00000001) failed with error 22 

In addition to SBL-OSD-00220 error messages in SiebSrvr.log log file, error messages like the following are being logged in the Enterprise Server log file (<enterprise_name>.<server_name>.log) under $SIEBEL_ROOT/enterprises/<enterprise_name>/<server_name>/log directory:

<NoCompName> 64527 SBL-GEN-00002 Process exited with error - Error code SBL-GEN-00002

Changes

 

Cause

A) This situation has been reported when the Unix machine has been shutdown without having run the stop_server script. The stop_server script should remove the osdf.<enterprise_name>.<server_name> file that resides in the $SIEBEL_ROOT/siebsrvr/sys directory.

B) This situation has also been reported when the svc.siebsrvr.<enterprise_name>:<server_name> was duplicated under $SIEBEL_ROOT/siebsrvr/sys directory.

When you specify the ALL argument, the start_server script searches for all files under $SIEBEL_ROOT/siebsrvr/sys in the format svc.siebsrvr.* and parses it to identify the Enterprise name and the Server name.
The first string after svc.siebsrvr. is the Enterprise name and the second one is the Server name.
The start_server script skips all filenames ended with the .bak extension, because they are considered backup files.
Then it starts the service and creates the OSDF file based on these parsed names.

Customer has three svc* files on his system:

- $SIEBEL_ROOT/siebsrvr/sys/svc.siebsrvr.<enterprise_name>:<server_name>
- $SIEBEL_ROOT/siebsrvr/sys/svc.siebsrvr.<enterprise_name>:<server_name>.bak
- $SIEBEL_ROOT/siebsrvr/sys/svc.siebsrvr.<enterprise_name>:<server_name>.OLD1

The second file is considered as a backup file by start_server script.
However, the other two files are used by start_server to start up the Siebel Server, and both point to the same Enterprise and Server names.
Therefore, the start_server script is starting the same Siebel Server twice.

The problem is that, when the second instance is started, the OSDF file is overwritten, and the information used by Siebel about the memory structures used by the first instance is lost. The second instance will conflict with the first one, and the processes end up failing.

Solution

In order to fix this behavior and guarantee you have a clean environment, please do the following:

1. Shutdown the Siebel Server and run the following commands to clean all structures that may remain:

    % stop_server ALL
    % reset_server -e <enterprise_name> <server_name>
    % siebclean -f $SIEBEL_ROOT/siebsrvr/admin/<enterprise_name>.<server_name>.shm -q
    % cleansync -f $SIEBEL_ROOT/siebsrvr/sys/osdf.<enterprise_name>.<server_name> -d
    % siebctl -r $SIEBEL_ROOT -S siebsrvr -i <enterprise_name>:<server_name> -k -q
    % mwcleanup -silent 2>/dev/null

2. If using AIX, log into UNIX as root and run the following command:

    % /usr/sbin/slibclean

3. Ensure no Siebel processes are running and check that there are no semaphores or shared memory segments allocated for the UNIX user who owns the Siebel Server installation:

    % ps -ef | grep <username>
    % ipcs -b

4. If there are any processes, shared memory segments or semaphores stuck in memory, they can be killed by using the following commands, respectively:

    % kill -9 <process_ID>
    % ipcrm -m <shared_memory_segment_ID>
    % ipcrm -s <semaphore_ID>

5. Remove the following files if they still exist:

    $SIEBEL_ROOT/siebsrvr/sys/osdf.<enterprise_name>.<server_name>
    $SIEBEL_ROOT/siebsrvr/admin/<enterprise_name>.<server_name>.shm

6. Remove all svc* files or move all of them out from $SIEBEL_ROOT/siebsrvr/sys directory.

7. Recreate the correct svc* file:

    % siebctl -S siebsrvr -i "<enterprise_name>:<server_name>" -a -g "-g <gateway_name> -e <enterprise_name> -s <server_name>"

8. Restart the Siebel Server:

    % start_server all

Customers should note that if there are still any processes, semaphores or shared memory segments stuck in memory, the machine will need to be rebooted before recreating the svc* file (between steps 6 and 7).

Customers should also note that recreating the svc* file (steps 6 and 7) is not necessary in all situations, and in most cases step 1 only is sufficient to guarantee a clean startup.

KEYWORDS: start_server all, failure to start Siebel on Unix server,  OSDmprotect, err=1300220 sys=22 sys=0 SBL-GEN-00001 SBL-GEN-00002 SBL-GEN-00003 SBL-GEN-00004 SBL-GEN-00005 SBL-GEN-00006 SBL-GEN-00007 pthread_mutex_trylock AIX slibclean ipcrm

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3.16 [16284] ESN
Database: Oracle 9.2.0.5
Application Server OS: IBM AIX 5L 5.2
Database Server OS: IBM AIX 5L 5.3

This document was previously published as Siebel SR 38-3442227811.

Symptoms

SBL-ESC-00054, SBL-SVR-01074, SBL-SMI-01000, SBL-SRB-00051, SBL-GEN-09103

Hi support

We upgraded our Siebel systems to 7.5.3.16 a month ago. Everythisg worked fine until we modified asignement rules in application.
Due to holidays periods, administrator had to remove/add users . After these operations were done, and new rules released, Aignment failed first time it tried to assign one SR to new user, and it is neccesary to stop and re-start component.
We didn't see These behaviour in 7.5.3.15.

We attach yo assignment logs; twice times when it became not available.

Regards    

Solution

Message 1

For the benefit of other readers, after applying 7.5.3.16 patch on AIX, it was found that the Assignment Manager server (AsgnSrvr) component became assumed a status pf “unavailable”.

The following error was repeatedly reported in the Srvrmgr.logowing error:

“srvrmgr 25746 1 /vol1/siebel/dmessias/sia75316/siebsrvr/log/srvrmgr.log 7.5.3.16
[16284] ENU
GenericLog      GenericError    1       2007-10-17 11:58:59     (sacmd.cpp 10(44
0) err=902055 sys=902058) SBL-ADM-02055: Error from server "(null)"
GenericLog      GenericError    1       2007-10-17 11:58:59     (sacmdl.cpp 29(6
71) err=902055 sys=0) SBL-ADM-02055: Error from server "(null)"
GenericLog      GenericError    1       2007-10-17 12:09:09     (sacmd.cpp 10(38
8) err=902049 sys=0) SBL-ADM-02049: There is no connected server targeted for th
at command”

The behaviour was reproducible on 7.5.3.16 ENU on AIX but not on Windows.

A new Change Request -12-1LO0K79 has been raised to report this behaviour as a defect.