Hi, Was working on my development server earlier this evening. Unfortunately my account got locked out. To worsen the matter none of the NT Admin guys are available (of course its Sunday night!) across the enterprise. This account peculiarly locks (I'm talking about least count 10 times a day! NT is practically tired of me!). Well, not my fault because a developer I work with has used it in many configurations. So, NT gave me a new alternate account since about 4 weeks now (I haven't used it since then). Now that crazy account locked me out tonight (and I definitely can't wait till tomorrow to finish this task). So, I decided to log on using the new account, unfortunately I re-started my lab server (before it dawned on me I shouldn't have done that...too late!). Well, rebooting, can't log in, so I used my new account. Well, Central Admin wouldn't respond to me, so I went into the Web App in IIS and reconfigured them with my new account (16 of them!). Went into the Services console and reconfigured SQL with the new account. Well, Central Admin still isn't responding. SQL Server Studio console ran, I went into the Security section and configured my new account as a db-owner in all databases and content databases. Well, Central Admin still didn't come up....argghhh! Am furious right now. So, I finally decided to use the stsadm -o updatefarmcredentials syntax. Well it threw this message One or more errors deploying administration application pool credentials. Please check the application event log and fix manually. I checked the log and found these in separate events item: Error reencrypting credential Id 1b061409-81a4-43f8-9dc8-0ff5e63009b8 with owner Id 071e5877-9c34-4fcc-91c4-a6d38a3a6ab8 during deploying of administration application pool credentials, please recreate credential manually. Operation is not valid due to the current state of the object. -------------------------------------------------------------------------------- The Execute method of job definition Microsoft.Office.Server.Search.Administration.IndexingScheduleJobDefinition (ID fe820736-4bbe-4a96-a361-96f01f5fa0da) threw an exception. More information is included below. Retrieving the COM class factory for component with CLSID {3D42CCB1-4665-4620-92A3-478F47389230} failed due to the following error: 8007042d. ---------------------------- Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (5cb49bbe-b4f4-4c17-a311-e3a537b9c1e8). Reason: Retrieving the COM class factory for component with CLSID {3D42CCB1-4665-4620-92A3-478F47389230} failed due to the following error: 8007042d ---------------------------- The Execute method of job definition Microsoft.Office.Server.Search.Administration.IndexingScheduleJobDefinition (ID fe820736-4bbe-4a96-a361-96f01f5fa0da) threw an exception. More information is included below. Retrieving the COM class factory for component with CLSID {3D42CCB1-4665-4620-92A3-478F47389230} failed due to the following error: 8007042d. ------------------------------- Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (5cb49bbe-b4f4-4c17-a311-e3a537b9c1e8). Reason: Retrieving the COM class factory for component with CLSID {3D42CCB1-4665-4620-92A3-478F47389230} failed due to the following error: 8007042d ------------------------------- The SSP Timer Job Distribution List Import Job was not run. Reason: The referenced account is currently locked out and may not be logged on to Technical Support Details: System.ComponentModel.Win32Exception: The referenced account is currently locked out and may not be logged on to at Microsoft.Office.Server.Utilities.WindowsSecurity.GetUserTokenFromCredentials(String userDomainName, String password, LogonType logonType) at Microsoft.Office.Server.Utilities.WindowsSecurity.GetUserTokenFromCredentials(String userDomainName, String password) at Microsoft.Office.Server.Administration.JobHandler.Execute(Object state) -------------------------------- I decided to run the other stsadm command with the -local syntax, and it returned this stuff below: To ensure that all credential caches in IIS have updated, you must run the comma nd "IISRESET /NOFORCE" on all servers in the farm. This should be done after al l credential updates have been completed. Operation completed successfully. Well, I felt relieved at this message. I followed the advise from the command prompt and did as it said by running the IISRESET (normal stuff). The good news was that this time Central Admin came up and requested credentials. I was so glad! After waiting like what was eternity, then I got this on the browser with that sweet looking blue, orange and white SharePoint background (y'know what I mean right): Go back to site Error An unexpected error has occurred. troubleshoot issues with Windows SharePoint Services F.R.U.S.T.R.A.T.I.N.G!...WELL, GUESS WHAT, while I was about posting all this stuff you've seen already as a question on this forum, I stretched my hands to the lab server and r.e.f.r.e.s.h.e.d the screen and CENTRAL ADMIN pops up...voila!!! So if you ever get locked out and no NT guys around to unlock you and time is of the essence, then, do everything i have mentioned in this post and you will be fine. Cheers everyone! Have a lovely Sunday night!You've only got one life; help as many people as you can, and enjoy it while it lasts.

Hi ISSALY, Lesson = learnedYou've only got one life; help as many people as you can, and enjoy it while it lasts.

hehe, the life of an admin is discovering what to do, and what to NEVER DO :) btw, we work in the same company, but i'm in the french HQ :D

Hullo, Checked up on you guys,am green with envy! Just concluded Single-Sign-On (SSO) on you guys, was the Lead. I know newcreationxavier doesn't speak French, so he must have googled that statement out...lol...sorry James (had to tell!). See you guys around.

Hullo, Checked up on you guys,am green with envy! Just concluded Single-Sign-On (SSO) on you guys, was the Lead. I know newcreationxavier doesn't speak French, so he must have googled that statement out...lol...sorry James (had to tell!). See you guys around. ?.?.?..Arrghh!You've only got one life; help as many people as you can, and enjoy it while it lasts.