|
|
|
|
Group: Forum Members
Last Login: Tuesday, February 19, 2013
Posts: 26,
Visits: 65
|
I have a simple remote command to run taskkill on command prompts from the 'Execute Remote Command' tool within VNC Manager:
taskkill /im cmd.exe /F /T
Before 6.8.14 I could use this command in my lab and get an error which I would ignore in which it would try to perform a taskkill on the window that initiated the taskkill command. With 6.8.14 I can still use the command but it hangs with 'In operation' until I try to cancel. This limits me to running only 20 at a time, the maximum value I can use for 'Number of threads'. It is probably an unintended consequence of the ability to cancel commands that are 'In operation' which is new in 6.8.14. Is there something that can be done to fix this issue?
Thanks,
Greg
|
|
Post #4196
|
|
|
|
|
|
Group: Administrators
Last Login: Friday, May 17, 2013
Posts: 1,686,
Visits: 3,175
|
Hi Greg,I couldn't reproduce this problem on the 6.8.14. ------------------------------------------------------------Computer address: MPC------------------------------------------------------------ Executing remote command. Please wait...
COMMAND OUTPUT BEGIN----------------------------------------
Connecting to remote service ... OkSUCCESS: The process with PID 3228 (child process of PID 5764) has been terminated.Remote command returned 0 (0x0)
COMMAND OUTPUT END------------------------------------------I'm fairly certain that the changes in the 6.8.14 couldn't have caused the problem that you are facing. But I'll be happy to investigate this issue further.
|
|
Post #4197
|
|
|
|
|
|
Group: Forum Members
Last Login: Tuesday, February 19, 2013
Posts: 26,
Visits: 65
|
Hi Yury,
I was going to add more to the issue, the method that was failing for me was using WinRM, I found that using psexec solves some of my problems, but my environment relies on using WinRM. Some of the other scripts I use create a scheduled task on the remote machine to get around the inability to launch programs with a GUI, these tools don't seem to work through psexec. Can you check to see if you're having issues with WinRM?
Let me know if I should make a separate post for this, but when trying to roll back to 6.8.7 it seems that my config file isn't compatible any more, is there some way that I can use the older versions with my new config file?
Thanks,
Greg
|
|
Post #4198
|
|
|
|
|
|
Group: Administrators
Last Login: Friday, May 17, 2013
Posts: 1,686,
Visits: 3,175
|
When I use the WinRM execution method, it seems to be working just as fine as well and the VNC Manager doesn't hang.I've also tried to use an old v6.0.5 build and it behaves in exactly the same way as the 6.8.14. ------------------------------------------------------------Computer address: w8k2.ad.scode------------------------------------------------------------ Executing remote command. Please wait...
COMMAND OUTPUT BEGIN----------------------------------------
SUCCESS: The process with PID 2772 (child process of PID 1960) has been terminated.
ERROR: The process with PID 2484 (child process of PID 2772) could not be terminated.Reason: The process cannot terminate itself.COMMAND OUTPUT END------------------------------------------PS: Between the 6.8.7 and the 6.8.14 there were some changes to the VNC deployment job configuration files format. But I don't recon any other breaking changes.
|
|
Post #4199
|
|
|
|
|
|
Group: Forum Members
Last Login: Tuesday, February 19, 2013
Posts: 26,
Visits: 65
|
Hi Yury,
When I try to roll back to 6.8.7 I get:
SmartCode VNC Manager has encountered a problem...
Valaue must be between the minimum and maximum values.
Parameter name: Value
I just sent an error report for this issue.
I still don't understand how WinRM is working for you with that command. I thought it could have been an issue with my configuration files, so I backed them up and started fresh, but with 6.8.14 and WinRM it still hangs:
------------------------------------------------------------
Computer address: intest007
------------------------------------------------------------
Executing remote command. Please wait...
until I select 'Cancel':
------------------------------------------------------------
Computer address: intest007
------------------------------------------------------------
Executing remote command. Please wait...
COMMAND OUTPUT BEGIN----------------------------------------
SUCCESS: The process with PID 3892 child of PID 4024 has been terminated.
SUCCESS: The process with PID 4024 child of PID 3296 has been terminated.
SUCCESS: The process with PID 3296 child of PID 3032 has been terminated.
SUCCESS: The process with PID 3032 child of PID 2296 has been terminated.
SUCCESS: The process with PID 3268 child of PID 3340 has been terminated.
ERROR: The process with PID 2924 child of PID 3268 could not be terminated.
Reason: The process cannot terminate itself.
The operation was canceled by the user.
COMMAND OUTPUT END------------------------------------------
Using the timeout does work, but waiting a minute for this command on 176 stations would take a lot longer than I want to wait.
Clearing my configuration files and restarting with 6.8.7 works for me, but putting all of my old configuration in place will be a big headache 
Is there anything else I can do to help you reproduce this issue? Or a quick fix for my configuration files?
Thanks,
Greg
|
|
Post #4200
|
|
|
|
|
|
Group: Forum Members
Last Login: Tuesday, February 19, 2013
Posts: 26,
Visits: 65
|
Hi Yury,
Okay, I'm not in as much trouble before, I found that if I roll back to 6.8.7 and copy only my preferences.xml and registered_computers.xml files into a cleared configuration folder, the program doesn't crash and my registered computers and remote commands are restored.
My problems with the 6.8.14 hanging with 'In Operation' still exist though.
|
|
Post #4201
|
|
|
|
|
|
Group: Administrators
Last Login: Friday, May 17, 2013
Posts: 1,686,
Visits: 3,175
|
SmartCode VNC Manager has encountered a problem...
Valaue must be between the minimum and maximum values.
Parameter name: Value
Most likely this one is caused by the value for VNC Thumbnails view items size. In the 6.8.14 the maximum size allowed was increased. The 6.8.7 may think that the value is out of range. I still don't understand how WinRM is working for you with that command. I'm not sure if it matters, but just in case...I'm was testing the WinRM method against a Windows Server 2008 R2.
|
|
Post #4202
|
|
|
|
|
|
Group: Forum Members
Last Login: Tuesday, February 19, 2013
Posts: 26,
Visits: 65
|
Hi Yury,
On all of the machines I'm working with we're using WindowsXP Pro.
-Greg
|
|
Post #4203
|
|
|
|
|
|
Group: Forum Members
Last Login: Tuesday, February 19, 2013
Posts: 26,
Visits: 65
|
Hi Yury,
Have you had any luck reproducing this issue on WindowsXP Pro?
Thanks,
Greg
|
|
Post #4205
|
|
|
|
|
|
Group: Administrators
Last Login: Friday, May 17, 2013
Posts: 1,686,
Visits: 3,175
|
gfinleyg (6/13/2012)
Hi Yury,
Have you had any luck reproducing this issue on WindowsXP Pro?
Thanks,
Greg
Hi Greg, I apologize for the delay. We are releasing v6.9.1 (with RealVNC v5 deployment support) tomorrow morning and after that I'm planning to take a look at this problem. I've already tested XP to Windows Server 2008 R2 scenario and it seems to be working. But I have yet to test XP to XP test case.
|
|
Post #4207
|
|