Applies to:
Siebel Email Marketing Server - Version: 7.8.2.3 SIA [19221] to 8.1 [21039] - Release: V7 to V8z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.8.2.3 [19221] SVE Transp
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server
This document was previously published as Siebel SR 38-3188433301.
Symptoms
SBL-EAI-04117, SBL-MKT-00453, SBL-BPR-00162 Dear Support Web,We are using Email Sending Daemon to send Email Offers. ESD is configured correctly and set up successfully. But when we are trying to send an email we get the following error message:
Error/Warning Error calling the service 'Wave Execution', metoden 'SendOffers' i steg 'Send Offers / Vendor Lists'.(SBL-BPR-00162)
Error in HTTP request under 'Submitting Data SendHTTP request': 'Status code - 404'(SBL-EAI-04117)
Could you, please, advice the solution to solve this issue?
Thank you!
Cause
The Email Sending Daemon (ESD) was set to run on port 8080 but this conflicted with another port.Solution
Message 1
For the benefit of other readers.The customer was encountering the following errors when using Basic Mode and Advanced Mode
Error/warning: Error when calling the service Wave Execution', the method 'SendOffers' in step 'Send Offers / Vendor Lists'.(SBL-BPR-00162)
One or several of the parallell “uppgifter” (perhaps; information, requests or similar...) found an error. All queued “uppgifter” that have been scheduled to following the wrong “uppgift” have been aborted. (SBL-MKT-00453)
Error/Warning Error calling the service 'Wave Execution', metoden 'SendOffers' i steg 'Send Offers / Vendor Lists'.(SBL-BPR-00162)
Error in HTTP request under 'Submitting Data SendHTTP request': 'Status code - 404'(SBL-EAI-04117)
The Email Sending Daemon (ESD) was set to run on port 8080 but this conflicted with another port. Once the port conflict was resolved (i.e. set ESD to use port 8082) the loading and launching of campaigns worked successfully.
Regards,
Applies to:
Siebel Campaigns - Version: 7.7.2 [18325] to 8.1.1.3[21219] - Release: V7 to V8Information in this document applies to any platform.
This document was previously published as Siebel SR 38-3056714371.
Symptoms
SBL-DAT-00175, SBL-EAI-04376, SBL-MKT-00453, SBL-BPR-00162We executed our first email program in Production this past weekend. To do so, we scheduled the program stage to automatically load and launch 11 campaigns. During the loading of the 6th campaign, we encountered the following errors:
Method 'Execute' of business
component 'Marketing Camp Con' (integration component 'Campaign Contact') returned the following
error:
Database connection was lost, please
retry.(SBL-DAT-00175) (SBL-EAI-04376)
Error invoking service 'EAI Siebel Adapter',
method 'Upsert' at step 'Update Camp Con'.(SBL-BPR-00162)
Error/Warning : The SRM
request '1-AUK-BXL' failed during parallel import for the Campaign Load/Analytics Data
Load. One or more of the parallel tasks may have encountered an error. Any
queued tasks that were scheduled to follow the failed task have been
cancelled.(SBL-MKT-00453)
Error invoking service 'Mktg Data Load Service', method
'CampaignLoad' at step 'Load Analytics Segment'.(SBL-BPR-00162)
We had run into the SRM error in our test environment when executing a program stage that would load and launch a much higher number of emails than this past weekend. Because of this as a precautionary measure, we set the Max # of Records value on the Campaign Load Format to 250.
What causes this error and what steps can we take to fix it?
Cause
.Solution
It was found that the errors were caused by a maintenance process that was kicked off in the morning on the OLAP database. At the end of the procedure, the process was configured to close all connections to the database. The errors observed were a direct result of this process closing open connections on the database.Applies to:
Siebel Marketing Server - Version: 8.1.1.5 SIA [21229] and later [Release: V8 and later ]Information in this document applies to any platform.
Symptoms
The following error was observed in the wfprocmgr log for the campaign launch :In one of the task triggered that execute the process, "List Export (Internal)", the following error was observed :
ObjMgrSessionLog Error 1 000002d64f3380e6:0 2012-02-09 15:11:36 (physmod.cpp (2066)) SBL-DAT-00938: The language code is not valid. Please check and try again.
GenericLog GenericError 1 000002d64f3380e6:0 2012-02-09 15:11:36 (srmconn.cpp (2544) err=1311736 sys=17) SBL-SVR-01016: Internal: Could not encode a SISNAPI message: (null)
GenericLog GenericError 1 000002d64f3380e6:0 2012-02-09 15:11:36 (srmconn.cpp (2313) err=1311736 sys=0) SBL-SVR-01016: Internal: Could not encode a SISNAPI message: (null)
GenericLog GenericError 1 000002d64f3380e6:0 2012-02-09 15:11:36 (fsmclientstub.cpp (355) err=1311736 sys=0) SBL-SVR-01016: Internal: Could not encode a SISNAPI message: (null)
ObjMgrBusCompLog Error 1 000002d64f3380e6:0 2012-02-09 15:11:37 (bcfile.cpp (4347)) SBL-UIF-00229: Error occurred while opening file 'S_CAMP_LSTOUTPT_1-14LA0CU_1-R1K18M.SAF'.
:
The above error then lead to the campaign launch to fail :
MktgCampaignLaunchEvent Info 4 000000da4efcb086:0 2011-12-29 10:02:28 CAMPAIGN EXECUTION: Successfully completed executing method LaunchWaveError
ObjMgrBusServiceLog InvokeMethod 4 000000da4efcb086:0 2011-12-29 10:02:28 Business Service 'Wave Execution' invoke method 'LaunchWaveError' Execute Time: 0.557 seconds.
ObjMgrBusServiceLog InvokeMethod 4 000000da4efcb086:0 2011-12-29 10:02:28 End: Business Service 'Wave Execution' invoke method: 'LaunchWaveError' at 40e77a08
StpExec TaskArg 4 000000da4efcb086:0 2011-12-29 10:02:28 Output: @0*1*0*0*0*0*
StpExec Cond 4 000000da4efcb086:0 2011-12-29 10:02:28 Step branch 'Default.CONNECTOR' passed.
StpExec End 4 000000da4efcb086:0 2011-12-29 10:02:28 Stopping step instance of 'Wave Launch Error' with a 'Completed' status.
StpExec Create 4 000000da4efcb086:0 2011-12-29 10:02:28 Instantiating step definition 'Stop'.
PrcExec PropSet 4 000000da4efcb086:0 2011-12-29 10:02:28 Getting runtime value of property 'Namespace: 'USER' Name: 'Error Message' Datatype: 'String''.
StpExec Task 4 000000da4efcb086:0 2011-12-29 10:02:28 Raising error code 'WF_ERR_CUSTOM_1'.
ObjMgrLog Error 1 000000da4efcb086:0 2011-12-29 10:02:28 (stepexec.cpp (950)) SBL-BPR-00131: Error invoking service 'Wave Execution', method 'SendOffers' at step 'Send Offers / Vendor Lists'.(SBL-BPR-00162)
--
One or more of the parallel tasks may have encountered an error. Any queued tasks that were scheduled to follow the failed task have been cancelled.(SBL-MKT-00453)
Cause
It was found that the FSMSRVR has maxtasks set to 20, whilst the campaign launch is triggering more than 20 tasks concurrently.Solution
Increase the maxtask of FsmSrvr comp to 50. The error then stop recurring.References
BUG:10578755 - [CR#12-1V7F8QN][FR#12-1VE6YU3] PROVIDE FSM RECONNECT FUNCTIONALITY FOR OBJECT MABUG:13651454 - WORKFLOW PROCESS MANAGER TASK GETTING EXITED FOR CAMPAIGN LAUNCH.
Applies to:
Siebel Campaign Management - Version: 8.1.1 [21112] and later [Release: V8 and later ]Information in this document applies to any platform.
Symptoms
Email campaign wave launches are failing with the following error:1. Error invoking service 'Mktg List Export Service', method 'SendEmail' at step 'Send Email'.(SBL-BPR-00162)
--
Operation
'createMailing' of Web Service
'urn:xml-send-mailing.SendMailingService' at port 'SendMailing' failed
with the following explanation: "Required column Email Address^M not
found in supplied columns [Account Location, First Name, Camp Con Id,
Last Name, Cellular Phone #, Contact Id, Account, Segment/List Name, Job
Title, Source Code, Fax Phone #, Prospect Id, Work Phone #, Middle
Name, Email Address, Current Date, Home Phone #, M/M]".(SBL-EAI-04308)
2.
Error/Warning : Error invoking service 'Wave Execution', method
'SendOffers' at step 'Send Offers / Vendor Lists'.(SBL-BPR-00162)
--
One
or more of the parallel tasks may have encountered an error. Any queued
tasks that were scheduled to follow the failed task have been
cancelled.(SBL-MKT-00453)
Cause
The root cause of this issue was a corrupted esd.properties file on the Email Sending Daemon machine. There were extra ^M characters at the end of 2 parameters esd.emailAddress and esd.recipientId# -- ESD Web Service configuration options
esd.emailAddress=Email Address^M <==== here is the problem
esd.recipientId=Camp Con Id^M <==== here is the problem
Solution
(1) Stop the ESD service
(2) Open esd.properties file in a good editor
(3) remove all occurrences of ^M The section highlighted above should look like this:
# -- ESD Web Service configuration options
esd.emailAddress=Email Address
esd.recipientId=Camp Con Id
(4) Save file and reopen the file to make sure the ^M characters are still gone after the save
(5) restart the ESD service
No comments:
Post a Comment