Logo 
Search:

MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

SPK2 Failed.... roll back uptions

  Asked By: Nakul    Date: Mar 31    Category: MOSS    Views: 748

I attempted to install the WSS/MOSS upgrade(s) on my DEV environment. [(2)
servers; 1-MOSS/1-SQL]

Now when I go to any of my web applications I get the following error, "...An
error has occurred on the server.
http://go.microsoft.com/fwlink?LinkID=96177..."

I can log into the CENTRAL ADMIN website with no issue.

Any suggestions on best practice to go forward? Should I be considering rolling
back and starting again? Or, should I be attacking the errors and try to go
forward? While the environment is DEV, it would be nice to get something back up
so people working on stuff and stop calling. Once we get it working again, I can
take a deep breath and re-evaluate the process for doing patches.

Share: 

 

4 Answers Found

 
Answer #1    Answered By: Kacy Bright     Answered On: Mar 31

There's a bunch of troubleshooting you can do.

1) Do both content and application pages fail?

2) If you can get to the application pages do the builds there
match with Central Admin?

3) If you detach the content DBs from the problem content web  apps
and reattach them does that help?

4) If you create a new web application does it work?

5) Any clues in the Event logs?

6) Any clues in the ULS logs?

That's just the stuff  off the top of my head.

 
Answer #2    Answered By: Ivette Burris     Answered On: Mar 31

1) Do both content and application pages fail?
>>>

I can't even get past the login page.

>>
2) If you can get to the application pages do the builds there
match with Central Admin?
>>

It errors  on the login submission.

>>
3) If you detach the content DBs from the problem content web  apps
and reattach them does that help?
>>

I did an unattached but when I went to reattach it errored.

>>
4) If you create a new web application does it work?
>>

I extended an existing web to a new port and it errors the same as the original
websites.

>>
5) Any clues in the Event logs?

6) Any clues in the ULS logs?

>>

There does seem to be some issue  with the TIMER and OFFICE SERVER SHARED
SERVICES. I'll look more at these.....

 
Answer #3    Answered By: Kaitlyn Clark     Answered On: Mar 31

Back up and running.... in a nutshell we believe it was tied to a bad service
account where the password was out of sync. This article was helpful in the
commands for resetting passwords: http://support.microsoft.com/kb/934838

Once we worked through resetting the account information, the wizard would
complete the install. I was able to check the version table in each web
application database to confirm the upgrade had taken place. Also, login was
restored which was the biggest indicator.

 
Answer #4    Answered By: Latanya Nieves     Answered On: Mar 31

I have faced this issue  when I ve upgraded my WSS 3.0 server  with SP1 and
upgrade package for WSS,

when u install  a service pack somehow web  application and Content database
mapping has been lost on that server. We have to upgrade this mapping
forcefully using command line utility STSADM.i had used this command ..

stsadm -o upgrade -inplace -forceupgrade

 
Didn't find what you were looking for? Find more on SPK2 Failed.... roll back uptions Or get search suggestion and latest updates.




Tagged: