Hi!

I'm trying to move mailboxes from Exchange 2010 without DAG to an Exchange 2013 DAG with 2 members, both are in the same forest/domain, and everytime I've got the following issues.

• Mailboxes bigger than 1GB - move mailbox stops and database failover occurs
• Small mailboxes are migrated without problems
• Copy queue length increases, can't suspend/resume
• Move mailbox status sometimes shows: StalledDueToHA
• The move request is already configured to increase the bad item limit (100) and to ignore rule limit errors
• When I try to restart the MRS service I've got an error saying that the service is stopped (however, it was running)
• Only solution: Restart the passive node   :(

I've got the following errors when the issue occurs:

msexchangerepl (4504) An attempt to open the file "J:\TESTDB\TestDB.edb" for read only access failed with system error 32 (0x00000020): "The process cannot access the file because it is being used by another process. ".  The open file operation will fail with error -1032 (0xfffffbf8).

Source: ESE
Event ID: 489
Level: Error

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

Replication for database TestBD is not flushed yet. Constraint: SecondCopy, number of copies: 2 (1 healthy passives, 1 active in site 'Default-First-Site-Name'), minimum replay time: 10/10/2013 21:27:42, maximum replay time: 10/10/2013 21:27:42, commit time: 10/10/2013 21:27:49. Failure reason: Database 93d327bb-a1ca-4dc6-85df-9b42e6c6dedf doesn't satisfy the constraint SecondCopy because the commit time 10/10/2013 21:27:49 isn't guaranteed by replication time 10/10/2013 21:27:42.

Source: MSExchange Mid-Tier Storage
Event ID: 10011
Level: Error

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

Process Microsoft.Exchange.InfoWorker.Common.Delayed`1[System.String]: Request from S-1-5-21-2373589661-269040492-120571974-1636 failed security checks.

Source: MSExchange Availability
Event ID: 4010
Level: Error

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

An asynchronous Microsoft Exchange Server Information Store task has not handled an Exception gracefully. Exception text is (Microsoft.Exchange.Server.Storage.Common.StoreException: ErrorCode: NotSupported, LID: 43296 - Invalid counter range allocation at this time.
   at Microsoft.Exchange.Server.Storage.StoreCommonServices.ChangeNumberAndIdCounters.AllocateCounterRange(Context context, Mailbox mailbox, UInt32 rangeSize, Boolean separateTransaction, StorePropTag propTagCounterRangeUpperLimit, PhysicalColumn nextUnusedCounterPhysicalColumn, GlobcntAllocationCache& allocationCache, Boolean& needNewGlobCountSet, UInt64& globCount)
   at Microsoft.Exchange.Server.Storage.StoreCommonServices.ChangeNumberAndIdCounters.AllocateCounterRange(Context context, Mailbox mailbox, UInt32 rangeSize, Boolean separateTransaction, StorePropTag propTagCounterRangeUpperLimit, PhysicalColumn nextUnusedCounterPhysicalColumn, GlobcntAllocationCache& allocationCache)
   at Microsoft.Exchange.Server.Storage.StoreCommonServices.ChangeNumberAndIdCounters.AllocateChangeNumberCounterRange(Context context, Mailbox mailbox, UInt32 rangeSize, Boolean separateTransaction)
   at Microsoft.Exchange.Server.Storage.StoreCommonServices.Mailbox.GetNextChangeNumber(Context context)
   at Microsoft.Exchange.Server.Storage.LogicalDataModel.Folder.Save(Context context)
   at Microsoft.Exchange.Server.Storage.StoreCommonServices.Mailbox.Save(Context context)
   at Microsoft.Exchange.Server.Storage.StoreCommonServices.MailboxTaskContext.EndTaskRequest(Boolean commitTransaction, Boolean pulseOnly)
   at Microsoft.Exchange.Server.Storage.StoreCommonServices.MailboxTaskQueue.RunMailboxTaskStep(MailboxTaskContext mailboxTaskContext, QueueItem queueItem, Func`1 shouldTaskContinue)
   at Microsoft.Exchange.Server.Storage.StoreCommonServices.TaskExecutionWrapper`1.<>c__DisplayClass6`1.<WrapExecute>b__5(TaskExecutionDiagnosticsProxy diagnosticContext, TTaskContext taskContext, Func`1 shouldCallbackContinue)).


Source: MSExchangeIS
Event ID: 1003
Level: Error


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

Global counter allocation in mailbox 60057047-33a8-4ee8-9421-3ed6578e71ca on database 93d327bb-a1ca-4dc6-85df-9b42e6c6dedf by source MailboxTask during operation 28 on call stack    at Microsoft.Exchange.Server.Storage.StoreCommonServices.ChangeNumberAndIdCounters.AllocateCounterRange(Context context, Mailbox mailbox, UInt32 rangeSize, Boolean separateTransaction, StorePropTag propTagCounterRangeUpperLimit, PhysicalColumn nextUnusedCounterPhysicalColumn, GlobcntAllocationCache& allocationCache, Boolean& needNewGlobCountSet, UInt64& globCount)
   at Microsoft.Exchange.Server.Storage.StoreCommonServices.ChangeNumberAndIdCounters.AllocateCounterRange(Context context, Mailbox mailbox, UInt32 rangeSize, Boolean separateTransaction, StorePropTag propTagCounterRangeUpperLimit, PhysicalColumn nextUnusedCounterPhysicalColumn, GlobcntAllocationCache& allocationCache)
   at Microsoft.Exchange.Server.Storage.StoreCommonServices.ChangeNumberAndIdCounters.AllocateChangeNumberCounterRange(Context context, Mailbox mailbox, UInt32 rangeSize, Boolean separateTransaction)
   at Microsoft.Exchange.Server.Storage.StoreCommonServices.Mailbox.GetNextChangeNumber(Context context)
   at Microsoft.Exchange.Server.Storage.LogicalDataModel.Folder.Save(Context context)
   at Microsoft.Exchange.Server.Storage.StoreCommonServices.Mailbox.Save(Context context)
   at Microsoft.Exchange.Server.Storage.StoreCommonServices.MailboxTaskContext.EndTaskRequest(Boolean commitTransaction, Boolean pulseOnly)
   at Microsoft.Exchange.Server.Storage.StoreCommonServices.MailboxTaskQueue.RunMailboxTaskStep(MailboxTaskContext mailboxTaskContext, QueueItem queueItem, Func`1 shouldTaskContinue)
   at Microsoft.Exchange.Server.Storage.StoreCommonServices.TaskExecutionWrapper`1.<>c__DisplayClass6`1.<WrapExecute>b__5(TaskExecutionDiagnosticsProxy diagnosticContext, TTaskContext taskContext, Func`1 shouldCallbackContinue)
   at Microsoft.Exchange.Server.Storage.StoreCommonServices.MailboxTaskQueue.WorkerTaskCallback(TaskExecutionDiagnosticsProxy diagnosticsContext, Func`1 shouldCallbackContinue)
   at Microsoft.Exchange.Server.Storage.StoreCommonServices.MailboxTaskQueue.WorkerTaskCallback(TaskExecutionDiagnosticsProxy diagnosticsContext, MailboxTaskQueue mailboxTaskQueue, Func`1 shouldCallbackContinue)
   at Microsoft.Exchange.Server.Storage.Common.Task`1.Invoke()
   at Microsoft.Exchange.Server.Storage.Common.SingleExecutionTask`1.Invoke()
   at Microsoft.Exchange.Server.Storage.Common.Task`1.<Worker>b__0()
   at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch[T](TryDelegate tryDelegate, GenericFilterDelegate filterDelegate, GenericCatchDelegate catchDelegate, T state)
   at Microsoft.Exchange.Server.Storage.Common.WatsonOnUnhandledException.Guard(IExecutionDiagnostics executionDiagnostics, TryDelegate body)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
 is temporary not allowed.


Source: MSExchangeIS
Event ID: 1050
Level: Error


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

MS Filtering Engine Update process was unsuccessful in contacting the Primary Update Path. Update Path: http://forefrontdl.microsoft.com/server/scanengineupdate

Source: FIPFS
Event ID: 6027
Level: Error

My environment:

3000 mailboxes
1 domain "contoso.com"
1 CAS + 1 MBX - Exchange 2010
2 CAS + 2 MBX - Exchange 2013 (dedicated replication network)

Any idea?

Thank you.

Regards,

Tiago Ferreira
MCITP EA, MCT, MCSA+M
http://www.msitpro.com.br
Linkedin

When installing the sp1 update for exchange 2013 we came across these errors:

    The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ECP (Exchange Back End)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity
 $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyCo
ntinue;
          if ($be -eq $null)
          {
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End"
 -DomainController $RoleDomainController;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication
:$false -WindowsAuthentication:$true;
          }
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -
ExternalUrl $null;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1"
 -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
        " was run: "The virtual directory 'ecp' already exists under 'exchangeserver.domain.local/Exchange Back End'.
Parameter name: VirtualDirectoryName".

     The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ECP (Exchange Back End)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity
 $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyCo
ntinue;
          if ($be -eq $null)
          {
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End"
 -DomainController $RoleDomainController;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication
:$false -WindowsAuthentication:$true;
          }
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -
ExternalUrl $null;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1"
 -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
        " was run: "The operation couldn't be performed because object 'exchangeserver
\ECP (Exchange Back End)' couldn't be found on 'dcserver.domain.local'.".

     The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ECP (Exchange Back End)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity
 $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyCo
ntinue;
          if ($be -eq $null)
          {
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End"
 -DomainController $RoleDomainController;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication
:$false -WindowsAuthentication:$true;
          }
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -
ExternalUrl $null;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1"
 -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
        " was run: "The operation couldn't be performed because object 'exchangeserver
\ECP (Exchange Back End)' couldn't be found on 'dcserver.domain.local'.".

I have not been able to find any information on the cause of these errors, any help would be appreciated.

Hello,

Running into a strange issue with a customer that was migrated from Exchange 2010 (running on SBS 2011) to Exchange 2013.  All user mailboxes have been moved and reported success, except for one one old Journal Mailbox on the Exchange 2010 Server.  The event log on the Exchange 2010 Server is generating the following event repeatedly however:

Source: MSExchangeIS

Event: 9660

Task: Logons

Description: User <NULL> (<NULL>) failed to sign in because their mailbox is in the process of being moved.

Any idea why this event would be thrown.  Is it because I still have that single Journal Mailbox on the old database, and have already moved all the other mailboxes including the arbitration mailboxes to the new server?

Any advice is greatly appreciated!  Thanks!

Hi ,

Is this following equence correct when migrating mailbox from On-Prem to O365 in Hybrid scenario?

1. create a new user account in O365 and do not asign a license.

2. create a migration bath and migrate the on-Prem mailbox to cloud

3. Once the migration is completed, the on-prem mailbox will be coverted as mail-enabled user object and the mailbox is migrated to O365.

4. now asign the license to O365 user account.

Hi Guys,

I need some help with the receive connector configuration in Exchange server 2013 and exchange 2010 environment.

I have migrated my Exchange environment from ex2010 to ex2013. i have 2 exchange 2010 server and 2 exchange 2013 server.

EXchange 2010

EX2010A : Client access (Was before the Migaration)

Ex2010B: Hub Transport and mailbox Server.

Exchange 2013

Ex2013A : Multirole server.

Ex2013B : Multirole Server. (Currently the Client facing server through Sophos Firewall.)

and i have configured the DAg as well between the Ex2013A and Ex2013B server , all is working fine and normal and now i also want to remove the legacy server (Ex2010 servers.)

but there is some question i am having about the receive connector. I didn't create any New Receive connector on the Exchange 2013 Server's. I have these by default created 5 Receive connector.

and i have these default receive connector on my Both Exchange 2013 Server.

in the old exchange 2010 Hub transport server i also had some other Hub transport receive connector.  for example.

SMTP-Proxy connecter. since my firewall is acting as the proxy for the emails so i wanted to created a smtp proxy connector which is allowed to receive the emails from the firewall but when i create the new hub transport server i get these warning.

I have these question:

1: Do i need to create the new receive connector before i remove the legacy exchange server ?

2: I also need to create some connector for the Post-fix server to send some alerts to exchange recipients. but i again receive the same error message's

3: what else i need to check before i can remove the legacy server.

thank you so much for the help in advance.

Hello everyone,

I'm doing an exchange 2007 > 2013 migration and following Exchange server deployment assistant.

I've installed exchange 2013 servers and configured 2013 URL last week. Only one test mailbox on DAG DB.

This monday users using their laptop complained that they couldn't access their emails over the weekend and had a pop up asking them credentials. I've reproduced this and seems that only setting Outlook anywhere settings to Negotiate or NTLM in outlook make Outlook working again. Still this setting is not persitent and failback to basic auth.

I've looked on Google for solutions but can't find one that would match mine.

From where should I start my troubleshooting?

Outlook 2013 RTM

Exchange 2013 CU 13

Exchange 2007 SP3 RU15

We need to implement exchange server 2013 in our network, currently our active directory domain is ABC.local and current third party email domain is ABCD.com , please let me know how to implement exchange in this scenario?

please help me how to install and configure exchange server on ABC.local to use ABCD.com as email ID.

Team,

I have 5 to 6  pop3 ids which is configured in outlook  as a profile on single system while downloading the mails in outlook client it keep on poping up for the password and also gives below error. But if i access the same through OWA. email id works fine. Requesting you to please help.

I cannot download the Exchange Server 2013 (Evaluation Version) from Microsoft's website. I get the following error message:

"This site can’t be reached 

The webpage at http://care.dlservice.microsoft.com/dl/download/8/1/1/811B7C54-DA45-48AF-A912-0AA2B6FDA02C/Exchange-x64.exe might be temporarily down or it may have moved permanently to a new web address.

ERR_INVALID_RESPONSE"

I have tried the following things:

1. Different Browser
2. Different Machine
3. Different Network

• URL = https://www.microsoft.com/en-us/evalcenter/evaluate-exchange-server-2013?i=1

Can anybody help?

Hi Folks,

Need some help with your valuable advice and suggestion

My environment

Active Directory- 2012 Server R2

Exchange Server- 2012 R2 OS/ 2013 exchange

Planning to migrate in Azure with office 365 and use sharepoint etc

We need to move our active directory and the exchange to cloud but need to keep all our Objects in On Premises as well as in Cloud.

I used the ad sync tool from Azure and now i cant assiged the mailbox in 365 because it has the Exchagne object id attached to it. I cant even use the cut over migration due to AD is already synced. we have only 10 mailboxes and AD is already synced. If i dont want to use HYBRID migration what are my options to use office 365 and AD (Azure) if i need to use/keep the same objects ?

UMESH DEUJA MCP,MCTS,MCSA,CCNA

Im in the middle of a rather large migration and a few users are see the below error when trying to log in to OWA:

X-OWA-Error: SDServerErr;Microsoft.Exchange.Data.Storage.StoragePermanentException
I cant find much on this error other than the enable inheritance permissions fix which all these accounts already have.
Has anyone else come across this before?

Hello,

I am trying to configure ADFS 3.0 on Windows Server 2012 R2 for Single Sign on with Exchange 2013. There seems to be very little information regarding configuring ADFS in an Exchange resources forest deployment, so I am hoping someone has come across this and has a solution :)

The environment:

There are four forests in the environment, consisting of:

• User forest 1 - user1.local
• User forest 2 - user2.local
• User forest 3 - user3.local
• Resource forest 1 - resource.local

The resource forest contains all of the Exchange infrastructure.

The user forests contain all the corporate users who have have linked mailboxes in the resource forest.

Each user only has one account, which will exist in one of the 3 users forest, and use their employee ID numbers (e.g. ID12345) to sign in 

There is a one-way outgoing trust between the resource.local forest and each of the user forests. There are no trust between the user forests.

The problem:

I would like to configure ADFS for OWA to allow the corporate users in the users domain to access their mailbox . Please keep in mind that these users only have accounts the their respective users domain, and their account\"place-holder"AD object in the resource forest is disabled.

The ADFS farm will be deployed in the resource forest

Environmental Restrictions:

• A two-way trust between the user forests and resource forest cannot be created
• We cannot migrate to Office365
• We cannot use Azure AD
• A new forest containing all users cannot be created

My research on this suggests that I will need to:

1. Deploy ADFS servers in each of the user forests
2. Add the user forest's ADFS farm as Claims Provider Trusts in the resources ADFS environment
3. Add the resource forest's ADFS farm as a Relying Party Trust in each of the user forest's ADFS farms
4. Configure OWA (and ECP) as a Relying Part Trusts in the resource forest.

I have done the above, but this does not appear to be working. When I browse the OWA URL, I get the ADFS log on page listing each of the user forest (I believe these are integrated Identity Providers (IDPs) for each of the Claims Provider Trusts I created with the user forests). Selecting one of these and trying to signing in with a user's UPN returns the "Something went wrong" OWA message with the "UpnClaimMissing" ADFS error in the URL. All Claim Provider Trusts (in the resource ADFS) and the Relying Party Trusts (in the user forest all have the default Acceptance\Issuance transform rules)

Is this the correct approach? Should I be adding the user domains as attribute stores in the ADFS server in the resource forest instead (not sure about this one, but though I'd throw it out there anyway)?

Thank you

Hey Exchange Experts,

Can we migrate mailboxes from Exchange 2007 (sp3) to Exchange 2013 without any downtime to mailbox access? does it support online move?

Regards

Boniface F

Hi,

We have recently deployed Exchange server 2013 with latest CU. Some of the users (7) are unable to login even after resetting the passwords.

We have tried different methods to correct this problem. Moved users to another OU, Reset passwords on AD , Deleted mailbox completely and created them from start. But still we are not able to log on using these userIDs.

Please help us.

Thanks,

SHAIK ABDUL KALEEM

Hello

i have the following scenario: 2 x MultiRole Exchange 2013 CU13 Server in One Site (Site A) und 2 x MultiRole Exchange Server in Site B.

In the near feature wie want to replace the Servers in Site B with Office 365 and want to Build up an Full Hybrid Szenario because the Servers in Site A should stay. 

Wenn i build up the hybrid szenario is there any kind of special configuration? I want to migrate all users from the Exchange Server in Site B to Office 365. 

Thx 4 your advice

skykitchen

Hello everyone!

I'm migrating from Exchange Srv 2007 to 2013 and changing NLB for HLB.

In Microsoft documentation I've found my HLB are supported and it's explained how to implement policies, farms,...

My doubt is because it says that I need to define Servers with port 80, not 443. And at the end of the document, it says how to do a policy for redirecting queries from http (port 80) to https (port 443).

Why is necessary doing that instead of configuring servers with port 443 and manage queries without thar redirection?My HLB are radware and the document is:

Thanks

hi,

i've got problem when update to cu8.

the file 'c:\program files\microsoft\exchange server\v15\transportroles\agents\hygiene\asdat.msi' is not a valid installation package for the product microsoft exchange 2007 standard anti-spam filter updates. try to find the installation package 'asdat.msi' in a folder from which you can install microsoft exchange 2007 standard anti-spam filter updates.

please help me..

Hello everyone,

I'm doing an exchange 2007 > 2013 migration and following Exchange server deployment assistant.

I've installed exchange 2013 servers and configured 2013 URL last week. Only one test mailbox on DAG DB.

This monday users using their laptop complained that they couldn't access their emails over the weekend and had a pop up asking them credentials. I've reproduced this and seems that only setting Outlook anywhere settings to Negotiate or NTLM in outlook make Outlook working again. Still this setting is not persitent and failback to basic auth.

I've looked on Google for solutions but can't find one that would match mine.

From where should I start my troubleshooting?

Outlook 2013 RTM

Exchange 2013 CU 13

Exchange 2007 SP3 RU15

Hello,

We are migrating from Exchange 2010 to Exchange 2013. All mailboxes are in Exchange 2010 databases.

When we change A hosts in DNS servers, all Outlooks, ActiveSync and OWA uses Exchange 2013 CAS to access 2010 mailboxes. We have problems with few Outlook clients, that are not able to connect to their mailboxes. We have tried to reconfigure entire Outlook profile, but we are not able to configure their Outlook account if A DNS are pointing to 2013 CAS.

These mailboxes are stored in two different databases and share database with another working mailboxes. Most of Outlook users are working fine.

What can I do to fix this problems?

Thank you