Home » Developer & Programmer » Forms » FRM-92101: There was a failure in the forms server during startup (forms 6 to 10g Migration)
|FRM-92101: There was a failure in the forms server during startup [message #397839]
||Tue, 14 April 2009 03:00
Registered: October 2008
I deployed my forms in the Application server and trying to launch with the URL.It is working fine for some time..if any error occurs in the forms during testingits giving the error message that "there was a failure in the forms server,this is due to invalid configuration,see webserver log for details."This error is recurring even if i try to reopen the browser or restart forms services in App server.
This also happened when i am trying to open another application by editing the url of an opened application.
The problem is sometimes resolved automatically when the session expires.And troubling me again when i try to run it.
I guess this is the problem related to the session setting in App server,Not shure .The problem sometimes getting resolved when i leave the application untouched.So I need help on this..What needs to be set in application server..
|Re: FRM-92101: There was a failure in the forms server during startup [message #431887 is a reply to message #431639]
||Thu, 19 November 2009 17:51
Registered: August 2009
Finally i solved the problem and here is the 2 step solution.|
1. Change the property setting for the iasformsservice in the windows services to
"[x] Allow service to interact with desktop"
This forces the Apache Service (Forms 6i) or the Oracle Process Manager Service
(Forms 9i and above) to use the IO Desktop heap which is larger than
the Non-IO Desktop heap by default. The term "Desktop", here, is not to be
confused with the normal Windows desktop, which holds your icons and your
background, etc. In this context, it is Microsoft terminology for an area of
2. Modify the appropriate variable in the registry. This should not be done
- A backup has been made of the registry. Any error in modification of the
registry can render the system unusable.
- Solution 1 has been tested and has increased the number of processes
that will run successfully.
The following information applies to Windows NT, Windows 2000.
From the HKEY_LOCAL_MACHINE sub tree, go to the following key:
Select the Windows value.From the Edit menu, choose String. Increase the
SharedSection parameter. SharedSection specifies the system and desktop
heaps using the followin g format:
The default values are 1024,3072,512
modified values are 1024,20480,5112
All the values are in kilobytes (KB).
xxxx = System-wide Heapsize. There is no need to modify this value and
it is ignored for the rest of this discussion.
yyyy = IO Desktop Heapsize. This is the heap for memory objects in the
zzzz = Non-IO Destop Heapsize. This is the heap for memory objects in
the Non-IO Desktop.
If you change these values, you must reboot the system.
Programs that get run as a service or which are spawned from a service fall
into the Non-IO Desktop, and therefore consume memory from that heap. All
other programs, such as those run from an icon or from a command line, or get
spawned from those, consume memory from the IO Desktop heap.
For server-style applications, such as a database, or Forms, a service has
the advantage that a user can logout and the program continues to run.
If you can't run any more processes, then you should increase the relevent
heap. Using the Forms examples in this bug, if you start Apache / Oracle Process
Manager from the command line, then it consumes memory from the IO Desktop heap.
Then for each user, there is a Forms runtime process spawned, which also
consumes memory form the IO Desktop heap.In the case of this bug, the memory
ran out after 483 users. The solution would be to increase the relevant heap.
As stated earlier in this bug, when it was changed to 5112 KB (from the default
of 3072 KB), more than 700 users were able to run concurrently. Note that
changing the Non-IO Desktop heap (the 512 KB) would achieve nothing in this
The converse is also true. If the Apache / Oracle Process Manager process were
started as a service, then the third value, Non-IO Desktop heap, would have to
have been increased.
The values are recommended to be a multiple of 512, but this isn't necessary.
There is a hard limit of 48 Mb, which is the total heap size for Windows. But
it seems unlikely that you will need to go this high.
If you increase the Non -IO Desktop heap and your server is dedicated to Forms
or some other server process , then you can safely decrease the IO Desktop heap
since that is just wasted. This isn't necessary, though.
In summary, if you are hitting this problem where your server can not create
any more processes, you should increase the heap size of the either the IO
Desktop or the Non-IO Desktop. The correct one depends on how you run your
application, whether from a service, or from an icon or command line.
You have to restart the all services from Oracle AS, after saving the changes.
This is an Operating system limitation on the heap sizes
Current Time: Sun Jan 22 04:01:00 CST 2017
Total time taken to generate the page: 0.08734 seconds