J
Joshua Andrews
We have an IIS setup that is exhibiting some odd behavior.
We have both asp.net and regular asp applications running on a single
box. They point to a SQL Server 2000 cluster. When the cluster fails
over, we'll see circumstances where the asp applications connect
seamlessly to the new cluster node, but the asp.net applications report
that they can't find the cluster node.
If both types of applications were failing to access the cluster, it
would probably be a networking or machine issue, but in this case I
can't tell why ASP.Net would fail, but asp would work?
Any suggestions?
Setup:
W2K3 Server Enterprise Edition
NLB IIS Webserver cluster (2 servers)
SQL Server 2000 SP 3 Enterprise 2-Node Cluster (on W2K3 Enterprise as well).
Thanks,
Josh
We have both asp.net and regular asp applications running on a single
box. They point to a SQL Server 2000 cluster. When the cluster fails
over, we'll see circumstances where the asp applications connect
seamlessly to the new cluster node, but the asp.net applications report
that they can't find the cluster node.
If both types of applications were failing to access the cluster, it
would probably be a networking or machine issue, but in this case I
can't tell why ASP.Net would fail, but asp would work?
Any suggestions?
Setup:
W2K3 Server Enterprise Edition
NLB IIS Webserver cluster (2 servers)
SQL Server 2000 SP 3 Enterprise 2-Node Cluster (on W2K3 Enterprise as well).
Thanks,
Josh