SixBit User Forum

Where shared knowledge and experience are on display for the benefit of the entire SixBit Community. Archived boards are available at forums.sixbitsoftware.com .
  1. Colleen Upton
  2. User to User
  3. Sunday, 31 December 2017
Good Morning,

Since I was forced to update my Windows 10 on Dec 24, I can no longer use SixBit. It's telling me the SQL server is unavailable. I used to be able to go into the task manager and end the process and restart it, but now when I end the SQL (which is actually running), I don't have the option to reboot. It just disappears from the list and I'm not tech savvy enough to find it in the menus.

Furthermore, it gives me the option when I try to run Sixbit to connect via SQL mode or Windows Mode. The Windows mode is the mode I have always used and it worked fine until the update. I tried the SQL mode with the fault user and password (given in the program) but it doesn't work.

I used to be able to have SixBit open when it was not connected to the server, but now it won't even allow me to see my listings, work on them, or do back ups at all. After telling me the SQL server is unavailable it forces me to quit the program. Rebooting the computer did nothing to fix this.

Help please!!

Thank you, C.
MOE Accepted Answer
0
Votes
Undo
If everything installed by SixBit installation,
Choose SQL mode
User:sa
Pass:S1xb1tR0x

https://www.sixbitsoftware.com/docs/webhelp_proen/Sharing_a_Database_on_a_Web_Server.htm
  1. more than a month ago
  2. User to User
  3. # 1
herb oberman Accepted Answer
0
Votes
Undo
Open SERVICES . Sort by NAME and STARTUP TYPE . Under AUTOMATIC look to see if your Sixbit Agent and SQL are running. If they aren't running highlight them and then click on the START SERVICES arrow at the top.
  1. more than a month ago
  2. User to User
  3. # 2
Todd Patterson Accepted Answer
0
Votes
Undo
Colleen,

We have this happen occasionally when there is a Windows update immediately with the next startup. What we do then is exactly as Herb stated on the "server". Once this is done and you can ensure that SixBit is opening on the server then go ahead a shutdown and restart. That seems to take care of the problem until the next Windows update. While it is not EVERY update that does this, I would guess probably right around 50% of the time we have this happen.

Also, as stated above by Moe, it is best to use the SixBit SQL option for connection. Make sure that you are using the exact same password, unless for some reason you have changed it....

Todd
  1. more than a month ago
  2. User to User
  3. # 3
Christopher Terry Accepted Answer
0
Votes
Undo
Even though I do as Herb stated it is forcing me to do the same every time after I bring up my computer in the morning. I shouldn't have to manually start this service every time. Why doesn't Sixbit fix this?
  1. more than a month ago
  2. User to User
  3. # 4
Steve Lea Accepted Answer
0
Votes
Undo
Even though I do as Herb stated it is forcing me to do the same every time after I bring up my computer in the morning. I shouldn't have to manually start this service every time. Why doesn't Sixbit fix this?


Christopher,

Anytime Windows Updates are executed it's going to stop the SQL Server Instance service and perform the updates. You can try changing the Startup Type to Automatic(Delayed Start) on the SQL Server (SIXBITDBSERVER) instance to see if that resolves the issue going forward.

Aside from that, you can set up a task within Windows Task Scheduler if the above doesn't work to have Windows run that task after a reboot to get the SQL Server Instance started back up. See the example screenshots attached to this response, let us know if you have any additional questions or concerns.

Sincerely,
Steve Lea
SixBit Support
Attachments (7)
  1. more than a month ago
  2. User to User
  3. # 5
  • Page :
  • 1


There are no replies made for this post yet.
However, you are not allowed to reply to this post.