RE: sps Recovery ERROR:database schema is too old to perform

Thank you very much for your immediate reply and the info.

Basically I was trying to use both the content and the configuration
database files (mdf files) of WSS on a virtual server "MyWSS" that used to
run on a physical server called "MyServer", on a new physical server
"MyServer2" with the same virtual server name... Of course, the physical
database server needed to be changed as well.

Besides the version conflicts, it sounded like a disaster recovery that is
almost identical to the WSS that comes with Small Business Server, and
actually the resources on that subject helped me as well.

I ended up exploring the Configuration database tables with MsAccess, and
replacing version numbers, server names, IP addresses, modifying the
references in XML property columns e.t.c. directly in the database.
Brutally...

:)

But worked.

I got it up and running except for a few image files... It is a shame that
sharepoint images, templates and WebParts (Yes, they seem to reside in the
database, but it didn't work, i had to re-install them) are still in the file
system...

OH, and by the way, I did compare the database structure of both versions...
The only difference was that : In "Docs" table, a calculated "Extension"
column was added in version 6.0.2.6411

What I did in a little more detail is:
Our system admin upgraded the WSS with the latest and greatest from MS.
I used a new configuration database, extended a new virtual server with the
same name as my poor old blown WSS with a new content database...
I explored my old configuration database in my good ol' friend MsAccess.
I added my new SQL server to the servers table.
I replaced the serverID in the services table to reference the new SQL server.
I replaced my old physical server name to my new server name in the
configuration database.
Then I changed my configuration database to my old (and purified :))
database in Central edministration.
IISreset
Expected it to work huh ? :) not yet...
Removed (without removing the content database) and re-extended my virtual
server.
IISreset.
I got it up and running without the webparts at that point.
Then installed my cabs.
Fully functional, company logo and my "trans.gif" missing

Do not try unless you have to, and if you do so, do it on your own risk

Thanks.


"Darbha" wrote:

> We solved this error with the help of Mr.Jackson who is also one of the
> user's of this community.
> Here are the few steps:
> 1) Write down the software configuration of both production and test servers.
> 2) if wss-sp1 or Hotfix is installed, it will not be displayed in add/remove
> programs.
> so we cannot trace it in add/remove programs.
> 3) Next thing is Start - Programs - MS sql server - enterprise manager -
> expand databases - click on the default content database say(SPS01_Config_db
> or the name which you gave) - click on tables - open GLOBALS table to see all
> rows - in this note down the version no. [This version no. must be the sam
> on both production and test servers]
> 4) Next goto: c:\Programfiles\common files\microsoft shared\webserver
> extensions\
> 60\bin\ and right click - properties - version tab on following files
> stsadm.exe, onetutil.dll, stswel.dll and note down the version of each file
> [this should be same on both production and test server]
> 5) Next goto c:\program files\sharepoint portal serverbin\ and right click -
> properties -version tab on MSSRCH.dll (This should also be the same on both
> production and Test Servers)
> 6) Next open sharepoint url on production server - site settings - General
> Settings -
> Go to SharePoint Portal Server central administration - Portal Site and
> Virtual Server Configuration-Configure virtual server settings from the
> Virtual Server List page.
> Note down the version next to default virtual server or the one which you
> created.
> (This should also match on both Production server and Test Server)
> 7)For Me
> Production Server(GLOBALS TABLE)Version is: 6.0.2.6411
> Test Server (GLOBALS TABLE) Version is: 6.0.2.5530
> 8) So we need to apply Wss-SP1+ Following HOTFIX on Test Server (ie) on the
> restoration computer.
> 9) LINKS TO GET THIS HOTFIX
> http://www.microsoft.com/technet/security/bulletin/ms05-006.mspx
> download this"Download the update (KB887981) "and install after installing
> WSS-SP1
> Helpful Links to this:
> KB Article: - 888839, 887981, 875358, 824721
> URL:- www.kbalertz.com/kb_888839.aspx
> URL:- http://support.microsoft.com/default.aspx?scid=kb;en-us;824721
> URL:- http://support.microsoft.com/default.aspx?scid=kb;en-us;887981
> URL:- http://support.microsoft.com/default.aspx?scid=kb;en-us;875358
> HOT FIX URL:- http://www.microsoft.com/technet/security/bulletin/ms05-006.mspx
>
> MOST IMPORTANT: - URL:- http://support.microsoft.com/kb/887981
> Click on IT-Professionals  Download the update (KB887981) for HOTFIX
> 10) After this you need to restart the system
> 11) Restore the backup. Success.
> 12) Now see the versions everything matches perfectly.
> 13) Note If page is not dispalyed or DNS error occurs or cannot complete this
> action read the following:
> KB Article: - 834546, 841216, 871149
> URL:- www.kbalertz.com/kb_834546.aspx
> URL:- http://support.microsoft.com/?kbid=834546
> URL:- http://support.microsoft.com/?kbid=841216
>
> and Login as a User Not as an Administrator
> and do the following: Start - Run - cmd-
> C:\program files\common files\microsoft shared\webserver extensions\60\bin\>
> stsadm -o Upgrade -forceupgrade.
> This will take few minutes. RESTART THE SYSTEM.
> After successful upgradation. Open the sharepoint Site.Success.
> 14) Do ask me, for any more information. I will help
> 15) I Really had a very hard time solving this... SO I WISH Others donot
> go through this. Give me your MAIL-ID I will forward the document.
>
> "Duray AKAR" wrote:
>
> > I am having a similar issue.
> >
> > My old WSS server is burned... The mdf files are recovered from the HDD. It
> > did not have SP1 installed...
> >
> > I am trying to use the content database on a new WSS server WITH SP1...
> >
> > How can I do this ?
> >
> > Thanks
> >
> > "Darbha" wrote:
> >
> > > The database schema is too old to perform this operation in this sharepoint
> > > cluster, please upgrade the database and try again.
> > >
> > > I have gone through the KB article 88839.
> > > our file version for sps is 11.05704.0
> > >
> > > How to solve this problem?
> > > we are unable to restore the backup of sps
> > >
> > > Any Ideas! Please Help
.

Relevant Pages

  • Re: major security concern - any sql user with minimal permission can see code for all stored procs
    ... this you may well enter the realm of an unsupported configuration and that's ... > things - and hence has enterprise manager - then this approach won't work. ... > If you just want to lock down a database, then I'd try my approace - lock ... >>> who needed to execute an SP on my server at his location. ...
    (microsoft.public.sqlserver.security)
  • Create SharePoint Portal failed.
    ... One mentioned ensuring that SQL Server uses a case ... 13:55:40 Service database server is 'USDC-JOHRIV'. ... Update dbo.propertylist set DisplayName = N'Last name' ...
    (microsoft.public.sharepoint.portalserver)
  • Re: Issues with Share Point Services after removing and restoring companyweb
    ... 1.Please check the server configuration at ... click set configuration database server,in the database server textbox,it ... message when you access your Windows SharePoint Services Web site ...
    (microsoft.public.windows.server.sbs)
  • Re: ADO Connection Timeout
    ... to the central server, but you are willing to live with periods where it ... i.e. a local database or even a text file. ... to function until the connection can be restored to the server. ...
    (microsoft.public.data.ado)
  • RE: WSS install locked into MSDE DB - Can not install for SQL Serv
    ... For the MASTER database ... Althought we change the Configuration Application pool several times ... interface BUT they appear to be MSDE databases and not SQL Server databases. ...
    (microsoft.public.sharepoint.windowsservices)