Microsoft Exchange 2007 SP3 failed to install

• 2012년 5월 8일 화요일 오전 6:01

   

   
  

  0

  Hi There,

  I'm performing migration for my company, current environment Exchange2k with window2k AD, 

  i already done the AD migration from win2k to win2k3, while trying to install exchange 2007, it always failed at hub transport roles,

  with the message  "Service 'MSExchangeTransport' failed to reach status 'Running' on this server"

  i already tried every solution to fix, included enable the IPV6.

  Then i run dcdiag on 3DC, there are errors out there, in sysvol and netlogon.

  ***There are one member server with exchange 2000

  ISTD1C - win2k (previosly there have 2 win2k DC, another one already decommission)

  Starting test: frssysvol
           Error: No record of File Replication System, SYSVOL started.
           The Active Directory may be prevented from starting.
           ......................... ISTD1C passed test frssysvol
        Starting test: kccevent
           ......................... ISTD1C passed test kccevent
        Starting test: systemlog
           An Error Event occured.  EventID: 0x0000165B
              Time Generated: 05/08/2012   10:56:45
              (Event String could not be retrieved)
           An Error Event occured.  EventID: 0x0000169E
              Time Generated: 05/08/2012   11:14:39
              (Event String could not be retrieved)
           An Error Event occured.  EventID: 0x00000457
              Time Generated: 05/08/2012   11:34:43
              Event String: Driver
           An Error Event occured.  EventID: 0x00000452
              Time Generated: 05/08/2012   11:34:43
              Event String: The printer could not be installed.
           ......................... ISTD1C failed test systemlog

  -----------------------------------------------------

  win2k3b

  Starting test: NetLogons
           Unable to connect to the NETLOGON share! (\\WIN2K3B\netlogon)
           [WIN2K3B] An net use or LsaPolicy operation failed with error 1203, No
  network provider accepted the given network path..
           ......................... WIN2K3B failed test NetLogons

   Starting test: systemlog
           An Error Event occured.  EventID: 0x00000457
              Time Generated: 05/08/2012   11:32:38
              (Event String could not be retrieved)
           ......................... WIN2K3B failed test systemlog
        Starting test: VerifyReferences
           ......................... WIN2K3B passed test VerifyReferences
  

  ---------------------------------------------

  win2k3a

      Starting test: NetLogons
           Unable to connect to the NETLOGON share! (\\WIN2K3A\netlogon)
           [WIN2K3A] An net use or LsaPolicy operation failed with error 1203, No
  network provider accepted the given network path..
           ......................... WIN2K3A failed test NetLogons
        Starting test: Advertising
           Warning: DsGetDcName returned information for \\istd1c.modenas.com.my,
  when we were trying to reach WIN2K3A.
           Server is not responding or is not considered suitable.
           ......................... WIN2K3A failed test Advertising

     ......................... WIN2K3A passed test kccevent
        Starting test: systemlog
           An Error Event occured.  EventID: 0x40000004
              Time Generated: 05/08/2012   10:55:23
              Event String: The kerberos client received a
           An Error Event occured.  EventID: 0xC0000033
              Time Generated: 05/08/2012   10:56:26
              (Event String could not be retrieved)
           An Error Event occured.  EventID: 0x40000005
              Time Generated: 05/08/2012   10:57:13
              Event String: The kerberos client received a KRB_AP_ERR_TKT_NYV
           An Error Event occured.  EventID: 0xC0000033
              Time Generated: 05/08/2012   10:58:19
              (Event String could not be retrieved)
           An Error Event occured.  EventID: 0xC0000033
              Time Generated: 05/08/2012   10:58:20
              (Event String could not be retrieved)
           An Error Event occured.  EventID: 0xC0000033
              Time Generated: 05/08/2012   10:58:21
              (Event String could not be retrieved)
           An Error Event occured.  EventID: 0xC0000033
              Time Generated: 05/08/2012   10:58:23
              (Event String could not be retrieved)
           An Error Event occured.  EventID: 0xC0000033
              Time Generated: 05/08/2012   10:59:07
              (Event String could not be retrieved)
           An Error Event occured.  EventID: 0xC0000033
              Time Generated: 05/08/2012   10:59:43
              (Event String could not be retrieved)
           An Error Event occured.  EventID: 0xC0000033
              Time Generated: 05/08/2012   10:59:44
              (Event String could not be retrieved)
           An Error Event occured.  EventID: 0xC0000033
              Time Generated: 05/08/2012   11:00:16
              (Event String could not be retrieved)
           An Error Event occured.  EventID: 0x40000005
              Time Generated: 05/08/2012   11:01:43
              Event String: The kerberos client received a KRB_AP_ERR_TKT_NYV
           An Error Event occured.  EventID: 0xC0000033
              Time Generated: 05/08/2012   11:02:32
              (Event String could not be retrieved)
           An Error Event occured.  EventID: 0xC0000033
              Time Generated: 05/08/2012   11:02:33
              (Event String could not be retrieved)
           An Error Event occured.  EventID: 0xC0000033
              Time Generated: 05/08/2012   11:03:05
              (Event String could not be retrieved)
           An Error Event occured.  EventID: 0xC0000033
              Time Generated: 05/08/2012   11:03:06
              (Event String could not be retrieved)
           An Error Event occured.  EventID: 0x40000005
              Time Generated: 05/08/2012   11:03:58
              Event String: The kerberos client received a KRB_AP_ERR_TKT_NYV
           An Error Event occured.  EventID: 0x00000457
              Time Generated: 05/08/2012   11:25:42
              (Event String could not be retrieved)
           An Error Event occured.  EventID: 0x00000457
              Time Generated: 05/08/2012   11:28:50
              (Event String could not be retrieved)
           ......................... WIN2K3A failed test systemlog

  -------------------------------------------------------------------------

  event log on replication at win2k - istd1c

         

  The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME

  (SYSVOL SHARE)" is in JRNL_WRAP_ERROR. 
  
   Replica set name is    : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" 
   Replica root path is   : "c:\winnt\sysvol\domain" 
   Replica root volume is : "\\.\C:" 
   A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found.  This can occur because of one of the following reasons. 
  
   [1] Volume "\\.\C:" has been formatted. 
   [2] The NTFS USN journal on volume "\\.\C:" has been deleted. 
   [3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal. 
   [4] File Replication Service was not running on this computer for a long time. 
   [5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\C:". 
   Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state. 
   [1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service. 
   [2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set. 
  
  WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again. 
  
  To change this registry parameter, run regedit. 
  
  Click on Start, Run and type regedit. 
  
  Expand HKEY_LOCAL_MACHINE. 
  Click down the key path: 
     "System\CurrentControlSet\Services\NtFrs\Parameters" 
  Double click on the value name 
     "Enable Journal Wrap Automatic Restore" 
  and update the value. 
  
  If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above. 

  -------------------------------------------------------------------------------------

  Is this one of the reason that cause exchange 2007 failed to install MStransport roles? 

   
  

  ---

  Alfred

  • 응답
  • 인용