Access to the path 'c:/somepath/dbo.mysp.sql' is denied
Skylink
Posts: 2 Bronze 1
Hi,
My team has just started using SSC3 (dedicated model) and we're seeing some troubles commiting changes to Perforce.
Commit goes through all the steps, checks off 'updating file set' as successful then fails 'sending files to source control (see details above). The details above are:
Access to the path 'c:/somepath/dbo.mysp.sql' is denied
Linking to the database and Getting Latest seem to work fine. Commit works the first time after linking the db but fails sometime after that.
We have checked the files. They are always there with no strange admin/etc permissions on them. They are readonly (perforce does that).
Any help you could provide would be greatly appreciated. We're a bit behind and this tool shows alot of promise if we can get around this checkin problem.
Thanks!!!
My team has just started using SSC3 (dedicated model) and we're seeing some troubles commiting changes to Perforce.
Commit goes through all the steps, checks off 'updating file set' as successful then fails 'sending files to source control (see details above). The details above are:
Access to the path 'c:/somepath/dbo.mysp.sql' is denied
Linking to the database and Getting Latest seem to work fine. Commit works the first time after linking the db but fails sometime after that.
We have checked the files. They are always there with no strange admin/etc permissions on them. They are readonly (perforce does that).
Any help you could provide would be greatly appreciated. We're a bit behind and this tool shows alot of promise if we can get around this checkin problem.
Thanks!!!
Comments
If SQL Source Control is failing at the 'sending files to source control' step, then the error returned is an error directly from Perforce, so I'm not really sure what could be causing that. There's a few things like this on their forum that seem like they might be relevant: http://forums.perforce.com/index.php?/t ... attribute/
My best guess is that there's something going askew in how Perforce is dealing with checked out files, but that's as far as I can really speculate - I'm afraid I don't have a huge amount of experience working with Perforce. I assume you're using the config file provided to work with Perforce - it might be worth trying the 'Working folder' option and manually checking in changes with the Perforce client to see if that works any better. Here's our documentation about how using the Working folder option works: http://documentation.red-gate.com/displ ... ng+folders
Hope that helps a bit!
Red Gate Technical Support Engineer