cube (urgent)

[raju111]

I am trying to create a powerplay report(ppr file) from cube(mdc file) on server.While draging and droping dimensions and measures it is saying out of memory.The application is not responding.Then i am killing the session.Plz help me in this issue.Cube size is 8 mb.
I am working on win-NT with ep series7.
Thnaks,
Noothan

 

[jamesdb]

Make sure you have sufficient space on the server's directory you're working in. Also on your PC go to C:/temp and delete any large temporary files that may have been produced by Cognos. These temp files will eat up all free space on your C drive, and Cognos by default uses your C drive temp folder. This happens for Impromptu reports too. If you have Cognos installed on your C drive and its creating reports on your C drive you may want to reinstall it on your D drive etc to free up space on your drive, which is probably limited to 2 GB. And empty your recycle bin. Here's an excerpt on space problems:
Memory could not be read
Problem Description
Error
Impuser.exe caused an Application Error
The instruction at 0x005972f1 reference memory at 0x0000000000: Memory could not be read.
This error occurs when you are attempting to create a report in Impromptu on Windows NT.
The following error messages may also occur:

In Windows 95/98:
<Application name> has caused an illegal operation
and will shutdown.
<Application name> has caused an invalid page fault in module
<UNKNOWN or name of a DLL file> in address ....
(followed by a list of memory dumps)

In Windows NT: Dr. Watson error message
An application error has occurred...
<IMPUSER.EXE or IMPADMIN.EXE> exception access violation
(0x########), address 0x#########...
(may be followed by a list of memory dumps)

In both Windows 95/98/NT:
System Process - Out of Virtual Memory
Your system is running low on virtual memory.
Please close some applications.
You can then start the System option in the Control Panel
and choose the Virtual Machine button to create an additional
page file or to increase the size of your current paging file.


Solution Description
Confirm that the latest Service Pack from Microsoft has been installed for Windows NT. Contact your system administrator for information on the Service pack in use on your system.
These error messages are also indicative of a resource issue. If the &quot;memory could not be read&quot; error message is accompanied by the other error message, note the details, specifically any file(s)listed, and search the Cognos Knowledge Base under the filename provided.

1. Does the error message occur:

a. only when working in Impromptu when other applications and/or background processes are running?
b. only when working in Impromptu as the only application running on the system?
c. with other applications as well?

This may determine the system's stability. If only a. and c. are true, the system resources may be causing this problem while Impromptu is running. Contact the system administrator to confirm the system resources are functioning correctly. Instructions in 4. through 7. are related to troubleshooting the system.

If only b. is true, be sure to follow instructions outlined in 2. and 3.

Note: Follow all instructions below to ensure optimal performance of your system when running Impromptu.

2. Free disk space on the system: make sure that the following temporary paths are set to the same location that is pointing to a hard drive with ample free disk space. Refer to Knowledge Base Documents 59706 & 63405 for further information.

Cognos.ini
[Services]
Temporary = C:\Temp

Impromptu.ini
[Default Directories]
Temporary Data Path= C:\Temp

For Windows 95/98, add the following to the Autoexec.bat* and reboot the system:

SET TEMP=C:\Temp
SET TMP=C:\Temp

*Make there is only of copy of this file on the system. It should be located in the root of the local hard drive of the operating system, usually C:\. Rename all other files with this exact name to Autoexec.old.

For Windows NT, User Variables:

On the Start menu, select Settings and open the Control Panel. Double-click the System icon.
On the Environment tab, set the following variables:

TEMP=C:\Temp
TMP=C:\Temp

3. RAM on the system: make sure that SortMemory has been increased from its default value of 512 to a value [multiple of 512] that is less than a quarter the RAM. Refer to Knowledge Base Document 72301 for further information.

4. Display settings: on the Start menu, select Settings and open the Control Panel. Double-click on the Display icon. On the Settings tab, change the settings to 256 colors and resolution of 800x640.

5. Windows NT:

a. Service Pack: On the Start menu, select Programs and click on Administrative Tools. Open Windows NT Diagnostics and click on the Version tab. If this Service Pack has been recently installed, re-install it and/or contact Microsoft Technical Support.

Virtual Memory: On the Start menu, select Settings and open the Control Panel. Double-click on the System icon and open the Performance tab. Increase this value to observe if the error message no longer occurs. If the error no longer occurs, it is recommended to contact the system administrator to investigate a virtual memory issue.

b. Reboot the system and run Impromptu in VGA mode. If the errors still persists, this may be an indication of bad or corrupt RAM, contact the system technician. If the errors do not occur in this mode, there may be a memory conflict with other applications and/or drivers, such as video or printer. Reboot in normal or default mode and close all applications before launching Impromptu.
Try installing a different video and/or printer driver to see if this resolves the issue.

6. Windows 95/98:

a. Run Scandisk and Defrag

b. Reboot the system and run Impromptu in VGA mode. If the errors still persists, this may be an indication of bad or corrupt RAM, contact the system technician. If the errors do not occur in this mode, there may be a memory conflict with other applications and/or drivers, such as video and printer. Reboot in normal or default mode and close all applications before launching Impromptu. Try installing a different video and/or printer driver to see if this resolves the issue.