I recently made the mistake of assuming a client would run whatever version of SharePoint we were. I provisioned a SharePoint instance for our team to develop on that was not RTM while our client was running RTM. From the moment we started to build up the site on that non RTM machine we were screwed. It was a rookie mistake on my part, and one my team had to pay for. It's also one I'm not on repeating any time soon. For some reason the idea that there were different versions of SharePoint and that they might not all play nice seemed to have eluded me that day.
Needless to say when we took our shinny new content database and tried to move the site to the clients machine we got an error that looked a lot like:
In addition to the fact that we were screwed, this meant that the schemas of our content database (running 220.127.116.1119) was different than that of our clients (running 18.104.22.16818). It's worth noting that just like the error message above says, you CAN restore content databases from earlier versions into newer ones (ie. you can restore an RTM 22.214.171.12418 content database into a Service Packed 126.96.36.19919 version of SharePoint). You just can't go the other way. Here's a quick grid with SharePoint versions from Penny Coventry's blog with updated links.
|MOSS 2007/WSS 3.0 Service Pack 1 (Contains the below)||188.8.131.5219|
|MOSS 2007/WSS 3.0 October 2007 Public Update||184.108.40.20639|
|MOSS 2007/WSS 3.0 August 2007 Hotfix||220.127.116.1136|
|MOSS 2007/WSS 3.0 RTM||18.104.22.16818|
For those of you who dig pictures here's a quick way of telling which version of SharePoint 2007 (MOSS or WSS) you're running.
How to Tell the Version of SharePoint 2007 (MOSS or WSS)
- Navigate to the SharePoint Central Administration.
- Click on Site Actions->Site Settings.
- The version is just below Site Information (below).
Take care and may you avoid the mistakes I've made.