The big windows 3gb switch mystery.

Last couple of days I was called to give a solution for an Hyperion 9.3.x problem.  When they started the ‘Reporting’  server they got a message ‘The system cannot log you on due to the following error: Not enough resources are available to complete this operation. Please try again or consult your system administrator’

 

 

Everything was working fine but for some reason they could not start the Reporting services.  After a while when we wanted to logon into the server to investigate, we could not get in.

So we did a search (for 2 days).

The problem was that there were some changes been made in the ‘Security updates by Microsoft’ (incl. service packs).

When you install drivers, patches, SP or anything. Windows will consume a bit more memory. Because there had been a modification in the ‘boot.ini’ and windows only had 1 GB to use, there was a threshold  being overwritten.
So every time when you login the resources weren’t there.

We had to remove this option in order to make Windows server 2003 accessible for us and to make Hyperion start.

So whenever you are planning to update drivers, apply patches or anything make sure that you have enough resources available. Also consider the use of PAE (http://msdn.microsoft.com/en-us/windows/hardware/gg487512)

JMSExceptions:045047 (Hyperion can't start up)

It is possible that Hyperion / Weblogic does not start anymore. This can have several causes eg:
• There is a deploy of web server made through the Configuration Tool (extra deployment)
• There is an extra tool installed in the weblogic server

ERROR<Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
Caweblogic.management.ManagementException: [Management:141266]Parsing Failure in config.xml: The following failures occurred:
-- [JMSExceptions:045047]The SubDeploymentMBean JRFWS_JMS_MODULE_SUBDEPLOYMENT_JRFWSJMSServer in deployment JRFWSAsyncJmsModule
can only be targeted to one JMSServerMBean because an entity that can only be targeted to a single JMS server (for example a queue,
topic or quota) has a sub-deployment-name element with value JRFWS_JMS_MODULE_SUBDEPLOYMENT_JRFWSJMSServer
at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:127)
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:41)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)

Sollution Locate the config.xml file in the directory:
D:\Oracle\Middleware\user_projects\domains\EPMSystem\config
(at the Weblogic server (HSS)) Edit this file and look for the following:

<sub-deployment>
<name>JRFWS_JMS_MODULE_SUBDEPLOYMENT_JRFWSJMSServer</name>
<target>FMWebServices</target>
</sub-deployment>

Replace it with the following (only the word ‘FMWebServices’ to ‘JRFWSAsyncJmsServer’)

<sub-deployment>
<name>JRFWS_JMS_MODULE_SUBDEPLOYMENT_JRFWSJMSServer</name>
<target>JRFWSAsyncJmsServer</target>
</sub-deployment>
Try again to start Hyperion.