SQL Server 2005 Standard edition install fails; An instance with the same name.../
-
Wednesday, January 18, 2006 8:07 AM
Good Morning
I am trying to install SQL Server 2005 onto Windows Server 2003 Small Business Edition. Previously SQL Server 2000 from the SBE disk was installed, automatic updates are enabled.
I have selected the default instance and everything I try results in the error:
An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name.
Log file says;
--------------------------------------------------------------------------------
Machine : ISAINTERNET
Product : Microsoft SQL Server 2005
Product Version : 9.00.1399.06
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_ISAINTERNET_SQL.log
Last Action : DetectInstanceClash
Error String : An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name.
Error Number : 28086
--------------------------------------------------------------------------------Ian Smith
All Replies
-
Wednesday, January 18, 2006 3:51 PMOwnerIn the setup GUI you're prompted to provide an instance name. The default setting is "Default Instance" - be sure to select "Names Instance" and provide a unique instance name.
-
Thursday, January 19, 2006 6:58 AM
Good morning,
Thank you for your suggestion
I don't think that I explained myself clearly enough, I have uninstalled SQL Server 2000 (and rebooted) so there should not be any instance of SQL Server on the computer.
I am not new to either computing or SQL server and I am quite clear in my mind that I should not need to install a named instance, indeed part of the functionality of installing named instances is that the install will leave other instances alone, in my case the non existent instance.
I take this installer message seriously, either SQL Server installer is wrong and there is no instance (highly unlikely) or that somewhere around there are still bits of SQL Server 2000. Now it may be that the bits of SQL Server 2000 that are left are of no consquence, but if I don't know what they are then I can not know now important they are.
I would rather format the disk and re-install Windows Sever and then install SQL Server 2005 as the default instance than have a named instance when I should not need one. This would mean bye bye the weekend and all the files that I need and haven't backed up but thought that I had! I know this sounds extreme, but it does avoid creating possible problems in the future.
Bye
Ian Smith
-
Thursday, January 19, 2006 4:19 PMOwner
Ian,
First, I don't understand your reasons for not wanting to install a named instance. There is absolutely no functional difference between a named instance and the default instance.
With that said, I now understand what you're saying. In order to trouble shoot this further, you'll need to look at the contents of the following log file:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_ISAINTERNET_SQL.log
Search for "Value 3" (This is a Windows Installer error code marker). Near the location of "Value 3" you should see some additional information about the error. If you can't figure it out from that please post the text around "Value 3" and I'll have a look at it. Please don't post the entire log file as it's probably pretty big.
Finally, one thing to remember is some software includes MSDE under the covers. Is it possible that something you installed in turn installed MSDE as a default instance? You wouldn't see this in Add Remove Programs. It would only show up in the process list.
Dan
-
Friday, January 20, 2006 7:15 AM
Good Morning
Once again thank you for your thoughts.
The suggestion that MSDE might be the culprit is very likely to be true, we are pretty sure that nothing should have installed it, but we did install Visual Web Developer a while back and most defintely did not choose to install MSDE, however windows Automatic Updates has tried and failed on numerous occasions to install updates to MSDE, I think it fails because MSDE is not installed but a fragment of it was.
This is a reasonable reason for why I have to install a named instance, I have done this as we need to carry on working, and have not come across any problems.
Just to clarifiy, my reluctance to install a named instance is based on the idea that I like everything to be perfectly set up, I don't like old or unexpected bits of programs hanging around. In practice they seem to come back and bite you a few months later in totally unexpected ways.
Finally thanks once more for your help.
Bye
Ian Smith
Out of interest here is the bit of the installer log
<Func Name='LaunchFunction'>
Function=DetectInstanceClash
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: DetectInstanceClash
PerfTime Start: DetectInstanceClash : Wed Jan 18 07:48:31 2006
<Func Name='DetectInstanceClash'>
<Func Name='ValidateInstanceName'>
Error Code: 0x80076db6 (28086)
Windows Error Text: Source File Name: sqlca\sqlcax.cpp
Compiler Timestamp: Wed Sep 21 01:10:12 2005
Function Name: ValidateInstanceName
Source Line Number: 445Error Code: 28086
MSI (s) (54!7C) [07:48:41:312]: Product: Microsoft SQL Server 2005 -- Error 28086. An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name.Error 28086. An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name.
<EndFunc Name='LaunchFunction' Return='28086' GetLastError='0'>
Action ended 07:48:41: DetectInstanceClash.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3.
Action ended 07:48:41: INSTALL. Return value 3.
Property(S): ProductCode = {FFFA78A7-BD51-4255-8470-C4D4A85B49F5}
Property(S): ProductLanguage = 1033
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductVersion = 9.00.1399.06
Property(S): MEDIAPACKAGEPATH = \Setup\
Property(S): ALLUSERS = 1
Property(S): NULLGUID = {00000000-0000-0000-0000-000000000000}
Property(S): ASPNetVersion = 2.0.50727
Property(S): ARPHELPLINK = http://go.microsoft.com/fwlink/?LinkId=52152
Property(S): ARPPRODUCTICON = ARPIcon.ico
Property(S): ARPNOREPAIR = 1
Property(S): ARPSYSTEMCOMPONENT = 1
Property(S): MsiHiddenProperties = SQLPASSWORD;AGTPASSWORD;ASPASSWORD;RSPASSWORD;SQLBROWSERPASSWORD;RSSQLPASSWORD;RSSQLPassword;RSSQLPasswordQuoted;RSSETUPPASSWORD;RSSetupPassword;SAPWD;saPWD;UPGRADEPWD;SqlUpgradePwd;SQLPassword;ServicePassword;ADMINPASSWORD;PIDKEY;FTEPassword.68C6D15C_77E0_11D5_8528_00C04F68155C;checksum.7354AFCB_913B_4E9F_B76C_2376101FDE0C;checksum.;DigitalProductID;DPID;Do_sqlScript.D20239D7_E87C_40C9_9837_E70B8D4882C2;Rollback_SqlConnection.D20239D7_E87C_40C9_9837_E70B8D4882C2;Do_XmlSingleNode.D20239D7_E87C_40C9_9837_E70B8D4882C2;Do_RSSetting.D20239D7_E87C_40C9_9837_E70B8D4882C2;PID;ProductID;RSUPGRADEPASSWORD;Do_RSSetSharePointExclusionPath.D20239D7_E87C_40C9_9837_E70B8D4882C2
Property(S): SecureCustomProperties = SQL_SHOWLIC;UPGRADESQL90
Property(S): SqlServerBuild = 1
Property(S): SqlCluster = 0 -
Monday, January 23, 2006 3:44 PMOwner
I don't understand you're concern with installing as named instance. I understand you don't think you need - given there doesn't seem to be any SQL2K left on the box - but all things being equal, what is the difference between default and named instance?
Did you take a look at the processes running on your machine to make sure there is no SQL2K running? Remember, some applications embed MSDE and if this was installed as a default instance you'd hit a clash. No, most apps that embed MSDE install as a named instance to avoid this problem, but maybe it's some internally developed application.
I grasping for something here as I've not heard of any other reports of the SQL2K5 setup misreporting the existence of a SQL2K instance.
Cheers,
Dan -
Sunday, January 29, 2006 9:34 PM
Hi,
I had the same problem due to a bad uninstall of a beta version. In my case, although all the sql server files had been removed there, was still a reference to the service in the registry. The solution was to
1. Uninstall any bits of sql server that did get installed
2. Remove C:\Program Files\Microsoft SQL Server although I think just removing C:\Program Files\Microsoft SQL Server\MSSQL.1 will suffice.
3. Open regedit and delete the following keys:
- HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSSQLServer
- HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\MSSQL.1
- HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\Services\SQL Server
4. Reboot and then reinstall.
Not sure if all of the registry keys need to be removed but this worked for me.
Good luck,
Dave Sparks
-
Tuesday, January 31, 2006 8:49 AM
Dear Mr Sparks
Thank you very much for your suggestion.
Unfortunately I got to the point where I had run out of time for experimentation, so I have had to install a named instance and can not confirm for anyone else that this will work, however is does sound extremely promising.
I have not convinced the chap from Microsoft why I do not really want to have a named instance, but in live environments I do like machines set up correctly. I am even more paranoid than normal in this instance as the server that we are installing on has a permanent internet connection. Hangovers from old installation can sometimes have unexpected side effects so I want to be sure that I am using SQL Sever 2005 not mostly 2005 with an odd bit of 2000.
In the past we got caught when we upgraded from SQL Server 7 to SQL Server 2000 with a number of applications that were written in Access/VBA but used SQL Server as the database. It was the issue of Access returning -1 from SQL 7 and 1 from 2000 bit columns. If we have bits of SQL Server 2000 hanging around we might miss similar issues.
Once more thank you for your assitance
Yours sincerely
Ian Smith
-
Tuesday, February 27, 2007 8:20 AM
Hi,
I experienced the same error (28086) installing SQL Server 2005 Express Edition SP2 yesterday. Before that, the machine was running MSDE 2000 until 01/2006, and then SQL Server 2005 Express Edition. Removing the registry keys helped, there were entries for MSSQL and SQLEXPRESS left. SQL Server 2005 Express Edition SP2 is installed and running now.
Yours
Alexander Mazurek
-
Sunday, August 05, 2007 6:28 AMDave,
Thank you very much.
I had the same problem after migrating from XP Professional to Vista Home Premium. I tried a lot of thins for hours to uninstall SQL 2005 Standard, but kept getting the error of existing instance with same name. Changing the registry keys solved the problem. -
Sunday, March 30, 2008 7:04 PM
Hi Dave,
thanks for your valuable suggestion!
i'm working on a project with C#.Net , i installed SQL Server 2005 Express Edition. during installation i selected named instance by mistake. the team leader asked me to remove sql server and reinstall it with default instance because named instance may cause problems and we don't have time to waste.
i tried several ways to uninstall sql server and finally found your suggestion and it worked , but while re-installing the installation wizard didn't give me the option to select between default and named instance , it installed named instance (SQLEXPRESS). now i would like to install the default instance , can anyone help me !!
with the named instance i tried to create my first page just to test the connection (after creating the database ) , but got this error msg:
ERROR [08001] [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied. ERROR [01000] [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
for this reason i felt i have to remove the named instance because it failed in the first test!
if anyone know how to reinstall the default instance or how to fix the above error please let me know
-
Thursday, July 01, 2010 2:52 AM
Hi,
I had a similar problem. I had a SQL 2005 Dev Edition installed on C: but wanted to move it to D: because of space constraints
I did the Complete Unistall but when tried to reinstall with a Default Instance Name I came across the following error:
Product: Microsoft SQL Server 2005 (64-bit) -- Error 28086. An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name.
I followed the above suggestion from DAVE and figured out the following about the residual Registry Keys:
1) HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSSQLServer - did not exist for me
2) HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\MSSQL.1 - did not exist but instead had
HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\MSSQL.3
3) HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\Services\SQL Server - existed
I did remove them and rebooted and that resolved the issue
Good Luck
Grishma
-
Monday, September 20, 2010 5:28 AM
Thank you sparkplug,
i had a problem with whs with mymovies sql not installing, your solution worked like a charm,after trying a lot of options and none worked.
thank you!!!!!
(here is a link i published using your solution: http://social.microsoft.com/Forums/en-US/whssoftware/thread/1c71b745-2cbd-4385-aabc-a82b1e960aa2/?prof=required)
-
Friday, July 22, 2011 7:27 AMI have moved from one blog to another trying to clean an MsSql 2005 default instance i installed. The first problem started when installing Sql Server 2005 Developer Edition with BI, giving an error saying Sql Server Service failed to start, thats when i tried to uninstall it and try some new way to install and now it keeps giving the "Error 28086. An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name."
I failed to follow the procedure on this blog as some of the keys you listed i couldnt find them so i just deleted the whole directory in registry and tried to reinstall but it still keeps giving the same message.
I'm on a Windows 7 Pro 64-bit machine.
Please help i'm really out of ideas on how to complete the installation. -
Tuesday, May 01, 2012 2:35 PM
My Movies 4 Stopped working cannot install SQL Server without error
I had the very same issue - the registry keys do not exist in the same place for the x64 windows 7 install.
[After uninstalling SQLServer and deleting the directory under program files]
I searched the registry for MSSQLServer and it shows up under local machine / software / microsoft.
I deleted this registry key and the installation (to my surprise as I had tried a lot of other hints and tips) worked
I think I also searched for MSSQL.1 and SQL Server just to make sure they were not referencing the install i was trying to do and deleted them if it referenced the installer package.
Good luck
Al
I also used ccleaner to clean up the registry entries after the uninstall, you have to run it twice in succession as it finds more issues after the first cleanup.
- Edited by Big Al Ramsay Tuesday, May 01, 2012 2:36 PM
.png)
