I'm having dificulty installing MS SQL Server 2005 EE onto my XP Pro Machine. I did have the VS2005 Beta2, but i think this was fully removed (Tried using Add/Remove Programs, but had to use Windows Install Cleanup in the end).
I've downloaded the executable and whenever i run it i pass the system configuration check 100%. I continue to install using the default options, and the following components install correctly:
- MSXML6
- SQL Setup Support Files
- SQL Native Client
- SQL VSS Writer
However, the SQL server database services does not install, giving the following error message:
TITLE: Microsoft SQL Server 2005 Setup
------------------------------An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name.
------------------------------
BUTTONS:OK
------------------------------
I then remove all installed components using add/remove programs before the next attempt.
Can any of you clever people offer any advice
Edd
Error installing SQL Server 2005 Express
FrankSh
Yes that is correct, what you could do is to have a look at the sql server express install and force the install to use another instance name. This will allow you to test and make sure the install works.
Gregfmorgan
Have a look at the running services on your machine and check to make sure that you do not have any SQL Server services running that have SQLExpress in there name. Also do you have any of the other express products installed, as they install a version of SQL Server express on it's default instance name.
hande
Thanks for the help, but i think this problem is ongoing still.
I can't find any SQL Express Services running at all in the processes section of task manager.
I do have vb.net express 2005 installed, but this failed to install SQL server express, and when i re-insert the vb express and select add optional products => MS SQL Server 2005 Express Edition x86, I get an error message saying " The following component failed to install: MS SQL Server 2005 Express Edition x86" I got the same error message when i first installed vb, which is why i downloaded teh seperate executable.
Could you confirm that I'm right in thinking that a name instance is something to do with you being able to install multiple copies of this service on a machine and have them running simultaneously, they just need a unique instance name to identify them.
Thanks for your help so far
Edd.