SBL-ADM-01050: The specified component is not active on this server

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3.4 [16180]
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: HP-UX 10.0

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

Symptoms

SBL-ADM-01050

I tried to perform a Generate New Database task and it stays in a queue. Also I could not find a log file (GenNewDb*.log) in the /<Siebel_server>/bin/ directory.

Please advise.

Solution

Message 1

For the benefit of other users:

Customer tried to perform a Generate New Database task using GUI but it stayed in a queue. Also they could not find a log file (GenNewDb*.log) in the /<Siebel_server>/bin/ directory. Then they tried to perform Generate New Database task using command line also without success.

We checked the System Preferences view and made sure parameter Docking:Transaction Logging is set to True. Also we checked and confirmed that Enterprise Component Group Siebel Remote is “Enabled”. Also from Component Group Assignment, we noticed that Siebel Remote is Enabled and Assigned for correct Server. It showed server correctly and all relevant fields had ticks (check marks). Siebel Remote is ‘Assigned to’, ‘Enabled?’, ‘Enabled for Enterprise?’ and ‘Enabled on Server’ all had ticks for the correct server.

We increased tracing and tried again using server manager command line and then they received following error.

"SBL-ADM-01050: The specified component is not active on this server".

They did batch synchronize, restarted Siebel Server and tried again but still it stayed in a queue. We checked the siebns.dat file also but all seemed to be in order.

After further investigation it appeared that the behaviour is due to some unknown problem with their environment. The behaviour was resolved with following actions.

1. Please un-assign/assign the component group ‘Siebel Remote’ from the relevant Siebel Server.

<Ctd>....

Message 2

<Ctd>

1. Please un-assign/assign the component group ‘Siebel Remote’ from the relevant Siebel Server.

To un-assign a component group from a Siebel Server do the following.

- Navigate to the Enterprise Operations screen.

- Click the Component Group Assignment view tab.

-In the Enterprise Component Groups list, select the component group you want to un-assign (which is Siebel Remote).

-In the Component Group Assignment list, select the correct Siebel Server from which you want to un-assign the component group.

- Click ‘Unassign’.

- The ‘Assigned To’ field no longer has a check mark in it now.

- For the change to take effect, stop and restart the Siebel Server System Service. (For information on how to stop and start the Siebel Server System Service, see Administering the Siebel Server System Service).

2. Now assign the component group to the Siebel Server as follows:

-Navigate to the Enterprise Operations screen.

-Click the Component Group Assignment view tab.

-In the Enterprise Component Groups list, select the component group Siebel Remote.

-In the Component Group Assignment list, select the relevant Siebel Server
-Click Assign.

- The ‘Assigned To’ field now has a check mark in it.

- For the change to take effect, stop and restart the Siebel Server System Service.

- Now try to perform a GenNewDB from GUI (if GUI does not work please try from server manager command line utility also).

The behaviour was ....<Ctd>..

Message 3

...<Ctd>

The behaviour was resolved after above actions and customer was able to perform Generate New Database task after that successfully.

Keywords: Generate New Database, SBL-ADM-01050, Component Group Assignment.

Thank you.

Applies to:

Siebel System Software - Version: 7.7.2.3 SIA [18361] to 8.1.1.2[21215] - Release: V7 to V8
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.7.2.3 [18361] DEU Fin Svcs
Database: Oracle 9.2.0.6
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-3034125971.

***Checked for relevance on 08-Dec-2010***

Symptoms

Hello there,

I am creating a server component using srvrmgr and have problem. This is what I tried:
1. login srvrmgr:
srvrmgr /g gateway:2327 /e epserver /u username /p password
2. create compdef:
create compdef MqSeriesAMIRcvr2 for comptype EAIRcvr compgrp EAI run mode background full name MqSeriesAMIRcvr2 desc "Customer-created AMI Receiver"
3. enable and list
enable compdef MqSeriesAMIRcvr2
enable compdef MqSeriesAMIRcvr2 for server siebserver
list compdef MqSeriesAMIRcvr2
-- CC_DISP_ENABLE_ST is Active
4. reconfig:
reconfig compdef MqSeriesAMIRcvr2
5. change param:
change parameter ReceiverMethodName="ReceiveDispatch" for component definition MqSeriesAMIRcvr2

all steps are carried out successifully, except step 5, with error message:
SBL-ADM-01050: Die angegebene Komponente ist auf diesem Server nicht aktiv

Please help - what is wrong?

Regards

Cause

Incorrect steps

Solution

For the benefits of other users:

Customer trying to create and enable the component through server manager command, and immediately after that tried to change one of the parameter of the component and it failed with error “"SBL-ADM-01050: The specified component is not active on this server".

Solution:

It’s recommended that customer should restart Siebel Server for any newly created and enabled component before changing the parameter setting or using the component.

After recreate the component again and restart Siebel Server before performing step 4 (reconfig compdef...), parameter changes command works fine.

Thank you,
Siebel Technical Support

Applies to:

Siebel System Software - Version: 7.0.4 [14068] - Release: V7
Information in this document applies to any platform.
Area(s):System Administration
Release(s):V7 (MidMarket), V7 (Enterprise)
Database(s):All Supported Databases
App Server OS(s):All Supported Platforms
Latest release tested against:V7 (Enterprise)
Keywords:Offline, srvrmgr, component definition, compdef, workflow, disappear, missing, lost, gone

This document was previously published as Siebel Alert 739.

Description

When working within the Server Administration screens, some Server Components which are known to have been enabled are not listed on the screen.

 

There are two behaviors that could account for situations under which components that have been enabled within a Siebel Enterprise may not appear within the Server Administration screens:

 

1. The component has been taken offline on a Siebel server, which causes the component definition to become disabled.

 

2. An attempt has been made to enable an already enabled component using the srvrmgr command line utility. When you enable the component, this sets the enabled state to disabled.

 

Bug 12-FYR3Q2 has been logged to address a product defect with taking a component offline. This change request has been fixed in Siebel version 7.7.

 

Bug 12-FYM1QK has been logged to address a product defect of enabling a component that is already enabled. This change request has been fixed in Siebel version 7.7.

Likelihood of Occurrence

If you take a component offline or you try to enable an already enabled component, you may encounter these behaviors:

 

1. The Component has been taken offline on a Siebel server.

 

If the Siebel Administrator uses the Offline button on the Site Map > Server Administration > Servers > Server Components view to take a component offline, the component will not appear within the Server Administration views once the Siebel server service has been shutdown and restarted.

 

2. An attempt has been made to enable an already enabled component using the srvrmgr command-line tool.

 

If the Siebel Administrator uses the srvrmgr command-line tool to enable a component which is already enabled on the Siebel server, the component will not appear within the Server Administration views once the Siebel server service has been restarted.

 

In this particular case, the following srvrmgr command was issued:

 

SIEBEL_HOME\siebsrvr\bin\srvrmgr> enable component <component name>

Possible Symptoms

If you see any of these errors or symptoms documented below, you may have encountered the behaviors documented in this Alert:

 

• SBL-ADM-04013: Component is already enabled

 

• SBL-ADM-01050: The specified component is not active on this server

 

• SBL-SRB-00047: (null) with key [(null)] is not available

 

• While trying to assign a record using the Assign button in the Siebel Client, in other words, running Interactive Assignment, you encounter the errors:

 

[1] AsgnSrvr with key [(null)] is not available

[2] no current server

 

• In the Siebel Client, the component does not appear under the Site Map > Server Administration > Server > Server Components View. Another place to check is in the Site Map > Server Administration > Component Groups > Component Group Components view. In the top applet, the field called Number of Components will not match the number of components actually listed in the bottom applet.

 

• If the definition of the component within the Siebel Name Server Backing file is listed as disabled, the component will not appear within the various Server Administration views. The Siebel Name Server Backing file is called siebns.dat and is located in the SIEBEL_HOME\gtwysrvr\admin directory on the Windows platform and SIEBEL_ROOT/gtwysrvr/sys directory on the UNIX platform.

Workaround or Resolution

There are two workarounds you can try to resolve this behavior:

 

1. Log into the srvrmgr command-line utility and issue the following command for any affected components:

 

SIEBEL_HOME\siebsrvr\bin\srvrmgr> enable component definition <component name>

 

Shut down and restart the Siebel server in order to make sure the component is made available.

 

2. If the workaround above does not work, try the following:

 

1. Unassign the server component from the Siebel server.

 

2. Restart Siebel services.

 

3. Reassign the component again to the Siebel server.

 

This should make the component visible again.

 

Detailed instructions on the above steps can be found in Siebel Bookshelf version 7.5.3 > Siebel Server Administration Guide > Using the Siebel Server Manager GUI > Component Group and Server Component Administration > Administering Component Groups and Server Components.

 

If you apply Siebel Fix Pack version 7.5.3.7 or higher to resolve the change requests listed in this Alert, there are additional configuration instructions that you must perform in Siebel Tools. The steps are listed below:

 

1. Check out the Server Admin project.

 

2. Click on the Siebel Objects from the Object Explorer, and then click on Command. This lists all the commands under the Server Admin project. NOTE: If this object is not visible, go to the menu View > Option > Object Explorer tab, and select this object from the list to make it visible.

 

3. Create 2 new command objects using the information in the table below: NOTE: The properties for these new objects should be similar to the EnableComp (SWE) and DisableComp (SWE) command objects except for the properties listed in the table.

 

Name	Method
OnlineComp	OnlineComp
OfflineComp	OfflineComp

 

4. From the Applet object, query for the Server Server Services List applet. Expand the Control tab and create 2 new control objects for the OnlineComp and OfflineComp controls using the information in the table below. NOTE: The properties of these new controls should be similar to the EnableComp and DisableComp control objects except for the properties listed in the table:

 

Name	Caption	Method
OnlineComp	Online	OnlineComp
OfflineComp	Offline	OfflineComp

 

5. Expand the Applet Method Menu Item tab, and create 2 new objects for the OnlineComp and OfflineComp, respectively. Make sure the Command property is chosen from an existing list of commands that should include the new ones created previously in step 3.

 

Command	Menu Text	Position
OnlineComp	Online Component	5
OfflineComp	Offline Component	6

 

6. Expand the Applet Web Template tab under Applet. The Server Server Services List applet should have three templates: Base, Edit, Edit List.

 

7. Click on View object from the Object Explorer, and find the view Server Server/Service Instances View. This is the view that contains the applet Server Server Services List.

 

8. Expand the View tab from Object Explorer, expand View Web Template, and then View Template Item. Look in the list and find the applet Server Server Services List applet and check the Applet Mode property (most likely Edit List).

 

9. Go back to the Applet object, find the Server Server Services List applet, and expand the Applet Web Template.

 

10. Find the template that matches the template that you found in Step 8, right-click on the record, and choose Edit Web Layout.

 

11. Delete the old button controls labeled Online and Offline accordingly and add the new controls created in step 4 onto the applet.

 

12. Compile a new srf file and test the buttons and new menu items.

Maintenance Release Number

Please click on the links below to view the current status of the Change Requests and associated Fix Requests:

 

Bug 12-FYR3Q2

Bug 12-FYM1QK

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3.5 [16183] Life Sci
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: IBM AIX 5L 5.1

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

Symptoms

SBL-ADM-02527

I am setting up my production environment with a number of custom object managers.

To reduce the work and risk of error, as there is no tool allowing me to clone an existing CompDef, I am using the command-line Server Manager to create the new component definitions.

However, due to the large numer of parameters to initialize, it seems that I have reached a limit of about 900 characters on the size of the command to send. I am therefore unable to use a single command like the one below,

create compdef SeroCCObjMgr_enu for comptype AppObjMgr compgrp SeroCC run mode Interactive full name "Serono CC Object Manager (ENU)" desc "Serono Call Center Object Manager" with param aaa=bbb, ccc=ddd, ....

So I thought I would change the parameters after creating the compdef, but when I type

     change param aaa=bbb for compdef SeroCCObjMgr_enu

I get "SBL-ADM-01050: The specified component is not active on this server"

My question: is there a command that I can use to modify a parameter of a not-yet enabled component definition using the command line ?

Thank you,
Damien

Solution

Message 1

For the benefit of other readers,

To workaround the issue some parameters were rearranged (for example adding a space before the component group, moving a parameter at the end of the list). After the change the command works successful.

Change request 12-LPN5O4 has been filed to address the issue.