Windows Server 2000 SP4 TS, PS4+R04 on 4.5 farm, Terminal Services SoftGrid client 4.1.0.56. 4gb ram, dual 1600mhz single core processors in an older pizza box. 1.6gb sequence, our largest by a gig or so.
- Code: Select all
[05/30/2008 09:31:29.450 MIME INF] {tid=3C94:usr=ProblemUser}
Updated MIME information from myserver:554/
[05/30/2008 09:32:07.888 OSDF INF] {hap=564:app=AppName P:tid=3DD8:usr=ProblemUser}
Elapsed time for synchronous pre-launch script wscript \\myserver.mydomain\content\AppName\HideDos.vbs xcopy \\anotherserver\stuff\textfile.txt.txt V:\AppName.123\AppName\ /y: 38.672 seconds
[05/30/2008 09:32:08.091 SWAP INF] {hap=564:app=AppName P:tid=3DD8:usr=ProblemUser}
Elapsed time for launch: 46.234 seconds
[05/30/2008 09:32:09.591 SWAP INF] {hap=574:app=AppName P:tid=1B54:usr=ProblemUser}
Elapsed time for upload: 0.000 seconds
[05/30/2008 09:32:10.450 OSDF INF] {hap=574:app=AppName P:tid=1B54:usr=ProblemUser}
Elapsed time for synchronous pre-launch script wscript \\myserver.mydomain\content\AppName\HideDos.vbs \\myserver.mydomain\content\AppName\tempdir.cmd: 0.859 seconds
[05/30/2008 09:32:20.888 OSDF INF] {hap=574:app=AppName P:tid=1B54:usr=ProblemUser}
Elapsed time for synchronous pre-launch script wscript \\myserver.mydomain\content\AppName\HideDos.vbs xcopy \\anotherserver\stuff\textfile.txt.txt V:\AppName.123\AppName\ /y: 10.438 seconds
[05/30/2008 09:32:21.419 SWAP ERR] {hap=574:app=AppName P:tid=1B54:usr=ProblemUser}
After the launch, SystemGuard could not resume the process (last error 2).
[05/30/2008 09:32:21.622 TRAY ERR] {tid=1E8C:usr=ProblemUser}
The SoftGrid Client could not launch AppName P.
An unexpected error occurred. Please report the following error code to your System Administrator.
Error code: 410038-0B016104-0000040F
I'm a little concerned that 09:32:07.888 takes 39 seconds given it's a 5mb text file on a server in the same data center, but alright.
That the same script launches again at 09:32:20.888 really bothers me, but okay, not the main issue here.
It's the 04-0000040F that I've never seen before and can't find any information on. Rather, I've seen it, but it fixed itself on next launch. I'm starting to suspect that the this happens when a script takes too long and the user tries to launch the app again.
Thoughts?
