Drive already mounted

[rhammond]

When I try submitting to one of our farm machines, the job just sits there pending with the reason "Drive already mounted". What is causing this?

The farm machine is Windows XP Pro SP2 with all the current High Priority updates. It was rebooted just prior to submission and I had not remotely logged into it.  Also, I do not request any kind of drive mapping in the job type itself.

[anthony]

This error is normally caused because of a conflict in windows pre-existing mounts and the worker's settings.  Normally an account shouldn't be setup to have permanent mounts.  (This is done when you say reconnect on login for a drive map)  Because windows has already mapped a drive in place of of a letter which you have already created, the worker rejects the job because it is unable to run it.  This rejection only happens if the mapped drive letters don't match each other's location.  You can easily see what the exact mounting error was by checking the worker's log file:

C:\program files\qube\logs\workerlog

A.

[rhammond]

Doh ><. The log doesn't tell me anything more unless it's saying that drive "rhammond" is already mounted. Have no idea what that could mean.

Thu Nov 10 10:17:38 2005] FARM010 : INFO: received start order: 254081.0
[Thu Nov 10 10:17:38 2005] FARM010 : login successful account: 'rhammond' domain: 'EACANADA'
[Thu Nov 10 10:17:38 2005] FARM010 : ERROR: drive already mounted: rhammond
[Thu Nov 10 10:17:38 2005] FARM010 : posting current status.
[Thu Nov 10 10:17:38 2005] FARM010 : sending host status report to the supervisor.
[Thu Nov 10 10:17:38 2005] FARM010 : host report - report successful.
[Thu Nov 10 10:17:38 2005] FARM010 : the supervisor has requested an update.
[Thu Nov 10 10:17:38 2005] FARM010 : sending host status report to the supervisor.
[Thu Nov 10 10:17:39 2005] FARM010 : host report - report successful.

[anthony]

Intresting.  You might want to try this:

Login interactivly on the host which is giving you the mounting error.  Select all of your existing network drives and disconnect them. 

Then see if trying the job again works. 

If it does, then you have a choice.  You can either turn auto mounting off for the host itself, or you can leave the account maps all disconnected.

Your facility is also approved for qube 4.0 beta as well and you might benefit from the job auto_mount flag.  This essentially lets the user choose to use auto_mounting or not.  Of course it must be enabled on the host.  However the job must have the auto_mount flag turned on for auto mounting to work.