Hyperion Enterprise web error message

Question

Hi,
I am using Hyperion Enterprise 6.5 version, When i tried to enable web version of Hyperion enterprise web by browsing http:\\localhost\Heweb from the server
Server Error in '/HEWeb' Application.
Module not found:he.hecontainer
Object variable or With block variable not set.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.NullReferenceException: Object variable or With block variable not set.
Source Error:
Line 338:     ' Get the application list
Line 339:
Line 340: vtStatusCode = Application("EntAppObject").EnumAppsForLogon(vtAppListXML, vtStatusDesc)
Line 341:
Line 342: Dim domXML
Source File: C:\Program Files (x86)\Hyperion Solutions\Hyperion Enterprise\HEWeb\LogonMain.aspx Line: 340
Stack Trace:
[NullReferenceException: Object variable or With block variable not set.]
Microsoft.VisualBasic.CompilerServices.Container..ctor(Object Instance) +765074
Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateGet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean[] CopyBack) +538
ASP.logonmain_aspx.__Render__control1(HtmlTextWriter __w, Control parameterContainer) in C:\Program Files (x86)\Hyperion Solutions\Hyperion Enterprise\HEWeb\LogonMain.aspx:340
System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +115
System.Web.UI.Page.Render(HtmlTextWriter writer) +38
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +4240
Version Information: Microsoft .NET Framework Version:2.0.50727.3615; ASP.NET Version:2.0.50727.3601

Answer 1

Hi Rakesh,
1.) Please confirm you followed the steps below during your HEWEB initialization process? (The first time you enable HEWEB - the applications added need a long time to cache depending on their complexity.)
*How to Prevent Hyperion Entperise Web Components from Timing out and Dropping from Memory on HEWEB Server [ID 1134663.1]*
Modified 03-AUG-2010 Type HOWTO Status PUBLISHED
Applies to:
Hyperion Enterprise - Version: 6.5.0.0.00 and later [Release: 6.5 and later ]
Information in this document applies to any platform.
Goal:
What steps are required to prevent an application loaded into HEWEB from timing out and dropping from memory thus requiring users to wait for the application to re-load whilst the connect?
Solution:
In order to use Hyperion Enterprise Web (HEWEB) and Hyperion Smartview for Enterprise (HSE) the application you wish to connect to needs to be Enabled for HEWEB on the designated HEWEB server.
To enable an Application for HEWEB the designated HEWEB Server needs to have Microsoft Internet Information Server (MIIS) and ASP.NET installed.
If the HWEB component has never been installed, the Enterprise Installer needs to be run selecting the HEWEB option on the Install component list. Once selected and run the install. This will install the required version of HEWEB and ASP.NET.
If the HEWEB server has been installed, in order to Web Enable the application(s) required follow the steps below:
1.Login to Enterprise as a user with Admin Rights.
2. Enter the Application Module from the Enterprise Desktop.
3. Choose the Navigate menu followed by Server Administration.
4. In the Web Server pane select the Enabled check box.
Set the Web Server URL to read http://YOUR SERVERNAME.
Set the Session Manager, task Server and Web Application Controller to be just the server name.
Set the upload location to be a suitable folder on the server in which to store dataload files.
5. If using Hyperion Enterprise Reporting Web (HERW) as well as HEWEB:
Set the Server name for your HERW server in the Hyperion Enterprise Reporting Web Server.
6. Leave the number of connections set to 12.
7. Once these parameters are all set. Hit Apply.
Depending on your application size and complexity of your metadata, after a delay, three processes will start up and consume memory and CPU. These are HeAppController.EXE, HeDataController.EXE and HeAppMgr.EXE. The time taken is a function of application metadata complexity and NOT the amount of data within the application.
Once the HeAppController.EXE has settles to 0% CPU utilization and the process memory usage has stopped increasing the application has loaded into HEWEB and should be visible in the list of applications when you hit the link http://YOURSERVERNAME/HeWeb/default.asp from a browser.
If the application takes a very long time to load, the amount of time can be reduced with no adverse affect by editing the Applicationname.ini located in the application folder to include the line ENABLECACHEFORSMARTVIEW=”0” towards the end of the file.
After some time these 3 processes, HeAppController.EXE, HeDataController.EXE and HeAppMgr.EXE will drop from memory and if the line WEBAUTOSTART=1 is set in your server Hypent.ini file, these processes will re-load when a user hits the HEWEB server via a browser or makes a Smartview Connection attempt.
Note if the load process for your application takes a long time, the first users to hit the server will have to wait while the processes re-load.
This can cause user confusion and lead users to think the server is down!
To prevent these processes dropping from memory perform the following steps on your HEWEB server:
1. From the Start Run command run INETMGR to bring up Microsoft Internet Information Manager Console.
2. Identify the Default Application Pool in the left hand pane by drilling down into Application Pools.
3. Right Click on the Default Application Pool and select properties.
4. Find the re-cycling TAG and edit the value in Recycle work processes in minutes to a long period i.e. 28800 (20 days).
5. Find the Performance Tag.
6. DESELECT, Shutdown worker processes after being idle for (time in minutes).
7. Exit from the Web pools setting and close down INETMGR.
8. From the start button re-set IIS services by issuing the command IISRESET from the run box.
9. IIS will now re-start and then once initially called the process for HEWEB should not remain in memory for the duration of the period specified.
Note: Be wary of taking back-ups while the webserver connection are held open. It is advised that the internal Enterprise back-ups are used which will not be affected by the HEWEB process remaining active.
2.) In your previous post you mentioned that you followed all of the installation steps required for installing HE 6.5.1. Could you please confirm that this was a new installation? Or was this an upgrade from an older version?
Let me know how you get on.
G'Luck,
-David