A few PC's here have the issue where outlook freezes for 30 sec to a fews mins particularly when changing outlook folders.

It occurs on 2010,2013,2016 and at least 2 user profiles.

I've tried loads of forums, new OST's and even tried disabling IPV6 following one hint.

Still the errors persist - Would you have any suggestions?

Many thanks

Stuart

Stuart

Hello, we have one particular user whose network account experiences 1 bad password attempt every 5 minutes.  After 5 bad password attempts it locks his AD account.  I have pinpointed it to the following audit failure events from our exchange 2013 server that occurs for each bad password attempt he gets:

First event that gets recorded:

Log name: Security

Source: Security-Auditing

EventID: 4776

Task Category:  Credential Validation

General:

The computer attempted to validate the credentials for an account.

Authentication Package:MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Logon Account:username
Source Workstation:exchange 2013 server
Error Code:0xC0000064

Second event that gets recorded immediately after the first one:

Log name: Security

Source: Security-Auditing

EventID: 4625

Task Category:  Logon

General:

He had mutiple mobile exchange activesync devices registered under his account.  We removed all of them and signed him out of any other devices we could find that he was logged in to.  Also tried running ExMon to see if I can catch his account trying to authenticate, but his account does not appear in the traces.  We even ran an anti-virus scan on and restarted the exchange server.  He also rebuilt his laptop.  The bad password attempts continue to happen.  Can anyone help me understand why this could be happening?  What does the MSExchangeFrontendTransport.exe do?

We would need to have two Mail Contacts created for one external email address. In our case of a basic school we would need to share parent's email addresses for all teachers - Office 365 users. It is not uncommon that a school is attended by siblings - one is older, one is younger. We tried to create an Exchange directory containing parent's email addressed - a contact is named based on a pupil's name, but in case a contact was created for a younger sibling and we try to create a contact for an older sibling, we receive an error:

The proxy address "SMTP:pupil_1_mother@tld.com" is already being used by the proxy addresses or LegacyExchangeDN of "Younger Sibling". Please choose another proxy address.

How to overcome this and have the same address for both siblings in All Contacts directory. 

#1. I am able to read the outlook emails of particular person from their respective mailbox Folders.
e.g.

Session emailSession = Session.getInstance(properties);
Store emailStore = (IMAPSSLStore) emailSession.getStore(protocol);
IMAPFolder emailFolder = (IMAPFolder) emailStore.getFolder("INBOX");

#2. I have read the already created Universal distribution groups and its members using:

e.g.

EmailAddress emailAddress = new EmailAddress();
emailAddress.setName("SUPPORT");
emailAddress.setAddress(groupEmail);
ExpandGroupResults results = service.expandGroup(emailAddress);
if (!StringUtils.isEmpty(results.getMembers())) {
    results.getMembers().forEach(new Consumer<EmailAddress>() {
        @Override
        public void accept(EmailAddress address) {
            System.out.println(address);
        }
    });
}

One of the ladies in our BDC (Business Development Center) received an email from a customer inquiring about a vehicle, he included a picture of a window sticker in the body of his email.

She then forwarded the email to a salesperson but when the salesperson received the email the embedded picture wasn't  there for his reference.

The lady who received the email went back to her inbox to re-forward the email again and the embedded picture was no longer in her received email and when she checked her 'sent' emails it wasn't included in the 'sent' email to the salesperson.

Does anyone know why this would happen and / or where the picture could be found?

I was at a loss as how to answer / help with her dilemma.

Brad

Hi

The title is a quick summary of the situation.

Exchange 2013 server running with no obvious errors.
Services all up as usual.
I can see mail arriving (I use a third party utility to pick-up from remote server and then pass on to Exchange) and being transferred.
Clients (Outlook 2013 or 2019) all say the are connected to server and up to date - but nothing has arrived or been sent since 31st Dec.
Internal mail is also failing.

I updated the server it lives on on 31st Dec, so initial thought was 'bad update'. I uninstalled those updates - no luck.
Tried with different clients (Outlook, Mail, eM client) and different protocols (ActiveSync, OWA, IMAP) - no luck.
Currently migrating mailboxes from old Db to new, in case of corruption.

Any help or ideas would be appreciated...

Robin

Hello,What does it mean if our self signed cert status is "Revocation check failed"?

We cannot connect to OWA or ECP. I checked IIS and the default website and back end website for both OWA and ECP are set to windows authentication and anonymous authentication are the only thing enabled under the authentication tab. I have checked event logs and nothing shows up.

If I try to pull up webmail or ECP on a windows 10 client, the site loads just fine but it says username and password is incorrect. But if you try to open both sites on the mail server itself, OWA does not load, it says http 403 error the website requires you to login and the ECP give you an http 404 error

I have also tries stopping and starting IIS a few times but nothing seems to be working.

When we open up the exchange powershell utility we get below.  Email is still flowing but we cannot connect to OWA for webmail or not able to manage Microsoft exchange using ECP

VERBOSE: Connecting to maiserverl.domain.ca
New-PSSession : [mail-server-name] Connecting to remote server maiserverl.domain.ca failed with the following error message
: The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the
destination computer. The content type is absent or invalid. For more information, see the
about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha …+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : -2144108297,PSSessionOpenFailedI

Hi,

Please help, there is a weird behaviour on our webmail.

Our SSL is valid and signed by Entrust.

SOmetimes,if users are trying to access the webmail, the info on the certificate is wrong. Prompting the user that the site is not safe.

Sometimes, if you just refresh the page, it will get the valid certificate (with the padlock).

Im not sure if the problem is with entrust or with us?

Thanks in advance

Hello

when I click on "Contacts" for a specific user on OWA in light version of Outlook Web App, this error will appeare: 

Request
Url: https://mail.domain.ir:444/owa/forms/basic/BasicContactView.aspx?ae=Folder&t=IPF.Contact
User host address: 172.25.10.10
User: Abolfazl Soltan
EX Address: /o=MSC/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=40f77edce0ac48c89404bfda7baa66e8-Abolfazl Soltan
SMTP Address: ab.soltani@domain.ir
OWA version: 15.0.1367.0
Mailbox server: MAILDB02.DOMAIN.IR

Exception
Exception type: System.Collections.Generic.KeyNotFoundException
Exception message: The given key was not present in the dictionary.

Call stack
System.ThrowHelper.ThrowKeyNotFoundException()
System.Collections.Generic.Dictionary`2.get_Item(TKey key)
Microsoft.Exchange.Clients.Owa.Basic.Controls.ListViewContents.RenderPhoneNumberColumn(TextWriter writer, Int32 itemIndex)
Microsoft.Exchange.Clients.Owa.Basic.Controls.ListViewContents.RenderColumn(TextWriter writer, ColumnId columnId, Int32 itemIndex, Boolean isBold, Boolean openForCompose)
Microsoft.Exchange.Clients.Owa.Basic.Controls.ListViewContents.ValidatedRender(TextWriter writer, Int32 startRange, Int32 endRange)
Microsoft.Exchange.Clients.Owa.Basic.Controls.ListView.Render(TextWriter writer, String errorMessage)
ASP.forms_basic_basiccontactview_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.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter)
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

But for other users this error don't appear!!!

Please help me!!!

Hi,

I am asking the same question on different forums, but so far no useful hints.

Customer has SBS 2011 with Exchange 2010,working fine for few years. But now, few weeks ago, clients (not all, but some!) with Outlook begun experiencing problems when connecting to SBS local Exchange from outside:

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 my.exchange.server.com. Outlook is unable to connect to the proxy server (Error Code 0) 

What I have tried to resolve?

• Checked installed SSL certificate on Exchange server, cert is OK, and is VALID. Actually, this cert was issued 1,5 years ago and has 2 years validity till 5th of May 2020, so nothing changed there.
• Verified latest updates....none. SBS has not been rebooted or updated for few months, so nothing changed there, too.
• Checked Outlook connectivity test https://testconnectivity.microsoft.com/ and is connectsOK, no errors, all green checks.
• Checked OWA and RPC via https://my.exchange.server.com/owa and /rpc, and both open just fine on LAN and WAN, presenting proper andvalid SSL cert.
• Verified if https://testconnectivity.microsoft.com/ SSL is the same as installed on Exchange - yes, it isthe same SSL, valid and working.
• Tried to connect form different locations with Outlook 2013, 2016 and 2019, but all experience the same problem.
• Checked, if I have for some weird reason PROXY enabled for my internet connection, but no, I do not. Neither does any of other testing locations.
• Tried to run OUTLOOK.EXE /SAFE, but as expected, still no joy.

Possible causes: There's SOPHOS UTM between Exchange server and public internet, but this has been so for years and it was working just fine all the time. However, there's still slight possibility that Sophos UTM somehow changed its internal algorithms in latest update, but I doubt very much. Just to be 100% sure, I disabled LetsEncrypt SSL on Sophos UTM and deleted LE SSL cert from Sophos just to see, if error message changes. But no, even after those changes, Outlook spits out the same error as before, and on the other hand, Outlook Connectivity test PASS OK, just as before.

And NO, none of these recommended actions do NOT help: Error message when Outlook tries to connect to a server by using an RPC connection or an HTTPS connection: "There is a problem with the proxy server's security certificate"

I would now like to have this answer:

Outlook says: "The name on the security certificate is invalid or does not match the name..."

My question: "Hey Outlook, please, show mi which certificate you are looking at, please!"

I would really like to know, what is he looking at, because from any point of view I see proper and valid certificate, so how can he see something else?

Any idea?

Hi Support

We recently have a very large number of users started experiencing an issue, where Outlook would prompt the user "Your mailbox has been temporarily moved to Microsoft Exchange server.
A temporary mailbox exists but might not have all of your previous data.
You can connect to the temporary mailbox or work offline with all of your old data.
If you choose to work with your old data, you cannot send or receive e-mail messages."

It appears rebuilding profile can help address the situation.

However, the background of the storage is due to an incident, we had to create dial tone mailboxes and merge data from backup together with Dial tone.

This issue started appearing after dial tone mailboxes are created.

Is there a way that we can make the issue go away by running some server side powershell cmdlets? Or is rebuilding profile for a few hundred users the only way to go?

Hello,

We are having issues with one specific mailbox. User A sends a mail to a distribution group.
Members of this distribution group receives these mail. When the users deletes these mail even before they read or mark the mail as read, user A receives a message which says:

Subject: Unread, followed by original subject

Your unread message:

To: User B
Subject: original subject
Send:  date, time and timezone

Has been deleted on date, time and timezone.

Important to notice is that user A didn't use "Ask for read confirmation" or "Ask for receive confirmation". 

What could be the possible cause for this behavior?

Kind regards,

Hello

I'm hoping somebody might be able to assist me in finding an issue.

I've 2 mailboxes that, starting last month, intermittently request a password when using Outlook 2013 or 2016.

Both these mailboxes are in addition to the users main mailboxes, which don't prompt for details.

I've not been able to find anything wrong with the mailbox and Exchange reports the mailbox and database in good health.

This only seems to affect users that have a second mailbox on their profile, or in our case the users are given full access to the mailbox so it appears in their folder list within Outlook.

What's strange is, that we ignore the message or cancel it, you can still get to the mailbox.  If you decided to enter your domain credentials in, you're prompted to enter them 4 times.  Now, this could be a coincidence but we have 4 domain controllers so I wondered if it Outlook is trying to authenticate to each of those.

I've reset the password, removed the Windows Credentials (via Control Panel) and also re-created Outlook profiles, all have no affect.

I'm open to suggestions if anybody has any, please.  :o)

Thanks, Richard

Running Exchange Server 2016 in a learning environment.

Running Windows 10 with Outlook 2013.

Issue regarding two users: User1 has given Send on Behalf and Full Access to User2 through an Administrator account in Exchange Admin Center. User2 can Send on Behalf without issue but does not see User1's mailbox.

User1 uses Outlook to Delegate Access, adds User2 and sets permissions for Calendar and Inbox to Editor status (read, write and modify).

Open Outlook as User2, see the email informing User2 of new delegated status. Still cannot see User1 mailbox. User1 Calendar now available but has a status of No Connection with red ! in a yellow diamond.

Outlook shows "Connected to: Microsoft Exchange", able to send/receive emails.

Logged into OWA as User2, from here they're able to view the mailbox and calendar.

Deleted and recreated Outlook profiles. Still not working.

Reinstalled Outlook. Still not working.

Looking for any assistance I can get! Thanks.

Hi,

I am asking the same question on different forums, but so far no useful hints.

Customer has SBS 2011 with Exchange 2010,working fine for few years. But now, few weeks ago, clients (not all, but some!) with Outlook begun experiencing problems when connecting to SBS local Exchange from outside:

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 my.exchange.server.com. Outlook is unable to connect to the proxy server (Error Code 0) 

What I have tried to resolve?

• Checked installed SSL certificate on Exchange server, cert is OK, and is VALID. Actually, this cert was issued 1,5 years ago and has 2 years validity till 5th of May 2020, so nothing changed there.
• Verified latest updates....none. SBS has not been rebooted or updated for few months, so nothing changed there, too.
• Checked Outlook connectivity test https://testconnectivity.microsoft.com/ and is connectsOK, no errors, all green checks.
• Checked OWA and RPC via https://my.exchange.server.com/owa and /rpc, and both open just fine on LAN and WAN, presenting proper andvalid SSL cert.
• Verified if https://testconnectivity.microsoft.com/ SSL is the same as installed on Exchange - yes, it isthe same SSL, valid and working.
• Tried to connect form different locations with Outlook 2013, 2016 and 2019, but all experience the same problem.
• Checked, if I have for some weird reason PROXY enabled for my internet connection, but no, I do not. Neither does any of other testing locations.
• Tried to run OUTLOOK.EXE /SAFE, but as expected, still no joy.

Possible causes: There's SOPHOS UTM between Exchange server and public internet, but this has been so for years and it was working just fine all the time. However, there's still slight possibility that Sophos UTM somehow changed its internal algorithms in latest update, but I doubt very much. Just to be 100% sure, I disabled LetsEncrypt SSL on Sophos UTM and deleted LE SSL cert from Sophos just to see, if error message changes. But no, even after those changes, Outlook spits out the same error as before, and on the other hand, Outlook Connectivity test PASS OK, just as before.

And NO, none of these recommended actions do NOT help: Error message when Outlook tries to connect to a server by using an RPC connection or an HTTPS connection: "There is a problem with the proxy server's security certificate"

I would now like to have this answer:

Outlook says: "The name on the security certificate is invalid or does not match the name..."

My question: "Hey Outlook, please, show mi which certificate you are looking at, please!"

I would really like to know, what is he looking at, because from any point of view I see proper and valid certificate, so how can he see something else?

Any idea?

Abp

We're restored our DCs, Exchange server from Veeam into an isolated DR environment and can see Email via OWA and Win7 box or 2012 OS vm --with an install of Outlook 2016.  However, we can't get any Windows 10 machines or even 2016 servers with Outlook 2016 to connect to our Exchange server, even though these both work fine in production. 

Our DCs are 2016 Server, Exchange is 2010SP3, and use Outlook 2016.   The message we get is "Cannot start MS Outlook. Cannot open Outlook window.  The set of folders cannot be opened. The attempt to log onto MS Exchange has failed."   I've gone through a good number of suggested fixes, any help greatly appreciated.

Thanks

Jim

jim_ea