CF2018 on IIS 10 Windows 2019 giving 404 randomly instead of redirecting or displaying default page

[Guest]

This is happening when there is no slash or sub directory in th url.

Running 

Server Error

404 - File or directory not found.
The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.
The requested URL was not found on this server!
If you entered the URL manually please check your spelling and try again.

Tomcat/ISAPI/isapi_redirector/1.2.46

Copyright © 1999-2018 Apache Software Foundation
All Rights Reserved

[WolfShade]

The only thing that I can think of is to make sure that you have default documents set up properly in IIS, and that there is at least one document in the folder that is in the list of default documents.

V/r,

^ _ ^

[paule12345]

Are you on CF2018 Update 5?  If so, the intermittent 404 may be due to the buggy connector that Adobe issued with Update 5.   Check the comments area of this thread for a Dropbox link to download an updated connector:

https://coldfusion.adobe.com/2019/09/coldfusion-2018-release-update-5-coldfusion-2016-release-update...

[Charlie Arehart]

Good call, Paul, but see the updated post from Adobe (for people experiencing problems with IIS or Apache after the recent updates) ,  where they offer an updated link to the .dll (for IIS) or .so (for Apache) which addresses connector issues.

https://coldfusion.adobe.com/2019/10/error-accessing-coldfusion-administrator-using-connector-port/

I do realize that the title of the blog post may lead some to think that it does not apply to them, but it is the only connector update I’ve seen offered so far for the Sept CF updates, so it’s worth giving it a shot to see if it solves your problems. (Of course, getting to the Sept. updates is important for the security fixes they offer.)

If this connector update doesn’t solve your problem, report that to cfinstal@adobe.com (yep, that’s one “L”).

[Guest]

Thanks for the replies on this. Adobe provided an updated isapi_redirect.dll file to correct this issue.