Hi Rick,

I have been messing with my app that we fixed a couple of weeks ago. I had a strange thing happen today, I got a message that reads as follows when I tried to load the COM servers. They would not load automatically.:

Retrieving the COM class factory for component with CLSID {79C2CA07-7190-42C6-8BA9-5E991EC73B98} failed due to the following error: 8000401a The server process could not be started because the configured identity is incorrect. Check the username and password. (Exception from HRESULT: 0x8000401A).

The change I made was in IIS URL Rewrite, I changed the script from Action Type: Redirect to "/" to Rewrite with /Default.wcsx

This change was done because I needed to get to a specific page that was not the login page which resides in the default.wcsx page. This is working fine all except this error which only started once my Remote Connection to the server timed out. Otherwise both the default and the target page I was not able to get to before are both working along with all the rest of the system.

After loggin back in with remote Connection and restarting the IIS domain, it again seems fine. So this is just a question to see if you think I screwed up the URL Rewrite which caused this problem.

Best,

Url Rewrite can be finicky and you often have to reset IIS for the routes to fully adjust. There's some sort of caching that can screw things up. If it works after restart then you're probably fine.

But... rewrite and redirect behave very differently. Rewrite internally re-routes the request - meaning the URL doesn't change. Internal basically routes to a different handler based on the new Url without exiting the existing request pipeline. Redirect externally re-routes by completely re-running the new url as a new request.

Sometimes they behave similarily - sometimes not. For most rewrite scenarios you'd want Redirect not Rewrite because you likely want the URL to change.

+++ Rick ---

Does this recommendation from Claude and your documentation page make sense at this point, keeping in mind the system has been running for over ten years without this being an issue ever before...?

In DCOM > Identity the account has been set to "The Interactive User" which I am assuming was done at the time I first created the site. After letting Claude read your documentation COM Security and Identity the recommendation was to change the account to "The launching User" and then restart IIS.

I am currently trying this change and waiting the 20 minutes for timeout to activate and shut down the servers. I will report back later today...

For production you don't want Interactive User because it forces your machine to be logged on. With another account the server is invisible and runs on an invisible desktop (or should be off per .ini settings).

For development Interactive User is fine and useful as you can see the server window and see errors pop up. But then in development you're likely running in File mode so you can debug your code and find any issues that way.

The only time Interactive really is useful if you have COM specific failures usually related to startup and so you can test locally and potentially pop up some error messages. Arguably this can be done better with trace messages, but wait windows or message boxes always seem to win out for most people...

+++ Rick ---