Unable to login to 360Suite after upgrading BusinessObjects

Unable to login to 360Suite after upgrading BusinessObjects

Symptoms

After upgrading SAP BusinessObjects (BOBJ), the client receives an error and cannot log in to 360Suite, while they can still log in to the Admin Console.

How to replicate the issue

  1. Upgrade the BOBJ environment to a newer version (BI platform update/upgrade).

  2. Open the 360Suite web application.

  3. Enter valid user credentials and attempt to sign in.

  4. Result: login fails with an error (while Admin Console access still works).


Cause

This issue commonly occurs due to compatibility differences between BOBJ Java libraries used by the upgraded environment and the Java libraries currently referenced/used by 360Suite.

After a BOBJ upgrade, 360Suite must use the BOBJ SDK Java libraries that match the upgraded BOBJ installation. If 360Suite still points to older libraries (or incompatible web-tier libraries), the 360Suite login can fail even though Admin Console access may remain available.

Resolution

Re-run the 360Suite setup and re-point to the upgraded BOBJ Java libraries

  1. Launch the 360Suite setup for the same 360Suite version currently installed (no 360Suite upgrade required).

  2. When prompted for the SAP BusinessObjects Libraries path, make sure it points to the new/upgraded BOBJ Java/SDK libraries (from the upgraded BOBJ environment, not outdated paths).

  3. Complete the setup.

  4. Restart the relevant 360Suite services (and/or the application server) and retry logging in.

Additional information 

Refer to the 360Suite online documentation sections covering prerequisites/installation / setup for guidance on selecting the correct SAP BusinessObjects SDK Java libraries path and related compatibility notes.

https://360wp.documentation.wiiisdom.com/en_US/getting_started/prerequisites

    • Related Articles

    • 360Eyes for SAP BusinessObjects – Complete List of Parameters

      360Eyes for SAP BusinessObjects – Complete List of Parameters This document provides a full list of all configuration parameters available in 360Eyes for SAP BusinessObjects. It serves as a centralized guide for understanding every option that can be ...

    • Unable to start 360Suite when tomcat uses slf4j

      Symptom tomcat root page is available /360suite url returns 404 error in tomcat/logs/localhost-{date}.log an error appears on 360Suite startup 03-May-2021 07:51:22.858 SEVERE [localhost-startStop-1] ...

    • SLA Unable to Connect to CMS (FWM 01009)

      Overview When using 360Suite Semantic Layer Agent (SLA), the task fails with a RemoteException indicating a communication error with the CMS. This issue typically occurs after installing SLA on a Windows host and configuring RMI settings, even when ...

    • Promotion & Backup of BusinessObjects UNX Universes and Users — Design Behavior and Synchronization Logic

      Overview When promoting or backing up UNX universes and users with 360Plus, you may notice that UNX files are always overwritten and that user timestamps change frequently. This behavior is by design on the BusinessObjects side and cannot be modified ...

    • Unable to create system preferences directory

      Condition The Apache Tomcat server log returns the following error on start-up: Could not create system preferences directory. System preferences are unusable Solution Cause This error occurs if the server is started using a user or service account ...