siebel

Applies to: Siebel System Software - Version: 7.7.1 [18306] and later   [Release: V7 and later ] z*OBSOLETE: Microsoft Windows 2000 Product Release: V7 (Enterprise) Version: 7.7.1 [18306] Database: Oracle 9.2.0.4 Application Server OS: Microsoft Windows 2000 Server SP 4 Database Server OS: Sun Solaris 8 This document was previously published as Siebel SR 38-1448826294. Symptoms SBL-NET-01218Hi,      Have managed to change DSConnectString from "SiebSrvr_css77hkes" to "siebel" but still not working until I went to update the passwords again for both sadmin and siebel from the Administration screen. Now all the services are running from GUI. Refer to attachment. captured by using delicated web client. 20040816screen.doc      However, I still can't login via web client.(http://[Server Name]/fins_enu) It gives me the familiar 'sys busy message'. Refer to 20040816screen.doc       a) I ha...

Applies to: Siebel CRM - Version: 8.1.1 [21112] to 8.1.1 [21112] - Release: V8 to V8 Information in this document applies to any platform. Symptoms Customer reported the following: In our new Siebel TEST environment, 2 Application Servers failing with Handshake failed error. This is newly built Siebel environment, we have multiple servers Ntsydasu304 - gateway and app server Ntsydasu303 - App Server Ntsydasu1186 - App Server Ntsydwbu117 - Web Server The Siebel gateway is up and running, all the application servers are started. But 2 application servers Ntsydasu304 and Ntsydasu1186 are failing with handshake Failed error Cause The issue seems to be caused by either port number being used by other non Siebel process, or the mapping between the hostname of the servers and the IP addresses. This analysis was based on the fact that when srvrmgr tried to communicate with the ServerMgr, it threw errors below: - Handshake(siebel://ntsydasu1186:49162/es_obfstsb1/servermgr/ntsydasu1186) on conn ...

Applies to: Siebel Finance Sales - Version: 8.1 SIA [21039] and later   [Release: V8 and later ] Information in this document applies to any platform. Symptoms The customer upgraded their application from 8.0.0.5 to 8.0.0.9 and experienced the following issues: a) The OM (Object Manager) stopped responding from time to time. b) All the logged in users were kicked out and no user could login thereafter. The server busy error message was encountered and the workaround was to restart the OM. There were no exact sequence of steps to reproduce this issue. The error was intermittent and was happening occasionally and whenever it happened, it kicked out users and then no user could login. The OM logs showed the following error: SBL-NET-01034: The SISNAPI connection was closed by the peer Cause The customer was using Message Broadcast feature in their environment and the issue was caused because of the incorrect parameter setting. The problem was caused by the parameter "Appli...

Applies to: Error Message Area:Networking Layer - NET Version:Siebel 7.5.3 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-NET-01023: Peer disconnected Scope This document is informational and intended for any user. SBL-NET-01023: Peer disconnected Explanation The server has closed the network connection. Below is a list of common causes for the error message: 1. The Web Server's Network cards did not have a Default Gateway Server IP Address configured correctly. 2. The 3rd party network connectivity software installed on the Siebel server machine (for example Oracle's SQL*Net software and Resonate), was not installed correctly. Additionally, the customer was encountering a "Handshake Failed" error when trying to access the Server Administration screens and one of the Siebel Object Managers had crashed and produced a call stack. 3. Resonate is used for load balancing and the customer is using a Net...