Hello everyone,

We have a strange issue with one of our jobs after we completed our upgrade to version 6.1.5 from 5.6.x. We also upgraded from Windows server 2003 to 2008. There is a job that executes in the background and attempts to generate an Excel report for some users. There is a popup error message from Excel saying "Not enough system resources to display completely." Once I click the 'ok' button the script continues on and generates the report. Based on some initial research on the internet, users have reported this error after attempting to interact with an existing report.

I am able to RDP onto the server with the credentials used that execute the task and run the program just fine from the session (report gets created successfully with no errors). So the issue appears to be with how we are calling the job?

I tried changing the job from running in the background to running in the foreground which seemed to work however I'm not sure if that is the best solution as we would need to have the user logged on all the time with the VCTray running as described here: http://www.visualcron.co...m.aspx?g=posts&t=849 

Does anyone else have suggestions on how we can get this job to execute as a background task? If not, I will pursue the option of running it as a foreground task. Before we tried testing with the foreground option we changed the local security policy of the server to disable the requirement of ctrl-alt-del as shown in the picture.

Thanks,

Peter

Hi,

there are some differencies between 2003 and 2008. In 2008 (like from Vista and forward) interactive applications (with window) have been moved to a closed environment. I think it is something there that limits excel.

What are you trying to do in Excel? Run a macro? Recalculate something?

---

Hi,

there are some differencies between 2003 and 2008. In 2008 (like from Vista and forward) interactive applications (with window) have been moved to a closed environment. I think it is something there that limits excel.

What are you trying to do in Excel? Run a macro? Recalculate something?

This particular program creates charts within the report as well as put formulas for the end users into the workbook. We have many other jobs that create Excel reports with no problems so I looked at this particular program and this seems to be the biggest difference as the others do not use charts or formulas.

Some users on internet forums report this error if the workbook contains multiple sheets with different zoom levels. I checked the report and all are the same. At this moment the program is running fine using the option of running as a foreground task. I'm thinking that I may add some debugging code into the program to see where exactly it throws this error message. The other option I'm considering is generating a new, blank workbook and copying the data as some people were able to get this problem resolved by creating a copy of the report.

Hello,

I have found the issue with the program. I narrowed the problem down to a specific block of code in the program. After adding a ‘loExcel.DisplayAlerts = .F.’ at the top of the ‘FOR’ loop the program completed successfully. The strange thing is the display alerts was already set to false so somehow when the sheet objects within the code block were added/copied in a workbook it appears the setting doesn’t carry over. This is what threw me off for a while as I figured it wouldn’t be a problem with the code itself since I assumed that display alerts setting was universally applied to the loExcel object.

So hopefully if anyone sees this message/issue in a future program, simply adding this will prevent these headaches.

Thanks,

Peter

Edit: Please mark this thread as 'resolved.'

Thanks for the update Peter!

---