OK passporter (and all you others waiting with baited breath), you ready? First of all, we got the same error message you did when we tried installing the sample db. We were trying to install it alongside our production installation so we could use it for training purposes. We fiddled with it a bit and then called Microsoft support (thank God for Premier support). The answer is (from Microsoft themselves) that the error message is a false error.
There is a problem (obviously!) but it's not that you don't necessarily have SP3 installed. Apparently this message will appear if the sampcfg.exe utility can't find the (local) database for any number of reasons. Named database instances being one of them. In our case it's probably caused by the fact that we have SQL running in a cluster for high availability.
The recommendation: install the sample db on a separate single machine configuration. Oh, the part that was conveniently left out of this recommendation was that we'd be starting from scratch on this installation.
Overall, I have to say that I agree with the recommendation. Why compromise your production installation by installing/running a training db on the same install? If the sample db is on a separate machine we can rework it at any time without worrying about interrupting our production instance.
The big question: will we have the same error when we try it on a single server install? Stay tuned...
You're trying to do a single server install, aren't you? Are you running your SQL server as a named instance?
Earl
Earl,
I did. I have installed Project Server 2003 for around 10 clients, in
different configurations and environments. I am doing a single server
installation for some personal development work, and needed some sample data.
I read the SAMPLEDB.HTM first, made sure I met all the requirements, not on
a DC, etc. So I am stuck under "Using the Sample Database Configuration
Wizard" between 1 and 2. I will be curious to here your results.
