Validation for Transport â€å“serverã¢â‚¬â Failed Could Not Upload Test File Child Exited With Code 1

and later on   [Release: V8 and afterward ]
Data in this certificate applies to any platform.

Symptoms

When running a BI Publisher report from the Siebel web customer and having selected an output format for the report an mistake message is returned :
XMLP Report Generation fourth dimension exceeds the Threshold time.
If you so navigate into the Site Map > BIP Reports Server > My Reports and attempt to drilldown on the generated written report a dissimilar error is returned :

SBL-SVC-00155: No file has been attached to this record. Please attach a file.

Cause

Having increased the logging levels on the XMLP Study Server component, restarted information technology, and then re-tested the behavior it was axiomatic from a review of the log file that the timeout errors were occurring because the XMLP Report Server component was unable to connect to the BI Publisher Server within the Timeout period. Prove of this can be seen in the log file excerpt below :

EAITransport EAITransportDebug 4 000005fb4a6f30e4:0 2009-08-04 ten:01:59 *** HTTP Transport Parameters:
EAITransport EAITransportDebug 4 000005fb4a6f30e4:0 2009-08-04 10:01:59 Request URL = http://xx.xx.xx.xx:9704/xmlpserver/services/PublicReportService
EAITransport EAITransportDebug 4 000005fb4a6f30e4:0 2009-08-04 x:01:59 Asking Method = Mail
EAITransportPerf EAITransportPerf 5 000005fb4a6f30e4:0 2009-08-04 10:02:03 Created Request Connection|4617

EAITransport EAITransportGeneric three 000005fb4a6f30e4:0 2009-08-04 10:02:03 Dropped one-time connection and creating new connection for 'Request'
EAITransportPerf EAITransportPerf v 000005fb4a6f30e4:0 2009-08-04 10:02:03 Destroyed Asking Connexion|2

EAITransport EAITransportDebug 4 000005fb4a6f30e4:0 2009-08-04 10:02:03 *** HTTP Transport Parameters:
EAITransport EAITransportDebug 4 000005fb4a6f30e4:0 2009-08-04 10:02:03 Asking URL = http://twenty.xx.xx.xx:9704/xmlpserver/services/PublicReportService
EAITransport EAITransportDebug 4 000005fb4a6f30e4:0 2009-08-04 10:02:03 Request Method = Post
EAITransportPerf EAITransportPerf 5 000005fb4a6f30e4:0 2009-08-04 ten:02:03 Created Asking Connexion|6

EAITransport EAITransportGeneric three 000005fb4a6f30e4:0 2009-08-04 10:02:03 Sending Asking
EAITransport EAITransportDebug 4 000005fb4a6f30e4:0 2009-08-04 10:02:04 *** HTTP request Headers for Information Ship Request:
User-Agent: Mozilla/4.0
Accept: text/*
SOAPAction: ""
Content-Type: text/xml; charset=UTF-8

ObjMgrLog Fault 1 000005fb4a6f30e4:0 2009-08-04 ten:02:05 (httptransport.cpp (1631)) SBL-EAI-04115: Cannot connect to the server
ObjMgrBusServiceLog InvokeMethod 4 000005fb4a6f30e4:0 2009-08-04 x:02:05 Concern Service 'EAI HTTP Send' invoke method 'SendReceive' Execute Fourth dimension: 5.902 seconds.
ObjMgrBusServiceLog InvokeMethod 4 000005fb4a6f30e4:0 2009-08-04 10:02:05 End: Business Service 'EAI HTTP Transport' invoke method: 'SendReceive' at a231100
ObjMgrBusServiceLog InvokeMethod 4 000005fb4a6f30e4:0 2009-08-04 10:02:05 Business organization Service 'PublicReportService' invoke method 'runReport' Execute Time: 30.095 seconds.
ObjMgrBusServiceLog InvokeMethod 4 000005fb4a6f30e4:0 2009-08-04 x:02:05 Terminate: Business Service 'PublicReportService' invoke method: 'runReport' at a3e0270
ObjMgrBusServiceLog Delete four 000005fb4a6f30e4:0 2009-08-04 10:02:05 Business organization Service 'PublicReportService' (address: 'a3e0270')was unregsitered at model '12ff3c0' for session ''
ObjMgrBusServiceLog Delete 4 000005fb4a6f30e4:0 2009-08-04 10:02:05 Business Service 'PublicReportService' was deleted at a3e0270
ObjMgrBusServiceLog Error 1 000005fb4a6f30e4:0 2009-08-04 10:02:05 (xmlpadaptersvc.cpp (1378)) SBL-EAI-04115: Cannot connect to the server
XMLPReportLog XMLPReportError one 000005fb4a6f30e4:0 2009-08-04 10:02:05 Error in generating Report Output file /crm/app/siebel/product/8.ane.i.0/siebsrvr/xmlp/reports/Account List1-6BGX.PDF in the XMLP Engine
ObjMgrBusServiceLog Mistake 1 000005fb4a6f30e4:0 2009-08-04 10:02:05 (xmlpadaptersvc.cpp (1696)) SBL-RPT-50524: BI Publisher engine failed to generate study.
ObjMgrBusServiceLog InvokeMethod iv 000005fb4a6f30e4:0 2009-08-04 10:02:05 Business Service 'XMLP Adapter Service' invoke method 'RunBIPReport' Execute Time: 30.161 seconds.

The following additional mistake message may too be reported in some scenarios :

ObjMgrLog Error 1 000022d94c891d18:0 2010-09-10 09:22:59 (httptransport.cpp (1631)) SBL-EAI-04116: HTTP Internet Exception during 'Information Ship': 'The connection with the server was reset
', lawmaking: '12031'

Solution

Equally the connectivity to the BI Publisher Server had previously been tested and confirmed every bit working correctly it was recommended to add some boosted lawmaking to ensure that the concluding connection had been cleaned upwards correctly.
The following actions were performed :
1. In Siebel Tools modify the vanilla 'EAI HTTP Transport' business service.
two. Right click on the proper noun of the business service and select 'Edit Server Scripts'.
3. Copy paste the following script in the 'PreInvokeMethod' upshot:

function Service_PreInvokeMethod (MethodName, Inputs, Outputs)
{
  if (MethodName == "SendReceive" || MethodName == "Ship")
  {
    Inputs.SetProperty("HDR.Connection","close");
  }
  return (ContinueOperation);
}

4. Compile the modified concern service and deploy the SRF to your application server. If you have multiple Siebel Application servers and so deploy the SRF to all the servers.

v. Test running the BIP reports.
=============
The piece of lawmaking provided initiates a connection closure Before calling the 'SendReceive' method and in this way it ensures that at that place are no stale or dead connections. The lawmaking has been written in the 'PreInvokeMethod' method which therefore gets executed earlier the actual 'SendReceive method is called.
Some performance gains have been seen during report generation with the above lawmaking change in place.

Siebel System Software - Version: 7.0.4 [14068] and later [Release: V7 and later ]
Information in this document applies to whatsoever platform.
Area(south):ADM - App. Deployment Manager, Siebel EAI
Release(s):V7 (Enterprise), V7 (Professional person)
Database(south):All Supported Databases
App Server Os(s):All Supported Platforms
Latest release tested against:V7 (Enterprise)
Keywords:Application Deployment Manager, ADM, UDA, EMT

This document was previously published as Siebel Troubleshooting Steps 41.
PurposeHow To Troubleshoot Application Deployment Manager (ADM) in Siebel seven.vii.
Last Review Date05-Jan-2006
Instructions for the Reader A Troubleshooting Guide is provided to assist in debugging a specific consequence. When possible, diagnostic tools are included in the document to aid in troubleshooting.
Troubleshooting DetailsThe information presented in this document is intended to help troubleshoot ADM related problems and the near normally reported symptoms and error letters while running Application Deployment Managing director (ADM). ADM is a new feature in Siebel version seven.seven that helps Siebel administrators easily and quickly automate the migration of key reference information beyond different Siebel environments, such as betwixt a development and a test environment. This troubleshooting document is a supplement to Siebel Bookshelf version seven.7 > Going Alive with Siebel eBusiness Applications > Migrating Customizations Betwixt Applications .
Annotation: This document may not be fully applicable for Siebel version eight.x due to the new ADM architecture, for more data please review Siebel Awarding Deployment Manager Guide from version 8.10.

Contents

Troubleshooting Overview

Table 1 - Deployment Session Status Field Values

Table 2 - Component Events to Enable for ADM Troubleshooting

Effigy one - Location of Log Files for ADM errors

Table 3 - ADM Session Log.

Architecture

Figure 2 - Siebel Components and Objects Used in ADM

ADM Workflow Processes for Online Deployments

Figure iii - Workflow Process and Business Services Used for Online Deployment

ADM Business organization Services for File Deployments

Figure 4 - Business organization Services Used for File Deployment

Common ADM Error Messages

Tabular array 4 - Mutual ADM Error Messages and Symptoms

Figure 5 - Hierarchical LOV Deployment with LOVs of the Same LOV Type

Figure 6 - Hierarchical LOV Deployment with LOVs of Different LOV Type

Considering ADM is designed with standard Siebel Business application components and objects, many tools already exist for troubleshooting the individual Siebel components. The claiming is to understand how the components communicate with each other and the sequence of events. An understanding of the ADM architecture and workflow processes is disquisitional to successful isolating and resolving problems.
The general steps for troubleshooting are:
Troubleshooting Overview

Applies to:

1. Navigate to Site Map > Application Deployment Manager > Deployment Session View View and locate your ADM session’s status. The status will let y'all know if in that location is an error. See Tabular array 1 for an explanation of the session statuses and showtime steps.

2. Check the source and target systems for log files or error messages. The locations where logs tin be constitute are shown in Figure i. Log file locations for the Siebel server and a dedicated customer are shown. If you lot are performing an online deployment OR a file deployment continued to a thin client, the logs you want to examine volition exist on the Siebel server. If you are performing a file deployment on the dedicated client, the logs you want to examine volition be on the defended customer.

3. Once you have found the relevant log files, browse the component logs to observe the first signal of failure. Typical error messages for ADM are listed in this Troubleshooting guide.

4. If the logs do not incorporate any detail, enable the appropriate component events for each server component. Run into Table two for a list of the component events to enable and which components to enable them on.

5. If you lot identify the problem to be related to an integration object, business component rules or the EAI Siebel Adapter, so do farther testing using export files.

In one case you take resolved the problem, re-create your ADM session and deploy it once more.
Table i - Deployment Session Status Field Values

Status	Description	Diagnostic
New	This is a new deployment session.	Deployment session has not submitted however.
Submitted	This is a condition that you volition usually come across for HTTP deployments. This means information has been sent successfully sent from the source system to the target system.	On the Source organisation, you will run into the Submitted condition until the jobs consummate on the Target organisation. If the status never changes on the source system, bank check target system for queued or failed server requests (jobs). Typically these requests will exist in the WorkFlow Procedure Manager server component. To find the jobs, navigate to Site Map > Administration - Server Management > Jobs. On the target system, also make sure the Workflow component grouping is online, and you lot have synchronized the batch components.
Validation Failed	This status indicates that the source organization was unable to validate the environment details (see fault SBL-SVC-00232) or log into the target server.	Check the source organization log file in the $SIEBSRVR/temp/<session_id>.log for the underlying error message.
Deployment Failed	The deployment failed.	Check the source system log file in the $SIEBSRVR/temp/<session_id>.log for the underlying error message. If it was an online deployment, also check target organization for Workflow or EAI object manager logs for any errors.
Incomplete Deployment	Some items did not deploy successfully. Other items may have been deployed successfully.	Check the source system log file in the $SIEBSRVR/temp/<session_id>.log for the underlying error message. If it was an online deployment, also check target system for Workflow or EAI object manager logs for any errors.
Export Completed	This is a condition normally for file deployments. Information technology indicates a successful file export.	The ADM data was exported successfully from the source system. Check the specified file directory for the output file. this status does not betoken that data was imported into the target system. NOTE:
Deployment Completed	This condition indicates successful data migration from source to target.	The submitted deployment ran successfully on the target system, and an acknowledgement was successfully sent dorsum and received.

- Component Events to Enable for ADM Troubleshooting
Tabular array 2

Component Consequence Proper noun (Allonym)	Level	Description	Components*
ADM Event (ADM Event)	4	Captures events related to ADM, such every bit errors.	EAIObjMgr, WfProcMgr, the AOM
EAI Siebel Adapter (EAISiebAdpt)	4	Captures EAI Siebel Adapter related events, including integration component and integration component fields accessed, and the values for the fields; business concern components and business component fields accessed and the values for the fields.	WfProcMgr, the AOM
EAI Transport (EAITransport)	4	Captures EAI Send related events: including direction (send/receive) and result. For HTTP transport, shows headers and responses. For File Transport, shows the full filename.	EAIObjMgr, WfProcMgr, the AOM
Functioning Event (FSMPerformance)	4	Captures events related to the File Systems performance such as time taken to read or write to the file system, and the proper noun of file.	EAIObjMgr, WfProcMgr, the AOM
Event Context (EventContext)	4	Captures applet and method executed, view names, and screen names that the user navigates to.	the AOM
SrmBusSvc Condition (SRMBusSvc)	iii	Captures when the Server Requests business service submits a task.	EAIObjMgr, WfProcMgr, the AOM, SRProc, SRBroker
Server Requests Routing Info (SRMRouting)	iv	Captures Server Requests routing data, including SRB Session ID and component name.	EAIObjMgr, WfProcMgr, the AOM, SRProc, SRBroker
Object Manager SQL Log (ObjMgrSQLLog)	iv	Captures the SQL select, insert, update, and delete statements.	EAIObjMgr, WfProcMgr, the AOM
Session Manager (SessMgr)	3	Captures SISNAPI events related to the Siebel session managing director.	WfProcMgr, the AOM
Object Manager Business Service Operation and SetErrorMsg Log (ObjMgrBusServiceLog)	4	Captures Business Service-related events such equally when business services are created, deleted, and the methods invoked.	EAIObjMgr, WfProcMgr, the AOM
Object Manager Business Component Operation and SetErrorMsg Log (ObjMgrBusCompLog)	4	Captures Business organisation Component-related events: create and delete.	EAIObjMgr, WfProcMgr, the AOM
Workflow Engine Invoked (EngInv)	4	Captures when the workflow process engine is invoked.	EAIObjMgr, WfProcMgr
Workflow Process Execution (PrcExec)	4	Captures workflow process related events, and shows process properties values.	EAIObjMgr, WfProcMgr
Workflow Step Execution (StpExec)	4	Captures the process step events including business services invoked and inputs and outputs of the business services, weather evaluated, and outcome of the step.	EAIObjMgr, WfProcMgr
XML Conversion (XMLConversion)	4	Captures the conversion of XML documents to property sets steps and vice versa, shows encoding used in the certificate.	EAIObjMgr, WfProcMgr

* AOM refers to your application object manager. If you are connected through the Siebel Web Client, you are using an application object director, such as CallCenter (SSCObjMgr_enu).
You can enable more than events than those listed in Table 2. The events listed in Tabular array 2 are intended as a starting point for troubleshooting generic ADM issues. For more data about the component event infrastructure, refer to Siebel Bookshelf version seven.7 > System Monitoring and Diagnostics Guide for Siebel eBusiness Applications > Configuring Siebel Server and Component Logging > Configuring Siebel Server Component Logging .

Figure 1 - Location of Log Files for ADM errors

On the source arrangement, the ADM log file in the $SIEB_ROOT/temp directory often contains more information than you will see on the screen. The ADM Session will show a hyperlink to the log file. Even if you practise not see a file listed in the ADM Session, bank check the Siebel server temp directory for a file.
A sample log where a deployment failed and the reason it failed is shown below in Table 3. The filename will exist the name of the deployment session with a .log suffix.
Table 3

Line #	Text
1	[Deployment Session Header]
2	ADM Deployment Session: 42-4P84F
3	ADM Deployment Projection: testtest
iv	Beginning Fourth dimension: 08/01/2004 17:00:00
5	Target Web Address: http://myserver/eai_enu
6	Target User Name: SADMIN
7
eight	[Transaction: ProdFeature]
9	Condition: Data Training Completed
10	Session Items: UDA Admin Product Line, UDA Product Feature
11	End Time: 08/01/2004 17:00:07
12
13	[Transaction: ProdFeature]
14	Status: Import Failed
fifteen	End Time: 08/01/2004 17:00:17
16	EAI Logs:
17	No inserts are immune in Integration Component 'Admin Product Line_Internal Product'. (SBL-EAI-04184)

In the sample ADM Session log, y'all can see the name of the ADM project testtest in line 3, as well as the target server name myserver in line v. You can also quickly see that the deployment information type, ProdFeature in line eight and line 13, and the concluding condition Import Failed in line 14. The Status Data Preparation Completed on line 9 means that the source system was able to successfully query and go information from the Source system. But so the import into the Target organization failed as shown by the status in Line xiv. The failure error message is in line 17.
At this point, y'all should check the Target system for WfProcMgr logs (workflow process manager tasks) where the EAI Siebel Adapter is used to update or insert the data. In this instance, the reason is because the standard Admin Product Line Internal Product integration component does not permit inserts. In social club to successfully deploy the Production Characteristic data, the products associated with the Product Lines must already be on the target organisation.
CompagesADM is built on the Server Requests, Workflow Procedure and Enterprise Awarding Integration (EAI) infrastructure.
Figure 2 presents a logical overview of the different components involved. There are two environments shown, a source and target. Each environment is a distinct Siebel enterprise with its own Siebel database and server(s). The Siebel database for each environment contains tables that store data that is to be migrated (i.east. LOV data), ADM workflow procedure definitions, task details for the server requests, and entries in the EAI Queue. Each Siebel enterprise has an SRF which contains the ADM integration objects. Each enterprise will likewise take access to its own Siebel FileSystem, which will temporarily store files used in the ADM session.
On the source arrangement, you need to have the Workflow and System Direction component groups online. On the target system, you need to accept the EAI, Workflow and System component groups online; you also need to setup the Siebel Spider web Server so that the target arrangement can receive the HTTP requests. (If you are deploying using Export file, you would non utilize the Siebel server components or the Spider web Server, but all the other components beneath the dashed line are still required.)
Figure 2

ADM Workflow Processes for Online DeploymentsThe workflow processes used by ADM and standard integration objects’ names beginning with the letters UDA (for Universal Deployment Amanuensis). The primary business service used in the UDA workflow procedure is the UDA Service. The sequence of events, workflow processes and business services for an online ADM session are outlined in Figure 3. Because of differences in the catamenia and architecture for a deployment using export files, that process is outlined separately in Figure 4.
Figure three

Effigy 3 likewise illustrates the flow of data in an online deployment. When you click Deploy in the ADM views, the button invokes the UDA Deployment workflow procedure. The UDA Deployment workflow procedure runs in the current application object manager you lot are using. So for example, if you lot are logged into the Financial Services object director, it will run in the FinsObjMgr_enu component. The UDA Deployment workflow process then runs a subworkflow process, UDA Environs Verification, to verify that the Target environment is up and its schema versions match those in the Source environs. The UDA Surround Verification workflow processes use HTTP at this point to communicate with the Target system.
On the target system, the EAI Object Director receives the request from the UDA Environs Verification workflow procedure through the UDA Deploy named subsystem. The UDA Deploy named subsystem dispatches the request to the UDA Service concern service and the UDA Service sends a response back to the source system.
After verification is complete, on the source system, the UDA Deployment workflow process uses the Server Requests business organisation service to submit an asynchronous workflow procedure job. The workflow procedure chore invokes the UDA Information Query workflow process. The UDA Data Query workflow process uses the EAI Siebel Adapter and method query to excerpt information that to be deployed (into a Siebel integration object and so into XML). Once the ADM data is obtained, it is sent from the source to the target organisation using the UDA HTTP Transport workflow process as a sub workflow process.
On the target system, the EAI Object Director receives the ADM data from the UDA HTTP Transport workflow process through the UDA Deploy named subsystem. This time UDA Deploy named subsystem uses the Server Requests business service to submit an asynchronous workflow process job. A new workflow process managing director task runs the UDA Target Workflow workflow process. In the UDA Target Workflow, the EAI Siebel Adapter, with method Upsert (in Siebel version 7.7), is used for the logic of determining if the information volition be updated or inserted. Upon successful processing of the ADM Data, the workflow process manager sends a confirmation back to the source using the SISNAPI protocol.
On the source system, the confirmation request is received past the same application object director that originally initiated the deployment. The UDA Acknowledgement workflow process runs to update the ADM Session data with the results from the target arrangement.
ADM Concern Services for File DeploymentsEffigy 4 illustrates the flow of data in a deployment using export files. Different batch or online deployments, when you use export files, you exercise not need to have a running Siebel server. There are besides no explicit workflow processes invoked. The architectural simplification makes the file deployment option ideal for testing ADM.
If you run across an mistake performing an online deployment, switching your test instance to a file deployment is a practiced manner to isolate the root cause of the error. When yous test with the file deployment option on a dedicated client, you can enable client-side tracing so you can see more details on what may exist happening with the underlying Siebel application layers. You can focus on errors specific to the integration objects, content objects or EAI Siebel Adapter, and not exist concerned with Siebel server infrastructure. For steps on how to perform customer logging, refer to How Should Client Side Logging Exist Ready? (Doc ID 475587.1).
Figure 4 - Business Services Used for File Deployment

In Effigy 4, the awarding object manager represents the object manager engine in a dedicated client or in a null human foot print client. In a file deployment, you need to create an XML file that represents the ADM data first in the source system. The file needs to be saved in a location that is accessible past both the source and the target environments.
On the target system, y'all import the file created from the source system. When the XML file is deployed on the target system, a re-create of the XML file is saved in the EAI Queue. When the update or insert is consummate on the target system, a broadcast message is displayed on the target system to the position of the user who initiated the import
On the source system, you volition yet need to create an ADM project and a new ADM Session. However, when you lot click the Deploy button in a File deployment scenario, no workflow processes will be dispatched. Instead, the UDA Service will provide the logic to create an XML file containing the ADM deployment data. On the target system, y'all tin directly import the XML file using the Menu -> Deploy from File option. You do non need to have the EAIObjmgr running or whatsoever deployment session or projection created on the target organisation.
The drawback to using file deployment is that y'all will non have a record showing if an import succeeded or failed on the source or target system. Since in that location is no HTTP or SISNAPI established betwixt the target and source surroundings in a file deployment, there is no ADM view that shows if the deployment data was successfully imported. If in that location is a failure on the target system to import the data, you volition run across the bulletin in the client GUI. You can also check the EAI Queue (under Awarding Assistants – Integration) for a status and a re-create of the XML that you lot attempted to import.
The file deployment mode is also supported via the server manager (srvrmgr) control line which optimizes the import performance. With one srvrmgr command, yous can import multiple files.
Common ADM Error Messages Below is a listing of common ADM error messages. Make certain to search SupportWeb with the error bulletin and check for the latest ADM alerts as well.
These error letters may appear on the GUI or in a log file. For a listing of places to check for log files that would contain ADM related errors, see Figure 1.
Table 4 - Common ADM Error Messages and Symptoms

An error occurred exporting to file. Please brand sure the path <path value> points to a valid directory which has plenty space and is writable by the application process owner (SBL-SVC-00255)

SBL-SRQ-00103: Unable to find definition of component WfProcMgr

SBL-SVC-00232: The schema and SRF of the source environment and the target environment must exist of the same version.

Footstep '<?>' references non-existent error symbol '<?>'.(SBL-BPR-00186)

EAI Queue Entry Always Created During File Import

Unable To Deploy: Target Server Path is a required field. Please enter a value for the field. (SBL-DAT-00498)

Deployment Failed: â€Å"[Microsoft][ODBC Commuter Manager] Invalid cursor state”

Cannot connect to the server (SBL-EAI-04115). An error occurred connecting to the Target System.

SBL-BPR-00158: Cannot execute workflow process definition 'UDA Batch Deployement'

ObjMgrSRFLog Warning...(objdef.cpp (2192)) SBL-DAT-00144: Could not find 'Import Object' named 'EMT Session'

Multiple matches found for instance of integration component '%i' using search specification '%2' in the business organization component '%3', based on user key '%4'

LAST_UPD_BY Field Does Not Contain Correct Values

Task Status Completed but Information Not Imported

"In that location were more rows than could exist returned. Delight refine your query to bring dorsum fewer rows (SBL-DAT-00500) (SBL-EAI-04376)

View: UDA Project Administration View does not contain applet: EMT Project Class Applet. (SBL-SVC-00254)

LOV Parent-Child Relationship Is Not Established

Symptom or Error Message You received the following error when exporting to a file:
An fault occurred exporting to file. Please make certain the path <path value> points to a valid directory which has plenty space and is writable past the awarding procedure possessor (SBL-SVC-00255)
Cause The export path specified is not a valid directory name or is inaccessible from the machine where the ADM process is running.
Diagnostic Steps Verify that the file path given is valid and can be accessed from the motorcar where the ADM procedure is running.
Solution The export path should be a shared network resource. If deploying to a file using a defended customer, specify an export path is that is relative to the dedicated client. For instance, if yous are on your local Windows machine, you tin can specify d:\temp as your export path.
If deploying to a file using a nix footprint client, specify an export path is relative to the Siebel server where the object manager is running. For example, if you are using the thin client, and connecting to a Siebel server running on Solaris, you lot need to specify a network path that is valid for the Solaris server, i.eastward. /tmp.
SBL-SRQ-00103: Unable to find definition of component WfProcMgr Symptom or Fault Bulletin After clicking Deploy and inbound the correct password, the deployment session fails. The following error messages shows up in the Siebel component log:
SBL-SRQ-00103: Unable to observe definition of component WfProcMgr
In the ADM log or on the Siebel client, you may meet this mistake message:
Mistake encountered at workflow "<?>", footstep "<?>"
- No change/update is in consequence.(SBL-EAI-04442)
Cause The Workflow Process Managing director Server component definition has not been synchronized from the Server Manager screen. When yous synchronize components, the Siebel server updates data about your Enterprise in the S_SRM_ACTION tabular array.
Diagnostic Steps

2. The middle applet (Batch Component Admin) should contain a list of server components. If the list is empty, synchronization has not been done.

Solution In the source and target environments, start a Siebel Client. Then navigate to Sitemap > Administration - Server Configuration > Enterprises > Synchronize, click Synchronize.
SBL-SVC-00232: The schema and SRF of the source environment and the target environs must be of the same version. Symptom or Mistake Message The deployment session fails with this error:
SBL-SVC-00232: The schema and SRF of the source environment and the target surroundings must be of the same version.
Crusade In Siebel versions 7.vii and 7.seven.1, ADM checks the Siebel SRF and schema versions of the target environment against that of the source environment. If either the SRF or the custom schema versions are different, yous will get the error.
Change Asking 12-MAR8FT has been logged to address this product defect. It has been stock-still in Siebel Fix Pack 7.7.2.i.
The new beliefs is that SRF version will not exist validated. The custom schema version checking will be skipped but the major, small and vertical schema versions are yet checked. However, if the SRFs between the target and source environments do not take matching integration objects, the deployment would still neglect.
Solution

2. If you are not able to install the prepare pack, a manual workaround is available. It is to deploy using Export Files then you can change the XML attributes. Here is how to change the XML:

1. Determine the schema and srf versions for the target system.

2. Deploy any file on the target System (you will not demand to import this project into any organisation.) Then open up the file you deployed in notepad and copy out the lines containing the SchemaVersion and SRFVersion. Information technology will expect something like this (with dissimilar values in double quotes):

SchemaVersion="41.57.0.69" SRFVersion="36|1074164158|1087259477"

3. Modify the Export file.

4. Open the XML file created from your source organization. And then cut and paste the Schema and SRF string from the target system’southward XML into your source system’s XML file. When you save the source organization XML file, brand sure you retain the original encoding of the XML certificate (utf-viii).

NOTE:
If you require a workaround for online deployments, delight contact Siebel Technical Support for assistance with modifying the UDA Deployment workflow process.
Step '<?>' references non-existent error symbol '<?>'.(SBL-BPR-00186) Symptom or Error Message When deploying a session using the command line interface, the status of the deployment session fails with the post-obit errors:
Nosotros detected an Mistake which may have occurred for i or more of the following reasons:
Stride '<?>' references non-existent error symbol '<?>'.(SBL-BPR-00186)
Yous may run into this mistake in the object director log:
SBL-GEN-00000: Unable to load message 0xffff
Cause Command line deployment using on-line way is not supported
Solution
In order to deploy in command line manner, the session must be configured to export to a file past checking the Export to File flag. Batch deployment using on-line mode is not supported.
EAI Queue Entry Ever Created During File Import Symptom or Mistake Message An EAI queue entry is always created when performing a file import regardless of the Business Component User Property value.
Cause This is an expected behavior for the standard ADM configuration.
Solution To stop entry generation in the EAI Queue, set the User Property Use EAI Queue to Never on the EMT Session business component.
For more data nearly the EAI Queue, refer to Siebel Bookshelf version 7.7 > Siebel Connector for SAP R/three .
Unable To Deploy: Target Server Path is a required field. Please enter a value for the field. (SBL-DAT-00498) Symptom or Mistake Message You are not able to deploy to a file. When you click Deploy, yous may come across this message:
Target Server Path is a required field. Delight enter a value for the field. (SBL-DAT-00498)
Cause The Consign to File box must be checked to deploy to a file.
Solution
Bank check the Consign to File box in the ADM Session.
If the box is grayed out, you need to recreate a new ADM Projection and check the Export to File box for the new ADM Project. And then enable the new ADM Project and redeploy.
Deployment Failed: â€Å"[Microsoft][ODBC Driver Manager] Invalid cursor state” Symptom or Error Message After clicking Deploy, the condition changes to Deployment Failed. The following fault message shows up in the SRProc.log file:
"[Microsoft][ODBC Driver Manager] Invalid cursor state"
Cause

2. In that location are too many connected users.

Diagnostic Steps Check the number of the cursors in the database and make sure it complies with Siebel system requirements.
Solution If the number of cursors is too low, increase the cursor number and run the deployment again.
Cannot connect to the server (SBL-EAI-04115). An error occurred connecting to the Target System. Symptom or Mistake Bulletin When submitting an online deployment, you receive the post-obit mistake:
Cannot connect to the server (SBL-EAI-04115). An error occurred connecting to the Target System. Delight verify the connection information. (SBL-SVC-00252)
Cause The HTTP session from the source to the target could not be started.
Diagnostic Steps

2. Check that you have typed in a valid username and password for the target system

3. Check that the EAI object director on the target system is online. Y'all can verify that the EAI object manager on the target system is online by using the statspage with this URL: http://<webserver>:<port>/eai_enu/_stats.swe (substitute <webserver> and <port> with values for your environment). If the stats page comes upwards, you take verified that you are able to connect to the EAI Object manager and it is online.

4. Bank check that the source and target environments accept network connectivity. For example, make certain you can ping the target webserver from the source Siebel server concrete motorcar.

Solution

2. Make certain that the EAIObjMgr is online on the target system.

3. If there are network bug, check with your network ambassador to resolve the issues (e.1000., name resolution issues, firewalls in place).

SBL-BPR-00158: Cannot execute workflow process definition 'UDA Batch Deployement' Symptom or Error Message When executing a batch deployment, y'all get the error:
SBL-BPR-00158: Cannot execute workflow process definition 'UDA Batch Deployement'
Crusade The workflow procedure name is not spelled correctly or the workflow process is not activated in the Siebel Client.
Diagnostic Steps

2. In Siebel Tools, check that workflow processes accept a status of Completed. In the Siebel client, verify the same workflow processes have a status of Agile.

Solution

2. If y'all have enabled a workflow process in the Siebel client, stop the workflow process managing director component and restart it. Resubmit your job.

ObjMgrSRFLog Warning...(objdef.cpp (2192)) SBL-DAT-00144: Could not discover 'Import Object' named 'EMT Session' Symptom or Error Message When you enable component event logging in the Siebel server components, you meet messages like these:
ObjMgrSRFLog Warning ... (objdef.cpp (2192)) SBL-DAT-00144: Could not find 'Import Object' named 'EMT Session'. This object is inactive or nonexistent.
Cause These are warning messages, and they are benign. You can ignore those messages. If the value after the component consequence is not Alert, and then y'all should investigate if the fault is fatal.
Multiple matches found for instance of integration component '%1' using search specification '%2' in the concern component '%3', based on user key '%4' Symptom or Fault Message When deploying all the out of the box LOVs, you get this fault:
Multiple matches found for instance of integration component '%one' using search specification '%2' in the business component '%3', based on user key '%4'.
Cause The Siebel seed data has indistinguishable values for LOVs.
Change Request 12-MPWXD3 has been logged to address this product defect.
Diagnostic Steps Log into the database and run the following SQL statement to run into if you take duplicate seed data:
select TYPE, NAME from S_LST_OF_VAL
where type = ‘LOV_TYPE’
grouping by TYPE, NAME
having count(*) > 1
Solution Log on a Siebel Client, and go to the LOV Views. Query for the LOV Types you found running the SQL Query in the diagnostic steps. For each duplicate pair, modify the display value for one of the records to make the record unique.
LAST_UPD_BY Field Does Not Contain Correct Values Symptom or Error Message Later on migrating information from the source application to the target awarding with different users, records are always inserted every bit SADMIN user ID. The LAST_UPD_BY field does non contain correct values.
Cause Information is inserted into the target awarding using the Server Request Banker (SRB) and Server Request Processor components (SRP). The user stamp on the inserted records will be the user proper noun set for the SRB/SRP components (typically SADMIN), not the user proper noun supplied from the source application.
Solution Create a new user ID with the aforementioned privilege equally SADMIN and update the SRB/SRP components to use that new user ID.
"There were more rows than could be returned. Please refine your query to bring back fewer rows (SBL-DAT-00500) (SBL-EAI-04376) Symptom or Error Message When exporting data to a file, y'all receive the following error bulletin:
Nosotros detected an Fault which may have occurred for one or more of the post-obit reasons:
Method 'NextRecord' of business concern component 'Feature Admission' (integration component 'Characteristic Admission') returned the following error: "There were more than rows than could be returned. Delight refine your query to bring back fewer rows (SBL-DAT-00500) (SBL-EAI-04376)
Cause There is a 10K limit on the EAI send.
Solution
Specify a search specification such as [Name] not similar 'A* to reduce the number of records returned to less than ten,000.
If yous are not in a production surround and would like to bypass the 10K limit, information technology is possible to do so. However, delight behave in mind that there is a potential for large memory usage of the Siebel server component.
To bypass the default 10000K limit, prepare the value for the parameter "DSMaxFetchArraySize" nether the "InfraDatasources" named sub-system to the number of records you await to consign. Notation that this param is for a given data source and would touch all components that share the aforementioned information source so we only advise you ready this value immediately prior to your export and reset information technology to the default after your export.
On a defended customer, you can prepare the value past setting param MaxFetchArraySize under the individual information source section on the client’s cfg file.
Chore Status Completed but Data Not Imported Symptom or Error Message When deploying sessions using the control line interface, the status of the workflow process task is completed. However the data has not been imported to the target environment.
Cause

2. The FileExportPath and FileImportPath process properties are non valid.

Diagnostic Steps

2. Confirm the workflow processes accept the right FileExportPath and FileImportPath process property values.

Solution

2. When exporting the file, verify the FileExportPath procedure property is ready correctly for the workflow process UDA Batch Deployment. When importing the file, verify that the FileImportPath for the UDA Batch Import workflow procedure has a valid value. The values should exist the directories which will incorporate the exported and imported files respectively. Both values can bespeak to the same location.

NOTE:
For more information about deploying in batch mode (running the workflow process), refer to Siebel Bookshelf version 7.7 > Going Live with Siebel eBusiness Applications > Migrating Customizations Between Applications > Reviewing the ADM Information Migration.
View: UDA Project Assistants View does not incorporate applet: EMT Project Form Applet. (SBL-SVC-00254) Symptom or Error Message View: UDA Project Assistants View does not contain applet: EMT Project Grade Applet. (SBL-SVC-00254)
Cause The applet might be missing in View: UDA Project Administration View
Diagnostic Steps In Siebel Tools, query for the View UDA Project Administration View.
Check for all the View Web Template Particular applets. Verify if the EMT Project Class Applet is at that place.
Solution In Siebel Tools navigate to View and query for UDA Project Assistants View and then add a View with the following information:
Spider web Template Item
Name = "EMT Projection Form Applet" applet
Item Identifier = three or next number
Applet Value = "EMT Project Form Applet"
Applet Mode = "Edit"
LOV Parent-Child Relationship Is Not Established
Symptom or Fault Bulletin When deploying dependent data types, such as hierarchical LOVs with the LOV-HierParent data type, both records are successfully imported in the target organisation, merely the parent-kid relationship is not established. For LOVs, afterward the outset deployment, the child LOV does non testify the parent LOV. When y'all redeploy the projection a second fourth dimension, then the parent-child relationship is established.
Cause For dependent data types, ADM will deploy the child data blazon before the parent information type. When ADM deploys the child data, the parent does not yet be and then the EAI Siebel Adapter cannot set the relationship on the kid to point to the parent. Hence, after the first deployment, while both data types are successfully deployed, the human relationship between the two records is not established.
Solution This is the intended behavior of ADM that all hierarchical data must be imported twice. When deploying a child record, ADM will not error out if the parent record does non exist because the picklist validation is disabled.
When an LOV tape with a reference to a parent Language Independent Code (LIC) value is being inserted, that parent LIC value must already exist nowadays in the target system for the reference to be successfully set. However, since the Parent LIC value is in itself another LOV record, the only manner to make sure that all the references are successfully established is to import the LOV values using two dependent data types both are LOV data types. Internally this will cause 2 deployment operations to occur, once per session item. See Figure v for a logical description of what happens.
Import pass #1 based on the LOV-HierChild session item
Import pass #ii based on the LOV-HierParent session item
In the case where the parent and child LOVs are of different LOV Types, y'all can deploy the data in one deployment session past using the deployment filter. Since the ADM child data type (LOV-HierChild) is always deployed first, if you fix the deployment filter for the child ADM information type to find the record for the parent LOV, the parent LOV tin can be inserted before the child LOV. And then fix the deployment filter for the parent ADM data blazon (LOV-HierParent) to detect the kid LOV deployment tape. See Figure 6 for the logical description of what happens.
Annotation:
Figure five - Hierarchical LOV Deployment with LOVs of the Aforementioned LOV Type

Figure 6 - Hierarchical LOV Deployment with LOVs of Unlike LOV Type
If you are deploying LOVs where the LOV child and parent are of dissimilar LOV types, be sure to review Document 477904.1 for data on how to obtain updated SIFs. Without the updated SIFs compiled into your SRF, yous volition not be able to deploy LOV data if the LOV Types are different. : the aforementioned LOVs will be updated. However, now any Parent LIC values referenced in the record being imported is already present in the target DB. So therefore, 2d import will update the LOV records previously upserted from the first deployment with the correct parent LIC value. : all LOVs volition be inserted successfully. For the child LOVs that reference a parent LIC, the parent LIC field will exist left blank. The UDA List of Values integration component has been configured to ignore errors on self referenced fields which are bounded to a picklist. For more information about how to deploy using the control line interface, refer to Siebel Bookshelf version 7.7 > Going Live with Siebel eBusiness Applications > Migrating Customizations Between Applications > Deploying Sessions Using Command-Line Interface.

Deploy the UDA Batch Import and UDA Batch Deployment workflow processes in Siebel Tools. Activate the workflow processes in the Siebel Client.

In Siebel Tools, check that UDA Batch Import and UDA Batch Deployment workflow processes accept a status of Completed. In the Siebel customer, verify the same workflow processes have a status of Active.

The UDA Batch Import and UDA Batch Deployment workflow processes accept not been deployed properly.

Resubmit your workflow process chore with the right spelling.

Check the spelling of your workflow process. In the symptom higher up, Deployement is misspelled (an extra 'e' between the 'y' and the 'm').

Fix any invalid arguments supplied and recreate the deployment session.

Check that yous take supplied a valid Siebel URL for the target system.

The database is running out of the cursors.

Other modifications to the XML content are non recommended unless otherwise directed past Siebel Technical Back up.

Contact Siebel Technical Support to request the latest available 7.seven.2.ten Fix Pack. Install the prepare pack on your target and source Siebel application environments.

Navigate to Sitemap > Administration - Server Configuration > Enterprises > Synchronize.

An mistake occurred exporting to file. Delight make sure the path <path value> points to a valid directory which has enough infinite and is writable past the application process owner (SBL-SVC-00255) - Workflow Process and Business Services Used for Online Deployment - Siebel Components and Objects Used in ADM - ADM Session Log. Filename Is 42-4P84F.log

baskinthermly.blogspot.com

Source: http://www.error-codes.info/2011/03/sbl-eai-04115-cannot-connect-to-server.html

Share this post