my sourcesafe database lives on a different machine then the one that i want to web deploy to, the machines are both in the same domain... i have set the sourceoffsite service to use the Administrator account (for the domain, so its using MYDOMAIN\Administrator), so it has full access to the remote folder..... if i set the web deploy directory to be a local folder it deploys fine, but if i try to deploy to the remote machine the deploy fails, when i check log.txt i see the message:
5/9/2004 8:58:46 PM - 1: Invalid DOS path: \\\\www1\\alpha (8004d845)
when i typed the deploy folder into the sourceoffsite manager i typed it as "\\www1\alpha" which IS a valid dos path (i am able to open that folder when logged into the machine that sourceoffsite server and my sourcesafe database live on..... SOS seems to add the "\\" for a "\" on its own....
i have tried mapping drives to this folder, accessing it via the hidden share (d$) or sharing the folder explicitly.... nothing seems to work.... has anyone ever successfully set SOS up to web deploy from one machine running SOS server and sourcesafe to a different machine in the same domain?
i am running SOS server version 4.0.1, i am sure it's the newest version of the server (and client) as i downloaded both of them this morning.... it is the demo version, which, if i can get these kinks worked out we will probably purchase shortly......
thanks for any help!
web deploy to another machine on the same LAN
Moderator: SourceGear
just wanted to get another status update on this bug.... i sent you a private email last week, but received no response.... is there still a fix for this bug in our near future?
we would be interested in trying the beta fix, we are about half way through our 30 day demo period and would like to see this last <PORN SPAM> get worked out so we can make sure the software suits all of our needs before making a purchase decision....
any thoughts on a timeline for when we can get a fix? hopefully it will give us some time to evaluate before our demo period expires?
thanks!
we would be interested in trying the beta fix, we are about half way through our 30 day demo period and would like to see this last <PORN SPAM> get worked out so we can make sure the software suits all of our needs before making a purchase decision....
any thoughts on a timeline for when we can get a fix? hopefully it will give us some time to evaluate before our demo period expires?
thanks!
I don't believe we got your email message. However you'll be glad to know we've been working on this bug and it has been fixed in SOS 4.0.2, released earlier this week.
http://support.sourcegear.com/viewtopic.php?t=1046
http://support.sourcegear.com/viewtopic.php?t=1046
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager