Re: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
From: Scott Ivey (sivey_at_online.nospam)
Date: 11/23/04
- Next message: oj: "Re: upgrade of SQL Server 2000 to SP3"
- Previous message: Tam O'Shanter: "Pivoting Results"
- In reply to: Aaron [SQL Server MVP]: "Re: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied."
- Next in thread: Aaron [SQL Server MVP]: "Re: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied."
- Reply: Aaron [SQL Server MVP]: "Re: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied."
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 23 Nov 2004 13:42:35 -0600
Aaron - sorry for the confusion. You're right, I should have brought that
up sooner (I mentioned it in the 17th post too - but that was still too far
in :). I've developed tunnel vision on this problem... :(
I am the network administrator as well as the DBA - and everything looks
good on the cluster setup. However - I'll be the first to admit that I'm no
Cluster expert. SQL, yes, but clustering, no.
The error still occurs even with the load balancing forcing the full load to
1 Windows2003 server - so a non-responsive server is definitely not the
problem.
My original thought on this was that it might be a cluster problem, so I
opened a paid support incident with MS in the Cluster group, but was told
that it has nothing to do with clustering, and was told to try the SQL
group. At that point, I asked for my credit back on the incident (which was
an SA incident). Maybe that MS support rep put false confidence in my head
about the cluster - if you think that the cluster is the problem, I'm more
than happy to chase that again.
>From my research on google groups - I found plenty of posts pointing to the
same thing - that people had experienced the same problem when moving from
2000 to 2003 on the server. Not once did I see anything about load
balancing being part of the problem - but I also didn't see any solutions.
Maybe everyone else with the problem also failed to mention the WLBS as well
;)
Once again Aaron - I'm sorry if I've either steered you in the wrong
direction and/or wasted your time. I hope that's not the way you feel,
since you are a valuable resource in this newsgroup, and I hope that you
continue your efforts.
Scott
"Aaron [SQL Server MVP]" <ten.xoc@dnartreb.noraa> wrote in message
news:OvksO6Y0EHA.3584@TK2MSFTNGP11.phx.gbl...
>> Edition boxes using Windows Load Balancing
>
> This is the 21st post from you on this issue, at least that I can see in
> my
> history. And this is the FIRST time I've seen load balancing mentioned.
> Why didn't you bring that up before? Is it possible that you might hit
> your
> network administrator up to look at the load balancing and make sure it is
> configured correctly? I have seen situations where load balancing was
> tested etc. blah blah, and it turns out that the load balancer had one
> server in its farm of ten that wasn't active. So initial testing passed,
> because it was very cursory, but then there were sporadic errors when it
> went live. Fortunately, we knew enough to look at the load balancing
> first,
> instead of trying to invent problems in the portions of the application
> that
> hadn't changed. And we also made sure to beef up our testing before
> actually publishing such changes going forward...
>
>
- Next message: oj: "Re: upgrade of SQL Server 2000 to SP3"
- Previous message: Tam O'Shanter: "Pivoting Results"
- In reply to: Aaron [SQL Server MVP]: "Re: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied."
- Next in thread: Aaron [SQL Server MVP]: "Re: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied."
- Reply: Aaron [SQL Server MVP]: "Re: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
