I wanted to provide another round of updates as we've run into this issue two more times.

The most recent time we had the issue an app restart did stop the error from being written to the ma.log, but the corrupt file was still hanging around. After several days it did go away, so it seems whatever process Mango uses to clean up the files eventually worked.

While working with the support team we were pointed to look for other programs that could possibly lock one of the data files while NoSQL is trying to write to it. If that happens, this issue could occur.

I checked with our infrastructure team and they had an antivirus program that was performing checks on the NoSQL database directory. The antivirus has been disabled for that folder now.

I also found this post about Windows Indexing locking files: https://techcommunity.microsoft.com/t5/windows-blog-archive/the-case-of-the-mysterious-locked-file/ba-p/723349 Because of this I made sure to uncheck the "Allow files in this folder to have contents indexed..." option as that could have also contributed to the file being locked when NoSQL needed to write to it.

So far things are good since making those updates. Hopefully this helps anyone that may run into this.

Thanks,
Chad

To get around my issue, we created a \rdsdbdata\db folder so Mango can read it, even though our DB is not local to the app server.

It's been well over a month and we haven't seen the issue come back. I think it's safe to say the problem is resolved.

Thanks @MattFox for the suggestions and being active in the forum! Your posts have helped me more than you know.

After trying various things with the file; elevating my privileges in Windows to System and still failing to do anything with it, we stopped Mango and tried to manipulate the file with no luck.

The good news is that when we restarted Mango, it looks like it removed the trouble file for us and all is good now.

Thanks,
Chad