Microsoft Sql Server 2005 Instance Wincc Programming
I have heard from a few customers who have tried to uninstall and re-install SQL 2005 and have run into errors with both the uninstall and the re-install. I have already described the most common uninstall error and a suggested workaround in this previous blog post (an error reading property 'Installids' from the cache and/or an error writing property 'flagCommit' to the cache).
Nov 07, 2005 Microsoft SQL Server 2005 Express Edition (SQL Server Express) is a powerful and reliable data management product that delivers rich features, data protection, and performance for embedded application clients, light Web applications, and local data stores. Sql Server 2005 Instance Wincc Sql Server 2005 Instance Wincc is a program collection with 90 downloads. The most lightweight of them are AJAXCMSCreator (sized at 15,393) and Product Key Finder (sized at 593,622), while the largest one is Microsoft SQL Server 2005 Books Online with 143,958,322 bytes.
I wanted to address one of the most common SQL Express install errors I have seen - a duplicate instance name error that causes SQL setup to fail and rollback. Big kahuna reef 2 full game. It is pretty easy to tell if you are running into this error if you launch SQL setup directly and step through the SQL setup UI. However, if you are installing SQL Express as a part of Visual Studio 2005, setup runs in silent mode and you will only see a generic error bubbled up from Visual Studio setup indicating that SQL Express failed to install.
VS 2005 configures SQL Express with an instance name of SQLEXPRESS when it runs SQL setup in silent mode. If you previously had SQL Express installed and try to uninstall it but something goes wrong with uninstall, you may end up with an orphaned instance name on your system, and then re-installing SQL Express can fail. In this case, the verbose setup log file for SQL Express will show an error that looks like the following:
MSI (s) (AC!38) [00:01:41:056]: Product: Microsoft SQL Server 2005 Express Edition -- 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.
If you are running into an error installing SQL Express as a part of Visual Studio 2005 setup, you can check in the SQL Express log files (located at %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOG). If you are receiving an error about the instance name not being unique, you can manually clean off the orphaned instance name by doing the following:
- Click on the Start menu, choose Run and type regedit
- Go to HKEY_LOCAL_MACHINESoftwareMicrosoftMicrosoft SQL Server
- Remove SQLEXPRESS from the REG_MULTI_SZ value named InstalledInstances
- Delete the subhive named MSSQL.1
- Delete the subhive named SQLEXPRESS
- Go to HKEY_LOCAL_MACHINESoftwareMicrosoftMicrosoft SQL ServerInstance NamesSQL
- Delete the value named SQLEXPRESS
- Delete the folder %ProgramFiles%Microsoft SQL ServerMSSQL.1
Note - the above steps apply to the instance name that is created when SQL Express is installed as a part of Visual Studio 2005. The actual instance name on your system may vary if you have had any other beta version of SQL 2005 (such as the developer edition). Please make sure to adjust the steps accordingly based on what instance name information is in your registry and file system.
<update date='7/24/2009'> Updated this post to not be beta-specific. The same type of error can occur if you uninstall and re-install the final release of SQL Express or SQL Express service packs. </update>
I forgot my password for Sql Server 2005. Windows Authentication is not enabled so I cannot login. How can I remove the current instance and create a new db instance? Or is there a better solution exists?
Kevin Fairchild3 Answers
Assuming you are a member of the Windows Admininstrator group, you can put the server in Single User mode, you could try this -
Russ CamRuss CamMy read of the question was that the server is set up to use SQL authentication only, and perhaps you don't know the sa password or any other SQL login credentials? If so, you might be able to change the authentication mode. For SQL Server 2005 default instances, it's stored in the registry at:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL ServerMSSQL.1MSSQLServer
in a DWORD called LoginMode. A value of 2 indicates Mixed Mode (both Windows and SQL authentication are supported); I think 0 is Windows only and 1 is SQL only. You can try changing it to 2, restart the MSSQL service, then try to get into the SQL management studio after logging into the machine as an administrator.
Marriages and families benokraitis. If that fails, you can create another instance by re-running the setup program.
Chris TyburChris TyburMicrosoft Sql Server 2005 Service Pack 4 (kb2463332)
Have you tried connecting when logged on as domain/server-local Administrator?
StuStu