Exchange Server 2010 SP3 Hub transport role hata 1605

Merhaba,

SP3 güncellemesi yüklü olabilir mi  kontrol edebilir misin? Get-ExchangeServer | Format-List Name, Edition, AdminDisplayVersion komutunu Exchange PowerShell den çalıştırarak Build Numberı paylaşırmısın?

 

İsmail bey merhaba , 

Öncelikle konu ile ilgilendiğiniz için teşekkür ederim.

Powershell i açtığımda

VERBOSE: Connecting to 

Connecting to remote server failed with the following error message : The WinRM client cannot process the request.

e about_Remote_Troubleshooting Help topic.

    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportException 

+ FullyQualifiedErrorId : PSSessionOpenFailed 

 Failed to connect to an Exchange server in the current site.

Enter the server FQDN where you want to connect.:

 Hatası görüntüleniyor. 

 

Ek olarak Management console açmak istediğimde 

 The following error occured while searching for the on-premises Exchange server : 

Connecting to remote server failed with the following error message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more informatin , see the about_Remote_Troubleshooting  Help topic. It was running the command 'Discover-ExchangeServer -UseWIA $true - SuppressError $true -CurrentVersion "Version 14.3 (Build 123.4)" 

şeklinde bir uyarı var. Bunun için support microsoft da bulduğum çözüm  http://support.microsoft.com/en-us/kb/2028305 

Fakat burada uygulanması önerilen komutu çalıştırmak istediğimde PowerShell de aldığım hata tekrarlanıyor  

Management console hatası için çözüm önerisi buldum fakat ISS Manager da önerideki görüntüyü göremedim. 

Ayrıca hotmail hesabımdan şirket mailime mail atabiliyorum fakat şirket mailimden hotmail hesabıma mail attığımda gönderildi olarak gözüküyor ama mail gelmiyor.  

kaynak : http://blogs.technet.com/b/exchange/archive/2010/02/04/3409289.aspx 

Issue:

Connecting to remote server failed with the following error message: The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.

Possible causes:

1. Remote PowerShell uses Kerberos to authenticate the user connecting. IIS implements this Kerberos authentication method via a native module. In IIS Manager, if you go to the PowerShell Virtual Directory and then look at the Modules, you should see Kerbauth listed as a Native Module, with the dll location pointing to C:\Program Files\Microsoft\Exchange Server\v14\Bin\kerbauth.dll. If the Kerbauth module shows up as a Managed module instead of Native, or if the Kerbauth module has been loaded on the Default Web Site level (instead of, or in addition to, the PowerShell virtual directory), you can experience this issue. To correct this, make sure that the Kerbauth module is not enabled on the Default Web Site, but is only enabled on the PowerShell virtual directory. The entry type of "Local" indicates that the Kerbauth module was enabled directly on this level, and not inherited from a parent.

2. If the WSMan module entry is missing from the global modules section of the C:\Windows\System32\Inetsrv\config\ApplicationHost.config file, as follows:

<globalModules>
           <add name="WSMan" image="C:\Windows\system32\wsmsvc.dll" />

This will result in the WSMan module displaying as a Managed module on the PowerShell virtual directory.

To correct this, make sure that the WSMan module has been registered (but not enabled) at the Server level, and has been enabled on the PowerShell virtual directory.

3. If the user that is attempting to connect is not Remote PowerShell enabled. To check if a user is enabled for Remote PowerShell, you need to open the Exchange Management Shell with an account that has been enabled, and run the following query.

(Get-User <username>).RemotePowershellEnabled

This will return a True or False. If the output shows False, the user is not enabled for Remote PowerShell. To enable the user, run the following command.

Set-User <username> -RemotePowerShellEnabled $True 

Merhaba,

Sistemin yedeği elinizde var ise geçiş öncesine dönmeniz en doğru yöntem olacaktır. Eğer böyle bir imkan yok ise mevcut sistemin bir yedeğini veya imajını alın, daha sonra kayıt defterinde aşağıdaki kodu arayın ve çıkan tüm girdileri silin

14f288c7-c695-40d5-971d-8890605c6040

daha sonra setup dosyasını yeniden çalıştırın.

Eğer bir sorun olur ise lütfen setup log dosyasının hara bölümlerini bizim ile paylaşın.

Hakan bey merhaba , 

Öncelikle ilgilendiğiniz için teşekkür ederim.

Dediğiniz gibi  14f288c7-c695-40d5-971d-8890605c6040 kayıt anahtarını tüm kayıt defterinde aradım ve çıkan sonuçları tek tek sildim. 

Ardından yeniden kurulumu başlattım ve tekrar bu hata ile karşılaştım. 

 Error : 

The following error was generated when "$error.Clear(); uninstall-MsiPackage -ProductCode '{14F288C7-C695-40D5-971D-8890605C6040}' -LogFile [$RoleSetupLoggingPath + "\UninstallASEntRS.msilog") 

" was run : " Couldn't remove product with code 14f288c7-c695-40d5-971d-8890605c6040. This action is only valid for products that are currently installed. Error code is 1605".

Couldn't remove product with code  14f288c7-c695-40d5-971d-8890605c6040. This action is only valid for products thar are currently installed. Error code is 1605. 

This action is only valid for products that are currently installed

Click here for help.

Setup log dosyasında hata bölümü 

[03.29.2015 10:44:17.0203] [2] Process standard error: 

[03.29.2015 10:44:17.0203] [2] Ending processing register-ComInteropTLB

[03.29.2015 10:44:17.0203] [1] Executing: 

          uninstall-MsiPackage -ProductCode '{C3F10D8C-BD70-4516-B2B4-BF6901980741}' -LogFile ($RoleSetupLoggingPath + "\UninstallASDat.msilog")

        

[03.29.2015 10:44:17.0203] [2] Active Directory session settings for 'Uninstall-MsiPackage' are: View Entire Forest: 'True', Configuration Domain Controller: 'x.local', Preferred Global Catalog: 'x.local', Preferred Domain Controllers: '{ x.local }'

[03.29.2015 10:44:17.0203] [2] Beginning processing uninstall-MsiPackage -ProductCode:'c3f10d8c-bd70-4516-b2b4-bf6901980741' -LogFile:'C:\ExchangeSetupLogs\UninstallASDat.msilog'

[03.29.2015 10:44:17.0203] [2] Ending processing uninstall-MsiPackage

[03.29.2015 10:44:17.0203] [1] Executing: 

          uninstall-MsiPackage -ProductCode '{14F288C7-C695-40D5-971D-8890605C6040}' -LogFile ($RoleSetupLoggingPath + "\UninstallASEntIRS.msilog")

        

[03.29.2015 10:44:17.0203] [2] Active Directory session settings for 'Uninstall-MsiPackage' are: View Entire Forest: 'True', Configuration Domain Controller: 'x.local', Preferred Global Catalog: 'x.ocal', Preferred Domain Controllers: '{ x.local }'

[03.29.2015 10:44:17.0203] [2] Beginning processing uninstall-MsiPackage -ProductCode:'14f288c7-c695-40d5-971d-8890605c6040' -LogFile:'C:\ExchangeSetupLogs\UninstallASEntIRS.msilog'

[03.29.2015 10:44:17.0203] [2] Removing MSI package with code '14f288c7-c695-40d5-971d-8890605c6040'.

[03.29.2015 10:44:17.0265] [2] [ERROR] Unexpected Error

[03.29.2015 10:44:17.0265] [2] [ERROR] Couldn't remove product with code 14f288c7-c695-40d5-971d-8890605c6040. This action is only valid for products that are currently installed. Error code is 1605.

[03.29.2015 10:44:17.0265] [2] [ERROR] This action is only valid for products that are currently installed

[03.29.2015 10:44:17.0281] [2] Ending processing uninstall-MsiPackage

[03.29.2015 10:44:17.0281] [1] The following 1 error(s) occurred during task execution:

[03.29.2015 10:44:17.0281] [1] 0.  ErrorRecord: Couldn't remove product with code 14f288c7-c695-40d5-971d-8890605c6040. This action is only valid for products that are currently installed. Error code is 1605.

[03.29.2015 10:44:17.0281] [1] 0.  ErrorRecord: Microsoft.Exchange.Configuration.Tasks.TaskException: Couldn't remove product with code 14f288c7-c695-40d5-971d-8890605c6040. This action is only valid for products that are currently installed. Error code is 1605. ---> System.ComponentModel.Win32Exception: This action is only valid for products that are currently installed

   --- End of inner exception stack trace ---

[03.29.2015 10:44:17.0297] [1] [ERROR] The following error was generated when "$error.Clear(); 

          uninstall-MsiPackage -ProductCode '{14F288C7-C695-40D5-971D-8890605C6040}' -LogFile ($RoleSetupLoggingPath + "\UninstallASEntIRS.msilog")

        " was run: "Couldn't remove product with code 14f288c7-c695-40d5-971d-8890605c6040. This action is only valid for products that are currently installed. Error code is 1605.".

[03.29.2015 10:44:17.0297] [1] [ERROR] Couldn't remove product with code 14f288c7-c695-40d5-971d-8890605c6040. This action is only valid for products that are currently installed. Error code is 1605.

[03.29.2015 10:44:17.0297] [1] [ERROR] This action is only valid for products that are currently installed

[03.29.2015 10:44:17.0297] [1] [ERROR-REFERENCE] Id=TransportCommonComponent___85242ca8afce4b699883dac5856c2fd6 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup

[03.29.2015 10:44:17.0297] [1] Setup is stopping now because of one or more critical errors.

[03.29.2015 10:44:17.0297] [1] Finished executing component tasks.

[03.29.2015 10:44:17.0375] [1] Ending processing Install-BridgeheadRole

 

 Not : x.local olarak adlandırdığım alan adc sunucusu , dc için böyle bir hata vermiyor. Bu bilgi problemin çözümü ile alakalı olabilir mi ? 

 

İşin ilginç kısmı , 2010 SP 3 yüklemesinde hata aldıktan sonra Management Console da versiyon bilgisine baktığımda SP3 gözüküyor. 

Ayrıca RU1 yükseltmesi sorunsuz bir şekilde üstüne yüklenebiliyor ve şuanda local de mail trafiği var , dışarıdan içeriye mail geliyor fakat sadece içeriden dışarıya mail gitmiyor ama gönderilen mailler gönderilmiş öğelere düşünüyor giden kutusunda beklemiyor.  

Management consol'u aşağıdaki hata görüntülendiği için açamadığımdan mailler nerede kalıyor göremiyorum.

The following error occured while searching for the on-premises Exchange server : 

Connecting to remote server failed with the following error message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more informatin , see the about_Remote_Troubleshooting  Help topic. It was running the command 'Discover-ExchangeServer -UseWIA $true - SuppressError $true -CurrentVersion "Version 14.3 (Build 123.4)"  

Hocam RU2 ile mail gönderme sorununu çözdüm. 

Şuan Management console'un açılırken alınan hata ve powershell de görüntülenen hata kaldı.

 

Geçmiş olsun, bu hatalar ise IIS ile ilgili bunun da virtual directoryleri yeniden oluşturarak çözebilirsiniz.