When using 'Publish as web page' function in Excel 2013 to upload the data to ftp-server as html, it does not work if the file already exists in the ftp-server. Excel 2007 has no problem overwriting the file, but 2013 gives me the following message:

"ftp://ftp.server.fi/home/user/file.html' cannot be accessed. The file may be corrupted, located on a server that is not responding, or read-only'.

I have to manually delete the file from the ftp-server first and then publish as web page. This is quite annoying and extra work for me. And as I said, it still works with Excel 2007 with the same exact file, server and permissions. File permissions in the ftp server are 0644. It does not matter if the file is saved on my computer or SkyDrive.

I do not want at this point to switch to excel web app as I prefer publishing as web page. Any suggestions?

Hi,

Is it possible that the file is opened by other users?

And is this occurs to only this file or occurs to all the files? If this issue only occurs to this file, then maybe this file is corrupted. Try to create a new file to publish.

Hi,

Thanks for your reply. There's no one else using the file. As I said this also happens when the file is saved and used locally. It happens with every file I've tested.

I uninstalled Office 2007 and 2013 from my system and after a reboot installed Office 2013 again, but it didn't solve my problem. But it seems to be a local problem since I have no problems doing the upload with the same file, from SkyDrive, from another computer with Excel 2013.

When I use Excel 2013 save a file as a webpage to an FTP site and autorepublish is on, I get an error message that the AutoRepublish process caused an "ERROR: Cause is unknown"

When I do the same thing with the same file using Excel 2010, it works fine.

I would like to know how to get it to work on Excel 2013 since I purchased the upgrade.

Hi,

Any solution to the issue. Having the same issue with Excel 2013.

Same file open in both PC, 1 with 2007 and 1 with 2013. The autopublish will give this error when save with Excel 2013 and Ok with 2007.

Thanks, Michael