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:
WARNING: Unexpected error. A Watson image is being generated: The mailbox was not found. Mailbox = 'extest_a8e4e849bf564@mail.frankysweb.local'..
The mailbox was not found. Mailbox = '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 most cases it is sufficient to execute the script, but it can also happen that "new-TestCasConnectivityUser.ps1" also reports an error that looks something like this:
[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
To fix the problem, open "new-TestCasConnectivityUser.ps1" with a text editor such as Notepad and delete this passage in line 49:
-OrganizationalUnit:$OrganizationalUnit
Test Outlook Web Services should work by now at the latest. The output looks something like this:
Geanu das macht das Script ja:
“new-TestCasConnectivityUser.ps1″
Den Fehler hatte ich auch konnte ihn aber beheben indem ich das Fehlende Emailpostfach erstellt habe. Bei dir wäre es dann ’extest_a8e4e849bf564@mail.frankysweb.local’.. :-)