Completed
Last Updated: 25 Nov 2016 13:57 by Martin
Scott
Created on: 05 Mar 2015 10:19
Type: Bug Report
1
report server web application LocalDB exception
Following the ReportServerManual.pdf I meet the system requirements, using Visual Studio 2013 and have followed the installation guide but I am getting the following error when running the report server web application;

"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: 50 - Local Database Runtime error occurred. Cannot create an automatic instance. See the Windows Application event log for error details.
)"

I have checked the application pool identity has permission to the files.
Please advise.  Kind regards, Scott.
2 comments
Martin
Posted on: 05 Mar 2015 16:38
The problem is that the web.config file points to an instance that no doubt doesn't exist on your SQL Server, the default one expects an instance called "V11.0". This is documented as a standard approach in the MSDN article "SQL Server Connection Strings for ASP.NET Web Applications" - https://msdn.microsoft.com/en-us/library/jj653752(v=vs.110).aspx

I was able to edit this to use my correct SQL instance and this brought a new error regarding the user didn't have permissions to open the file, this was because my web directory was not in the standard wwwroot folder. Once I created a new local user, gave it permissions and set this as the App Pool identity this then produced a new error relating to the CREATE DATABASE script failed as the file already existed, I altered the name of the .MDF file in the web.config and then I was able to launch the web page correctly and also sign-up.

Not a true out of the box solution, but if the manual was updated to include a few more scenarios then it would be straightforward.
Jan Brandenburger
Posted on: 05 Mar 2015 11:26
I have the same problem...
The problem: I want to use the File storage provider and not an SQl.

The SQL I want to test in an later release?