JBickford.com

SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified

This problem was driving me crazy! Trying to work on a project in Visual Studio 2012, with my SQL Connections pointed at “(localdb)\Projects”. I would be working, refresh and the page would come to a complete halt – could not find instance.

Then I stumbled upon this helpful comment from Ward Beattie:

By default, a LocalDB instance will terminate after 5 minutes with no connections. This can be changed, as follows:

1. Connect to the instance as sysadmin.

2. Run the following batch to show advanced options:

exec sp_configure ‘show advanced options’,1

reconfigure

exec sp_configure

go

3 Run the following batch to change the timeout to 65535. This value is in seconds, but 65535 is the magic number meaning infinite:

exec sp_configure ‘user instance timeout’,65535

reconfigure

exec sp_configure ‘user instance timeout’

go

Once this is done, you will need to shut down the instance using SqlLocalDB.exe, or by connecting and using the T-SQL shutdown command. The instance will also shut down if the user that started it (and owns it) logs off.

 

Sure enough, I extended the timeout and it seems to build and run correctly again!

Crystal Reports Runtime 64-bit: Error 1606

Driving myself crazy trying to move our ASP.NET Application from an old IIS6 server to IIS7, I ran into a problem deploying the 64-bit version of the CR redistributable.

Building off a fresh install of Windows Server 2008 R2, I thought, ‘no problem’. Installed IIS7.5, ASP.NET, .NET, ect.

As soon as I went to deploy the runtime, I was greeted with this lovely message:

Error 1606: Could not access network location \ASP.NETClientFiles\.

While it took me a long time to figure out what was the problem (mostly because I assumed that a fresh image would have no issues), the solution was quite simple. It turned out to be a privileges issue. Incorrectly, I had ruled this out because I had been working on the system with a Local Administrator account. Regardless, continued to have problems.

I didn’t research why exactly there was no additional ‘run elevated’ option from the executable, and instead I opened a fresh command prompt with elevated privileges. After navigating to my CRRuntime_64bit_13_0.msi file, everything installed without a hitch.