Exchange 2013 Update from SP1 to CU5 failed

Hello, guys!
I need your help. I've just tried to make an update my Exchange Server with CU5 and get an error:
"$error.Clear(); 
          Uninstall-CrimsonManifest -DefinitionXml "bin\ActiveMonitoringEvents.man";
          Install-CrimsonManifest `
            -DefinitionXml "bin\ActiveMonitoringEvents.man" `
            -MessageDll "bin\ActiveMonitoringEventMsg.dll" `
            -ProviderName "Microsoft-Exchange-ActiveMonitoring"
The following error occurred: "System.InvalidOperationException:
Failed to perform event manifest action (manifest =
C:\Program Files\Microsoft\Exchange Server\V15\bin\ActiveMonitoringEvents.man, event = install-manifest,
exitcode  
= 5, errors = The publishers and channels are installed successfully. However, we can't enable one or more publishers and channels. Access is denied.
   in Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory
category, Object target, Boolean reThrow, String helpUrl)
   in Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory
category, Object target)
   in Microsoft.Exchange.Management.SystemConfigurationTasks.InstallCrimsonManifest.InternalProcessRecord()
   in Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   in Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func,
Boolean terminatePipelineIfFailed)".
Help me, please!!!
What should i do to resolve this problem???

Hi,
This issue occurs if any of the following conditions are true:
The built-in security group “NT Service\Eventlog”  does not have permissions on the folder %SystemRoot%\System32\winevt\Logs.
The built-in security group “NT Service\Eventlog”  does not have permissions on the registries and its sub keys,  
                         HKLM\Software\Microsoft\Windows\CurrentVersion\Reliability Analysis
                         HKLM\System\CurrentControlSet\Control\WMI\Autologger\EventLog-Application\
To solve this issue, please take the following steps to give requires permissions on the log folders and registry
Step 1:
Restore the default permissions on %SystemRoot%\System32\winevt\logs.
Authenticated user - List folder/read data, Read attributes, Read Extended attributes, Read permissions
Administrators - Full control
SYSTEM - Full control
EventLog - Full control
To restore the default permissions on folder %SystemRoot%\System32\winevt\logs, follow these steps.
Right-click on %SystemRoot%\System32\winevt\logs and select Properties.
Select the Security tab.
Click Edit button and click the Add button in the permissions dialog box.
In Select users, computers, or Groups dialog box ensure that under object types Built in Security Principals and the location as local computer name is selected.
Enter the object name as "NT SERVICE\EventLog" without quotes. And click
OK. This group should have full control on the folder.
Once EventLog group is added add the rest of the groups with above mentioned permissions.
Step 2:
Provide the permission to registry,
Open Registry Editor
Locate
HKLM\Software\Microsoft\Windows\CurrentVersion\Reliability Analysis, Right-click it and Select
Permissions...
Checked whether you have Eventlog group. If not, add “NT Service\Eventlog”, then give Full Control, then click OK.
Locate HKLM\System\CurrentControlSet\Control\WMI\Autologger\EventLog-Application\, right-click and Select
Permissions...
Repeat same in the No.3 step.
Note: Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number
to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
Best Regards.

Similar Messages

  • Update from Exchange 2013 Cu2 to SP1 - Outlook 2010 with SP2 clients disconnected

    Hi,
    we recently upgraded a standalone Exchange 2013 Server to SP1. Owa works fine, but all internal Outlook 2010 Clients (with SP2) get disconnected. Creating a new Profile, and testing the internal autodiscovery leeds to an Error 12030 (Connection reset) during
    the discovery process.
    I already checked the Service Point, the discovery URLs, even recreated the autodiscover virtual Directory in iis. But nothing changed.
    The self signed certificate, that was used before the update is further used, and well known to all Clients. As I tested, OWA is working well everywhere.
    Anyone some new ideas?
    Best regards
    Bernhard

    Hi,
    How did you recreate outlook profile? Manually or Automatic?
    If automatic failed, please try to recreate manually and check the result.
    If manual failed, please refer to the following methods to troubleshoot the issue:
    1>Try to open the following link and check the result:
     https://CASName/autodiscover/autodiscover.xml
    2>Try to use RCA to test outlook autodiscover and check the result.
    https://testconnectivity.microsoft.com/
    Thansk.
    Niko Cheng
    TechNet Community Support

  • Setup Error 1603 with Exchange 2013 incl. SP1 on Windows Server 2012 R2

    Hello all,
    i've started the installation of a new Exchange 2013 with SP1 in a Windows 2012 R2 environment. New AD, no Exchange previously installed. Exchange ISO from
    Volume Licensing Service Center (Filename: SW_DVD9_Exchange_Svr_2013w_SP1_MultiLang_Std_Ent_MLF_X19-35118.iso)
    All the prerequisites are ok, installed also the “Unified Communications Managed API (UCMA) 4.0″ as requested.
    Setup.exe i've started with "run as administrator" and all went well, until Step 11 of 15 (Mailbox role:Mailbox service).
    Setup stopped and gives an error:
    The following error was generated when "$error.Clear(); 
    Install-MsiPackage `
    -PackagePath ([System.IO.Path]::Combine($RoleLanguagePacksPath, "Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.nb-NO.msi")) `
    -PropertyValues ("ARPSYSTEMCOMPONENT=1 ALLUSERS=1") `
    -LogFile ([System.IO.Path]::Combine($RoleSetupLoggingPath, "InstallSpeech-nb-NO.msilog"))
    " was run: "Installing product F:\Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.nb-NO.msi failed. Fatal error during installation. Error code is 1603. Last error reported by the MSI package is 'The cabinet file 'EngineInstanceData.cab'
    required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.'.".
    Exchange ECP is not working (HTTP Error 404.0 - Not Found), EMS (Shell) is working - if i try a get-mailboxserver it gives me the correct servername.
    Exchange Services are running:
    Running MSExchangeADTop... Microsoft Exchange Active Directory...
    Running MSExchangeAntis... Microsoft Exchange Anti-spam Update
    Running MSExchangeDelivery Microsoft Exchange Mailbox Transpor...
    Running MSExchangeDiagn... Microsoft Exchange Diagnostics
    Running MSExchangeEdgeSync Microsoft Exchange EdgeSync
    Running MSExchangeHM Microsoft Exchange Health Manager
    Stopped MSExchangeIMAP4BE Microsoft Exchange IMAP4 Backend
    Running MSExchangeIS Microsoft Exchange Information Store
    Running MSExchangeMailb... Microsoft Exchange Mailbox Replication
    Running MSExchangeMigra... Microsoft Exchange Migration Workflow
    Stopped MSExchangePOP3BE Microsoft Exchange POP3 Backend
    Running MSExchangeRPC Microsoft Exchange RPC Client Access
    Running MSExchangeServi... Microsoft Exchange Service Host
    Running MSExchangeSubmi... Microsoft Exchange Mailbox Transpor...
    Running MSExchangeTrans... Microsoft Exchange Transport
    Running MSExchangeTrans... Microsoft Exchange Transport Log Se...
    Running MSExchangeUM Microsoft Exchange Unified Messaging
    So, how to proceed ? Try to download a new ISO for Exchange 2013 incl. SP1 and run the setup again ? 
    What happens to the existing  (corrupt) installation of the exchange which is not working ?
    Thanks for your help
    Bruno

    Hi,
    From the error message, the cabinet file 'EngineInstanceData.cab' required for this installation is corrupt and cannot be used. I'm afraid you have to download a new ISO for Exchange 2013 incl. SP1 and run the setup again.
    If it still doesn't work, I recommend you remove the failed Exchange server installation, then re-install Exchange server.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Error when updating Client Access Front End Service to Exchange 2013 Update 6

    When updating to Exchange 2013 Update 6 we received the following error at the Step 11 of 13: Client Access role: Client Access Front End service step: 
    Error:
    The following error was generated when "$error.Clear();
    $fe = get-ActiveSyncVirtualDirectory -server $RoleFqdnOrName -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
    if ($fe -eq $null)
    new-ActiveSyncVirtualDirectory -DomainController $RoleDomainController -Role ClientAccess;
    else
    update-ActiveSyncVirtualDirectory $fe -DomainController $RoleDomainController -InstallIsapiFilter $true
    " was run: "System.Management.Automation.ParameterBindingException: Cannot convert 'System.Object[]' to the type 'Microsoft.Exchange.Configuration.Tasks.VirtualDirectoryIdParameter' required by parameter 'Identity'. Specified method is not supported. ---> System.NotSupportedException: Specified method is not supported.
    at System.Management.Automation.ParameterBinderBase.CoerceTypeAsNeeded(CommandParameterInternal argument, String parameterName, Type toType, ParameterCollectionTypeInformation collectionTypeInfo, Object currentValue)
    --- End of inner exception stack trace ---
    at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)
    at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)
    at System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame frame)
    at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)".
    Problem was that if you have more than one ActiveSyncVirtualDirectory, the installer for Update 6 fails because it's not expecting an array of virtual directories to be returned. Solution is to remove the "extra" virtual directory, perform the
    installation, and then re-add the virtual directory. 
    None of the other types of virtual directories are susceptible to this, only ActiveSync. 

    Hi,
    Please try to reset registrar state:
    http://tsoorad.blogspot.in/2013/04/lync-2013-ee-pool-wont-start.html
    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
    sure that you completely understand the risk before retrieving any suggestions from the above link.
    Kent Huang
    TechNet Community Support

  • Exchange 2013 update fails from SP1 to CU5

    Hi,
    Trying to upgrade my exchange server 2013 SP1 to CU5 but not able to do it successfully it is giving below error while analyzing prerequisites .
    Server is in test environment and it has 2 network interfaces.
    Error:
    There was a problem accessing the registry on this computer. This may happen if the Remote Registry service isn't running. It may also indicate a network problem or that the TCP/IP Netbios Helper service isn't running.
    #kkalas

    Hi
    Are those services running?
    Have you tried doing a restart and then apply the update again?

  • Exchange Server 2013 Update from to CU3 to CU8 stuck, Exchange completely down

    Hello,
    We tried to update a Exchange 2013 server to CU8 because we needed support from Microsoft (certificate revoked, so OWA not working anymore) and they could only help us after updating to CU8 first. The problem is that the update got stuck and now Exchange
    is not working at all anymore. Since it is a production enviroment and there is mail in all outboxes we do not want to turn back to a snapshot but solve the problem and continue the update. Any help is welcome because all mail is down now :-(
    The error we received at the Exchange Server is:
    C:\Users\administrator.DOMAINNAME\Downloads\Exchange-cu8>setup.exe /m:upgrade /In
    stallWindowsComponents /IAcceptExchangeServerLicenseTerms
    Welcome to Microsoft Exchange Server 2013 Cumulative Update 8 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for
    installation.
    Languages
    Mailbox role: Transport service
    Client Access role: Front End Transport service
    Mailbox role: Client Access service
    Mailbox role: Unified Messaging service
    Mailbox role: Mailbox service
    Management tools
    Client Access role: Client Access Front End service
    Performing Microsoft Exchange Server Prerequisite Check
        Configuring Prerequisites                                 COMPLETED
        Prerequisite Analysis                                     COMPLETED
    Configuring Microsoft Exchange Server
        Preparing Setup                                          
    COMPLETED
        Stopping Services                                         COMPLETED
        Language Files                                            COMPLETED
        Removing Exchange Files                                   COMPLETED
        Preparing Files                                          
    COMPLETED
        Copying Exchange Files                                    COMPLETED
        Language Files                                            COMPLETED
        Restoring Services                                        COMPLETED
        Language Configuration                                    COMPLETED
        Mailbox role: Transport service                           FAILED
         The following error was generated when "$error.Clear();
              $connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
              foreach($connector in $connectors) { if($connector.MaxLocalHopCount -g
    t 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 }
            " was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.Recei
    veConnectorRoleConflictException: The values that you specified for the Bindings
     and RemoteIPRanges parameters conflict with the settings on Receive connector "
    SERVER-EXCHANGE\Externe POP3 mailboxen". Receive connectors assigned to differen
    t Transport roles on a single server must listen on unique local IP address & po
    rt bindings.
       bij Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exceptio
    n, ErrorCategory errorCategory, Object target, String helpUrl)
       bij Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exceptio
    n, ErrorCategory category, Object target)
       bij Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnecto
    r.InternalValidate()
       bij Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       bij Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String fu
    ncName, Action func, Boolean terminatePipelineIfFailed)".
         The following error was generated when "$error.Clear();
              $connectors = Get-ReceiveConnector -Server $RoleFqdnOrName;
              foreach($connector in $connectors) { if($connector.MaxLocalHopCount -g
    t 1) { Set-ReceiveConnector -Identity $connector.Identity -MaxLocalHopCount 5 }
            " was run: "Microsoft.Exchange.Management.SystemConfigurationTasks.Recei
    veConnectorRoleConflictException: The values that you specified for the Bindings
     and RemoteIPRanges parameters conflict with the settings on Receive connector "
    SERVER-EXCHANGE\Default Frontend SERVER-EXCHANGE". Receive connectors assigned t
    o different Transport roles on a single server must listen on unique local IP ad
    dress & port bindings.
       bij Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exceptio
    n, ErrorCategory errorCategory, Object target, String helpUrl)
       bij Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exceptio
    n, ErrorCategory category, Object target)
       bij Microsoft.Exchange.Management.SystemConfigurationTasks.SetReceiveConnecto
    r.InternalValidate()
       bij Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       bij Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String fu
    ncName, Action func, Boolean terminatePipelineIfFailed)".
    The Exchange Server setup operation didn't complete. More details can be found
    in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.

    Hello Gadget,
    Please find the solution as follows
    This error is concern about WMSVC certificate which was deleted, we could refer to the following steps:
    1- Go to IIS Manager and select server certificate,
    2- Select “Create Self-Signed Certificate”,
    3- For Server 2012 in the Friendly Name Field type: WMSVC and select the personal (certificate Store),
    4- Now go to ” Management Service”,
    5- From SSL Certificate choose the newly create “WMSVC” Self-Signed Certificate,
    6- Apply,
    7- Now  start service of “Web Management service”.
    https://social.technet.microsoft.com/Forums/office/en-US/eac00dc2-6e43-45ae-939c-aad82a144908/cu8-install-fails?forum=exchangesvrgeneral
    Exchange Queries

  • Windows 8.1 system with new Office 2013 install not pulling down any Office 2013 updates from my SCCM 2012 SP1 server

    Hi,
    I've just setup a new Windows 8.1 system and added to my SCCM 2012 SP1 server and all is good and it pulled down all the correct Windows updates and pulls down automatically the FEP updates that are distributed from SCCM 2012 daily. 
    I just installed Office 2013 on this system and have activated it as necessary.  The problem is that the system doesn't seem to be pulling down any of the Office 2013 updates that have distributed thru SCCM.  I have other systems with
    Office 2013 installed and they have pulled down Office 2013 updates in the past when I published them.
    If I look at the Office 2013 updates in the SCCM console software section, I can see that for example it shows that Office 2013 SP1 (x86) is needed by one system and installed on 8 other systems and shows as downloaded and deployed.
    I've restarted the new system multiple times and also tried to force a software update check from the Configuration Manager applet but nothing seems to happen.
    What can I check to try and determine what the problem is?
    Thanks in advance,
    Nick

    Yes, the 8.1 system is a member of collection where the update deployment is targeted.
    Are there any specific logs I should check in the client?  If I check the WindowsUpdate.log I can see messages about the machine pulling down the FEP updates but that's all it appears to be doing.
    in CCM\logs, focus on the updatehandler and updatedeployment, to begin with
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • Exchange 2013 upgrade from 2010 and no mail flow and cannot move mailboxes

    I am in the process of moving to Ex 2013 from 2010. I have installed Ex 2013 SP1 on a new server 2012 R2. All of my Ex 2010 servers are SP3 RU 5. Ex 2013 is running and I can connect through the EAC and see all other Exchange servers and connectors that
    were already in existence. Several puzzling things are happening now that the servers are in coexistence:
    1) As soon as Ex 2013 was installed on the network, many Outlook users are continuously being prompted to enter their domain credentials.  They can cancel the prompt and Outlook still sends/receives email.  No user mailboxes are on Ex 2013 yet. 
    Why is this happening?
    2) I am following the Ex 2013 Deployment Assistant and I get to the step to move the Ex 2010 Arbitration mailbox to Ex 2013 and the move does not happen--it just says "syncing" and never completes.  I tried moving a test mailbox from Ex 2010
    to the 2013 database and I get the same result.  I created the move request on the Ex2013 server and I see it as queued on the Ex2010 server, so I know they are "talking" to each other.  However, when reviewing the status of the move I
    see "MapiExceptionNoAccess: Unable to open message store".
    3) There seems to be no mail flow on the same Ex2013 server or between the Ex 2010 and 2013 servers.  I created two new test user mailboxes in Ex 2013.  The Ex2013 mailboxes cannot send/receive to each other or to Ex 2010 users.  This
    seems strange, unless I am completely missing something in the Ex 2013 install?
    I know this is a lot in one post, but following the Deployment assistant, I was hoping this would be something that others have faced.  Thanks for any input here.

    Does the below points already fit for you.
    Exchange 2013 Supported with the following minimum versions of Exchange:
    1) Exchange*** 2010 SP3 on all Exchange 2010 servers in the organization, including Edge Transport servers.
    2) Exchange 2013 CU2 or later on all Exchange 2013 servers in the organization.
    *** If you want to create an EdgeSync Subscription between an Exchange 2010 Hub Transport server and an Exchange 2013 SP1 Edge Transport
    server, you need to install Exchange 2010 SP3 Update Rollup 5 or later on the Exchange 2010 Hub Transport server.
    Thanks Prem P Rana MCSA Messaging 2003 MCSE 2003 Server MCTS MCITP Exchange 2007, 2010 Gurgaon, India http://blogs.msexchange-experts.com

  • "Configuration Manager cannot connect to the site" after site update from SP1 to R2

    Our dev SCCM environment only has a single primary site with a remote SQL database.  Initially, the dev primary site had SP1 Beta (5.00.7782.1000) installed but as everyone is aware there is no upgrade path available to SP1 or R2 from Beta; so, we uninstalled
    the site and removed the database, re-installed SP1 non-Beta (5.00.7804.1000), then proceeded to update all devices with the latest client agent.  Afterwards, we attempted to upgrade the site from SP1 non-Beta (5.00.7804.1000) to R2 (5.00.7958.1000).
     All seemed well until we attempt to open the Configuration Manager console and we get the following error message:
    Configuration Manager cannot connect to the site (Site Name)
    The Configuration Manager Administrator console could not connect to the Configuration Manager site database. Verify the version of the console is compatible with the version of the site server you are connecting to and then try to connect again.
    So we tried reinstalling the console directly from here...
    "C:\Program Files\Microsoft Configuration Manager\tools\ConsoleSetup\AdminConsole.msi"
    still the same error message persisted, so we tried installing it from here...
    "C:\Program Files\Microsoft Configuration Manager\tools\ConsoleSetup\ConsoleSetup.exe"
    still the same error message persisted, so then we tried installing it directly from the R2 (5.00.7958.1000) installation media, and afterwards the same error message persisted....
    All along, we were checking the AdminConsole log from here:
    "C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\AdminUILog\SmsAdminUI.log"
    Here are the contents:
    [4, PID:4836][04/22/2014 15:21:10] :Property: 'Features'\r\nSystem.Management.ManagementException\r\nNot found \r\n   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
       at System.Management.PropertyData.RefreshPropertyInfo()
       at System.Management.PropertyDataCollection.get_Item(String propertyName)
       at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObjectBase.get_Item(String name)\r\nManagementException details:
    [4, PID:4836][04/22/2014 15:21:10] :ReadExtraProperties: Failed to initialize extra properties
    [4, PID:4836][04/22/2014 15:21:11] :Transport error; failed to connect, message: 'The Configuration Manager Administrator console could not connect to the Configuration Manager site database. Verify the version of the console is compatible with the version
    of the site server you are connecting to and then try to connect again.'\r\nMicrosoft.ConfigurationManagement.ManagementProvider.SmsConnectionWithDetailException\r\nThe Configuration Manager Administrator console could not connect to the Configuration Manager
    site database. Verify the version of the console is compatible with the version of the site server you are connecting to and then try to connect again.\r\n   at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.ValidateConnectionParameters(ConnectionManagerBase
    connection)
       at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.GetConnectionManagerInstance(String connectionManagerInstance)\r\nNo details are available for this error.\r\n
    Once again, we validated we could connect to the SQL database from this box, and that the console was at the same version as the site.  Any help or guidance with getting our access to the console restored after the SP1 to R2 upgrade would be greatly
    appreciated. 

    From the Primary Site Server, I tried uninstalling the Admin Console and re-installing using:
    consolesetup.exe /q TargetDir="%ProgramFiles%\Microsoft Configuration Manager" EnableSQM=0 DefaultSiteServerName=<SiteServerName>
    Of course replacing <SiteServerName> with the FQDN of my Primary Site Server.  Console installed successfully however the same error message persists.
    Also tried installing the console on a clean Windows Server 2008 R2 installation.  I tried it from the R2 (5.00.7958.1000) installation media, from the "C:\Program Files\Microsoft Configuration Manager\tools\ConsoleSetup\" both without any luck, the
    same error message persists.  I verified I could ping the FQDN of the site server also, and that the firewall between the two permits communication over the ports listed here: http://technet.microsoft.com/en-us/library/hh427328.aspx
    Any help would be greatly appreciated.

  • Outlook 2010 connecting to Exchange 2013 and 2007 ... delivery fails

    Hello,
    we are having a problem with a few Outlook 2010 Clients that have two Exchange accounts setup in one profile. One account is connecting to the company's Exchange 2013 Server, the second account is connecting to an external provider's Exchange 2007 infrastructure
    using Outlook Anywhere.
    The companies Exchange 2013 was recently migrated from Exchange 2010 and this is the point where the problem started.
    Some users are no longer able to send using the external Exchange 2007 account. When they try they are receiving an NDR with the following error message:
    #554 5.6.0 STOREDRV.Deliver; Corrupt message content##  from the external provider's servers.
    When I setup a profile containing only the external provider's mailbox everything works fine until I am adding the company's Exchange 2013 back in at which point the same error appears.
    We have no problems using the company's Exchange 2013 servers.
    Does anyone have an idea what causes this and how to resolve it? The external provider is uncooperative in troubleshooting so we are left with the problem.
    Thank you
    Sascha

    Hi,
    The problem should be related to the External Exchange 2007.
    Please refer to this kb below:
    http://support.microsoft.com/kb/2203381/en-us
    This problem occurs when the email message is a multipart/mixed MIME message which contains a text/plain body and an application/applefile body.  If the corresponding body is not a real application/applefile body, the Exchange Server 2007 server considers
    that the email message is invalid. Therefore, it generates the NDR. However, Exchange Server 2010 can deliver this kind of email message successfully.
    To resolve this problem, you should let the External Provider install the following update rollup:
    2279665 Description of Update Rollup 1 for Exchange Server 2007 Service Pack 3
    Hope this helps.
    Thanks,
    Melon Chen
    Forum Support
    Come back and mark the replies as answers if they help and unmark them if they provide no help.
    If you have any feedback on our support, please click
    here

  • Accessing Exchange 2013 Mailboxes from Terminal Server hosted on Server 2003 Std - Cert Issues

    We are in the midst of deploying an Exchange 2013 SP1 CU5 environment and have run into some issues.  Currently there is a good coexistence between a single Exchange 2007 server and the 5 2013 servers.  Mail is flowing through 2013 and then being
    relayed to 2007 when necessary.  
    We have a number of Server 2003 Terminal Servers.  On two separate machines, both running the lastest rollups of Outlook 2010, any user with a 2013 mailbox receives a password prompt after launching Outlook.  It is trying to connect to one of the
    two CAS, fills in the user's account, and will not accept any password.  In addition, a window pops up behind stating "There is a problem with the proxy server's security certificate.  the name on the security certificate is invalid or does
    not match the name of the target site mail.pvschemicals.com.  Outlook is unable to connect to the proxy server.  (error code 0)."  2007 mailboxes are not affected.
    We have checked pretty much everything that we can think of.  Virtual Directories are good, certificate is good, etc.  The strange thing is that only happens on 2003 TS machines, so I have to think that it's related.  Our 2008 TS' are just
    find.
    We have applied the 2003 SHA2 certificate hotfix. 

    Hi,
    According to your description, the configurations of Outlook Anywhere are proper. And based on my research, the issue can be related to the version of the terminal server 2003. Thus, please check if your terminal 2003 server is 2003 R2 SP2 or later.
    For more information, you can refer to the following thread:
    http://social.technet.microsoft.com/Forums/exchange/en-US/295bf2bc-584b-4de2-85fb-94096fac52e7/outlook-connectivity-problem-on-2003-term-server-exchange-2013?forum=exchangesvrclients
    Thanks,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Angela Shi
    TechNet Community Support

  • Server 2012 and Exchange 2013 Migration from SBS 2011

    Server UpgradeI'm migrating an SBS 2011 server to a new machine with Server 2012 R2 and a Hyper-V server running Exchange 2013. I've set up the new machine, all is running well in a test environment. I now want to migrate the old server to new. These are the steps I'm going to take and I wanted advice for any modifications or errors. 1. Demote DC on Server 2012 that I set up to test. 2. Join new Server 2012 to existing SBS 2011 domain. 3. Promote Server 2012 to DC. 4. Join the Hyper-V Server 2012 to the Server 2012 domain.5. Migrate Exchange 2010 on the SBS 2011 Server to Exchange 2013. 6. Transfer FSMO role from SBS 2011 Server to Server 2012 DC. I'll copy shared data files using robocopy.The only things I'm not sure about is the FSMO order, when to do that and the fact that I already have Exchange 2013 installed in the test...
    This topic first appeared in the Spiceworks Community

    I recently acquired a SuperMicro chassis that has a SAS2 expander backplane. It has SFF-8087 ports on it.http://www.supermicro.com/manuals/other/BPN-SAS2-846EL.pdfI made a post on another forum and someone mentioned that the card couldn't be used with that backplane since it's a SATA controller, however, the backplane is both SAS and SATA device compliant, it's only the RAID controller, as far as I know, that is a "SATA II" controller, and not a SAS controller.So, I couldn't find anything in the official documentation of this controller on whether or not it was able to control SAS devices. The card itself has a 3 SFF-8087 ports though, couldn't this theoretically still be used with a SFF-8087 to SFF-8087 cable(seen below)since the backplane is a SAS/SATA backplane?...

  • Installing Exchange 2013 CU1 on a production server fails: Couldn't mount the database that you specified.

    Error:
    The following error was generated when "$error.Clear();
              $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName;
              $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
              $dismbx = get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1;
              if( $dismbx -ne $null)
              $srvname = $dismbx.ServerName;
              if( $dismbx.Database -ne $null -and $RoleFqdnOrName -like "$srvname.*" )
              Write-ExchangeSetupLog -info "Setup DiscoverySearchMailbox Permission.";
              $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true };
              if( $mountedMdb -eq $null )
              Write-ExchangeSetupLog -info "Mounting database before stamp DiscoverySearchMailbox Permission...";
              mount-database $dismbx.Database;
              $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true };
              if( $mountedMdb -ne $null )
              $dmRoleGroupGuid = [Microsoft.Exchange.Data.Directory.Management.RoleGroup]::DiscoveryManagement_InitInfo.WellKnownGuid;
              $dmRoleGroup = Get-RoleGroup -Identity $dmRoleGroupGuid -DomainController $RoleDomainController -ErrorAction:SilentlyContinue;
              if( $dmRoleGroup -ne $null )
                trap [Exception]
                  Add-MailboxPermission $dismbx -User $dmRoleGroup.Name -AccessRights FullAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
                  continue;
                Add-MailboxPermission $dismbx -User $dmRoleGroup.Identity -AccessRights FullAccess -DomainController $RoleDomainController -WarningAction SilentlyContinue;
        " was run: "Couldn't mount the database that you specified. Specified database: DB01; Error code: An Active Manager operation failed with a transient error. Please retry the operation. Error: Database action failed with transient
    error. Error: A transient error occurred during a database operation. Error: An error occurred while preparing to mount database 'DB01'. Error: An I/O error occurred while attempting to enumerate log files in directory 'D:\Logs\DB01'. Error 0x3
    I have dismount DB01 off the my Exchange 2013 and my database DB01 is also corrupt not able to repair so I created a new database called DB1.  I'm having issue running cumulative
    Vien H. Lim

    Hi Vien,
    Have you checked Martina's suggestion?
    If the issue persists, I would like to clarify the following things for further research:
    1. Please check if there exists DAG in your Exchange 2013.
    2. Please check if the directory 'D:\Logs\DB01' exists.
    What's more, I recommend you to use the ESEUTIL/mh cmdlet to check the database status when you create a database.
    Hope it helps. If there are any problems, please feel free to let me know.
    Best regards,
    Amy

  • Exchange 2013 Migration from 2010 Test (Shared split DNS)

    Hi
    Im testing a migration from Exchange 2010 to 2013. I have tried to run a single DNS name to both servers, so externally mail.test.com resolves to the external IP and that NAT's to the new Exchange 2013. Then internally mail.test.com resolves both to EXC13
    and EXC10 ip adresses (Round Robin).
    I have moved some mailboxes to 2013. If the IP resolves to the new Exchange and i try to login to a mailbox on the old server i get redirected as im supposed to. If the IP resolves to the old Exchange and i try to login with a mailbox on the new server i
    get:
    A server configuration change is temporarily preventing access to your account. Please close all Web browser windows and try again in a few minutes. If the problem continues, contact your helpdesk.
    Should this be possible, or do i need to change the intarnal URL on all virtual directories on the old server to the local netbios name or what to do?

    You should never use the server name in any of the URLs.  You should use either a CNAME or a load-balanced VIP with a generic name like mail.company.com or webmail.company.com.  Then you just point this name to the new server.  If
    you're currently using a server name, it's about time to change that first before trying to switch to Exchange 2013.
    Curently im using a generic name, mail.test.com. But that's just a normal A record on the internal DNS. So i cannot use that on both?

  • Journaling mailbox - Exchange 2013 Migrations from 2010

    hi guys
    i am about to start mailbox movement from Exchange 2010 to 2013. my setup is working fine. i have enabled journaling from Exchange 2010 and as ii found, automatically journaling rules will be reflected to exchange 2013. i had very big journaling mailbox
    and then newly created New Exchange 2010 journaling mailbox. now new journaling mailbox is configured for journaling and that also still on 2010(both Old and new journaling mailbox ), new mailx is couple of weeks old (6-8 GB) and old one is 2.6 TB. So i will
    move old one at the end .
    my questions is if i move new journaling mailbox to 2013 before start normal Mailboxes, it will cause some issues for journaling. i use premium journaling . is it okay to move journaling mailbox at the begin ?? 
    thank you
    Indunil

    Hi,
    Based on my test, journal rules will be synchronized in Exchange 2013 after you create in Exchange 2010. If you create in Exchange 2013, then the rule will be synchronized in Exchange 2010.
    And I did create a rule to send message to a Exchange 2013 jounal mailbox for Exchange 2010 users. It worked.
    So you can migrate journal mailbox to Exchange 2013 firstly based on this test.
    Best regards,
    Belinda Ma
    TechNet Community Support

Maybe you are looking for

  • Error when running Adobe form?

    Hi all, When i ran my Adobe Form appl, I got this error. What to be configured?Plz help me <b>Error:</b> com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Error during call to AdobeDocumentServer: Processing exception during a "UsageRights

  • How to Play 3gp in a MIDlet?

    Hi, wich APY should I use? MMAPI? oR 3D? Has someone some exaple of code? Thanks.

  • WSDL 1.1 Binding Extension for SOAP 1.2

    Hi, The WSDL file that is generated in XI 3.0 uses the specification SOAP 1.1 To apply the specification "WSDL 1.1 Binding Extension for SOAP 1.2", is it sufficient with adding the necessary parameters or have I to create the WSDL file again? Paramet

  • BBM GROUP COMMENTS

    My comments on my BBM Group in some chat rooms are not posted sequentially. I have ensured date and time are accurate, yet no change. e.g posted comment shows 2016

  • How avoid getting duplicate e-mails

    all e-mail received to my address is received twice  how do i correct?