The jobs that I launch on Windows are failing. What might be going wrong?

There are several conditions under which jobs launched from Maestro or Canvas on Windows can fail.

• Jobs fail if the username contains spaces. The only solution is to obtain a username that does not have spaces.


• Jobs run locally can fail to run to start on Windows XP if there are multiple applications running. These applications use up the available desktop heap memory. This situation can arise in particular when your browser has many tabs open, or if it has been running for an extended period. The failure is usually accompanied by a "fork failed" error message. Usually the problem can be alleviated by closing down or restarting the other applications. See Article 841 for more information.


• Remote jobs can fail if the host name used in the schrodinger.hosts file differs from that used when establishing passwordless ssh connection to the host. These two names must match. The simplest solution is to edit the schrodinger.hosts file and change the host field for the host.


• If the job files are specified with a UNC path, jobs can fail with the error message

  CMD.EXE was started with the above path as the current directory.
  UNC paths are not supported. Defaulting to Windows directory
  

  This can happen if Maestro's working directory is set to a UNC path, for example. See http://support.microsoft.com/kb/156276 for more information on this problem. You can fix this problem by mapping the UNC path to a Windows drive.
  
  An alternative fix requires creation of a registry entry, as follows. Under the registry path

  HKEY_CURRENT_USER
  \Software
  \Microsoft
  \Command Processor
  

  create a new DWORD with the following values:

  Value Name: DisableUNCCheck
  Data Type: REG_DWORD
  Value Data: 1
  

  To fix the problem for all users on a machine, the entry should be created under HKEY_LOCAL_MACHINE rather than HKEY_CURRENT_USER.

Keywords: Windows, jobs, username, UNC path, host name

Back to Search Results