installing an Avaya provided MAS and the mmdct is able to complete past :
add 3rd party software -
MAPI client , Exchange Management 2007 tools ( 32-bit ) , Exchange 2007 Service SP 1 ( 32-bit )
MM software installation
network config
RAS set-up
then reports :
" Unable to set system installation state "
I was able to find a PSN 002468u with regards to the " unable to set system installation state " message.
but this has to do with customer supplied equipment and installing on another drive other then where the Windows is installed , typically the C: drive
which is not the case here - checked mmdct and we are checked off for exchange behind Avaya provided MAS as we should be.
looking at the mmrep.xml I see the following
Detail Value="17:19.21 2009/12/09 : [20%]: Preparing installation - Unable to set system installation state (attempt 1)" />
<Detail Value="17:19.36 2009/12/09 : [20%]: Preparing installation - Unable to set system installation state (attempt 2)" />
<Detail Value="17:19.51 2009/12/09 : [20%]: Preparing installation - Unable to set system installation state (attempt 3)" />
<Detail Value="17:20.06 2009/12/09 : [20%]: Preparing installation - Unable to set system installation state (attempt 4)" />
<Detail Value="17:20.21 2009/12/09 : [20%]: Preparing installation - Unable to set system installation state (attempt 5)
on another known good install be it MM4.0 this is the part where its " adding everyone started ".
Detail Value="10:15.40 2009/04/18 : [20%]: Adding Everyone started" />
<Detail Value="10:15.40 2009/04/18 : [20%]: AddEveryone returned (0x00000000) The operation completed successfully." />
<Detail Value="10:15.40 2009/04/18 : [20%]: Tries = 0" />
<Detail Value="10:15.40 2009/04/18 : [20%]: Adding Everyone completed" />
<Detail Value="10:15.40 2009/04/18 : [30%]: Restarting..." />
<Detail Value="10:15.40 2009/04/18 : [30%]: Start MAS service" />
<Detail Value="10:15.40 2009/04/18 : [30%]: MAS service started" />
<Detail Value="10:15.40 2009/04/18 : [30%]: SetEmailServerType started" />
group , service account & permissions are correct just wondering if anyone else has running into this when installing a MM5.1 behind Exchange 2007 ( running on window server 2008 ).
MAS is Windows Server 2003 R2 SP 2 ( 32-bit )
Peer Exchange - Windows Server 2008 SP 2( 64-bit )
Peer Directory - is Windows Server 2008 SP 2( 62-bit )
MAS reports as 9.0.424.1005 ( MM5.1 )
seeing patches for WSO ,MAS ,ADMIN in about Modular Messaging.
even tried to run the gvconfig as well and it never gets to an open to ask me about my peer directory sits at " this may take several minutes " (waited for 25 or more minutes)
for some reason I recall something about the earlier MM5.1 systems showing as MM5.0 9.0.203.0 in about Modular Messaging and you needed a upgrade MM5.1 ( MM510000.exe )before running the MISCM application as I recall when talking to Avaya a few months back on another issue.
perhaps this the reason the install is failing ?
If so then I would need to reload the MM once again and load the MM5.1 upgrade application - the system then removes the updates while running the MISCM and then loads them back once again while going through the install process ?
cheers !
ayavauser
add 3rd party software -
MAPI client , Exchange Management 2007 tools ( 32-bit ) , Exchange 2007 Service SP 1 ( 32-bit )
MM software installation
network config
RAS set-up
then reports :
" Unable to set system installation state "
I was able to find a PSN 002468u with regards to the " unable to set system installation state " message.
but this has to do with customer supplied equipment and installing on another drive other then where the Windows is installed , typically the C: drive
which is not the case here - checked mmdct and we are checked off for exchange behind Avaya provided MAS as we should be.
looking at the mmrep.xml I see the following
Detail Value="17:19.21 2009/12/09 : [20%]: Preparing installation - Unable to set system installation state (attempt 1)" />
<Detail Value="17:19.36 2009/12/09 : [20%]: Preparing installation - Unable to set system installation state (attempt 2)" />
<Detail Value="17:19.51 2009/12/09 : [20%]: Preparing installation - Unable to set system installation state (attempt 3)" />
<Detail Value="17:20.06 2009/12/09 : [20%]: Preparing installation - Unable to set system installation state (attempt 4)" />
<Detail Value="17:20.21 2009/12/09 : [20%]: Preparing installation - Unable to set system installation state (attempt 5)
on another known good install be it MM4.0 this is the part where its " adding everyone started ".
Detail Value="10:15.40 2009/04/18 : [20%]: Adding Everyone started" />
<Detail Value="10:15.40 2009/04/18 : [20%]: AddEveryone returned (0x00000000) The operation completed successfully." />
<Detail Value="10:15.40 2009/04/18 : [20%]: Tries = 0" />
<Detail Value="10:15.40 2009/04/18 : [20%]: Adding Everyone completed" />
<Detail Value="10:15.40 2009/04/18 : [30%]: Restarting..." />
<Detail Value="10:15.40 2009/04/18 : [30%]: Start MAS service" />
<Detail Value="10:15.40 2009/04/18 : [30%]: MAS service started" />
<Detail Value="10:15.40 2009/04/18 : [30%]: SetEmailServerType started" />
group , service account & permissions are correct just wondering if anyone else has running into this when installing a MM5.1 behind Exchange 2007 ( running on window server 2008 ).
MAS is Windows Server 2003 R2 SP 2 ( 32-bit )
Peer Exchange - Windows Server 2008 SP 2( 64-bit )
Peer Directory - is Windows Server 2008 SP 2( 62-bit )
MAS reports as 9.0.424.1005 ( MM5.1 )
seeing patches for WSO ,MAS ,ADMIN in about Modular Messaging.
even tried to run the gvconfig as well and it never gets to an open to ask me about my peer directory sits at " this may take several minutes " (waited for 25 or more minutes)
for some reason I recall something about the earlier MM5.1 systems showing as MM5.0 9.0.203.0 in about Modular Messaging and you needed a upgrade MM5.1 ( MM510000.exe )before running the MISCM application as I recall when talking to Avaya a few months back on another issue.
perhaps this the reason the install is failing ?
If so then I would need to reload the MM once again and load the MM5.1 upgrade application - the system then removes the updates while running the MISCM and then loads them back once again while going through the install process ?
cheers !
ayavauser