Unexpected build error: The specified path is invalid.  .  Make sure that the product is installed properly._
A build of any project will work until I set Deployment to True then I get the following error. What path is it talking about? Unexpected build error: The specified path is invalid. . Make sure that the product is installed properly.
April 22nd, 2010 5:31pm

Do u have access to the Deploymentoutputpath , that is below the createdeployment = TRUE
Free Windows Admin Tool Kit Click here and download it now
April 22nd, 2010 10:56pm

Yes, and it says bin\Deployment. I assume that some leading path gets concatenated with that but from where?
April 22nd, 2010 11:01pm

its u r project folder by default
Free Windows Admin Tool Kit Click here and download it now
April 22nd, 2010 11:09pm

Here is what I found. I tried changing the paths under Options in several places because I wanted to save in a different place than when VS was originally installed. But nothing works. When I change the Project path back to where the original install pointed then the Deploy works. There must be a variable/option that will correct this problem. It is as if the Deploy path is kept somewhere else and it must agree to where the project is saved which makes sense but changing the project path should change the Deploy path. Anyone have any ideas on this????
April 26th, 2010 8:01pm

Mr Scotsman , Is u r machine VISTA or Windows 7 or server 2008 ? If so run , in adminstartor mode ( if u right Click u can see as run as ADMINstartor mode ) check if this works ----------------------------------- Mark as answered if it helps
Free Windows Admin Tool Kit Click here and download it now
April 26th, 2010 8:09pm

Try XP. What would Administrator mode on the PC have to do with this? I am an Administrator on the PC anyway.
April 26th, 2010 8:26pm

Error 1 Unexpected build error: Access to the path 'c:\bdlog.txt' is denied.. Make sure that the product is installed properly. 0 0 i hope u also got the above error Please try the solution ?? for Admin,, this how SSIS works ........ On systems where UAC is enabled, when an application (like SSIS) is launched by an account that is a member of the Administrators group, it gets two security tokens, one a low privileged token and another an elevated token. The elevated token is only used when the application is explicitly run under an Administrator account by choosing “Run as Administrator” option. By default SSIS always uses the low privileged token resulting in a failure when connecting to a SQL Destination. even if u r a part of Local Admin group it wont work . it will work only for those who are created during OS installations. Check Microsoft KB for further details ------------------------------------------------------------------- Mark as answered if it helps
Free Windows Admin Tool Kit Click here and download it now
April 26th, 2010 8:59pm

SCOTSMAN any updates on this ??
April 27th, 2010 10:08pm

I encountered the same error, I tried right click the project then "Clean" then after that i tried "Build" it works all of a sudden.. maybe you guys can try it too.. maybe it is some bugs..im not sure :)
Free Windows Admin Tool Kit Click here and download it now
December 2nd, 2010 6:50pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics