We created a Windows application in .net 3.5. When I run it on my development machine (installed application, rather than VS), I can connect to the local server database database data using the name of the server (localdb)\v11.0. When I run on the client computer, I get an exception when using this server name. When I use the name named-pipe servername, I can connect and query the database.
On my development machine, I can also connect to (localdb)\v11.0from SSMS (Express) 2008 R2 SP2. This also does not work on the client machine.
Has anyone got any ideal that is missing on a client machine and is installed on my development machine?
Error from SSMS:
Cannot connect to (localdb) \ v11.0.
Er is een netwerkfout of een instanceplaarspecifieke fout opgetreden tijdens het maken van verbinding met SQL Server. De server is niet gevonden of is niet toegankelijk. The Exemplaarnaam controller is correct in that in SQL Server externe verbindingen zijn toegestaan. (provider: SQL-netwerkinterfaces, error: 26 - Fout bij zoeken van opgegeven server / instanceplaar) (Net SqlClient data provider)
For help, click http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476
Error Number: -1 Severity: 20 State: 0
UPDATE:
When executing the following request from 2008 R2 SP2 Management Studio:
SELECT net_transport FROM sys.dm_exec_connections WHERE session_id = @@ SPID;
Result: Named pipe
, - SSMS , (localdb)\v11.0, . , named-pipe - .
SQL- ( sqlexpress) TCP , .
2:
(. ) , , .NET3.5. , :.net 4.0.3. Windows 7 .net 4.5, , .net 4.0.3 ?
3: ###
2014-12-22: () . , , . (localdb)\v11.0 ". Visual Studio 2012 .
Microsoft, ? , ?