Skip to Content
avatar image
Former Member

Crystal Server Publications failing, log file question

We get intermittent failures on our regularly scheduled publications - no clear reasons why. when it is re-run manually, all processes ok. when peak reporting times, there are about 150 publications using 225 reports, but run over a couple of days - each report runs an average of 25 minutes. Our job server is set for 4 instances (we cant do more because the data server would choke)

My question is about trying to figure out if the numerous errors i am seeing in the Crystal Log, samples listed below. Do any of these suggest any diagnosis and repair of the server itself, which may in turn help our publication failure rate?

Any kind of fine tuning that should be done on the server? its been up for about 4 years, and probably could use a spring cleaning.

Thanks so much!

Number files in FileStore:

Input 1512

Output 19500

Server =Windows 2008 SP2

Memory 32GB


Crystal version: SAP BusinessObjects BI Platform 4.1 Support Pack 7


Typical error message:

Failed publication (rerunning it works fine, without changing any parameters):

2017-01-23 14:52:57,090 ERROR [PublishingService:HandlerPool-0] BusinessObjects_PublicationAdminErrorLog_Instance_1017170 - [Publication ID # 1017170] - Failure: Username| To: | Failed (Failure) [1 recipients processed.]

2017-02-20 15:07:58,268 ERROR [PublishingService:HandlerPool-22] BusinessObjects_PublicationAdminErrorLog_Instance_823365 - [Publication ID # 823365] - Scheduling document job "ER27-13 Bandwidth Month Trend Report Master Excel" (ID: 824,183) failed: Error in File ~tmpfac911de91c7a0.rpt: Unable to connect: incorrect log on parameters. Details: [Database Vendor Code: 18470 ] Scheduling document 'ER27-13 Bandwidth Month Trend Report Master Excel' (ID: 824,183) failed for the following users:

the Crystal Server log file has thousands of errors over just two days

More than 19500 of these errors:

Error| | |E| |cms_OurserverName.CentralManagementServer| 6128|2112|| ||||||||||||||||||||||Performing instance cleanup on an instance. Instances should not have instances

160 Deadlock errors:

Database deadlock encountered. Ensure database is correctly tuned and that data statistics are up to date.

over 450 "assert Failures" like below

|855|0|9|0|CMC.WebApp|cms_OurserverName:1680:313.20194:1|BIPSDK.InternalInfoStore:schedule|nac-ams-cry01:5672:43999.5086723:114|cms_OurserverName.CentralManagementServer.commitEx4|localhost:6128:5528.5167381:1|Ck6BtFHO_EZYrZWlIGyNQYQ4ee2|||||||||||assert failure: (.\ScheduleObject.cpp:202). (0 : no message).

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

0 Answers