As the release date of our project was nearing, I had become a bit busier in the past few weeks. That would explain the absence of any activity in this blog. The long coding and debugging sessions were fun. We faced plenty of issues during deployment in our test environment. Had loads of fun solving them, though at times it was pretty stressful. Learnt a lot! Here, I am posting a couple of issues we faced and how we solved them.
We have a COM+ application in our project. It was working fine until one fine day, it started throwing the following error:
8000401A – “The server process could not be started because the configured identity is incorrect. Check the username and password.”
It turned out that all this while, whenever we had tested the COM+ application, someone was “interactively logged” into the server console. But, this time no one was. The identity for the COM+ application had been set as Interactive User. So, we got this error. Changing the identity to Local Service fixed this issue. But, the application threw another exception:
System.Data.Odbc.OdbcException: ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
This was because we had configured a User DSN to connect to the database. A user DSN is visible only to the user for whom it is configured. As the identity for the COM+ application had been set as Local Service, it was unable to find the DSN. Configuring a System DSN which is visible to all users of a machine solved this issue.
The COM+ application was making certain changes to the configured IPSec policy. It was working fine until the above changes were made after which it started throwing the following error:
ERR IPSec [05073] Unable to open Policy Store.
Clearly this was a user permission issue. So, the identity of the COM+ application was changed to “Administrator” instead of “Local Service”. And then, we all lived happily until the next bug showed its ugly face.
REFERENCES:
