[AG-TECH] Probs starting VIC&RAT on AGTK3.01 winxp - fixed

[Sebastian Adams]

Just confirming to everyone that Andrew's solution fixed the problem - many thanks :)
Cheers, Seb

>>> "Andrew A Rowley" <Andrew.Rowley at manchester.ac.uk> 02 June 2006 14:42:31 >>>
Hi,

This is an error I have reported, but I thought it was fixed.  The bug is that the toolkit does not put the path to the vic and rat executables in inverted commas, so it does not parse the path with spaces in it correctly.  This does not appear to happen on all windows platforms, so I have no idea what the actual cause is (it happens on mine, but if it happened to everyone, I would think there would be more messages about it!).

The solution, if you don't want to wait for one, is to edit 
C:\Python23\Lib\site-packages\AccessGrid3\AccessGrid\Platform\win32\ProcessManager.py

You need to add:
if command.find(" ") != -1:
            command = '"' + command + '"'
To the top of the StartProcess function.

I would back up this file before doing this.

Andrew :)

============================================
Access Grid Support Centre,
RSS Group,
Manchester Computing,
Kilburn Building,
University of Manchester,
Oxford Road,
Manchester, 
M13 9PL, 
UK
Tel: +44(0)161-275 0685
Email: Andrew.Rowley at manchester.ac.uk 

> -----Original Message-----
> From: owner-ag-tech at mcs.anl.gov [mailto:owner-ag-tech at mcs.anl.gov] On
> Behalf Of Sebastian Adams
> Sent: 02 June 2006 12:56
> To: ag-tech at mcs.anl.gov 
> Subject: [AG-TECH] Probs starting VIC&RAT on AGTK3.01 winxp
> 
> Hi there,
> 
> One of the machines here has an odd prob starting the vic & rat
> executables. Example error:
> 
> eg audioservice.log
> 06/02/06 12:00:27 2984 Toolkit     agservice.py:182 INFO  SetStream:
> ignoring trivial re-configuration
> 06/02/06 12:00:27 2984 Toolkit     audioservice.py:274 INFO  Starting
> AudioService
> 06/02/06 12:00:27 2984 Toolkit     audioservice.py:275 INFO   executable =
> C:\Documents and Settings\JWW\Application
> Data\AccessGrid3\local_services\AudioService\rat.exe
> 06/02/06 12:00:27 2984 Toolkit     audioservice.py:277 INFO   options =
> ['-C', u'AGSC
> u'c0ab9a180f6c420a2c48365f6d2f3d12', '-f', 'L16-16K-Mono',
> u'sam.ag.manchester.ac.uk/10824']
> 06/02/06 12:00:27 2960 ProcessManager     processmanager.py:138 ERROR
> couldn't shutdown process <PyHANDLE:660>: (1444, 'PostThreadMessage',
> 'Invalid thread identifier.')
> Traceback (most recent call last):
>   File "C:\Python23\lib\site-
> packages\AccessGrid3\AccessGrid\Platform\win32\ProcessManager.py", line
> 131, in TerminateProcess
>     win32api.PostThreadMessage(self.threadid[pid], 18, 0, 0)
> error: (1444, 'PostThreadMessage', 'Invalid thread identifier.')
> 06/02/06 12:00:27 2984 ProcessManager     processmanager.py:62 DEBUG
> Creating process: C:\Documents and Settings\JWW\Application
> Data\AccessGrid3\local_services\AudioService\rat.exe -C "AGSC Venue Server
> Lobby" -S c0ab9a180f6c420a2c48365f6d2f3d12 -f L16-16K-Mono
> sam.ag.manchester.ac.uk/10824
> 06/02/06 12:00:27 2984 ProcessManager     processmanager.py:100 ERROR
> process creation failed: (193, 'CreateProcess', '%1 is not a valid Win32
> application.')
> Traceback (most recent call last):
>   File "C:\Python23\lib\site-
> packages\AccessGrid3\AccessGrid\Platform\win32\ProcessManager.py", line
> 73, in StartProcess
>     startup_info)
> error: (193, 'CreateProcess', '%1 is not a valid Win32 application.')
> 
> similarlarly for vic (videoproducerservice.log):
> 
> 06/02/06 12:14:08 2884 Toolkit     videoproducerservice.py:324 INFO
> enabled: 1
> 06/02/06 12:14:08 2884 Toolkit     agservice.py:171 INFO  SetStream:
> [consume
> ster.ac.uk 10194
> 06/02/06 12:14:08 2884 Toolkit     videoproducerservice.py:175 INFO
> Mapping windows device: Logitech QuickCam Pro 4000
> 06/02/06 12:14:08 2884 Toolkit     videoproducerservice.py:303 INFO
> Starting VideoProducerService
> 06/02/06 12:14:08 2884 Toolkit     videoproducerservice.py:304 INFO
> executable = C:\Documents and Settings\JWW\Application
> Data\AccessGrid3\local_services\VideoProducerService\vic.exe
> 06/02/06 12:14:08 2884 Toolkit     videoproducerservice.py:305 INFO
> options = ['-u',
> 'C:/
> 'Logitech QuickCam Pro 4000', '-X',
> u'site=c0ab9a180f6c420a2c48365f6d2f3d12',
> u'sam.ag.manchester.ac.uk/10194']
> 06/02/06 12:14:08 2884 ProcessManager     processmanager.py:62 DEBUG
> Creating process: C:\Documents and Settings\JWW\Application
> Data\AccessGrid3\local_services\VideoProducerService\vic.exe -u
> C:/DOCUME~1/JWW/LOCALS~1/Temp/VideoProducerService_2920.vic -C "Logitech
> QuickCam Pro 4000" -X site=c0ab9a180f6c420a2c48365f6d2f3d12
> sam.ag.manchester.ac.uk/10194
> 06/02/06 12:14:08 2884 ProcessManager     processmanager.py:100 ERROR
> process creation failed: (193, 'CreateProcess', '%1 is not a valid Win32
> application.')
> Traceback (most recent call last):
>   File "C:\Python23\lib\site-
> packages\AccessGrid3\AccessGrid\Platform\win32\ProcessManager.py", line
> 73, in StartProcess
>     startup_info)
> error: (193, 'CreateProcess', '%1 is not a valid Win32 application.')
> 
> So it looks like python getting confused with the path/arguments or
> somesuch? I have checked that there isn't a directory called c:\documents
> which could cause this prob.
> 
> I can start (without probs) vic & rat with the correct arguments via
> command line.
> 
> At first I thought it was another application (statistica) installed on
> the PC which uses the .svc extension for macros - but have uninstalled
> that without resolution.
> 
> AGTK has worked the machine in the past but has stopped working at some
> point (both agtk 2.4 & 3.01 exhibit the same prob).
> 
> Many thanks, Seb
> 
> Seb Adams
> CEH Computer Support
> Tel 01524 595818
> 
> --
> This message (and any attachments) is for the recipient only. NERC
> is subject to the Freedom of Information Act 2000 and the contents
> of this email and any reply you make may be disclosed by NERC unless
> it is exempt from release under the Act. Any material supplied to
> NERC may be stored in an electronic records management system.
> 


-- 
This message (and any attachments) is for the recipient only. NERC
is subject to the Freedom of Information Act 2000 and the 
of this email and any reply you make may be disclosed by NERC unless
it is exempt from release under the Act. Any material supplied to
NERC may be stored in an electronic records management system.