>Hi there
>
>I have seen a few posts about this one already but none that have a
>solution. There appears to be a bug report at
>
>http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx?feedbackid=d0279ec7-8730-4445-9f3e-1d1a01235cf1
>
>but this was closed as it could not be reproduced by Microsoft.
>
>Well I can reproduce it and having found two or so posts I guess there is a
>problem somewhere.
>
>Basically when I try to copy a project to the ISP using the Copy Project
>Option on either http or Ftp the copy takes place and then the upload hangs.
>When you close the copy option using the x in the top right hand corner the
>error message is:
>
>"Could not find a part of the path c:\windows\.......... PublichState.xml"
>
>I have checked the path and this path doesn't exist.
>
>I am working using Visual Studio 2005 Pro on Windows XP Pro and the website
>is being developed on IIS 6.0 on a Windows 2003 Server. So in effect when I
>am trying to copy the site I am attempting to copy the website from one IIS
>Server (my development machine) to another IIS Server (the production server
>at the ISP).
>
>Any help appreciated.
>
>PS I was origonally going to post on the Visual Studio group but an earlier
>post there said that the VS Web Tools team monitor this group.

>Thanks for Otis's input.
>
>Hi mfewtrell,
>
>For the publishState.xml file, it's used internally for maintaining the
>status info during our copy web site operation, so far we haven't any
>documented info on it. However, it is likely that in your environment, this
>file is not created correctly or get corrupted. Based on my test, this file
>will be created when we start connecting to a remote site and application
>to do the copy site. And the file is created under the
>
>C:\Documents and Settings\{current user}\Local Settings\Application
>Data\Microsoft\WebsiteCache\{ebApplicationName}
>
>You can mointor the directly when you try performing copy website. If that
>exists, you can try deleting it and reconnect the remote site again to
>test.(and deleting the complete application dir under WebsiteCache is also
>possible for test).
>
>Thanks,
>
>Steven Cheng
>Microsoft Online Support
>
>Get Secure! www.microsoft.com/security
>(This posting is provided "AS IS", with no warranties, and confers no
>rights.)

"Otis Mukinfus" wrote:

> On Wed, 22 Feb 2006 05:31:30 GMT, stch***@online.microsoft.com (Steven
> Cheng[MSFT]) wrote:
>
> >Thanks for Otis's input.
> >
> >Hi mfewtrell,
> >
> >For the publishState.xml file, it's used internally for maintaining the
> >status info during our copy web site operation, so far we haven't any
> >documented info on it. However, it is likely that in your environment, this
> >file is not created correctly or get corrupted. Based on my test, this file
> >will be created when we start connecting to a remote site and application
> >to do the copy site. And the file is created under the
> >
> >C:\Documents and Settings\{current user}\Local Settings\Application
> >Data\Microsoft\WebsiteCache\{ebApplicationName}
> >
> >You can mointor the directly when you try performing copy website. If that
> >exists, you can try deleting it and reconnect the remote site again to
> >test.(and deleting the complete application dir under WebsiteCache is also
> >possible for test).
> >
> >Thanks,
> >
> >Steven Cheng
> >Microsoft Online Support
> >
> >Get Secure! www.microsoft.com/security
> >(This posting is provided "AS IS", with no warranties, and confers no
> >rights.)
> Thank you Steven
>
> Otis Mukinfus
> http://www.arltex.com
> http://www.tomchilders.com
>

"Steven Cheng[MSFT]" wrote:

> Thanks for followup Martyn,
>
> Glad to hear that you've got it working now. Could it be something with
> network ,sometimes this could be the cause.
>
> Regards,
>
> Steven Cheng
> Microsoft Online Support
>
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>
>