I have a web farm of two II7.5 hosts that use a shared content location for a site via a UNC path\\server\share style.  Both servers are able to acess the share just fine for content/confg, have been able to for some time now.

When I deploy a site to one of the two servers using web deploy 2.1 I get the following error:

Error Code: ERROR_INSUFFICIENT_ACCESS_TO_SITE_FOLDER
More Information: Unable to perform the operation ("Create Directory")  for the specified directory ("\\server\
stg_content\path"). This can occur if the server administrator has not authorized this operation for the user crede
ntials you are using.
Error: The error code was 0x80070005.
Error: Access to the path '\\server\stg_content\path' is denied.

I am running the deploy as an admin of all of the servers in question.  When I navigate to the UNC path from anyone of those servers while logged in as the same user, I am able to create files/directories all day long.

Is anyone aware of a problem with deploying sites to shared content paths using this tool?

Hi,

We are using MS Deploy to deploy to a server running the Web Management Service.  The deployment package includes SQL scripts which get executed with the dbFullSql provider.  When those scripts run, we need the credentials of the user (i.e. the person running MSDeploy) to flow through to SQL Server.

We are thinking this should be possible with Kerberos.  We have set up SPN's on the server for the 8172 port, and as far as we can tell, that side of things is OK.  BUT it appears that MSDeploy.exe is not trying to use Kerberos.  It seems to be immediately opting to use NTLM.

Is it supposed to work with Kerberos?  If so, is there some kind of switch we need to set or something?  Is there any difference between MSDeploy 2 and MSDeploy 3, in this regard?

John

can vs2010 deploy do the differentiation deploy?

or other tools can do the differentiation deploy for the asp.net!

thank you!

I have a Web application that have been written with ASP.Net 4 C#. I have a Web Deployment(2010 Version 10.0.30319) Project for deploying this web application.
I am using Visual Studio 2010 SP1.When I get latest version from server the new files are got, and after this when I build my Web Deployment I get a strange error in new files that I have got from server.It say:
"error ASPPARSE: The resource object with key '?????' was not found."
I can see resource file with ????? name-value, the web application build successfully and I can browse the new page successfully too.
Any idea?

I'm not sure if this is technically an msbuild or an msdeploy/vsmsdeploy question - if this isn't the right place, let me know.

I have a web forms application (Visual Studio 2010) with an existing wpp.targets file working successfully to do things like LESS preprocessing, resource minification/bundling, web.config encryption, etc.

I have always been able to deploy just fine by simply right-clicking on the web app, and choosing the Publish - File System option.

I recently decided to try and automate the setting of the ACL permissions on a specific folder within the app. This led me down the road of changing from the File System publish option to the Web Deploy option (which also works fine after installing and configuring Web Deploy 3 on the server).

The reason I switched to Web Deploy is because it's my understanding that by using the Web Deploy option, I should be able to add additional steps to my wpp.targets file to set the necessary folder permissions.

I've seen numerous articles, blogs, forum posts, etc. on the subject and it seems fairly straight forward.

I'm trying to give Read/Write/Modify access to Domain Users for a folder named "IDAutomation" - so I basically just added the following at the end of my existing wpp.targets file:

<Target Name="SetupCustomAcls" AfterTargets="AddIisSettingAndFileContentsToSourceManifest"><ItemGroup><MsDeploySourceManifest Include="setAcl"><Path>$(_MSDeployDirPath_FullPath)\IDAutomation</Path><setAclUser>Domain Users</setAclUser><setAclAccess>Read,Write</setAclAccess><setAclResourceType>Directory</setAclResourceType><AdditionalProviderSettings>setAclResourceType;setAclAccess</AdditionalProviderSettings></MsDeploySourceManifest></ItemGroup></Target><Target Name="DeclareCustomParameters" AfterTargets="AddIisAndContentDeclareParametersItems"><ItemGroup><MsDeployDeclareParameters Include="IDAutomationSetAcl"><Kind>ProviderPath</Kind><Scope>setAcl</Scope><Match>^$(_EscapeRegEx_MSDeployDirPath)\\IDAutomation$</Match><Description>Add permissions to the IDAutomation folder.</Description><DefaultValue>{$(_MsDeployParameterNameForContentPath)}/IDAutomation</DefaultValue><Value>$(_DestinationContentPath)/IDAutomation</Value><Tags>Hidden</Tags><Priority>$(VsSetAclPriority)</Priority><ExcludeFromSetParameter>True</ExcludeFromSetParameter></MsDeployDeclareParameters></ItemGroup></Target>

But I'm obviously missing something because I click Publish -> Web Deploy - and let it do its thing, the permissions are not applied to the folder. The app is deployed successfully and everything looks good - it just doesn't set the permissions on the folder for me.

Here's some excerpts from the end of the deploy output:

Target "Package" skipped, due to false condition; ($(_CreatePackage)) was evaluated as (false).
Target "MSDeployPublish" in file ..... from project .....
Start Web Deploy Publish the Application/package to....
...
Starting Web deployment task from source:manifest(.....) to Destination:auto().
Updating setAcl (Site/app).
Updating setAcl (Site/app).
Updating setAcl (Site/app/IDAutomation).     <--  Appears to be doing something??
Updating filePath......
....
Updating setAcl (Site/app).
Updating setAcl (Site/app).
Updating setAcl (Site/app/IDAutomation).     <--  Appears to be doing something??
Successfully executed Web deployment task.
Publish is successfully deployed.
Task "MSdeploy" skipped, due to false condition; ($(UseMsdeployExe)) was evaluated as (False).
Done building target "MSDeployPublish" in project ...
Done building project ...

So it appears to be setting the acl on the folder (twice for some reason) as you can see, but when I go look at the folder on the remote server, the permissions have not been applied.

What am I missing here?

I'm not trying to build a package for later/manual deployment or anything involving a build server. I'm simply manually trying to Publish -> Web Deploy.

Also Web Deploy 3.0 is installed on my machine (win7) as well as the web server (Win2008R2/IIS7.5).

I have also tried adding UseMsDeployExe=true to my wpp.targets file to switch from VsMsdeploy to Msdeploy - but the result is the same.  It appears to be setting the ACLs in the log, but when I look at the folder on the server - the permissions are not applied.

I have also checked the WMSvc log and there is no indication of problem.

* I have a duplicate of this question open on SO, but still looking for a solution.

UPDATE:

I've discovered that regardless of what I set in the setAclUser element, the sitemanifest.xml file is *always* missing the setAclUser attribute for the folder (abbreviated paths):

<sitemanifest><IisApp path="C:\...\obj\...\Package\PackageTmp" managedRuntimeVersion="v4.0" /><setAcl path="C:\...\obj\...\Package\PackageTmp" setAclResourceType="Directory" /><setAcl path="C:\...\obj\...\Package\PackageTmp" setAclUser="anonymousAuthenticationUser" setAclResourceType="Directory" /><setAcl path="C:\...\obj\...\Package\PackageTmp\IDAutomation" setAclResourceType="Directory" setAclAccess="Read,Write" /></sitemanifest>

So you can see there's no setAclUser on the setAcl element for the IDAutomation folder.  Hopefully that will be a clue to someone?

<sigh>  finally realized i was missing setAclUser in the AdditionalProviderSettings...

<AdditionalProviderSettings>setAclUser;setAclResourceType;setAclAccess</AdditionalProviderSettings>

Hi,

We are using MS Deploy to deploy to a server running the Web Management Service.  The deployment package includes SQL scripts which get executed with the dbFullSql provider.  When those scripts run, we need the credentials of the user (i.e. the person running MSDeploy) to flow through to SQL Server.

We are thinking this should be possible with Kerberos.  We have set up SPN's on the server for the 8172 port, and as far as we can tell, that side of things is OK.  BUT it appears that MSDeploy.exe is not trying to use Kerberos.  It seems to be immediately opting to use NTLM.

Is it supposed to work with Kerberos?  If so, is there some kind of switch we need to set or something?  Is there any difference between MSDeploy 2 and MSDeploy 3, in this regard?

John

can vs2010 deploy do the differentiation deploy?

or other tools can do the differentiation deploy for the asp.net!

thank you!

I have a Web application that have been written with ASP.Net 4 C#. I have a Web Deployment(2010 Version 10.0.30319) Project for deploying this web application.
I am using Visual Studio 2010 SP1.When I get latest version from server the new files are got, and after this when I build my Web Deployment I get a strange error in new files that I have got from server.It say:
"error ASPPARSE: The resource object with key '?????' was not found."
I can see resource file with ????? name-value, the web application build successfully and I can browse the new page successfully too.
Any idea?

I'm not sure if this is technically an msbuild or an msdeploy/vsmsdeploy question - if this isn't the right place, let me know.

I have a web forms application (Visual Studio 2010) with an existing wpp.targets file working successfully to do things like LESS preprocessing, resource minification/bundling, web.config encryption, etc.

I have always been able to deploy just fine by simply right-clicking on the web app, and choosing the Publish - File System option.

I recently decided to try and automate the setting of the ACL permissions on a specific folder within the app. This led me down the road of changing from the File System publish option to the Web Deploy option (which also works fine after installing and configuring Web Deploy 3 on the server).

The reason I switched to Web Deploy is because it's my understanding that by using the Web Deploy option, I should be able to add additional steps to my wpp.targets file to set the necessary folder permissions.

I've seen numerous articles, blogs, forum posts, etc. on the subject and it seems fairly straight forward.

I'm trying to give Read/Write/Modify access to Domain Users for a folder named "IDAutomation" - so I basically just added the following at the end of my existing wpp.targets file:

<Target Name="SetupCustomAcls" AfterTargets="AddIisSettingAndFileContentsToSourceManifest"><ItemGroup><MsDeploySourceManifest Include="setAcl"><Path>$(_MSDeployDirPath_FullPath)\IDAutomation</Path><setAclUser>Domain Users</setAclUser><setAclAccess>Read,Write</setAclAccess><setAclResourceType>Directory</setAclResourceType><AdditionalProviderSettings>setAclResourceType;setAclAccess</AdditionalProviderSettings></MsDeploySourceManifest></ItemGroup></Target><Target Name="DeclareCustomParameters" AfterTargets="AddIisAndContentDeclareParametersItems"><ItemGroup><MsDeployDeclareParameters Include="IDAutomationSetAcl"><Kind>ProviderPath</Kind><Scope>setAcl</Scope><Match>^$(_EscapeRegEx_MSDeployDirPath)\\IDAutomation$</Match><Description>Add permissions to the IDAutomation folder.</Description><DefaultValue>{$(_MsDeployParameterNameForContentPath)}/IDAutomation</DefaultValue><Value>$(_DestinationContentPath)/IDAutomation</Value><Tags>Hidden</Tags><Priority>$(VsSetAclPriority)</Priority><ExcludeFromSetParameter>True</ExcludeFromSetParameter></MsDeployDeclareParameters></ItemGroup></Target>

But I'm obviously missing something because I click Publish -> Web Deploy - and let it do its thing, the permissions are not applied to the folder. The app is deployed successfully and everything looks good - it just doesn't set the permissions on the folder for me.

Here's some excerpts from the end of the deploy output:

Target "Package" skipped, due to false condition; ($(_CreatePackage)) was evaluated as (false).
Target "MSDeployPublish" in file ..... from project .....
Start Web Deploy Publish the Application/package to....
...
Starting Web deployment task from source:manifest(.....) to Destination:auto().
Updating setAcl (Site/app).
Updating setAcl (Site/app).
Updating setAcl (Site/app/IDAutomation).     <--  Appears to be doing something??
Updating filePath......
....
Updating setAcl (Site/app).
Updating setAcl (Site/app).
Updating setAcl (Site/app/IDAutomation).     <--  Appears to be doing something??
Successfully executed Web deployment task.
Publish is successfully deployed.
Task "MSdeploy" skipped, due to false condition; ($(UseMsdeployExe)) was evaluated as (False).
Done building target "MSDeployPublish" in project ...
Done building project ...

So it appears to be setting the acl on the folder (twice for some reason) as you can see, but when I go look at the folder on the remote server, the permissions have not been applied.

What am I missing here?

I'm not trying to build a package for later/manual deployment or anything involving a build server. I'm simply manually trying to Publish -> Web Deploy.

Also Web Deploy 3.0 is installed on my machine (win7) as well as the web server (Win2008R2/IIS7.5).

I have also tried adding UseMsDeployExe=true to my wpp.targets file to switch from VsMsdeploy to Msdeploy - but the result is the same.  It appears to be setting the ACLs in the log, but when I look at the folder on the server - the permissions are not applied.

I have also checked the WMSvc log and there is no indication of problem.

* I have a duplicate of this question open on SO, but still looking for a solution.

UPDATE:

I've discovered that regardless of what I set in the setAclUser element, the sitemanifest.xml file is *always* missing the setAclUser attribute for the folder (abbreviated paths):

<sitemanifest><IisApp path="C:\...\obj\...\Package\PackageTmp" managedRuntimeVersion="v4.0" /><setAcl path="C:\...\obj\...\Package\PackageTmp" setAclResourceType="Directory" /><setAcl path="C:\...\obj\...\Package\PackageTmp" setAclUser="anonymousAuthenticationUser" setAclResourceType="Directory" /><setAcl path="C:\...\obj\...\Package\PackageTmp\IDAutomation" setAclResourceType="Directory" setAclAccess="Read,Write" /></sitemanifest>

So you can see there's no setAclUser on the setAcl element for the IDAutomation folder.  Hopefully that will be a clue to someone?

<sigh>  finally realized i was missing setAclUser in the AdditionalProviderSettings...

<AdditionalProviderSettings>setAclUser;setAclResourceType;setAclAccess</AdditionalProviderSettings>

Hi,

We are using MS Deploy to deploy to a server running the Web Management Service.  The deployment package includes SQL scripts which get executed with the dbFullSql provider.  When those scripts run, we need the credentials of the user (i.e. the person running MSDeploy) to flow through to SQL Server.

We are thinking this should be possible with Kerberos.  We have set up SPN's on the server for the 8172 port, and as far as we can tell, that side of things is OK.  BUT it appears that MSDeploy.exe is not trying to use Kerberos.  It seems to be immediately opting to use NTLM.

Is it supposed to work with Kerberos?  If so, is there some kind of switch we need to set or something?  Is there any difference between MSDeploy 2 and MSDeploy 3, in this regard?

John

can vs2010 deploy do the differentiation deploy?

or other tools can do the differentiation deploy for the asp.net!

thank you!

I had started a thread in General Troubleshooting, but there has not been any answers yet, so I've decided to start a new here. Here is my problem description:

http://forums.iis.net/t/1192976.aspx/1?Web+Deploy+3+0+Web+deployment+task+failed+Root+element+is+missing

In a nutshell it seems WD3 is not working when I have more than one Azure instances but WD2 is. My question is, are there any WD3 options to get it works again?

I am getting the below error.

msdeploy.exe is not a valid win32 appplication

i get the error when run using exec task of msbuild and also when i just run msdeploy from a command prompt.

i tried uninstalling web deploy and re-installing it. the error doesn't seem to go away.

Any idea how to solve this? let me know what additional information is required.

I have an old server, that at some point in the past someone migrated "most" of the sites away from. However we have just discovered that a few people have continued to use one of the internal Wiki's that was hosted here and we now need to move that site (and no others) off the box, so that it can be scrapped (win2k3 I don't know which version of IIS).

Most MS server stuff is new to me (IBM Power system specialist by trade), and I am having some difficulty in finding how I would go about moving just the one site from this IIS installation. The main server (where this site should be) is Win2k8 with IIS7.

The complication is that the new versions of the other sites are hosted on the destination server, so I cannot move anything except the old Wiki site and it's associated stuff.

Any help greatly appreciated

I'm having issues with web deploy and trying to figure out how to get the web.deploy.cmd to update remote files.  Here's the command I'm running:

web.deploy.cmd /Y /M:\\servername\C$\physicalPath -allowUntrusted /U:\AdminUserName /P:password /A:Basic

Every time I run this from my local machine, it updates my files at the physical path location and not the server.  All the credentials are right.  I'm not getting any error messages, it just updates the wrong computer.

Any ideas on what I'm doing wrong?

Hi 

I want to migrate from IIS6 on Server 2003 to IIS7 on Server 2008 R2. I installed everything fine from the MS Web Platform Installer on my 2k8 R2 box (it isn't in my DMZ yet) but had some issues getting the installer to run so had to update to .net3.5 on my 2003 box. I then had to download the ms deploy, the one on my 2008 box is v3 that came automatically, the one on the 2003 box i had to download manually is v2. I managed to export my stuff from IIS6 but when i run the command with whatif bit in from here

http://www.iis.net/learn/publish/using-web-deploy/migrate-a-web-site-from-iis-60-to-iis-7-or-above

I get 

C:\Program Files (x86)\IIS\Microsoft Web Deploy V3>msdeploy -verb:sync -source:p

ackage=c:\Site1.zip -dest:metakey=lm/w3svc/1 -whatif > WebDeploySync.log
Error Code: ERROR_FRAMEWORK_VERSIONS_DO_NOT_MATCH
More Information: The versions of the .NET Framework Configuration Provider (roo
tWebConfig32) are different on the source (2.0.50727.1433) and destination (4.0)
. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_FRAMEWORK_
VERSIONS_DO_NOT_MATCH.
Error count: 1.

Can someone advise me how I get around this please 

Many thanks 

James 

Hi,

I've been fighting WebDeploy 3.0 for a few days because Web Deploy Service (MsDepSvc.exe) randomly crashes. I've managed to recreate this behavior by executing the following run command 10-15 times on a row:

msdeploy.exe -verb:sync -source:runCommand="ipconfig" -dest:auto,computerName="remoteServer",userName="domain\user",password="password"

By duplicating this command in a .bat file about 20 times, I've managed to consistently replicate this crash. In addition we've seen this behaviour very frequently in our continuous deployment process, where this issue was originally discovered, but at different intervals and times.

Note: By adding back Web Deploy 2.0 on the servers, the problem goes away.

On the server running MsDepSvc the follwing relevant entries are found in the event log:

1) Entry from WebDeploy: 

System.ArgumentException: Invalid token for impersonation - it cannot be duplicated.
at System.Security.Principal.WindowsIdentity.CreateFromToken(IntPtr userToken)
at System.Security.Principal.WindowsIdentity..ctor(IntPtr userToken, String authType, Int32 isAuthenticated)
at System.Security.SecurityContext.CreateCopy()
at System.Threading.ExecutionContext.CreateCopy()
at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)

2) Entry from .NET runtime:

Application: MsDepSvc.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ArgumentException
Stack:
at System.Security.Principal.WindowsIdentity.CreateFromToken(IntPtr)
at System.Security.Principal.WindowsIdentity..ctor(IntPtr, System.String, Int32)
at System.Security.SecurityContext.CreateCopy()
at System.Threading.ExecutionContext.CreateCopy()
at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)

Note: We use WebDeploy 3.0 from the source/client. The command works perfectly with WebDeploy 2.0 on the server, so for now we've been forced to use 2.0 until this problem is solved in 3.0. 

Would be very interested to hear if others are able to replicate this, cause we have these errors on 10s of servers in 2 different environments/domains.

Thanks,

Jon Arild Tørresdal

I read about the Web Deploy Powershell Cmdlets, and I'd like to start using them.  Of course, the first task as I begin is to backup the current configuration state of my test webserver--and this cmdlet should do it:

Backup-WDServer -ConfigOnly

But, when I run it I get this complaint--I'm unsure how to resolve it:

Backup-WDServer : The property 'password' located at '/webServer/appHostConfig[@path='']/location[@path='']/section[@name='system.applicationHost/applicationPools']/applicationPools/applicationPoolDefaults/processModel' is 
marked as secure. You must specify an encryption password to archive this property.
At line:1 char:1
+ Backup-WDServer -ConfigOnly

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [Backup-WDServer], DeploymentEncryptionException
    + FullyQualifiedErrorId : Microsoft.Web.Deployment.PowerShell.BackupServer