Not sure about Diskeeper, but since the error is related to slow access (thread output stream) possibly by something interrupting or
slowing the data stream, it could be interfering
- try turning it off
(also try defragging your hard drive as that was indicated as another cause of the slow access)
| Sir,
|
| Thank You for your reply. Those are the only two articles that I could find
| also. As you noted, neither are related to "Publishing".
|
| Since I am desparate, I will "again" recalculate hyperlinks on the source
| server, and check the Server Extensions - and health - on the destination
| server ( They are both in the same room, my office). I might even check the
| health of the source server, just to be sure. And try again, and again, and
| again.
|
| It just occured to me that I have Diskeeper running on the source server.
| Does anyone think that might be interfering with the publish operation?
|
| Thank You,
|
| Larry Barnhill
|
| "Stefan B Rusynko" wrote:
|
| > You are correct in that the error appears to be related to a "thread output stream"
| > Only ref to that error I can find is
| >
http://support.microsoft.com/default.aspx?scid=kb;en-us;234583
| > and
| >
http://support.microsoft.com/default.aspx?scid=kb;en-us;218464
| > - but neither is directly related to publishing
| > Both indicate a slow server due to large or fragmented files
| > Try opening the site online and running a Tools Recalculate Hyperlinks or having your host check the server performance (health)
| > --
| >
| > _____________________________________________
| > SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
| > "Warning - Using the F1 Key will not break anything!" (-;
| > To find the best Newsgroup for FrontPage support see:
| >
http://www.net-sites.com/sitebuilder/newsgroups.asp
| > _____________________________________________
| >
| >
| > | > | Mr. Rusynko, Thank you very much for your reply. However, when publishing to
| > | a server, the write process is from the source - in this case the Win2K
| > | currently active web server - to the destination - in this case the new
| > | Win2k3 server. A write error would imply that the "file" is on the
| > | destination, and Frontpage cannot write to it.
| > |
| > | A "thread output stream" doesn't sound to me like a file, but more like a
| > | process
| > | handle. Please correct me if I'm wrong. I have searched both machines, and
| > | neither have a "file" by that name. This is the first time that I've seen
| > | this error while trying to publish this "#*/?@" blinkety Web Site to this new
| > | server. Now why would Frontpage try to write to a "thread output stream" ?
| > | Technically, all it should be doing is copying a file structure from one
| > | machine to another, or ? Does it make a difference if the indexing service is
| > | running on the destination/source? Could that be the "process" that Frontpage
| > | is trying to write to ?
| > |
| > | Please share your thoughts on this, if I'm in left field, let me know.
| > |
| > | Sincerely,
| > |
| > | Larry Barnhill
| > |
| > | "Stefan B Rusynko" wrote:
| > |
| > | > If you have a file named "thread output stream" it is not a valid name (mime type) and your host server will not accept it
| > | > Try renaming it w/o spaces and w/ a proper file type extension (like.htm if it is a web page)
| > | >
| > | > --
| > | >
| > | > _____________________________________________
| > | > SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
| > | > "Warning - Using the F1 Key will not break anything!" (-;
| > | > To find the best Newsgroup for FrontPage support see:
| > | >
http://www.net-sites.com/sitebuilder/newsgroups.asp
| > | > _____________________________________________
| > | >
| > | >
| > | > | > | > | Ladies and Gentlemen,
| > | > |
| > | > | Will someone please tell me what causes this error - when publishing a web
| > | > | site based on W2k server, to a server running Win2k3 server Enterprise
| > | > | Edition, using
| > | > | Frontpage 2000 and FPSE 2002, and how I can avoid it ? ( So that I can
| > | > | hopefully finish publishing this web site )
| > | > |
| > | > | Thank You in advance for any suggestions or comments,
| > | > |
| > | > | Larry Barnhill
| > | >
| > | >
| > | >
| >
| >
| >
