Skip to Content
0
Former Member
Jan 29, 2009 at 05:40 PM

Publications fail intermittently on XI 3.1

136 Views

Hello,

We have publications that fail intermittently with the error:

An exception was caught while scheduling the publication. (FBE60203) or

Unable to find the infostore service. Is your CMS running and configured properly? (FBE60002)

com.crystaldecisions.sdk.exception.SDKException$OCAFramework: Unable to reconnect to the CMS xxx.ny2.xxx.net:6400. The session has been logged off or has expired. (FWM 01002)

cause:com.crystaldecisions.enterprise.ocaframework.OCAFrameworkException$LogonFailover: Unable to reconnect to the CMS xxx.ny2.xxx.net:6400. The session has been logged off or has expired. (FWM 01002)

The publication log also invarably contains Unable to reconnect to the CMS xxx.ny2.xxx.net:6400. The session has been logged off or has expired. (FWM 01002).

The publications are scheduled as follows:

1. A program object is scheduled to kick off the publication. This program object passes values to the prompts in the publication at run time.

2. The publications are scheduled as MHTML files to an FTP server.

3. The publications are based on different tabs in Webi report

Our environment consists of a full stack on a single server.

Environment details:

BO XI 3.1 Premium CPU on RHEL 4 (64 bit) (2.6.9-67.0.15.ELsmp)

Oracle 64 bit

Tomcat 5.5

We schedule a lot of reports using a similar process flow. It is only the publications that fail.

We have a case open too. I was hoping someone had seen something like this before.

The entire publication log from the last time one of the publications failed is below:

2009-01-26 18:45:27,761 INFO  [pool-4-thread-7] BusinessObjects_PublicationAdminLog_Instance_126761 - [Publication ID # 126761] - Running publication instance.
2009-01-26 18:45:27,805 INFO  [pool-4-thread-7] BusinessObjects_PublicationAdminLog_Instance_126761 - [Publication ID # 126761] - The global delivery rule for this publication was met; publication processing will now begin.
2009-01-26 18:45:28,015 ERROR [PublishingService:HandlerPool-39] BusinessObjects_PublicationAdminLog_Instance_126761 - [Publication ID # 126761] - An exception was caught while scheduling the publication. (FBE60203)
com.crystaldecisions.enterprise.ocaframework.IManagedService$ManagedLogoffException: Unable to reconnect to the CMS xxx.ny2.xxx.net:6400. The session has been logged off or has expired. (FWM 01002)
	at com.crystaldecisions.enterprise.ocaframework.ManagedService.invoke(ManagedService.java:604)
	at com.crystaldecisions.sdk.occa.infostore.internal._InfoStoreEx4Proxy.queryEx3(_InfoStoreEx4Proxy.java:364)
	at com.crystaldecisions.sdk.occa.infostore.internal.InternalInfoStore.queryHelper(InternalInfoStore.java:708)
	at com.crystaldecisions.sdk.occa.infostore.internal.InternalInfoStore.query(InternalInfoStore.java:566)
	at com.crystaldecisions.sdk.occa.infostore.internal.QuerySettings.executeQuery(QuerySettings.java:94)
	at com.crystaldecisions.sdk.occa.infostore.internal.InfoObject.getParent(InfoObject.java:1377)
	at com.crystaldecisions.sdk.occa.infostore.internal.InfoObject.getParent(InfoObject.java:1363)
	at com.businessobjects.publisher.processing.AuditDetailHelper.buildPublicationPath(AuditDetailHelper.java:108)
	at com.businessobjects.publisher.processing.AuditDetailHelper.setupAuditDetails(AuditDetailHelper.java:72)
	at com.businessobjects.publisher.scheduling.SchedulingHelper.scheduleScopeBatch(SchedulingHelper.java:304)
	at com.businessobjects.publisher.processing.ScopeBatchHandler.run(ScopeBatchHandler.java:101)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
2009-01-26 18:45:28,028 INFO  [pool-4-thread-7] BusinessObjects_PublicationAdminLog_Instance_126761 - [Publication ID # 126761] - Publication scheduling complete.

Once a publication fails, the only method to ensure success is to:

1. Restart the CMS, Publication Job Server and Webi Processing Server

2. Recreate the publication (remove the source, add it again)

As an aside, I've had cases open twice before for the same issue. I closed them both because I can't replicate on demand (we were on XI3.0 RTM at that point).

I'd appreciate any help.

Thanks.

Srinivas