May 5, 2011 at 7:29 am
Hey all,
I setup an alias both in my Native Client Configuration for 64bit and 32bit on a Windows 2008 R2 server. The 64bit one works as I'm able to connect to the alias via SSMS; however I am unable to connect to the alias using powershell or sqlcmd.
I'm getting the generic error that an error occurred while establishing a connection.
- The alias exists in SQL Server Configuration Manager (32 bit and 64 bit)
- The alias exists when launching cliconfg from C:\Windows\SysWOW64
- The alias exists in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSSQLServer\Client\ConnectTo
- The alias exists in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConectTo
Any thoughts?
Thanks
May 5, 2011 at 7:49 am
Interesting ... after reading this: http://social.technet.microsoft.com/Forums/en/winserverMigration/thread/84626fc0-b36b-4775-acf7-678fd6ea60dc
I recreated the 32bit and 64bit alias and now it works ...
October 24, 2011 at 9:20 am
Its a wierd one. I came across this myself today, and your link did the trick.
Seems the order of creating the alias is important.
I started by deleting everything,
1) run CLICONFG - create your TCP alias (will default to the x64 version if you're on a 64-bit O/S)
2) From SQL Server Configuration Manager create the alias under "SQL Native Client 10.0 configuration"
Try to connect using SSMS - it worked for me. If it doesn't you could go on to try the 32-bit set-up. I did this anyway as the application I'm developing is x86
3) %SystemRoot%/SysWow64/CliConfg.exe (32-bit version on 64-bit O/S)
4) "SQL Native Client 10.0 Configuration (32bit)" under the configuration manager tool.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply