After 2005 install, can't add sample databases - help

[thamms]

Hi,

I installed 2005 on a server + SP2. Everything went fine, however I realized after the fact that I DO want the sample "AdventureWorks" OLTP and OLAP databases and sample code.

So, I put Disk 1 back in, and run the installer, selecting:

Sample Databases:
AdventureWorks Sample OLTP
AdventureWorksDW Sample Data Warehouse
AdventureWorks Sample OLAP
Sample Code and Applications

However, when I click "Next", I can't proceed. Here is the error message I'm receiving:

Name: Microsoft SQL Server 2005 Tools
Reason: Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.

Build version check:
Your upgrade is blocked because the existing component is a later version than the version you are trying to upgrade to. To modify an existing SQL Server component, go to Add or Remove Programs in Control Panel, select the component you would like to modify, and then click Change/Remove.

Need help!

Thanks

 

[onpnt]

You don't have SQL Server 2000, MSDE or Express installed also do you? Possibly selecting that instance by mistake?

Also if you check BOL there is a set procedure to installing the samples after the fact which is not from the CD

To complete the installation of the samples, after Setup, perform one of the following steps:


From the Start menu, click All Programs, click Microsoft SQL Server 2005, click Documentation and Tutorials, click Samples, and then click Microsoft SQL Server 2005 Samples. 


Alternatively, using Windows Explorer, navigate to n:\Program Files\Microsoft SQL Server\90\Tools\Samples\ and double-click SqlServerSamples.msi to launch the installer.

[sub]____________ signature below ______________
I am Tedward Keyboardhands!!!
You are a amateur developer until you realize all your code sucks.
Jeff Atwood[/sub]

 

[thamms]

I tried to add using Add/Remove programs (I found information on how to do this from Microsoft), but even that did not work as it could not find a dll file it needed from a disk that we do not have. (That was not part of the directions from Microsoft)