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%
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)
Please log in to answer
Posted by:
kkaminsk
15 years ago
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.
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
15 years ago
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.
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
15 years ago
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.