Just did is a fresh installation of my app using the .NET managed handler. Ran into a problem when I tried to update my app online.
When I selected Upload Server Exe, it let me select the file and appeared to upload it, but then I got:
500 - Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.
I then copied the file over manually and hit Swap Server Exe. Again got the 500 error.
All other admin functions appear to be working correctly. My copies of wc.dll and webconnectionmodule.dll are current, and the config entries look correct:
<add key="ExeFile" value="f:\inetpub\aceweb\aw3.exe" />
<add key="UpdateFile" value="f:\inetpub\aceweb\updates\aw3.exe" />
Did I miss something in the setup process? I do have access to the server console so can apply updates manually but it would be handy to do it remotely.
--stein
OK, never mind.
I manually installed the new exe which of course required unloading the COM servers. I then restarted them and just for kicks tried the Swap Server option and it appears to have worked just fine:
The Exe file has been updated on your server and the latest version is now running.
Of course it just put in another copy of the same exe. I'll see what happens next time need to do a real update.
--stein
OK, tried an update tonight. I am still getting this when trying to upload a new exe:
500 - Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.
It brings up the dialog to select the file on my local system, then appears to upload it (shows % progress in the status area). But then shows the error.
If RDP to the server and copy the file over manually I can load it using Swap Server Exe. But not being able to upload kind of defeats the purpose...
--stein
If the upload fails then most likely you have a permissions problem. Make sure the application folder has rights to all the application pool identity to create the file in the location you have there. It could also be a file size issue - if your EXE is greater than 4megs it may fail the IIS POST buffer restrictions.
The file swapping can fail if the servers are not properly unloaded, but it sounds like you're not getting that far.
Also - the new features work best with the .NET Module.
+++ Rick ---
Permissions are correct, and I'm already using the .NET handler. But file size may well be the issue as my exe is 4.5 Megs.
As noted, the swap routine works fine if I use some other method to copy the exe up to the server.
--stein
I just tried putting the exe in a zip file and uploading that - worked just fine. So the problem is clearly the file being larger than 4 Mb.
--stein
Check here:
to bump your POST buffer to a larger size.
+++ Rick ---