Comments
Sort by recent activity
Hey Casey,
Thanks for the reply; I checked out the server configuration and TCP/IP is already enabled. Actually, I noted that I verified that named pipes and TCP/IP are enabled in my first post [image]
We just moved offices, so I was hoping it would magically start working, but no luck so far... I'll go back and try everything again and will post if something works or I figure it out. / comments
Hey Casey,
Thanks for the reply; I checked out the server configuration and TCP/IP is already enabled. Actually, I noted that I verified that named pipes and TCP/IP are enabled in my first post
We...
Problem solved! One of the other developers figured it out (thank goodness).
In the server field, we have to put:
serverIP\SQLEXPRESS,1433
I'd give an explanation for it, but frankly I don't know why this format has to be used. Something about the port number the server's listening on, which isn't dynamic? I have no idea really. / comments
Problem solved! One of the other developers figured it out (thank goodness).
In the server field, we have to put:
serverIP\SQLEXPRESS,1433
I'd give an explanation for it, but frankly I don't know w...
Still the same "invalid connection" error.
Any reason why these two variations would give a different error?:
servername\SQLEXPRESS = SQL Server does not exist or access denied
TCP:servername\SQLEXPRESS = Invalid connection / comments
Still the same "invalid connection" error.
Any reason why these two variations would give a different error?:
servername\SQLEXPRESS = SQL Server does not exist or access denied
TCP:servername\SQLEX...
Probably wouldn't be the .NET Framework, both of us who can't connect are running 2.0 ... / comments
Probably wouldn't be the .NET Framework, both of us who can't connect are running 2.0 ...
Yes, I've verified that remote connections are allowed on the server, stopped and started the SQL service, and still get the connection error.
The next possibility seems to be starting the Server Browser service and creating firewall exceptions, but we don't want to do that due to increased security risks.
Any other possibilities? I've talked to our dedicated server support and since we can connect via SQL Server Management Studio and this is 3rd party software, they can't really give us support for it but will of course make whatever changes we think need to be made... If only we knew what changes we need! / comments
Yes, I've verified that remote connections are allowed on the server, stopped and started the SQL service, and still get the connection error.
The next possibility seems to be starting the Server B...
Ok, apparently one developer here can connect no problem, the other 2 of us can't. I'm on XP as is the developer who can connect, so... now I'm really stumped. / comments
Ok, apparently one developer here can connect no problem, the other 2 of us can't. I'm on XP as is the developer who can connect, so... now I'm really stumped.