November 2nd, 2007 by jmedero
This blog entry is going to first talk about how to get around the error message shown in the title of this blog entry. Next it is going to talk about the DST patch and why you should patch up your SharePoint servers (WSS 2.0/3.0, SPS 2003, and MOSS 2007). If you are interested in the later then skip to the bottom of this post J (but I think you should still read through the rest of the blog entry). You ever get this error when restoring your SharePoint installation? I bet you have and I am hoping this blog will enable you to solve this error when you come across it in a quick manner. Today I was tasked with another upgrade from SharePoint Portal Server 2003 (SPS 2003) to Microsoft Office SharePoint Server 2007 (MOSS 2007). The first thing I do is backup the production environment and restore everything (custom web parts, content DB, IIS metabase, IIS virtual directories, 60 hive). Throughout my days of backing up and restoring SPS 2003 I would say that I can successfully restore my portal about 30% of the time!
Yeah I know that is a very low percentage and with the amount of restores that I have done in the past years, this alone is a great reason why organizations should have what I like to call SharePoint DR fire drills. This drill should consist of restoring a current backup of your production environment into a test environment to ensure the integrity of your backups. I personally think that this should be done on a bi-monthly basis. Trust me a guy who has probably done well over 250 restores just because the backup is successful DOES NOT mean that the restore is going to be. I remember I once had a time where the client had run successful SQL backups but when I went to perform the restore it failed. I quickly checked the event viewer and in the application log was an error which stated that there was a SQL DB consistency error and a new backup had to be taken. So it just goes to show you that the backup and restore process should be planned for and practiced! Anyways I digress from the adventures of backup and restore and will now get to the topic at hand J. I was performing a restore when the restore would fail. I quickly checked the diagnostic log and it stated some gibberish exceptions followed by “The database schema is too old to perform this operation in this SharePoint cluster, please upgrade the database and try again.”So I have run into this issue in the past and usually am frantically looking at the version numbers for the SPS/MOSS/WSS installation within Add-remove programs click on “more information” to find the version number. I then match the test environment version number to the production environment version number.
But what happens if they match but the restore keeps failing?! J This occurs when post service pack hot fixes have been applied. Sometimes unbeknown to the client you may be working with, a hot fix may have been applied automatically through MS updates.In order to find out the real version number you must look to the configuration database of your SharePoint farm. The following steps will demonstrate how I was able to find the version number in the GLOBAL table within the configuration DB to figure out exactly what post service pack hot fixes have been applied.
1. Open up SQL server 2005 management studio
2. Navigate to the configuration DB
3. Expand the configuration DB tables
Navigate to the Globals DB as shown below in SQL server management studio
Th
The schema version shows what version number your virtual server (IIS website) is running at. The version number you see in the image above shows the version that was on the production server. The version that was shown on my test server was:

Once I applied the hot fix above the restore was successful. But man this definitely took me some time to do the research and let's just say I have a few less hairs on my head. While we are talking about DST hot fixes I would like to point to a great blog entry by the man Joel O about all questions you may have with updating your WSS 3.0 and MOSS 2007 servers. The October 9 public update for WSS 3.0 and MOSS 2007 includes a fix for security vulnerability (cross site scripting). The public update also includes the DST patch which will influence your SharePoint environment. Especially the one time timer jobs will be effected such as solution package deployments/updates, backup and restores, feature deployments, and form services InfoPath forms upgrades or deletions. I would recommend taking a look at Joel O's blog entry titled SharePoint FAQ on DST and October 9th Public Update. This will be extremely helpful for organizations wondering what exactly these hot fixes will fix and what it protects them against. My suggestion is to apply the public update ASAP before you begin experiencing the DST issues which affect all aspects of your WSS 3.0 and MOSS 2007 environments.
Cheers!
Jason Medero
Posted in Uncategorized | No Comments »
November 2nd, 2007 by jmedero
This blog entry is going to first talk about how to get around the error message shown in the title of this blog entry. Next it is going to talk about the DST patch and why you should patch up your SharePoint servers (WSS 2.0/3.0, SPS 2003, and MOSS 2007). If you are interested in the later then skip to the bottom of this post J (but I think you should still read through the rest of the blog entry). You ever get this error when restoring your SharePoint installation? I bet you have and I am hoping this blog will enable you to solve this error when you come across it in a quick manner. Today I was tasked with another upgrade from SharePoint Portal Server 2003 (SPS 2003) to Microsoft Office SharePoint Server 2007 (MOSS 2007). The first thing I do is backup the production environment and restore everything (custom web parts, content DB, IIS metabase, IIS virtual directories, 60 hive). Throughout my days of backing up and restoring SPS 2003 I would say that I can successfully restore my portal about 30% of the time!
Yeah I know that is a very low percentage and with the amount of restores that I have done in the past years, this alone is a great reason why organizations should have what I like to call SharePoint DR fire drills. This drill should consist of restoring a current backup of your production environment into a test environment to ensure the integrity of your backups. I personally think that this should be done on a bi-monthly basis. Trust me a guy who has probably done well over 250 restores just because the backup is successful DOES NOT mean that the restore is going to be. I remember I once had a time where the client had run successful SQL backups but when I went to perform the restore it failed. I quickly checked the event viewer and in the application log was an error which stated that there was a SQL DB consistency error and a new backup had to be taken. So it just goes to show you that the backup and restore process should be planned for and practiced! Anyways I digress from the adventures of backup and restore and will now get to the topic at hand J. I was performing a restore when the restore would fail. I quickly checked the diagnostic log and it stated some gibberish exceptions followed by “The database schema is too old to perform this operation in this SharePoint cluster, please upgrade the database and try again.”So I have run into this issue in the past and usually am frantically looking at the version numbers for the SPS/MOSS/WSS installation within Add-remove programs click on “more information” to find the version number. I then match the test environment version number to the production environment version number.
But what happens if they match but the restore keeps failing?! J This occurs when post service pack hot fixes have been applied. Sometimes unbeknown to the client you may be working with, a hot fix may have been applied automatically through MS updates.In order to find out the real version number you must look to the configuration database of your SharePoint farm. The following steps will demonstrate how I was able to find the version number in the GLOBAL table within the configuration DB to figure out exactly what post service pack hot fixes have been applied.
1. Open up SQL server 2005 management studio
2. Navigate to the configuration DB
3. Expand the configuration DB tables
Navigate to the Globals DB as shown below in SQL server management studio
Th
The schema version shows what version number your virtual server (IIS website) is running at. The version number you see in the image above shows the version that was on the production server. The version that was shown on my test server was:

Once I applied the hot fix above the restore was successful. But man this definitely took me some time to do the research and let's just say I have a few less hairs on my head. While we are talking about DST hot fixes I would like to point to a great blog entry by the man Joel O about all questions you may have with updating your WSS 3.0 and MOSS 2007 servers. The October 9 public update for WSS 3.0 and MOSS 2007 includes a fix for security vulnerability (cross site scripting). The public update also includes the DST patch which will influence your SharePoint environment. Especially the one time timer jobs will be effected such as solution package deployments/updates, backup and restores, feature deployments, and form services InfoPath forms upgrades or deletions. I would recommend taking a look at Joel O's blog entry titled SharePoint FAQ on DST and October 9th Public Update. This will be extremely helpful for organizations wondering what exactly these hot fixes will fix and what it protects them against. My suggestion is to apply the public update ASAP before you begin experiencing the DST issues which affect all aspects of your WSS 3.0 and MOSS 2007 environments.
Cheers!
Jason Medero
Posted in Uncategorized | No Comments »
October 30th, 2007 by jmedero
Hey guys and gals,
Just wanted to let everyone know that I will be in Vegas for SharePoint Connections Nov. 4-8. SharePoint connections has a ton of great speakers and a lot of great sessions. I consider SharePoint Connection to be the second best conference of the year of course next to TechEd
! So if you read this and are going to be in town leave a comment on this page and I am sure we can discuss any topics that may be on your mind. I will be accompanied by the entire (well pretty much everyone) B&R SharePoint hit squad and I am sure if I can't answer you question then someone on my team could definitely lend a hand. I mean we consist of some of the best consultants in the US
guys like Bob Fox, Chris Regan, Michael Lotter, Josh Carlisle and some new secret members as well! If you would like to ask a question or just say whats up I will be at the Microsoft SharePoint booth on Tuesday Nov. 6 from 330-415 answering questions and chatting away about all kinds of cool stuff!
Looking forward to seeing some of you loyal SharePointers there!
Cheers,
Jason Medero
Posted in Uncategorized | No Comments »
October 30th, 2007 by jmedero
Hey guys and gals,
Just wanted to let everyone know that I will be in Vegas for SharePoint Connections Nov. 4-8. SharePoint connections has a ton of great speakers and a lot of great sessions. I consider SharePoint Connection to be the second best conference of the year of course next to TechEd
! So if you read this and are going to be in town leave a comment on this page and I am sure we can discuss any topics that may be on your mind. I will be accompanied by the entire (well pretty much everyone) B&R SharePoint hit squad and I am sure if I can't answer you question then someone on my team could definitely lend a hand. I mean we consist of some of the best consultants in the US
guys like Bob Fox, Chris Regan, Michael Lotter, Josh Carlisle and some new secret members as well! If you would like to ask a question or just say whats up I will be at the Microsoft SharePoint booth on Tuesday Nov. 6 from 330-415 answering questions and chatting away about all kinds of cool stuff!
Looking forward to seeing some of you loyal SharePointers there!
Cheers,
Jason Medero
Posted in Uncategorized | No Comments »
October 29th, 2007 by jmedero
Hey guys/girls,
As everyone knows Halo 3 has been out for a decent amount of time and I am sure those late nights on work days are really catching up with people! I don't know about everyone else but I know for sure that I have been playing this game every free moment that I have had. Of course forgetting about the rest of my social life for the past 30 days without even noticing. Anyways for those of you who have been going through this Halo 3 coma phase this ones for you!
http://youtube.com/watch?v=ZOkF0McZKIw
Cheers! 
Posted in Uncategorized | No Comments »
October 29th, 2007 by jmedero
Hey guys/girls,
As everyone knows Halo 3 has been out for a decent amount of time and I am sure those late nights on work days are really catching up with people! I don't know about everyone else but I know for sure that I have been playing this game every free moment that I have had. Of course forgetting about the rest of my social life for the past 30 days without even noticing. Anyways for those of you who have been going through this Halo 3 coma phase this ones for you!
http://youtube.com/watch?v=ZOkF0McZKIw
Cheers! 
Posted in Uncategorized | No Comments »
October 17th, 2007 by jmedero
Recently I was tasked with leading the capacity planning session for quite a large number of users (25K+). The organization was going to be heavily utilizing Forms services. We were in the process of developing and deploying over 800 forms once their current MOSS implementation was launched. So the team and I sat down to discuss how we were going to accommodate the use of form service without performance implications. This was the first time that I have worked with the Form Services feature within MOSS 2007 at such a scale. For those of you who are not familiar with what form services is I will quickly summarize and provide some links:InfoPath Form Services is a feature found within MOSS 2007 Enterprise edition only. In general it allows InfoPath forms to be consumed via the web browser. This has its advantages and disadvantages the major advantage being that users no longer have to have the expensive InfoPath thick client installed on their machine in order to fill out these forms and submit them. MOSS 2007 WFE's will render these forms through a web browser and will allow the user to interact with the form as if they were inside of the InfoPath client. Below are a couple links for anyone who is looking to gain some knowledge on InfoPath Form Services. This blog entry will not go into the intricate details of how Form Services works but more so of what to be aware of when planning your MOSS 2007 architecture.
Introduction to Form Services:
http://office.microsoft.com/en-us/sharepointserver/HA101672841033.aspx
Configuring Form Services within MOSS 2007:
http://technet2.microsoft.com/Office/en-us/library/3728d1fa-c1db-4445-8d00-e26f9015dd951033.mspx?mfr=true
Form Services Development:
http://msdn2.microsoft.com/en-us/library/ms540731.aspx
Now that you have thoroughly read through the links above
lets jump into the topic at hand. As far as MOSS 2007 topologies go there are four main layers:
- Web Front End (WFE)
- Index/Query
- Application
- Database
So the first thing that came to mind is that we would dedicate Forms Server at the application server just like its similiar counterpart Excel Services. I proceeded to do some digging and it quickly became apparent through the documentation and the help of fellow MVP Spence Harbar that you cannot dedicate machines to take on the Forms Services role. The documentation makes you think that application means to take on such roles as excel services, document conversion, etc. the exception to this rule is the form services role. So what does this mean when you are planning to use Form Services very heavily within your MOSS 2007 implementation? Well plan and simple the load will be taken across your Web Front Ends (WFE's). Since the load will be taken on your WFE's it may make sense depending on the complexity of your forms to beef them up a bit more than you normally would for a WFE.
WFE minimum hardware requirements is something like:
- 2GB RAM
- 1 X Dual Core proc @ 2.8GHZ
- 73GB RAID 0
For an organization that is planning on utilizing form services I would suggest hardware requirements of:
- 64 bit OS and MOSS 2007
- 8GB RAM
- 2 X dual core proc @ 2.8GHZ
- 73GB RAID 0
**Note** The amount of WFE's will vary depending on a couple other variables (# of users, % of concurrent users at peak time, high availability needs, etc..)
The purpose of this blog was to make everyone aware that forms services CANNOT run as its own role which I naively presumed. Forms services is a service that once enabled will run on every front end in your farm. You will need to add WFE's if you are experiencing performance issues that have been traced back to the rendering of forms from MOSS 2007 and would like to scale out NOT app servers!
Cheers!
Jason Medero
Posted in Uncategorized | No Comments »
October 17th, 2007 by jmedero
Recently I was tasked with leading the capacity planning session for quite a large number of users (25K+). The organization was going to be heavily utilizing Forms services. We were in the process of developing and deploying over 800 forms once their current MOSS implementation was launched. So the team and I sat down to discuss how we were going to accommodate the use of form service without performance implications. This was the first time that I have worked with the Form Services feature within MOSS 2007 at such a scale. For those of you who are not familiar with what form services is I will quickly summarize and provide some links:InfoPath Form Services is a feature found within MOSS 2007 Enterprise edition only. In general it allows InfoPath forms to be consumed via the web browser. This has its advantages and disadvantages the major advantage being that users no longer have to have the expensive InfoPath thick client installed on their machine in order to fill out these forms and submit them. MOSS 2007 WFE's will render these forms through a web browser and will allow the user to interact with the form as if they were inside of the InfoPath client. Below are a couple links for anyone who is looking to gain some knowledge on InfoPath Form Services. This blog entry will not go into the intricate details of how Form Services works but more so of what to be aware of when planning your MOSS 2007 architecture.
Introduction to Form Services:
http://office.microsoft.com/en-us/sharepointserver/HA101672841033.aspx
Configuring Form Services within MOSS 2007:
http://technet2.microsoft.com/Office/en-us/library/3728d1fa-c1db-4445-8d00-e26f9015dd951033.mspx?mfr=true
Form Services Development:
http://msdn2.microsoft.com/en-us/library/ms540731.aspx
Now that you have thoroughly read through the links above
lets jump into the topic at hand. As far as MOSS 2007 topologies go there are four main layers:
- Web Front End (WFE)
- Index/Query
- Application
- Database
So the first thing that came to mind is that we would dedicate Forms Server at the application server just like its similiar counterpart Excel Services. I proceeded to do some digging and it quickly became apparent through the documentation and the help of fellow MVP Spence Harbar that you cannot dedicate machines to take on the Forms Services role. The documentation makes you think that application means to take on such roles as excel services, document conversion, etc. the exception to this rule is the form services role. So what does this mean when you are planning to use Form Services very heavily within your MOSS 2007 implementation? Well plan and simple the load will be taken across your Web Front Ends (WFE's). Since the load will be taken on your WFE's it may make sense depending on the complexity of your forms to beef them up a bit more than you normally would for a WFE.
WFE minimum hardware requirements is something like:
- 2GB RAM
- 1 X Dual Core proc @ 2.8GHZ
- 73GB RAID 0
For an organization that is planning on utilizing form services I would suggest hardware requirements of:
- 64 bit OS and MOSS 2007
- 8GB RAM
- 2 X dual core proc @ 2.8GHZ
- 73GB RAID 0
**Note** The amount of WFE's will vary depending on a couple other variables (# of users, % of concurrent users at peak time, high availability needs, etc..)
The purpose of this blog was to make everyone aware that forms services CANNOT run as its own role which I naively presumed. Forms services is a service that once enabled will run on every front end in your farm. You will need to add WFE's if you are experiencing performance issues that have been traced back to the rendering of forms from MOSS 2007 and would like to scale out NOT app servers!
Cheers!
Jason Medero
Posted in Uncategorized | No Comments »
October 2nd, 2007 by jmedero
Hey guys!
As of yesterday I was awarded a renewal of my Microsoft MVP for Windows SharePoint Services for 2008!! I feel very honored to receive this award for the second time and I thank everyone for their awesome support. I really enjoy being a part of such a great growing community. A lot has grown in the SharePoint world over the past year and I will due my best to keep that trend going in the right direction
!
Looking forward to March for the MVP Summit and some serious paintballin!!
Heres to another great year!
Cheers!
Posted in Uncategorized | No Comments »
October 2nd, 2007 by jmedero
Hey guys!
As of yesterday I was awarded a renewal of my Microsoft MVP for Windows SharePoint Services for 2008!! I feel very honored to receive this award for the second time and I thank everyone for their awesome support. I really enjoy being a part of such a great growing community. A lot has grown in the SharePoint world over the past year and I will due my best to keep that trend going in the right direction
!
Looking forward to March for the MVP Summit and some serious paintballin!!
Heres to another great year!
Cheers!
Posted in Uncategorized | No Comments »