Troubleshooting Code Error 80070055 - The local device is already in use
Introduction to error Code 80070055
Error code 80070055 occurs when you try to map a network drive with a VBScript. My
suggestion is that you have already mapped a drive with this particular letter.
The Symptoms you get 80070055
When you execute the VBScript you get a WSH (Windows Script Host) message box like this
diagram opposite.
The script does not execute as you had hoped.
The Cause of Error 80070055
One possibility is that you trying to map a network drive but the drive
letter you wish to use has already been assigned. Perhaps you
have already run the script once, and now you double click the .vbs file one
more time. Alternatively, you have forgotten that the H:\ or K:\ drive
letter is a physical drive on this particular
machine.
Another cause could be your VBScript contains an illegal LDAP reference,
probably a typing mistake, maybe an extra letter. Check the spelling of
your objects in the script.
Another clue is the Source: WSHNetwork.MapNetworkDrive. A clear indication
that the MapNetworkDrive method is causing the error.
For 'The local device name is already in use', check your drive letters
and printers, in particular lookout for potential duplicates.
The Solutions for The local device is already in use
To examine the drive letters, open windows explorer and check the local drive
letters against the DriveLetter used in your script. In this example it
is the K:
drive which is causing the problem.
Another cause could be a syntax error. Check or adjust the slashes
in your path.
For example:
RemotePath = "\\ alan\home" is correct. For
example:
RemotePath = "\\ alan\home\" has an
extra \ at the end and is incorrect.
Under different circumstance is could be a duplicate printer. So
check the printer folder to see what printers have already been installed.
The DriveLetter corresponds to K: and the problem was that the drive letter was already mapped.
'Purpose of the script is to Connect or Disconnect the K drive
'If connected it disconnects
Set WshShell = WScript.CreateObject("WScript.Shell")
Set GuyNet = WScript.CreateObject("WScript.Network")
Set CheckDrive = GuyNet.EnumNetworkDrives()
DriveLetter = "K:" 'DriveLetter must be a CAPITAL letter
RemotePath = "\\alan\home"
AlreadyConnected = False
'GuyNet.RemoveNetworkDrive DriveLetter
For i = 0 To CheckDrive.Count - 1 Step 2
If CheckDrive.Item(i) = DriveLetter Then AlreadyConnected = True
Next
If AlreadyConnected = True then
GuyNet.RemoveNetworkDrive DriveLetter GuyNet.MapNetworkDrive DriveLetter, RemotePath WshShell.PopUp "Drive " & DriveLetter & "Disconnected, then connected
successfully."
Try
a different solution, download SolarWinds ipMonitor
Here is my thinking,
ipMonitor will give you valuable data about your network and servers.
This extra information just may unlock the solution to your error code.
One more thing, sometimes when troubleshooting you go around in circles;
therefore if you try a different, but related approach, you may just crack the
problem.
Free Download
of SolarWinds ipMonitor
Their topics and material are ideal for getting you started with VBScript. The
videos are easy to follow and you can control the pace. Try their free demo material and then see if you want to buy the full package.
See more about VB Script Training CD.
The extra features you get in your eBook
include, more pages full of detailed examples. Also, ten 'how to...'
sections, with screen shots showing which menus to use. Go for Guy's
eBook - and get a printable version with copy enabled and no expiry date.