none
Websitepostfächer RRS feed

  • Frage

  • Hallo,

    ich hoffe, hier kann mir jemand einen Tipp für die Problemlösung geben.

    Ich habe Sharepoint Server 2013 und Exchange 2013 nach dieser Anleitung für Websitepostfächer konfiguriert:

    http://technet.microsoft.com/de-de/library/jj552524%28v=office.15%29.aspx

    Wenn ich versuche, ein Websitepostfach einzurichten, bekomme ich aber immer die folgende Meldung:

    Websitepostfach

    Ihre Exchange Server-Konfiguration wird nicht unterstützt.

    Die Exchange Server-Konfiguration Ihrer Organisation wird nicht unterstützt. Wenden Sie sich an den Systemadministrator, um weitere Informationen zu erhalten.

    Korrelations-ID: 4b4d939c-f049-9019-2ce4-0748b668d86e, Fehlercode 3

    Weiß jemand, was ich machen?

    Danke

    Johannes

    Donnerstag, 22. Mai 2014 07:05

Antworten

  • Hi,
    in der CA ist konfiguriert, wo die Log-Dateien abgelegt werden. Üblicherweise (ohne eigene Anpassung) befinden sich die Log-Dateien im Pfad:

    C:\Program Files\Common Files\Microsoft Shared\Web server extensions\15\LOGS

    Da die Log-Dateien immer neu erstellt werden und dann zyklisch gelöscht werden, musst Du natürlich die zum Zeitpunkt des Ereignisses gehörende Log-Datei auswerten. Wenn Du sofort nach dem Auftreten des Fehlers die Log-Datei mit dem jüngsten Erstellungsdatum öffnest, findest Du fast immer den Eintrag, wenn nicht, dann nimm die vorherige Log-Datei.

    "Alles aktivieren" bedeutet sehr viel Speicherplatz, sehr lange Log-Dateien und meist auch mehr Aufwand die gewünschte Log-Datei zu finden. Mit dem UlsViewer kannst Du mehrere Log-Dateien laden und gleichzeitig auswerten, z.B. gefiltert nach der ID.

    --
    Peter

    Donnerstag, 22. Mai 2014 14:45
  • Hallo Peter,

    danke, das Problem ist gelöst.

    Falls es noch jemanden betrifft:

    ich habe einfach die interne Domain in der E-Mail Adressrichtlinie hinzugefügt.

    Lg

    Johannes

    Montag, 26. Mai 2014 09:49

Alle Antworten

  • Hi,
    was steht ganu im Log zu dieser ID? Villeicht kann man da etwas mehr erkennen.

    --
    Peter

    Donnerstag, 22. Mai 2014 13:47
  • Leider nichts. Mit dieser Id läßt sich kein Log-Eintrag finden (über get-splogevent)
    Donnerstag, 22. Mai 2014 14:14
  • Hi,
    geh doch mal direkt ins log oder mit dem ULSViewer. Wenn wirklich nichts im Log steht, dann vergrößere mal den Log-Umfang (in der CA).

    --
    Peter

    Donnerstag, 22. Mai 2014 14:22
  • Hallo,

    danke. Kannst du mir bitte ungefähr sagen, welches Log? Ich hab leider von Sharepoint nicht allzuviel Ahnung. Bei den Logs hab ich alles aktiviert.

    Donnerstag, 22. Mai 2014 14:26
  • Hi,
    in der CA ist konfiguriert, wo die Log-Dateien abgelegt werden. Üblicherweise (ohne eigene Anpassung) befinden sich die Log-Dateien im Pfad:

    C:\Program Files\Common Files\Microsoft Shared\Web server extensions\15\LOGS

    Da die Log-Dateien immer neu erstellt werden und dann zyklisch gelöscht werden, musst Du natürlich die zum Zeitpunkt des Ereignisses gehörende Log-Datei auswerten. Wenn Du sofort nach dem Auftreten des Fehlers die Log-Datei mit dem jüngsten Erstellungsdatum öffnest, findest Du fast immer den Eintrag, wenn nicht, dann nimm die vorherige Log-Datei.

    "Alles aktivieren" bedeutet sehr viel Speicherplatz, sehr lange Log-Dateien und meist auch mehr Aufwand die gewünschte Log-Datei zu finden. Mit dem UlsViewer kannst Du mehrere Log-Dateien laden und gleichzeitig auswerten, z.B. gefiltert nach der ID.

    --
    Peter

    Donnerstag, 22. Mai 2014 14:45
  • Hallo,

    danke für deine Hilfe. Ich hoffe, ich komme heute dazu, mir das anzusehen.

    Alle Logs aktiviert habe ich, in der Hoffnung, etwas zu meinem Fehler zu finden. Der ULSViewer funktioniert bei mir leider nicht. Der aktuellste, den ich gefunden habe, ist aus 2009 und hat vielleicht ein Problem mit Server 2012.


    Freitag, 23. Mai 2014 05:04
  • Hi,
    ich nutze den UlsViewer von CodePlex in der Version 2.0.3530.27850 völlig problemlos für den SP 2013 unter Windows Server 2012. Was funktioniert da bei Dir nicht.

    --
    Peter

    Freitag, 23. Mai 2014 05:24
  • Hallo Peter,

    danke für deine Hilfe. Die Version des ULSViewer, die ich heruntergeladen hatte, ist immer sofort nach dem Start wieder abgestürzt, diese funktioniert. Allerdings sind die Logs nicht sehr vielsagend. Alles, was ich zu so einer Korrelations-ID finde ist:

    [Forced due to logging gap, cached @ 05/26/2014 07:39:33.36, Original Level: Verbose] SQL connection time: 0.0672
    [Forced due to logging gap, Original Level: Verbose] {0}
    [Forced due to logging gap, cached @ 05/26/2014 07:39:33.42, Original Level: Verbose] Completed deserializing the type named {0} and with id {1}.
    [Forced due to logging gap, Original Level: Verbose] ExchangeHasPermissionsToSiteSubscription: Found TrustedSecurityTokenService: {0}
    [Forced due to logging gap, cached @ 05/26/2014 07:39:33.44, Original Level: High] The ouput name identifier generated by SPAppPrincipalName is '{0}'.
    [Forced due to logging gap, Original Level: High] The scale out database mappings cache is getting refreshed for service id e05eebdb-9191-432f-8e56-d34810f5a872.
    [Forced due to logging gap, cached @ 05/26/2014 07:39:33.59, Original Level: Verbose] SQL connection time: 0.0699
    [Forced due to logging gap, Original Level: Verbose] Deserializing the type named {0} and with id {1}.
    [Forced due to logging gap, cached @ 05/26/2014 07:39:33.66, Original Level: Medium] WcfSendRequest: RemoteAddress: '{0}' Channel: '{1}' Action: '{2}' MessageId: '{3}'
    [Forced due to logging gap, Original Level: High] Leaving Monitored Scope ({0}).{1}
    [Forced due to logging gap, cached @ 05/26/2014 07:39:36.53, Original Level: Verbose] SPSecurityTokenServiceManager!GetTrustedSecurityTokenServiceByNameId: Searching trusted security token issuers for input {0}
    [Forced due to logging gap, Original Level: VerboseEx] Reverting to process identity
    [Forced due to logging gap, cached @ 05/26/2014 07:39:36.59, Original Level: VerboseEx] GetConfiguredProperty: No Property Configured for {0}; returning null
    [Forced due to logging gap, Original Level: Verbose] Authenticating OAuth2 Bearer challenge.
    [Forced due to logging gap, cached @ 05/26/2014 07:39:37.11, Original Level: Verbose] Requesting self-issued token for '{0}'.
    [Forced due to logging gap, Original Level: Medium] WcfSendRequest: RemoteAddress: '{0}' Channel: '{1}' Action: '{2}' MessageId: '{3}'
    [Forced due to logging gap, Original Level: High] Leaving Monitored Scope ({0}).{1}
    [Forced due to logging gap, cached @ 05/26/2014 07:39:37.27, Original Level: Verbose] ____{0}={1}
    [Forced due to logging gap, Original Level: Medium] SearchServiceApplication::ExchangeAdapter::SharePoint CorrelationId:7593949c-6074-9019-2ce4-0bd1db1da70a; Exchange Request Id:0ba970ce-8cd4-47e8-8c5e-2ff0f32a9109; Diagnostic Info:

    Durch googeln habe ich jetzt herausgefunden, dass es mit den Domain-Einstellungen zu tun haben könnte. Mir wird auch mit dem Befehl

    Get-AutodiscoverVirtualDirectory -DomainController Exch1 -Server CAS01

    keine InternalURL angezeigtl, auch nicht, wenn ich vorher mit Get-ClientAccessServer | Set-ClientAccessServer -AutoDiscoverServiceInternalUri eine URL festlege.

    Montag, 26. Mai 2014 07:08
  • Hallo Peter,

    danke, das Problem ist gelöst.

    Falls es noch jemanden betrifft:

    ich habe einfach die interne Domain in der E-Mail Adressrichtlinie hinzugefügt.

    Lg

    Johannes

    Montag, 26. Mai 2014 09:49
  • Hallo Johannes,

    ich habe das selbe Problem, wie oben geschrieben.

    Kannst du mir sagen, was du genau mit der internen Domain meinst?

    Danke im Voraus.

    Marc

    Dienstag, 3. Juni 2014 15:38
  • Hi,
    kannst Du mal den Fehler posten, der mit der angezeigten Korrelations-ID in die Log-Datei eingetragen wurde.

    --
    Peter

    Mittwoch, 4. Juni 2014 03:52
  • Hallo Peter,

    hier das LOG:

    06/04/2014 09:19:35.63  w3wp.exe (0x1A54)                        0x3EC4 SharePoint Foundation          Logging Correlation Data       xmnv Medium   Name=Request (POST:https://server241.domain.de:82/_vti_bin/client.svc/ProcessQuery) c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:35.64  w3wp.exe (0x1A54)                        0x3EC4 SharePoint Foundation          Authentication Authorization   agb9s Medium   Non-OAuth request. IsAuthenticated=True, UserIdentityName=0#.w|domain\user, ClaimsCount=96 c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:35.71  w3wp.exe (0x1A54)                        0x3EC4 SharePoint Foundation          Runtime                        ajd6l High     [Forced due to logging gap, cached @ 06/04/2014 09:19:35.64, Original Level: Verbose] Value for checkAuthenticationCookie is : {0} c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:35.71  w3wp.exe (0x1A54)                        0x3EC4 SharePoint Foundation          Runtime                        fx7p High     [Forced due to logging gap, Original Level: Verbose] Service at {0} implemented interface IServiceFactoryUsingAuthSchemeInEndpointAddress: {1} c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:36.84  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Asp Runtime                    aj1kl High     [Forced due to logging gap, cached @ 06/04/2014 09:19:35.71, Original Level: Verbose] SPRequestModule.PreRequestExecuteAppHandler c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:36.84  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          CSOM                           ki7a High     [Forced due to logging gap, Original Level: Verbose] Creating binding for service {0} and endpoint at {1}. c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:37.05  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          CSOM                           ki7i High     [Forced due to logging gap, cached @ 06/04/2014 09:19:36.88, Original Level: Verbose] Cannot find configuration for service {0} c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:37.05  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Topology                       ainyp Medium   The context uri in ConfigServiceHostIfClaimsAuth is https://server241.domain.de:82/_vti_bin/client.svc/ProcessQuery c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:39.35  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Monitoring                     aeap2 High     [Forced due to logging gap, Original Level: Verbose] Set diagnostics context correlationid {0}, trace level {1}, isDevdashboardenabled {2} c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:39.35  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Monitoring                     aeap2 High     [Forced due to logging gap, Original Level: Verbose] Set diagnostics context correlationid {0}, trace level {1}, isDevdashboardenabled {2} c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:39.61  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          CSOM                           aiv4e High     [Forced due to logging gap, Original Level: Verbose] Processing CSOM queries c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:39.65  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          CSOM                           agw10 Medium   Begin CSOM Request ManagedThreadId=55, NativeThreadId=6512 c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:39.66  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Logging Correlation Data       xmnv Medium   Site=/ c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:39.96  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          CSOM                           ajwqi High     [Forced due to logging gap, cached @ 06/04/2014 09:19:39.70, Original Level: Verbose] Request has SPBasePermissions.UseRemoteAPIs permission c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:39.96  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          CSOM                           ajoyd High     [Forced due to logging gap, Original Level: Verbose] Request schema version is 15 c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:39.96  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          CSOM                           ajoyd High     [Forced due to logging gap, Original Level: Verbose] Request schema version is 15 c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:40.02  w3wp.exe (0x1A54)                        0x1970 SharePoint Server              Taxonomy                       aiyhr High     [Forced due to logging gap, Original Level: Verbose] Begin: TaxonomyCsomProcessingHandler.Initialize c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:40.03  w3wp.exe (0x1A54)                        0x1970 SharePoint Portal Server       Microfeeds                     aizmk High     serviceHost_RequestExecuting c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:40.11  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          CSOM Api                       agw12 High     [Forced due to logging gap, cached @ 06/04/2014 09:19:40.07, Original Level: Verbose] Entering Microsoft.SharePoint.Portal.CollaborationMailboxInternalService.GetCollabMailboxViewInfo c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:40.11  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Database                       8acb High     [Forced due to logging gap, Original Level: VerboseEx] Reverting to process identity c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:40.16  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Database                       ahjqp High     [Forced due to logging gap, cached @ 06/04/2014 09:19:40.12, Original Level: Verbose] SQL connection time: 0.0731 c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:40.16  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Database                       8acb High     [Forced due to logging gap, Original Level: VerboseEx] Reverting to process identity c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:40.16  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Database                       ahjqp High     [Forced due to logging gap, cached @ 06/04/2014 09:19:40.12, Original Level: Verbose] SQL connection time: 0.0731 c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:40.16  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Database                       8acb High     [Forced due to logging gap, Original Level: VerboseEx] Reverting to process identity c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:40.22  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          General                        6t8j High     [Forced due to logging gap, cached @ 06/04/2014 09:19:40.21, Original Level: Verbose] {0} c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:40.22  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Database                       8acb High     [Forced due to logging gap, Original Level: VerboseEx] Reverting to process identity c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:40.33  w3wp.exe (0x1A54)                        0x1970                                0x6FB700D                      ahg9p High     [Forced due to logging gap, cached @ 06/04/2014 09:19:40.27, Original Level: Verbose] Completed deserializing the type named {0} and with id {1}. c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:40.33  w3wp.exe (0x1A54)                        0x1970 SharePoint Portal Server       Site Mailbox                   ajv83 High     [Forced due to logging gap, Original Level: Verbose] ExchangeHasPermissionsToSiteSubscription: Found TrustedSecurityTokenService: {0} c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:40.34  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Application Authentication     aiixd High     The ouput name identifier generated by SPAppPrincipalName is '00000002-0000-0ff1-ce00-000000000000@domain.com'. c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:40.63  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Database                       abihh High     The scale out database mappings cache is getting refreshed for service id 0d085904-b597-4d19-a6fd-8fe5d88ff42e. c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:40.71  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Topology                       ahg9p High     [Forced due to logging gap, cached @ 06/04/2014 09:19:40.65, Original Level: Verbose] Completed deserializing the type named {0} and with id {1}. c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:40.71  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Topology                       e5mc Medium   WcfSendRequest: RemoteAddress: 'http://server241:32843/59c3f9b9087a430b8414673c8a46829e/AppMng.svc' Channel: 'Microsoft.SharePoint.AppManagement.IAppManagementServiceApplication' Action: 'http://schemas.microsoft.com/sharepoint/soap/IAppManagementServiceApplication/GetAppManagementDatabaseMap' MessageId: 'urn:uuid:0394734f-5cde-48cc-9db4-e6cacc9db31b' c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:40.75  w3wp.exe (0x30C0)                        0x2330 SharePoint Foundation          Monitoring                     nasq Medium   Entering monitored scope (ExecuteWcfServerOperation). Parent No 
    06/04/2014 09:19:40.75  w3wp.exe (0x30C0)                        0x2330 SharePoint Foundation          Topology                       e5mb Medium   WcfReceiveRequest: LocalAddress: 'http://server241.domain.de:32843/59c3f9b9087a430b8414673c8a46829e/AppMng.svc' Channel: 'System.ServiceModel.Channels.ServiceChannel' Action: 'http://schemas.microsoft.com/sharepoint/soap/IAppManagementServiceApplication/GetAppManagementDatabaseMap' MessageId: 'urn:uuid:0394734f-5cde-48cc-9db4-e6cacc9db31b' c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:40.77  w3wp.exe (0x30C0)                        0x2330 SharePoint Foundation          Database                       afjqz Medium   The following range is retrieved for database Service_AppManagement while constructing the database map: Range Start: 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00, Range End: NULL, Lower Sub-Range Mode: ReadWrite, Lower Sub-Range Point NULL, Upper Sub-Range Mode: ReadWrite, Upper Sub-Range Point: NULL. c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:40.77  w3wp.exe (0x30C0)                        0x2330 SharePoint Foundation          Monitoring                     b4ly Medium   Leaving Monitored Scope (ExecuteWcfServerOperation). Ausführungszeit=14,2689 c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:40.81  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Monitoring                     b4ly High     Leaving Monitored Scope (AppManagementServiceApplicationProxy.GetAppManagementDatabaseMap). Ausführungszeit=181,4468 c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:40.83  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Database                       abihi High     The scale out database mappings cache has been refreshed for service id 0d085904-b597-4d19-a6fd-8fe5d88ff42e. The new mappings are as follows: For database Data Source=server242;Initial Catalog=Service_AppManagement;Integrated Security=True;Enlist=False;Pooling=True;Min Pool Size=0;Max Pool Size=100;Connect Timeout=15: range start 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00, range end NULL. c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:40.88  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Database                       ahjqp High     [Forced due to logging gap, cached @ 06/04/2014 09:19:40.85, Original Level: Verbose] SQL connection time: 11.0206 c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:40.88  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Application Authentication     adnh0 High     [Forced due to logging gap, Original Level: Verbose] Retrieving the authentication realm for context '{0}'. c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:40.88  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Application Authentication     aiixd High     The ouput name identifier generated by SPAppPrincipalName is '00000002-0000-0ff1-ce00-000000000000@35602163-d0c1-4474-8e46-dbaec0e168bc'. c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:40.96  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Claims Authentication          ajau9 High     [Forced due to logging gap, cached @ 06/04/2014 09:19:40.90, Original Level: Verbose] SPSecurityTokenServiceManager!GetTrustedSecurityTokenServiceByNameId: Searching trusted security token issuers for input {0} c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:40.96  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Database                       8acb High     [Forced due to logging gap, Original Level: VerboseEx] Reverting to process identity c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:41.01  w3wp.exe (0x1A54)                        0x1970                                0x6FB7003                      ahjqp High     [Forced due to logging gap, cached @ 06/04/2014 09:19:41.00, Original Level: Verbose] SQL connection time: 0.0689 c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:41.01  w3wp.exe (0x1A54)                        0x1970 SharePoint Portal Server       Site Mailbox                   ah2dm High     [Forced due to logging gap, Original Level: VerboseEx] GetTeamMailboxSmtpAddress: Returning Web Application Domain: {0} c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:41.65  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation Search   Exchange Integration           aiwxh High     [Forced due to logging gap, cached @ 06/04/2014 09:19:41.04, Original Level: VerboseEx] GetConfiguredProperty: No Property Configured for {0}; returning null c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:41.65  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Application Authentication     age6e High     [Forced due to logging gap, Original Level: Verbose] Authenticating OAuth2 Bearer challenge. c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:41.73  OWSTIMER.EXE (0x2438)                    0x37BC SharePoint Foundation          Monitoring                     b4ly Medium   Leaving Monitored Scope (Timer Job job-application-server-admin-service). Ausführungszeit=3303,1021 c37e979c-c64b-c08b-5348-7952fc8fd182
    06/04/2014 09:19:41.73  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Application Authentication     airzo High     [Forced due to logging gap, Original Level: Verbose] Using elevated OAuth2 bearer credentials. c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:41.87  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Application Authentication     aiv3a High     [Forced due to logging gap, cached @ 06/04/2014 09:19:41.77, Original Level: Verbose] Requesting self-issued token for '{0}'. c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:41.87  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Topology                       e5mc Medium   WcfSendRequest: RemoteAddress: 'net.pipe://localhost/SecurityTokenServiceApplication/appsts.svc' Channel: 'Microsoft.SharePoint.IdentityServices.IApplicationSecurityTokenServiceContract' Action: 'http://schemas.microsoft.com/sharepoint/2011/05/securitytokenservice/IApplicationSecurityTokenServiceContract/Issue' MessageId: 'urn:uuid:1ca84e12-c442-47bc-bbd4-ce7c03c82efa' c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:42.05  w3wp.exe (0x27A0)                        0x22DC SharePoint Foundation          Monitoring                     nasq Medium   Entering monitored scope (ExecuteWcfServerOperation). Parent No 
    06/04/2014 09:19:42.05  w3wp.exe (0x27A0)                        0x22DC SharePoint Foundation          Topology                       e5mb Medium   WcfReceiveRequest: LocalAddress: 'net.pipe://server241.domain.de/SecurityTokenServiceApplication/appsts.svc' Channel: 'System.ServiceModel.Channels.ServiceChannel' Action: 'http://schemas.microsoft.com/sharepoint/2011/05/securitytokenservice/IApplicationSecurityTokenServiceContract/Issue' MessageId: 'urn:uuid:1ca84e12-c442-47bc-bbd4-ce7c03c82efa' c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:42.06  w3wp.exe (0x27A0)                        0x22DC SharePoint Foundation          Monitoring                     b4ly Medium   Leaving Monitored Scope (ExecuteWcfServerOperation). Ausführungszeit=7,2382 c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:42.07  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Monitoring                     b4ly High     Leaving Monitored Scope (ExecuteWcfOperation:http://schemas.microsoft.com/sharepoint/2011/05/securitytokenservice/IApplicationSecurityTokenServiceContract/Issue). Ausführungszeit=203,2029 c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:42.13  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Monitoring                     nass High     [Forced due to logging gap, cached @ 06/04/2014 09:19:42.07, Original Level: Verbose] ____{0}={1} c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:42.13  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Monitoring                     b4ly High     Leaving Monitored Scope (Request self-issued token). Ausführungszeit=357,3104 c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:42.13  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Application Authentication     aiv3e High     Self-issued token request for '00000002-0000-0ff1-ce00-000000000000/server11.domain.de@domain.com' succeeded. c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:42.13  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Monitoring                     b4ly High     Leaving Monitored Scope (Get OAuth2 actor token). Ausführungszeit=379,5178 c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:42.13  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Monitoring                     b4ly High     Leaving Monitored Scope (Issue OAuth2 S2S application token). Ausführungszeit=385,563 c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:42.13  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Monitoring                     b4ly High     Leaving Monitored Scope (Authenticate OAuth2 Bearer challenge). Ausführungszeit=485,0216 c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:42.30  w3wp.exe (0x1A54)                        0x1970                                0x6FB7030                      nass High     [Forced due to logging gap, cached @ 06/04/2014 09:19:42.13, Original Level: Verbose] ____{0}={1} c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:42.31  w3wp.exe (0x1A54)                        0x1970 SharePoint Server Search       Exchange Integration           aiwxi Medium   SearchServiceApplication::ExchangeAdapter::SharePoint CorrelationId:c27e979c-d69c-c08b-5348-741d60765c0c; Exchange Request Id:48caa81b-9c1b-4783-9aa5-ad415e5afa28; Diagnostic Info: c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:42.31  w3wp.exe (0x1A54)                        0x1970 SharePoint Server Search       Exchange Integration           ai1pi Medium   Autodiscover Diagnostics EWS Client Version: 15.00.0847.030 c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:42.31  w3wp.exe (0x1A54)                        0x1970 SharePoint Server Search       Exchange Integration           ai1pj Medium   Autodiscover Diagnostics Response Headers: Transfer-Encoding: chunked  request-id: 48caa81b-9c1b-4783-9aa5-ad415e5afa28  client-request-id: c27e979c-d69c-c08b-5348-741d60765c0c  X-CalculatedBETarget: server12.domain.de  X-DiagInfo: server12  X-BEServer: server12  X-FEServer: server11  Cache-Control: private  Content-Type: text/xml; charset=utf-8  Date: Wed, 04 Jun 2014 07:19:41 GMT  Set-Cookie: X-BackEndCookie=OrganizationAnchor@=u56Lnp2ejJqBmp7MnMvLz53SzsjLnNLLnZ6b0p3Ix8jSys3HnMacms3JyMicgYHPyNDPy9DNz87L38/Ixc7GxcvN; expires=Fri, 04-Jul-2014 05:19:42 GMT; path=/autodiscover; secure; HttpOnly  Server: Microsoft-IIS/8.0  X-AspNet-Version: 4.0.30319  X-Powered-By: ASP.NET     c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:42.31  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Monitoring                     b4ly High     Leaving Monitored Scope (Microsoft.SharePoint.Portal.CollaborationMailboxInternalService.GetCollabMailboxViewInfo). Ausführungszeit=2235,6333 c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:42.33  w3wp.exe (0x1A54)                        0x1970 SharePoint Portal Server       Microfeeds                     aizmj High     serviceHost_RequestExecuted c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:42.38  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          CSOM                           agw11 Medium   End CSOM Request. Duration=2724 milliseconds. c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:42.45  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Topology                       ahg9p High     [Forced due to logging gap, cached @ 06/04/2014 09:19:42.40, Original Level: Verbose] Completed deserializing the type named {0} and with id {1}. c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:42.45  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Monitoring                     aeg6b High     [Forced due to logging gap, Original Level: Verbose] SPServiceDiagnosticsContextBehavior ws called end Invoke.  c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:42.46  OWSTIMER.EXE (0x2438)                    0x3098 SharePoint Foundation          Monitoring                     nasq Medium   Entering monitored scope (Timer Job MySite-Instantiation-Interactive-Request-Queue). Parent No fa410232-c87e-4637-8ba9-edb280658f9c
    06/04/2014 09:19:42.58  w3wp.exe (0x1A54)                        0x1970 SharePoint Foundation          Asp Runtime                    aj1kp High     [Forced due to logging gap, Original Level: Verbose] SPRequestModule.PreSendRequestHeaders c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:42.60  w3wp.exe (0x1A54)                        0x1630 SharePoint Foundation          Monitoring                     b4ly Medium   Leaving Monitored Scope (Request (POST:https://server241.domain.de:82/_vti_bin/client.svc/ProcessQuery)). Ausführungszeit=6978,6989 c27e979c-d69c-c08b-5348-741d60765c0c
    06/04/2014 09:19:43.69  w3wp.exe (0x3490)                        0x22FC SharePoint Server Search       Query                          ac3iq High     Ims::EndPoints: old: net.tcp://server241/C12503/QueryProcessingComponent1/ImsQueryInternal;, new: net.tcp://server241/C12503/QueryProcessingComponent1/ImsQueryInternal;

    Mir ist noch aufgefallen, dass die ID, die beim abfragen des AppPrincipalName eine andere ist, als im Exchange die PartnerApplicationID. kann das ebenfalls damit zusammenhängen?

    Gruß

    Marc

    Mittwoch, 4. Juni 2014 07:48
  • Sorry, habs erst heute gesehen. Mit interner Domain, meine ich die xxxx.local
    Donnerstag, 12. Juni 2014 10:18
  • Hi,

    das Problem hat sich gelöst. Hier das Szenario:

    Bei uns wird Exchange 2010 und Exchange 2013 im Mischbetrieb eingesetzt, deshalb mussten wir eine "Arbitration-Mailbox" per Konsole erstellen, damit die Requests der Site Mailboxes an Exchange 2013 gehen.

    Zudem muss dann der Parameter "ExchangeSiteMailboxDomain" im Skript "Set-SiteMailboxConfig.ps1" die smtp Adresse der Arbitration-Mailbox sein.

    Damit hat sich das Problem gelöst und der Error Code 3 wurde nicht mehr angezeigt.

    Montag, 16. Juni 2014 10:18