Search This Blog

SBL-EAI-04307: No ports were initialized for Web Service named '%1' having namespace value '%2'.

Applies to:
Siebel System Software - Version: 7.5.2 SIA [15051] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (MidMarket)
Version: 7.5.3.11 [16199] MME
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: Microsoft Windows 2000 Advanced Server SP 4

This document was previously published as Siebel SR 38-2010810421.
***Checked for relevance on 11-NOV-2010***
Symptoms
When clicking on GenerateWSDL button in site map->administration-web services-> inbound web services screen the following error was observed:


ObjMgrLog Error 4 2005-05-26 10:32:17 (SBL-EAI-04307) No ports were initialized for Web Service named 'UHC SEP WS Test' having namespace value 'http://'.


Cause
The root cause of the error is the custom business service for the web services is created in the client in Business Service Administration
Solution

The GenerateWSDL button works successful after recreating the business service in Siebel Tools, recompile client .srf, copy .srf to the server side, and create a new Inbound Web Service in Web Services Administration > Inbound Web Services.

The business service in Siebel Tools has Class = CSSService.
This actually works fine for GenerateWSDL, it doesn't require Class = CSSEAIDataSyncService.

The Documentation Enhancement CR# 10498241 has been raised to have it documented in EAI Guide:
In order to generate a WSDL, Business Service should be created using Siebel Tools and not in Clent.


References
BUG:10498241 - IN ORDER TO GENERATE A WSDL , BUSINESS SERVICE SHOULD BE CREATED USING TOOLS AND NOT IN CLENT.









Applies to:
Siebel Reports - Version: 8.1.1 [21112] and later [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms
When running a report the XMLPReportServer log file may show the following error messages :


ObjMgrLog Error 1 000000024a1a1d34:0 2009-05-25 07:18:38 (factory.cpp (229)) SBL-EAI-04319: Active Workflow Process named 'SelfServicePostLogin' cannot be found in runtime database 'ServerDataSrc'.
ObjMgrLog Error 1 000000024a1a1d34:0 2009-05-25 07:18:38 (wservice.cpp (140)) SBL-EAI-04307: No ports were initialized for Web Service named 'SelfServicePostLogin' having namespace value 'http://siebel.com/SelfService/Common/Login'.
ObjMgrLog Error 1 000000024a1a1d34:0 2009-05-25 07:18:41 (factory.cpp (181)) SBL-EAI-04299: Business Service 'UserBSTest' does not exist.
ObjMgrLog Error 1 000000024a1a1d34:0 2009-05-25 07:18:41 (wservice.cpp (140)) SBL-EAI-04307: No ports were initialized for Web Service named 'UserBSTest' having namespace value 'http://siebel.com/CustomUI'.

Solution

The error message concerning the workflow SelfServicePostLogin comes up because the status of this workflow is “In Progress” in Siebel Tools.

In order to resolve the behavior perform a query for this workflow in Siebel Tools and then Publish/Activate this object. There is a Publish/Activate button in Siebel Tools if View -> Toolbars -> “WF/Task Editor Toolbar” is enabled.

After the Siebel Server has been restarted the error message should no longer appear in the XMLPReportServer log file.

Business Service UserBSTest is missing in the repository. Change Request #12-1THO6N2 has been logged to address this behavior in a future version.
References
BUG:10567889 - USERBSTEST MISSING ERROR IN LOG FILE












Applies to:
Siebel Call Center - Version: 8.1.1 SIA [21111] to 8.1.1 SIA [21111] - Release: V8 to V8
Information in this document applies to any platform.
***Checked for relevance on 11-Feb-2010***
Symptoms
When attempting to deploy a Workflow Process as a web service (from Siebel Tools), and generate the wsdl, the following errors were reported :-

SBL-BPR-00158: Cannot execute workflow process definition 'UCM My Customer Profile'.

SBL-EAI-04307: No ports were initialized for Web Service named 'UCM My Customer Profile' having namespace value 'http://siebel.com/CustomUI'.

SBL-EAI-50162: WSDL cannot be generated for web service 'UCM My Customer Profile'. The Workflow Process 'UCM My Customer Profile' may not be activated and caused the WSDL generation to fail.
Cause
During the deployment of the Workflow Process as a web service, SQL was generated to check the deployment definition, for example :-

SELECT
T1.CONFLICT_ID,
...
FROM
SIEBEL.S_WFA_DPLOY_DEF T1
WHERE
(T1.TYPE_CD IN ( 'PROCESS' )) AND
(T1.NAME = 'UCM My Customer Profile' AND T1.DEPLOY_STATUS_CD IN ( 'ACTIVE' ) AND (T1.EFF_START_TS < CONVERT(TIMESTAMP, '07/23/2008 05:55:44') OR T1.EFF_START_TS IS NULL) AND (T1.EFF_END_TS > CONVERT(TIMESTAMP, '07/23/2008 05:55:44') OR T1.EFF_END_TS IS NULL))
ORDER BY
T1.VERSION DESC

If this did not find a row, the generation of the wsdl would fail. In the customer environment, the SQL returned 0 rows.

Solution
Remove the Expiration Date/Time from the Workflow Process in the Admin - Business Processes > Workflow Deployment > Active Workflow Processes view.

Re-deploy the Workflow Process as a web service from Siebel Tools.

Change request Bug 10547166 has been logged to request that when a new Workflow Process is revised from a version where the Effective End Date is set, that the end date is nulled.











Applies to:
Siebel CRM - Version: 8.1.1.3 SIA[21219] and later [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

Issue :-
-------------
An error occurs while invoking inbound WS :-

Error :-
-----
ObjMgrLog Error 1 0000011c4ca816b0:0 2010-10-03 19:27:36 (oracon.cpp
(3246)) SBL-DBC-00105: An error has occurred executing a Sql statement.
...
ObjMgrLog Error 1 0000011c4ca816b0:0 2010-10-03 19:27:36 (wservice.cpp (140)) SBL-EAI-04307: No ports were initialized for Web Service named 'Account' having namespace value 'http://siebel.com/marketing/account'.



Cause

thei issue was related to the diccache.dat:
---------------------------------------------------
error SBL-DAT-60237: Error loading dictionary file diccache.dat

Solution

Removing diccache.dat and restarting the siebel server has resolved the issue.

Thank you
Technical Support

No comments:

Post a Comment