Previous Next

• 08-07-2008, 8:27 PM

  SparksFlyn Joined on 06-19-2002, 6:15 AM Pierre, SD Posts 11

  The Operation has timed out. Reply Contact I am running the MS Web deploy Tool Beta 1.  Trying to sync an IIS6 staging server as source to an IIS6 Web Front End as destination. I get Fatal: The Operation has Timed Out in my log.  Here is my command line:  msdeploy -verb:sync -source:webserver60,computerName=http://<deafult web site>:8080/MyMSWebDeploy/ -dest:webserver60 -disableRule:DefaultDependencyCheck -whatif -verbose -debug > MSMyWD.log   Fatal: The operation has timed out.  Debug: System.Net.WebException: The operation has timed out.    at System.Net.ConnectStream.Read(Byte[] buffer, Int32 offset, Int32 size)    at System.IO.BufferedStream.Read(Byte[] array, Int32 offset, Int32 count)    at System.IO.BinaryReader.ReadBytes(Int32 count)    at Microsoft.Web.Deployment.PackageProvider..ctor(BinaryReader reader, String fileName, PackageDeserializer deserializer)    at Microsoft.Web.Deployment.PackageProvider..ctor(BinaryReader reader, String fileName, PackageDeserializer deserializer)    at Microsoft.Web.Deployment.PackageProvider..ctor(BinaryReader reader, String fileName, PackageDeserializer deserializer)    at Microsoft.Web.Deployment.PackageProvider..ctor(BinaryReader reader, String fileName, PackageDeserializer deserializer)    at Microsoft.Web.Deployment.PackageProvider..ctor(BinaryReader reader, String fileName, PackageDeserializer deserializer)    at Microsoft.Web.Deployment.PackageProvider..ctor(BinaryReader reader, String fileName, PackageDeserializer deserializer)    at Microsoft.Web.Deployment.PackageProvider..ctor(BinaryReader reader, String fileName, PackageDeserializer deserializer)    at Microsoft.Web.Deployment.PackageProvider..ctor(BinaryReader reader, String fileName, PackageDeserializer deserializer)    at Microsoft.Web.Deployment.PackageProvider..ctor(BinaryReader reader, String fileName, PackageDeserializer deserializer)    at Microsoft.Web.Deployment.PackageProvider..ctor(BinaryReader reader, String fileName, PackageDeserializer deserializer)    at Microsoft.Web.Deployment.PackageProvider..ctor(BinaryReader reader, String fileName, PackageDeserializer deserializer)    at Microsoft.Web.Deployment.AgentClientProvider.get_PackageProviderInternal()    at Microsoft.Web.Deployment.AgentClientProvider.get_Name()    at Microsoft.Web.Deployment.DeploymentSyncContext.ProcessSync(DeploymentObject destinationObject, DeploymentObject sourceObject)    at Microsoft.Web.Deployment.AgentClientProvider.RemoteSourceSync(DeploymentObject destObject, DeploymentObject sourceObject, DeploymentSyncConfig syncConfigOriginal)    at Microsoft.Web.Deployment.DeploymentObject.Sync(DeploymentObject sourceObject, DeploymentSyncConfig syncConfig) Change count: 0 Fatal count: 1 What should I try next, please?     -OOPs! Shouldn't have touched that with a screwdriver while plugged in!

• 08-18-2008, 1:15 PM

  In reply to

  SparksFlyn Joined on 06-19-2002, 6:15 AM Pierre, SD Posts 11

  Re: The Operation has timed out. Reply Contact I was checking to see if the service is running on my servers.  I found an earlier post that said to run: netsh http show urlacl.  When I run this on my Windows Server 2003 SP2 w/IIS6, it says the following command was not found: http show urlacl. It this something new in Window Server 2008?  Is there another method to find out if the service is working or not? I am able to do the other examples such as to dump and make a backup of the configuration.  That shows me that the MSDeploy.exe is working. -OOPs! Shouldn't have touched that with a screwdriver while plugged in!

• 08-18-2008, 1:38 PM

  In reply to

  SparksFlyn Joined on 06-19-2002, 6:15 AM Pierre, SD Posts 11

  Re: The Operation has timed out. Reply Contact I was able to answer my own question.  I found what I was looking for in the MSDeploy.chm file. At a Windows Server 2003 command prompt, type httpcfg query urlacl. The Httpcfg.exe file is part of the Windows Support Tools. For more information, see Configuring the HTTP Kernel-Mode Driver (Http.sys). -OOPs! Shouldn't have touched that with a screwdriver while plugged in!

• 08-18-2008, 3:17 PM

  In reply to

  SparksFlyn Joined on 06-19-2002, 6:15 AM Pierre, SD Posts 11

  Re: The Operation has timed out. Reply Contact I am having to tinker with my command line.  I was able to verify that the MSDepSvc is working.  I was able to copy the httpcfg.exe file from my staging server to the WFE using the command: msdeploy -verb:sync -source:dirpath=C:\WINDOWS\Support,computerName="http://Server1:8080/MyMSWebDeploy" -dest:dirpath=C:\WINDOWS\Support But I still get a timeout with -source:webserver60.  I will try with a smaller subset. -OOPs! Shouldn't have touched that with a screwdriver while plugged in!

• 08-18-2008, 4:36 PM

  In reply to

  SparksFlyn Joined on 06-19-2002, 6:15 AM Pierre, SD Posts 11

  Re: The Operation has timed out. Reply Contact msdeploy -verb:sync -source:metakey=LM/W3SVC/860641225,computerName="http://Server1:8080/MyMSWebDeploy" -dest:metakey=LM/W3SVC/860641225 -disableRule:DefaultDependencyCheck -whatif -verbose -debug > MSWDTelescope.log With this command line, I get this in my log: Informational: Skipping destination rootWebConfig64 (metaKey/metaProperty[@name='ServerComment']/rootWebConfig64) due to rule BitTo64BitRuleHandler Informational: Skipping destination machineConfig64 (metaKey/metaProperty[@name='ServerComment']/machineConfig64) due to rule BitTo64BitRuleHandler Change count: 0  My metabase.xml file is 1,163 KB in size.  Is there a size limitation that would be causing the timeout?   -OOPs! Shouldn't have touched that with a screwdriver while plugged in!

• 08-19-2008, 1:28 PM

  In reply to

  SuperTramp Joined on 07-07-2008, 2:41 AM Seventies Posts 15

  Re: The Operation has timed out. Reply Contact This shouldn't be related to the size of the metabase.  Probably more related to the size of the content in your directories.  There are some bugs related to have large content vdirs and worse when you have multiple vdirs pointing to the same (large) physical directories.  Can you try adding a "-disableLink:ContentExtension".  This will tell us not to copy over content.  That will help isolate the problem. Thanks for your help.

• 09-16-2008, 9:04 PM

  In reply to

  SparksFlyn Joined on 06-19-2002, 6:15 AM Pierre, SD Posts 11

  Re: The Operation has timed out. Reply Contact Thank you!  That parameter worked.  I am now getting an eyeful of entries in the log.  There were 86 changes at the end of the report.  I have been using RoboCopy to replicate changes for the web content for the past few weeks.  This will now allow me to get the IIS changes moved out to the farm, hopefully.  I will be doing further testing. I found the parameter -disableLink:ContentExtension in the msdeploy_readme.html under Known Issues reguarding moving more than a million files and folders.  I am examining my staging server now for the specs.  I wonder if that threshold might need to be lowered?  I have 492,471 files across 27,657 folders for 18.7 GB of content on my staging server.  So you can see why I might have ignored that parameter.  But I can see now that I am going to have to chunk up my deployment into smaller pieces to get this done.  But this is good!  I can move forward again.   -OOPs! Shouldn't have touched that with a screwdriver while plugged in!