July 8, 2009 at 5:33 am
So I've been using remote perfmon for years across my database environment (but write directly into a SQL DB and use our monitoring page to aggregate and average out readings over a minute for live perfmon stats), but since I upgraded (in-place) all my clusters to SQL 2008 from SQL 2005 (still on WIndows 2003) I can no longer connect to any of the cluster names via perfmon from my remote perfmon box. I just instantly get the error "Unable to Connect to Machine".
I can connect to the host names but that's not gonna work as I need the virtual names.
All SQL 2008 instances on single boxes work fine, even ones with Windows Server 2008.
Any ideas?
July 8, 2009 at 7:32 pm
I would check the SQL cluster name resource. When I did a sql 2008 clustered install, it created the sql network name with kerberos authentication enabled. I'm not sure what the behavior is for upgrades, but if SQL is up and running, then I doubt it's this. The SQL network name would not come online until there was a computer object with the sql virtual name created in AD, in my case.
I would also try using the cluster name instead of the sql clustered virtual name to get at the counters. My guess is that something happened with the sql virtual name and how it maps or is accessed externally.
Hope that helps,
Steve
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply