SQL Server (SIXBITDBSERVER) Service Stops Frequently Even When Set to Automatic


You are experiencing an error with SixBit and it has been determined that one of the Windows Services necessary to run SixBit has probably stopped. (Click Here for Steps to Check Your Services) When you check the Windows Services, SQL Server (SIXBITDBSERVER) has indeed stopped. This can happen for several reasons. Windows Updates will sometimes stop this Service. Whatever the reason, usually the problem can be very simply resolved by right-clicking SQL Server (SIXBITDBSERVER) in the Services list and re-setting its status to Started and Automatic. However, once in a while SQL Server (SIXBITDBSERVER) will keep stopping and will continually need to be restarted. The same error pops up frequently and the whole procedure needs to be followed all over again. This is obviously frustrating but never fear, after careful research, we have discovered the reason for this behavior and how it can be fixed.


Please try setting the recovery options.

1. From the search box under Windows Start in Vista or Windows 7, or from Start|Run in Windows XP, enter "services.msc" to show the list of services running on your computer.
2. Look for "SQL Server (SIXBITDBSERVER)" in the list.
3. Right-click on the SQL Server (SIXBITDBSERVER) and select Properties
4. Select the Recovery Tab
5. Set First Failure, Second Failure, and Subsequent Failure to: Restart the Service
6. Set Restart service after to "0" (zero) minutes.
7.Click Apply & OK

If that does not work, you can try the following instructions for editing the registry.

Caution: Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data.
To change the service timeout value:

1. Click the Start button, then click Run, type regedit, and click OK.
2. In the Registry Editor, click the registry subkey HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control.
3. In the details pane, locate the ServicesPipeTimeout entry, right-click that entry and then select Modify.
Note: If the ServicesPipeTimeout entry does not exist, you must create it by selecting New on the Edit menu, followed by the DWORD Value, then typing ServicesPipeTimeout, and clicking Enter.
4. Click Decimal, enter the new timeout value in milliseconds (180000 is 3 minutes), and then click OK.
5. Restart the computer.

  • 19 Users Found This Useful
Was this answer helpful?

Related Articles

"Invocation of the constructor... Root element is missing" error starting SixBit

Background: SixBit stores many of its operating parameters such as window locations, settings...

"Invocation of the constructor... Item has already been added" error starting SixBit

Background:SixBit uses controls from 3rd party vendors. Sometimes those controls have bugs that...

Argument Out of Range Exception When a Wacom Tablet is Installed

Symptom:When switching views, users running with a Wacom tablet get an "Argument out of range...

Database is in Single User Mode

If the database is in Single User mode please take the following steps to correct the issue:1....

How to Tell if a Client can Access the Database on the Server

Background SixBit stores its data using Microsofts SQL Server 2008 R2.  SQL Server is a separate...