0

For some reason when I install SQL Server Express (2014), it works fine for a while (usually a day or two), and then quits allowing me to sign in.

I'm not just talking about remotely here, either. Even through the Management Studio, I get:

enter image description here

I sign in using Windows Authentication, and as I said, it DOES WORK fine for a little bit, and then, even though I haven't made any changes, of any kind to the system, the program, or even the database it's linked to, it just decides to quit working until I uninstall/reinstall SQL Server Express (2014), and then it works fine again for a day or two.

I've done this 3 times now, and this is the third time it's decided to spontaneously quit working.

I've tried all the tricks on this website (accepts remote connections, firewall, connection string, starting SQL Browser, ): http://www.sswug.org/articlesection/default.aspx?TargetID=44331 but everything seems in order, and again, it works for a while after install each time.

What could possibly cause this to happen? I don't know where else to look. Should I just go with the (seemingly) more stable SQL Server CE (despite its limitations). Should I go with SQL Server Express 2012, instead? Is 2014 just buggy?

3
  • 2
    No, 2014 is not buggy, and no, CE is not better or more stable - it's actually deprecated. Sounds like the SQL Server service is stopping for some reason (check the Windows event log) or isn't starting up automatically after a reboot (check the startup properties in SQL Server Configuration Manager). – Aaron Bertrand Jun 3 '15 at 19:14
  • @AaronBertrand Yeah, I think you're right. I think I've rebooted between each of these SQL Server fails. I see the SQL Server (SQLEXPRESS) service is stopped, but it also won't let me start it as it errors (either through windows services or Sql Server Manager). I will check the event logs and see if it tells me anything. – VoidKing Jun 3 '15 at 19:28
  • @AaronBertrand Okay, I think I'm in the right place, in Computer Management, I'm in Event Viewer, Windows Logs, and Application. There I can see the error (Event ID 63) "SideBySide" Here is the text it displays: [Activation context generation failed for "C:\Program Files (x86)\Microsoft SQL Server\120\Tools\Binn\ManagementStudio\CopyDatabaseWizard.exe".Error in manifest or policy file "C:\Program Files (x86)\Microsoft SQL Server\120\Tools\Binn\ManagementStudio\CopyDatabaseWizard.exe" on line 8. The value "1.0" of attribute "version" in element "assemblyIdentity" is invalid.] – VoidKing Jun 3 '15 at 19:31
2

The problem is very likely related to your machine; not SQL Server 2014 itself.

A few things I would start checking when the same issue happens:

  1. SQL Server Error Log
  2. Windows Event Log
  3. SQL Server Service Account state and password (is the account disabled or locked?)
  4. Try pinging the IP of SQL Server
  5. Try connecting by forcing TCP, using tcp:192.168.0.1,1433 (replace 192.168.0.1 with the actual IP address)
  6. Try running SysInternal's Process Monitor to see what is happening exactly while attempting the login process.
  7. Is the Kerberos SPN set correctly?

I very much doubt the SQL Server team would release buggy products which even starts failing at login. The logs will definitely give a clue about what is happening, perhaps the installation logs also show something relevant.

1
  • Thanks Max for the edits,I was typing from small screen phone – TheGameiswar Jun 4 '15 at 2:37
1

can you try a get-service *sql* from Powershell next time it stops so you can see if it is running? If not, can you get us the application logs for SQL Server from eventvwr.msc so we can review it? Something might be causing the service to stop. If it isn't, then perhaps your SQL Browser service is stopped. We will need the logs to help you out further.

Just in general be careful with jumping to a older/different product due to what might be a minor issue that isn't related to the product at large. You could waste a lot of time redoing everything then run into a similar problem and jump ship again or get really frustrated.

13
  • You force start the service - and the service starts successfully? Or doesn't? – Aaron Bertrand Jun 3 '15 at 19:24
  • It doesn't. It fails. I checked the event logs and I get a Event ID of 63 "SideBySide" Error. The text reads as follows [Activation context generation failed for "C:\Program Files (x86)\Microsoft SQL Server\120\Tools\Binn\ManagementStudio\CopyDatabaseWizard.exe".Error in manifest or policy file "C:\Program Files (x86)\Microsoft SQL Server\120\Tools\Binn\ManagementStudio\CopyDatabaseWizard.exe" on line 8. The value "1.0" of attribute "version" in element "assemblyIdentity" is invalid.] – VoidKing Jun 3 '15 at 19:38
  • @AaronBertrand When I try to force start the service (SQL Server (SQLEXPRESS)) I get the following message "The request failed or the service did not respond in a timely fashion. Consult the event log or other applicable error logs for details." To which it shows an error 63 (SideBySide) error. I looked here: social.technet.microsoft.com/wiki/contents/articles/… and it says to possibly reinstall C++ which I have, but to no avail. – VoidKing Jun 3 '15 at 19:59
  • What is your operating system? Is your operating system x86 or x64? Are you running the x86 or x64 version of SQL Express? – Aaron Bertrand Jun 3 '15 at 20:05
  • @AaronBertrand Okay, I've got it. Apparently it was trying to logon with a specific account (not sure what account it thought it should have since I've only been logging on using Windows Authentication), but after I resolved that and restarted the service, I was able to get back on. I'm assuming I don't need the SQL Browser, since it's still disabled but I'm logging on just fine? Anyway, I really appreciate the help, I'll just have to check it again at startup. If you want to write this up as an answer, I'll be happy to upvote and accept. – VoidKing Jun 3 '15 at 20:08

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.