MSDE instance servername$sharepoint removed manually unable to uninstall Sharepoint from SBS

Hello,
Client has uninstalled the MSDE instance of SharePoint now i can not remove the SharePoint services from add remove panel it generates log
=== Verbose logging started: 1/25/2008  1:58:39  Build type: SHIP UNICODE 3.01.4000.4042  Calling process: C:\Program Files\Microsoft Integration\Windows Small Business Server 2003\SETUP.EXE ===
MSI (c) (A4:10) [01:58:39:828]: Resetting cached policy values
MSI (c) (A4:10) [01:58:39:828]: Machine policy value 'Debug' is 0
MSI (c) (A4:10) [01:58:39:828]: ******* RunEngine:
           ******* Product: {91140409-7000-11D3-8CFE-0150048383C9}
           ******* Action:
           ******* CommandLine: **********
MSI (c) (A4:10) [01:58:39:828]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (A4:10) [01:58:42:828]: Failed to grab execution mutex. System error 258.
MSI (c) (A4:10) [01:58:42:828]: Cloaking enabled.
MSI (c) (A4:10) [01:58:42:828]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (A4:10) [01:58:42:828]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (c) (A4:10) [01:58:42:843]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (c) (A4:10) [01:58:42:843]: MainEngineThread is returning 1618
=== Verbose logging stopped: 1/25/2008  1:58:42 ===

=== Verbose logging started: 1/25/2008  2:15:51  Build type: SHIP UNICODE 3.01.4000.4042  Calling process: C:\Program Files\Microsoft Integration\Windows Small Business Server 2003\setup.exe ===
MSI (c) (1C:CC) [02:15:51:000]: Resetting cached policy values
MSI (c) (1C:CC) [02:15:51:000]: Machine policy value 'Debug' is 0
MSI (c) (1C:CC) [02:15:51:000]: ******* RunEngine:
           ******* Product: {91140409-7000-11D3-8CFE-0150048383C9}
           ******* Action:
           ******* CommandLine: **********
MSI (c) (1C:CC) [02:15:51:000]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (1C:CC) [02:15:54:000]: Failed to grab execution mutex. System error 258.
MSI (c) (1C:CC) [02:15:54:031]: Cloaking enabled.
MSI (c) (1C:CC) [02:15:54:031]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (1C:CC) [02:15:54:031]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (c) (1C:CC) [02:15:54:031]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (c) (1C:CC) [02:15:54:031]: MainEngineThread is returning 1618
=== Verbose logging stopped: 1/25/2008  2:15:54 ===

=== Verbose logging started: 1/25/2008  2:56:21  Build type: SHIP UNICODE 3.01.4000.4042  Calling process: C:\Program Files\Microsoft Integration\Windows Small Business Server 2003\setup.exe ===
MSI (c) (E0:7C) [02:56:21:562]: Resetting cached policy values
MSI (c) (E0:7C) [02:56:21:562]: Machine policy value 'Debug' is 0
MSI (c) (E0:7C) [02:56:21:562]: ******* RunEngine:
           ******* Product: {91140409-7000-11D3-8CFE-0150048383C9}
           ******* Action:
           ******* CommandLine: **********
MSI (c) (E0:7C) [02:56:21:562]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (E0:7C) [02:56:24:562]: Failed to grab execution mutex. System error 258.
MSI (c) (E0:7C) [02:56:24:562]: Cloaking enabled.
MSI (c) (E0:7C) [02:56:24:562]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (E0:7C) [02:56:24:562]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (c) (E0:7C) [02:56:24:578]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (c) (E0:7C) [02:56:24:578]: MainEngineThread is returning 1618
=== Verbose logging stopped: 1/25/2008  2:56:24 ===
I also followed http://support.microsoft.com/kb/830326 (unable to get any entry in registry)
Please advice
harishshrivastavaAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Olaf De CeusterCommented:
Have you tried this?
http://support.microsoft.com/kb/829114
Olaf
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Actually Olaf... you're a digit off...  :-)

http://support.microsoft.com/kb/829113 is the correct KB article to follow in this instance.

Jeff
TechSoEasy
0
Olaf De CeusterCommented:
Sorry Jeff, I picked the wrong one.
Olaf
0
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Actually, I reread the question and see that there may be a bit more to this...

"I also followed http://support.microsoft.com/kb/830326 (unable to get any entry in registry)"

First you should realize that article is regarding SharePoint Portal Server which is not Windows SharePoint Services.

Then its important to understand the error messages which are showing up:

Error 1618 is: "Another installation is already in progress.  Complete that installation before proceeding with this install."  
Error 258 is "The wait operation timed out."

This failure happened because another Windows Installer package may be installed in the background, and only one Windows Installer-based setup can be running at a time.

Make sure that you clear out ALL temp files in the Administrator's directory:
C:\Documents and Settings\Administrator\Local Settings\Temp\

Then reboot the server before trying to follow KB829113.

Jeff
TechSoEasy


0
harishshrivastavaAuthor Commented:
I was stuck up with multiple issues.
The credentials which I was using was not of built-in administrator it was generated and renamed as an administrator, setup.sdb was modified so I was not able to catch the issue immediately.
Thanks for help.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SBS

From novice to tech pro — start learning today.