Cannot Login To Financial Reporting (FR) Server From Financial Reporting (FR) Studio On A Client Desktop

Cannot Login To Financial Reporting (FR) Server From Financial Reporting (FR) Studio On A Client Desktop [ID 1111287.1]
		Modified 26-OCT-2010     Type PROBLEM     Status PUBLISHED

In this Document
  Symptoms
  Changes
  Cause
  Solution

---

Applies to:

Hyperion BI+ - Version: 11.1.1.0.00 to 11.1.1.3.00 - Release: 11.1 to 11.1
Information in this document applies to any platform.

Symptoms

When using the Financial Reporting Studio, you are able to access different Financial Reporting Reports Servers as long as your Financial Reporting Studio version is the same as the Financial Reporting Server.

As an administrator, if you want to access two separate Financial Reporting Reports Servers, you would just change the server name when logging into the Financial Reporting Studio. 

Due to the complexity on an installation, certain files may or may not get laid down if the installation is not done properly causing connection issues. 

Changes

Tried to reconfigure the Financial Reporting Reports Server from your desktop by running the configuration utility.

OR

Installed a new version of Financial Reporting Studio over an existing one.

Cause

At some point in time you, as an administrator, needed to configure the Financial Reporting Server and you inadvertently did it from your Desktop machine.  This should only be done by someone with admin privileges, and only on the Financial Reporting Server.

When the configuration tool was run on the Financial Reporting Studio machine, it created a reg.properties file which should only reside on the Financial Reporting Server.  The Financial Reporting Studio on the client machine reads it own reg.properties file instead of the one on the Financial Reporting Server.

OR

You do not have the same Financial Reporting Studio version on your client as the Financial Reporting Reports Server you were trying to connect to.

Solution

1 - You are trying to connect to 2 different Financial Reporting Reports Servers from one Financial Reporting Studio, one server name works but the other does not you may get one of these or both errors:

a) "Unexpected error occurred"

Then as soon as you close that error, you immediately get this error:

b) "DatasourceIDLoginLoadDatasoureceName Error: -2147467259 Error Loading DatasourceList to Repository"

• If you only see error b) then go to Step 2.
• If you only see error a) then go to Step 3. 
• If you see both errors a) and b) then you need to check in hyperion\common\config\9.5.0.0 for the reg.properties file on your Financial Reporting Studio machine.  If you find this file there then rename it to something different and save it.  Then go back to make sure the file has been renamed.  If you do not find this file, then refer to Doc ID 1109585.1 for more Financial Reporting Studio connectivity troubleshooting.

2 - If you only see error b), locate the HReports.jar and Foundation.jar files on the Financial Reporting Reports Server and the client machine and do a comparison of size, date and location. In versions 11.1.1.1 and 11.1.1.3: The HReports.jar file is located in \Hyperion\products\biplus\lib. The Foundation.jar file is located in \Hyperion\products\Foundation\workspace\lib. In 11.1.1.2: The HReports.jar file is located in \Hyperion\products\biplus\lib. The Foundation.jar file is in both lib folders -- the one for Foundation and the one for BIPlus.  Both of these files need match exactly in size, date and location.  If they match exactly, then refer to Doc ID 1109585.1 for more Financial Reporting Studio connectivity troubleshooting. 3 - If the HReports.jar and the Foundation.jar file do not match exactly in size, date and location on the Financial Reporting Reports Server and the desktop Financial Reporting Studio, then:

a. Rename the the HReports.jar and the Foundation.jar on the client machine. b. Stop all Hyperion Financial Reporting services on the Financial Reporting Reports Server. c. Copy both of these files over from the Financial Reporting Reports server to the same locations on the client machine. d. Restart all Hyperion Financial Reporting services on the Financial Reporting Server. e. Go back to the Financial Reporting Studio log in page.  Log in testing the different Financial Reporting Servers to make sure they work properly.  f. If they do not, refer to Doc ID 1109585.1 for more Financial Reporting Studio connectivity troubleshooting.

Related Products Middleware > Business Intelligence > Hyperion Query & Reporting > Hyperion BI+ Keywords LOGIN; STUDIO Errors 467259 ERROR

Back to top