Tuesday, March 11, 2014

Could not start Service Broker for database id

Could not start Service Broker for database id: 27. A problem is preventing SQL Server from starting Service Broker. Check the SQL Server error log for additional messages.


I ran into this issue and was happy to find this solution. Thought of sharing this fix and also for my future reference purpose.

When I checked in the error log, below message was logged.

Starting up database 'master4IDR'.
The database 'master4IDR' is marked RESTORING and is in a state that does not allow recovery to be run.
Starting up database 'master4IDR'.
CHECKDB for database 'master4IDR' finished without errors on 2014-03-10 22:07:42.393 (local time). This is an 22:52:21.10 Backup Database was restored: Database: master4IDR, creation date(time): 2014/03/08(23:03:49), first LSN: 78191:16:37, last LSN: 78191:40:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'RESTORE_restore_'}). Informational message. No user action required.
Could not start Service Broker for database id: 27. A problem is preventing SQL Server from starting Service Broker. Check the SQL Server error log for additional messages.


The windows and application logs do not give me any for information. I have checked the database instance and found that Database ID 27 does not exist in the sys.databases table.

Solution/Fix: To avoid this alert, I have set the "Enable Disaster Recovery File Updates" parameter to 0 in the regedit at the below location.

MY Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Engine\SQL Server

For futher details, please refer to the below links.

1) http://www.symantec.com/connect/forums/backup-exec-2010-r3-idr-sql-backup-will-not-uninstall
2) http://www.symantec.com/business/support/index?page=content&id=TECH49015

4 comments:

  1. Dear Naveen- Thanks a lot for this article. I am facing this exact same issue. The reference links of Symantec website that you have shared are not working.

    The Regedit key path that you have showed - it shows the name of "Symantec Backup Exec" application. I also have this same application on the server where I am getting this error. So, it seems more related to this application.....not anything of SQL Server itself. Also, no troubleshooting needed in Service Broker in SQL - right? FYI, the IS_BROKER_ENABLED of BEDB (BackupExec) database is 0.

    Thanks in advance.

    ReplyDelete
  2. This is a great inspiring article.I am pretty much pleased with your good work.You put really very helpful information. Keep it up. Keep blogging. Looking to reading your next post. south africa brokerage firms

    ReplyDelete
  3. The crypto neighborhood is keen to see whether crypto continues to rally as it started the year. This, or continue to drop with the typical markets. In this situation, the securities market can be aided by the government, the crypto market gets on its very own which means it could experience substantial losses. Bitcoin investment

    ReplyDelete
  4. Individuals who have Marfan syndrome are advised to avoid Make contact with and aggressive sports and isometric exercise like excess Aortic valve-sparing surgery in Marfan syndrome. Dr. Eyal Nachum is a senior cardiologist working in Heart Transplantation Unit, Sheba Medical Center, Ramat Gan, Israel.

    ReplyDelete