AuthenticationFailed Error from MongoDB using ColdFusion 2021

I found that after changing the password for a MongoDB NoSQL DSN using ColdFusion Administrator you need to restart the ColdFusion Application service in Windows. Even changing to the correct password will cause a MongoDB authentication error:

Exception authenticating MongoCredential{mechanism=SCRAM-SHA-256, userName='{Your Username}', source='{Your Auth Source}', password=, mechanismProperties=} null

Command failed with error 18 (AuthenticationFailed): 'Authentication failed.' on server XXXXXXXXXXXXX:27017. The full response is {"ok": 0.0, "errmsg": "Authentication failed.", "code": 18, "codeName": "AuthenticationFailed"}

This error may be logged in the MongoDB server log:

{"t":{"$date":"2021-11-08T14:39:07.067-06:00"},"s":"I",  "c":"ACCESS",   "id":20249,   "ctx":"conn122","msg":"Authentication failed","attr":{"mechanism":"SCRAM-SHA-256","speculative":false,"principalName":"{Your Username}","authenticationDatabase":"{Your Auth Source}","remote":"XXX.XXX.XXX.XXXX:51204","extraInfo":{},"error":"AuthenticationFailed: SCRAM authentication failed, storedKey mismatch"}}

After the most recent Windows 10 update (1703); my very solid and stable workstation started getting blue screens.

Being a windows user for more than twenty years I’ve come to expect the occasional BSOD. Things fail. It just happens.

So while the first BSOD was troubling; I was not immediately alarmed.

After the third BSOD I knew something was wrong.

Running WhoCrashed revealed the root cause to be:

netwtw04.sys

A bit of searching revealed that to be WiFi related.

I fixed my problem by downloading the latest reference drivers from my WiFi networking card manufacturer.

Ran across an interesting problem. While setting up a new Windows 2008 R2 erver and website on IIS; I noticed that the site was generating 500 errors when serving static files (images, css, html, etc.)

I turned on Failed Request Tracing and noticed that I was getting this logged

This configuration section cannot be used at this path. 
This happens when the section is locked at a parent level. 
Locking is either by default (overrideModeDefault="Deny"), or set explicitly by a location tag with overrideMode="Deny" or the legacy allowOverride="false".

Based simply on previous experience I went to the IIS Feature Delegation and reviewed the delegation for the various IIS modules.

I found that by setting Handler Mappings to Read/Write the error was resolved.

I’m still not sure why this causes a problem since I’m not defining any custom handlers at the site level.

Perhaps this setting must be read/write even when custom handlers are set at the server level?

I upgraded from Windows 7 Enterprise to Windows 8 Enterprise. My upgrade was very smooth. Probably the easiest Windows upgrade I’ve done. The new OS seems as solid as Windows 7. I thought the new Modern UI (aka Metro) would present a problem in my day to day use of the OS and applications. Surprisingly this is not true. While I’m not terribly impressed with the UI it’s fairly easy to ignore. It essentially replaces the Start Menu with a full screen UI. The Desktop view is still available and works as it has in previous versions of Windows.

In fact, the only real complaint I have about Windows 8 is that it’s going to be a tough sell to the casual user. The replacement of the Start Menu could be just enough to scare them and it doesn’t appear to enhance anything about the Windows experience. In my short time with Windows 8 I’ve already spent 99% of my time outside of the Modern UI and it’s Apps.

Windows 8 is a good OS, but probably not worth the upgrade for the casual computer user.