Exchange 2010 DB log folders constanly filling up, with my fix

Hello All,
I'm posting this, because I couldn't find an obvious solution online, and happened to stumble upon my fix.  I had a database log drive/folder that was constantly filling up for a couple of weeks.
I used all of the suggested tools including exmon, and still couldn't quite pinpoint the problem.
We have Quest Archive manager, and have the journal user for that program in this Db.  Exmon showed this as the most likely culprit, but I couldn't move it easily, because it has so much mail flow.  I tried many other alternatives to pin down exactly
why the log file was growing to no avail.
Anyway, after a few days, I decided to check the "Queue viewer" under the toolbox in EMC.  I'm fairly new to exchange, and this was just a guess.  Maybe you all, already know about this.  IN the queue viewer I noticed the queue for
the problematic DB had some emails that were never clearing out.  One of them was about 21 meg.  I showed the date column, sorted by date, and deleted anything that was older than today.  This was about 5 emails in total.
As soon as I did that, the logs stopped filling up.

Hi,
As ExchangeITPro suggested, please do a full backup. The logs will be truncated after a full backup is finished successfully.
What's more, I recommend you use the Troubleshoot-DatabaseSpace.ps1 script to detect and correct any excess log growth or Microsoft Exchange database (.edb) file growth.
Here is an article for your reference.
Manage Database Log Growth by Using the Troubleshoot-DatabaseSpace.ps1 Script in the Shell
http://technet.microsoft.com/en-us/library/ff477617.aspx
Hope it helps.
Best regards,
Amy
Amy Wang
TechNet Community Support

Similar Messages

  • Exchange 2010 SP2 : Log Sequence Missing...

    Hi Friends,
    Recently we configure EMC Networker backup in our environment. but somehow it's not running incremental backup. when we send logs to EMC they reply some log sequence is missing. how i can fix this issue. can anyone help me.
    I am using Exchange 2010 SP2
    DAG Environment
    Two Hubcas Server with two seprate Mailbox servers (Active and Passive)
    Few logs are below...
    18/05/2014 16:01:40  
    Mailbox.domain.local nsrsnap_vss_save NMM .. Possible loss of log data. For database DB-2GB-1, the current log file on disk is E01000D779E.log -- 882590. Previous log file backed up was E01000D6B22.log -- 879394.
    Mailbox.domain.local nsrsnap_vss_save NMM .. Log file gap detected from previous backup to current for APPLICATIONS:\Microsoft Exchange 2010. Promoting this saveset to FULL.  
    Mailbox.domain.local nsrsnap_vss_save Save set name APPLICATIONS:\Microsoft Exchange 2010 is valid.
    19/05/2014 16:01:18  
    Mailbox.domain.local nsrsnap_vss_save NMM .. Possible loss of log data. For database DB-2GB-1, the current log file on disk is E01000D8741.log -- 886593. Previous log file backed up was E01000D78AD.log -- 882861.
    Mailbox.domain.local nsrsnap_vss_save NMM .. Log file gap detected from previous backup to current for APPLICATIONS:\Microsoft Exchange 2010. Promoting this saveset to FULL.  
    Mailbox.domain.local nsrsnap_vss_save Save set name APPLICATIONS:\Microsoft Exchange 2010 is valid.

    Hi,
    Please make sure the Microsoft Exchange Server Extension for Windows Server Backup service running fine.
    Please also try to collect some App log for the further troubleshooting.
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Moving Exchange 2010 Transaction Log

    Hi. Running a single instance of SBS2011 with Exchange 2010. We only have one mailbox.
    Earlier today I moved our main exchange database (.edb) file to a different hard drive. Used EMC, went through smoothly, no issues.
    I then started moving the transaction logs. Same process:
    Exchange Management Console > Organization Configuration > Mailbox > Move
    Database Paths
    This appeared to be going fine but after 40 mins came up with an error along the lines of "WinRM cannot process the request in the time specified"
    Now I cant access any mailboxes. OWA giving the error - Your mailbox appears to be unavailable. Try to access it again in 10 seconds. If you see this
    error again, contact your helpdesk
    I have checked in EMC and the mailbox is successfully mounted. I have restarted all exchange services.
    I also now have 8.5GB of log files in the "new" location. Not if these are just copies or exchange is actually using this drive.

    Hi:
    I think you may be over complicating this.  SBS includes a wizard in the SBS Console to move most/all of the user impacted data stores, including Exchange, SharePoint, WSUS and Redirected folders.  The transaction logs are limited in size if you
    use either the SBS backup or a third party backup that is "Exchange Aware" to backup the server or the Exchange subsystem, so there is really no need to move the logs, assuming you are making good backups.
    Larry Struckmeyer[MVP] If your question is answered please mark the response as the answer so that others can benefit.

  • Exchange 2010 System Public Folders trying to replicate to decommissioned Exchange 2003

    I was checking the mail queue on Exchange 2010 and noticed several hundred messages in retry. Looking at the messages I found that they were all destined for an old 2003 exchange that has been decommissioned. I looked at the System Public Folders and found
    replication is set up on "events root, OWAScatchpad, SchemaRoot, and Store Events. They are set to replicate to the old mail server. When I try to remove the old server from replication it gives me an error;
    Microsoft Exchange Error
    The following error(s) occurred while saving changes:
    Set-PublicFolder
    Failed
    Error:
    You must specify a value with the Replicas parameter.
    OK
    Not sure where to go with this error.  Could someone point me in the right direction?
    Thank you,
    Wade Harris

    Hi,
    For this issue, I recommend you add an Exchange 2010 public folder database to the replica list and then remove Exchange 2003 server from this list to check result.
    I tested in my lab, and I got the same error with yours, we need to keep at least one public folder database in the replica list.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Exchange 2010 - Event Logging Failure - "System.ServiceModel 3.0.0.0"

    Exchange 2010 14.3 Build 123.4
    Stumped. Can't seem to figure out why this suddenly started but this Exchange error is logging every minute.
    According to Process Explorer, this is the Exchange process (PID 6860) not logging correctly:
    c:\windows\system32\inetsrv\w3wp.exe -ap "MSExchangeServicesAppPool" -v "v2.0" -l "webengine4.dll" -a \\.\pipe\iisipma54689d0-13bc-4c77-a060-0bae334c1a34 -h "C:\inetpub\temp\apppools\MSExchangeServicesAppPool\MSExchangeServicesAppPool.config"
    -w "" -m 0
    This is the error logged:
    Source: System.ServiceModel 3.0.0.0
    Event ID: 5
    Task Category: Message Logging
    Details:
    A message was not logged.
     Exception: System.InvalidCastException: Unable to cast object of type 'System.ServiceModel.Channels.StreamedMessage' to type 'System.ServiceModel.Channels.BufferedMessage'.
       at System.ServiceModel.Security.SecurityVerifiedMessage.GetReaderAtEnvelope()
       at System.ServiceModel.Security.ReceiveSecurityHeader.GetReaderAtSecurityHeader()
       at System.ServiceModel.Security.ReceiveSecurityHeader.OnWriteHeaderContents(XmlDictionaryWriter writer, MessageVersion messageVersion)
       at System.ServiceModel.Diagnostics.MessageLogTraceRecord.WriteHeader(XmlDictionaryWriter dictionaryWriter)
       at System.ServiceModel.Diagnostics.MessageLogTraceRecord.WriteTo(XmlWriter writer)
       at System.ServiceModel.Diagnostics.MessageLogger.LogInternal(MessageLogTraceRecord record)
       at System.ServiceModel.Diagnostics.MessageLogger.LogMessageImpl(Message& message, XmlReader reader, MessageLoggingSource source)
       at System.ServiceModel.Diagnostics.MessageLogger.LogMessage(Message& message, XmlReader reader, MessageLoggingSource source)
     Process Name: w3wp
     Process ID: 6860

    Hi,
    Please firstly confirm if the Autodiscover service, OAB service, Free/Busy information, OOF feature, OWA and ECP can work well for Exchange users or not.
    If there are some issues when using these services or features for client users, please do the following points in IIS manager:
    1. Go to control panel and checked if there are any third party application or message logging application.
    2. Please recycle Autodiscover, MSExchangeServicesAppPool.
    3. Try to install the below hotfixes:
    http://support.microsoft.com/kb/2801728
    http://support.microsoft.com/kb/2637518
    If Autodiscover, EWS and other features are working fine but we still get above error messages reported for the Autodiscover, EWS PID's, please make sure that SystemLogging is turned OFF in Microsoft Exchange Troubleshooting Assistant tool (EXTRA) on the
    Exchange servers:
    1. Launch Microsoft Exchange Troubleshooting Assistant tool by clicking Start > run > type EXTRA > Select a task > Trace control > Set manual trace tags.
    2. Under Components to Trace, uncheck SystemLogging.
    3. Click Start tracing > Stop the tracing once the tracing has started.
    (Please note: Even if we are not running EXTRA but still enabling the SystemLogging component will turn on MessageLogging)
    Then check whether the issue persists.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Exchange 2010 can't send or receive email with attachments.

    Hello,
    We have an Exchange 2010 server, running under Windows 2008R2. Both the server and Exchange are current for Windows and Exchange updates. Exchange is on SP3 installed about a month ago with no errors reported in the event logs.
    The problem is that attachments over about 1 MB do not send or receive and no error message is returned. If I send an email message with a 3 MB attachment to myself, it reports as sent in Outlook. On the Exchange server the message queue shows nothing in
    the queue. I try to use Exchange mail flow tracking tool and it hangs when selecting “messages received from” option. I gave up waiting after 5 minutes for the display to populate.
    As the server is set attachments should be able to send and receive up to 20 MB.
    I checked and verified all settings I could find related to this. I checked with the Exchange Management Console per the following article:
    http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/managing-limits-exchange-server-2010-part1.html
    I also checked using the Exchange Power Shell using the following article:
    http://eightwone.com/2010/09/29/exchange-message-size-limits/
    Both show that all settings are suitable. Details are below
    I would appreciate feedback on this problem.
    Thank you!
    Details from the articles noted above:
    First test was to attach a 3 mb text file in Outlook sent from my in house account to my in house account. After 5 minutes the test message was not received nor was there an error message returned.
    Checked The Exchange server mail queue and there was nothing in the queue. Checked the Exchange mail flow tracking tool and it hung when selecting “messages received from” option.
    Reviewed and verified settings per the following 2 articles:
    Article #1
    http://www.msexchange.org/articles-tutorials/exchange-server-2010/management-administration/managing-limits-exchange-server-2010-part1.html
    Organization Configuration>Hub Transport>General Settings>Global Settings>Transport Settings set to max receive size (KB) = 20480
    Settings set to max send size (KB) = 20480
    Organization Configuration> Hub Transport> Send Connectors tab.
    Maximum message size (KB) set to 20480
    Exchange Management Console> Server Configuration> Hub Transport> and then on the right side, select the desired server.
    A list of all Receive Connectors will be shown below
    There are 3 receive Connectors
    #1) named Client XXXXXXXXXX
    Maximum message size (KB) set to 20480
    #2) named Default  XXXXXXXXXX
    Maximum message size (KB) set to 20480
    #3) named relay
    Maximum message size (KB) set to 20480
    Use Exchange Management Shell to check settings
    #1) Get-ADSite
    Returns:
    Name                           HubSiteEnabled
    Default-First-Site-Name        False
    #2) Get-ADSiteLink
    Name                      ADCost     ExchangeCost    Sites
    DEFAULTIPSITELINK         100                        {xxxx.local/Configuration/Si...
    #3) Get-ADSiteLink | select Max*
    MaxMessageSize
    unlimited
    Exchange Management Console>Expand Organization Configuration>Click on Hub Transport item>Click on Transport Rules tab
    No rules
    Article #2 
    http://eightwone.com/2010/09/29/exchange-message-size-limits/
    COMMAND: Get –TransportConfig
    results:
    ClearCategories                     : True
    ConvertDisclaimerWrapperToEml       : False
    DSNConversionMode                   : UseExchangeDSNs
    ExternalDelayDsnEnabled             : True
    ExternalDsnDefaultLanguage          :
    ExternalDsnLanguageDetectionEnabled : True
    ExternalDsnMaxMessageAttachSize     : 10 MB (10,485,760 bytes)
    ExternalDsnReportingAuthority       :
    ExternalDsnSendHtml                 : True
    ExternalPostmasterAddress           :
    GenerateCopyOfDSNFor                : {}
    HygieneSuite                        : Standard
    InternalDelayDsnEnabled             : True
    InternalDsnDefaultLanguage          :
    InternalDsnLanguageDetectionEnabled : True
    InternalDsnMaxMessageAttachSize     : 10 MB (10,485,760 bytes)
    InternalDsnReportingAuthority       :
    InternalDsnSendHtml                 : True
    InternalSMTPServers                 : {}
    JournalingReportNdrTo               : <>
    LegacyJournalingMigrationEnabled    : False
    MaxDumpsterSizePerDatabase          : 18 MB (18,874,368 bytes)
    MaxDumpsterTime                     : 7.00:00:00
    MaxReceiveSize                      : 20 MB (20,971,520 bytes)
    MaxRecipientEnvelopeLimit           : 500
    MaxSendSize                         : 20 MB (20,971,520 bytes)
    MigrationEnabled                    : False
    OpenDomainRoutingEnabled            : False
    Rfc2231EncodingEnabled              : False
    ShadowHeartbeatRetryCount           : 12
    ShadowHeartbeatTimeoutInterval      : 00:15:00
    ShadowMessageAutoDiscardInterval    : 2.00:00:00
    ShadowRedundancyEnabled             : True
    SupervisionTags                     : {Reject, Allow}
    TLSReceiveDomainSecureList          : {}
    TLSSendDomainSecureList             : {}
    VerifySecureSubmitEnabled           : False
    VoicemailJournalingEnabled          : True
    HeaderPromotionModeSetting          : NoCreate
    Xexch50Enabled                      : True
    COMMAND: 
    Set-TransportConfig –MaxReceiveSize 20MB –MaxSendSize 20MB
    C:\Windows\system32>Set-TransportConfig -MaxReceiveSize 20MB -MaxSendSize 20MB
    WARNING: The command completed successfully but no settings of 'Transport Settings' have been modified.
    COMMAND: 
    Get-SendConnector
    Identity                                AddressSpaces                         
     Enabled
    Internet                                {SMTP:*;1}                             
    True
    COMMAND: 
    Set-SendConnector -Identity Internet -MaxMessageSize 20MB
    WARNING: The command completed successfully but no settings of 'Internet' have been modified.
    COMMAND: 
    Get-ReceiveConnector
    Identity                                Bindings                                Enabled
    XXXXXXXXXX\Default XXXXXXXXXX           {0.0.0.0:25}                           
    True
    XXXXXXXXXX \Client XXXXXXXXXX     {:::587, 0.0.0.0:587}                   True
    XXXXXXXXXX \relay                        {0.0.0.0:25}                           
    True
    COMMAND: 
    Get-ReceiveConnector | fl Identity,MaxMessageSize
    Identity       : XXXXXXXXXX \Default XXXXXXXXXX
    MaxMessageSize : 20 MB (20,971,520 bytes)
    Identity       : XXXXXXXXXX \Client XXXXXXXXXX
    MaxMessageSize : 20 MB (20,971,520 bytes)
    Identity       : XXXXXXXXXX \relay
    MaxMessageSize : 20 MB (20,971,520 bytes)
    COMMAND: 
    Get-AdSiteLink | fl Name,*max*
    Name           : DEFAULTIPSITELINK
    MaxMessageSize : unlimited
    COMMAND: 
    Get-RoutingGroupConnector <ConnectorID> | FL Name, *Max*
    No routing group connectors are installed
    Individual
    Recipient Configuration > Mailbox>Properties of the User> Activate tab Mail Flow Settings> Properties>Message Size Restrictions settings:
    Set to 20480 for send and receive for all.
    Re-tested and had the same problem. 
    Post on Technet.

    ExchangeITPro,
    Thank you for your reply.
    >what SP are you at?
    As noted in the first paragraph: "We have an Exchange 2010 server, running under Windows 2008R2. Both
    the server and Exchange are current for Windows and Exchange updates. Exchange is on SP3 installed about a month ago with no errors reported in the event logs."
    >try restarting the transport services.
    Done previously as well as the entire server. No change.

  • Exchange 2010 - Virtual Directory Internal & External URL's with Wildcard Cert

    Hi Guys
    I am trying to determine if my Exchange 2010 server Virtual Directory URL's are setup according to best practice. I'm sure anyone with good Exchange experience will instantly be able to tell me if my Virtual Directory DNS is correct or could cause issues.
    Scenario:
    Hosted Exchange 2010 SP1. Multiple client mail domains hosted
    2x CA, 2x HT, 2x MB, 2x DC
    Wildcard *.example.co.za certificate being used on CA servers
    AD domain is he.example.za.net
    CA Server naming example: ca1.he.example.za.net, ca2.he.example.za.net
    he.example.net DNS is done by DC servers
    External name used by clients: outlook.example.co.za (For Outlook setup and OWA access)
    outlook.example.co.za has two A records pointing to the CA IP's
    PROBLEM/CONCERN:
    We have a random OWA log out issue that we believe might be due to ambiguous DNS names being used.
    If I change the Virtual Directories External URL to be the FQDN of the server, we get a Certificate Error in clients (due to the .co.za Wildcard). The external URL clients use
    must be on .co.za.
    So are the Virtual Directory URL's causing the CA servers to loose track of who is authenticated in where (leading to OWA disconnection)? Is it fine to load balance the CA servers with the DNS the way we are doing currently? Any other issues you see?
    Current Virtual Directory settings:
    Note that they are identical on CA1 and CA2
    [PS] C:>Get-OabVirtualDirectory -server ca2 |fl *url
    InternalUrl : https://outlook.example.co.za/OAB
    ExternalUrl : https://outlook.example.co.za/OAB
    [PS] C:>Get-WebServicesVirtualDirectory -Server ca2 |fl *url
    InternalNLBBypassUrl : https://ca2.he.example.za.net/ews/exchange.asmx
    InternalUrl          : https://outlook.example.co.za/ews/Exchange.asmx
    ExternalUrl          : https://outlook.example.co.za/ews/Exchange.asmx
    [PS] C:>Get-ActiveSyncVirtualDirectory -Server ca2 |fl  *url
    MobileClientCertificateAuthorityURL :
    InternalUrl                         : https://outlook.example.co.za/Microsoft-Server-ActiveSync
    ExternalUrl                         : https://outlook.example.co.za/Microsoft-Server-ActiveSync
    [PS] C:>Get-EcpVirtualDirectory -Server ca2 |fl  *url
    InternalUrl : https://ca2.he.example.za.net/ecp
    ExternalUrl : https://outlook.example.co.za/ecp
    [PS] C:>Get-OwaVirtualDirectory -Server ca2 |fl  *url
    Url             : {}
    Exchange2003Url :
    FailbackUrl     :
    InternalUrl     : https://ca2.he.example.za.net/owa
    ExternalUrl     : https://outlook.example.co.za/owa
    [PS] C:>Get-AutodiscoverVirtualDirectory |fl *url, server
    InternalUrl :
    ExternalUrl :
    Server      : CA1
    InternalUrl : https://outlook.example.co.za/
    ExternalUrl : https://outlook.example.co.za/
    Server      : CA2
    REALLY APPRECIATE SOME EXPERT ADVISE. Thanks.

    Hi Kane,
    Why did not you use cas array to load balance client connectivity?
    If you create a CAS array, you can assign an virtual IP (VIP) for the CAS array FQDN (e.g CASarray.example.za.net), and then point all the Virtual Directories internal URL to CAS array fqdn;
    For external, you can point outlook.example.co.za to VIP which had been assigned to CAS array.
    I recommend you refer to the following article to understand CAS array:
    http://technet.microsoft.com/en-us/library/ee332317(v=exchg.141).aspx#CASarray
    http://blogs.technet.com/b/ucedsg/archive/2009/12/06/how-to-setup-an-exchange-2010-cas-array-to-load-balance-mapi.aspx
    http://blogs.technet.com/b/exchange/archive/2012/03/23/demystifying-the-cas-array-object-part-1.aspx
    Best regards,
    Niko Cheng
    TechNet Community Support

  • Remove Exchange 2010 DC from single server environment coexisting with Exchange 2013

    My new Exchange server (2013) has completed all the migration steps including public folders. Mail is working well.  I do not use the old DC running Exchange 2010 for any local domain logins or computer control, it is strictly for OWA as is my new Exchange
    2013.  I went through the uninstall of Exchange 2010 with out error but cancelled it after it said it was ready to uninstall. When I shut down Exchange 2010 server mail no longer is available.  What am I missing? I am using same Public IP and different
    private (192.168.1.4 new EXchange 2013, 192.168.1.7 for Exchange 2010) I changed these settings in my asa Firewall and that is working with new settings as well.  Send and Receive connectors are on new while old one have been deleted.  Do my MX records
    need to be updated to reflect new server (ex2) as opposed to old server name (ex)? 
    You can come to Maui for a "Site Inspection" lol!
    System Admin

    Hi
    You need to make sure all your DNS settings are correct with the new server IP as well as autodiscover. Remove any routing connectors between exchange 2010 and 2013.
    Not best practice to run exchange on a DC but if you comfortable you have migrated all system mailboxes, user mailboxes and that the settings on your new server match the old one then proceed with the uninstall.
    Your ISP will obviously route mail to your firewall as you are doing the NAT from there.

  • Installing Exchange 2010 on Server 2008 R2 Get error with Hub Transport Role

    Hub Transport Role
    Failed
    Error:
    The following error was generated when "$error.Clear();
              install-MsiPackage `
              -PackagePath ($RoleInstallPath + "TransportRoles\agents\Hygiene\ASEntIRS.MSI") `
              -LogFile ($RoleSetupLoggingPath + "\InstallASEntIRS.msilog") `
              -PropertyValues ("ALLUSERS=1") `
              -UpdatesDir $RoleUpdatesDir
            " was run: "Installing product D:\Program Files\Microsoft SQL Server\Microsoft\Exchange Server\V14\TransportRoles\agents\Hygiene\ASEntIRS.MSI failed. Fatal error during installation. Error code is 1603.".
    Installing product D:\Program Files\Microsoft SQL Server\Microsoft\Exchange Server\V14\TransportRoles\agents\Hygiene\ASEntIRS.MSI failed. Fatal error during installation. Error code is 1603.
    Fatal error during installation
    Elapsed Time: 00:00:01
    Client Access Role
    Cancelled

    Hi,
    From the description, I recommend you copy the Exchange installation files to the local machine, or download a fresh copy of Exchange 2010 and then reinstall it.
    Besides, please ensure that you install Exchange 2010 on 64-bit edition of Windows Server 2008 R2 Standard with SP1 or Windows Server 2008 R2 Enterprise with SP1.
    If the issue persists, please refer to the following KB further troubleshooting.
    You receive error 1603 when you try to install the Exchange Server 2010 RU1
    https://support.microsoft.com/kb/981474
    Hope it helps.
    If you need further assistance, please feel free to let me know.
    Best regards,
    Amy
    Amy Wang
    TechNet Community Support

  • Exchange 2010 SP3 DAG Witness/Quorom Server Placement with 3 Datacenters

    Hi we have 2 Exchange 2010 SP3 Server in the same Organization in a DAG
    First one in Datacenter 1 in Germany
    Second one in Datacenter 2 in Austria
    There is a Third Datacenter available in Switzerland
    Where should we place the Witness Server?
    Our major concern is not a WAN Link will go down, most time a Datacenter will loose Power for some hours due
    maintenance work or other things.
    Is it a good idea to place the Witness Server in the third Datacenter!?
    We found a Document which some missconception which talks about placing the witness always in
    the primary Datacenter. But the Datacenter Switchover Document for Exchange 2013 says use a third Datacenter.
    Is that also okay for Exchange 2010 or are they totally different?
    Thank you in advance
    Troga

    Hi,
    It is a new configuration option in Exchange 2013 that we use a third location for hosting the witness server.
    Placing FSW in the third location will privide the ability automatically failover databases to the other datacenter in response to a datacenter-level failure event.
    For more details, you can look at the "Witness server placement considerations" section in the following article.
    http://technet.microsoft.com/en-us/library/dd298065(v=exchg.150).aspx
    Best regards,
    Belinda Ma
    TechNet Community Support

  • New replacement Exchange 2010 server doesn't want to integrate with other two.

    I've run "winrm quickconfig" as this error suggests on ALL THREE servers and it says that everything is configured locally and remotely.

    I have a triple setup Exchange 2010 system and one of my exchange servers went down hard and I had to rebuild it.  it's been a while since I did this.  I'm running Windows Server 2012 R2 on the replacement serverand windows 2k8 R2 on the other two that remained running.
    Installation of Exchange 2010 went fine, but when I attempt to start the EMC on the new machine it can't make a connection to itself.
    I've completely removed the old server from the configuration, and the new server is using a new host name even, but I'm getting the following error.
    This topic first appeared in the Spiceworks Community

  • Exchange 2010 ambiguous URL'S issue while coexist with exchange 2013

    Hi ,
    Please correct me if i am wrong and also all of you tell me your valuable suggestions.
    Like as said in the below article we are having an exchange 2010 ambiguous url's in place.
    Referred
    article : 
    http://blogs.technet.com/b/exchange/archive/2013/05/23/ambiguous-urls-and-their-effect-on-exchange-2010-to-exchange-2013-migrations.aspx
    As said in this article, if we have exchange 2010 ambiguous url's in place we will face issues during exchange 2013 coexistence.I agree with that point .
    Question : On such case why don't we use a separate namespace for internal and external outlook anywhere settings in exchange 2013 which is different from cas array name and also there is no need to disturb the existing exchange 2010
    environment by changing the rpc client access attribute in exchange 2010 databases or by forcing the exchange 2010 internal outlook clients to connect via OA. Please clarify my doubt and say whether the mentioned scenario is possible or not ?
    Note : Same time please consider the new namespace which is going to be utilized on exchange 2013 outlook anywhere settings is available on SAN certificate.
    Regards
    S.Nithyanandham

    Hi ,
    Please someone shed light on this case.
    Regards
    S.Nithyanandham
    Thanks & Regards S.Nithyanandham

  • Exchange 2010 SP2 Public Folders Stubborn Replicas (OAB)

    I migrated to a new server with 2010 SP3 all is working good, I am able to see all Public Folders and their contents fine. Now I need to delete this stubborn Public Folder on the older 2010 SP2 server to decommission it. But I get the dreadful 'you cannot
    delete this database because it contain replicas' blah blah. Very annoying.
    This is what the stats pulled up. They are not folders to me, and the new server is the default for OAB. Not sure what to do, I just want to delete this database the right way without resorting to ASIEDIT. I do not want to use that tool, read many horrible
    stories of people deleted the database only to have hours of after affects where other public stores went into an inconsistent state. HELP! 
    [PS] C:\Program Files\Microsoft\Exchange Server\V14\scripts>Get-PublicFolderStatistics -server server-04
    Name                                     ItemCount                                  
                        LastAccessTime
    EX:/o=LMV/ou=Exchange Administrative ... 28                                                       10/25/2014 9:20:35 PM
    EX:/o=LMV/ou=first administrative group  10                                                       10/25/2014 9:13:30
    PM
    OAB Version 2                            28                                          
                10/25/2014 9:44:33 PM
    OAB Version 4                            16                                          
                10/25/2014 9:44:33 PM

    Did you create replicas of these folders on the other server and remove the replicas from the server you want to uninstall? Have you configured the OAB so that it's generated on the new server?
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Exchange 2010: Redirect Logging folder

    I need to redirect the E:\Exchange\V14\Logging folder to L:\Logging.  Will the mklink be able to redirect the folder?
    mklink /j E:\Exchange\V14\Logging folder  L:\Logging
    Is there a better option?

    Hello,
    Since different kinds of logging files are store under the folder, I am afraid its location cannot be changed.
    Thanks,
    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]
    Simon Wu
    TechNet Community Support

  • Exchange 2010 cross subnet Dag - Errors creating DB copies in DR site

    We are running exchange 2010 standard edition in our main site with 2 mailbox servers in a DAG. I've added 2 more mailbox servers in a DR site connecting over a 20Mb fiber connection. I've tried adding one of the DR mailbox servers over to the DAG as database
    server, also tried updating copies of the database after it fails to update it.  Been working with Microsoft support on this but they have been little slow getting back with me so wanted to see if I can find anyone that has had this issue before. We've
    changed TCP global settings, they've set the Cluster setting for samesubnet and crosssubnet threshholds settings to recommended, made sure my DAG replication networks were correct and that's about it so far.  Tried running the update database
    from GUI and shell but to no avail.  Seems like it is copying the logs and database but fails at the very end.  We thought it might be backup software running so we turned that off completely.  Here are the different error messages I get..
     A source-side operation failed while performing seed operation.  error occurred whil communicating with mbx-01 (source server..)  unable to read data from transport connection..  connected host failed to respond..
    A source side operation failed performing seed operation.  An I/O error occurred while attempting to access file ..CatalogData-...ci on source server could not be opened. sys cannot find file.
    Information Store (1988) Mailbox-MBX-01:  The internal database copy (for seeding or analysis purposes) has been stopped because it was halted by the client or because the connection with the client failed.
    Any help is appreciated..
    Michael Duhon

    Hello,
    I recommend you try to restart Microsoft Exchange Replication Service to check the result.
    If the issue persists, please try to rebuild the Index for your database to check the result.
    If you have any feedback on our support, please click
    here
    Cara Chen
    TechNet Community Support

Maybe you are looking for