BusinessObjects Board

Publication fails for Email

Hi All,
We are having a tough time resolving an issue regarding Publication.
Burst reports work fine when sent to File System or BI Inbox destinations, but just not Email. Also, when sending a regular report to an email destination, the email gets sent fine also. The problem just seems to affect the combination of bursting and emailing together.

We made sure all servers that have destinations (Adaptive Job Server, Publication Scheduling, Platform Search and LCMJobServer) were set up the same for SMTP emailing. We also tried shutting down the latter 2 but that didn’t help. We also tried a fresh BI server reboot.

The log file link above leads to this…

2015-05-26 05:50:34,355 INFO [PublishingService:RunInstancePool-6] BusinessObjects_PublicationAdminLog_Instance_20784 - [Publication ID # 20784] - Running publication instance.
2015-05-26 05:50:34,402 INFO [PublishingService:RunInstancePool-6] BusinessObjects_PublicationAdminLog_Instance_20784 - [Publication ID # 20784] - The global delivery rule for this publication was met; publication processing will now begin.
2015-05-26 05:56:55,946 ERROR [PublishingService:HandlerPool-1] BusinessObjects_PublicationAdminLog_Instance_20784 - [Publication ID # 20784] - Distribution to destination CrystalEnterprise.Smtp (To: XXXX) failed. Recipient: 10, Document Scope: Burst Set Report Sample 30042015 (Loc ID Covg Code) : 20800 (Pdf) : (OR (AND )). Object failed to run due to an error while processing on the Job Server. (FBE60013)
2015-05-26 05:56:56,071 INFO [PublishingService:RunInstancePool-6] BusinessObjects_PublicationAdminLog_Instance_20784 - [Publication ID # 20784] - Publication scheduling complete.

Any input can be of much help. We are having a tough time finding any solution on this part.

:hb:


boakshay (BOB member since 2014-09-03)

I know this is a bit late for a reply but we had the same issue “Object failed to run due to an error while processing on the Job Server. (FBE60013)”.

In our case it was the mail server IP address - it had been changed without us knowing, and this caused the above error.


Ringpull (BOB member since 2015-11-19)