cancel
Showing results for 
Search instead for 
Did you mean: 

Analysis for Office 2.2: "The BoeSession Service is not logged in yet"

Former Member
0 Kudos

We have two different local installations of Analysis for Office 2.2 connecting to the BO Launchpad 4.1.SP4.  One plug-in is installed in Office 2013 on the client and the other in Office 2010.  The Office 2013 pc has no issue connecting to the BO Launchpad folders while the Office 2010 pc with the same installation consistently receives the error message "The BoeSessionService is not logged in yet.."  Both attempts are using the Business objects Administrator Enterprise password and the same URL to connect to the Launchpad.

What are the possibilities for the cause of the error on one machine and not the other.  The PC receiving the error can connect directly to the BW to view BEx queries with Analysis for Office.  It just cannot log into the BO Launchpad URL in the same way the other PC with the Office 2013 installation can.

Zack93

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Of course it's Monday.

Users were logging in no problem last week but today 2 of them are encountering this error trying to log in for a datasource.

We've patched up to version 2.2.0.51997 (not sure what the patch level is but should be p2 or above)

Any other resolutions I could try?

thanks.

TammyPowlas
Active Contributor
0 Kudos

Neil - it appears that this may be a known issue as SAP release SAP Note 2266124 just last week - see https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F6465...

(hope that link works) or try https://websmp130.sap-ag.de/sap/support/notes/2266124 - SMP logon - looks like it is planned for a patch

Matthew_Shaw
Product and Topic Expert
Product and Topic Expert
0 Kudos

I found the same issue. I've tested this with a version of the product not yet available to customers and it is fixed. That version is Analysis for Office version 2.2 Support Pack 2. I understand this is due to be released around the middle of March (subject to change) for customers.

If you get an error "Could not connect to CMS" then please ensure you specify the port in the 'System' field. For example:  MyCMSServername:6400

The 'System' field is accessible on the Logon page by pressing "Options>"