I had a harrowing day at work; my password keeps getting locked everytime I do a SharePoint deployment and I had to do multiple deployments using stsadm commands. I had to change my password this morning when my password expired.
I error I was getting was: "The farm is unavailable" and in the Application event log: "Cannot generate SSPI context."
I figured, that the WFE was trying to log onto the SharePoint Database server and it wasn't able to do that. Almost all of the STSADM commands have to access the content database server. But I was lost for quite some time since I logged onto the WFE with my newer credentials and not sure where the older creds are picked up.
What I finally found out was one of the application pool running a SharePoint webapplication was using my credential as the identity account(where the password is not changed). When the stsadm command was running it will use the app pool account, so its trying to use the wrong crentials and after three retries the account is locked. It is really a bad practice to have an application pool running a personal account than a service account. I paid a price of two to three hours for this.
Monday, October 18, 2010
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment