Application Center Administration

Author

SQLAgent$MSAC error

Rich Raffenetti

2005-05-29, 2:47 am

I have a new two-member AC2000 cluster with Windows Server 2003, SP1 and SP2
for AC2K. I applied the 891330 post installation fixes.

I had the cluster working with a back-end network on a hub. The cluster is
hardware load-balanced. I replaced the hub with a VLAN on a switch and
different IP numbers than the hub.

The cluster showed some instability so I decided to disband and rebuild it.
I formed the cluster on the A node and then had trouble bringing the B node
into the cluster. This happened several times. There was a SQLAgent$MSAC
error.

I decided to build the cluster on the B node instead and the B node failed
to build a cluster. The error again was the SQLAgent$MSAC error (see
below).

Has anyone seen and fixed this problem? Little is available on this
problem. I am tempted to uninstall and reinstall AC2K on the B node. It
seems like something in the SQLAgent is corrupted and there is no
description of ways to clear the problem.

The wizard error is "Failed to authenticate, or connect to, SQL Server.
(0xc0140060)"

The corresponding event log message is:

Event Type: Error
Event Source: SQLAgent$MSAC
Event Category: Service Control
Event ID: 103
Date: 5/28/2005
Time: 9:45:27 PM
User: N/A
Computer: GRWSCB
Description:
SQLServerAgent could not be started (reason: Unable to connect to server
'GRWSCB\MSAC'; SQLServerAgent cannot start).

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Comejato

2005-08-25, 6:02 pm

Rich,
did you resolve this issue?
It's a change in the password of "sa".

"Rich Raffenetti" wrote:

> I have a new two-member AC2000 cluster with Windows Server 2003, SP1 and SP2
> for AC2K. I applied the 891330 post installation fixes.
>
> I had the cluster working with a back-end network on a hub. The cluster is
> hardware load-balanced. I replaced the hub with a VLAN on a switch and
> different IP numbers than the hub.
>
> The cluster showed some instability so I decided to disband and rebuild it.
> I formed the cluster on the A node and then had trouble bringing the B node
> into the cluster. This happened several times. There was a SQLAgent$MSAC
> error.
>
> I decided to build the cluster on the B node instead and the B node failed
> to build a cluster. The error again was the SQLAgent$MSAC error (see
> below).
>
> Has anyone seen and fixed this problem? Little is available on this
> problem. I am tempted to uninstall and reinstall AC2K on the B node. It
> seems like something in the SQLAgent is corrupted and there is no
> description of ways to clear the problem.
>
> The wizard error is "Failed to authenticate, or connect to, SQL Server.
> (0xc0140060)"
>
> The corresponding event log message is:
>
> Event Type: Error
> Event Source: SQLAgent$MSAC
> Event Category: Service Control
> Event ID: 103
> Date: 5/28/2005
> Time: 9:45:27 PM
> User: N/A
> Computer: GRWSCB
> Description:
> SQLServerAgent could not be started (reason: Unable to connect to server
> 'GRWSCB\MSAC'; SQLServerAgent cannot start).
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
>
>

George Cheng [MSFT]

2005-08-30, 8:48 pm

Try the following

1. Add the following Registry key:
HKLM\SOFTWARE\Microsoft\Microsoft SQL
Server\MSAC\MSSQLServer\SuperSocketNetLi
b
Certificate = 0 (REG_SZ )
2. Stop, and then start the SQL Server service.

Thank You

George Cheng

Application Center2000/Index Server/Commerce Server Support

Application Center 2000 SP2 and Windows 2003 SP1
891330 You may experience problems after you install Windows Server 2003
Service Pack 1 on a server that is running Application Center 2000

http://support.microsoft.com/?id=891330

Note: This article has no warranties implicit or explicit.
All the content is given on the "as is" basis and the user
takes full responsibility for its use and assumption.
Microsoft Corporation Copyright 2004
All Rights Reserved

--------------------
| Thread-Topic: SQLAgent$MSAC error
| thread-index: AcWpvyicI7gFNrbDR3Sr6rclNBVUFw==
| X-WBNR-Posting-Host: 200.61.45.156
| From: "=?Utf-8?B?Q29tZWphdG8=?=" <Comejato@discussions.microsoft.com>
| References: <eAjY9aAZFHA.3164@TK2MSFTNGP09.phx.gbl>
| Subject: RE: SQLAgent$MSAC error
| Date: Thu, 25 Aug 2005 14:51:33 -0700
| Lines: 50
| Message-ID: <90C4A450-D4C2-4DAF-BF70-2AFAE17C0671@microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.applicationcenter.admin
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.applicationcenter.admin:1162
| X-Tomcat-NG: microsoft.public.applicationcenter.admin
|
| Rich,
| did you resolve this issue?
| It's a change in the password of "sa".
|
|
| "Rich Raffenetti" wrote:
|
| > I have a new two-member AC2000 cluster with Windows Server 2003, SP1
and SP2
| > for AC2K. I applied the 891330 post installation fixes.
| >
| > I had the cluster working with a back-end network on a hub. The
cluster is
| > hardware load-balanced. I replaced the hub with a VLAN on a switch and
| > different IP numbers than the hub.
| >
| > The cluster showed some instability so I decided to disband and rebuild
it.
| > I formed the cluster on the A node and then had trouble bringing the B
node
| > into the cluster. This happened several times. There was a
SQLAgent$MSAC
| > error.
| >
| > I decided to build the cluster on the B node instead and the B node
failed
| > to build a cluster. The error again was the SQLAgent$MSAC error (see
| > below).
| >
| > Has anyone seen and fixed this problem? Little is available on this
| > problem. I am tempted to uninstall and reinstall AC2K on the B node.
It
| > seems like something in the SQLAgent is corrupted and there is no
| > description of ways to clear the problem.
| >
| > The wizard error is "Failed to authenticate, or connect to, SQL Server.
| > (0xc0140060)"
| >
| > The corresponding event log message is:
| >
| > Event Type: Error
| > Event Source: SQLAgent$MSAC
| > Event Category: Service Control
| > Event ID: 103
| > Date: 5/28/2005
| > Time: 9:45:27 PM
| > User: N/A
| > Computer: GRWSCB
| > Description:
| > SQLServerAgent could not be started (reason: Unable to connect to
server
| > 'GRWSCB\MSAC'; SQLServerAgent cannot start).
| >
| > For more information, see Help and Support Center at
| > http://go.microsoft.com/fwlink/events.asp.
| >
| >
| >
|