none
Users Can't login to Exchange Server 2013 CU5

    Question

  • I have an issue with exchange server 2013 that users can't to login to exchange from outlook or OWA.

    there is a free space on the server more than 500 GB, but i don't know why asking for free space as mentioned on below 

    on event viewer i found errors :

    * The SMTP availability of the Receive connector Default Frontend was low (97 percent) in the last 15 minutes.

    * The performance counter '\\BHEXCH02\LogicalDisk(HarddiskVolume1)\Free Megabytes' sustained a value of '107.00', for the '15' minute(s) interval starting at '7/24/2017 10:03:00 AM'. Additional information: None. Trigger Name:DatabaseDriveSpaceTrigger. Instance:harddiskvolume1

    Monday, July 24, 2017 10:45 AM

Answers

  • When citing an entry in the event logs, please post the entire event log entry.  You are welcome to use the handy-dandy "copy to clipboard" button in the event log detail window to assist you with this.

    You're running out of disk space on the volume shown in the second message.  If you don't think so, you might want to open a ticket with Microsoft Support to report a bug.  But before you do that, you should upgrade to the latest cumulative update, which is CU17, since CU5 is over three years out of date.

    https://technet.microsoft.com/en-us/library/hh135098(v=exchg.150).aspx

    Note that you'll have to upgrade to CU15, upgrade .NET Framework to 4.6.2 (not 4.7) and then upgrade to CU17.  Maybe that'll fix your problem and you won't have to open a ticket.


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Monday, July 24, 2017 8:35 PM
    Moderator

All replies

  • When citing an entry in the event logs, please post the entire event log entry.  You are welcome to use the handy-dandy "copy to clipboard" button in the event log detail window to assist you with this.

    You're running out of disk space on the volume shown in the second message.  If you don't think so, you might want to open a ticket with Microsoft Support to report a bug.  But before you do that, you should upgrade to the latest cumulative update, which is CU17, since CU5 is over three years out of date.

    https://technet.microsoft.com/en-us/library/hh135098(v=exchg.150).aspx

    Note that you'll have to upgrade to CU15, upgrade .NET Framework to 4.6.2 (not 4.7) and then upgrade to CU17.  Maybe that'll fix your problem and you won't have to open a ticket.


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Monday, July 24, 2017 8:35 PM
    Moderator
  • Hi,

    You can follow steps below to solve this issue:

    1. Go to “C:\Program Files\Microsoft\Exchange Server\V15\Bin” and open the “Microsoft.Exchange.Diagnostics.Service.exe.config” file.
    2. Find the following line and change it to Enabled=”False”
    <add Name=”Microsoft.Exchange.Diagnostics.Service.ExchangeJobs.Triggers.DatabaseDriveSpaceTrigger” Assembly=”Microsoft.Exchange.Diagnostics.Service.ExchangeJobs.dll” Enabled=”True” Role=”Mailbox” /> 
    3. Save the file.

    Note: Since applying Exchange 2013 CU6, this error has not reproduced.


    Best Regards,

    Manu Meng
    TechNet Community Support


    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 tnmff@microsoft.com.
    Tuesday, July 25, 2017 4:30 PM
    Moderator
  • When citing an entry in the event logs, please post the entire event log entry.  You are welcome to use the handy-dandy "copy to clipboard" button in the event log detail window to assist you with this.

    You're running out of disk space on the volume shown in the second message.  If you don't think so, you might want to open a ticket with Microsoft Support to report a bug.  But before you do that, you should upgrade to the latest cumulative update, which is CU17, since CU5 is over three years out of date.

    https://technet.microsoft.com/en-us/library/hh135098(v=exchg.150).aspx

    Note that you'll have to upgrade to CU15, upgrade .NET Framework to 4.6.2 (not 4.7) and then upgrade to CU17.  Maybe that'll fix your problem and you won't have to open a ticket.


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Thank you Ed, after upgrade to latest CU is working fine and issue solved.
    Wednesday, July 26, 2017 6:29 AM
  • Cheers! Glad to see issue has been solved.

    Best Regards,

    Manu Meng
    TechNet Community Support


    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 tnmff@microsoft.com.

    Wednesday, July 26, 2017 11:10 AM
    Moderator