RE: Inconsistent Schema Versions

Hi Steven,

I believe that I may have got this sorted out.

Despite windows update telling me that all updates had been installed, when
I looked at the Servers In Farm page on Central ADmin, I noticed that the
versions of the servers in my farm were not the same. I (re?)applied SP1 to
my farm server, and ran the configuration wizard, and I am now able to join
the new server to the farm.

Thanks very much for your assistance on this!!

"Steven Cheng [MSFT]" wrote:

Hi Arduk,

Any progress on this issue?

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
From: stcheng@xxxxxxxxxxxxxxxxxxxx (Steven Cheng [MSFT])
Organization: Microsoft
Date: Thu, 10 Jul 2008 10:19:07 GMT
Subject: RE: Inconsistent Schema Versions

Hi Arduk,

From your description, you're encountering the following error after
installed MOSS web front end and joined an existing farm, correct?

================
The schema version (3.0.150.0) of the database
SharePoint_AdminContent_234cee22-04f6-458b-bcf1-27afb4a207e7 on
DBSERVERNAME
is not consistent with the expected database schema version (3.1.3.0) on
=============

Based on my reseaerch, such error may occur when the SPS admin database has
inconsistent version info. For the new front end server and the existing
farm environment. have you checked whether the operating system's version
and patch and the MOSS system's version and patches status are the same?

Here I've found an blog entry mentioned a problem caused by applied a
hotfix, you can have a look:

#KB934525 Troubleshooting "Cannot start service SPAdmin on computer '.'."
http://blogs.technet.com/wbaer/archive/2007/10/15/kb934525-troubleshooting.a
spx

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


--------------------
From: =?Utf-8?B?YXJkdWs=?= <arduk@xxxxxxxxxxxxx>
Subject: Inconsistent Schema Versions
Date: Wed, 9 Jul 2008 19:35:00 -0700


I am attempting to add a new web front end to my MOSS farm, so that I can
install reporting services on the machine.

I have installed the web front end components, and ran the configuration
wizard to connect it to the farm. All of this seemed to go OK.

However I have received the following error in the log:
The schema version (3.0.150.0) of the database
SharePoint_AdminContent_234cee22-04f6-458b-bcf1-27afb4a207e7 on
DBSERVERNAME
is not consistent with the expected database schema version (3.1.3.0) on
NEWWEBFRONTENDSERVER. Connections to this database from this server have
been blocked to avoid data loss. Upgrade the web front end or the content
database to ensure that these versions match.

I am unable to complete configuration of the web front end server as a
result.

I have applied all updates to both of my sharepoint servers (existing, and
new web front end).

Any ideas on what is causing this error, and how to fix it?

Thanks in advance



.

Relevant Pages

  • WSUS Errors after System state restored
    ... recover sufficiently and the server went off whilst running. ... no avail and in the end just restored system state from the backup. ... Connection to database failed. ... see Help and Support Center at ...
    (microsoft.public.windows.server.sbs)
  • RE: Inconsistent Schema Versions
    ... on the existing server, to try to force it to upgrade to the same version. ... Microsoft MSDN Online Support Lead ... Subject: Inconsistent Schema Versions ... The schema version of the database ...
    (microsoft.public.sharepoint.portalserver.development)
  • RE: Adding Full Text Search to SBS 2003 - Yes I have searched and Read Everything
    ... You receive a "The database this server is using does not support search" ... SQL Enterprise Manager. ...
    (microsoft.public.windows.server.sbs)
  • Re: Event 1000 Windows SharePoint Services 2.0 Error
    ... BTW I do differentiate between the DIYer and the VAR/VAP but you can call into MS support, explain the situation and it will be a free call. ... Volume Shadow Copy for D Drive is enabled. ... At 3 am this morning, my MSSQL$Sharepoint service stopped running and the server restarts by itself, most probably due to an update. ... And this morning when I came to work, I discovered that when I try to access http://companyweb/, I receive the "Cannot connect to the configuration database." ...
    (microsoft.public.windows.server.sbs)
  • RE: EventID1000: #50070:Unable to Connect to Database - WSS 2.0
    ... Microsoft Support Engineer by contacting Microsoft Customer Support ... Subject: EventID1000: #50070:Unable to Connect to Database - WSS 2.0 ... lot work for server that has lots of virtual servers/sites. ...
    (microsoft.public.sharepoint.windowsservices)