Problem with memory errors when running nvision on the process scheduler. The problem may be seen during high volume times when multiple nVision reports are being run.
The following information is gathered from the Red Paper out on Customer Connection titled, “nVision in the PeopleSoft Internet Architecture”. For more information you can reference that Red Paper. The applicable information from there for this issue is below:
Please check the following information. Please go thru all the documents very carefully and we recommend that an NT Admin perform the following tasks.
1)Apply Microsoft hotfix for the GDI resource leak problem in Windows operating system.
The Report server used for testing nVision reports crashed over a period of time ( 24- 48 hrs), and the problem was due to a GDI resource leak in windows operating system. You may also experince GUI painting issues and the system not responding to mouse events. This is a Microsoft issue and a hot fix is available from Microsoft. Please refer to Microsoft KB article Q826518 for more details.
To get the hotfix, call Microsoft at 1-800-936-4900, select option 3 and request hotfix Q826518. (specify Windows 2000 or XP)
2)Increase the shared section memory heap for running multiple nVision reports on background mode.
When nVision runs in interactive mode (foreground), it runs within the 3 MB of desktop heap and in non-interactive (background) mode it runs within 512 KB of desktop heap. When nVision and Excel run, they use a fair amount of desktop heap space. Programs run in non-interactive mode gets only 512 KB of heap size and this may not be sufficient if you run large number of programs. If there is not enough heap for running nVision reports on the background mode, some reports may not run, hang during the initial stage, and may block other nVision reports.
For running the same reports in foreground and back ground mode, you need to increase the shared section value for the background heap to the same as the foreground value. The shared section heap value used for testing 30 nVision reports and other applications was 3072.(3 MB)
The shared section value needs to be changed in the system registry and users will have to change this value using registry editor. The MS article 126962, explains this in detail and contains instructions for changing the shared section value. http://support.Microsoft.com/default.aspx?scid=kb;EN-US;126962
A problem incident has been opened in PeopleTools to automate this change and will be addressed in a future release.
The following section explains the registry values for shared section memory.
Windows uses different shared section memory heap for interactive and non interactive programs. The size of the desktop heap allocated for a desktop associated with a window station is stored in the registry, in:
The default values are,
SharedSection=1024KB (common), 3072KB (interactive), 512KB (non-interactive)
· The first SharedSection value (1024 KB) is the shared heap size common to all desktops.
· The second SharedSection value (3072 KB) is the size of the desktop heap for each desktop that is associated with the “interactive” window
· The third SharedSection value, (512 KB ) is the size of the desktop heap for desktops created in noninteractive window stations.
3) Change the Performance Options to optimize performance for Background services.
By changing this setting, the system will assign equal amounts of processor resources to all programs. (Foreground and Background)
To change the value of this entry, in Control Panel, double-click System, click the Advanced tab, click Performance Options, and then, in the Application response section, select either Applications or Background services.
Clicking Applications sets the value of this entry to 100110, and provides for short, variable length processor intervals in which foreground processes get three times as much processor time as do background processes.
Clicking Background services sets the value of this entry to 011000, and provides for longer, fixed-length processor intervals in which foreground processes and background processes get equal processor priority.