Exchange 2010 SP3 - schanell errors

Hi there.
Exchange 2010 SP3 with latest CU (v8 i think). It's installed on Domain Controller (I know, not recommened - LONG STORY).
We recieved "a lot of Schanell" errors in the past days (8 errors).
Should we be concirned?
bostjanc

Hi,
Below links might help you..
- https://social.technet.microsoft.com/Forums/windowsserver/en-US/55d3ef33-caf0-41d3-874d-fc1ad65455cb/event-id-36887-source-schannel-error-the-following-fatal-alert-was-received-0?forum=winservergen
Managing SSL for a Client Access Server
http://technet.microsoft.com/en-us/library/bb310795.aspx
How to Setup SSL on IIS 7
http://learn.iis.net/page.aspx/144/how-to-setup-ssl-on-iis-7/

Similar Messages

  • Sharepoint 2013 vs Exchange 2010 SP3 search (Error while crawling LOB contents)

    Hi there:
    We are trying to solve the problem: ERROR CRAWLING LOB CONTENTS when we wish to search Exchange 2010 SP3 public folder content on Sharepoint 2013 Foundation.
    Quick briefing:
    Followed this instructions:
    http://technet.microsoft.com/en-us/library/jj591608(v=office.15).aspx
    * Created CRAWL RULE
    - Used Domain Admin for content access ---> IS THIS WRONG?
    - Domain Admin can access public folder thru Outlook Web Access (checked)
    - Included all items in this path
    PRINTSCREEN 1
    * Added a content source for Exchange Server public folders
    - Logged to Outlook Web Access with domain admin, expanded Public folders and opened 1st subfolder in new window and copied the address
    - Logged to Outlook Web Access with domain admin, expanded Public folders and opened 2nd subfolder in new window and copied the address
    PRINTSCREEN2
    * Did a FULL CRAWL
    PROBLEM:
    - Search results does not throw "correct data". Some items are not being found
    CRAWL LOG is reporting: Error while crawling LOB contents
    Detailed error message:
    https://mail.domain.com/OWA/?ae=Folder&id=PSF.LgAAAAAaRHOQqmYRzZvIAKoAL8RaAwAnt2ed15IATLg8XoXLNj4EAAAAXsN8AAAB&t=IPF.Note
    Error while crawling LOB contents.
    Error caused by exception: Microsoft.BusinessData.Infrastructure.BdcException
    The shim execution failed unexpectedly - Exception has been thrown by the target of an invocation..:
    System.InvalidOperationException An internal server error occurred.
    Try again later.; SearchID = 4E8542D3-48EF-404E-8025-8D9AAEFE777A )
    We thought it's a throttling issue / found possible solution:
    http://powersearching.wordpress.com/2013/07/23/exchange-public-folders-search-fail-error-while-crawling-lob-contents/
    Tried it, still same Error messages, problem not resolved.
    Any hints? Please advise.
    With best regards
    bostjanc

    Hi Bostjan,
    From the error message, the issue might be caused by throttling policy on Exchange side. And the article you posted provides the right solution, some modification to the solution and please try again.
    For throttling policy part
    1.Execute the command for Set-ThrottlingPolicy
    Set-ThrottlingPolicy SharePoint -RCAMaxConcurrency Unlimited -EWSMaxConcurrency Unlimited -EWSMaxSubscriptions Unlimited -CPAMaxConcurrency Unlimited -EwsCutoffBalance Unlimited -EwsMaxBurst Unlimited -EwsRechargeRate Unlimited
    2.Execute the command Get-ThrottlingPolicy SharePoint to double confirm the policy setting has been successfully executed
    For registry key part
    1. Start Registry Editor (regedit).
    2. Navigate to the following registry subkey:
    \\HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
    3. Right-click ParametersSystem, point to New, and then click Key.
    A new key is created in the console tree.
    4. Rename the key MaxObjsPerMapiSession, and then press Enter.
    5. Right-click MaxObjsPerMapiSession, point to New, and then click DWORD (32-bit) Value.
    The new value is created in the result pane.
    6. Rename the key to <Object_type>, where <Object_type> is the name of the registry object type that you're modifying. For example, to modify the number of messages that can be opened, use objtMessage. Press Enter.
    7. Right-click the newly created key, and then click Modify.
    8. In the Value data box, type the number of objects that you want to limit this entry to, and then click OK. For example, type 350 to increase the value for the object.
    9. Restart the Microsoft Exchange Information Store service.
    If it still doesn’t help, please check ULS log for related error message.
    Regards,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected] .
    Rebecca Tu
    TechNet Community Support

  • The Test-OrganizationRelationship function on Exchange 2010 SP3 Rollup4 error

    Hi
      If I run Test-OrganizationRelationship function on Exchange 2010 SP3 Rollup4 the fallowing error appear:
    [PS] C:\WINDOWS\system32>Test-OrganizationRelationship -Identity "emag" -UserIdentity [email protected] -verbose
    VERBOSE: [12:24:44.359 GMT] Test-OrganizationRelationship : Active Directory session settings for
    'Test-OrganizationRelationship' are: View Entire Forest: 'False', Default Scope: 'hq.flanco.ro', Configuration Domain
    Controller: 'CALYPSO.hq.flanco.ro', Preferred Global Catalog: 'CALYPSO.hq.flanco.ro', Preferred Domain Controllers: '{
    CALYPSO.hq.flanco.ro }'
    VERBOSE: [12:24:44.359 GMT] Test-OrganizationRelationship : Runspace context: Executing user: hq.flanco.ro/FLANCO -
    Users/HQ/IT/Marian NICA, Executing user organization: , Current organization: , RBAC-enabled: Enabled.
    VERBOSE: [12:24:44.359 GMT] Test-OrganizationRelationship : Beginning processing &
    VERBOSE: [12:24:44.359 GMT] Test-OrganizationRelationship : Instantiating handler with index 0 for cmdlet extension
    agent "Admin Audit Log Agent".
    VERBOSE: [12:24:44.391 GMT] Test-OrganizationRelationship : Current ScopeSet is: { Recipient Read Scope: {{, }},
    Recipient Write Scopes: {{, }}, Configuration Read Scope: {{, }}, Configuration Write Scope(s): {{, }, }, Exclusive
    Recipient Scope(s): {}, Exclusive Configuration Scope(s): {} }
    VERBOSE: [12:24:44.391 GMT] Test-OrganizationRelationship : Searching objects "[email protected]" of type "ADUser"
    under the root "$null".
    VERBOSE: [12:24:44.406 GMT] Test-OrganizationRelationship : Previous operation run on global catalog server
    'CALYPSO.hq.flanco.ro'.
    VERBOSE: [12:24:44.406 GMT] Test-OrganizationRelationship : Searching objects "emag" of type "OrganizationRelationship"
    under the root "$null".
    VERBOSE: [12:24:44.406 GMT] Test-OrganizationRelationship : Previous operation run on domain controller
    'CALYPSO.hq.flanco.ro'.
    VERBOSE: Test that organization relationships are properly configured.
    VERBOSE: [12:24:44.406 GMT] Test-OrganizationRelationship : Resolved current organization: .
    VERBOSE: [12:24:44.406 GMT] Test-OrganizationRelationship : Calling the Microsoft Exchange Autodiscover service for the
    remote federation information.
    VERBOSE: [12:24:44.983 GMT] Test-OrganizationRelationship : The Autodiscover call succeeded for the following URL:
    https://autodiscover.emag.ro/autodiscover/autodiscover.svc.
    VERBOSE: [12:24:44.983 GMT] Test-OrganizationRelationship : The Autodiscover call succeeded for the following URL:
    https://autodiscover.emag.ro/autodiscover/autodiscover.svc.
    VERBOSE: [12:24:44.983 GMT] Test-OrganizationRelationship : Generating delegation token for user [email protected]
    for application FYDIBOHF25SPDLT.exchangedelegation.emag.ro.
    VERBOSE: [12:24:46.138 GMT] Test-OrganizationRelationship : The delegation token was successfully generated.
    VERBOSE: [12:24:46.138 GMT] Test-OrganizationRelationship : The Microsoft Exchange Autodiscover service is being called
    to determine the remote organization relationship settings.
    VERBOSE: [12:24:46.138 GMT] Test-OrganizationRelationship : The Client will call the Microsoft Exchange Autodiscover
    service using the following URL: https://autodiscover.emag.ro/autodiscover/autodiscover.svc/WSSecurity.
    VERBOSE: [12:24:46.185 GMT] Test-OrganizationRelationship : The Microsoft Exchange Autodiscover service failed to be
    called at 'https://autodiscover.emag.ro/autodiscover/autodiscover.svc/WSSecurity' because the following error occurred:
    SoapException.Code =
    http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd:InvalidSecurityToken
    Exception:
    System.Web.Services.Protocols.SoapHeaderException: An error occurred when processing the security tokens in the
    message.
       at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse
    response, Stream responseStream, Boolean asyncCall)
       at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
       at Microsoft.Exchange.SoapWebClient.CustomSoapHttpClientProtocol.<>c__DisplayClass4.<Invoke>b__3()
       at
    Microsoft.Exchange.SoapWebClient.HttpAuthenticator.NoHttpAuthenticator.AuthenticateAndExecute[T](SoapHttpClientProtocol
    client, AuthenticateAndExecuteHandler`1 handler)
       at Microsoft.Exchange.SoapWebClient.SoapHttpClientAuthenticator.AuthenticateAndExecute[T](SoapHttpClientProtocol
    client, AuthenticateAndExecuteHandler`1 handler)
       at
    Microsoft.Exchange.SoapWebClient.AutoDiscover.DefaultBinding_Autodiscover.GetOrganizationRelationshipSettings(GetOrgani
    zationRelationshipSettingsRequest Request)
       at
    Microsoft.Exchange.Management.Sharing.TestOrganizationRelationship.<>c__DisplayClass8.<GetInvokeDelegate>b__7(DefaultBi
    nding_Autodiscover binding)
       at
    Microsoft.Exchange.SoapWebClient.AutodiscoverClient.<>c__DisplayClassf.<InvokeAndFollowSecureRedirects>b__c(IWebProxy
    webProxy)
       at Microsoft.Exchange.SoapWebClient.AutodiscoverClient.InvokeWithWebProxy(String url, InvokeWithWebProxyDelegate
    invokeWithWebProxy)
       at Microsoft.Exchange.SoapWebClient.AutodiscoverClient.InvokeAndFollowSecureRedirects(InvokeDelegate invokeDelegate,
    Uri url)
       at Microsoft.Exchange.SoapWebClient.AutodiscoverClient.InvokeForUrl(InvokeDelegate invokeDelegate, Uri url)
    VERBOSE: [12:24:46.185 GMT] Test-OrganizationRelationship : The Autodiscover call failed.
    RunspaceId  : b3b378f5-d912-4042-b578-e949b54da4c1
    Identity    :
    Id          : AutodiscoverServiceCallFailed
    Status      : Error
    Description : The Autodiscover call failed.
    IsValid     : True
    VERBOSE: [12:24:46.185 GMT] Test-OrganizationRelationship : Admin Audit Log: Entered Handler:OnComplete.
    VERBOSE: [12:24:46.185 GMT] Test-OrganizationRelationship : Ending processing &
        

    It's not this, is it -
    http://johanveldhuis.nl/en/error-occurred-processing-security-tokens-message/ ?

  • After Exchange 2010 SP3 upgrade, UAG publised OWA is throwing a "You do not have permissions to view this folder or page" error

    Hi,
    We have an issue with our OWA page.  We are currently publishing OWA via UAG.
    We recently upgraded to Exchange 2010 SP3 and then SP3 Rollup7.  Since the upgrade, we are keep getting the following error after entering our credentials on the login page.  I've tried with every possible browser. 
    You do not have permissions to view this folder or page
    Strangely enough, the mobile phones are sending and receiving emails just fine, the phones use the same OWA link, so it's not an authentication issue, the phones login into the UAG servers with no issues.  I can see this on the Active Sessions screen
    on Web Monitor. 
    I've attempted to connect to the OWA by bypassing the UAG server, so putting in the local OWA address of one of my Exchange servers, it works... so the OWA page is up and running. 
    No error logs get generated on Web Monitor when we receive the permission error, I think this is because it's past authentication, it's on the Exchange layer. 
    Any insight would be helpful?  I'm assuming something changed on the Exchange side after the upgrade.
    Just in case, I've upgraded the UAG and TMG servers to the latest SP and Rollup packets.
    UAG > SP4
    TMG > SP2 Rollup 5

    I've found a solution; UAG requires Basic Authentication over OWA.  For some reason Integrated Windows Authentication got turned on after the SP3 upgrade.
    http://technet.microsoft.com/en-us/library/ee921443.aspx
    Turning Integrated Windows Authentication off via the Client Access OWA settings resolved the issue.  Though beware, you
    have do this on all your Client Access servers.  

  • [SOLVED] Can't add a node to the cluster with error (Exchange 2010 SP3 DAG Windows Server 2012)

    Hi there!
    I have a problem which makes me very angry already :)
    I have two servers Exchange 2010 SP3 with MB role started on Windows Server 2012. I decided to create a DAG.
    I have created the prestaged AD object for the cluster called msc-co-exc-01c, assigned necessary permissions and disabled it. Allowed through the Windows Firewall traffic between nodes and prepared the File Share Witness server.
    Then I have tried to add nodes. The first node has been added successfully, but the second node doesn't want to be added :). Now I can add only one node to the DAG. I tried to add different servers first, but only the first one was added.
    LOGS on the second nodes: 
    Application Log
    "Failed to initialize cluster with error 0x80004005." (MSExchangeIS)
    Failover Clustering Diagnostic Log
    "[VER] Could not read version data from database for node msc-co-exc-04v (id 1)."
    CMDLET Error:
    Summary: 1 item(s). 0 succeeded, 1 failed.
    Elapsed time: 00:06:21
    MSC-CO-EXC-02V
    Failed
    Error:
    A database availability group administrative operation failed. Error: The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode()
    (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed. [Server: msc-co-exc-04v.int.krls.ru]
    An Active Manager operation failed. Error An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed..
    This operation returned because the timeout period expired
    Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.174.1&t=exchgf1&e=ms.exch.err.ExC9C315
    Warning:
    Network name 'msc-co-exc-01c' is not online. Please check that the IP address configuration for the database availability group is correct.
    Warning:
    The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2014-11-17_13-54-56.543_add-databaseavailabiltygroupserver.log".
    Exchange Management Shell command attempted:
    Add-DatabaseAvailabilityGroupServer -MailboxServer 'MSC-CO-EXC-02V' -Identity 'msc-co-exc-01c'
    Elapsed Time: 00:06:21
    UPD:
    when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
    I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
    on both nodes.
    It's confused me, because there is normal connectivity between these DAG members through the main interface.
    Please, help me if you can.

    Hi, Jared! Thank you for the reply.
    Of course I did it already :) I have new info:
    when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
    I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
    on both nodes.
    It's confused me, because there is normal connectivity between these DAG members through the main interface.

  • Exchange 2010 SP3 Move Mailbox fails on every mailbox with Fatal error MapiExceptionJetErrorIndexNotFound has occurred

    We are currently running Small Business Server 2003 with Exchange 2003 SP2 and are migrating to Server 2008 R2 with Exchange 2010 SP3 as an interim before moving to Server 2012 R2 with Exchange 2013 SP1. The mailbox move reaches 95% before failing with the
    message "Fatal error MapiExceptionJetErrorIndexNotFound has occurred.
    Error details: MapiExceptionJetErrorIndexNotFound: Unable to copy to target. (hr=0x80004005, ec=-1404)
    Diagnostic context:
        Lid: 45095   EMSMDB.EcDoRpcExt2 called [length=78]
        Lid: 61479   EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=75][latency=0]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropGetPropsSpecific [7]
        Lid: 21921   StoreEc: 0x40380   
        Lid: 31418   --- ROP Parse Done ---
        Lid: 45095   EMSMDB.EcDoRpcExt2 called [length=45]
        Lid: 61479   EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=140][latency=0]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropGetReceiveFolderTable [104]
        Lid: 31418   --- ROP Parse Done ---
        Lid: 45095   EMSMDB.EcDoRpcExt2 called [length=69]
        Lid: 61479   EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=48][latency=0]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropGetAllPerUserLtids [125]
        Lid: 17082   ROP Error: 0xFFFFFA84
        Lid: 29793  
        Lid: 21921   StoreEc: 0xFFFFFA84
        Lid: 31418   --- ROP Parse Done ---
        Lid: 22753  
        Lid: 21817   ROP Failure: 0xFFFFFA84
        Lid: 25738  
        Lid: 18570   StoreEc: 0xFFFFFA84
        Lid: 23370   StoreEc: 0xFFFFFA84
        Lid: 24302  
        Lid: 32494   StoreEc: 0xFFFFFA84
       at Microsoft.Mapi.MapiExceptionHelper.ThrowIfErrorOrWarning(String message, Int32 hresult, Boolean allowWarnings, SafeExInterfaceHandle iUnknown, Exception innerException)
       at Microsoft.Mapi.MapiUnk.ThrowIfErrorOrWarning(String message, Int32 hr)
       at Microsoft.Mapi.MapiProp.CopyTo(MapiProp destProp, Boolean reportProgress, CopyPropertiesFlags copyPropertiesFlags, Boolean copySubObjects, ICollection`1 excludeTags)
       at Microsoft.Mapi.MapiProp.ExportObjectHelper(IMapiFxProxy dest, PropTag[] tags, CopyPropertiesFlags copyPropertiesFlags, Boolean useCopyProps)
       at Microsoft.Mapi.MapiProp.ExportObject(IMapiFxProxy fxProxy, CopyPropertiesFlags copyPropertiesFlags, PropTag[] excludeTags)
       at Microsoft.Exchange.MailboxReplicationService.LocalSourceMailbox.Microsoft.Exchange.MailboxReplicationService.ISourceMailbox.CopyTo(IFxProxy fxProxy, PropTag[] excludeTags)
       at Microsoft.Exchange.MailboxReplicationService.SourceMailboxWrapper.<>c__DisplayClass7.<Microsoft.Exchange.MailboxReplicationService.ISourceMailbox.CopyTo>b__6()
       at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
       at Microsoft.Exchange.MailboxReplicationService.SourceMailboxWrapper.Microsoft.Exchange.MailboxReplicationService.ISourceMailbox.CopyTo(IFxProxy destMailbox, PropTag[] excludeProps)
       at Microsoft.Exchange.MailboxReplicationService.MailboxMover.FinalSyncCopyMailboxData()
       at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.ForeachMailboxContext(MailboxMoverDelegate del)
       at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.FinalSync(Object[] wiParams)
       at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
    Error context: --------
    Operation: ISourceMailbox.CopyTo
    OperationSide: Source"
    This is happening on every mailbox we attempt to move. Any help would be appreciated

    Thanks for responding
    I'm already using BadItemLimit of 50. The largest corrupt message that was skipped is 10.
    We're on Small Business Server Standard Edition which only permits one mailbox store. I should mention that the interim machine (where Exchange 2010 is installed) is a Hyper V virtual machine
    Here is the entire message from the log:
    11/28/2014 7:18:07 PM [VRTL-SVR2008] 'PeacePresbyterianChurch.local/MyBusiness/Users/SBSUsers/Dev Mathura' created move request.
    11/28/2014 7:18:27 PM [VRTL-SVR2008] The Microsoft Exchange Mailbox Replication service 'VRTL-SVR2008.PeacePresbyterianChurch.local' (14.3.123.2 caps:07) is examining the request.
    11/28/2014 7:18:27 PM [VRTL-SVR2008] Connected to target mailbox 'Primary (d3391cdd-bc37-41ad-9e44-9f8880c47270)', database 'Mailbox Database 0224662151', Mailbox server 'VRTL-SVR2008.PeacePresbyterianChurch.local' Version 14.3 (Build 123.0).
    11/28/2014 7:18:27 PM [VRTL-SVR2008] Connected to source mailbox 'Primary (d3391cdd-bc37-41ad-9e44-9f8880c47270)', database 'PEACE-SERVER\First Storage Group\Mailbox Store (PEACE-SERVER)', Mailbox server 'peace-server.PeacePresbyterianChurch.local' Version
    6.0 (Build 7654.0).
    11/28/2014 7:18:38 PM [VRTL-SVR2008] Request processing started.
    11/28/2014 7:18:38 PM [VRTL-SVR2008] Mailbox signature will not be preserved for mailbox 'Primary (d3391cdd-bc37-41ad-9e44-9f8880c47270)'. Outlook clients will need to restart to access the moved mailbox.
    11/28/2014 7:18:38 PM [VRTL-SVR2008] Source mailbox information before the move:
    Regular Items: 20, 1.906 MB (1,998,818 bytes)
    Regular Deleted Items: 3, 7.803 KB (7,990 bytes)
    FAI Items: 20, 0 B (0 bytes)
    FAI Deleted Items: 0, 0 B (0 bytes)
    11/28/2014 7:18:39 PM [VRTL-SVR2008] Initializing folder hierarchy in mailbox 'Primary (d3391cdd-bc37-41ad-9e44-9f8880c47270)': 31 folders total.
    11/28/2014 7:18:40 PM [VRTL-SVR2008] Folder hierarchy initialized for mailbox 'Primary (d3391cdd-bc37-41ad-9e44-9f8880c47270)': 31 folders total.
    11/28/2014 7:18:40 PM [VRTL-SVR2008] Stage: CreatingInitialSyncCheckpoint. Percent complete: 15.
    11/28/2014 7:18:40 PM [VRTL-SVR2008] Stage: LoadingMessages. Percent complete: 20.
    11/28/2014 7:18:40 PM [VRTL-SVR2008] Mailbox 'Primary (d3391cdd-bc37-41ad-9e44-9f8880c47270)' contains 3 soft-deleted items (7.803 KB (7,990 bytes)). They won't be migrated.
    11/28/2014 7:18:40 PM [VRTL-SVR2008] Stage: CopyingMessages. Percent complete: 25.
    11/28/2014 7:18:40 PM [VRTL-SVR2008] Copy progress: 0/38 messages, 0 B (0 bytes)/1.906 MB (1,998,550 bytes).
    11/28/2014 7:18:41 PM [VRTL-SVR2008] Messages have been enumerated successfully. 38 items loaded. Total size: 1.906 MB (1,998,550 bytes).
    11/28/2014 7:18:43 PM [VRTL-SVR2008] Initial seeding completed, 38 items copied, total size 1.906 MB (1,998,550 bytes).
    11/28/2014 7:18:44 PM [VRTL-SVR2008] Final sync has started.
    11/28/2014 7:18:45 PM [VRTL-SVR2008] Stage: FinalIncrementalSync. Percent complete: 95.
    11/28/2014 7:18:46 PM [VRTL-SVR2008] Fatal error MapiExceptionJetErrorIndexNotFound has occurred.
    Error details: MapiExceptionJetErrorIndexNotFound: Unable to copy to target. (hr=0x80004005, ec=-1404)
    Diagnostic context:
        Lid: 45095   EMSMDB.EcDoRpcExt2 called [length=78]
        Lid: 61479   EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=75][latency=0]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropGetPropsSpecific [7]
        Lid: 21921   StoreEc: 0x40380  
        Lid: 31418   --- ROP Parse Done ---
        Lid: 45095   EMSMDB.EcDoRpcExt2 called [length=45]
        Lid: 61479   EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=140][latency=0]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropGetReceiveFolderTable [104]
        Lid: 31418   --- ROP Parse Done ---
        Lid: 45095   EMSMDB.EcDoRpcExt2 called [length=69]
        Lid: 61479   EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=48][latency=0]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropGetAllPerUserLtids [125]
        Lid: 17082   ROP Error: 0xFFFFFA84
        Lid: 29793 
        Lid: 21921   StoreEc: 0xFFFFFA84
        Lid: 31418   --- ROP Parse Done ---
        Lid: 22753 
        Lid: 21817   ROP Failure: 0xFFFFFA84
        Lid: 25738 
        Lid: 18570   StoreEc: 0xFFFFFA84
        Lid: 23370   StoreEc: 0xFFFFFA84
        Lid: 24302 
        Lid: 32494   StoreEc: 0xFFFFFA84
       at Microsoft.Mapi.MapiExceptionHelper.ThrowIfErrorOrWarning(String message, Int32 hresult, Boolean allowWarnings, SafeExInterfaceHandle iUnknown, Exception innerException)
       at Microsoft.Mapi.MapiUnk.ThrowIfErrorOrWarning(String message, Int32 hr)
       at Microsoft.Mapi.MapiProp.CopyTo(MapiProp destProp, Boolean reportProgress, CopyPropertiesFlags copyPropertiesFlags, Boolean copySubObjects, ICollection`1 excludeTags)
       at Microsoft.Mapi.MapiProp.ExportObjectHelper(IMapiFxProxy dest, PropTag[] tags, CopyPropertiesFlags copyPropertiesFlags, Boolean useCopyProps)
       at Microsoft.Mapi.MapiProp.ExportObject(IMapiFxProxy fxProxy, CopyPropertiesFlags copyPropertiesFlags, PropTag[] excludeTags)
       at Microsoft.Exchange.MailboxReplicationService.LocalSourceMailbox.Microsoft.Exchange.MailboxReplicationService.ISourceMailbox.CopyTo(IFxProxy fxProxy, PropTag[] excludeTags)
       at Microsoft.Exchange.MailboxReplicationService.SourceMailboxWrapper.<>c__DisplayClass7.<Microsoft.Exchange.MailboxReplicationService.ISourceMailbox.CopyTo>b__6()
       at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
       at Microsoft.Exchange.MailboxReplicationService.SourceMailboxWrapper.Microsoft.Exchange.MailboxReplicationService.ISourceMailbox.CopyTo(IFxProxy destMailbox, PropTag[] excludeProps)
       at Microsoft.Exchange.MailboxReplicationService.MailboxMover.FinalSyncCopyMailboxData()
       at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.ForeachMailboxContext(MailboxMoverDelegate del)
       at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.FinalSync(Object[] wiParams)
       at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
    Error context: --------
    Operation: ISourceMailbox.CopyTo
    OperationSide: Source
    Primary (d3391cdd-bc37-41ad-9e44-9f8880c47270)
    PropTags: [ContainerHierarchy; ContainerContents]
    11/28/2014 7:18:46 PM [VRTL-SVR2008] Relinquishing job.

  • Exchange 2010 SP3 mailbox role installation error

    Hello.
    I can't install the Mailbox role on a Windows 2008 R2 server, the first Exchange in the domain and forest (2 dcs in the domain).
    Client Access Role and Hub Transport Role installed correctly.
    Setup preparations - without an error.
    Started the Exchange 2010 SP3 Installation, which start correctly, all prerequisites are seems to be ok. When arriving on the Mailbox Roles it make this error:
    02.05.2014 13:42:46.0634] [2] [ERROR] Active Directory operation failed on <dc fqdn>. This error is not retriable. Additional information: An attempt was made to modify an object to include an attribute that is not legal for its class.
    Active directory response: 0000207D: UpdErr: DSID-0315121C, problem 6002 (OBJ_CLASS_VIOLATION), data -1731808180
    [02.05.2014 13:42:46.0634] [2] [ERROR] An object class violation occurred.
    [02.05.2014 13:42:46.0634] [2] Ending processing enable-mailbox
    [02.05.2014 13:42:46.0649] [1] The following 1 error(s) occurred during task execution:
    [02.05.2014 13:42:46.0649] [1] 0.  ErrorRecord: Active Directory operation failed on <dc fqdn>. This error is not retriable. Additional information: An attempt was made to modify an object to include an attribute that is not legal for its class.
    Active directory response: 0000207D: UpdErr: DSID-0315121C, problem 6002 (OBJ_CLASS_VIOLATION), data -1731808180
    [02.05.2014 13:42:46.0649] [1] 0.  ErrorRecord: Microsoft.Exchange.Data.Directory.ADOperationException: Active Directory operation failed on <dc fqdn>. This error is not retriable. Additional information: An attempt was made to modify an object to
    include an attribute that is not legal for its class.
    Active directory response: 0000207D: UpdErr: DSID-0315121C, problem 6002 (OBJ_CLASS_VIOLATION), data -1731808180
     ---> System.DirectoryServices.Protocols.DirectoryOperationException: An object class violation occurred.
       at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
       at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
       at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation, IAccountingObject budget, Nullable`1 clientSideSearchTimeout)
       at Microsoft.Exchange.Data.Directory.ADSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)
       --- End of inner exception stack trace ---
       at Microsoft.Exchange.Data.Directory.ADSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)
       at Microsoft.Exchange.Data.Directory.ADSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)
       at Microsoft.Exchange.Data.Directory.ADSession.Save(ADObject instanceToSave, IEnumerable`1 properties)
       at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientSession.Microsoft.Exchange.Data.IConfigDataProvider.Save(IConfigurable instance)
       at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalProcessRecord()
       at Microsoft.Exchange.Management.RecipientTasks.EnableMailbox.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
    [02.05.2014 13:42:46.0649] [1] [ERROR] The following error was generated when "$error.Clear();
              if (!$RoleIsDatacenter)
                $arbUsers = @(get-user -Filter {lastname -eq "MSExchApproval 1f05a927-3be2-4fb9-aa03-b59fe3b56f4c"} -IgnoreDefaultScope -ResultSize 1);
                if ($arbUsers.Length -ne 0)
                  $mbxname = $arbUsers[0].name;
                  $mbxs = @( get-mailbox -arbitration -Filter {name -eq $mbxname} -IgnoreDefaultScope -resultSize 1 );
                  if ( $mbxs.length -eq 0)
                    $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
                    if ($dbs.Length -ne 0)
                      enable-mailbox -Arbitration -identity $arbUsers[0] -database $dbs[0].Identity;
            " was run: "Active Directory operation failed on <dc fqdn>. This error is not retriable. Additional information: An attempt was made to modify an object to include an attribute that is not legal for
    its class.
    Active directory response: 0000207D: UpdErr: DSID-0315121C, problem 6002 (OBJ_CLASS_VIOLATION), data -1731808180
    [02.05.2014 13:42:46.0649] [1] [ERROR] Active Directory operation failed on <dc fqdn>. This error is not retriable. Additional information: An attempt was made to modify an object to include an attribute that is not legal for its class.
    Active directory response: 0000207D: UpdErr: DSID-0315121C, problem 6002 (OBJ_CLASS_VIOLATION), data -1731808180
    [02.05.2014 13:42:46.0649] [1] [ERROR] An object class violation occurred.
    [02.05.2014 13:42:46.0649] [1] [ERROR-REFERENCE] Id=SystemAttendantDependent___04bbd8c4a86b4d2c9403cdddf5b39579 Component=EXCHANGE14:\Current\Release\Transport\BCM\Moderated Transport
    [02.05.2014 13:42:46.0649] [1] Setup is stopping now because of one or more critical errors.
    [02.05.2014 13:42:46.0649] [1] Finished executing component tasks.
    [02.05.2014 13:42:46.0712] [1] Ending processing Install-MailboxRole
    Any help would be appreciate.
    Thanks,
    Igor K.

    Hi,
    The above error may occur when the federated built-in e-mail account that links to the computer account no longer exists or the federated built-in e-mail account in the Active Directory service is corrupted.
    I recommend you follow the steps below for troubleshooting:
    1. Remove the FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 e-mail account by using the ADSIEdit tool.
    a. Run adsiedit.msc.
    b. Locate the Default Naming Context node, and then locate to the CN=Users container.
    c. Locate and then right-click the CN=FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 container. Then, click Delete.
    2.Rerun the Exchange Server 2010 Mailbox role setup application.
    3.Create a new federated e-mail account by using the following cmdlet:
    New-Mailbox -Arbitration -Name FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 -UserPrincipalName
    FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042@<Default_Accepted_Domain>
    Hope it helps.
    If you need further assistance, please feel free to let me know.
    Best regards,
    Amy
    Amy Wang
    TechNet Community Support

  • SME 7.1 not working with Exchange 2010 SP3 UR8v2 and OnTap 8.2.3 7mode

    Followed IMT and installed software that NetApp said would work.Ontap 8.2.3 7-modevmWare 5.0 SP3Microsoft Windows Server 2008 R2 SP1Exchange 2010 SP3 UR8v2NetApp Host Tools 6.0.2SnapDrive 7.1.1SME 7.1 Everything connects fine.  SnapDrive sees my drives.  SME connects to Exchange Server.  However in the process of configuring SME, I get the following error.  I have followed knowledge base article and increased the timeout of DFM connection in registry, but that has not solved the problem.  Has anyone run into this before?  SME 6.1 works fine, but is not compatible with SnapDrive 7.1.1 (causes verifications to fail because server can't mount clone) and lower SnapDrive versions are not compatible with Ontap 8.2.3.  I am in a real bind here. Thanks in advance. 

    the following configuration for SME 7.1 is no longer supported: Windows Server 2008 R2Exchange 2010 SP3 RU1 – RU5WMF/PowerShell 3.0SME 7.1 The supported configuration will now be: Windows Server 2008 R2Exchange 2010 SP3 RU5WMF/PowerShell 4.0SME 7.1 this is because Microsoft does not support WMF 3.0 on Server 2008 R2 running Exchange 2010 SP3, with any RU version.SME 7.1 requires a minimum of PowerShell 3.0 (part of WMF 3.0) in order to run. Feel free to review the Exchange Server Supportability Matrix located here: https://technet.microsoft.com/en-us/library/ff728623%28v=exchg.150%29.aspx. All existing documentation (ISG, Admin Guide, IMT) will be updated shortly to reflect this change in requirements. hope that helps,Domenico.

  • Exchange 2010 SP3 - Delayed emails with XLSM attachments...

    Running Exchange 2010 SP3 Rollup 5.  Clients running Windows 7 and Office 2010 Pro Plus SP2.  Have one specific user / client that when sending emails with an XLSM attachment around 5:30AM, the email is delayed getting to the Exchange server and
    is delayed up to 16 hours.  Unfortunately, this is a random occurrence, and not necessarily easy to duplicate.
    The Sent Items on the Outlook client reflect the correct sent time, but the Message Tracking Log on the Exchange server shows the server did not receive the email until approximately 12 to 16 hours later.
    The desktop is a shared system and this issue appears to be isolated to the user's profile, AD account, or Exchange.  I've literally blown away the users local profile and reconfigured it with no resolution.
    Any suggestions are greatly appreciated.
    Fuel

    Hi,
    Please verify whether there is any error/warning/information message left in App log. If yes, please paste the details without sensitive information.
    I suggest re-send a .xlsm attachment for testing to verify whether it delays.
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Exchange 2010 SP3 UR9 OWA users cannot open mail items

    We recently had users reporting unable to open items in OWA.  Issue is confirmed across all CAS servers.
    Issue started while on Exchange 2010 SP3 UR8v2, we upgraded to Exchange Server 2010 SP3 UR9 during troubleshooting.
    3 AD Site DAG, multi-role servers
    So far we have done the following to troubleshoot:
    * Check security propagation for account permissions.
    * Check security on all virtual directories.
    * Check permissions on web.config
    * Re-run PrepareAD
    * Uninstall and reinstall CAS role
    Please review the errors below and let me know if you have any words of wisdom on this issue.  Thanks!
    Errors:
    Request
    Url: https://domain.com:443/owa/forms/premium/SubPageEventHandler.aspx?ae=Item&a=Preview&t=IPM.Conversation&id=CID.K5jy5dmxQru9sRoituQBvQ%3d%3d.LgAAAAD5wKVzMPRWToarE%2bpbowlJAQAqvhe3P6jjT4tregHxbY2pANbZjrf2AAAB.1DEA1tmOt%2fIAAAAAiIUWAAAAAAA%3d&calist=&canary=BV_LDf9RIkOwB1AREM0QuJ6gLZ_9QNIIWwpFOZKWH-iRvFnaQLhvOrQQBEkvAoafNX8eyWt3pOI.&SP=1&pfmk=M46%3a1427993956363&subpage=ReadConversation.ascx
    User: user
    EX Address: /o=company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=user
    SMTP Address: [email protected]
    OWA version: 14.3.235.1
    Mailbox server: server.domain.com
    Exception
    Exception type: System.UriFormatException
    Exception message: Invalid URI: The format of the URI could not be determined.
    Call stack
    System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
    Microsoft.Exchange.Security.RightsManagement.DrmClientUtils.GetServiceLocation(SafeRightsManagementSessionHandle sessionHandle, ServiceType serviceType, ServiceLocation serviceLocation, String issuanceLicense)
    Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.GetOnPremiseRmsServerUri()
    Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.GetRmsServerActiveCryptoMode()
    Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.DrmEnvironment.InitializeEnvironment()
    Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.Initialize()
    Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.InitializeIfNeeded()
    Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.get_IRMConfig()
    Microsoft.Exchange.Clients.Owa.Core.UserContext.get_IsIrmEnabled()
    Microsoft.Exchange.Clients.Owa.Premium.ConversationUtilities.LoadConversation(UserContext userContext, OwaStoreObjectId owaConversationId, PropertyDefinition[] requestedProperties)
    Microsoft.Exchange.Clients.Owa.Premium.ReadConversation.OnLoad(EventArgs e)
    System.Web.UI.Control.LoadRecursive()
    System.Web.UI.Control.LoadRecursive()
    System.Web.UI.Control.LoadRecursive()
    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
    Request
    Url: https://domain.com:443/owa/forms/premium/SubPageContainer.aspx?ae=Item&a=Open&t=IPM.Note&id=RgAAAAD5wKVzMPRWToarE%2bpbowlJBwAqvhe3P6jjT4tregHxbY2pANbZjrf4AACsvITjR9r%2fQaXcC90BhfOwAI8oXwgBAAAJ&pspid=_1427993955843_521407833&subpage=ReadMessage.ascx
    User: user
    EX Address: /o=company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=user
    SMTP Address: [email protected]
    OWA version: 14.3.235.1
    Mailbox server: server.domain.com
    Exception
    Exception type: System.UriFormatException
    Exception message: Invalid URI: The format of the URI could not be determined.
    Call stack
    System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
    Microsoft.Exchange.Security.RightsManagement.DrmClientUtils.GetServiceLocation(SafeRightsManagementSessionHandle sessionHandle, ServiceType serviceType, ServiceLocation serviceLocation, String issuanceLicense)
    Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.GetOnPremiseRmsServerUri()
    Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.GetRmsServerActiveCryptoMode()
    Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.DrmEnvironment.InitializeEnvironment()
    Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.Initialize()
    Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.InitializeIfNeeded()
    Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.get_IRMConfig()
    Microsoft.Exchange.Clients.Owa.Core.UserContext.get_IsIrmEnabled()
    Microsoft.Exchange.Clients.Owa.Premium.ReadMessage.AddIrmMessageToInfobar()
    Microsoft.Exchange.Clients.Owa.Premium.ReadMessage.AddMessagesToInfobar()
    Microsoft.Exchange.Clients.Owa.Premium.ReadMessage.OnLoad(EventArgs e)
    System.Web.UI.Control.LoadRecursive()
    System.Web.UI.Control.LoadRecursive()
    System.Web.UI.Control.LoadRecursive()
    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

    Hi Noel,
    Base on my search, it may be due to IRM feature been enabled for OWA.
    I recommend you use the following command to check if the value of IRMEnabled parameter is true:
    Get-OWAVirtualDirectory – Identity “servername\owa (default web site)” |FL name,IRMEnabled
    If the value is true, you can use "Set-OWAVirtualDirectory" cmdlt to change it to false, and check if any helps.
    Best regards,
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Niko Cheng
    TechNet Community Support

  • Exchange 2010 SP3 Update Rollup 6 breaks first OWA login (timezone selection) on SBS 2011

    The Exchange 2010 SP3 Update Rollup 6 broke the OWA for Users who access OWA for the first time and have to set a timezone. They get this error:
    Request
    Url: https://xxxxx:443/owa/languageselection.aspx
    User: xxxxxx
    EX Address: /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=xxxxx
    SMTP Address: xxxxxx
    OWA version: 14.3.195.1
    Exception
    Exception type: System.ArgumentNullException
    Exception message: Value cannot be null. Parameter name: value
    Call stack
    Microsoft.Exchange.Clients.Owa.Core.Utilities.RenderDirectionEnhancedValue(TextWriter output, String value, Boolean isRtl)
    Microsoft.Exchange.Clients.Owa.Core.LanguageSelection.RenderTimeZoneSelection()
    ASP.languageselection_aspx.__Render__control1(HtmlTextWriter __w, Control parameterContainer)
    System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)
    System.Web.UI.Page.Render(HtmlTextWriter writer)
    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
    This Server is an SBS2011.
    The update broke nothing on a "normal" 2008R2 with exchange 2010.
    Uninstalling RU6 helped but thats obviously not the desired way.
    Removing the RenderTimeZoneSelection() call from languageselection.aspx obviously helped but then there is no timezone dropdown displayed anymore. The timezone dropdown is working normaly in other places like ecp. Afaik this error occours only in the languageselection.aspx
    file which is displayed for "new" OWA users. (Users without a timezone set)
    my workaround was to set the language and timezone for these mailboxes via exchange shell.

    Hello,
    Thank you for your post.
    This is a quick note to let you know that we are performing research on this issue.
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • Exchange 2010 SP3 - "500 5.3.3 Unrecognized command" in SMTP Receive Log. Senders get message with the same problem

    Hi
    My exchange environment consist with "Server Exchange 2010 SP3" and "Edge Server with Exchange 2010 SP3".
    On Edge server in SMTP receive log i get every now and then an entry: xxxxxx 500 5.3.3 Unrecognized command.
    It is serius problem because I got few e-mails from senders that they had problem with sending e-mail messages to our e-mail domain. They receive e-mail report, for example
    Technical details of permanent failure:
    Google tried to deliver your message, but it was rejected by the server for the recipient domain domena.plby
    mail.domena.pl.
    [95.xxx.xxx.xx].
    The error that the other server returned was:
    500 5.3.3 Unrecognized command
    Could you help me to solve this problem? What could cause this problem?
    Thank you in advance
    Tomasz
    Kind Regards Tomasz

    I have the same issue, but there is plenty of hard disk storage on the Exchange Server. This seems to only be happening from Google Business account/ Postini. If I send message from my personal Gmail account it works fine, but an agency who is on Google
    business seems to have issues sending to us and they are delayed, sometimes they get through and other times they just don't. 
    Results from Mail Acceptance Test:
    I enter my internal address and the remote users postini account as the test setup I received two emails from the tool but the end results of the test are:
     Error submitting mail
            Mail submission failed: Error message: Syntax error, command unrecognized. The server response was: 5.3.3 Unrecognized command.
    Google support stated this:
    Here are the logs from Postini trying to connect to mydomain.com (IP x.x.x.x) :
    1. 2014/08/09 03:26:28 IP:209.85.218.50 SMTP-STLS:OK <null> TLSv1:RC4-SHA Validate:None 2. 2014/08/09 03:26:28 IP:209.85.218.50 SMTP LOG: Sender => FFD:MAIL FROM:<[email protected]>
    3. 2014/08/09 03:26:28 IP:209.85.218.50 Fdal:Customer has null root_iid outbound default at org 100000001 4, 2014/08/09 03:26:28 IP:209.85.218.50 SMTP LOG: Sender <= FFD:250 Ok 5. 2014/08/09 03:26:28 IP:209.85.218.50 SMTP LOG: Sender => FFD:RCPT TO:[email protected]>
    6. 2014/08/09 03:26:34 IP:209.85.218.50 To:[email protected] SMTP LOG: FFD => mydomain.com (x.x.x.x):Connection established 7. 2014/08/09 03:26:34 IP:209.85.218.50 To:[email protected] SMTP LOG: FFD <= mydomain.com (x.x.x.x):220 server.mydomain.com
    ESMTP Service ready 8. 2014/08/09 03:26:34 IP:209.85.218.50 To:[email protected] SMTP LOG: Sender <= FFD:250 Ok 9. 2014/08/09 03:26:35 IP:209.85.218.50 To:[email protected] SMTP LOG: Sender => FFD:968 last bytes of data with dot 10. 2014/08/09 03:28:05
    IP:209.85.218.50 To:[email protected] From:[email protected]:1119780 FP:2603ec6d38c69886eb1000e516fb745a0384e50b SMTP:Delivery still in progress after 90 seconds, recording FP 11. 2014/08/09 03:31:17 IP:209.85.218.50 To:[email protected] SMTP
    LOG: FFD => mydomain.com (x.x.x.x):failed to send the last period(.) 12. 2014/08/09 03:31:17 IP:209.85.218.50 To:[email protected] oremote:Skipping Archive for Sender because did not deliver message 13. 2014/08/09 03:31:17 IP:209.85.218.50 To:[email protected]
    SMTP:451 Remote connection lost - psmtp 14. 2014/08/09 03:31:17 IP:209.85.218.50 To:[email protected] SMTP LOG: Sender <= FFD:451 Remote connection lost - psmtp
    As you can see, on line 9, at 03:26:35, we declared to the receiving server what we were about to send. At the line number 10, almost two minutes passed without an authorization (250 OK) from the receiving server. You can see our status being pushed back
    at that moment to the receiving mail server: SMTP:Delivery still in progress after 90 seconds. Two more minutes later the connection was simply dropped and so we generated a 400 error message to encourage the sending server to try again later (since no bounce
    was given per say from the receiving server, we won't hard-bounce it but defer it).
    I hope this will help. you can try to look in the mydomain.com  inbound logs and see at that exact time what happened? Unfortunately, our visibility pretty much ends there as we don't have full visibility of your mail environment. You'll need to investigate
    within your own environment unfortunately. If you have any more information to share with me, in case it might help me help you, feel free to do so. I'll leave this case opened for now.
    Sincerely,
    Patricia
    Google Enterprise Support

  • Exchange 2010 SP3 installation Problem

    Im getting below error when upgrading with Exchange 2010 Sp3. Please assist.
    Couldn't remove product with code 4934d1ea-be46-48b1-8847-f1af20e892c1. Fatal error during installation. Error code is 1603.
    Below the complete error from Exchange Setup Logs
    [02/16/2014 04:55:04.0515] [0] Setup will run the task 'uninstall-msipackage'
    [02/16/2014 04:55:04.0515] [1] Setup launched task 'uninstall-msipackage -logfile 'C:\ExchangeSetupLogs\ExchangeSetup.msilog' -ProductCode '4934d1ea-be46-48b1-8847-f1af20e892c1' -PropertyValues 'BYPASS_CONFIGURED_CHECK=1 DEFAULTLANGUAGENAME=ENU''  
    [02/16/2014 04:55:04.0515] [1] Active Directory session settings for 'Uninstall-MsiPackage' are: View Entire Forest: 'True', Configuration Domain Controller: 'domain.local', Preferred Global Catalog: 'Domain.local', Preferred Domain Controllers: '{ domain.local
    [02/16/2014 04:55:04.0515] [1] Beginning processing uninstall-msipackage -LogFile:'C:\ExchangeSetupLogs\ExchangeSetup.msilog' -ProductCode:'4934d1ea-be46-48b1-8847-f1af20e892c1' -PropertyValues:'BYPASS_CONFIGURED_CHECK=1 DEFAULTLANGUAGENAME=ENU'
    [02/16/2014 04:55:04.0547] [1] Removing MSI package with code '4934d1ea-be46-48b1-8847-f1af20e892c1'.
    [02/16/2014 04:55:06.0187] [1] [ERROR] Unexpected Error
    [02/16/2014 04:55:06.0187] [1] [ERROR] Couldn't remove product with code 4934d1ea-be46-48b1-8847-f1af20e892c1. Fatal error during installation. Error code is 1603.
    [02/16/2014 04:55:06.0187] [1] [ERROR] Fatal error during installation
    [02/16/2014 04:55:06.0234] [1] Ending processing uninstall-msipackage
    [02/16/2014 05:03:04.0333] [0] End of Setup
    [02/16/2014 05:03:04.0333] [0] **********************************************

    Hi,
    As you have found, the error is caused by that .msp installer files correlating to all the Update Rollups are not present in the c:\windows\installer folder.
    Based on my research, there is no Microsoft article about the hotfix of  KB2492690 (SP1 Update Rollup 3). Because our Exchange Team pulled the download due to issues with integration with Blackberry.
    For more information, you can refer to the following article:
    http://blogs.technet.com/b/exchange/archive/2011/03/14/exchange-2010-sp1-rollup-3-and-blackberrys-sending-duplicate-messages.aspx
    Thus, to get more professional and faster help, I recommend you contact with our following support:
    https://support.microsoft.com/common/international.aspx?RDPATH=%2foas%2fdefault.aspx%3fgprid%3d730
    If you have any question, please feel free to let me know.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Exchange 2010 SP3 Rollup 8 and Rollup 7

    Hi
    I have a customer with a Small Business Server 2010 with Exchange 2010 SP3.
    The Customer installed updates on the server 10/12/2014 where Rollup 8 for Exchange was included.
    After that the Customer has a lot of problems with connection from Outlook to Exchange and they phoned us.
    We have looked on the problem and found a Microsoft article about rollup 8 where they said DO NOT INSTALL
    We ran Windows Update again on the 13/12/2014 where Rollup 7 was installed
    The customers still has problems with connection from Outlook.
    One of the errors:
    From: Systemadministrator
    Sent: 15. december 2014 10:54
    Subject: Unable to be delivered: Test
    This message did not reach one or all of the recipients.
          Subject:     Test
          Sent:15-12-2014 10:54
    Unable to deliver to the following recipient(s):
          MST the 15-12-2014 10:54
                This message could not be sent. Try to send the message again later, or contact the networkadministrator.  Error [0x80004005-00000000-00000000].
    Another error in Application log:
    Log Name:      Application
    Source:        MSExchange Common
    Date:          16-12-2014 08:09:00
    Event ID:      4999
    Task Category: General
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      <servername>.<domain>.local
    Description:
    Watson report about to be sent for process id: 9340, with parameters: E12, c-RTL-AMD64, 14.03.0224.001, M.E.RpcClientAccess.Service, M.E.RpcClientAccess.Handler, M.E.R.H.ViewCache.IsRowWithinUnreadCache, System.IndexOutOfRangeException, 8e38, 14.03.0224.001.
    ErrorReportingEnabled: False
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchange Common" />
        <EventID Qualifiers="16388">4999</EventID>
        <Level>2</Level>
        <Task>1</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-12-16T07:09:00.000000000Z" />
        <EventRecordID>174679</EventRecordID>
        <Channel>Application</Channel>
        <Computer><servername>.<domain>.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>9340</Data>
        <Data>E12</Data>
        <Data>c-RTL-AMD64</Data>
        <Data>14.03.0224.001</Data>
        <Data>M.E.RpcClientAccess.Service</Data>
        <Data>M.E.RpcClientAccess.Handler</Data>
        <Data>M.E.R.H.ViewCache.IsRowWithinUnreadCache</Data>
        <Data>System.IndexOutOfRangeException</Data>
        <Data>8e38</Data>
        <Data>14.03.0224.001</Data>
        <Data>False</Data>
        <Data>
        </Data>
      </EventData>
    </Event>
    What to do ?
    Best Regards
    John B

    Hi John,
    Please type
    outlook /safe in RUN to start Outlook in safe mode and then check if this issue still exists. Meanwhile, please run Exchange Best Practices Analyzer and check if find relevant issues.
    à
    This message could not be sent. Try to send the message again later, or contact the networkadministrator. 
    Error [0x80004005-00000000-00000000].
    The issue typically occurs if send messages to a large number of recipients. 
    When this issue occurred, did you check if send message successfully via OWA?
    à
    We have looked on the problem and found a Microsoft article about rollup 8 where they said DO NOT INSTALL
    Did you mean this article:
    Exchange releases: December 2014?
    à
    We ran Windows Update again on the 13/12/2014 where Rollup 7 was installed
    From the Event ID 4999, I noticed that point to
    14.03.0224.001, it should mean the old Exchange Server 2010 SP3 Update Rollup 8. From above
    mentioned article (Exchange releases: December 2014),
    Exchange Server 2010 SP3 Update Rollup 8 has been re-released to the Microsoft download center resolving a regression discovered in the initial release. The update RU8 package
    corrects the issue which impacted users connecting to Exchange from Outlook. The updated RU8 package is version number 14.03.0224.002. Just a confirmation, did you
    reinstall that re-released Exchange Server 2010 SP3 Update Rollup 8? Any difference?
    If any update, please feel free to let me know.
    Hope this helps.
    Best regards,
    Justin Gu
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Email Delivery problem from Mailman to Exchange 2010 SP3 - Invalid Character Set Name in Message Subject

    Dear all,
    we have a problem in the email delivery from Mailman 2.6 List Server to Exchange 2010 SP3 CU7, 
    related to the encoding name of the Message Subject.
    The error we receive is the following:
    #550 5.6.0 CAT.InvalidContent.Exception: InvalidCharsetException, Character set name (iso8859-7) is invalid or not installed.; 
    cannot handle content of message with InternalId
    First of all, we can notice that given an encoding name as 'iso-8859-X',  it is transformed by the Mailman to 'iso8859-X' (without the first dash). 
    Our previous Exchange version ( Exchange 2003) didn't have any problem with this, but now, 
    Microsoft Exchange 2010 doesn't like the form of the encoding name without the dash, 
    and bounces the emails from Mailman. 
    The strange is that other email systems like Gmail, Yahoo accept the transformed encoding name.
    Any help would be appreciated.
    Kind Regards
    Panagiotis Kontogiannis

    Hi Panagiotis,
    Base on my search, I found a similar issue which was caused by the antivirus software in exchange server.
    I recommend you try to disable all the antivirus services and check if any helps.
    The similar thread for you reference:
    https://social.technet.microsoft.com/Forums/en-US/5bcf3098-2fe7-442f-a0bd-b720d703c6d0/problem-with-microsoft-exchange-2010-on-sbs-2011-550-560-catinvalidcontentexception?forum=exchangesvrdevelopment
    Best regards,
    Niko Cheng
    TechNet Community Support

Maybe you are looking for