Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

SAP BO Publication LOG-FILE

Hi,

when a publication failed and i open the log-file, i have always the problem that the information in there are really bad.

Can someone tell me, how i can find out which publication instance failed ?

I scheduled the report based on a webi-list with around 2000 recipients and i'm not able to find the failed credentials.

Can i use the ID -> (ID: 7,765,961) to find something (maybe a folder)  on windows-level ??

Thanks a lot

Simon

2015-10-21 11:10:52,645 INFO  [PublishingService:RunInstancePool-659] BusinessObjects_PublicationAdminLog_Instance_7765945 - [Publication ID # 7765945] - Running publication instance.

2015-10-21 11:10:52,739 INFO  [PublishingService:RunInstancePool-659] BusinessObjects_PublicationAdminLog_Instance_7765945 - [Publication ID # 7765945] - The global delivery rule for this publication was met; publication processing will now begin.

2015-10-21 11:11:35,716 INFO  [PublishingService:HandlerPool-72] BusinessObjects_PublicationAdminLog_Instance_7765945 - [Publication ID # 7765945] - Loans returns overdue (id 7,765,961): com.businessobjects.js.processingsubsystem.procreport.ProcReportException exception, Message: The data source is invalid: 'Failed to retrieve the cube for connection SD_M001.'. Please contact the maintainer of the data source to solve the problem. (CRS 300003)

2015-10-21 11:11:35,747 ERROR [PublishingService:HandlerPool-72] BusinessObjects_PublicationAdminLog_Instance_7765945 - [Publication ID # 7765945] - Scheduling document job "returns overdue" (ID: 7,765,961) failed: The data source is invalid: 'Failed to retrieve the cube for connection SD_M001.'. Please contact the maintainer of the data source to solve the problem. (CRS 300003) (FBE60502)

2015-10-21 11:56:46,708 INFO  [PublishingService:RunInstancePool-659] BusinessObjects_PublicationAdminLog_Instance_7765945 - [Publication ID # 7765945] - Publication scheduling complete.

Tags:
replied

Hi Simon,

We use that switch (-trace) in BO3.1 only, I have never used that in BI4.1. You are using BI 4.1 SP04 so you would find the below option in the properties of AJS. You just need to change it from unspecified to HIGH, the severity of the trace depends on you.

So remove the switch "-trace", change the above log level and restart the AJS(For changing the log level we do not need to restart any service but here we would be removing a switch "-trace" from the command line which will need a restart). Tracing will be enabled on AJS.

Now, lets come to the Auditing part. I really cannot tell you whether these settings are fine in your environment or not.

Those are events what we need to select as per our requirement. So if you think capturing that much events is fine for you then keep it as it is or else select the events what all you want to be captured in the audit database.

Yes, this is the directory where AJS will create the trace files. You would need to search few keywords in the trace files like failed/error/userid etc.

Hope that helps

~SwapnilY

0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question