April, 2010

  • <dw:daniel_walzenbach runat="server" />

    Visual Studio 2010 and .NET FX 4 available in Japanese, German and French

    • 4 Comments

    Being a German working for Microsoft in the US I am extremely excited to announce that the Japanese, German, and French versions of Visual Studio 2010 and .NET Framework 4 are now available for MSDN subscribers!!  It’s been a long journey, and it is truly rewarding to know that many of our international customers will now be able to experience this incredible product in their native language (and there is more to come :-) ).

    Here are the SKUs available for download as of 5 pm (UTC-08:00) Pacific Time (US & Canada).

    • .NET Framework 4 Client Profile (x86 and x64) LangPack - Japanese, German, French
    • .NET Framework 4 Client Profile (x86) LangPack - Japanese, German, French
    • .NET Framework 4 Full (x86 and ia64) LangPack - Japanese, German, French
    • .NET Framework 4 Full (x86 and x64) LangPack - Japanese, German, French
    • .NET Framework 4 Full (x86) LangPack - Japanese, German, French
    • Report Viewer 2010 Redistributable (x86) LangPack - Japanese, German, French
    • Visual Studio 2010 Express (x86) - DVD (Japanese, German, French)
    • Visual Studio 2010 FSharp 2.0 Runtime (x86) LangPack - Japanese, German, French
    • Visual Studio 2010 Integrated Shell (x86) - Japanese, German, French
    • Visual Studio 2010 Isolated Shell (x86) - Japanese, German, French
    • Visual Studio 2010 Premium (x86) - DVD (Japanese, German, French)
    • Visual Studio 2010 Professional (x86) - DVD (Japanese, German, French)
    • Visual Studio 2010 Remote Debugger (ia64) - Japanese, German, French
    • Visual Studio 2010 Remote Debugger (x64) - Japanese, German, French
    • Visual Studio 2010 Remote Debugger (x86) - Japanese, German, French
    • Visual Studio 2010 Tools for the Office System 4.0 Runtime (x64) LangPack - Japanese, German, French
    • Visual Studio 2010 Tools for the Office System 4.0 Runtime (x86) LangPack - Japanese, German, French
    • Visual Studio 2010 Ultimate (x86) - DVD (Japanese, German, French)
    • Visual Studio Agents 2010 (x86) - DVD (Japanese, German, French)
    • Visual Studio Team Explorer 2010 (x86) - DVD (Japanese, German, French)
    • Visual Studio Team Foundation Server 2010 (x86 and x64) - DVD (Japanese, German, French)
    • Visual Studio Test Professional 2010 (x86) - DVD (Japanese, German, French)

    Enjoy!

       Daniel

  • <dw:daniel_walzenbach runat="server" />

    How to enable remote connections in SQL Server 2008?

    • 102 Comments

    You experience the following error message:

    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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
    SQL Server 2008: The server was not found or was not accessible.

    How to solve this issue?

    There are a couple of things that might be going on here… (All of the following configurations are made on the computer running your SQL Server 2008 instance)

    Allow remote connections to this server

    The first thing you want to check is if Remote Connections are enabled on your SQL Server database. In SQL Server 2008 you do this by opening SQL Server 2008 Management Studio, connect to the server in question, right click the server…

    SQL Server 2008: Server Properties

    … and open the Server Properties.

    SQL Server 2008: Server Properties - Connections

    Navigate to Connections and ensure that Allow remote connections to this server is checked. Check if this solves the problem. If it does, here you go, continue with whatever you were doing and have a nice day.

    Protocols for MSSQLServer

    If you’re still running in issues let’s dig a bit deeper. The next good thing to check is the SQL Server Network Configuration. Open the SQL Server Configuration Manager, unfold the node SQL Server Network Configuration and select Protocols for MSSQLServer (or whatever the name of your SQL Server instance is).

    SQL Server 2008: Protocols for MSSQLServer

    Make sure that TCP/IP is enabled and try again. Even though I hope that this resolved your problems there might still be an issue with…

    The Firewall

    If there is still no communication happening between your computer and the remote SQL Server you most likely need to configure your firewall settings. A good first step is to figure out which port is being used by TCP/IP (and which you need to open in your firewall). You can do this by right clicking TCP/IP and selecting Properties.

    SQL Server 2008: TCP/IP Properties

    Click on the tab IP Addresses and voilà – Port 1433 it is :-) That was easy enough and all there is left to do is to allow inbound TCP/IP traffic on Port 1433 in your firewall. In Windows 7 this works something like this. Open the Control Panel and navigate to Windows Firewall.

    Microsoft Windows 7 Firewall settings

    Click on Advanced Settings on the left hand side and you should see the Windows Firewall with Advanced Security. Select the Inboud Rules on the left hand side and click on New Rule… on the right hand side.

    Microsoft Windows 7 Firewall with Advanced Security

    This opens the New Inbound Rule Wizard which you can use to allow inbound traffic on Port 1433 for TCP/IP (and which is exactly how you configured your SQL Server in the steps above). Just follow the steps outlined below and you should be good :-)

    New Inbound Rule Wizard - Protocols and Ports

    New Inbound Rule Wizard - Protocols and Ports

    New Inbound Rule Wizard - Action

    New Inbound Rule Wizard - Profile

    New Inbound Rule Wizard - Name

    That’s it, success! From here you should be able to access your SQL Server remotely. Enjoy!

    Cheers!

       Daniel

    P.S. There's a good article on msdn on this topic if you're looking for additional information >> Configuring the Windows Firewall to Allow SQL Server Access.

    Update (June 14th, 2010):

     

Page 1 of 1 (2 items)