The CMDlet „Test-OutlookWebServices“
is handy for detecting configuration problems, but unfortunately the CMDlet is a bit bitchy until it runs J
This error normally occurs when executing Test Outlook WebServices on:
WARNUNG: Unerwarteter Fehler. Ein Watson-Abbild wird generiert: Das Postfach wurde nicht gefunden. Postfach =’extest_a8e4e849bf564@mail.frankysweb.local‘..
Das Postfach wurde nicht gefunden. Postfach = ‚extest_a8e4e849bf564@mail.frankysweb.local‘.
+ CategoryInfo : NotSpecified: (:) [Test-OutlookWebServices], MailboxNotFoundException
+ FullyQualifiedErrorId : Microsoft.Exchange.Monitoring.MailboxNotFoundException,Microsoft.Exchange.Management.SystemConfigurationTasks.TestOutlookWebServicesTask
To fix this error, there is a script under C:\Program Files\Microsoft\Exchange Server\V14\Scripts or the installation directory of Exchange 2010, which is called „new-TestCasConnectivityUser.ps1“
is called. This script creates the corresponding user and mailbox so that Test-OutlookWebServices works.
In den meisten Fällen reicht es aus das Script auszuführen, es kann aber auch vorkommen das „new-TestCasConnectivityUser.ps1“ ebenfalls einen Fehler meldet, der ungefähr so aussieht:
[PS] C:\Exchange Server\V14\Scripts>.\new-TestCasConnectivityUser.ps1
Please enter a temporary secure password for creating test users. For security purposes, the password will be changed regularly and automatically by
the system if SCOM is installed. The password must be changed manually if SCOM is not installed.
Enter password: ***************
Create test user on: mail.frankysweb.local
Click CTRL+Break to quit or click Enter to continue..:
CreateTestUser : Mailbox could not be created. Verify that OU ( Users ) exists and that password meets complexity requirements.
At C:\Exchange Server\V14\Scripts\new-TestCasConnectivityUser.ps1:255 char:27
+ $result = CreateTestUser <<<< $exchangeServer $mailboxServer $securePassword $OrganizationalUnit $UMDialPlan $UMExtension $Prompt
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,CreateTestUser
Um das Problem zu beheben öffnet man „new-TestCasConnectivityUser.ps1“ mit einem Texteditor wie zum Beispiel Notepad und löscht diese Passage in Zeile 49:
-OrganizationalUnit:$OrganizationalUnit
Test Outlook Web Services should work by now at the latest. The output looks something like this:
