Installation and deployment
Version 7.x > Installation and deployment > Staging Server Service URL Returns 404 View modes: 
User avatar
Member
Member
andrew-robulack - 2/11/2014 11:29:16 AM
   
Staging Server Service URL Returns 404
I'm following the instructions in the "Kentico CMS 7.0 Developer's Guide" on pages 2127 through 2130.

I've gotten to the point where I input and test the "Server service URL" for the target server. When I test it, I get this message:

###

The remote server returned an error: (404) Not Found.

at System.Net.HttpWebRequest.GetRespond()
at CMSAdminControls_UI_System_ServerChecker.CheckServer(String parameters)

###

A few notes:

-I've changed the C:\\inetpub\wwwroot\bin\Microsoft.Web.Services3.dll file name on both servers
-I've triple-verified the authentication information (name and password)
-I've triple-verified that the "Enable staging service" box is checked on the target server
-I've triple-verified that the URL is correctly formatted: https://www.domain.com/CMSPages/SyncServer.asmx (I've tested both http and https)
-I've verified the error in the Activity Log; the Event Code is, "PAGENOTFOUND"
-I've verified that the target file actually exists on the server
-I've verified that I can access other files in the directory along with the SyncServer.asmx file (using a browser on the source server)

So I'm stumped... what else might be the problem?

User avatar
Member
Member
andrew-robulack - 2/11/2014 1:10:56 PM
   
RE:Staging Server Service URL Returns 404
It looks like there's a problem running asmx files on these servers. I checked the web server log and here's a record of the transaction (I've anonymized the IPs):

2014-02-11 18:26:29 66.11.000.000 GET /CMSPages/SyncServer.asmx - 80 - 199.247.000.000 Mozilla/5.0+(Windows+NT+6.3;+WOW64;+Trident/7.0;+MDDCJS;+rv:11.0)+like+Gecko 404 7 0 138

The protocol status is 404, and the protocol substatus is 7. According to Microsoft (http://support.microsoft.com/kb/943891) that means, "File extension denied".

So I'm taking that to mean that the asmx extension has not been set up correctly.

Unfortunately, I'm no IIS wiz, so I'm wondering if anyone out there is and has some sort of quick fix to this problem. Web searches on this issue indicate there's probably no easy fix.

Any sort of insight or input is appreciated.

User avatar
Member
Member
andrew-robulack - 2/11/2014 2:09:44 PM
   
RE:Staging Server Service URL Returns 404
Just to wrap this up here in case anyone else ever has a similar problem...

I’ve sorted this out and the Server Service URL is now reporting an “OK” status.

In a nutshell, the file extension .asmx was missing from the Request Filtering panel in IIS. Once I added it and made sure it was enabled, the server responded OK.