When I install the DA Toolset, it will show this error when installing SQL Server 2005 "An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name. "
More specifically, during the configuration of the SQL Server Database Services components.
I am aware of the Dragon Age Wiki, and maybe it says something about this; the remedy is probably bonehead stuff, but if someone could tell me how to change the instance name or show me a link to a fix, I would be most grateful!!!
Help with the Dragon Age Toolset...
Débuté par
christophe333
, déc. 05 2009 02:55
Retour en haut
#2
Posté 05 décembre 2009 - 02:58
Taleroth
-
- Members
- 9 136 messages
You can probably find something in the toolset forum.
#3
Guest_Aislin Bow Maiden_*
Posté 05 décembre 2009 - 03:04
Guest_Aislin Bow Maiden_*
Guest_Aislin Bow Maiden_*
-
- Guests
Ok, I tried doing a little research and putting in a few links for you to look through which will hopefully fix the issue your encountering.
This link below is directions on how to do an install for the toolset. The page gives information if your using Steam or if you have a directory path over 58 characters in length.
social.bioware.com/wiki/datoolset/index.php/Installing_the_toolset
This link is for troubleshooting
social.bioware.com/wiki/datoolset/index.php/Installation_troubleshooting
This link below is directions on how to do an install for the toolset. The page gives information if your using Steam or if you have a directory path over 58 characters in length.
social.bioware.com/wiki/datoolset/index.php/Installing_the_toolset
This link is for troubleshooting
social.bioware.com/wiki/datoolset/index.php/Installation_troubleshooting
Modifié par Aislin Bow Maiden, 05 décembre 2009 - 03:09 .
#4
Posté 05 décembre 2009 - 03:09
Georg Zoeller
-
- Members
- 188 messages
The toolset forum would be the way to go.
However, from personal fights with SQLServer 2005, I remember the solution to this one, and it ain't pretty.
Basically Microsoft's SQL server setup permanently hoses itself if there is a problem during installation that leaves the instance name registered.
Here is how to clean that up. You will need to do that before you can successfully try to install again.
http://blogs.msdn.co.../08/501885.aspx
However, from personal fights with SQLServer 2005, I remember the solution to this one, and it ain't pretty.
Basically Microsoft's SQL server setup permanently hoses itself if there is a problem during installation that leaves the instance name registered.
Here is how to clean that up. You will need to do that before you can successfully try to install again.
http://blogs.msdn.co.../08/501885.aspx
#5
Posté 05 décembre 2009 - 03:34
christophe333
-
- Members
- 4 messages
That fixed it, the directory path was too long and the registry values were messing with the instance name, thanks!
