Web Site Publisher
Known issues ...
Web Site Publisher should be trouble free, but occasionally problems do arise. The list below shows all known problems. Follow the links to see any known work around and whether the problem has been resolved in a later version:
- Error code (C): 12002 - Timed out
- Failed to connect to server ... Overlapped I/O operation is in progress
- Help! Something is wrong - where can I get help on Web Site Publisher?
- Problem changing directory - The system cannot find the path specified
- Status: Needs publishing
- The WEBSITEPUBLISHER.EXE is linked to a missing export OLEAUT32.DLL: VarNot
- The WEBSITEPUBLISHER.EXE is linked to a missing export WININET.DLL: FtpCommandA
- Windows 95 and Windows 98 (first edition)
Troubleshooting notes for older expired versions of Web Site Publisher are available for reference here.
When Web Site Publisher is copying files up to the FTP server the following error is generated and publishing stops:
Error: Failed to copy file ... Error code (C): 12002 Description: Timed out
Cause and Resolution
This error indicates that whilst trying to copy a file up to the server no response was received from the server for sufficiently long that Web Site Publisher has timed-out the connection. Web Site Publisher times out the connection because sometimes the most effective way of dealing with a slow and unresponsive FTP server is to stop and try again. There is a limit to how many times Web Site Publisher will attempt to reconnect and restart the copy, and this error indicates that this limit has been reached.
There is no single best approach to dealing with this error (because it may indicate a problem at the server end), but the following suggestions are known to have got around this problem:
- If you are on a good broadband connection and have successfully been able to publish your website previously then the problem probably lies either with the FTP server or with issues which are slowing the connection between your PC and the FTP server - in the latter case the issue may be nearer to the FTP server than to you so in all other respects the internet may seem fine. The simplest (but least satisfying) approach is to wait a few hours or until the following day and try again.
- You could try increasing the timeout value. The initial timeout value
(30 seconds in Web Site Publisher version 2.1.2, 20 seconds in earlier
versions) should be more than adequate when working on a broadband
connection and for most dial-up connections. To increase the timeout:
- Open the properties for the web site.
- On the "FTP" parameters tab, under the section "Timeout Settings" increase the value for "All other timeouts (secs)".
- Click [Save], and then try to republish.
When Web Site Publisher is attempting to connect to a server the following error is generated:
Failed to connect to server XXXX Error code: 997 Description: Overlapped I/O operation is in progress
where "XXXX" is the name of the server. The connection attempt fails.
Cause and Resolution
This error has been observed on systems with both LAN/broadband and dial-up networking options available, where the dial-up networking was active but the web site could only be successfully published via the LAN/broadband connection.
To resolve this problem do not attempt to publish the website while the dial-up networking connection is active. Ensure that the connection for the web site is specified as "LAN only", since this will not publish the web site if a dial-up connection is active.
Since Web Site Publisher is free, it does not come with any support. However if you have looked over these troubleshooting notes and consulted the FAQ and still cannot find an answer to your question then the author can be e-mailed care of email@example.com. Please include a description of the problem and state which version of web site publisher you are using.
Remember: By reporting a problem you are helping to make the tool better for everyone.
When trying to publish a website the following error is reported and publishing stops:
Publishing website Connecting to ftp.for.website/folder/
Connected ... starting to publish
Problem changing directory to ftp.for.website\folder (error 12003) Internet extended error: 550 /folder: The system cannot find the path specified.
Where items in italics will be specific to your website.
If publishing was always successful with a version prior to 2.0.x but fails immediately after upgrading to version 2.0.x then this is most likely due to a bug in version 2.0.x.
2.0.3, 2.0.4 and 2.0.5
This bug affects those cases where the initial folder on the FTP server is a folder other than the root. In this case Web Site Publisher incorrectly ignores the initial folder and tries to publish relative to the root. Since the majority of FTP servers have the initial folder the same as the root folder, this problem will only affect the minority of users.
This problem is resolved in version 2.1.0.
If publishing was always successful with version 2.0.x but fails after upgrading to version 2.1.x (or later) this is most likely due to a change in the behaviour of Web Site Publisher. (The behaviour change introduced in version 2.1.0 is a return to the behaviour prior to version 2.0.0.)
Version 2.1.0 onwards.
Version 2.0.x ignored the initial folder on the FTP server. This behaviour was incorrect, and has been restored in later versions. The problem is observed where the home folder on the FTP is a folder other than the root.
Open up the properties of the website in Web Site Publisher. On the "FTP parameters" tab check "Ignore FTP home folder".
Normally when Web Site Publisher reports the status of a website as "Needs publishing" it is because something local has been changed which has not yet been pushed up to the server, and the resolution is simply to publish the website.
An obscure bug existed which meant that some sites would report "Needs publishing" after having been published (with no changes to the local file system) whenever the status was updated (either when pressing F8 to request a status update or when restarting Web Site Publisher). This affected some sites which used "Exclusions", specifically when file types were set to be ignored on the server.
This error was first reported in version 2.1.0, but will have existed in previous versions as well.
Cause and Resolution
The problem was related to how Web Site Publisher counts pages on the website. This figure did not take into account files which might exist on the server but which are not copied. This caused Web Site Publisher to think that the local site had fewer files than were on the server which triggered the status being flagged as "Needs publishing".
This problem is fixed in version 2.1.1, so upgrading to the latest version will fix the problem.
When attempting to run Web Site Publisher a message box appears containing the following error:
The WEBSITEPUBLISHER.EXE is linked to a missing export WININET.DLL: FtpCommandA
All - but only on those machines with Microsoft Internet Explorer 4 or earlier installed.
Cause and Resolution
This error is caused by the PC having an older version of the Microsoft WinInet (Windows-Internet) dll, which is distributed with Internet Explorer. To resolve the issue upgrade to Internet Explorer 5 or later.
If you attempt to run Web Site Publisher on a machine running Windows 95 or Windows 98 (first edition) then you may encounter the following DCOM error:
The WEBSITEPUBLISHER.EXE is linked to a missing export OLEAUT32.DLL: VarNot
This error can be resolved by either:
- downloading the latest DCOM service pack from Microsoft (http://msdn.microsoft.com):
- On a Window 95 machine download and install DCOM95 for Windows 95 version 1.3 (at the last time of checking this was available for download from http://www.microsoft.com/com/dcom/dcom95/dcom1_3.asp).
- On a Windows 98 machine download and install DCOM98 for Windows 98 version 1.3 (at the last time of checking this was available for download from http://www.microsoft.com/com/dcom/dcom98/dcom1_3.asp).
- downloading a newer version of Internet Explorer (since this will automatically update the DCOM components).