on 04-21-2016 11:51 AM
Dear SAP Community,
Analysis Office Workbook scheduling is failing in all environment (Prod/Dev/Test) for all users with below error message:
Error: Error during scheduling; workbook does not contain OLAP connection.
Environment Details are as below:
- Product Version: SAP BI 4.1 SP6 Patch 3
- Analysis Office BIP Server Add-on 2.2 (server version)
- SAP BO Analysis Edition for Office 2.2.2.55076 (client version)
- Server OS: Windows Server 2012 R2
SSO using STS to backend BW server works fine
We followed SAP KBA: 2134836: Checklist for scheduling Analysis for office workbooks. We made sure all necessary things are in place however all workbooks are continues failing.
We are able to view and refresh same affected workbooks when opened from AAO client. Only scheduling part is impacted via BI-Launchpad in all environments.
I could not attach complete logs here, but here is the snippet for reference. Could someone assist us on this?
Regards,
Mahesh
Hi Raunak,
Yes, we used same installer in all environments.
Here one thing I would to add is, out of 70 Analysis workbooks, two existing workbooks we are able to schedule successfully in all environments. Both working workbooks are are based off of same data source and same OLAP connection. As we have checked with our developer team, there were no changes made in workbooks designing.
Considering above scenario, we can say that scheduling functionality has no issues. Still I would like to give try of re-install. We will update you once done.
Thanks!
Regards,
Mahesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Testing this issue with a blank database is little tough as it would take a lot of approvals and its a time consuming process and need to involve other teams. However we are able to reproduce this issue on our Dev/Test/QA and Prod, so I believe testing this issue on blank schema would give us same result.
On other side, we can create new OLAP connection to test the issue; however I would like to mention again that we already have Webi reports based on same OLAP connection and its working fine. Still let me try. I will update you once done.
As per sap kba: 2134836 - "Checklist for scheduling Analysis for office workbooks" Single Sign-on must be working in order to schedule AO workbooks. This is a kind of pre-requisites. We replaced FQDN with BW server's IP and tested connection along with auth method SSO for OLAP connection. Result is still the same, AO workbook is failing with same error message.
Hello Stephan/Everyone,
After investigation found that the issue had caused because of missing mandatory prompts values.
If your Analysis Workbook contains "Mandatory prompts" then it should contains some values in SAP BW backend. If that value is blank/missing then schedule fails with said error message.
In my case, workbooks whose schedules succeeds, its corresponding mandatory prompt values were already in place in backend BW system and it can be seen while refreshing those workbooks; however in case of non-working workbooks, values were missing against mandatory prompts. Assigning values against mandatory prompts in BW backend system solved the problem and AFO scheduling started working
I hope this helps!
Regards,
Mahesh
Are you using SSO with your OLAP connection for scheduling?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sure Tammy.
We have already opened an OSS with SAP, but unfortunately no progress so far on this.
I feel this issue is more into platform/admin side as only scheduling functionality impacted here in all environments. So is it possible for you to move this thread into BI Platform, to get additional thoughts?
Regards,
Mahesh
Here is the logs snippet for reference: ====jobserver_DEV1.AdaptiveJobServer_AOSchedulingService_CHILD0_trace.000001.glf=====
|A88CC8F01B494B3992610246F6605FE70|2016 01 21 13:28:19.147|+0200|Error| |==|E| |jobserver_KESBIDEV1.AdaptiveJobServer_AOSchedulingService_CHILD0|36532| 30|ORBacus:ThreadPerRequest:Dispatcher| |460|0|4|0|BIlaunchpad.WebApp|kesbidev1:1360:29769.226194:1|CMS.runJobs|localhost:7464:48096.2275539:1|.run|kesbidev1:36532:30.8:1|CloXJt41fUzFhxj0AAfDFl837383|||||||||com.businessobjects.js.child.processingsubsystem.aoprecalc||
An error occurred; could not precalulcate instance 266029 : 360 |A88CC8F01B494B3992610246F6605FE71|2016 01 21 13:28:19.147|+0200|Error| |==|E| |jobserver_KESBIDEV1.AdaptiveJobServer_AOSchedulingService_CHILD0|36532| 30|ORBacus:ThreadPerRequest:Dispatcher| |460|0|4|0|BIlaunchpad.WebApp|kesbidev1:1360:29769.226194:1|CMS.runJobs|localhost:7464:48096.2275539:1|.run|kesbidev1:36532:30.8:1|CloXJt41fUzFhxj0AAfDFl837383|||||||||com.businessobjects.js.child.processingsubsystem.aoprecalc||
AOPrecalcExecutor.Execute returned false |9F4990DEBF5E47FCBC95E3A4FAE732F30|2016 01 21 14:13:08.149|+0200|Error| |==|E| |jobserver_KESBIDEV1.AdaptiveJobServer_AOSchedulingService_CHILD0|27388| 31|ORBacus:ThreadPerRequest:Dispatcher| |220|0|4|0|BIlaunchpad.WebApp|kesbidev1:1360:29808.226444:1|CMS.runJobs|localhost:7464:46240.2297245:1|.run|kesbidev1:27388:31.8:1|CloXJt41fUzFhxj0AAfDFl83747d|||||||||com.businessobjects.js.child.processingsubsystem.aoprecalc||
Document does not contain OLAP connections |9F4990DEBF5E47FCBC95E3A4FAE732F31|2016 01 21 14:13:08.149|+0200|Error| |==|E| |jobserver_KESBIDEV1.AdaptiveJobServer_AOSchedulingService_CHILD0|27388| 31|ORBacus:ThreadPerRequest:Dispatcher| |222|0|4|0|BIlaunchpad.WebApp|kesbidev1:1360:29808.226444:1|CMS.runJobs|localhost:7464:46240.2297245:1|.run|kesbidev1:27388:31.8:1|CloXJt41fUzFhxj0AAfDFl83747d|||||||||com.businessobjects.js.child.processingsubsystem.aoprecalc||
failed to retrieve connection information.
Please let me know if anymore info needed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.