{"id":279,"date":"2017-07-04T12:46:43","date_gmt":"2017-07-04T10:46:43","guid":{"rendered":"https:\/\/itblogwildi.wordpress.com\/?p=279"},"modified":"2017-07-04T12:46:43","modified_gmt":"2017-07-04T10:46:43","slug":"exchange-ecp-defekt-error-500","status":"publish","type":"post","link":"https:\/\/itblog.wildi.dk\/?p=279","title":{"rendered":"Exchange ECP defekt: Error 500"},"content":{"rendered":"<p>In meiner Laborumgebung hatte ich auf einem Windows Server 2016 mit Exchange 2016 testhalber .NET 3.5 installiert, da dies von einem Tool gefordert wurde.<\/p>\n<p>Ja, ich weiss: nix solches direkt auf dem Exchange installieren \ud83d\ude09<\/p>\n<p>Nachdem ich alles wieder deinstalliert hatte, erhielt ich folgende Fehlermeldung, wenn ich Exchange verwalten wollte:<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-286\" src=\"https:\/\/itblog.wildi.dk\/wp-content\/uploads\/2017\/07\/ex2016_01.jpg\" alt=\"Ex2016_01\" width=\"795\" height=\"198\" srcset=\"https:\/\/itblog.wildi.dk\/wp-content\/uploads\/2017\/07\/ex2016_01.jpg 795w, https:\/\/itblog.wildi.dk\/wp-content\/uploads\/2017\/07\/ex2016_01-300x75.jpg 300w, https:\/\/itblog.wildi.dk\/wp-content\/uploads\/2017\/07\/ex2016_01-768x191.jpg 768w\" sizes=\"auto, (max-width: 795px) 100vw, 795px\" \/><\/p>\n<pre>500\nUnerwarteter Fehler\nAufgrund eines Fehlers konnte die Anforderung nicht abgeschlossen werden. Bitte versuchen Sie es noch mal.<\/pre>\n<p>Die Exchange Powershell funktionierte ebenfalls nicht mehr:<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-287\" src=\"https:\/\/itblog.wildi.dk\/wp-content\/uploads\/2017\/07\/ex2016_02.jpg\" alt=\"Ex2016_02\" width=\"1790\" height=\"425\" srcset=\"https:\/\/itblog.wildi.dk\/wp-content\/uploads\/2017\/07\/ex2016_02.jpg 1790w, https:\/\/itblog.wildi.dk\/wp-content\/uploads\/2017\/07\/ex2016_02-300x71.jpg 300w, https:\/\/itblog.wildi.dk\/wp-content\/uploads\/2017\/07\/ex2016_02-1024x243.jpg 1024w, https:\/\/itblog.wildi.dk\/wp-content\/uploads\/2017\/07\/ex2016_02-768x182.jpg 768w, https:\/\/itblog.wildi.dk\/wp-content\/uploads\/2017\/07\/ex2016_02-1536x365.jpg 1536w\" sizes=\"auto, (max-width: 1790px) 100vw, 1790px\" \/><\/p>\n<pre>AUSF\u00dcHRLICH: Verbindung mit SERVER.domain.local wird hergestellt.\nNew-PSSession : [SERVER.domain.local] Beim Verarbeiten von Daten vom Remoteserver\n\"SERVER.domain.local\" ist folgender Fehler aufgetreten: [ClientAccessServer=SERVER,BackEndServer=SERVER.domain.local,RequestId=0d25df17-f96e-4619-a9e3-549e9638fccb,TimeStamp=04.07.2017 09:23:33]\n[AuthZRequestId=a3b17802-46df-4f8b-9495-eab944a0faea][FailureCategory=AuthZ-SetupVersionInformationCorruptException]\nDie installierte Dateiversion kann nicht anhand des Registrierungsschl\u00fcssels\n'HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\PowerShell\\1\\PowerShellEngine' ermittelt werden. Weitere Informationen finden\nSie im Hilfethema \"about_Remote_Troubleshooting\".\nIn Zeile:1 Zeichen:1\n+ New-PSSession -ConnectionURI \"$connectionUri\" -ConfigurationName Micr ...\n+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n + CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin\n gTransportException\n + FullyQualifiedErrorId : IncorrectProtocolVersion,PSSessionOpenFailed\n\n<\/pre>\n<p>Einfache L\u00f6sung dieses Problems:<\/p>\n<p>Folgende Registry Keys importieren:<\/p>\n<p>Windows Registry Editor Version 5.00<\/p>\n<pre>[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\PowerShell\\1\\PowerShellEngine]\n\"ApplicationBase\"=\"C:\\\\Windows\\\\System32\\\\WindowsPowerShell\\\\v1.0\"\n\"ConsoleHostAssemblyName\"=\"Microsoft.PowerShell.ConsoleHost, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=msil\"\n\"ConsoleHostModuleName\"=\"C:\\\\Windows\\\\System32\\\\WindowsPowerShell\\\\v1.0\\\\Microsoft.PowerShell.ConsoleHost.dll\"\n\"PowerShellVersion\"=\"2.0\"\n\"PSCompatibleVersion\"=\"1.0, 2.0\"\n\"RuntimeVersion\"=\"v2.0.50727\"<\/pre>\n<p>Es ist kein Neustart erforderlich.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In meiner Laborumgebung hatte ich auf einem Windows Server 2016 mit Exchange 2016 testhalber .NET 3.5 installiert, da dies von&#8230; <a class=\"read-more\" href=\"https:\/\/itblog.wildi.dk\/?p=279\">Read more<\/a><\/p>\n","protected":false},"author":2,"featured_media":286,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5,13],"tags":[95],"class_list":["post-279","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-allgemein","category-exchange","tag-windows"],"_links":{"self":[{"href":"https:\/\/itblog.wildi.dk\/index.php?rest_route=\/wp\/v2\/posts\/279","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/itblog.wildi.dk\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/itblog.wildi.dk\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/itblog.wildi.dk\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/itblog.wildi.dk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=279"}],"version-history":[{"count":0,"href":"https:\/\/itblog.wildi.dk\/index.php?rest_route=\/wp\/v2\/posts\/279\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/itblog.wildi.dk\/index.php?rest_route=\/wp\/v2\/media\/286"}],"wp:attachment":[{"href":"https:\/\/itblog.wildi.dk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=279"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/itblog.wildi.dk\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=279"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/itblog.wildi.dk\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=279"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}