Hi All,

I followed the Exchange help files to ensure that all forest, domain and local server pre-requisites were installed, in the correct order, with time being allowed for replication of changes across the forest. The install went well with no errors reported. I am however having an issue with accessing the ECP (OWA behaves the same) in that the URL changes to https://serverFQDN/owa/auth/logon.aspx?url=https%3a%2f%2fserverFQDN%2fecp&reason=0 ( originally entered as https://serverFQDN/ecp )and all that is produced is a blank page.

Environment:

Windows Server 2008 R2 (all updates applied) freshly installed in a child domain using a Domain Admin account granted Enterprise and Schema admin rights and added to the Organisation Management group. No previous Exchange organisation existed as this is a freshly configured (pre-production) environment that I intend to migrate into. Both the MAilbox and CAS server roles are installed, the server has 16 GB of RAM

Following research on the web I have already tried:

• Uninstalling and re-installing Windows Identity Foundation
• Checking the mailbox for corruption using the EMS. The mailbox seemed ok but to be sure I created a new user, ran the enable-mailbox command, added the user to the Organisation Management group but still get exactly the same issue
• Running %windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -ir
• Using the EMS to perform a Test-EcpConnectivity, it failed even with the test user created with the supplied creation script

I can't find any consistent entries in the event logs. Any suggestions?

If I want to use the Same mailbox servers and upgrade them to exchange 2013, what is the recommended way? I have a 4 member exchange 2010 DAG.

I was thinking (where A,B,C,D are mailbox servers, A,B are in one site and C,D another active directory site):

 A  B  -------------- C D

Remove A and C from the 2010 DAG, Format and install Exchange 2013 on both, and create a 2013 dag :

A1 ----------- C1

B ------------- D

Then move across all mailboxes from B to A1. Upgrade B and D to exchange 2013 and put them in the DAG

A1 B1 ----------- C1 D1

Does this make sense ? I am trying to do this while having as much high availability as possible during the transition. I have no extra servers so I have to use the existing server hardware.

Anand_N

I have just setup a new server with win2k12 standard and exchange 2013 standard.

Outlook web mail works but Outlook 2010 (have latest updates) doesn't work.

On the same subnet, I open outlook and it says:'cannot open your default e-mail folders. microsoft exchange is not available. either there are network problems or the exchange server is down for maintenance.'

What do I need to do to get Outlook working? Are there additional steps that I need to configure on exchange 2013? I remember after install of exchange 2010, outlook would work fresh after exchange2010 install without additional configuration.

I have a co-existence of versions 2007 and Exchange Server 2013 CU2 and currently have the following problem: 

- Customers now where I performed the migration to the 2013 version, when starting Outlook is always asking for password. The settings for Outlook Anywhere are as follows: 

Can anyone help me identify the problem?

Since the installation of Exchange CU3 none of our XP users can access Public Folders.  I can't seem to find a fix nor have a heard ifMicrosoft plans to address this with a patch/fix. I understand that there isn't an option to rollback the update.  I have seen people suggest uninstalling exchange completely and then re-installing with Cu2.  Is this possible or does the exchange version have to match what the AD schema version is?  If so, can someone offer some references on how this can be done without losing configuration, data, etc?

Hi,

We have just moved our Exchange Server 2013 to a brand new server, this included changing to new IP addresses.

Almost everything is in order except for the fact that sending and receiving mails are not working, looking in the transport logs I can see that the exchange server says that it can't connect to the primary IP and that no alternate servers are responding and the last IP tried was "old server IP address"

We can furthermore see that our reverse DNS has not been changed yet "due to 24 hours TTL" to the new IP, my question here is can this be the root cause of the sending and receiving issues? I'm thinking if the server does a reverse lookup on our FQDN for the mail server it would get the wrong IP and thus result in a failing test from Microsoft Connectivity Analyzer.

Hello

I was running Exchange Server 2013 CU1 on a Windows Server 2012 server and decided to update it to CU3.

The first attempt led to a failure due to the fact that I had to first uninstall KB2874216: https://dirteam.com/blogs/davestork/archive/2013/09/25/failed-exchange-server-2013-cu2-install-due-to-security-update-2874216.aspx

This also left all the Exchange services disabled again so I had to re-enable them all in services.

After CU3 said it was successfully installed I restarted the server but then realised that external email seemed to stop coming in.

If I telneted to the server on port 25 it said

421 4.3.2 Service not available

If I restart the transport service then it works for a short while (about 15 minutes) and then goes back to saying service unavailable.

I have had to write a script and add a scheduled task to restart the transport service every 15 minutes to keep mailflow working.

I then decided to set up a new server with CU3 but after Exchange is installed on this second server it seems to have created 3 mailbox databases all of which are dismounted. If I try to create another database then I get this error:

An inconsistency in the Active Directory was detected: Database 'Mailbox Database RWS-MAIL1' is expected to be in a database availability group but the value for its MasterServerOrAvailabilityGroup property ('RWS-MAIL1') is not valid. This may be a defect in the product and this should be reported to Microsoft Product Support.

I have waited 24 hours and tried again but still get the same error and the database I tried to create appears there as well but all are dismounted.

Please can someone suggest anything I can try to resolve this.

I have one server where the transport service doesn't work properly and another where I can't create any mailboxes.

Before CU3 everything was working normally on the first single server.

Thanks

Robin

Robin Wilson

Fatal error  toomanylargeitemspermanentexception.

I have 20 GB of Public Folders to move. This is my script.

Exchange 2010 to Exchange 2013 on-premise Migration.

New-PublicFolderMigrationRequest -SourceDatabase (Get-PublicFolderDatabase -ServerEX2010) -CSVData (Get-Content C:\PF-Import-File\PFFolder2Mailbox.csv -Encoding Byte) -AcceptLargeDataLoss -BadItemLimit 40000

No matter what I try I get to 95 % and fail. I have broken it into several Mailbox Folders, changed bad -item limit, etc.

I cannot find the large files in public folders because there are too many of them. I assume I must remove the items larger than 35mg before I can successfully move the PF's.

Is there a way to increase this limit or a script I can run that will tell me the large items in Public folders?

Thanks

When I did a migration of a mailbox, I ran into the following error 'Exchange 2013 error code -2146233088 - Exceeded Maximum Number of Large Items'. After some searching I found following post describing fix and error. It is claimed that you can alter the size defined as 'large email' (35 mb for office365, don't know what it is for exchange 2013), through the set-transportconfig cmdlet.  anybody able to point me to how? What switch?

I try to install Exchange Server 2013 on a fresh install of Windows Server 2012.

Windows Server 2012, have already install on it:

• AD CD
• DNS
• IIS
• Exchange 2013 Prerequisites for Win.Server 2012 like described here http://technet.microsoft.com/en-us/library/bb691354(v=exchg.150).aspx

And the (winner) error message is:

Exchange Server component Mailbox role: Client Access service failed.
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 ABC7C6378BF63CED166794CFBF410C73B29EDD3A because a cryptographic exception was thrown.".

I search online for a solution and I found many others with same problem but any solution yet. :(
If anyone can help me I am able to dedicate him my next ode.

Thank you,
Adrian

HI

I am starting an exchange 2010 to 2013 migration and am trying to migrate the arbitration mailbox. Only it keeps failing.

This is what I see in EAC 

Data migrated:  
Migration rate:  
Error: MigrationPermanentException: Mailbox 'Microsoft Exchange' has a completed move request associated with it. Before you create a new move request for the mailbox, run the Remove-MoveRequest cmdlet to clear the completed move request. --> Mailbox 'Microsoft Exchange' has a completed move request associated with it. Before you create a new move request for the mailbox, run the Remove-MoveRequest cmdlet to clear the completed move request. 

In event viewer I see

An unexpected failure has occurred. The problem requires administrator intervention. Diagnostic information:

  at Microsoft.Exchange.Migration.MrsAccessorBase.HandleException[T](String commandString, Exception ex)    at Microsoft.Exchange.Migration.RunspaceAccessorBase.HandleException[T](String commandString, Exception ex, ICollection`1 ignoreExceptions)   at Microsoft.Exchange.Migration.RunspaceAccessorBase.RunCommand[T](PSCommand command, ICollection`1 ignoreExceptions)    at Microsoft.Exchange.Migration.MrsMoveRequestAccessor.CreateMoveSubscription(MoveMigrationJobItem jobItem, Boolean whatIf)    at Microsoft.Exchange.Migration.MoveSubscriptionHandlerBase.InternalCreate(MigrationJobItem jobItem, Boolean forceRecreate, Boolean isTest)    at Microsoft.Exchange.Migration.MigrationJobValidatingProcessor.<Process>b__1(MigrationJobItem jobItem)    at Microsoft.Exchange.Migration.JobProcessor.<>c__DisplayClass9.<>c__DisplayClasse.<FindAndRunJobItemOperation>b__8()    at Microsoft.Exchange.Migration.ItemStateTransitionHelper.RunBatchOperation(MigrationJob job, IEnumerable`1 jobItems, IMigrationDataProvider dataProvider, Nullable`1 failedStatus, Action batchOperation)|permanent error occurred for job items:0239039c-c331-47d5-98c2-854bfd381ec0:systemmailbox[e0dc1c29-89c3-4034-b678-e6c29d823ed9]@openjive.com:CompletionFailed|New-MoveRequest -WhatIf -Identity -CompletedRequestAgeLimit -BatchName -BadItemLimit -LargeItemLimit -TargetDatabase -ArchiveTargetDatabase |Mailbox 'Microsoft Exchange' has a completed move request associated with it. Before you create a new move request for the mailbox, run the Remove-MoveRequest cmdlet to clear the completed move request.|InnerException:ManagementObjectAlreadyExistsException:Mailbox 'Microsoft Exchange' has a completed move request associated with it. Before you create a new move request for the mailbox, run the Remove-MoveRequest cmdlet to clear the completed move request.|Microsoft.Exchange.Configuration.Tasks.ManagementObjectAlreadyExistsException: Mailbox 'Microsoft Exchange' has a completed move request associated with it. Before you create a new move request for the mailbox, run the Remove-MoveRequest cmdlet to clear the completed move request.    at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)    at Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest.EnsureUserNotAlreadyBeingMoved()    at Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest.InternalValidate()    at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()|:,0239039c-c331-47d5-98c2-854bfd381ec0,arb1,systemmailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}@openjive.com
%2

Not sure where to go from here,

HI, I've installed Exchange Server 2013 Standard on Server 2012 Datacenter.Now my problem is whenever i try to open Exchange Server Toolbox the below mentioned error always pop up

"mmc has detected an error in a snap-in and will unload it"

- report this error to microsoft and shut down mmc

- unload the snap-in and continue running

PLZZZZZ HELP ASAP................I'm in great trouble

Hi Guys

I'm currently undertaking an Exchange 2007 SP3 to Exchange 2013 migration, and all has been going swimmingly so far.  We've moved all mailboxes across and are at the final stages and just want to move the public folders across.

I've been following the instructions in: http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx this article, and we have gotten up to stage 5 (Start the Migration Request).  The process gets around 20% of the way through, and from what we can tell seems to migrate all content from PF folders, however it then stops.  I've posted an extract of the log below, which should show you the error we're currently getting (it tries then exhausts retries & stops).

Furthermore, in the event log, I get the following logged as the PF migration errors out:

I've attempted to find some solutions, and searching for the respective error codes has suggested a couple of ideas, such as not being a PF Admin (checked), resource issues on source/destination servers (checked, and restarted for good measure), I saw mention of a problem with NETBIOS resolution so added the source server into the host files (checked).

Any assistance would be greatly appreciated

Cheers

Dear Members,

  I've problem with the following situation:

- there is a Hyper-V 2012 host, containing two VM's:

-- one for antivirus and antispam solution

-- one for Exchange 2013 CU3 installed

- the internet connection goes through a firewall, the incoming SMTP traffic is forwarded to the antivirus host

- the antivirus host is sending (relaying) the checked traffic to the Exchange host

- the Exchange is deferring all messages, in the log: TransportRoles\Logs\FrontEnd\ProtocolLog\SmtpReceive can be found:

---------------------------------------------------------

"2013-12-14T20:18:08.623Z,EXCHANGE01\From_Relay,08D0C6E4B867234F,43,192.168.0.11:25,192.168.0.25:45113,-,,Local
2013-12-14T20:18:13.639Z,EXCHANGE01\From_Relay,08D0C6E4B867234E,46,192.168.0.11:25,192.168.0.25:45897,>,250 2.1.0 Sender OK,
2013-12-14T20:18:13.639Z,EXCHANGE01\From_Relay,08D0C6E4B867234E,47,192.168.0.11:25,192.168.0.25:45897,>,250 2.1.5 Recipient OK,
2013-12-14T20:18:13.639Z,EXCHANGE01\From_Relay,08D0C6E4B867234E,48,192.168.0.11:25,192.168.0.25:45897,>,250 2.0.0 OK,
2013-12-14T20:18:13.639Z,EXCHANGE01\From_Relay,08D0C6E4B867234E,49,192.168.0.11:25,192.168.0.25:45897,<,BDAT 10483 LAST,
2013-12-14T20:18:13.639Z,EXCHANGE01\From_Relay,08D0C6E4B867234E,50,192.168.0.11:25,192.168.0.25:45897,*,,Proxy destination(s) obtained from OnProxyInboundMessage event
2013-12-14T20:18:13.639Z,EXCHANGE01\From_Relay,08D0C6E4B867234E,51,192.168.0.11:25,192.168.0.25:45897,*,,Message or connection acked with status Fail and response 554 5.4.4 SMTPSEND.DNS.NonExistentDomain; nonexistent domain
2013-12-14T20:18:13.639Z,EXCHANGE01\From_Relay,08D0C6E4B867234E,52,192.168.0.11:25,192.168.0.25:45897,>,451 4.7.0 Temporary server error. Please try again later. PRX2 ,
2013-12-14T20:18:13.639Z,EXCHANGE01\From_Relay,08D0C6E4B867234E,53,192.168.0.11:25,192.168.0.25:45897,<,RSET,
2013-12-14T20:18:13.639Z,EXCHANGE01\From_Relay,08D0C6E4B867234E,54,192.168.0.11:25,192.168.0.25:45897,>,250 2.0.0 Resetting,
2013-12-14T20:18:13.639Z,EXCHANGE01\From_Relay,08D0C6E4B867234E,55,192.168.0.11:25,192.168.0.25:45897,<,QUIT,
2013-12-14T20:18:13.639Z,EXCHANGE01\From_Relay,08D0C6E4B867234E,56,192.168.0.11:25,192.168.0.25:45897,>,221 2.0.0 Service closing transmission channel,"

---------------------------------------------------------

I created a new Receive Connector like this:

Permission group: Anonymous

Remote network system: the IP of antivirus system

Network adapter bindings: All IPv4, Port 25

From [PS]:

Get-ReceiveConnector “Receive Connector Name” | Add-ADPermission -User “NT AUTHORITY\ANONYMOUS LOGON” -ExtendedRights “Ms-Exch-SMTP-Accept-Any-Recipient”

Any ideas?

Best Regards,

Zoltan

I'm in the middle of a migration from EX2010 SP3 to EX2013 CU3.  Transfers were going real slow, so I disabled global chimney and RSS scaling to see if that would help.  Running W2K8 R2.

Mailbox migrations now fail with this error message:

Relinquishing job: The request has been temporarily postponed: Resource reservation has expired. --> Resource reservation has expired.

Has anyone seen this before?  Thanks

"Warning:

Setup can't verify that the 'Host' (A) record for this computer exists within the DNS database on server 192.168.x.x.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.HostRecordMissing.aspx"

This is the warning message that I get during install of Exchange 2013. The DNS is working totally fine without any errors so I looked this problem.

To get rid of this warning message, all you have to do is make sure the IPv4 DNS is set to 127.0.0.1 on your network interface and not to the IP address of the IPv4 interface. The warning message doesn't look at the IPv6 interface so you can leave the IPv6 interface as is. I ignored the warning message and left the DNS set to the IP of the IPv4 interface and Exchange 2013 installed without any errors.

Microsoft should really fix this warning message. If I set the DNS IP to be the same as the IPv4 interface IP, I shouldn't get this warning message at all.

We are in the process of migrating from 2007 to 2013. 2013 is installed with CU2, new mailboxes created on 2013 work fine, mail is routing between both servers, etc. The only issue we seem to be having is we can't migrate mailboxes from 2007 to 2013. We are testing migration with test email accounts with just a couple emails in them. We have several databases on the 2007 server and we've created several new ones on 2013, regardless of what database we try and migrate from and what database we try and migrate to we have the same problem. The status just sits at "Syncing" and when I use Exchange PS with the Get-MoveRequestStatistics on the mailbox it shows StatusDetail-Finalization and PercentComplete-95%. The Mailbox size is only 6k.