RE: [OzMOSS] SharePoint_Config Problem

2008-02-20 Thread Craig Stevens
Also reinstalling any templates (that stumped me for a bit, I thought I
had corrupted the database)

 

Cheers

Craig

 



From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Daniel Brown
Sent: Thursday, 21 February 2008 11:53 AM
To: listserver@ozMOSS.com
Subject: RE: [OzMOSS] SharePoint_Config Problem

 

Thanks Kristen,

 

Ill add that to the list as we have done some modifications.

 

Hostname, IP, actual servers are still staying exactly the same :-)

 

Thanks again,

 

Daniel

 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Hodges, Kristen
Sent: Thursday, 21 February 2008 11:16 AM
To: listserver@ozMOSS.com
Subject: RE: [OzMOSS] SharePoint_Config Problem

 

Having done it many times (while testing our 2003  2007 upgrade and in
moving between servers during deployment), have never had any major
probs.  Always found it to be a simple process - assuming the hostname
doesn't change.  When moving to a different hostname we had a few
hiccups but nothing too complicated.  The only thing in that list of
tasks I can see that immediately jumps out as being missing is if you
have made any changes to file system images, layouts, aspx, css etc
don't forget about them.

 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Daniel Brown
Sent: Thursday, 21 February 2008 11:38 AM
To: listserver@ozMOSS.com
Subject: [OzMOSS] SharePoint_Config Problem

 

Hi all,

 

I've recently come across a SharePoint installation which appears to
have stuffed a bit of a botched Service Pack 1 installation.

 

When running SPSReport everything appears fine, however, this error does
appear:

 

The specified SPConfigurationDatabase Name=SharePoint_Config
Parent=SPDatabas

eServiceInstance has been upgraded to a newer version of SharePoint.
Please upgr

ade this SharePoint application server before attempting to access this
object.

 

No backup of the database  is available (grr!)

 

Sounds serious and times are not running at all.

 

My plan is to just blow away the configuration database and reattach the
content databases then reinstall the WSS  MOSS service packs.

 

However never actually performing this action before, I'm after some
information about the process of recreating the configuration database
and reattaching the content databases.

 

My understanding of this processes is

 

* Backup everything (databases and images of web  application
servers)

* Remove/Delete existing configuration database

* Run the SharePoint technology wizard, creating a new farm  CA
site

* Create a new web application (same settings as previous site,
i.e. host header, port, etc)

* Delete the newly created content database

* Reattach the original content database.

* Everything should work with the new databases as they did with
the old (however, no more errors)

 

Does anyone have any links to any white papers or sites, which outlines
the process of attaching a existing content database? Or if someone has
gone though this previously and has any advise, it is most welcome! Or
is there any gotcha's with it?

 

Thanks,

 

 

Daniel Brown

Blog: http://www.danielbrown.id.au http://www.danielbrown.id.au/ 

Mobile: 0419-804-099

 

 

 

---
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 

---
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



RE: [OzMOSS] SharePoint_Config Problem

2008-02-20 Thread Daniel Brown
Lucky! As there are custom templates and web parts involved too.

 

Thanks for the tip!

 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Craig Stevens
Sent: Thursday, 21 February 2008 11:52 AM
To: listserver@ozMOSS.com
Subject: RE: [OzMOSS] SharePoint_Config Problem

 

Also reinstalling any templates (that stumped me for a bit, I thought I had
corrupted the database)

 

Cheers

Craig

 

  _  

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Daniel Brown
Sent: Thursday, 21 February 2008 11:53 AM
To: listserver@ozMOSS.com
Subject: RE: [OzMOSS] SharePoint_Config Problem

 

Thanks Kristen,

 

Ill add that to the list as we have done some modifications.

 

Hostname, IP, actual servers are still staying exactly the same J

 

Thanks again,

 

Daniel

 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Hodges, Kristen
Sent: Thursday, 21 February 2008 11:16 AM
To: listserver@ozMOSS.com
Subject: RE: [OzMOSS] SharePoint_Config Problem

 

Having done it many times (while testing our 2003  2007 upgrade and in
moving between servers during deployment), have never had any major probs.
Always found it to be a simple process - assuming the hostname doesn't
change.  When moving to a different hostname we had a few hiccups but
nothing too complicated.  The only thing in that list of tasks I can see
that immediately jumps out as being missing is if you have made any changes
to file system images, layouts, aspx, css etc don't forget about them.

 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Daniel Brown
Sent: Thursday, 21 February 2008 11:38 AM
To: listserver@ozMOSS.com
Subject: [OzMOSS] SharePoint_Config Problem

 

Hi all,

 

I've recently come across a SharePoint installation which appears to have
stuffed a bit of a botched Service Pack 1 installation.

 

When running SPSReport everything appears fine, however, this error does
appear:

 

The specified SPConfigurationDatabase Name=SharePoint_Config
Parent=SPDatabas

eServiceInstance has been upgraded to a newer version of SharePoint. Please
upgr

ade this SharePoint application server before attempting to access this
object.

 

No backup of the database  is available (grr!)

 

Sounds serious and times are not running at all.

 

My plan is to just blow away the configuration database and reattach the
content databases then reinstall the WSS  MOSS service packs.

 

However never actually performing this action before, I'm after some
information about the process of recreating the configuration database and
reattaching the content databases.

 

My understanding of this processes is

 

. Backup everything (databases and images of web  application
servers)

. Remove/Delete existing configuration database

. Run the SharePoint technology wizard, creating a new farm  CA
site

. Create a new web application (same settings as previous site, i.e.
host header, port, etc)

. Delete the newly created content database

. Reattach the original content database.

. Everything should work with the new databases as they did with the
old (however, no more errors)

 

Does anyone have any links to any white papers or sites, which outlines the
process of attaching a existing content database? Or if someone has gone
though this previously and has any advise, it is most welcome! Or is there
any gotcha's with it?

 

Thanks,

 

 

Daniel Brown

Blog: http://www.danielbrown.id.au http://www.danielbrown.id.au/ 

Mobile: 0419-804-099

 

 

 

---
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 

---
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 




--- 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