/build/static/layout/Breadcrumb_cap_w.png

Dot net Application error after sequencing

I have sequenced couple of .net application without any error, but having problem with one application, it is an inhouse application.

The application launches fine during sequencing, but when launching from the XP Client / Win 2k3 TS i get the following error and this error is from the application but not from softgrid.

"NOT ENOUGH MEMORY RESOURCE TO PROCEED. System Resource: 0% GDI Resource: 0%

0 Comments   [ + ] Show comments

Answers (3)

Posted by: kkaminsk 16 years ago
9th Degree Black Belt
0
1) Run the lastest code available on the client and sequencer. If you are doing a 4.5 POC the 4.5 RC1 code is supposed to have better support.

2) Look at this article. http://support.microsoft.com/kb/939084

3) You can profile the application with dependency walker but I haven't had the best luck getting meaningful information out of that when it is a SxS issue.
Posted by: bheers 16 years ago
Second Degree Blue Belt
0
Seems like the application is hardcoded to run from C:\Program FIles\APP Name.

i tested it out by copying the application exe to the C:\Program Files\App Name directory, and launch the virtual application the application launches fine.
Posted by: kkaminsk 16 years ago
9th Degree Black Belt
0
So you are copying the EXE to the physical location then bringing it into the virtual environment via the OSD?
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ