A post on experts-exchange.com says "A big warning about SSL offloading, and that is proxy to a different site *will not work* for Exchange ActiveSync or OWA."

http://www.experts-exchange.com/Networking/Protocols/SSL/Q_28486166.html

I'm unable to find any other information to corroborate that statement. Can someone point me to MS documentation that would confirm or deny that proxying to a different site will not work with SSL Offloading enabled?

Thanks

Chad

We are in an hybrid environment of Exchange OnPremises and Exchange Online and in the OnPremises environment we have cohexistence of Exchange 2010 and Exchange 2013. 

As a backup solution we have CA Arcserve Backup, that allow us to make a backup in document level of the exchange 2013 mailboxes. 

We still can´t do the backup document level. In the logs files from the ca agent installed in the server, we found some MAPI errors. 

We followed all the articles bellow, but without success. 

We had a remote support from CA and they told us that we are facing a problem on the Exchange Server. 

We ran the Test-MapiConectivity that returns Success.

Below of the links, follow the logs, if someone could help-me to diagose the MAPI on Exchange 2013, I will be vary glad. 

http://www.arcserve-knowledgebase.com/index.php?View=pdf&EntryID=4969

https://arcserve.zendesk.com/hc/en-us/articles/201992659-Exchange-2013-Document-Level-Backup-fails-to-backup-n-mailboxes-Error-AE9609-A-necessary-Exchange-service-is-not-running-Please-start-the-related-service-on-the-Exchange-server-manually-

http://www.arcserve-knowledgebase.com/index.php?View=entry&EntryID=5481

https://arcserve.zendesk.com/hc/en-us/articles/202153889-AE9609-AE9603-AW9627-ErrErr-800000008004011d

https://communities.ca.com/thread/241692506

https://communities.ca.com/thread/241690757 

http://arcserve-knowledgebase.com/index.php?View=entry&EntryID=2

http://arcserve-knowledgebase.com/index.php?View=entry&EntryID=1193

http://arcserve-knowledgebase.com/index.php?View=entry&EntryID=2522

http://arcserve-knowledgebase.com/index.php?View=pdf&EntryID=4600

https://arcserve.zendesk.com/hc/pt-br/requests/10740

<01/28/2015-17:36:16:852 TID:20ac>Begin MAPILogonEx() failed MAPICODE: 0 
<01/28/2015-17:36:16:992 TID:20ac>End MAPILogonEx() failed MAPICODE: 0 
<01/28/2015-17:36:17:08 TID:20ac>After  MAPILogonEx() before call my failed MAPICODE: 0 

Thanks in advance!

Fabio Martins MCDST/MCSA Brasil!!!

Fabio Martins MCDST/MCSA Brasil!!!

On Step 1 of 7, the "Mailbox role: Client Access service," I got an error during installing:

Error:
The following error was generated when "$error.Clear(); 
          Install-ExchangeCertificate -WebSiteName "Exchange Back End" -services "IIS, POP, IMAP" -DomainController $RoleDomainController -InstallInTrustedRootCAIfSelfSigned $true
          if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
          {
            Install-AuthCertificate -DomainController $RoleDomainController
          }
        " was run: "Could not grant Network Service access to the certificate with thumbprint 8FCF29D8F3A4D8E3D649BF4231DC9B4641D5A077 because a cryptographic exception was thrown.".

I couldn't find help anywhere on this. Can someone help me? If you need any more info, please let me know ^_^

Hi,

I have Exchange 2010/2013 coexistence.  DNS is now pointed to 2013.  Users with mailbox on 2010 are unable to open shared 2013 mailboxes from within Outlook (2010,2013).  I get 'The set of folders cannot be opened. Microsoft Exchange is unavailable. Either there are problems or the Exchange server is down for maintenance'

Any ideas how to start troubleshooting this?   - Thanks

I am bit puzzled and frustrated with this issue I have in my lab.  I have exported my test mailboxes from my 2010 environment (other settings are minor and easily reproduced), and uninstalled 2010.  Next I went and installed 2013 RTM from TechNet.

The first time I installed 2013 the install was successful, but when the ECP came up it was just a empty browser window - it would never display.  So I thought, maybe there was something left over from the previous 2010 server.  I blew away the OS (was 2008 R2) and built a clean 2012 server.  Installed all the Exchange 2013 prerequisites, extended the Schema and installed 2013 using all the defaults in the wizard.

This time the the ECP login came up, but here is where it gets puzzling and frustrating.  I put my Admin credentials in (this account has all proper group membership that I'm aware of) and the screen goes blank for a second and then the OWA login is displayed.  The ECP never comes up again, just goes straight to the OWA login.  If I enter my credentials in the OWA login, the screen just flashes and the password field clears but doesn't login.

I have tried uninstalling and cleaning up AD and reinstalling, but the same thing keeps happening.  I can't help but think it has something to do with permissions, but I'm not sure what that would be.

Exchange 2013 is up and running (still in test mode) and I can process mail with POP, IMAP, Outlook Anywhere, and activesync (with my cellphone and tablet). Event logs are pretty normal except for the ProbeResult log. I see errors in there for ActiveSync, IMAP and POP and some others. I ran the get-serverhealth cmdlet and then followed the instructions in the knowledgebase articles to reset stuff in IIS.  I am at a loss what else to do. Everything seems to be working fine but I see those errors. (Maybe I shouldn't have looked in that log :)

Any suggestions? Thanks,

Lou

Hello,

We are currently in the process of migrating from Exchange 2007 to Exchange 2013, coexistence has been implemented and 20% of our mailboxes have been migrated.

In the past week or so I have had two occurrences where mailbox migration batches containing a high number of mailboxes with small mailbox size appear to have caused one or all of the Exchange 2013 servers to fall over. These batches are all started through PowerShell from a CSV containing mailbox primary email address and target database so as to target multiple databases at in a single batch:

New-MigrationBatch -Local -Name $BatchName -CSVData ([System.IO.File]::ReadAllBytes($CSV)) -BadItemLimit 100 -NotificationEmails $AdminEmail -AutoStart

In addition the concurrent mailbox move limit has been left at the default of 20, in both the occurences of this issue the batches contained target databases on 3 Exchange 2013 servers meaning as I understand it we can have up to 60 synchronisations in progress at any one time during the batch.

The initial occurrence of this was a migration batch of 408 users, all of whom have small mailboxes, so the entire batch totalled only 43GB. Roughly 2 hours after the batch had begun its initial sync our service desk began to receive reports of mail delay, following investigation it appeared that one of the three target servers had begun to get its submission queue backed up with messages unable to connect to target databases on that server in order to deliver the messages. Worrying that the migration batch was the cause we stopped the job and within about 15minutes everything had returned to normal. The batch was then deleted and split into 3 separate batches of roughly 130 users each based on target server and re-run in order to identify if this was an issue with the target server which had the problem, however all 3 completed without issue separately.

The second occurrence of the issue has however been far more severe, in this case the batch was 120 mailboxes (again all small totalling 17GB for the entire batch) as we had drawn the conclusion that smaller batches are were better following the previous issue. In this case roughly an hour following the start of the synchronisation all 3 target servers began to be unresponsive in varying degrees:

• Users on all three servers were disconnected from Outlook
• One would not load ECP, however this degraded to none loading ECP as time went on
• SMTP continued to process initially, however this gradually begin to fail on each server
• Exchange Management Shell would not load on two servers, the remaining server would hang processing any EMS commands
• One of the three would not accept any new RDP connections and the majority of applications would not run
• All three however showed no noticeable problems from a resource point of view, CPU and memory and disk latency were all normal.

From the experience of the previous issue the first thing to be done was to stop the suspected migration batch, however up until the point where ECP and EMS stopped functioning none of the move requests went into a stopping or suspended state, and in turn this had no corrective impact on the issue.

On the surface in initially appeared that IIS was unhappy on all three target servers, iisreset however had no impact.

We took the view that restarting the worst impacted server was the only course of action for that device, this reboot took a lot longer than normal but did restore connection to mailboxes on that server, as such the other more severely impacted server was also rebooted.

During these reboots the Exchange Search service was stopped on the least impacted server, this lead to EMS commands completing and a manual suspension of the move requests was done. This server however continued to be unable to offer any client connectivity or access to ECP. As such this ended up being rebooted once the others had returned.

I have concerns around this now as I am unable to track down why this issue happened. I'm of the suspicion that the number of frequent and concurrent move requests doing their initial sync on such small mailboxes is causing one of the transport services to go into a tailspin and take other services out along the way, that said no services crashed and there was no unusually high resource usage from any of the Exchange services during these events. I have been toying with the idea that it is may be related to indexing the mailboxes as the drop into a 'Synced' state, and the number of  indexing jobs running based on how quickly the mailboxes are syncing. Hence the delay in symptoms occurring after the batch is started and that stopping the Search Service seemed to somewhat alleviate some of the symptoms. If this were the case however I would have thought the noderunner.exe would have been chewing up CPU permanently, however it only appeared to be intermittently spiking up the resource tables during the course of the problems.

Is this likely to simply be a concurrency issue in move requests be it by the amount syncing at once or the amount sat open in total? Or is there something I'm missing here?

Thanks for any assistance anyone can offer.

Hi,

We've recently migrated our on-premise Exchange to Office 365 but we keep management of users in our on-premise Active directory and dirsynced the attribute changes to Office 365. As per Microsoft recommendation, an Exchange server with CAS and Mailbox role should still be on-premise to manage the Exchange attributes. I have two Exchange 2013 servers, one CAS and one Mailbox, I wanted to decommission the Mailbox role server so that I can reuse the storage.

Is it possible to uninstall the Mailbox role and then add the role in the existing Exchange CAS server?

Or, I'll just uninstall Exchange on the 2 servers and setup a new Exchange server with both CAS and Mailbox role?

Hello!

We are on an hybrid deployment with some users on Exchange 2013 on-premises and others on Exchange Online (Office 365 E3 plan). We have enabled photo sync (PhotosEnabled attribute) in the organization relationship, both on-premises and online, but while Exchange Online users can see all profile pictures, Exchange on-premises can see only on-premises pictures.

It also looks like that online users can see only a low resolution version of on-premises users' pictures.

Do you have any idea how to troubleshoot or fix this, please?

Hi All,

Unable to find this issue anywhere else, please excuse if it's a duplicate of another issue.  

Basically, I have a new 2008 R2 server setup, added it to a domain, and want to install Exchange 2013 on this new server.  There are no Exchange servers anywhere on the domain.

The server is fully up to date, including .Net 4, and looking for updates results in zero new updates found.

When I run setup.exe for Exchange 2013, a command prompt appears for less than a second, then closes, then nothing else happens.

Did a fresh reboot before trying to install, and after waiting about 20 minutes to see if anything happened after the vanishing command prompt, rebooted again, tried again, same result.

There is nothing called Exchange anywhere on the server that I can find, no setup logs or anything, and I am totally stumped.

Thanks in advance for any advice.

Michael

Hello,

I cant find my solution that woks.

I have a fresh install of windows 2012R2 server.

I was installing exchange 2013 R1 on the server and i got the error:

Error:
The following error was generated when "$error.Clear();
          Install-ExchangeCertificate -WebSiteName "Exchange Back End" -services "IIS, POP, IMAP" -DomainController $RoleDomainController -InstallInTrustedRootCAIfSelfSigned $true
          if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
          {
            Install-AuthCertificate -DomainController $RoleDomainController
          }
        " was run: "Could not grant Network Service access to the certificate with thumbprint 9A9744EF8A9251AF974C6D8C25466D602D08B82C because a cryptographic exception was thrown.".

I think the error has to do with a certicate??

I dont know.

Greetings,

Albert Koenders

Hello, 

We recently moved our frontend server over to Exchange 2013. So now both internally and externally all mail traffic will flow through the new servre. After battling issue after issue I was able to get the new exchange environment working as it should. The only problem is that IMAP and POP3 logins do not work for 2013 mailboxes. It works fine for 2010 but not 2013. Here are the results from the testconnectivity website:

The IMAP service is being tested.
There was an error testing the IMAP service

Additional Details

Secured: CN=mail.domain.com, OU=Unified Communications, O=Companhy, POBox=United States, S...
S: * OK The Microsoft Exchange IMAP4 service is ready.
C: 1 CAPABILITY
S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN UIDPLUS CHILDREN IDLE NAMESPACE LITERAL+
1 OK CAPABILITY completed.
C: 2 LOGIN user <password>
S: 2 NO LOGIN failed.
C: 3 LIST "" *
S: 3 BAD Command received in Invalid state.

Microsoft.Exchange.Tools.ExRca.Tests.ImapPop.MailProtocolException: 3 BAD Command received in Invalid state.
at Microsoft.Exchange.Tools.ExRca.Tests.ImapPop.ImapProtocolTester.SendCommand(String command, String logString)
at Microsoft.Exchange.Tools.ExRca.Tests.ImapPop.BaseProtocolTest.PerformTestReally()
Elapsed Time: 1829 ms.

Here are my Get-ImapSettings from the mailbox server

The IMAP service is being tested.
	There was an error testing the IMAP service
	Additional Details   Secured: CN=mail.willowcreek.org, OU=Unified Communications, O=Willow Creek Community Church, POBox=United States, STREET=67 E Algonquin Road, L=South Barrington, S=IL, PostalCode=60010, C=US S: * OK The Microsoft Exchange IMAP4 service is ready. C: 1 CAPABILITY S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN UIDPLUS CHILDREN IDLE NAMESPACE LITERAL+ 1 OK CAPABILITY completed. C: 2 LOGIN ssimpson <password> S: 2 NO LOGIN failed. C: 3 LIST "" * S: 3 BAD Command received in Invalid state. Microsoft.Exchange.Tools.ExRca.Tests.ImapPop.MailProtocolException: 3 BAD Command received in Invalid state. at Microsoft.Exchange.Tools.ExRca.Tests.ImapPop.ImapProtocolTester.SendCommand(String command, String logString) at Microsoft.Exchange.Tools.ExRca.Tests.ImapPop.BaseProtocolTest.PerformTestReally() Elapsed Time: 1829 ms.

The IMAP service is being tested.
	There was an error testing the IMAP service
	Additional Details   Secured: CN=mail.willowcreek.org, OU=Unified Communications, O=Willow Creek Community Church, POBox=United States, STREET=67 E Algonquin Road, L=South Barrington, S=IL, PostalCode=60010, C=US S: * OK The Microsoft Exchange IMAP4 service is ready. C: 1 CAPABILITY S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN UIDPLUS CHILDREN IDLE NAMESPACE LITERAL+ 1 OK CAPABILITY completed. C: 2 LOGIN ssimpson <password> S: 2 NO LOGIN failed. C: 3 LIST "" * S: 3 BAD Command received in Invalid state. Microsoft.Exchange.Tools.ExRca.Tests.ImapPop.MailProtocolException: 3 BAD Command received in Invalid state. at Microsoft.Exchange.Tools.ExRca.Tests.ImapPop.ImapProtocolTester.SendCommand(String command, String logString) at Microsoft.Exchange.Tools.ExRca.Tests.ImapPop.BaseProtocolTest.PerformTestReally() Elapsed Time: 1829 ms.

I have been reading a bunch of links on setting up a Windows 2012 R2 server to house Exchange Server standard 2013.   My company is small  <100 mailboxes.  My thought was to have two disk volumes.  Let's call them C: and D:.  I was planning on installing the operating system on the C: drive and all of the Exchange system on the D: drive (configured as a Raid 10 drive).  Does this make sense or should I be doing something else.

TIA for ideas.

Bob

We have been having issue with our Exchange Server 2010's Transport Service failing due to a database corruption. I was hoping that maybe applying the Roll-up 7 for Exchange might fix this issue, however after applying the patch we are unable to start the MSExchangeMailboxAssistants "Error 1053: The service did not respond to the start or control request in a timely fashion."Then I notice that we were unable to connect to the Management Console or through PowerShell. 

Event 1000, Application Error

Faulting application name: MSExchangeMailboxAssistants.exe, version: 14.3.210.2, time stamp: 0x53e2bf34
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x5315a05a
Exception code: 0xe0434f4d
Fault offset: 0x000000000000940d
Faulting process id: 0x%9
Faulting application start time: 0x%10

Faulting application path: %11

Faulting module path: %12

Report Id: %13

PowerShell error:

We are in the process of migrating our company from Lotus Notes to Exchange 2013.  We installed Exchange with split permissions and I use my Account Operator to administer Exchange. We have calendars in Notes that are set up as Mail users for divisions to use as their "Shared Calendar" to put vacation time, hours, etc...  I wanted to create a Shared Mailbox in Exchange to be used at the "Shared Calendar". I tried to create the shared mailbox in the EAC, but I got access denied/insufficient rights.

I then added a new user to AD then went into the EAC and created the mailbox from the user I just created.  All is fine there.  The issue comes when I try to use the Powershell and run this command: 'Set-Mailbox -Identitydisproce.calendar@abc.org -Type Shared'.  I once again get the access denied/insufficient access error.  What roles/permissions need to be modified to be able to create a shared mailbox?

I'm using Exchange 2010 Edge Transport in our organization that I've recently upgraded to Exchange 2013. I like Edge Transport - along with our spam filter it is an effective and simple way to send and receive external e-mail - and I don't want to get rid of it.  But it seems like it needs a 2010 Hub Transport server to interact with. 

Right now the only other Exchange 2010 Server I have left running in the organization is the one Hub Transport server that interacts with the Edge Server.  Is there a way to undeploy this server too and connect the Edge Server directly to one of the 2013 Mailbox Servers?  Or will this need to stay as part of the organization as a pair with Edge Transport?

I noticed mail flow was running just fine while the Hub Transport server was turned off.  So it seems like it's possible.  But I want to be able to undeploy it safely without hurting mail flow.  Are there any links or white papers that show how best do do this?

----------- Ron E Biggs Chief Tech Officer Entertainment Studios

hi guys,

recently I finished Exchange 2013 installation and i want to do migration from exchange 2010 sp3 to exchange 2013.

first off all when i want to migrate one of the test mailbox from 2010 database to 2013 database this error has appeared:

 Cannot open mailbox /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=EXC2013/cn=Microsoft System Attendant.

after that i open the adsiedit and look at this path in my organization but i couldn't find my exchange 2013 server.

guys everything is working so good, i mean i can send an receive internal and external mail but mailbox migration doesn't work.

what can i do?

I have just installed my first Exchange 2013 deployment.  Small single server install, no Edge Server.  Things seem to have gone pretty well.  I haven't enabled external mail yet but just wanted to do a bit of testing.  I can send test messages and log in via OWA just fine.

However, when I try to connect an Outlook client I get the message: "Outlook cannot log on.  Verify you are connected to the network.  The connection to Microsoft Exchange is unavailable."  I have an internal DNS record for autodiscover and the internal urls in Exchange.

Before I go much further, I will also add that I have not yet installed the cert.  So I do get the certificate error when setting up Outlook.  I think I read that without a valid cert install, Outlook will not connect to Exchange 2013.  Is that true?  I will be finishing things up and installing the cert soon.  Once I do that, do you suspect the above error message will go away?

Also, after the error above, the dialog box appears that lists the server name.  Instead of what I would consider a valid server name, the name shows up as 505ef3b4-5d84-458e-b084-53d45c532bf0@domain.com.  Is that normal?

Thanks for any clarification

A post on experts-exchange.com says "A big warning about SSL offloading, and that is proxy to a different site *will not work* for Exchange ActiveSync or OWA."

http://www.experts-exchange.com/Networking/Protocols/SSL/Q_28486166.html

I'm unable to find any other information to corroborate that statement. Can someone point me to MS documentation that would confirm or deny that proxying to a different site will not work with SSL Offloading enabled?

Thanks

Chad

I migrated all functions and mailboxes to a new Exchange 2013 server with all updates.

I further installed a public SSL certificate. Access seemed fine to all mailboxes.

I clicked on the gear button for all options and some of them return with a page 500 error:

Here are the ones not working:

Set automatic replies:
https://my server/ecp/?rfr=owa&owaparam=modurl%3D0&p=organize/AutomaticReplies.slab

Manage apps:
https://myserver/ecp/?rfr=owa&owaparam=modurl%3D0&p=installed

Change password:
https://myserver/ecp/?rfr=owa&owaparam=modurl%3D0&p=PersonalSettings/Password.aspx

Options:
https://myserver/ecp/?rfr=owa&owaparam=modurl%3D0&p=account

They seem to go to the virtual directory ecp. I checked the virtual directory settings and the External is set correctly to the outside URL (https://myserver/ecp) and the internal is set to an internal URL (https://servername/ecp). Not sure if they both should have the external settings.

Not sure what is going on. I did notice when I setup the SSL cert I choose domains pointing to my external URL of m1.myserver.domain.  I checked the subject alternate domains of the certificate and the only one there is the m1.myserver.domain. The autodiscovery.myserver.com is not listed. Not sure if this is an impact. Also the certificate is setup to use   IMAP, POP, IIS, SMTP. Please advise.