This is 2nd day I'm spending on this sql server problem! long story short, I have downloaded/installed sql server 2014 express version on my windows 8.1 operating system. sql server works fine however when I get in it and create tables or etc, when I run asp.net (mvc 4) and click on login page or register page it throws following error:
error: 50 - Local Database Runtime error occurred. Cannot create an automatic instance. See the Windows Application event log for error details.
I have searched in stackoveflow and also msdn, few other forums but did not find a specific and solution to nail this down.
on my machine I have:
SQL SERVER (MSSQLSERVER) service running (Automatic)
Microsoft LocalDB is installed
However,
SQL Server Browser stopped
SQL Server Agent stopped
every time I am trying to restart or start them I get this message:
The service cannot be started, either because it is disabled or because it has no enabled device associated with it[0x80070422]
I also tried this solution but it didn't help. please see this URL
http://www.aspneter.com/2013/08/error-50-local-database-runtime-error-occurred/
Can this be something in web.config?
any help will be appreciated greatly.
Thanks.
amit
Ok the problem is resolved by downloading Microsoft SQL Server 2012 SP1 Feature Pack.
Service Pack SP1
Related
DNN Upgrade error from 9.1 to 9.3.2 : After upgrade we observe that if we reboot server and immediately try to access the web site then we get error like 'Connection To The Database Failed'.This is happen only first time after server reboot. once we start receiving this error after then we continue receive this error irrespective of how many times we hit website. It is exists till we do IIS Restart or Application pool recyle manually.
Because of this issue we have paused server reboot schedule as well.
Please guide how to overcome from this.
Just a guess, but is it possible that SQL Server starts up slowly after the reboot.
Try waiting 5 minutes before going to the website.
I'm actually a bit surprised that you have this on a DNN 9 installation. I haven't seen it myself as of DNN 8.
I recall solving that by changing the startup type for IIS (in the services MMC) from "Automatic" to "Automatic (Delayed)". That should give SQL Server a decent chance to be started before IIS is.
You could also try to configure the IIS service being dependent on SQL Server (if both IIS and SQL Server are installed on the same machine):
sc config W3SVC depend=MSSQLSERVER
Take care, if you are using a named instance as in the SQL Server Express standard installation, the name could be MSSQL$SQLEXPRESS or whatever instead of MSSQLSERVER. Have a look at the properties of the service to find out.
We've had this .NET component (.exe) running to migrate documents between 2 databases for almost a year. Console app is using the System.Data.SqlTypes.SqlFileStream .NET class to read/write from file system.
After a recent upgrade of SQL Server to SQL Server 2016 (SP2-CU3) (KB4458871) - 13.0.5216.0 (X64) - the console app has stopped working and throws the following error when trying to open specific document for read operation:
System.ComponentModel.Win32Exception (0x80004005): The device is not ready
We double-checked FILESTREAM properties on both databases to make sure they are enabled (just in case they were removed somehow during the upgrade) and we confirmed they are configured as needed.
We are running out of troubleshooting options as we don't know what to check for. All ports seem to be open between the app server where this tool runs and the database servers (same as before).
Let me know if anybody has any idea what could have changed after recent SQL Server upgrade.
just in case someone faces the same issue... we were able to resolve this by actually disabling FILESTREAM, rebooting servers, enabling FILESTREAM back on.
Issue was related to some un-mapped path of physical drives for SQL (sorry i cant provide more details)
I recently inhereted a DNN site that has went down as of yesterday (I made no changes to it).
On the front end I see the error
500 - Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed."
I looked at the logs in /Portals/_default/Logs and I see
"2018-08-21 05:57:01,024 [WEBA9][Thread:37][ERROR] DotNetNuke.Common.Initialize - The connection to the database has failed, however, the application is already completely installed, a 500 error page will be shown to visitors"
Does anyone know how I could begin to start debugging this? I'm completely new to DNN. Thanks!
You'll want to start by looking at your web.config file in the root of the site.
From there you'll find the connection string. (control-F to search)
Using the Connection information in that connection string, you should try
Try remoting into the database server to see if you can access it via Remote Desktop, can you access it? Does that server need rebooting?
Try connecting to the database using SSMS (SQL Server Management Studio) using the username/pwd in the connection string.
I imagine that the SQL server is for some reason offline, and you'll need to get it back up and running.
It can happen after a reboot of the server. When IIS with the DNN site comes online earlier than the SQL server is done loading.
Stopping and starting the AppPool of the DNN installation might help.
I installed SQL Server 2014 Developer edition a few days ago. I am eager to work with SSRS, but I cannot seem get the web based Report Server to work.
Following instructions based on issues from others, I made some system corrections on my Windows 7 Professional system by adding my local machine trusted sites (http : / /minint-teerupj ) - my PC Name.
I proceed to run Internet Explorer as Adminstrator, and go to my report server url:
http://minint-teerupj/ReportServer
When I do this, all the screen displays is the following:
minint-teerupj/ReportServer - /
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Microsoft SQL Server Reporting Services Version 12.0.2000.8
Has anyone has this issue?
Maybe I could paste my answers here.
There are two URLs there. Open your reporting service configuration manager, and you could find them: webservice URL & Report manager URL.
I was accessing the incorrect URL,
- the report manager url is:
http://localhost/reports
Thank you zhongxiao
Okay, these are the errors I can't backtrace at all. So I was hoping you had any idea.
When I recently rebooted my server (The server is a home computer, and just runs Windows 7 as a development machine) with Sharepoint 2010, a whole list of problems occurred.
The major error was that when I deployed my Visual Studio 2010 project, it couldn't activate my Feature. This happens more often, because I sometimes mess up in my Feature Activation event handler. But, when that happens, I can access the site, and debug the error while activating the feature manually.
However, this time, things were different. My site didn't even want to start up? So I checked IIS Manager, and it said that the site was stopped. Manually starting it resulted in the following error:
The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020)
I have no clue what that could mean? What file? The web.config? I really don't know.
But I saw that the Sharepoint Central Administration was running, so I decided to check there. However, this resulted in even more errors, well, there was one, but it really frightened me:
Cannot connect to the configuration database.
So, not only my Web server is having errors, but also my database server. Time to check the event logs is what I thought.
And there I'm a bit stunned. There are so many errors, I don't even know where to start. I'm just going to copy the ones which I think are important.
Unknown SQL Exception -1 occurred. Additional error information from SQL Server is included below.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
Sharepoint Foundation seems to give me that one.
The World Wide Web Publishing Service (WWW Service) did not register the URL prefix http://*:80/ for site 908852174. The site has been disabled. The data field contains the error number.
IIS-W3SVC seems to give me that one.
I.. really have no clue what could be the case. Since I cannot acces Central Administration, I can't check for any health issues either.
Anyone has even the slightest idea? I didn't do anything funny I believe. I was thinking that it could've been the updates that were installed, but the only updates installed were:
Security Update for Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package (KB973923)
Definition Update for Microsoft Security Essentials - KB972696 (Definition 1.93.855.0)
Definition Update for Microsoft Security Essentials - KB972696 (Definition 1.93.1040.0)
Definition Update for Microsoft Security Essentials - KB972696 (Definition 1.93.1148.0)
So, it really couldn't have been that. I'm out of ideas, and I really would like to solve this.
Thanks,
Mats
EDIT: Okay, manually started up the SQL Service, and now Central Administration works. But, The Health reporting site started scaring me. There's a list of 8 items requiring my attention.
NT AUTHORITY\NETWORK SERVICE, the account used for the SharePoint timer service and the central administration site, is highly privileged and should not be used for any other services on any machines in the server farm. The following services were found to use this account: SharePoint - 80 (Application Pool)
SPUserCodeV4(Windows Service)
OSearch14(Windows Service)
Web Analytics Data Processing Service(Windows Service)
All required products must be installed on all servers in the farm, and all products should have the same patching and upgrade level across the farm.
Upgrade is required on server MATS-PC. Without the upgrade, the server is not in a supported state.
The following databases have versions that are older than the current SharePoint software, but are within the backwards compatible range:
SharePoint_Config_c5681991-3bec-45b3-9376-ea8c19c51b6a,
SharePoint_AdminContent_39d0c8e9-214e-42b9-909e-ffbe4147208b,
WSS_Content,
WSS_Search_MATS-PC,
WSS_Logging.
Those seemed to be the most relevant. Hm. I have no clue? Especially about the upgrading? I didn't upgrade anything recently.
Especially about the upgrading? I didn't upgrade anything recently.
This sounds a lot like a Microsoft Update. Service packs for SQL Server come through Microsoft Update, and if you applied those without checking carefully, some of them produce similar symptoms to what you're describing. SQL Server can take longer to start up, and when that happens, sometimes antivirus software grabs the MDF/LDF files for scanning. That will cause the databases to be unavailable, and other services will then fail on startup.
When you started SQL manually, things started working again, but now you've got version dependency problems. You're lucky SQL even starts, though - I've had clients with issues where SQL won't start after careless SP applications if they had changed the SA login, for example.
The errors you got while doing the reboot where just because the SQL Service did not startup. No database = no SharePoint. This happens to me all the time.
The other messages in Central Administration are nothing to do with your SQL startup and chances are they have been there for some time.
As any other developer on a single box hosting SharePoint, you have permissioned stuff with a single powerful account. Central Admin now detects this and gives you the warning.
It looks like the SharePoint versions of one or more of your server databases are out of sync with the version of 2010? Not exactly sure how it got into this state, but for a dev box I would not be completely stressed. An upgrade to the new service pack hopefully would sort this out.