Search This Blog

SBL-SVR-01051

Applies to:

Siebel Handheld - Version 7.5.3.9 PDA [16194_2] to 8.2.2.3 SIA [23021] [Release V7 to V8]
Microsoft Windows CE
Product Release: V7 (Enterprise)
Version: 7.7.0.1 [AN307]
Database: Oracle 9i
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Sun Solaris 9

This document was previously published as Siebel SR 38-1719219591.
***Checked for relevance on 27-Mar-2013***

Symptoms

SBL-SVR-01051, SBL-NET-01218
We are experiencing problems syncronising our Siebel Handheld devices with the Server using DSS. It has worked in the past, but since the server went down during a sync, we can't get it to work again.

We continue to get these error, taken from the log on the HH device.

SYSTEM    0xd290894e    01/17/2005 10:00:40    Loading Metadata.
ERROR    0xd290894e    01/17/2005 10:00:40    0x7766: Failed to load configuration. Metadata file is absent or invalid. Siebel Handheld Sync will be launched now.
SYSTEM    0xB3605DE2    01/17/2005 10:00:41    Initializing SyncClient.
SYSTEM    0xd290894e    01/17/2005 10:00:41    Terminating Siebel application.
ERROR    0xD2BB26E6    01/17/2005 10:01:13    0x65aa: Server returned NOTOK
ERROR    0xD2BB26E6    01/17/2005 10:01:13    Server returned NOTOK
ERROR    0xD2BB26E6    01/17/2005 10:01:13    The server may be busy. Please try again later. Contact your administrator if the problem persists.
ERROR    0xD2BB26E6    01/17/2005 10:01:13    Fatal Error, Shutting Down Session
SYSTEM    0xB3605DE2    01/17/2005 10:01:26    Exiting SyncClient.

Any ideas what may be causing this. We thought that it may still have an active sync task running, but we have started and stopped the server and it still conitnues to error out.

Many Thanks

Andy

Cause

As cause was identified the entry for the handheld application in eapps_sia.cfg file. All sections for handheld applications require the additional line 'EnableExtServiceOnly = TRUE'. The standard eapps*.cfg files do contain this line.

Solution

Message 1

For the benefit of other users:

The object manager log file showed following errors a couple of times:
SBL-NET-01218: The connection was refused by server gal-rtw-app-16. No component is listening on port 49160.
SBL-SVR-01051: SISNAPI connection is refused by the Siebel server: (null)

As cause was identified the entry for the handheld application in eapps_sia.cfg file. All sections for handheld applications require the additional line 'EnableExtServiceOnly = TRUE'. The standard eapps*.cfg files do contain this line. In the case here for some reason this line was missing. After correcting this the handheld synchronization worked properly.




Applies to:

Siebel System Software - Version: 7.5.3 [16157] and later   [Release: V7 and later ]
Information in this document applies to any platform.
Error Message Area:Server Common Layers - SVR
Version:Siebel 7.5.3

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-SVR-01051: SISNAPI connection refused, the server could be down: %1

Scope

This document is informational and intended for any user.

SBL-SVR-01051: SISNAPI connection refused, the server could be down: %1

Explanation

Cannot connect to the Siebel Server machine to start a process. The Siebel Server machine might not be available over the network or the Siebel Server process may not be started. The details of the error from the SISNAPI layer replaces the %1 in the error message.

Corrective Action

Make sure the Siebel Server machine is up and running and that the Siebel Server process is running.









Applies to:

Product Release: V7 (Enterprise)
Version: 7.7.1 [18306]
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Server
Database Server OS: Sun Solaris 8

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

Symptoms

SBL-SVR-01051, SBL-SMI-00049, SBL-NET-01218Hi Support,

We have created new Object Managers for PRM Portal (for 8 different languages). As part of this, we have created new virtual directories, new components, new entries in the eapps.cfg. And finally, we synchronized the components.

But, when we try to access the new OM, it says 'Page can not be displayed'.

For example, we created new OM: echannelObjMgr_enu_eidm and when we access it through:

http://hostname/prmportal_enu_eidm we get a 'Page can not be displayed' message.

We see that the URL gets re-directed to homepage like:

http://hostname/prmportal_enu_eidm/start.swe?SWECmd=Start&SWEHo=hostname

I think the OM is not responding to the request that has passed through SWSE.

Please let us know your ideas on this.

Thanks,
Jagadeesh

Solution

Message 1

For the benefit of other user:

The customer has created new Object Managers for PRM Portal (for 8 different languages). As part of this, he has created new virtual directories, new components, and new entries in the eapps.cfg. And finally, he synchronized the batch server components.

But, when he tried to access the new Object Manager, it says "Page can not be displayed".

The problem has been resolved after the customer modified the web server (IIS) parameters as follows:
1. Open IIS (Start menu --> Program Files--> Administrative Tools--> Internet Services Manager)
2. Expand default web site
3. Choose Virtual directory created (for the custom component) and right click and go to Properties
4. In Virtual directory tab, choose Configuration button. Click that
5. You get another pop up- choose tab - App mappings. Highlight .swe and click on edit
6. Another pop up opens - At the bottom, there is a check box - "Check that file exists"
7. Uncheck the check box
8. Repeat this for .swef

Documentation Enhancement request 12-QAWCBM (Update the "Creating a New Virtual Directory" section from Siebel Installation Guide for MS Windows) was logged to address this matter.



Applies to:

Siebel CRM - Version: 7.5.3 [100] to 8.1.1.7 [21238] - Release: V7 to V8
Information in this document applies to any platform.
Product Release: V7 (Professional)

Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: Microsoft Windows 2000 Server SP 4

Symptoms

It was reported that there were problems using drag drop functionality in the Siebel application. When the user was trying to save an attached document, the system was displaying the following error message:
Session Warning: The server you are trying to access is either busy or experiencing difficulties. Please close the Web browser, open a new browser window, and try logging in again.
After this error, the user is usually logged out of the application.

The issue was only present in the thin client and could not be reproduced in the dedicated client.
The same error was observed in the thin client using both DB authentication and ADSI authentication.

The following messages were displayed in the SWE logs:
ProcessPluginRequest    ProcessPluginRequestError    1    0    2006-04-18 17:15:22     5116: [SWSE] RPC coming in without a user session

ProcessPluginRequest    ProcessPluginRequestError    1    0    2006-04-18 17:15:22     5116: [SWSE] Failed to obtain a session ID. NOT OK

ProcessPluginRequest    ProcessPluginRequestError    1    0    2006-04-18 17:15:22     5116: [SWSE] Set Error Response (Session: Error: 00065535 Message: NOT OK)


The following error messages may also be seen for the end user or in the logs related to this issue:
SBL-UIF-00401, SBL-SCR-00141, SBL-DAT-00215, SBL-DAT-00712, SBL-SVR-01051, SBL-SCM-00022, SBL-SMI-00033, SBL-NET-01023, SBL-BPR-00125, SBL-BPR-00151

Cause

The cause of this issue was determined to be an underscore "_" character in the naming of the servers.

Solution

The workaround for this issue is to use the IP address of the server instead of the server name.

Document 477993.1  has additional information regarding problems using a dash/hyphen in the Siebel Server Name.
Document 477993.1 was previously referred to as Alert 1067.




Applies to:

Siebel Financial Services Call Center - Version: 7.7.2.10 SIA [18385] and later   [Release: V7 and later ]
Information in this document applies to any platform.

Symptoms


Web client not working after migration with CUSTOM srf. It works fine with STANDARD srf.

 OM logs were misleading indicating following errors:
2010-02-01 13:58:57 4848: [TCPIP-client] connect() to drlmrsie07p:49164 failed (err=10061 | Connection refused.)

2010-02-01 13:58:57 (srmconn.cpp (905) err=1801218 sys=49164) SBL-NET-01218: The connection was refused by server drlmrsie07p. No component is listening on port 49164.


2010-02-01 13:58:57 (srmconn.cpp (905) err=2001051 sys=126) SBL-SVR-01051: SISNAPI connection is refused by the Siebel server: (null)

Changes

Customer was  in the process of building a Siebel disaster recovery (DR) environment, which mimics their production environment.  They built the environment from a fresh installation of Siebel. The vanilla Siebel web client worked perfect, however, after doing a database refresh from production, as well as repository migration (including repository import, copying over SRF, bscript, image and CSS files from production), the web client stopped working.

Cause


Custom srf was failing because Firstlogic was not installed

Solution


Installed Firstlogic and web client started working with custom srf. 

 

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)