Clustered System Attendant does not start
Exchange Server Forum Index Exchange Server
Discussion forums for Microsoft Exchange Server users.
Microsoft Outlook
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web ExchangeServerHelp.com
Clustered System Attendant does not start

 
Post new topic   Reply to topic    Exchange Server Forum Index -> Connectivity
Author Message
BillB
Guest





Posted: Thu Dec 23, 2004 10:00 am    Post subject: Clustered System Attendant does not start Reply with quote

Had issue with time on my network
When time was corrected and cluster was moved from ne node to other it does
not work

The first error in the applog is

Event Type: Error
Event Source: MSExchangeMU
Event Category: General
Event ID: 1047
Date: 12/22/2004
Time: 10:51:47 PM
User: N/A
Computer: Serverx
Description:
Metabase Update failed to properly initialize its context. It will retry
initialization every 60 seconds until succeeds or shutdown is requested.

Any ideas would be greatly appreciated
BillB

Back to top
Gerald Aigenbauer
Guest





Posted: Thu Dec 23, 2004 3:35 pm    Post subject: Re: Clustered System Attendant does not start Reply with quote

hi!

here is a hint for the asonet security account that cannot be accessed....

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

gerald aigenbauer.

"BillB" <user@abc.def> schrieb im Newsbeitrag
news:eopTEQK6EHA.2568@TK2MSFTNGP10.phx.gbl...
Quote:
Had issue with time on my network
When time was corrected and cluster was moved from ne node to other it
does not work

The first error in the applog is

Event Type: Error
Event Source: MSExchangeMU
Event Category: General
Event ID: 1047
Date: 12/22/2004
Time: 10:51:47 PM
User: N/A
Computer: Serverx
Description:
Metabase Update failed to properly initialize its context. It will retry
initialization every 60 seconds until succeeds or shutdown is requested.

Any ideas would be greatly appreciated
BillB
Back to top
BillB
Guest





Posted: Fri Dec 24, 2004 1:45 am    Post subject: Re: Clustered System Attendant does not start Reply with quote

This Cluster has 2 member servers none have been promoted or demoted to a
2003 DC
I found this article yesterday any other insights

Thx in advance,
BillB



"Gerald Aigenbauer" <ga@ntc.at> wrote in message
news:uwegCLN6EHA.3076@TK2MSFTNGP15.phx.gbl...
Quote:
hi!

here is a hint for the asonet security account that cannot be accessed....

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

gerald aigenbauer.

"BillB" <user@abc.def> schrieb im Newsbeitrag
news:eopTEQK6EHA.2568@TK2MSFTNGP10.phx.gbl...
Had issue with time on my network
When time was corrected and cluster was moved from ne node to other it
does not work

The first error in the applog is

Event Type: Error
Event Source: MSExchangeMU
Event Category: General
Event ID: 1047
Date: 12/22/2004
Time: 10:51:47 PM
User: N/A
Computer: Serverx
Description:
Metabase Update failed to properly initialize its context. It will retry
initialization every 60 seconds until succeeds or shutdown is requested.

Any ideas would be greatly appreciated
BillB




Back to top
Gerald Aigenbauer
Guest





Posted: Fri Dec 24, 2004 3:05 pm    Post subject: Re: Clustered System Attendant does not start Reply with quote

hi billb!

the time on the dc´s is correct?

i would try to deinstall and install asp.net on the cluster nodes

if this is still not the solution, you can delete the ds2mb in the
metabase... look there
http://support.microsoft.com/?kbid=883380

gerald aigenbauer.

"BillB" <user@abc.def> schrieb im Newsbeitrag
news:%23AYEufS6EHA.2452@TK2MSFTNGP14.phx.gbl...
Quote:
This Cluster has 2 member servers none have been promoted or demoted to a
2003 DC
I found this article yesterday any other insights

Thx in advance,
BillB



"Gerald Aigenbauer" <ga@ntc.at> wrote in message
news:uwegCLN6EHA.3076@TK2MSFTNGP15.phx.gbl...
hi!

here is a hint for the asonet security account that cannot be
accessed....

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

gerald aigenbauer.

"BillB" <user@abc.def> schrieb im Newsbeitrag
news:eopTEQK6EHA.2568@TK2MSFTNGP10.phx.gbl...
Had issue with time on my network
When time was corrected and cluster was moved from ne node to other it
does not work

The first error in the applog is

Event Type: Error
Event Source: MSExchangeMU
Event Category: General
Event ID: 1047
Date: 12/22/2004
Time: 10:51:47 PM
User: N/A
Computer: Serverx
Description:
Metabase Update failed to properly initialize its context. It will retry
initialization every 60 seconds until succeeds or shutdown is requested.

Any ideas would be greatly appreciated
BillB




Back to top
BillB
Guest





Posted: Wed Dec 29, 2004 8:56 pm    Post subject: Re: Clustered System Attendant does not start Reply with quote

Gerald,
Followed 883380
The virtual directories were not re-created as the system attendant fails to
start. Is there an exchange log that would give more info on while this is
failing other than the event viewer??

Thanks,
BillB


"Gerald Aigenbauer" <ga@ntc.at> wrote in message
news:en1WJfZ6EHA.540@TK2MSFTNGP12.phx.gbl...
Quote:
hi billb!

the time on the dc´s is correct?

i would try to deinstall and install asp.net on the cluster nodes

if this is still not the solution, you can delete the ds2mb in the
metabase... look there
http://support.microsoft.com/?kbid=883380

gerald aigenbauer.

"BillB" <user@abc.def> schrieb im Newsbeitrag
news:%23AYEufS6EHA.2452@TK2MSFTNGP14.phx.gbl...
This Cluster has 2 member servers none have been promoted or demoted to a
2003 DC
I found this article yesterday any other insights

Thx in advance,
BillB



"Gerald Aigenbauer" <ga@ntc.at> wrote in message
news:uwegCLN6EHA.3076@TK2MSFTNGP15.phx.gbl...
hi!

here is a hint for the asonet security account that cannot be
accessed....

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

gerald aigenbauer.

"BillB" <user@abc.def> schrieb im Newsbeitrag
news:eopTEQK6EHA.2568@TK2MSFTNGP10.phx.gbl...
Had issue with time on my network
When time was corrected and cluster was moved from ne node to other it
does not work

The first error in the applog is

Event Type: Error
Event Source: MSExchangeMU
Event Category: General
Event ID: 1047
Date: 12/22/2004
Time: 10:51:47 PM
User: N/A
Computer: Serverx
Description:
Metabase Update failed to properly initialize its context. It will
retry initialization every 60 seconds until succeeds or shutdown is
requested.

Any ideas would be greatly appreciated
BillB






Back to top
Scott Schnoll [MSFT]
Guest





Posted: Wed Dec 29, 2004 11:07 pm    Post subject: Re: Clustered System Attendant does not start Reply with quote

Is this a new Exchange Virtual Server, or one that has been used by users
before? What is the current status right now? Does the SA still fail to
start? If so, what errors are generated in the event logs and in the
cluster.log file? If you're still just experiencing the MSExchangeMU error,
it could indicate an error in the registry. To check for this:

1. Open regedit.exe.
2. Navigate to the HKLM\SOFTWARE\Microsoft\ASP.NET.
3. Verify the value of the RootVer key, edit it as needed. When editing,
verify that the new value matches an existing key under:
HKLM\SOFTWARE\Microsoft\ASP.NET

For example, if RootVer is 1.1.4322.0 then there should a key named
HKLM\SOFTWARE\Microsoft\ASP.NET\1.1.4322.0

Another resolution is to run ASPNET_REGIIS.EXE -I from the
\Windows\Microsoft.Net\Framework\v1.1.4322\ folder to re-register the proper
values.

Post back here if this does not help.
--
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.


"BillB" <user@abc.def> wrote in message
news:%23704Lab7EHA.2788@TK2MSFTNGP15.phx.gbl...
Quote:
Gerald,
Followed 883380
The virtual directories were not re-created as the system attendant fails
to start. Is there an exchange log that would give more info on while this
is failing other than the event viewer??

Thanks,
BillB


"Gerald Aigenbauer" <ga@ntc.at> wrote in message
news:en1WJfZ6EHA.540@TK2MSFTNGP12.phx.gbl...
hi billb!

the time on the dc´s is correct?

i would try to deinstall and install asp.net on the cluster nodes

if this is still not the solution, you can delete the ds2mb in the
metabase... look there
http://support.microsoft.com/?kbid=883380

gerald aigenbauer.

"BillB" <user@abc.def> schrieb im Newsbeitrag
news:%23AYEufS6EHA.2452@TK2MSFTNGP14.phx.gbl...
This Cluster has 2 member servers none have been promoted or demoted to
a 2003 DC
I found this article yesterday any other insights

Thx in advance,
BillB



"Gerald Aigenbauer" <ga@ntc.at> wrote in message
news:uwegCLN6EHA.3076@TK2MSFTNGP15.phx.gbl...
hi!

here is a hint for the asonet security account that cannot be
accessed....

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

gerald aigenbauer.

"BillB" <user@abc.def> schrieb im Newsbeitrag
news:eopTEQK6EHA.2568@TK2MSFTNGP10.phx.gbl...
Had issue with time on my network
When time was corrected and cluster was moved from ne node to other it
does not work

The first error in the applog is

Event Type: Error
Event Source: MSExchangeMU
Event Category: General
Event ID: 1047
Date: 12/22/2004
Time: 10:51:47 PM
User: N/A
Computer: Serverx
Description:
Metabase Update failed to properly initialize its context. It will
retry initialization every 60 seconds until succeeds or shutdown is
requested.

Any ideas would be greatly appreciated
BillB








Back to top
Scott Schnoll [MSFT]
Guest





Posted: Thu Dec 30, 2004 1:09 am    Post subject: Re: Clustered System Attendant does not start Reply with quote

This looks like either it is a replication problem, or that one or more
objects are missing from AD. Since this is a test system, I would remove
Exchange, get the cluster part up and running, and then reinstall Exchange.
Post back here if you have any questions about this.
--
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.


"BillB" <user@abc.def> wrote in message
news:%23Jy20Yd7EHA.3076@TK2MSFTNGP15.phx.gbl...
Quote:
Used (but in test mode)
Currently: not accessible front end or back end server can not start
System Attendant
Attached is a .txt with event log errors
RootVer and Key under are 1.1.4322.0

Cluster Log has a lot of info to look thru is there a specific phrase to
look for (i.e. error or failed)?

Thanks for your help in advance
BillB

"Scott Schnoll [MSFT]" <scschnol@online.microsoft.com> wrote in message
news:umWhkjc7EHA.1296@TK2MSFTNGP10.phx.gbl...
Is this a new Exchange Virtual Server, or one that has been used by users
before? What is the current status right now? Does the SA still fail to
start? If so, what errors are generated in the event logs and in the
cluster.log file? If you're still just experiencing the MSExchangeMU
error,
it could indicate an error in the registry. To check for this:

1. Open regedit.exe.
2. Navigate to the HKLM\SOFTWARE\Microsoft\ASP.NET.
3. Verify the value of the RootVer key, edit it as needed. When
editing,
verify that the new value matches an existing key under:
HKLM\SOFTWARE\Microsoft\ASP.NET

For example, if RootVer is 1.1.4322.0 then there should a key
named
HKLM\SOFTWARE\Microsoft\ASP.NET\1.1.4322.0

Another resolution is to run ASPNET_REGIIS.EXE -I from the
\Windows\Microsoft.Net\Framework\v1.1.4322\ folder to re-register the
proper
values.

Post back here if this does not help.
--
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.


"BillB" <user@abc.def> wrote in message
news:%23704Lab7EHA.2788@TK2MSFTNGP15.phx.gbl...
Gerald,
Followed 883380
The virtual directories were not re-created as the system attendant
fails
to start. Is there an exchange log that would give more info on while
this
is failing other than the event viewer??

Thanks,
BillB


"Gerald Aigenbauer" <ga@ntc.at> wrote in message
news:en1WJfZ6EHA.540@TK2MSFTNGP12.phx.gbl...
hi billb!

the time on the dc´s is correct?

i would try to deinstall and install asp.net on the cluster nodes

if this is still not the solution, you can delete the ds2mb in the
metabase... look there
http://support.microsoft.com/?kbid=883380

gerald aigenbauer.

"BillB" <user@abc.def> schrieb im Newsbeitrag
news:%23AYEufS6EHA.2452@TK2MSFTNGP14.phx.gbl...
This Cluster has 2 member servers none have been promoted or demoted
to
a 2003 DC
I found this article yesterday any other insights

Thx in advance,
BillB



"Gerald Aigenbauer" <ga@ntc.at> wrote in message
news:uwegCLN6EHA.3076@TK2MSFTNGP15.phx.gbl...
hi!

here is a hint for the asonet security account that cannot be
accessed....

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

gerald aigenbauer.

"BillB" <user@abc.def> schrieb im Newsbeitrag
news:eopTEQK6EHA.2568@TK2MSFTNGP10.phx.gbl...
Had issue with time on my network
When time was corrected and cluster was moved from ne node to other
it
does not work

The first error in the applog is

Event Type: Error
Event Source: MSExchangeMU
Event Category: General
Event ID: 1047
Date: 12/22/2004
Time: 10:51:47 PM
User: N/A
Computer: Serverx
Description:
Metabase Update failed to properly initialize its context. It will
retry initialization every 60 seconds until succeeds or shutdown is
requested.

Any ideas would be greatly appreciated
BillB













Back to top
Redrocker
Guest





Posted: Sat Jan 08, 2005 4:53 am    Post subject: Re: Clustered System Attendant does not start Reply with quote

I have had this exact same problem where the system attendent will not start
after applying Exch03 SP1. The upgrade from Ex2k to Ex03 base went fine. I
checked that asp.net rootver key and on node A there was a mismatch. Running
the utility fixed that and then all resources came online. I checked the B
node before the SP1 install and the asp.net values matched. After the SP1
install the asp.net values still matched. This is a very strange problem
none the less.

"Scott Schnoll [MSFT]" wrote:

Quote:
This looks like either it is a replication problem, or that one or more
objects are missing from AD. Since this is a test system, I would remove
Exchange, get the cluster part up and running, and then reinstall Exchange.
Post back here if you have any questions about this.
--
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.


"BillB" <user@abc.def> wrote in message
news:%23Jy20Yd7EHA.3076@TK2MSFTNGP15.phx.gbl...
Used (but in test mode)
Currently: not accessible front end or back end server can not start
System Attendant
Attached is a .txt with event log errors
RootVer and Key under are 1.1.4322.0

Cluster Log has a lot of info to look thru is there a specific phrase to
look for (i.e. error or failed)?

Thanks for your help in advance
BillB

"Scott Schnoll [MSFT]" <scschnol@online.microsoft.com> wrote in message
news:umWhkjc7EHA.1296@TK2MSFTNGP10.phx.gbl...
Is this a new Exchange Virtual Server, or one that has been used by users
before? What is the current status right now? Does the SA still fail to
start? If so, what errors are generated in the event logs and in the
cluster.log file? If you're still just experiencing the MSExchangeMU
error,
it could indicate an error in the registry. To check for this:

1. Open regedit.exe.
2. Navigate to the HKLM\SOFTWARE\Microsoft\ASP.NET.
3. Verify the value of the RootVer key, edit it as needed. When
editing,
verify that the new value matches an existing key under:
HKLM\SOFTWARE\Microsoft\ASP.NET

For example, if RootVer is 1.1.4322.0 then there should a key
named
HKLM\SOFTWARE\Microsoft\ASP.NET\1.1.4322.0

Another resolution is to run ASPNET_REGIIS.EXE -I from the
\Windows\Microsoft.Net\Framework\v1.1.4322\ folder to re-register the
proper
values.

Post back here if this does not help.
--
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.


"BillB" <user@abc.def> wrote in message
news:%23704Lab7EHA.2788@TK2MSFTNGP15.phx.gbl...
Gerald,
Followed 883380
The virtual directories were not re-created as the system attendant
fails
to start. Is there an exchange log that would give more info on while
this
is failing other than the event viewer??

Thanks,
BillB


"Gerald Aigenbauer" <ga@ntc.at> wrote in message
news:en1WJfZ6EHA.540@TK2MSFTNGP12.phx.gbl...
hi billb!

the time on the dc´s is correct?

i would try to deinstall and install asp.net on the cluster nodes

if this is still not the solution, you can delete the ds2mb in the
metabase... look there
http://support.microsoft.com/?kbid=883380

gerald aigenbauer.

"BillB" <user@abc.def> schrieb im Newsbeitrag
news:%23AYEufS6EHA.2452@TK2MSFTNGP14.phx.gbl...
This Cluster has 2 member servers none have been promoted or demoted
to
a 2003 DC
I found this article yesterday any other insights

Thx in advance,
BillB



"Gerald Aigenbauer" <ga@ntc.at> wrote in message
news:uwegCLN6EHA.3076@TK2MSFTNGP15.phx.gbl...
hi!

here is a hint for the asonet security account that cannot be
accessed....

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

gerald aigenbauer.

"BillB" <user@abc.def> schrieb im Newsbeitrag
news:eopTEQK6EHA.2568@TK2MSFTNGP10.phx.gbl...
Had issue with time on my network
When time was corrected and cluster was moved from ne node to other
it
does not work

The first error in the applog is

Event Type: Error
Event Source: MSExchangeMU
Event Category: General
Event ID: 1047
Date: 12/22/2004
Time: 10:51:47 PM
User: N/A
Computer: Serverx
Description:
Metabase Update failed to properly initialize its context. It will
retry initialization every 60 seconds until succeeds or shutdown is
requested.

Any ideas would be greatly appreciated
BillB
















Back to top
 
Post new topic   Reply to topic    Exchange Server Forum Index -> Connectivity All times are GMT
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




Windows Server Dedicated Servers
Contact Us
New Topics Powered by phpBB