How can we help you today? How can we help you today?

Trial: Service hangs on clustered named instance

Hi. I had a frustrating experience trying to get the demo to run on the cluster. After quite a bit of digging, I finally discovered that the -i <instance> option was added to the cluster resource, but not to the service on the server. Once I added the -i <instance> the service would actually start.

Now I just can't connect to it.

We are using a non-standard TCP port. I didn't come across any documentation that explained how to deal with this. I also tried changing the connection protocol to Shared Memory and Named Pipes (making sure they were enabled on the SQL server) and that didn't help either.

How does one connect to a SQL server?

Thanks!
kellino
0

Comments

2 comments

Sort by
  • kellino
    What a blond moment. It's always something simple.

    I used the browser to select the server to connect to. This used the name of the local server, rather than the virtual server on the cluster.

    I manually typed in the virtual server on the cluster, bypassing the browse, and it works fine now.
    kellino
    0
  • HJoyce
    Very pleased you managed to sort it out. I think the fact you found a solution yourself shows a high level of intellegence worthy of being blonde.
    HJoyce
    0

Add comment

Please sign in to leave a comment.