Locked install with sql alias

  • Wednesday, September 05, 2012 4:27 PM
     
     

    Hey,

    I want install SharePoint 2013 with a SQL Alias. The SQL Server and the SharePoint Server are on the same machine.

    For the SQL Server I create a Alias. It works when I connect with the “SQL Management Studio” to the SQL Server.

    But when I put the SQL Alias in the SharePoint Farm wizard it’s not connect to the SQL Server (in the windows events stand: SQL Server not found). When I put the SQL Server Name in the wizard its runs correct.

    What can I do to install SP 2013 with SQL Alias?

    Thanks for your help

    Stefan


    Viele Grüße Stefan

    Kontakt unter Info@IT-Kiessig.de

All Replies

  • Wednesday, September 05, 2012 7:55 PM
     
     

    The configuration wizard should accept an alias without issue, in fact it's the recommended approach and you should use an alias.

    Did you create both 32-bit (C:\Windows\system32\cliconfg.exe) and 64-bit (C:\Windows\SysWOW64\cliconfg.exe) aliases?

    Will you please post the entire error message you are seeing in the event viewer (along with event IDs and other key information) and the configuration log?


    Jason Warren
    Infrastructure Architect

  • Wednesday, September 05, 2012 10:18 PM
     
     

    Thanks Jason for your help.

    I had just had create a 64bit alias. Now I also create a 32bit alias and it works. Will it be working with only a 32bit alias? Why I have to create a 32bit alias on a 64bit machine?

    Thanks Stefan  


    Viele Grüße Stefan

    Kontakt unter Info@IT-Kiessig.de

  • Friday, September 14, 2012 8:19 PM
     
     

    Each alias is for clients running in the different architecture. Even though the server is 64-bit, you can still run 32-bit applications. The different versions of cliconfig.exe update different registry keys for the different architectures.

    I don't know for sure but my guess is the configuration wizard is a 32-bit application which is why setting the 32-bit alias works.


    Jason Warren
    Infrastructure Architect

  • Monday, September 24, 2012 2:00 PM
     
     

    Hi Stefan and Jason,

    I have the same problem. I configured sql alias (both 32bit and 64bit) for a SQL server 2012 instance, which is located on the same box as SharePoin 2013 to be configured. I can access the instance with SQL management studio via alias, but when I try to setup SharePoint 2013 with SharePoint Product Configuration Wizard. It cannot connect via alias, yet serverName\instanceName works fine. Any other possible reasons? I have already had both 32bit and 64bit alias configured and even set fireware inbound rule for the port.

    Thanks

  • Monday, September 24, 2012 2:23 PM
     
     

    Hi Ming,

    I suggest trying to see if you can access the instance using the alias via another method, i.e. a UDL file.

    Log on to the server as the account you are setting up SharePoint with and create a file on the desktop (e.g. aliastest.udl). Open this file and the Data link properties window will open. Try to connect using the alias name and Windows authentication. If you still cannot connect verify the alias's configuration that it is pointing to the correct location (typos happen) and that the account you are using to install SharePoint has the dbcreator and securityadmin roles in SQL Server.


    Jason Warren
    Infrastructure Architect

  • Monday, September 24, 2012 5:56 PM
     
     Answered

    Hi Jason,

    With aliastest.udl, I still cannot connect via alias, but I can connect via alias by using SQL Sever Management Studio.  Doesn't it confirm that my alias is configured correctly? If there is any typos or my windows account does not have the privilige, the alias should not work on SSMS either, right?

    Ming

  • Monday, September 24, 2012 6:04 PM
     
     Answered
    Did you double check both 64-bit (C:\Winddows\SysWOW64\cliconfg.exe) and 32-bit (C:\Windows\system32\cliconfg.exe) aliases? It sounds like one of them may be incorrect which is why it is working in one application but not another (in this case the two applications could be of different architectures).

    Jason Warren
    Infrastructure Architect

  • Monday, September 24, 2012 6:14 PM
     
     

    I configured the alias in SQL Server Configuration Manger in both 32 bit client and 64 bit SQL Native Client 11.0 Configuration with same alias name: SPDB. I also checked the cofiguration with both C:\Winddows\SysWOW64\cliconfg.exe and C:\Windows\system32\cliconfg.exe. The alias is there in both cliconfg. Are there any difference for the connection for SSMS and SharePoint configuration wizard or aliastest.udl? Anything else I can try?

    Thank you.

    Ming

  • Monday, September 24, 2012 6:23 PM
     
     

    Hi Jason,

    I found the problem. You are right, typo is the culprit. I notice that the alias name in SQL Server Configuration Manager 32bit SQL Native Client Configuration has a trialing space after the name: "SPDB ", which is hardly notice.  After I delete the trailing space it works.

    Thank you so much.

    Ming


    • Edited by Ming Z Monday, September 24, 2012 6:23 PM
    •