|
| | | Forum Newbie
Group: Forum Members
Last Login: 6/17/2010 2:56:22 AM
Posts: 5, Visits: 43 |
| | Hi! We're encountering an issue with prism Deploy :
after 30 actions (/runs in script tasks, command tasks or package tasks), an error appear in C:\Documents and Settings\All Users\Application Data\Prism Deploy\PrismXL\ClientLog.XML, wich says ***File not found. The 30 firsts actions are ok, but once the error appears every following action also fail.
The scripts or tasks are launched with another account than the current logged user ("runas this account" option).
A workaround is to close an reopen the session, wich will execute the next 30 actions in queue (after 30, the error appears again). To troubleshoot this issue we've made a basic script wich execute about 200 times the same action : /run /continue write.exe
/run /continue %comspec% /c tskill write
/run /continue write.exe
/run /continue %comspec% /c tskill write
... The result (in french): ...
/Run /Continue write.exe
/Run /Continue C:\WINDOWS\system32\cmd.exe /c tskill write
/Run /Continue write.exe
/Run /Continue C:\WINDOWS\system32\cmd.exe /c tskill write
/Run /Continue write.exe
***Le fichier n'existe pas
/Run /Continue C:\WINDOWS\system32\cmd.exe /c tskill write
***Le fichier n'existe pas
...
The error appears only if the script is assigned through the Prism Console, not if launched manualy.
Tested with Prism (Server and Client) versions 8 and 10 (also version 10.5.0.86)... Does anyone have an idea? |
| |
| | | 
Supreme Being
Group: Moderators
Last Login: 2/12/2011 11:11:06 PM
Posts: 742, Visits: 1,211 |
| I am not aware of any restrictions as far as the limit of commands you can place within a Prism Script. I have tried testing your example but it pushes out successfully.
I did note however that the process for write.exe is wordpad, so you are attempting to kill a process that doesn't exist which could have some problems but even with your exact syntax my script ran fine.
I also tried testing just opening 200 Notepads/calculators/word pads to see if I could replicate your problem but I was unsucessful.
My script looked like this:
/run /continue calc
/run /continue notepad
/run /continue write
/run /continue %comspec% /c tskill calc
/run /continue %comspec% /c tskill notepad
/run /continue %comspec% /c tskill wordpad
I copied those set of commands 50 times and let it run on 5 seperate computers. Each of those computers ran the script successfully.
The only thing I can think of that might cause this is the OS might be getting overloaded with the process requests since you are not telling it to wait, which would be a bottleneck of the machine. Have you tried testing it on different machines, or maybe on a freshly installed OS?
New Boundary Technologies Support
support@newboundary.com |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 6/17/2010 2:56:22 AM
Posts: 5, Visits: 43 |
| | Hi, I tested your script, the error is the same on different machines...
Windows XP (existing machine, virtual machine or from scratch install) and a Windows Server 2003. Have you tested your script by deploying it through the console with "Run as this account" option?
Because manually, the script ends without any error... |
| |
| | |
Supreme Being
Group: Moderators
Last Login: 2/12/2011 11:11:06 PM
Posts: 742, Visits: 1,211 |
| I have also tested having the client machine logged on as a non admin user, and setting the task to "run as specified user" with a user that has administrative rights on that computer, as well as has access to the network share where the script is located.
I have attached some screen shots of my testing. From the client machine, you can see some of the command prompt windows opening and closing very fast. I checked the client log files and it shows that the script played fine with no errors reported anywhere.
It seems very strange that you are running into this issue as I have not been able to replicate it at all. I know that we have several customers who use scripts extensively, many of which are well over 50 commands so there has not been any concern that I know of regarding a limit in regards to Prism Scripts.
New Boundary Technologies Support
support@newboundary.com
|
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 6/17/2010 2:56:22 AM
Posts: 5, Visits: 43 |
| | Hi, I noticed you have done your tests on Windows 7...
Tried the same, and it works! Strange problem :-) The problem is that about 95% of our computers are running Windows XP SP3...
Do you have tested your script on a Windows XP machine? |
| |
| | |
Supreme Being
Group: Moderators
Last Login: 2/12/2011 11:11:06 PM
Posts: 742, Visits: 1,211 |
| I tested the script with a WinXp SP3 machine and it ended up failing after 32 commands just like in your case. I spoke with a few of our developers and it appears that Xp had a limit of 32 nested command shells running simultaneously. So this is a limit of the operating system and not a Prism limitation.
If you wanted to get past that limit, you'd have to specify the /wait switch instead of the /continue switch, which will just wait for that certain process to complete before moving on to the next one.
New Boundary Technologies Support
support@newboundary.com |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 6/17/2010 2:56:22 AM
Posts: 5, Visits: 43 |
| We're already using the /wait switch, so I made a test script with about 50 times the following command :
/Run /Wait C:\WINDOWS\system32\cmd.exe /c ping -n 1 127.0.0.1These actions are not running simultaneously (verified with Process Explorer from SysInternals), but I have the same error again.
It seems like the 32 simultaneous nested shells limit is not the ploblem... Or something is wrong with the /wait switch :-) |
| |
| | |
Supreme Being
Group: Moderators
Last Login: 2/12/2011 11:11:06 PM
Posts: 742, Visits: 1,211 |
| I put together the same test you did on your windows XP machine and mine ran successfuly. I'm not sure if there is anything else in your environment that may be affecting how commands are getting run, but one idea would be to switch to some sort of Prism scripts with batch file integration.
My tests were on a completely clean Windows XP SP3 machine, creating a basic script task with no additional configuration. After deploying the script task I can see on the client computer that many cmd boxes pop up one after the other until all have ran. I attached a picture of the client log for that task.
New Boundary Technologies Support
support@newboundary.com
|
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 6/17/2010 2:56:22 AM
Posts: 5, Visits: 43 |
| | Are you sure you did your last test with the "Run as this account..." option? Because on your screenshot, the task seems to be launched by the current user...
That could explain why it works for you but not for us. |
| |
| | |
Supreme Being
Group: Moderators
Last Login: 2/12/2011 11:11:06 PM
Posts: 742, Visits: 1,211 |
| You were correct that I was running most of my tests as current user. I started testing them with Run as Specific User and I started getting the errors you were seeing. It seems that running as Current user is the best way to get these to run currently. Suggestions I have as a work around would be either having it run as current user or Local System account. If you must set it as a Specified user, then I would try integrating it with batch files to make sure that it doesn't hit the 32 command limit that seems to be the issue.
I have logged this as a known problem which will go under review by our developers.
New Boundary Technologies Support
support@newboundary.com |
| |
|
|