I love when people set up alias for their SQL Server installation; and wondering why it is not working (Of course complaining to DBA’s that the SQL Server remote access is not enabled ). Well, remote access is just fine, alias as well… then what can be the problem?
Let’s see in a real world scenario:
Running an application on Windows Server 2008 R2 can be both 32 and 64 bit application. If the alias created using the 64 bit version of cliconfg.exe and the application is built for 32 bit, it will not be able to see the alias, network error 53 will be returned. The following table shows the path for the correct cliconfg.exe in different scenarios:
|Server Platform ||Application platform ||cliconfg path |
|X86 ||X86 ||C:\windows\system32 |
|X64 ||X86 ||C:\Windows\SysWOW64 |
|X64 ||X64 ||C:\windows\system32 |
Another option is to use SQL Server Configuration Manager and you will find both platforms there.
I’ve found a great article about the same at Tibor Karaszi’s blog.