Financial Reporting Studio Patching in 11.1.2.2

The client tools have been repackaged in 11.1.2.2. Instead of requiring a special bloated installer, they come packaged as a streamlined .msi installer package. This greatly simplifies the distribution and patching process. However, keep an eye out for updated client installers when patching.

For example, The newest version of the financial reporting client comes inside in the patches.
Patch 13997553: Patch Set Update: 11.1.2.2.300 for Oracle Hyperion Reporting and Analysis for Financial Reporting

The studio installer is in this directory: 13997553/files/install/bin/financialreportingstudio.exe 

It is required to uninstall the old version and re-install the new version on all client machines.

EIS Console Crashes When Opening

In 11.1.2.2 If you Install EIS on a standalone machine without Essbase Server, the console will crash with

Essbase Integration Services Console
"Unable to initialize Essbase."

This turns out to be because msvcr71.dll is missing from the PATH in startOlapbldr.bat.

To fix this,
Navigate to
\Oracle\Middleware\EPMSystem11R1\products\Essbase\eis\console\bin

Edit startOlapbldr.bat

Find the PATH line and change it to include %HYPERION_HOME%\ccr\bin at the END of the specified path but before the %PATH% directive. Yes... The location in the PATH does matter...

For instance:

set PATH=%HYPERION_HOME%\bin-32;%ARBORPATH%\bin;%HYPERION_HOME%\ccr\bin;%PATH%

The console will now start up.

DRM Console in 11.1.2.2 Crashes When Opening

Problem:
DRM Console will not open - Application Crash Details:

Description:
  Stopped working

Problem signature:
  Problem Event Name: APPCRASH
  Application Name: drm-server-console.exe
  Application Version: 11.1.22302.3
  Application Timestamp: 50464102
  Fault Module Name: KERNELBASE.dll
  Fault Module Version: 6.1.7601.17932
  Fault Module Timestamp: 503285c2
  Exception Code: e0434f4d
  Exception Offset: 000000000000caed
  OS Version: 6.1.7601.2.1.0.272.7
  Locale ID: 1033

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Resolution:

This was simply a mistake preparing the pre-requisites for the install...
Install .Net 3.5.1 Features in Windows 

Problem Accessing Windows Share on Node - BackConnectionHostNames

Windows 2008 R2 has some enhanced security which can get in the way of the Hyperion installation process. The problem is that the default settings will not allow network connections back to the node itself. For instance, if you create a windows share on a particular node, and then try to access the share from the same node, the connection fails. However, anywhere else on the network will be able to access the share.

This can come into play for the Windows Shares for FDM, Reporting and Analysis, and the Share for the LCM import_export assuming you are using the Hyperion servers to host the shares, rather than a remote share location. Additionally, you will notice that if you log into a server and try using the client tools to connect to Hyperion it will fail on one node, but work on the others. For instance, if you open FDM Workbench and try to connect to FDM it may show "Backup Load Balance Server is being used!". This is because the server cannot talk back to itself to connect to the primary load balance server.

The Solution:

http://support.microsoft.com/kb/926642
Error message when you try to access a server locally by using its FQDN or its CNAME alias after you install Windows Server 2003 Service Pack 1: "Access denied" or "No network provider accepted the given network path"

Additional info:
http://serverfault.com/questions/23823/how-to-configure-windows-machine-to-allow-file-sharing-with-dns-alias

Add the new key "BackConnectionHostNames" as a Multi-String Value in this registry path:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0

Enter the different names for the node using a newline as a separator:

server1
server1.fullyqualified.com