Activity overview
Latest activity by fullonmac
I have solved the problem and it wasnt related to Vista at all, I guess I was just grasping at straws.
It turns out the SQL Server was on a different domain than the user I was logging in as.
If I logged in as a new local user to my computer I can connect fine.
So it is a network/security issue.
No idea why SSMS managed to connect and nothing else could though.
As a contractor I had no access to the server and so had to make assumptions based on what the overly busy network admin told me.
As we all know when problem solving, never make any assumptions / always double check things for yourself. But in some situations this is very difficult.
Thanks for all your help. / comments
I have solved the problem and it wasnt related to Vista at all, I guess I was just grasping at straws.
It turns out the SQL Server was on a different domain than the user I was logging in as.
If I ...
I have managed to borrow a colleagues computer (Windows XP) to try from.
I have installed and run SQL Compare 6 (logged in as myself) and it works fine.
This would signify that it is something to do with my client computer either Vista itself or some other software I have installed.
Maybe the default security / firewall settings in Vista are causing the problems?
Maybe the version of ado.net, is this what SQL Compare uses?
All I have installed is SQL Server 2005 SP1 (Server and Client), Visual Studio 2005 SP1, Office 2007 and SQL Compare 6.
I will post if I find a solution, if I dont post again I have resorted to ditching Vista and installing XP from scratch... / comments
I have managed to borrow a colleagues computer (Windows XP) to try from.
I have installed and run SQL Compare 6 (logged in as myself) and it works fine.
This would signify that it is something to d...
I now get the following error if I force it to use TCP over port 1433:
The list of databases for the specified SQL Server could not be retrieved:
A connection was successfully established with the server, but then an error occurred during the pre-login handshake.
When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
(provider: TCP Provider, error:0 - No connection could be made because the target machine actively refused it.)
I originally had exactly the same problem with SQL Server Management Studio (SP2) and I had to uninstall and reinstall using only SP1 and now I can connect from SSMS.
But still no luck with SQL Compare. :evil:
Still not 100% convinced its a Vista issue but im getting there. / comments
I now get the following error if I force it to use TCP over port 1433:
The list of databases for the specified SQL Server could not be retrieved:
A connection was successfully established with the ...
SQL Compare connection issue from Vista
I am getting the following error connecting to a remote SQL Server database from SQL Compare 6 running on Vista Business.
"The list of databases for the specified SQL Server could not be retrieved:...
Was there a resolution to this problem?
I am getting the following error connecting to a remote SQL Server database on Vista.
The list of databases for the specified SQL Server could not be retrieved:
A connection was successfully established with the server, but then an error occurred during the pre-login handshake.
When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error:0 - No process is on the other end of the pipe.)
It is nothing on the server end as I can fine using SQL Server Management Studio from the same computer and other users can connect to the SQL Server. Remote access is allowed. Only TCP/IP. Port 1433.
Any help would be greatly appreciated as I am not able to use another computer to run SQL Compare from. / comments
Was there a resolution to this problem?
I am getting the following error connecting to a remote SQL Server database on Vista.
The list of databases for the specified SQL Server could not be retriev...