Hi All

Gotten a SSL certificate from a provider, but the provider mention that they no longer allow (.local) domain to be added in the certificate.
Because of this , all users when open outlook will prompt a error saying certificate mismatch. Have most of the internal URL to mail.domain.com accept for autodiscover URL. Currently is using Exchange 2013 with Microsoft Server 2012 Standard.

Thanks in advance

Hi,

First, sorry for the long post, I have a few really weird issues, I'm trying to resolve since yesterday, without any luck :(

It would be great if someone could point me into the right direction since I don't even know where to start looking.

I hope that those issues are related and that they can be used to narrow it down:

Connecting from the internet works fine. ActiveSync autodiscovery and Outlook anywhere autodiscovery work and remote analyzer can't find any problems.

OWA internally as well as externally works fine too, the only problems are with Outlook when used from inside the network.

Setup:

The Exchange server 2013 is installed on a separate win2012 server.

The DC (also a win2012 server) is on the same network and currently none but one workstation is joined the domain (for testing purposes, migrating the other clients from a nt4 domain is planned).

The DC is also used as a DNS server for all clients. It's a split domain and quite identical to the public dns, except for the internal hosts and the records for the exchange pointing to their respective internal ips.

All clients run Windows XP SP3.

The problems occur when logging on with a local user account aswell as when logging on with a nt4 domain user account, it doesn't matter at all. It also doesn't matter whether Outlook 2007 or 2010 is used.

Configuring 1 Outlook profile (cached mode is always off)/user account works.

Autodicovery works. When starting Outlook for the first time a login/password prompt appears after which the profile is immediately available. Trying the autodiscovery test from Outlook also completes without any problems.

Accessing public folders works too, but trying to open the personal online archive results in an error: translation: folder couldn't be opened, error logging into Exchange.

Accessing the same personal archive via owa from inside the local or remote networks works without problems!

But the real issues start when configuring a second Outlook profile for the same user account on the same machine shortly afterwards.

While autodicovery runs it suddenly prompts for login/password after which outlook freezes for a few minutes, but it completes.

When starting Outlook with this second profile, the login prompt appears again after which Outlook freezes trying to connect to Exchange. It stays like that like forever. While this is going on an event 1309, code 3005 is logged (client closed connection..)

Application domain: /LM/W3SVC/1/ROOT/Rpc-7-130068161998831561
Trust level: Full
Application Virtual Path: /Rpc
Application Path: E:\Exchange Server\V15\FrontEnd\HttpProxy\rpc\
Machine name: EMAIL
Process information:
Process ID: 2508
Process name: w3wp.exe
Account name: NT-AUTORITÄT\SYSTEM
Exception information:
Exception type: HttpException
Exception message: Der Client hat die Verbindung getrennt.
   bei Microsoft.Exchange.HttpProxy.ProxyRequestHandler.EndProcessRequest(IAsyncResult result)
   bei System.Web.HttpApplication.CallHandlerExecutionStep.OnAsyncHandlerCompletion(IAsyncResult ar)

  Request information:
Request URL: https://<fqdn>:443/rpc/rpcproxy.dll?fba28549-98eb-4fde-8b6a-6aac708a70ca@ikjf.at:6001
Request path: /rpc/rpcproxy.dll
User host address: 192.168.0.167
User: <DOMAIN>\Administrator
Is authenticated: True
Authentication Type: NTLM
Thread account name: NT-AUTORITÄT\SYSTEM
Thread information:
Thread ID: 16
Thread account name: NT-AUTORITÄT\SYSTEM
Is impersonating: False
Stack trace: bei Microsoft.Exchange.HttpProxy.ProxyRequestHandler.EndProcessRequest(IAsyncResult result)
   bei System.Web.HttpApplication.CallHandlerExecutionStep.OnAsyncHandlerCompletion(IAsyncResult ar)

Afterwards the error about the standard mail container can't be opened et.c. appears.

The same event (although not everytime it seems) is also logged when trying to access the personal archive, but for user: <DOMAIN>\SM_a68acd26159349938

Finally, when trying to setup an Outlook profile on the ADC joined test machine, it states: the action couldn't be completed. The Exchange server couldn't be reached, Outlook must be in onlinemode or connected....

Trying the autodicovery test in Outlook on that machine doesn't tell about any problems either (found through scp) and the urls match the fqdn for the Exchange server.

Although the autodiscovery urls for a local client that isn't joined the ADC domain differ (same dns server): <exchange host name>.<domain>/Autodiscover/Autodiscover.xml <-- adc joined machine vs. autodiscover.<domain>/Autodiscover/Autodiscover.xml

Apart from the event mentioned above, the following warnings are logged:

A lot of 6002 "Ping of mdb ... timed out after '00:00:00' minutes.  Last successful ping was at ... UTC."

And very rarely:

Failed to read killbit list file because of exception System.IO.IOException: Der Prozess kann nicht auf die Datei "E:\Exchange Server\V15\ClientAccess\owa\15.0.516.30\owa2\ext\killbit\killbit.xml" zugreifen, da sie von einem anderen Prozess verwendet wird.
   bei System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   bei System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   bei System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
   bei System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
   bei System.IO.File.Open(String path, FileMode mode, FileAccess access, FileShare share)
   bei Microsoft.Exchange.Data.ApplicationLogic.Extension.KillBitHelper.TryReadKillBitFile(Int32& refreshRate, DateTime& lastModifiedTime)

And especially during boot: many "Performance counter updating errors"

I really hope that the issues described above are related

Thank you very much for any hint you can give me and for reading all that crap ;)

Max

Hello Everyone,

I installed a new exchange 2013 in Windows Server 2012, post which i can login to OWA and getting e-mails.

When i try to view the e-mail, it says "Your request can't be completed right now. Please try again later"

When i try to compose an e-mail and click on send option it says "The message can't be sent right now. please try again later"

I verified authentication and IIS settings, but couldn't able to figure out what could be the problem.

Kindly share your thoughts.

Hi there!

All of you know the reg key to set to enable the feature that will allow users with expired passwords to change their password (orchange password at next logon).
http://blogs.technet.com/b/exchange/archive/2010/10/06/so-you-want-to-change-your-expired-passwords-in-owa.aspx

On Exchange 2013 this key is set oob.

On Exchange 2010 SP1 RU3 this works fine with UPNs.

But on Exchange 2013 some of the old Problems are back! I am not able to change the Password while using UPN Logonname. Its not a Problem when using the pre-win2k logon domain\username.

UPNs still work fine for normal OWA logon.

Is there any way to resolve this issue?
On OWA virtual folder i set form based authentication to UPN.

Thanks alot and sorry for my english skills ;)

Garfield

Hi

I have setup a test environment with a virtual machine of server 2012 and on a separate virtual machine exchange 2013. OWA works internally and externally and I have a 30day trial of a SAN certificate installed on the exchange server but I am unable to connect outlook 2010 or 2013 to exchange it just keeps saying that THE CONNECTION TO THE MICROSOFT EXCHANGE SERVER IS UNAVAILABLE. I have tried on 3 different computer systems running different os versions and different outlook versions and all have the same problem. I have also tries typing the exchange server by name and ip and I have tried using auto discover to setup outlook but all attempts so far did not work

It definitelly does not work as expecting..

I have disabled for ONE user OWA in ECP web console, but user has still access to hit mailbox via OWA..

I run iisreset, waited couple days (doing some different things of :horse :) .. but still no luck.

Also tryied some powershell cmd, disabled alost everything.. he still can login..

Set-CASMailbox -Identity "my user" -OWAEnabled $False ..

also same with Ews, Ecp .. no luck

any idea ?

My goal : just like in SBS2008 i have to disable OWA for all users and enable for few of them..

Hi all,

I have one AD 2012 and another box of Exchange 2013 all in one roles. We are able to access and operate email as normal. We would like to add roles to Organization Management groups for Reset Password. But, if we try to save the setting, below error shown:

"You dont have access to create, change, or remove the "Reset Password-Organization Management" management role assignment. You must be assigned a delegating role assignment to the management role or its parent in the hierarchy without a scope restriction"

What is the possible issue? I am using administrator account with full privileges.

Hello,

I am asking this at both the Outlook and Exchange forums.  When I try to connect Outlook 2010 at a satellite office to Exchange 2010 at the main office, I get the following error:

The action cannot be completed.  The connection to Microsoft Exchange is unavailable.  Outlook must be online or connected to complete this action.

I click OK and a Microsoft Exchange window pops up with Microsoft Exchange Server: servername.localdomain.local and Mailbox: =SMTP:username@domain.net.

I have tried this on multiple Win7/Outlook 2010 systems, but continue to get the same error.

I can safely connect to Exchange via OWA, Active-sync, etc. and testexchangeconnectivity.com does not come up with any errors.

Any ideas?  Any and all help is greatly appreciated!

Thank you,

Don

Hello,

I can't find in ECP for MS Exchange 2013 function to enable S/MIME for OWA. Can somebody help me? I found only registry update for MS Exchange 2010 SP1 or download S/MIME function for IE7+ for MS Exchange 2010, but I am not sure if I can use it for 2013.

Thank you,

Pavel Hula

I had to delete a users AD & Exchange account. I recreated it with the exact same email address. The user now can't receive internal email from the company but is email from external account. I deleted the auto complete option from my outlook client, tried to send from the GAL and it failed. He did receive the email if I sent it from OWA, and from my gmail account. The image below is the bounce back message. Any help will be appreciated.

I'm running exchange 2010 on server 2k8. He's outlook client is 2010.  

We have a fresh install of Server 2012 and Exchange 2013. The clients that are using 2007 requires a password every time they open outlook. I have checked all of the obvious settings and I have tried serveral things that I have searched on the internet. Any ideas or suggestions will be appreciated.

I am having a bit of an unusual issue with Outlook 2013 and Autodiscover.  At present for all Office 2010/2007/2003, Android, Apple and Windows phone autodiscover works perfectly without any issue  If I use the MS tool to test autodiscover and outlook anywhere the connection comes back 100% with no errors. 

When I try to connect a new Outlook 2013 client I enter in the clients name, email and password information and the process starts, after a moment we get presented with a certificate error.  The error says it is the wrong name on the certificate and that the certificate is expired.  If I open the certificate presented, it is for a totally different company (www .otherdomain.com) that is hosted at the same Domain\Web Hosting service.  If I click ignore the certificate the autodiscover continues and works but I don't want that happening everytime we setup Outlook 2013....

For our company we use a web hosting services that has our main web site at www .domain.com and dns resolves domain.com to this site as well.  What I think may be happening is Outlook 2013 sends a first autodiscover request to https ://domain.com/autodiscover.  This resolves to our hosted web servers which returns the first hosted client to respond and their certificate which is https ://othercompany.com.  Accepting the certificate allows the request to proceed but then fails when no Autodiscovery response returns from that address in time.  Then it makes a request to autodiscover.domain.com and it succeeds in getting the configuration information.

I have ruled out an issue with our certificate if I check it from the shell or from OWA the alternate names and domain names are correct.

So...I opened a call with our hosting services to see if there was anything they could do on their side but I wonder if this is a bug with Outlook 2013?  Why would my config work with everything else except this one new product?  Has anyone else seen a similar issue?  Is there a way to suppress the first autodiscover request from the outlook client in the registry to confirm my suspicion?

I have been trying to do this for a little while

So I added testacct1 and testacct2 into exchange and simply disabled OWA through the ECP – I thought you know … it would work.  It does not.  I found some powershell commands as well but none seem to work yet. 

Get-Mailbox –Identity <username> | Set-CASMailbox -MAPIBlockOutlookRpcHttp:$True

Get-Mailbox –Identity <username> | Set-CASMailbox -OWAEnabled $False

Get-Mailbox –Identity <username> | Set-CASMailbox -OWAMobileAppEnabled $False

Set-CASMailbox <username> -OWAMobileAppEnabled $False

None of those disabled anything.

Hi all,

My lab includes 4PCs (co-existence system) (Win 2008 R2):

PC1: Exchange 2007 Sp3

PC2: Exchange 2010 Sp3

PC3: Exchange 2013 has 1 mailbox: admin2k13@abc.com

PC4: DC (also as DNS server)

From another computer (PC5/non-domain client) open Outlook (2007/2010) create profile for admin2k13@abc.com, but the screen display error as follow:

Outlook cannot log on. Verify you are connected to the network and are using proper server and mailbox name. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action

Check network and PC

+ At PC5, ping to PC3: ok (PC3 and 4 have same network)

+ restart PC5 and PC3: this issue has still occurred

WOrk arround:

+ from PC5, log on admin2k13@abc.com by OWA: successfully

+ can create Exchange 2010/2007 profile into PC5 successfully.

Summary: cannot create Exchange2013 profile by Outlook.

So, please help me to solve it.

Thanks.

Hi

Working on a new 2013 install and when trying to setup out look get the error about the default folders - even though this is the first login by this user. Deleted and recreated outlook profile - same issue.

suspect the problem is with connectivity to exchange as having the same issue with all users now.

Thanks

Hello,

We use Exchange 2013 but some OWA users prefer to use OWA light (not premium). Is there a way to add the choice on the OWA logon page ?

(this option exist in OWA 2010)

Thanks a lot for your help.

Sylvain

Hello all,

Following problem: Exchange server 2013 installed on an windows Server 2012. Client connecting with Outlook 2007 and 2010. All users using cached mode because they are out of the office a lot of time. The problem we have is if the user is on the road , sending an recieving mail is not a problem. While they are in the office the outlook client updates the folders and says "Online". When the user sends a message the message is stuck in the outbox. When clicking on send and recive we got an eror "unknow error 0x8004011C" and while transmitting error 0x80040115 for this action the exchange server should be online... but the server is online because the folders are beeing updated. Looking into autodiscovery and so all url's are correct.

Anyone having a tip ?

many thanks

Chris

Hello all,

i am working on a Exchange 2013 on Windows Server 2012 project. I configured everything great and am able to send and receive email internally and externally.

However, yesterday, my Outlook 2013 client says that there is a proxy server error or that the names of the servers did not match.

I was using a self-signed cert...I have since learned that that is unacceptable. So from what I have read, getting an SSL cert from an actual CA should allow me to connect with no issues.

I want to make the internal and external hostnames the same...mail.itnasa.com. Which is already set up as a domain w/ DNS through DynDNS. I will really have no need to connect to the OWA locally because I will have Outlook clients for that. 

Has anyone else done this before...in theory, should this work?

Thanks in advance for any and all assistance.

We have 2 Exchange 2010 servers in our network; both are installed with CAS, Hub Transport and the Mailbox roles. These servers are in a Database Availability Group.  OWA is also hosted from these servers. We would like to move OWA to the DMZ zone...  CAS will continue to be hosted from the existing Exchange servers.  Unfortunately, we haven’t managed to find any procedures on how to do this?  Maybe we are searching with the wrong key words. Can anybody help with some procedures?  Is there a way to install just the OWA compoents of Exchange from the Exchange installation discs?