Your sql server installation is either corrupt or has been tampered with

Repair a failed SQL Server installation

The repair operation can be used in the following scenarios:

• Repair an instance of SQL Server that is corrupted after it was successfully installed.
• Repair an instance of SQL Server if the upgrade operation is canceled or fails after the instance name is mapped to the newly upgraded instance.
  • If you see the following message in the summary log, you can repair the failed upgrade instance:

  SQL Server upgrade failed. To continue, investigate the reason for the failure, correct the problem, and then repair your installation.

  SQL Server upgrade failed. To continue, investigate the reason for the failure, correct the problem.

  These instructions don’t apply to SQL Server Express edition.

  When you repair an instance of SQL Server:

  • All missing or corrupt files are replaced.
  • All missing or corrupt registry keys are replaced.
  • All missing or invalid configuration values are set to default values.

  Before you continue, for SQL Server failover clusters, review the following important information:

  • Repair must be run on individual cluster nodes.
  • To repair a failover cluster node after a failed Prepare operation, use Remove node and then perform the Prepare step again. For more information, see Add or remove nodes in a failover cluster instance (Setup).

  Repair a failed installation of SQL Server from the Installation Center

  1. Launch the SQL Server Setup program ( setup.exe ) from SQL Server installation media.
  2. After prerequisites and system verification, the Setup program will display the SQL Server Installation Center page.
  3. Select Maintenance in the left-hand navigation area, and then select Repair to start the repair operation.

  Tip If the Installation Center was launched using the start menu, you’ll need to provide the location of the installation media at this time.

  Repair a failed installation of SQL Server using the command prompt

  1. Run the following command at a command prompt:

  Setup.exe /q /ACTION=Repair /INSTANCENAME=instancename 

  Related content

  • View and Read SQL Server Setup Log Files
  • Installation How-to articles

  Your sql server installation is either corrupt or has been tampered with

  SQL Server 2005 (running side by side with SQL Server 2000). The problem is
  with one of my SQL Server 2005 instances.

  I suffered a power loss. Now, I can’t connect to one of my installed
  instances via Enterprise Manager and I can’t start the service directly
  either via the Services applet. The full error message is:

  Your SQL Server installation is either corrupt or has been tampered with
  (Error getting instance ID from name.). Please uninstall and then re-run
  setup to correct this problem.

  OK, so how do I go about uninstalling an instance? I don’t need to install
  the entire product do I? Oh, please, please say no.

  Thanks for your advice!

  2006-11-30 11:08:25 UTC

  Hmmm — sounds to me your registry is screwed!
  You could try this (at your own risk) before you go down the route of
  reinstalling.
  http://support.microsoft.com/default.aspx?scid=kb;en-us;290301
  Immy

  Post by Joseph Geretz
  SQL Server 2005 (running side by side with SQL Server 2000). The problem
  is with one of my SQL Server 2005 instances.
  I suffered a power loss. Now, I can’t connect to one of my installed
  instances via Enterprise Manager and I can’t start the service directly
  Your SQL Server installation is either corrupt or has been tampered with
  (Error getting instance ID from name.). Please uninstall and then re-run
  setup to correct this problem.
  OK, so how do I go about uninstalling an instance? I don’t need to install
  the entire product do I? Oh, please, please say no.
  Thanks for your advice!
  — Joe Geretz —

  Joseph Geretz
  2006-11-30 18:20:24 UTC

  Are you saying there’s no documented procedure for uninstalling an instance?
  I’d much rather completely uninstall and reinstall SQL SErver 2005 than mess
  around with the Registry. But I’m hoping I won’t have to.

  Post by Immy
  Hmmm — sounds to me your registry is screwed!
  You could try this (at your own risk) before you go down the route of
  reinstalling.
  http://support.microsoft.com/default.aspx?scid=kb;en-us;290301
  Immy

  Post by Joseph Geretz
  SQL Server 2005 (running side by side with SQL Server 2000). The problem
  is with one of my SQL Server 2005 instances.
  I suffered a power loss. Now, I can’t connect to one of my installed
  instances via Enterprise Manager and I can’t start the service directly
  Your SQL Server installation is either corrupt or has been tampered with
  (Error getting instance ID from name.). Please uninstall and then re-run
  setup to correct this problem.
  OK, so how do I go about uninstalling an instance? I don’t need to
  install the entire product do I? Oh, please, please say no.
  Thanks for your advice!
  — Joe Geretz —

  Tibor Karaszi
  2006-11-30 21:38:44 UTC

  The setup program has an option to fix the registry entries for you. Also, uninstalling is like any
  application.
  —
  Tibor Karaszi, SQL Server MVP
  http://www.karaszi.com/sqlserver/default.asp
  http://www.solidqualitylearning.com/

  Post by Joseph Geretz
  Hi Immy,
  Are you saying there’s no documented procedure for uninstalling an instance? I’d much rather
  completely uninstall and reinstall SQL SErver 2005 than mess around with the Registry. But I’m
  hoping I won’t have to.
  Thanks,
  Joe Geretz

  Post by Immy
  Hmmm — sounds to me your registry is screwed!
  You could try this (at your own risk) before you go down the route of reinstalling.
  http://support.microsoft.com/default.aspx?scid=kb;en-us;290301
  Immy

  SQL Server 2005 (running side by side with SQL Server 2000). The problem is with one of my SQL
  Server 2005 instances.
  I suffered a power loss. Now, I can’t connect to one of my installed instances via Enterprise
  Manager and I can’t start the service directly either via the Services applet. The full error
  Your SQL Server installation is either corrupt or has been tampered with (Error getting instance
  ID from name.). Please uninstall and then re-run setup to correct this problem.
  OK, so how do I go about uninstalling an instance? I don’t need to install the entire product do
  I? Oh, please, please say no.
  Thanks for your advice!
  — Joe Geretz —

  Joseph Geretz
  2006-12-04 22:38:40 UTC

  I was unable to uninstall the instance because the uninstall program didn’t
  show that instance. I searched my registry for all occurrences of the
  instance name (stuff showed up like MSSQL$TENX) and deleted them. The
  service is gone, no more errors on startup and Enterprise Manager no longer
  shows the instance.

  Problem solved, thanks for all your advice.

  Post by Tibor Karaszi
  The setup program has an option to fix the registry entries for you. Also,
  uninstalling is like any application.
  —
  Tibor Karaszi, SQL Server MVP
  http://www.karaszi.com/sqlserver/default.asp
  http://www.solidqualitylearning.com/

  Post by Joseph Geretz
  Hi Immy,
  Are you saying there’s no documented procedure for uninstalling an
  instance? I’d much rather completely uninstall and reinstall SQL SErver
  2005 than mess around with the Registry. But I’m hoping I won’t have to.
  Thanks,
  Joe Geretz

  Post by Immy
  Hmmm — sounds to me your registry is screwed!
  You could try this (at your own risk) before you go down the route of reinstalling.
  http://support.microsoft.com/default.aspx?scid=kb;en-us;290301
  Immy

  Post by Joseph Geretz
  SQL Server 2005 (running side by side with SQL Server 2000). The
  problem is with one of my SQL Server 2005 instances.
  I suffered a power loss. Now, I can’t connect to one of my installed
  instances via Enterprise Manager and I can’t start the service directly
  Your SQL Server installation is either corrupt or has been tampered
  with (Error getting instance ID from name.). Please uninstall and then
  re-run setup to correct this problem.
  OK, so how do I go about uninstalling an instance? I don’t need to
  install the entire product do I? Oh, please, please say no.
  Thanks for your advice!
  — Joe Geretz —

  Help: SQL Server

  Sharing my knowlege about SQL Server Troubleshooting Skills

  • Home
  • In-Memory OLTP Series
  • SQL Server 2014 Learning Series
  • select * from SQL_World where name = ‘Balmukund’

  Blog Stats

  • 2,099,944 hits

  Blogroll

  • Amit Banerjee
  • Jonathan Kehayias Blog
  • Sudarshan’s Blog

  Select GETDATE()

  December 2014

  M	T	W	T	F	S	S
  1	2	3	4	5	6	7
  8	9	10	11	12	13	14
  15	16	17	18	19	20	21
  22	23	24	25	26	27	28
  29	30	31

  Subscribe

  Follow Blog via Email

  Join 4,729 other subscribers

  Date < getdate()

  • December 2019 (2)
  • November 2019 (1)
  • April 2018 (1)
  • July 2017 (1)
  • August 2016 (1)
  • May 2016 (1)
  • February 2016 (1)
  • July 2015 (2)
  • June 2015 (1)
  • May 2015 (3)
  • April 2015 (4)
  • March 2015 (2)
  • February 2015 (2)
  • January 2015 (1)
  • December 2014 (5)
  • November 2014 (6)
  • September 2014 (8)
  • August 2014 (8)
  • July 2014 (9)
  • June 2014 (8)
  • May 2014 (9)
  • April 2014 (8)
  • March 2014 (6)
  • February 2014 (8)
  • January 2014 (10)
  • December 2013 (11)
  • August 2013 (1)
  • January 2013 (1)
  • December 2012 (1)
  • July 2012 (1)
  • May 2012 (2)
  • March 2012 (1)
  • February 2012 (2)
  • December 2011 (1)
  • November 2011 (1)
  • September 2011 (2)
  • July 2011 (3)
  • June 2011 (7)
  • May 2011 (1)

  Select location from world

  

  Meta

  Error : Your SQL Server installation is either corrupt or has been tampered with (Error getting instance ID from name.). Please uninstall then re-run setup to correct this problem

  Posted by blakhani on December 16, 2014

  While working for my next blog I made some stupid changes and wanted to start SQL from command line. I have been using net start command to start SQL Services from command line but today I ran the executable directly. The advantage of this method is that information which goes to ERRORLOG is also shown on command line. I browsed to Binn folder and typed executable name sqlservr.exe and hit enter. I was welcomed with Error message as below.

  

  E:\Program Files\Microsoft SQL Server\MSSQL12.SQL2014\MSSQL\Binn>sqlservr.exe
  2014-12-16 05:14:43.93 Server Multiple instances of SQL server are installed on this computer. Renter the command, specifying the -s parameter with the name of the instance that you want to start.

  Since my machine has multiple instances, the error message was quite clear so I added –s SQL2012 and hit enter. and this time, I got more dangerous error message

  —————————
  SQL Server
  —————————
  Your SQL Server installation is either corrupt or has been tampered with (Error getting instance ID from name.). Please uninstall then re-run setup to correct this problem
  —————————
  OK
  —————————

  Well, error message as interesting information “Error getting instance ID from name” I went ahead and looked at instance name and it was SQL2014. Once I gave sqlservr.exe –sSQL2014 on command prompt, life was good and SQL Server got started.

  If you get similar error, First make sure that instance name is correct. To know the instance name, refer my earlier blog What’s my SQL Server Name?

  Hope this helps.
  Balmukund

  Your sql server installation is either corrupt or has been tampered with

  We are getting this error message when we try and reload a computer running MSDE. This is installed when we install some software on our computers.

  However we need to change all the computer names, and when we do it kicks out this error, and the only thing that can be done is to say ‘OK’

  We have tried reinstalling the MSDE package, and it comes up with some different error. any ideas?

  **********************************************************************
  Sent via Fuzzy Software @ http://www.fuzzysoftware.com/
  Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources.

  James Luetkehoelter
  2003-07-28 16:29:56 UTC

  You may need to rename the registered server name in sysservers before
  renaming the computer. I haven’t done this with MSDE so I’m not sure if it
  will work the same way.

  sp_dropserver ‘OldServerName’
  go
  sp_addserver ‘NewServerName’,’local’
  go

  Post by Dan Elms ()
  Hi
  We are getting this error message when we try and reload a computer
  running MSDE. This is installed when we install some software on our
  computers.
  Post by Dan Elms ()
  However we need to change all the computer names, and when we do it kicks
  out this error, and the only thing that can be done is to say ‘OK’
  Post by Dan Elms ()
  We have tried reinstalling the MSDE package, and it comes up with some
  different error. any ideas?
  2003-07-30 16:59:49 UTC

  We have tried the Dropserver routine and this part works in that the server changes to whatever newname is specified. However when we now reboot the computer we are getting the following error message:

  Your SQL Server installation is either corrupt or has been tampered with (unknown Package ID). Please rerun Setup.

  We then get the OK option but no others.

  **********************************************************************
  Sent via Fuzzy Software @ http://www.fuzzysoftware.com/
  Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources.

  Mark Broadbent
  2003-07-31 07:27:32 UTC

  what do the sql logs say -and windows event logs?
  —
  BR,

  Mark Broadbent mcdba,mcse+i
  _________________________

  Post by Dan Elms ()
  Hi,
  We have tried the Dropserver routine and this part works in that the
  server changes to whatever newname is specified. However when we now reboot
  Post by Dan Elms ()
  Your SQL Server installation is either corrupt or has been tampered with
  (unknown Package ID). Please rerun Setup.

  Post by Dan Elms ()
  We then get the OK option but no others.
  Any more ideas!!
  Cheers
  Dan
  **********************************************************************
  Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources.

  Похожие публикации:

  1. A tdr has been detected the application must close error code 7
  2. Марка стали с245 это ст3сп
  3. Металл и графит тип проводника
  4. Снип iii 18 75 статус