VDI error 1000: Failed to recognize the SQL Server instance

• 
  Just to add, I ran:

  sc sdshow "SQL Backup Agent"
  

  on the server and got this output:

  [SC] OpenService FAILED 1060:
  
  The specified service does not exist as an installed service.
  

  However when I run

  net start "SQL Backup Agent"
  

  I get:

  The requested service has already been started.
  More help is available by typing NET HELPMSG 2182.
  

  keymoo December 02, 2008 05:52

  - 0 +
• 
  In the first example, you need to use the internal name (listed as "ServiceName"), so you would run:
  

  sc sdshow "SqlBackupAgent"
  

  
  A couple of questions:
  - Are there other instances on the same machine, and what version of SQL Server are they.
  - What account is the SQL Backup Agent account running as?
  
  Jason

  Jason Cook December 02, 2008 08:28

  - 0 +
• 
  Thanks Jason, when running

  sc sdshow "SqlBackupAgent"
  

  I get

  D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
  

  
  To answer your other questions
  - There is only one default instance of SQL Server (2000 SP3)
  - The SQL Backup Agent is running as a domain account called sa-SQLBackup and is in sysadmin server role in SQL Server. It is a normal account on the server (i.e. not a local admin).

  keymoo December 02, 2008 09:01

  - 0 +
• 

  keymoo wrote:

  Thanks Jason, when running

  sc sdshow "SqlBackupAgent"
  

  I get

  D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
  

  
  To answer your other questions
  - There is only one default instance of SQL Server (2000 SP3)
  - The SQL Backup Agent is running as a domain account called sa-SQLBackup and is in sysadmin server role in SQL Server. It is a normal account on the server (i.e. not a local admin).

  
  Just make it local admin and that will fix everything.

  brosato December 02, 2008 09:52

  - 0 +
• 

  brosato wrote:

  Just make it local admin and that will fix everything.

  Very funny - actually I did do that just as a test and I got identical behaviour.

  keymoo December 02, 2008 10:10

  - 0 +
• 

  keymoo wrote:

  brosato wrote:

  Just make it local admin and that will fix everything.

  Very funny - actually I did do that just as a test and I got identical behaviour.

  
  
  I wasn't trying to be funny actually. That's what I had to do to get it working. Although I have another server that's set up identical and it works without being local admin.

  brosato December 02, 2008 10:21

  - 0 +
• 

  keymoo wrote:

  brosato wrote:

  Just make it local admin and that will fix everything.

  Very funny - actually I did do that just as a test and I got identical behaviour.

  
  
  Oh, make sure you restart the service after adding the account to local admin.

  brosato December 02, 2008 10:22

  - 0 +
• 
  Great that fixed it - however I really don't want to run the SQL Backup service as a local admin.
  
  red-gate: anything else for me to try?

  keymoo December 03, 2008 02:42

  - 0 +
• 
  This issue is usually caused by security restrictions on the SQL Server service object. When you run sc sdshow, you should run it against the SQL Server service, not the SQL Backup Agent service. That should tell you the rights that have been assigned to the service.
  
  Alternatively, you can download this app to check the DACL of the service.

  petey December 03, 2008 03:18

  - 0 +

Add comment

Please sign in to leave a comment.