I had an SP1 install die on me.

The cause was my fault, I used my personal domain account for the SharePoint 
Search Service (BAD idea), and a few days before the SP1 install my password 
reset and I changed it, so the service was still making use of my old Password, 
I didn't notice this and should have updated the credentials used before 
running SP1.

When the upgrade tried to start-up the SharePoint Search Service it errored due 
to wrong credentials, so the SP1 upgrade bombed out.

I wasted a few more hours trying to resolve the issue with no luck, in the end 
I gave up and completely uninstalled and re-installed MOSS and restored my 
sites to get my development environment back up again.

________________________________
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Daniel Brown [EMAIL 
PROTECTED]
Sent: Saturday, 2 February 2008 9:28 AM
To: [email protected]
Subject: RE: [OzMOSS] Sharepoint SP1 installation failure

Just a quick note on my dealings with SP1.

Clean installs for me, it’s always just gone on with no problem. If the site 
has anything in it bar a default team site or another standard template.. wham, 
a magnitude of errors.

I’m 0 for 2 attempts to install it on a instance with any substance due to all 
these kind of “funky” and obscure errors. Such as that the process that is 
running inside of STDADM is preventing the current one. Try running this one 
again during the running of the config wizard???

However, last time I did get to step 9 or 9 before it bombed out on be.

Hopefully 3rd time is a charm!

Just a FYI thing / mini rant about SP1 :P

Daniel Brown
Blog: http://www.danielbrown.id.au<http://www.danielbrown.id.au/>
Mobile: 0419-804-099

Adelaide SharePoint User group
http://www.sharepointusers.org.au/Adelaide


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian H. Madsen
Sent: Saturday, 2 February 2008 12:59 AM
To: [email protected]
Subject: [OzMOSS] Sharepoint SP1 installation failure

Hey Guys,

I’m hoping somebody here can shed some light on a problem i’m facing.

I have a virtual environment (my development environment) which is a 
self-contained domain/sql/sharepoint server + development tools – and i’m 
trying to install Sharepoint SP1.

I install WSS 3.0 SP1, close the configuration manager, run the Sharepoint SP1 
installation and then the configuration manager (as has been advices all over 
the interweb). Both installs just fine. But, the configuration manager dies 
just after i’ve been informed that i have to run the update on all farm servers 
etc. I click “OK” and then BANG – it fails.

The error is an IdentityNotMapped exception. I cannot, for the life of me get 
this resolved. After this, naturally WSS and Sharepoint is dead. Cannot roll it 
back so i have to bring up one of my virtual image backups (yes, virtulisation 
does have its uses).

Does anybody have any ideas as to what is causing this? I’ve checked the 
credentials for the SQL Server, the service accounts and the application 
pools..everything is honky dorry.

I’ve tried to install this update 8-9 times so far – all have failed at 
approximately the same place each time.

Cheers

[cid:[email protected]]

------------------------------------------------------------------- OzMOSS.com 
- to unsubscribe from this list, send a message back to the list with 
'unsubscribe' as the subject.
Powered by mailenable.com - List managed by www.readify.net



------------------------------------------------------------------- OzMOSS.com 
- to unsubscribe from this list, send a message back to the list with 
'unsubscribe' as the subject.

Powered by mailenable.com - List managed by www.readify.net

<<inline: image001.jpg>>

Reply via email to