Previous Next

• 06-20-2008, 6:07 PM

  hautesecure Joined on 06-20-2008, 5:30 PM Posts 6 hautesecure	Proper syntax for msdeploy? Reply Contact I think i am doing this correctly, but can someone give me the correct syntax for remote syncronizing FROM a x64 machine to a x32 machine?

• 06-20-2008, 6:26 PM

  In reply to

  hautesecure Joined on 06-20-2008, 5:30 PM Posts 6 hautesecure

  Re: Proper syntax for msdeploy? Reply Contact Here is what I am trying to do: C:\Program Files\Microsoft Web Deploy>msdeploy -verb:sync -source:metakey=lm/w3s vc/1379865194 -dest:metakey=lm/w3svc/1379865194,computerName=http://xxx.xxx.xxx.xxx:80/msdeployagentservice Action: Adding metaKey (/lm/w3svc/1379865194) Action: Adding child metaProperty (/lm/w3svc/1379865194/SecureBindings) Action: Adding child metaProperty (/lm/w3svc/1379865194/ServerComment) Action: Adding child rootWebConfig64 (metaKey/metaProperty[@name='ServerComment' ]/rootWebConfig64[@path='www.DELETETED.com']) Fatal: Sync operation 'AddChild' failed with destination metaProperty (/lm/w3svc /1379865194/ServerComment) Fatal: Child element 'rootWebConfig64' can not be added to element 'metaProperty '. Change count: 4 Fatal count: 2   and that is the output...any clues?

• 06-20-2008, 6:43 PM

  In reply to

  ksingla Joined on 06-14-2006, 3:02 AM Redmond, WA Posts 411 ksingla

  Re: Proper syntax for msdeploy? Reply Contact Hi hautesecure, Syncing a 64-bit server to a 32-bit server is not supported right now. One of the problem is there are two machine.config and root web.config files (one for 64-bit fx and one for 32-bit) on x64 machines and we are not sure which one to pick. We are looking at supporting a 32-bit msdeploy for 64-bit servers which will allow you to sync to a 32-bit server. This way we will make it little clearer that we are going to pick 32-bit configuration and not 64-bit. There is an unsupported way for you to move little further than where you hit error right now but that might have some unknown side effects. If you are willing to take some risk (might leave your destination server in bad state), you can try adding -disableLink:FrameworkConfigExtension to the commandline which will tell the tool to not bother picking machine.config and root web.config settings for the site. Here is what the command will look like msdeploy -verb:sync -source:metakey=lm/w3svc/1379865194 -dest:metakey=lm/w3svc/1379865194,computerName=http://xxx.xxx.xxx.xxx:80/msdeployagentservice -disableLink:FrameworkConfigExtension -debug -verbose -Kanwal-

• 06-20-2008, 6:44 PM

  In reply to

  hautesecure Joined on 06-20-2008, 5:30 PM Posts 6 hautesecure

  Re: Proper syntax for msdeploy? Reply Contact I even tried this and it fails: msdeploy -verb:sync -source:archivedir=c:\ folder_com -dest:metakey=lm/w3cv/1619542901,computerName=http://xxx.xxx.xxx.xxx:80/msdeployagentservice Action: Adding child rootWebConfig64 (metaKey/metaProperty[@name='ServerComment ]/rootWebConfig64[@path='www.xxxx.com']) Fatal: Sync operation 'AddChild' failed with destination metaProperty (/lm/w3cv 1619542901/ServerComment) Fatal: Child element 'rootWebConfig64' can not be added to element 'metaPropert '. Change count: 1 Fatal count: 2   Help!:)

• 06-20-2008, 6:47 PM

  In reply to

  hautesecure Joined on 06-20-2008, 5:30 PM Posts 6 hautesecure

  Re: Proper syntax for msdeploy? Reply Contact Thanks...I tried and it failed as well: Informational: Pre-authenticating to remote agent URL 'http://xxxxxxxx:80 msdeployagentservice' as xxxxx. Informational: Attempting to sync without payload (optimistic sync).  Waiting f r response... Informational: Received response from agent (HTTP status 'Accepted') Informational: Agent requires 1707 payload entries to complete sync. Informational: Re-syncing with necessary payload.  Waiting for response... Informational: Processing any events fired during remote agent operation Informational: The dependency check 'IisVersion' found no issues Informational: The dependency check 'Iis5IsolationMode' found no issues Informational: The dependency check 'IIS7SourceUsingMetabase' found no issues Informational: The dependency check 'ConfigRedirection' found no issues Informational: The dependency check 'InUseDependency' found no issues Informational: The dependency check 'InstalledComponent' found no issues Informational: The dependency check 'DriveSpace' found no issues Informational: The dependency check 'IsapiCgiExistence' found no issues Informational: The dependency check 'UsingW3SVCMimemap' found no issues Informational: The dependency check 'AppPoolNotFound' found no issues Informational: The dependency check 'DisabledDependency' found no issues Informational: The dependency check 'NativeModuleExistence' found no issues Informational: The dependency check 'ProviderPathLevelMismatch' found no issues Informational: Source rootWebConfig32 (www.xxxxx.com) missing from destin tion parent (/lm/w3cv/1619542901/ServerComment).  Add pending Action: Adding child rootWebConfig32 (metaKey/metaProperty[@name='ServerComment ]/rootWebConfig32[@path=xxxx.com']) Fatal: Sync operation 'AddChild' failed with destination metaProperty (/lm/w3cv 1619542901/ServerComment) Debug: Microsoft.Web.Deployment.DeploymentException: Child element 'rootWebConf g32' can not be added to element 'metaProperty'    at Microsoft.Web.Deployment.DeploymentObject.AddChild(DeploymentObject sourc , Int32 position, DeploymentSyncContext syncContext)    at Microsoft.Web.Deployment.DeploymentSyncContext.HandleAddChild(DeploymentO ject destParent, DeploymentObject sourceObject, Int32 position)    at Microsoft.Web.Deployment.DeploymentSyncContext.SyncChildrenNoOrder(Deploy entObject dest, DeploymentObject source)    at Microsoft.Web.Deployment.DeploymentSyncContext.SyncChildren(DeploymentObj ct dest, DeploymentObject source)    at Microsoft.Web.Deployment.DeploymentSyncContext.SyncChildrenNoOrder(Deploy entObject dest, DeploymentObject source)    at Microsoft.Web.Deployment.DeploymentSyncContext.SyncChildren(DeploymentObj ct dest, DeploymentObject source)    at Microsoft.Web.Deployment.DeploymentSyncContext.ProcessSync(DeploymentObje t destinationObject, DeploymentObject sourceObject)    at Microsoft.Web.Deployment.DeploymentObject.Sync(DeploymentObject sourceObj ct, DeploymentSyncConfig syncConfig) Fatal: Child element 'rootWebConfig32' can not be added to element 'metaPropert '. Debug: Microsoft.Web.Deployment.DeploymentException: Child element 'rootWebConf g32' can not be added to element 'metaProperty'    at Microsoft.Web.Deployment.DeploymentObject.AddChild(DeploymentObject sourc , Int32 position, DeploymentSyncContext syncContext)    at Microsoft.Web.Deployment.DeploymentSyncContext.HandleAddChild(DeploymentO ject destParent, DeploymentObject sourceObject, Int32 position)    at Microsoft.Web.Deployment.DeploymentSyncContext.SyncChildrenNoOrder(Deploy entObject dest, DeploymentObject source)    at Microsoft.Web.Deployment.DeploymentSyncContext.SyncChildren(DeploymentObj ct dest, DeploymentObject source)    at Microsoft.Web.Deployment.DeploymentSyncContext.SyncChildrenNoOrder(Deploy entObject dest, DeploymentObject source)    at Microsoft.Web.Deployment.DeploymentSyncContext.SyncChildren(DeploymentObj ct dest, DeploymentObject source)    at Microsoft.Web.Deployment.DeploymentSyncContext.ProcessSync(DeploymentObje t destinationObject, DeploymentObject sourceObject)    at Microsoft.Web.Deployment.DeploymentObject.Sync(DeploymentObject sourceObj ct, DeploymentSyncConfig syncConfig) Change count: 1

• 06-20-2008, 7:02 PM

  In reply to

  hautesecure Joined on 06-20-2008, 5:30 PM Posts 6 hautesecure	Re: Proper syntax for msdeploy? Reply Contact OK, that seemed to work actually. So after it transfers over, should it populate in IIS? It didn't and i created a new site, and then reran sync to that ID, and it seemed to change the metadata properly.  However, the site doesn't run. Any clues on how to troubleshoot?

• 06-22-2008, 2:37 AM

  In reply to

  ksingla Joined on 06-14-2006, 3:02 AM Redmond, WA Posts 411 ksingla	Re: Proper syntax for msdeploy? Reply Contact What do mean by "populate in IIS"? Do you mean show up in UI? After the transfer is over, it should show in inetmgr. What is the error you are getting when trying to start the site?