I have a three member ACS Cluster on Windows 2003 Standard Edition.
On the cluster master the SQLAgent$MSAC service is started and working
correctly.  However, on the two member servers the SQLAgent$MSAC
service will not start and generates the following error in the
application event log when attempting to start:

SQLServerAgent could not be started (reason: Unable to connect to
server 'DWDMADWSA143\MSAC'; SQLServerAgent cannot start).

This is causing two problems.  One, without this service running it
appears that the health monitor will not function correctly.  It also
causes hundreds of ACS errors to be written to the Event Log.

If anyone could provide some assistance in getting the service to
start correctly on the member servers it would be much appreciated.
Thanks!

[ Post a follow-up to this message ]

Hi Kevin,

I did found a couple of articles, but they didn't work.
http://support.microsoft.com/defaul...kb;en-us;288621
http://support.microsoft.com/defaul...kb;en-us;288606
http://support.microsoft.com/defaul...us;267934&sd=ee

I'm having the same problem on a two node web test cluster (W2K3 Web Ed/AC2K
SP2).  As well, I cannot connect review the performance becasue we get the
error:  Failed to authenticate, or connect to, SQL Server. (oxc0140060) on
the node that is not running the SQLAgent$MSAC service.

On node1
I'm getting a numbe of App Center/8015 events.
On node2
I'm getting a numbe of App Center/8010 and 8020 events.

I think it's going to take a call PSS to resolve...

"Kevin Acker" wrote:

> I have a three member ACS Cluster on Windows 2003 Standard Edition.
> On the cluster master the SQLAgent$MSAC service is started and working
> correctly.  However, on the two member servers the SQLAgent$MSAC
> service will not start and generates the following error in the
> application event log when attempting to start:
>
> SQLServerAgent could not be started (reason: Unable to connect to
> server 'DWDMADWSA143\MSAC'; SQLServerAgent cannot start).
>
> This is causing two problems.  One, without this service running it
> appears that the health monitor will not function correctly.  It also
> causes hundreds of ACS errors to be written to the Event Log.
>
> If anyone could provide some assistance in getting the service to
> start correctly on the member servers it would be much appreciated.
> Thanks!
>

[ Post a follow-up to this message ]

Hi!
I've exactly the same problem, my problems started when I changed binding
order on my NICs. But even if I change back to the original binding order th
e
problem still exists. I'm not sure if this is a part of the problem. Is ther
e
anyone who had solved this yet?

My Config
2X Windows 2003 Web Ed, App Center 2000 SP2

"troyboy14k" wrote:
[vbcol=seagreen]
> Hi Kevin,
>
> I did found a couple of articles, but they didn't work.
> http://support.microsoft.com/defaul...kb;en-us;288621
> http://support.microsoft.com/defaul...kb;en-us;288606
> http://support.microsoft.com/defaul...us;267934&sd=ee
>
> I'm having the same problem on a two node web test cluster (W2K3 Web Ed/AC
2K
> SP2).  As well, I cannot connect review the performance becasue we get the
> error:  Failed to authenticate, or connect to, SQL Server. (oxc0140060) on
> the node that is not running the SQLAgent$MSAC service.
>
> On node1
> I'm getting a numbe of App Center/8015 events.
> On node2
> I'm getting a numbe of App Center/8010 and 8020 events.
>
> I think it's going to take a call PSS to resolve...
>
> "Kevin Acker" wrote:
> 

[ Post a follow-up to this message ]

I'm calling MS PSS 11/01/04 to get this stupid problem solved.  It is now
affecting two of my production servers.

I've tried...
. ac cluster /clean
. mcutil.exe
from:
http://www.microsoft.com/application
center/community/newsgroups/dgbrowser/en-us/default.mspx?query=Failed+to+aut
henticate+SQL&dg=microsoft.public.applicationcenter.admin&cat=ac&lang=en&cr=
US&pt=&catlist=56C28711-CD9F-4998-BECB-C5D4D86DFBCB&dglist=&ptlist=&exp=&slo
c=en-us

Tried:
. Taking my webtest02 AC2K server offline
. Removed from cluster
. Uninstalled AC2K
. Delete program folders for AC2K and SQL
. Used setup.hta to log setup
. and it's failing with a SQL error.

I also Attempted to remove all AC2K settings, using acremover tool, and
install msisap.exe from windows support tools.  Still didn't work.
---
"Johan S" wrote:
[vbcol=seagreen]
> Hi!
> I've exactly the same problem, my problems started when I changed binding
> order on my NICs. But even if I change back to the original binding order 
the
> problem still exists. I'm not sure if this is a part of the problem. Is th
ere
> anyone who had solved this yet?
>
> My Config
> 2X Windows 2003 Web Ed, App Center 2000 SP2
>
> "troyboy14k" wrote:
> 

[ Post a follow-up to this message ]

If you get an answer from PSS on this I would really appreciate it if
you could post it.  I've turned off the performance monitors, since we
have another tool monitoring performance anyway, and the 8010 errors
have gone away but we still receive a number of ACS errors since the
SQLAgent$MSAC service is not running.  Thanks much!

"troyboy14k" <troyboy14k@discussions.microsoft.com> wrote in message news:<2B3E1186-1A65-442
7-A1AD-6F7483B9957D@microsoft.com>...[vbcol=seagreen]
> I'm calling MS PSS 11/01/04 to get this stupid problem solved.  It is now
> affecting two of my production servers.
>
> I've tried...
> . ac cluster /clean
> . mcutil.exe
> from:
> http://www.microsoft.com/application
> center/community/newsgroups/dgbrowser/en-us/default.mspx?query=Failed+to+a
uthenticate+SQL&dg=microsoft.public.applicationcenter.admin&cat=ac&lang=en&c
r=US&pt=&catlist=56C28711-CD9F-4998-BECB-C5D4D86DFBCB&dglist=&ptlist=&exp=&s
loc=en-us
>
> Tried:
> . Taking my webtest02 AC2K server offline
> . Removed from cluster
> . Uninstalled AC2K
> . Delete program folders for AC2K and SQL
> . Used setup.hta to log setup
> . and it's failing with a SQL error.
>
> I also Attempted to remove all AC2K settings, using acremover tool, and
> install msisap.exe from windows support tools.  Still didn't work.
> ---
> "Johan S" wrote:
> 

[ Post a follow-up to this message ]

We actually started having NLB problems on one of the web systems, and it
hung the cluster due to duplicate IPs.
I've made the decision to just rebuild the two problem servers.

I think the issue has to due with us having to rebuild the first controller
server, and then moving back to it.  We had to fix the IUSR_xxxxx account.  
I
think it is the same issue with ACC_xxxxx account which I think controls SQL
security and access to all servers.  You might pull the server having
problems from the cluster, run ac cluster clean, rename that IUSR and ACC
accounts, and then re-add the on the server to the cluster.

To me, since we have load balancing.  The best solution is to just rebuild,
and re-add the servers to the cluster.  It's less head banging and more time
efficient.


"Kevin Acker" wrote:

> If you get an answer from PSS on this I would really appreciate it if
> you could post it.  I've turned off the performance monitors, since we
> have another tool monitoring performance anyway, and the 8010 errors
> have gone away but we still receive a number of ACS errors since the
> SQLAgent$MSAC service is not running.  Thanks much!
>
> "troyboy14k" <troyboy14k@discussions.microsoft.com> wrote in message news:
<2B3E1186-1A65-4427-A1AD-6F7483B9957D@microsoft.com>... 
>

[ Post a follow-up to this message ]