From: Andyba on
I do have the PSCDiagnostics, and Upgrade logs created immediately after the
patch, but lack the knowledge to interpret them.

What should I look for?

Rgds


"Chris Puckett [MSFT]" wrote:

> I don't know that I would do that. The psconfig utility, which gets run
> after Sharepoint updates, failed to complete for some reason.
>
> I would look at the logs it generates to try and get a better idea of why it
> failed to complete and go from there.
>
> 944267 How to troubleshoot common errors that occur when you run the
> SharePoint Products and Technologies Configuration Wizard on a computer that
> is running Windows SharePoint Services 3.0 or SharePoint Server 2007
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;944267
>
> --
> Chris Puckett
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
> "Andyba" <Andyba(a)discussions.microsoft.com> wrote in message
> news:44699CF0-8F3A-49A5-B53B-FFAD4E3ADC14(a)microsoft.com...
> > Thanks Chris.
> >
> > Still no joy. Have tried psconfig both with and without the -force switch.
> >
> > I get:-
> >
> > Total number of configuration settings run: 1
> > Total number of successful configuration settings: 0
> > Total number of unsuccessful configuration settings: 3
> > Successfully stopped the configuration of SharePoint Products and
> > Technologies.
> >
> > More or less my exact issue is described in
> > http://forums.techarena.in/small-business-server/1342755.htm
> >
> > I've tried KB926062 too
> >
> > Following that thread my next step would be to:
> >
> > - Go to SharePoint 3.0 Central Administration > Application Management >
> > Content Databases
> > - Remove the default database. Remove the content database from Manage
> > content database page for default site.
> > - Then re-add the same content database from command prompt using STSADM
> > command.
> > - Following is the command to add content database.
> >
> > But I'm a bit nervous as others in that thread have indicated problems.
> >
> > So still looking for something definitive before "removing the default
> > database" !!
> >
> > Rgds
> >
> > "Chris Puckett [MSFT]" wrote:
> >
> >> Try the same troubleshooting steps as in:
> >>
> >> http://blogs.technet.com/b/sbs/archive/2009/05/06/companyweb-inaccessible-after-sharepoint-3-0-service-pack-2.aspx
> >>
> >> --
> >> Chris Puckett
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >>
> >>
> >> "Andyba" <Andyba(a)discussions.microsoft.com> wrote in message
> >> news:DE3BAE48-4019-4FD0-9CA1-1ECA80A0C709(a)microsoft.com...
> >> > Sorted, I think? Will find out tonight?
> >> >
> >> >
> >> > "Andyba" wrote:
> >> >
> >> >> Was working yesterday! but did some updates last night:
> >> >>
> >> >> Cumulative Security Update for ActiveX Killbits for Windows Server
> >> >> 2008
> >> >> x64
> >> >> Edition (KB980195)
> >> >> Installation date: ‎14/‎06/‎2010 19:44
> >> >> Installation status: Successful
> >> >>
> >> >> Security Update for Windows Server 2008 x64 Edition (KB980218)
> >> >> Installation date: ‎14/‎06/‎2010 19:44
> >> >> Installation status: Successful
> >> >>
> >> >> Cumulative Security Update for Internet Explorer 8 for Windows Server
> >> >> 2008
> >> >> x64 Edition (KB982381)
> >> >> Installation date: ‎14/‎06/‎2010 19:43
> >> >> Installation status: Successful
> >> >>
> >> >> Microsoft .NET Framework 3.5 SP1, Windows Vista SP2, and Windows
> >> >> Server
> >> >> 2008
> >> >> SP2 Update for x64-based Systems (KB982536)
> >> >> Installation date: ‎14/‎06/‎2010 19:43
> >> >> Installation status: Successful
> >> >>
> >> >> Security Update for Windows Server 2008 x64 Edition (KB979559)
> >> >> Installation date: ‎14/‎06/‎2010 19:42
> >> >> Installation status: Successful
> >> >>
> >> >> Microsoft .NET Framework 3.5 SP1, Windows Vista SP2, and Windows
> >> >> Server
> >> >> 2008
> >> >> SP2 Security Update for x64-based Systems (KB979910)
> >> >> Installation date: ‎14/‎06/‎2010 19:42
> >> >> Installation status: Successful
> >> >>
> >> >> Security Update for Windows SharePoint Services 3.0 x64 (KB983444)
> >> >> Installation date: ‎14/‎06/‎2010 19:42
> >> >> Installation status: Successful
> >> >>
> >> >> Security Update for Windows Server 2008 x64 Edition (KB979482)
> >> >> Installation date: ‎14/‎06/‎2010 19:37
> >> >> Installation status: Successful
> >> >>
> >> >> Security Update for Windows Server 2008 x64 Edition (KB982666)
> >> >> Installation date: ‎14/‎06/‎2010 19:37
> >> >> Installation status: Successful
> >> >>
> >> >> Following a single re-boot last night no internal companyweb this am.
> >> >> Nothing externally on 987 either.
> >> >>
> >> >> Will try a second re-boot this eve, but in the interim where should I
> >> >> start
> >> >> looking?
> >> >>
> >> >> Rgds
> >>
> >> .
> >>
> .
>
From: Cognite on
Your issue could be related to the Windows Update 982666 (yes 666!). See
here:
http://blogs.msdn.com/b/webtopics/archive/2010/06/14/iis-6-applications-may-stop-responding-after-you-install-microsoft-update-kb-982666.aspx

We had the same problem with MOSS/CRM/IIS websites but on Windows Server
2003 with SP2 server.

It does say this should not affect Windows Server 2008 (which it looks like
you are using)...

Hope this helps you get further along...

"Andyba" wrote:

> I do have the PSCDiagnostics, and Upgrade logs created immediately after the
> patch, but lack the knowledge to interpret them.
>
> What should I look for?
>
> Rgds
>
>
> "Chris Puckett [MSFT]" wrote:
>
> > I don't know that I would do that. The psconfig utility, which gets run
> > after Sharepoint updates, failed to complete for some reason.
> >
> > I would look at the logs it generates to try and get a better idea of why it
> > failed to complete and go from there.
> >
> > 944267 How to troubleshoot common errors that occur when you run the
> > SharePoint Products and Technologies Configuration Wizard on a computer that
> > is running Windows SharePoint Services 3.0 or SharePoint Server 2007
> > http://support.microsoft.com/default.aspx?scid=kb;EN-US;944267
> >
> > --
> > Chris Puckett
> >
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> >
> >
> > "Andyba" <Andyba(a)discussions.microsoft.com> wrote in message
> > news:44699CF0-8F3A-49A5-B53B-FFAD4E3ADC14(a)microsoft.com...
> > > Thanks Chris.
> > >
> > > Still no joy. Have tried psconfig both with and without the -force switch.
> > >
> > > I get:-
> > >
> > > Total number of configuration settings run: 1
> > > Total number of successful configuration settings: 0
> > > Total number of unsuccessful configuration settings: 3
> > > Successfully stopped the configuration of SharePoint Products and
> > > Technologies.
> > >
> > > More or less my exact issue is described in
> > > http://forums.techarena.in/small-business-server/1342755.htm
> > >
> > > I've tried KB926062 too
> > >
> > > Following that thread my next step would be to:
> > >
> > > - Go to SharePoint 3.0 Central Administration > Application Management >
> > > Content Databases
> > > - Remove the default database. Remove the content database from Manage
> > > content database page for default site.
> > > - Then re-add the same content database from command prompt using STSADM
> > > command.
> > > - Following is the command to add content database.
> > >
> > > But I'm a bit nervous as others in that thread have indicated problems.
> > >
> > > So still looking for something definitive before "removing the default
> > > database" !!
> > >
> > > Rgds
> > >
> > > "Chris Puckett [MSFT]" wrote:
> > >
> > >> Try the same troubleshooting steps as in:
> > >>
> > >> http://blogs.technet.com/b/sbs/archive/2009/05/06/companyweb-inaccessible-after-sharepoint-3-0-service-pack-2.aspx
> > >>
> > >> --
> > >> Chris Puckett
> > >>
> > >> This posting is provided "AS IS" with no warranties, and confers no
> > >> rights.
> > >>
> > >>
> > >>
> > >> "Andyba" <Andyba(a)discussions.microsoft.com> wrote in message
> > >> news:DE3BAE48-4019-4FD0-9CA1-1ECA80A0C709(a)microsoft.com...
> > >> > Sorted, I think? Will find out tonight?
> > >> >
> > >> >
> > >> > "Andyba" wrote:
> > >> >
> > >> >> Was working yesterday! but did some updates last night:
> > >> >>
> > >> >> Cumulative Security Update for ActiveX Killbits for Windows Server
> > >> >> 2008
> > >> >> x64
> > >> >> Edition (KB980195)
> > >> >> Installation date: ‎14/‎06/‎2010 19:44
> > >> >> Installation status: Successful
> > >> >>
> > >> >> Security Update for Windows Server 2008 x64 Edition (KB980218)
> > >> >> Installation date: ‎14/‎06/‎2010 19:44
> > >> >> Installation status: Successful
> > >> >>
> > >> >> Cumulative Security Update for Internet Explorer 8 for Windows Server
> > >> >> 2008
> > >> >> x64 Edition (KB982381)
> > >> >> Installation date: ‎14/‎06/‎2010 19:43
> > >> >> Installation status: Successful
> > >> >>
> > >> >> Microsoft .NET Framework 3.5 SP1, Windows Vista SP2, and Windows
> > >> >> Server
> > >> >> 2008
> > >> >> SP2 Update for x64-based Systems (KB982536)
> > >> >> Installation date: ‎14/‎06/‎2010 19:43
> > >> >> Installation status: Successful
> > >> >>
> > >> >> Security Update for Windows Server 2008 x64 Edition (KB979559)
> > >> >> Installation date: ‎14/‎06/‎2010 19:42
> > >> >> Installation status: Successful
> > >> >>
> > >> >> Microsoft .NET Framework 3.5 SP1, Windows Vista SP2, and Windows
> > >> >> Server
> > >> >> 2008
> > >> >> SP2 Security Update for x64-based Systems (KB979910)
> > >> >> Installation date: ‎14/‎06/‎2010 19:42
> > >> >> Installation status: Successful
> > >> >>
> > >> >> Security Update for Windows SharePoint Services 3.0 x64 (KB983444)
> > >> >> Installation date: ‎14/‎06/‎2010 19:42
> > >> >> Installation status: Successful
> > >> >>
> > >> >> Security Update for Windows Server 2008 x64 Edition (KB979482)
> > >> >> Installation date: ‎14/‎06/‎2010 19:37
> > >> >> Installation status: Successful
> > >> >>
> > >> >> Security Update for Windows Server 2008 x64 Edition (KB982666)
> > >> >> Installation date: ‎14/‎06/‎2010 19:37
> > >> >> Installation status: Successful
> > >> >>
> > >> >> Following a single re-boot last night no internal companyweb this am.
> > >> >> Nothing externally on 987 either.
> > >> >>
> > >> >> Will try a second re-boot this eve, but in the interim where should I
> > >> >> start
> > >> >> looking?
> > >> >>
> > >> >> Rgds
> > >>
> > >> .
> > >>
> > .
> >
From: Chris Puckett [MSFT] on
1. Search the PSCDiagnostics logs for " ERR " (without quotes). It should
read <space>ERR<space> .

2. Search the upgrade.log for [ERROR] .

What are some of the error strings? Do they match anything in KB 944267?

If you haven't seen the blog post below, he posts an example screenshot that
may help you see what to look for.
http://www.newagedev.net/2010/06/window-sharepoint-service-3-0-cant-load-after-install-kb983444-security-update/

944267 How to troubleshoot common errors that occur when you run the
SharePoint Products and Technologies Configuration Wizard on a computer that
is running Windows SharePoint Services 3.0 or SharePoint Server 2007
http://support.microsoft.com/default.aspx?scid=kb;EN-US;944267

--
Chris Puckett

This posting is provided "AS IS" with no warranties, and confers no rights.



"Andyba" <Andyba(a)discussions.microsoft.com> wrote in message
news:9BC5A6F5-550E-48A0-9EFA-0854C2371C9D(a)microsoft.com...
> I do have the PSCDiagnostics, and Upgrade logs created immediately after
> the
> patch, but lack the knowledge to interpret them.
>
> What should I look for?
>
> Rgds
>
>
> "Chris Puckett [MSFT]" wrote:
>
>> I don't know that I would do that. The psconfig utility, which gets run
>> after Sharepoint updates, failed to complete for some reason.
>>
>> I would look at the logs it generates to try and get a better idea of why
>> it
>> failed to complete and go from there.
>>
>> 944267 How to troubleshoot common errors that occur when you run the
>> SharePoint Products and Technologies Configuration Wizard on a computer
>> that
>> is running Windows SharePoint Services 3.0 or SharePoint Server 2007
>> http://support.microsoft.com/default.aspx?scid=kb;EN-US;944267
>>
>> --
>> Chris Puckett
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>
>>
>> "Andyba" <Andyba(a)discussions.microsoft.com> wrote in message
>> news:44699CF0-8F3A-49A5-B53B-FFAD4E3ADC14(a)microsoft.com...
>> > Thanks Chris.
>> >
>> > Still no joy. Have tried psconfig both with and without the -force
>> > switch.
>> >
>> > I get:-
>> >
>> > Total number of configuration settings run: 1
>> > Total number of successful configuration settings: 0
>> > Total number of unsuccessful configuration settings: 3
>> > Successfully stopped the configuration of SharePoint Products and
>> > Technologies.
>> >
>> > More or less my exact issue is described in
>> > http://forums.techarena.in/small-business-server/1342755.htm
>> >
>> > I've tried KB926062 too
>> >
>> > Following that thread my next step would be to:
>> >
>> > - Go to SharePoint 3.0 Central Administration > Application Management
>> > >
>> > Content Databases
>> > - Remove the default database. Remove the content database from Manage
>> > content database page for default site.
>> > - Then re-add the same content database from command prompt using
>> > STSADM
>> > command.
>> > - Following is the command to add content database.
>> >
>> > But I'm a bit nervous as others in that thread have indicated problems.
>> >
>> > So still looking for something definitive before "removing the default
>> > database" !!
>> >
>> > Rgds
>> >
>> > "Chris Puckett [MSFT]" wrote:
>> >
>> >> Try the same troubleshooting steps as in:
>> >>
>> >> http://blogs.technet.com/b/sbs/archive/2009/05/06/companyweb-inaccessible-after-sharepoint-3-0-service-pack-2.aspx
>> >>
>> >> --
>> >> Chris Puckett
>> >>
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> rights.
>> >>
>> >>
>> >>
>> >> "Andyba" <Andyba(a)discussions.microsoft.com> wrote in message
>> >> news:DE3BAE48-4019-4FD0-9CA1-1ECA80A0C709(a)microsoft.com...
>> >> > Sorted, I think? Will find out tonight?
>> >> >
>> >> >
>> >> > "Andyba" wrote:
>> >> >
>> >> >> Was working yesterday! but did some updates last night:
>> >> >>
>> >> >> Cumulative Security Update for ActiveX Killbits for Windows Server
>> >> >> 2008
>> >> >> x64
>> >> >> Edition (KB980195)
>> >> >> Installation date: ‎14/‎06/‎2010 19:44
>> >> >> Installation status: Successful
>> >> >>
>> >> >> Security Update for Windows Server 2008 x64 Edition (KB980218)
>> >> >> Installation date: ‎14/‎06/‎2010 19:44
>> >> >> Installation status: Successful
>> >> >>
>> >> >> Cumulative Security Update for Internet Explorer 8 for Windows
>> >> >> Server
>> >> >> 2008
>> >> >> x64 Edition (KB982381)
>> >> >> Installation date: ‎14/‎06/‎2010 19:43
>> >> >> Installation status: Successful
>> >> >>
>> >> >> Microsoft .NET Framework 3.5 SP1, Windows Vista SP2, and Windows
>> >> >> Server
>> >> >> 2008
>> >> >> SP2 Update for x64-based Systems (KB982536)
>> >> >> Installation date: ‎14/‎06/‎2010 19:43
>> >> >> Installation status: Successful
>> >> >>
>> >> >> Security Update for Windows Server 2008 x64 Edition (KB979559)
>> >> >> Installation date: ‎14/‎06/‎2010 19:42
>> >> >> Installation status: Successful
>> >> >>
>> >> >> Microsoft .NET Framework 3.5 SP1, Windows Vista SP2, and Windows
>> >> >> Server
>> >> >> 2008
>> >> >> SP2 Security Update for x64-based Systems (KB979910)
>> >> >> Installation date: ‎14/‎06/‎2010 19:42
>> >> >> Installation status: Successful
>> >> >>
>> >> >> Security Update for Windows SharePoint Services 3.0 x64 (KB983444)
>> >> >> Installation date: ‎14/‎06/‎2010 19:42
>> >> >> Installation status: Successful
>> >> >>
>> >> >> Security Update for Windows Server 2008 x64 Edition (KB979482)
>> >> >> Installation date: ‎14/‎06/‎2010 19:37
>> >> >> Installation status: Successful
>> >> >>
>> >> >> Security Update for Windows Server 2008 x64 Edition (KB982666)
>> >> >> Installation date: ‎14/‎06/‎2010 19:37
>> >> >> Installation status: Successful
>> >> >>
>> >> >> Following a single re-boot last night no internal companyweb this
>> >> >> am.
>> >> >> Nothing externally on 987 either.
>> >> >>
>> >> >> Will try a second re-boot this eve, but in the interim where should
>> >> >> I
>> >> >> start
>> >> >> looking?
>> >> >>
>> >> >> Rgds
>> >>
>> >> .
>> >>
>> .
>>
From: Cognite on
Update:
After re-applying Windows Server 2003 SP2, we found that the IIS ASP.NET
mappings had reverted back to use 1.1 framework. You know the dril...open
IIS Damager, click ASP.NET tab for each website and set to 2.0 framework.

Hope this helps you further...

"Cognite" wrote:

> Your issue could be related to the Windows Update 982666 (yes 666!). See
> here:
> http://blogs.msdn.com/b/webtopics/archive/2010/06/14/iis-6-applications-may-stop-responding-after-you-install-microsoft-update-kb-982666.aspx
>
> We had the same problem with MOSS/CRM/IIS websites but on Windows Server
> 2003 with SP2 server.
>
> It does say this should not affect Windows Server 2008 (which it looks like
> you are using)...
>
> Hope this helps you get further along...
>
> "Andyba" wrote:
>
> > I do have the PSCDiagnostics, and Upgrade logs created immediately after the
> > patch, but lack the knowledge to interpret them.
> >
> > What should I look for?
> >
> > Rgds
> >
> >
> > "Chris Puckett [MSFT]" wrote:
> >
> > > I don't know that I would do that. The psconfig utility, which gets run
> > > after Sharepoint updates, failed to complete for some reason.
> > >
> > > I would look at the logs it generates to try and get a better idea of why it
> > > failed to complete and go from there.
> > >
> > > 944267 How to troubleshoot common errors that occur when you run the
> > > SharePoint Products and Technologies Configuration Wizard on a computer that
> > > is running Windows SharePoint Services 3.0 or SharePoint Server 2007
> > > http://support.microsoft.com/default.aspx?scid=kb;EN-US;944267
> > >
> > > --
> > > Chris Puckett
> > >
> > > This posting is provided "AS IS" with no warranties, and confers no rights.
> > >
> > >
> > >
> > > "Andyba" <Andyba(a)discussions.microsoft.com> wrote in message
> > > news:44699CF0-8F3A-49A5-B53B-FFAD4E3ADC14(a)microsoft.com...
> > > > Thanks Chris.
> > > >
> > > > Still no joy. Have tried psconfig both with and without the -force switch.
> > > >
> > > > I get:-
> > > >
> > > > Total number of configuration settings run: 1
> > > > Total number of successful configuration settings: 0
> > > > Total number of unsuccessful configuration settings: 3
> > > > Successfully stopped the configuration of SharePoint Products and
> > > > Technologies.
> > > >
> > > > More or less my exact issue is described in
> > > > http://forums.techarena.in/small-business-server/1342755.htm
> > > >
> > > > I've tried KB926062 too
> > > >
> > > > Following that thread my next step would be to:
> > > >
> > > > - Go to SharePoint 3.0 Central Administration > Application Management >
> > > > Content Databases
> > > > - Remove the default database. Remove the content database from Manage
> > > > content database page for default site.
> > > > - Then re-add the same content database from command prompt using STSADM
> > > > command.
> > > > - Following is the command to add content database.
> > > >
> > > > But I'm a bit nervous as others in that thread have indicated problems.
> > > >
> > > > So still looking for something definitive before "removing the default
> > > > database" !!
> > > >
> > > > Rgds
> > > >
> > > > "Chris Puckett [MSFT]" wrote:
> > > >
> > > >> Try the same troubleshooting steps as in:
> > > >>
> > > >> http://blogs.technet.com/b/sbs/archive/2009/05/06/companyweb-inaccessible-after-sharepoint-3-0-service-pack-2.aspx
> > > >>
> > > >> --
> > > >> Chris Puckett
> > > >>
> > > >> This posting is provided "AS IS" with no warranties, and confers no
> > > >> rights.
> > > >>
> > > >>
> > > >>
> > > >> "Andyba" <Andyba(a)discussions.microsoft.com> wrote in message
> > > >> news:DE3BAE48-4019-4FD0-9CA1-1ECA80A0C709(a)microsoft.com...
> > > >> > Sorted, I think? Will find out tonight?
> > > >> >
> > > >> >
> > > >> > "Andyba" wrote:
> > > >> >
> > > >> >> Was working yesterday! but did some updates last night:
> > > >> >>
> > > >> >> Cumulative Security Update for ActiveX Killbits for Windows Server
> > > >> >> 2008
> > > >> >> x64
> > > >> >> Edition (KB980195)
> > > >> >> Installation date: ‎14/‎06/‎2010 19:44
> > > >> >> Installation status: Successful
> > > >> >>
> > > >> >> Security Update for Windows Server 2008 x64 Edition (KB980218)
> > > >> >> Installation date: ‎14/‎06/‎2010 19:44
> > > >> >> Installation status: Successful
> > > >> >>
> > > >> >> Cumulative Security Update for Internet Explorer 8 for Windows Server
> > > >> >> 2008
> > > >> >> x64 Edition (KB982381)
> > > >> >> Installation date: ‎14/‎06/‎2010 19:43
> > > >> >> Installation status: Successful
> > > >> >>
> > > >> >> Microsoft .NET Framework 3.5 SP1, Windows Vista SP2, and Windows
> > > >> >> Server
> > > >> >> 2008
> > > >> >> SP2 Update for x64-based Systems (KB982536)
> > > >> >> Installation date: ‎14/‎06/‎2010 19:43
> > > >> >> Installation status: Successful
> > > >> >>
> > > >> >> Security Update for Windows Server 2008 x64 Edition (KB979559)
> > > >> >> Installation date: ‎14/‎06/‎2010 19:42
> > > >> >> Installation status: Successful
> > > >> >>
> > > >> >> Microsoft .NET Framework 3.5 SP1, Windows Vista SP2, and Windows
> > > >> >> Server
> > > >> >> 2008
> > > >> >> SP2 Security Update for x64-based Systems (KB979910)
> > > >> >> Installation date: ‎14/‎06/‎2010 19:42
> > > >> >> Installation status: Successful
> > > >> >>
> > > >> >> Security Update for Windows SharePoint Services 3.0 x64 (KB983444)
> > > >> >> Installation date: ‎14/‎06/‎2010 19:42
> > > >> >> Installation status: Successful
> > > >> >>
> > > >> >> Security Update for Windows Server 2008 x64 Edition (KB979482)
> > > >> >> Installation date: ‎14/‎06/‎2010 19:37
> > > >> >> Installation status: Successful
> > > >> >>
> > > >> >> Security Update for Windows Server 2008 x64 Edition (KB982666)
> > > >> >> Installation date: ‎14/‎06/‎2010 19:37
> > > >> >> Installation status: Successful
> > > >> >>
> > > >> >> Following a single re-boot last night no internal companyweb this am.
> > > >> >> Nothing externally on 987 either.
> > > >> >>
> > > >> >> Will try a second re-boot this eve, but in the interim where should I
> > > >> >> start
> > > >> >> looking?
> > > >> >>
> > > >> >> Rgds
> > > >>
> > > >> .
> > > >>
> > > .
> > >
From: Andyba on
Thanks again Chris.

I have listed below what I've found in the two logs. Can find any
similarities in either of your links :(

If I might impose further and ask you to please have a look.

Thanks in advance.

PSCDiagnostics Log

06/15/2010 21:40:29 7 ERR The B2B upgrader timer job
failed.
06/15/2010 21:40:29 7 ERR Task upgrade has failed with a
PostSetupConfigurationTaskException An exception of type
Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException
was thrown. Additional exception information: Failed to upgrade SharePoint
Products and Technologies.
06/15/2010 21:40:29 7 ERR An exception of type
Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException
was thrown. Additional exception information: Failed to upgrade SharePoint
Products and Technologies.
Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException:
Exception of type
'Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException' was thrown.
at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
06/15/2010 21:40:29 7 ERR Task upgrade has failed
06/15/2010 21:40:29 1 ERR Task upgrade has
stopped and failed. Total failed is now 1
06/15/2010 21:40:30 6 ERR Task upgrade SharePoint Products
and Technologies failed, so stopping execution of the engine
06/15/2010 21:40:30 6 ERR Failed to upgrade SharePoint
Products and Technologies.
Failed to upgrade SharePoint Products and Technologies. Further information
regarding this failure can be found at C:\Program Files\Common
Files\Microsoft Shared\Web Server Extensions\12\LOGS\Upgrade.log.
An exception of type
Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException
was thrown. Additional exception information: Failed to upgrade SharePoint
Products and Technologies.
Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException:
Exception of type
'Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException' was thrown.
at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
06/15/2010 21:40:30 6 ERR One or more configuration tasks
has failed or some tasks were not run
06/15/2010 21:40:30 6 ERR One or more configuration tasks
has failed or some tasks were not run


Update Log

[SPManager] [ERROR] [6/14/2010 7:41:55 PM]: Upgrade [SPSearchDatabase
Name=WSS_Search_WIN-EUGSO7LO7PY Parent=SPDatabaseServiceInstance
Name=Microsoft##SSEE] failed.
[SPManager] [ERROR] [6/14/2010 7:41:55 PM]: SPSearch (SharePointFix)
[SPManager] [ERROR] [6/14/2010 7:41:55 PM]:
Server stack trace:
at
Microsoft.SharePoint.AdministrationOperation.Win32.SPAdvApi32.ChangeServiceConfiguration(String
strServiceName, String strAccountName, SecureString sstrPassword,
IdentityType identityType, Boolean bDontRestartService)
at
Microsoft.SharePoint.AdministrationOperation.SPProvisioningAssistant.ProvisionProcessIdentity(String
strUserName, SecureString secStrPassword, IdentityType identityType, Boolean
isAdminProcess, Boolean isWindowsService, String strServiceName, Boolean
dontRestartService)
at
Microsoft.SharePoint.AdministrationOperation.SPAdministrationOperation.DoProvisionProcessIdentity(String
username, String password, Int32 identityType, Boolean isAdminProcess,
Boolean isWindowsService, String serviceName, Boolean delayRestartTimer)
at
System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr
md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext,
Object[]& outArgs)
at
System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage
reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData&
msgData, Int32 type)
at
Microsoft.SharePoint.AdministrationOperation.SPAdministrationOperation.DoProvisionProcessIdentity(String
username, String password, Int32 identityType, Boolean isAdminProcess,
Boolean isWindowsService, String serviceName, Boolean delayRestartTimer)
at
Microsoft.SharePoint.Administration.SPProcessIdentity.ProvisionInternal(SecureString sstrPassword, Boolean isRunningInTimer)
at Microsoft.SharePoint.Administration.SPProcessIdentity.Provision()
at
Microsoft.SharePoint.Administration.SPWindowsServiceInstance.ProvisionCredentials()
at
Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Provision(Boolean start)
at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Provision()
at
Microsoft.SharePoint.Search.Administration.SPSearchServiceInstance.Provision()
at
Microsoft.SharePoint.Upgrade.SPSearchDatabaseSequence.EnableAndProvisionSearchNTService()
at Microsoft.SharePoint.Upgrade.SPSearchDatabaseSequence.PostUpgrade()
at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean
bRecurse)
[SPManager] [DEBUG] [6/14/2010 7:41:55 PM]: Elapsed time upgrading
[SPSearchDatabase Name=WSS_Search_WIN-EUGSO7LO7PY
Parent=SPDatabaseServiceInstance Name=Microsoft##SSEE]: 00:00:21.
[SPManager] [INFO] [6/14/2010 7:41:55 PM]: Resetting the status of
PersistedUpgradableObject: SPSearchDatabase Name=WSS_Search_WIN-EUGSO7LO7PY
Parent=SPDatabaseServiceInstance Name=Microsoft##SSEE to Online.
[SPManager] [ERROR] [6/14/2010 7:41:55 PM]: ReflexiveUpgrade
[SPSearchDatabase Name=WSS_Search_WIN-EUGSO7LO7PY
Parent=SPDatabaseServiceInstance Name=Microsoft##SSEE] failed.
[SPManager] [ERROR] [6/14/2010 7:41:55 PM]: SPSearch (SharePointFix)
[SPManager] [ERROR] [6/14/2010 7:41:55 PM]:
Server stack trace:
at
Microsoft.SharePoint.AdministrationOperation.Win32.SPAdvApi32.ChangeServiceConfiguration(String
strServiceName, String strAccountName, SecureString sstrPassword,
IdentityType identityType, Boolean bDontRestartService)
at
Microsoft.SharePoint.AdministrationOperation.SPProvisioningAssistant.ProvisionProcessIdentity(String
strUserName, SecureString secStrPassword, IdentityType identityType, Boolean
isAdminProcess, Boolean isWindowsService, String strServiceName, Boolean
dontRestartService)
at
Microsoft.SharePoint.AdministrationOperation.SPAdministrationOperation.DoProvisionProcessIdentity(String
username, String password, Int32 identityType, Boolean isAdminProcess,
Boolean isWindowsService, String serviceName, Boolean delayRestartTimer)
at
System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr
md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext,
Object[]& outArgs)
at
System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage
reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData&
msgData, Int32 type)
at
Microsoft.SharePoint.AdministrationOperation.SPAdministrationOperation.DoProvisionProcessIdentity(String
username, String password, Int32 identityType, Boolean isAdminProcess,
Boolean isWindowsService, String serviceName, Boolean delayRestartTimer)
at
Microsoft.SharePoint.Administration.SPProcessIdentity.ProvisionInternal(SecureString sstrPassword, Boolean isRunningInTimer)
at Microsoft.SharePoint.Administration.SPProcessIdentity.Provision()
at
Microsoft.SharePoint.Administration.SPWindowsServiceInstance.ProvisionCredentials()
at
Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Provision(Boolean start)
at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Provision()
at
Microsoft.SharePoint.Search.Administration.SPSearchServiceInstance.Provision()
at
Microsoft.SharePoint.Upgrade.SPSearchDatabaseSequence.EnableAndProvisionSearchNTService()
at Microsoft.SharePoint.Upgrade.SPSearchDatabaseSequence.PostUpgrade()
at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean
bRecurse)
at
Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveUpgrade(Object o,
Boolean bRecurse)
[SPManager] [INFO] [6/14/2010 7:41:55 PM]: Resetting the status of
PersistedUpgradableObject: SPServer Name=XXXXX-SBS Parent=SPFarm
Name=SharePoint_Config_29c26fca-17b8-48c1-9704-b869932abcb6 to Online.
[SPManager] [ERROR] [6/14/2010 7:41:55 PM]: ReflexiveUpgrade [SPServer
Name=XXXXX-SBS Parent=SPFarm
Name=SharePoint_Config_29c26fca-17b8-48c1-9704-b869932abcb6] failed.
[SPManager] [ERROR] [6/14/2010 7:41:55 PM]: SPSearch (SharePointFix)
[SPManager] [ERROR] [6/14/2010 7:41:55 PM]:
Server stack trace:
at
Microsoft.SharePoint.AdministrationOperation.Win32.SPAdvApi32.ChangeServiceConfiguration(String
strServiceName, String strAccountName, SecureString sstrPassword,
IdentityType identityType, Boolean bDontRestartService)
at
Microsoft.SharePoint.AdministrationOperation.SPProvisioningAssistant.ProvisionProcessIdentity(String
strUserName, SecureString secStrPassword, IdentityType identityType, Boolean
isAdminProcess, Boolean isWindowsService, String strServiceName, Boolean
dontRestartService)
at
Microsoft.SharePoint.AdministrationOperation.SPAdministrationOperation.DoProvisionProcessIdentity(String
username, String password, Int32 identityType, Boolean isAdminProcess,
Boolean isWindowsService, String serviceName, Boolean delayRestartTimer)
at
System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr
md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext,
Object[]& outArgs)
at
System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage
reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData&
msgData, Int32 type)
at
Microsoft.SharePoint.AdministrationOperation.SPAdministrationOperation.DoProvisionProcessIdentity(String
username, String password, Int32 identityType, Boolean isAdminProcess,
Boolean isWindowsService, String serviceName, Boolean delayRestartTimer)
at
Microsoft.SharePoint.Administration.SPProcessIdentity.ProvisionInternal(SecureString sstrPassword, Boolean isRunningInTimer)
at Microsoft.SharePoint.Administration.SPProcessIdentity.Provision()
at
Microsoft.SharePoint.Administration.SPWindowsServiceInstance.ProvisionCredentials()
at
Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Provision(Boolean start)
at Microsoft.SharePoint.Administration.SPWindowsServiceInstance.Provision()
at
Microsoft.SharePoint.Search.Administration.SPSearchServiceInstance.Provision()
at
Microsoft.SharePoint.Upgrade.SPSearchDatabaseSequence.EnableAndProvisionSearchNTService()
at Microsoft.SharePoint.Upgrade.SPSearchDatabaseSequence.PostUpgrade()
at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean
bRecurse)
at
Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveUpgrade(Object o,
Boolean bRecurse)
at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean
bRecurse)
at
Microsoft.SharePoint.Administration.SPPersistedUpgradableObject.Upgrade(Boolean recursively)
at Microsoft.SharePoint.Upgrade.SPManager.ReflexiveUpgrade(Object o,
Boolean bRecurse)
[SPManager] [INFO] [6/14/2010 7:41:55 PM]: Resetting the status of
PersistedUpgradableObject: SPFarm
Name=SharePoint_Config_29c26fca-17b8-48c1-9704-b869932abcb6 to Online.
[SPManager] [INFO] [6/14/2010 7:41:55 PM]: Inplace Upgrade session finishes.
root object = SPFarm
Name=SharePoint_Config_29c26fca-17b8-48c1-9704-b869932abcb6, recursive =
True. 3 errors and 0 warnings encountered.
[SPManager] [DEBUG] [6/14/2010 7:41:55 PM]: Removing exclusive upgrade
regkey by setting the mode to none
[SPManager] [INFO] [6/14/2010 7:41:55 PM]: Turning off the administration
service since upgrade has failed. Restart it before resuming upgrade.
[SPManager] [DEBUG] [6/14/2010 7:42:01 PM]: SyncUpgradeTimerJob: Upgrade
timer job failed. Return -1.