Re: SA not starting on Cluster
- From: BrYan <BrYan@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 27 Apr 2006 05:59:02 -0700
Scott,
I ran step 1 and this came back...
wamusername : (STRING) "IWAM_PDNXBEX03"
The server was renamed to PNXBEXCH01 before exchange or cluster was set up
but IIS was already on. PDNXBEX03 was the old server name. Could this be
causing the problem?
"Scott Schnoll [MSFT]" wrote:
Has the node's role recently changed from a domain controller to a member.
server or vice versa?
One other thing to check is the IWAM account. To do this:
1- Check the account configured in the metabase
Open a command prompt
Go to c:\inetpub\adminscript
Run: cscript adsutil.vbs get w3svc/wamusername
2- Verify this account exists either in the local SAM if it is a member or
in the Active Directory if it is a domain controller
3- If the account does not exist, create it and set its password. Make sure
to check "The password never expires"
4- Backup IIS metabase as described in "302573 HOW TO: Back Up and Restore
IIS"
5- Set the account name in the metabase From the command prompt run:
cscript adsutil.vbs set w3svc/wamusername "IWAM_account" (replace account
with the actual name).
6- Set the password in the metabase if you have changed it. From the
command prompt run: cscript adsutil.vbs set w3svc/WAMUserPass Password (The
password is the one you set in step 3)
7- Verify the IWAM account is correctly set: cscript adsutil.vbs get
w3svc/wamusername
8- Synchronise IWAM "cscript synciwam.vbs -v" and check the output for any
errors
9- Restart IIS Admin service
10- Start the Exchange services
Post back here if this does not resolve the problem for you.
--
Scott Schnoll
This posting is provided "AS IS" with no warranties, and confers no
rights. Please do not send email directly to this alias. This alias is for
newsgroup
purposes only.
"BrYan" <BrYan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:310A6CC7-31ED-4610-AC59-3F835733D274@xxxxxxxxxxxxxxxx
Receiving this error when trying to bring an Exchange 2003 cluster online
for
the first time...
One of the System Attendant's task is blocked.
Function: ScStartVM
Server is completely patched with all updates and verified the ASP.NET
version as described in article 906154 is correct.
- Follow-Ups:
- Re: SA not starting on Cluster
- From: BrYan
- Re: SA not starting on Cluster
- References:
- Re: SA not starting on Cluster
- From: Scott Schnoll [MSFT]
- Re: SA not starting on Cluster
- Prev by Date: Re: Outlook unable to connect to exchange, entourage can
- Next by Date: Re: SA not starting on Cluster
- Previous by thread: Re: SA not starting on Cluster
- Next by thread: Re: SA not starting on Cluster
- Index(es):
Relevant Pages
|