After many long hours working on upgrading our clients intranet from SPS 2003 to MOSS, we completed the rollout over a very long weekend. Ed Buhain, the client and I spent a fair bit of time babysitting the process, tackling last minute gotchas as they came up. One of the final issues we had was after all of the time testing, debugging, prepping, etc we had not run through the upgrade process with the infrastructure update applied. I was fully prepared to do my workarounds in order to get all the...
Man, this issue has been kicking my butt all day. We've been working on a SharePoint 2003 upgrade (testing) and got to the final content database. Life was good up to this point. 110GB of content had upgraded and there were just a few hiccups, mostly related to size. Then, it came. The nasty, evil, dispicable: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. Over and Over... Basically what's happening from what we can tell is SQL Server...
Again, maybe old news but I thought I would post something interesting that happened during a recent upgrade from SPS 2003 to MOSS. SharePoint is very finicky when it comes to database transactions and sizing during the gradual upgrade process. Here are a couple of things to note: 1. Make sure you have enough size - When upgrading a site that had about 150GB in content, we needed about 500GB in space to complete the migration. 2. Make sure you know where your _Pair DB's Are - SharePoint for some...
This may be old news, but we just hit this issue the other day. If you try to upgrade an instance of SharePoint Portal Server 2003 or WSS 2.0 that is running on a named instance of SQL Server called "SharePoint", the gradual upgrade option is greyed out. It turns out that this is because the installer thinks that you are trying to upgrade an instance of MSDE. Changing the instance name to something other than "SharePoint" does the trick. Talk about hardcoding something
I finally got a Virtual Server 2005 VM running with my clients entire intranet SPS 2003 portal running. It took a bit of time to restore all 70GB of content data. What I have now is a 120 GB VM that is a great way to test the upgrade. Here are some lessons learned: 1. VPC 2007 to Virtual Sever 2005 Does not always work as advertised - I started off this project with a baseline Windows 2003 VPC built on my laptop. The trick is that the VPC used specific IDE controller drivers based on the hardware...