Web deploy '\\' problem

levank · Post by **levank** » Thu Jul 21, 2005 5:15 am

Hi

I know this has been discussed here before and i have upgraded my copy of SOS client to version 4.1, but i am still experiencing this problem:

I set the folder "$/Websites/melville.co.uk/Publish" to deploy to "X:\MellvileWebsite"

When i try to deploy, the path i am getting is "X:\\MelvilleWebsite" (notice two slashes - "\\").

What can i do to resolve it?

Thanks
Levan

bfinney · Post by **bfinney** » Fri Jul 22, 2005 2:53 pm

The double slashes are just a client-side display problem - if the deploy is failing, there's something else going on. We'd probably need to see the server log to diagnose it with any certainty, but I'll take a crack at it anyway.

I'm assuming that X: is a mapped drive. If so, check that the account that's running the SOS Server service has write access to that machine.

levank · Post by **levank** » Mon Jul 25, 2005 2:42 am

Hi Brody and thanks for the reply.

I have checked the permissions and i am sure that 'Everybody' has full access. I also investigated the log and this is what i found in it:

25/07/2005 09:38:34 - 37: COM Exception processing client message: Invalid DOS path: X:\MelvilleWebsite
25/07/2005 09:38:34 - 37: COM Exception processing client message: Invalid DOS path: X:\MelvilleWebsite\Arena
25/07/2005 09:38:34 - 37: COM Exception processing client message: Invalid DOS path: X:\MelvilleWebsite\images
25/07/2005 09:38:34 - 37: COM Exception processing client message: Invalid DOS path: X:\MelvilleWebsite\Templates
25/07/2005 09:38:34 - 37: COM Exception processing client message: Invalid DOS path: X:\MelvilleWebsite\Templates\_notes

I am guessing that the system does not like mapped drives at all. i need to find an alternative way to access the network location

Levan

bfinney · Post by **bfinney** » Mon Jul 25, 2005 8:02 am

Yeah, going with a UNC path is usually safer. In some cases the SOS service starts up before the mapping was complete which wrecks everything. That doesn't explain every case of mapped drives not working, but that's the olny one we've ever been able to pin down!

Guest · Post by **Guest** » Mon Jul 25, 2005 8:15 am

I have changed the path to UNC, but getting same error:

25/07/2005 15:08:47 - 1: COM Exception processing client message: Invalid DOS path: \\192.9.150.57\lk\MelvilleWebsite
25/07/2005 15:08:47 - 1: COM Exception processing client message: Invalid DOS path: \\192.9.150.57\lk\MelvilleWebsite\Arena
25/07/2005 15:08:47 - 1: COM Exception processing client message: Invalid DOS path: \\192.9.150.57\lk\MelvilleWebsite\images
25/07/2005 15:08:47 - 1: COM Exception processing client message: Invalid DOS path: \\192.9.150.57\lk\MelvilleWebsite\Templates
25/07/2005 15:08:47 - 1: COM Exception processing client message: Invalid DOS path: \\192.9.150.57\lk\MelvilleWebsite\Templates\_notes

bfinney · Post by **bfinney** » Wed Jul 27, 2005 10:02 am

The next thing to do is to explicitly grant the account that operates the service full control over the deploy path (i.e. don't trust the "everyone" settings and manually configure account access).

I didn't ask earlier, but is the service operating as a domain account? Is the delpoly path on the same domain? If not, there are other hoops that may have to be jumped through. Probably the easiest thing to do would be to set the service account to be the same as the user you're logged in as - in you can see the deploy path through Windows Explorer, then by definition, the service account can see it.