Can't Connect to Sql Server Express Instance

[Saad Farooq]

I am trying to connect to a local instance of Sql Server Express (On a Surface Pro Tablet) from the ReportingStartup.cs file, and Unable to connect to it. The same connection string works fine in web.config, and i can view the report on the web, but I cant open my jsrep file in visual studio.

using (var ctx = new Context(@"Data Source=(local);Initial Catalog=QISDB;Integrated Security=True"))

I have also tried but it isnt working also:
using (var ctx = new Context(@"Data Source=(local)\MSSQLSERVER;Initial Catalog=QISDB;Integrated Security=True"))


I was able to connect to a remote server though.

[Saad Farooq]

Attached is the Screenshot of the error message. The error is being generated in the Reporting Startup file. Also In my opinion, if there is a multi-line textbox for the stacktrace, it would be easier to read & copy them.

[Jan Blaha]

Does it work if you try to connect to Server Name (local)\MSSQLSERVER in sql server management studio?

I have just a different instance name and it works: (local)\SQLEXPRESS . Maybe you could try also localhost\MSSQLSERVER but it will have probably the same effect.

[Saad Farooq]

No, I cannot acces in SSMS using localhost\MSSQLSERVER .

I can access in SSMS using either
(local)
localhost OR
USER

I am using (local) for my web.config also.
I have a instance named sqlexpress on my laptop and I can access using that on my laptop without any problem. having this problem on my tab only and also the instance name is a little different.

[Jan Blaha]

Hm. Maybe you can try also @"server=localhost;Initial Catalog=QISDB;Integrated Security=True" or put an alias to the instance name or reinstall sql server with a non default instance name.

Anyway I am not sure if this has something to do with jsreport. The connection string is maybe just differently resolved by ado.net classes when it comes from web.config, but this is not an issue of jsreport. It basically just takes the bin folder and runs the ReportingStartup.Configure. There is no place where it could block access to db for example.

[Saad Farooq]

Yes. I thought, I would share to find if there is any connection. I will try to reinstall without the named instance.

[Saad Farooq]

Update:
I installed a new instance WITHOUT the Default name (MSSQLSERVER) and everything works perfect.. I can connect via (local)\SQLEXPRESS