Exchange 2013 sp1- msexchangemailboxreplication.exe.config now XML?
I just went to check the maximum moves setting before I start a migration and this file is now XML? It used to be a text file. Its now very hard to follow. What is the best practice way of viewing and modifying this file now?
The reference I used to use was this- but I think its outdated
http://www.msexchange.org/articles-tutorials/exchange-server-2013/mobility-client-access/exchange-2013-local-mailbox-moves-part1.html
I can see a line:
MaxActiveMovesPerTargetServer="100" MaxActiveMovesPerSourceServer="100" MaxActiveMovesPerTargetMDB="20" MaxActiveMovesPerSourceMDB="20" MaxMoveHistoryLength="5" RetryDelay="00:00:30"
I'm guessing I can modify that- but from those numbers maybe I don't need to :)
Hi Tony,
Really great information .
Though they have increased all the values from CU3 I think even if we change these values there shouldn't be any problem. I think your guess should be most likely correct.
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you
Similar Messages
-
I have a new Exchange 2013 server with plans to migrate from my current Exchange 2007 Server.
I installed Exchange 2013 SP1 and the only errors I saw in the event log seemed to be long standing known issues that did not indicate an actual problem (based on what I read online).
I updated to CU7 and now lots of errors have appeared (although the old ones seem to have been fixed so I have that going for me).
Currently the Exchange 2013 server is not in use and clients are still hitting the 2007 server.
Issue 1)
After each reboot I get a Kernel-EventTracing 2 error. I cannot find anything on this on the internet so I have no idea what it is.
Session "FastDocTracingSession" failed to start with the following error: 0xC0000035
I did read other accounts of this error with a different name in the quotes but still can’t tell what this is or where it is coming from.
Issue 2)
I am still getting 5 MSExchange Common 106 errors even after reregistering all of the perf counters per this page:
https://support.microsoft.com/kb/2870416?wa=wsignin1.0
One of the perf counters fails to register using the script from the link above.
66 C:\Program Files\Microsoft\Exchange Server\V15\Setup\Perf\InfoWorkerMultiMailboxSearchPerformanceCounters.xml
New-PerfCounters : The performance counter definition file is invalid.
At C:\Users\administrator.<my domain>\Downloads\script\ReloadPerfCounters.ps1:19 char:4
+ New-PerfCounters -DefinitionFileName $f
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo
: InvalidData: (:) [New-PerfCounters], TaskException
+ FullyQualifiedErrorId : [Server=VALIS,RequestId=71b6bcde-d73e-4c14-9a32-03f06e3b2607,TimeStamp=12/18/2014 10:09:
12 PM] [FailureCategory=Cmdlet-TaskException] 33EBD286,Microsoft.Exchange.Management.Tasks.NewPerfCounters
But that one seems unrelated to the ones that still throw errors.
Three of the remaining five errors are (the forum is removing my spacing between the error text so it looks like a wall of text - sorry):
Performance counter updating error. Counter name is Count Matched LowFidelity FingerPrint, but missed HighFidelity FingerPrint, category name is MSExchange Anti-Malware Datacenter Perfcounters. Optional code: 3. Exception: The
exception thrown is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
at System.Diagnostics.PerformanceCounter.InitializeImpl()
at System.Diagnostics.PerformanceCounter.set_RawValue(Int64 value)
at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)
Last worker process info : System.ArgumentException: Process with an Id of 7384 is not running.
at System.Diagnostics.Process.GetProcessById(Int32 processId)
at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
Performance counter updating error. Counter name is Number of items, item is matched with finger printing cache, category name is MSExchange Anti-Malware Datacenter Perfcounters. Optional code: 3. Exception: The exception thrown
is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
at System.Diagnostics.PerformanceCounter.InitializeImpl()
at System.Diagnostics.PerformanceCounter.set_RawValue(Int64 value)
at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)
Last worker process info : System.ArgumentException: Process with an Id of 7384 is not running.
at System.Diagnostics.Process.GetProcessById(Int32 processId)
at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
Performance counter updating error. Counter name is Number of items in Malware Fingerprint cache, category name is MSExchange Anti-Malware Datacenter Perfcounters. Optional code: 3. Exception: The exception thrown is : System.InvalidOperationException:
The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
at System.Diagnostics.PerformanceCounter.InitializeImpl()
at System.Diagnostics.PerformanceCounter.set_RawValue(Int64 value)
at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)
Last worker process info : System.ArgumentException: Process with an Id of 7384 is not running.
at System.Diagnostics.Process.GetProcessById(Int32 processId)
at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
Issue 3)
I appear to have some issues related to the healthmailboxes.
I get MSExchangeTransport 1025 errors for multiple healthmailboxes.
SMTP rejected a (P1) mail from 'HealthMailbox23b10b91745648819139ee691dc97eb6@<my domain>.local' with 'Client Proxy <my server>' connector and the user authenticated as 'HealthMailbox23b10b91745648819139ee691dc97eb6'. The Active Directory
lookup for the sender address returned validation errors. Microsoft.Exchange.Data.ProviderError
I reran setup /prepareAD to try and remedy this but I am still getting some.
Issue 4)
I am getting an MSExchange RBAC 74 error.
(Process w3wp.exe, PID 984) Connection leak detected for key <my domain>.local/Admins/Administrator in Microsoft.Exchange.Configuration.Authorization.WSManBudgetManager class. Leaked Value 1.
Issue 5)
I am getting MSExchange Assistants 9042 warnings on both databases.
Service MSExchangeMailboxAssistants. Probe Time Based Assistant for database Database02 (c83dbd91-7cc4-4412-912e-1b87ca6eb0ab) is exiting a work cycle. No mailboxes were successfully processed. 2 mailboxes were skipped due to errors. 0 mailboxes were
skipped due to failure to open a store session. 0 mailboxes were retried. There are 0 mailboxes in this database remaining to be processed.
Some research suggested this may be related to deleted mailboxes however I have never had any actual user mailboxes on this server.
If they are healthmailboxes or arbitration mailboxes that might make sense but I am unsure of what to do on this.
Issue 6)
At boot I am getting an MSExchange ActiveSync warning 1033
The setting SupportedIPMTypes in the Web.Config file was missing.
Using default value of System.Collections.Generic.List`1[System.String].
I don't know why but this forum is removing some of my spacing that would make parts of this easier to read.Hi Eric
Yes I have uninstalled and reinstalled Exchange 2013 CU7 for the 3<sup>rd</sup> time.
I realize you said one issue per forum thread but since I already started this thread with many issues I will at least post what I have discovered on them in case someone finds their way here from a web search.
I have an existing Exchange 2007 server in the environment so I am unable to create email address policies that are defined by “recipient container”.
If I try and do so I get “You can't specify the recipient container because legacy servers are detected.”
So I cannot create a normal email address policy and restrict it to an OU without resorting to some fancy filtering.
Instead what I have done is use PS to modify extensionAttribute1 (otherwise known as Custom Attribute 1 to exchange) for all of my users.
I then applied an address policy to them and gave it the highest priority.
Then I set a default email address policy for the entire organization.
After reinstalling Exchange all of my system mailboxes were created with the internal domain name.
So issue number 3 above has not come up.
For issue number one above I have created a new thread:
https://social.technet.microsoft.com/Forums/office/en-US/7eb12b89-ae9b-46b2-bd34-e50cd52a4c15/microsoftwindowskerneleventtracing-error-2-happens-twice-at-boot-ex2013cu7?forum=exchangesvrdeploy
For issue number four I have posted to this existing thread where there is so far no resolution:
https://social.technet.microsoft.com/Forums/exchange/en-US/2343730c-7303-4067-ae1a-b106cffc3583/exchange-error-id-74-connection-leak-detected-for-key?forum=exchangesvradmin
Issue number Five I have managed to recreate and get rid of in more than one way.
If I create a new database in ECP and set the database and log paths where I want, then this error will appear.
If I create the database in the default location and then use EMS to move it and set the log path, then the error will not appear.
The error will also appear (along with other errors) if I delete the health mailboxes and let them get recreated by restarting the server or the Health Manager service.
If I then go and set the retention period for deleted mailboxes to 0 days and wait a little while, these will all go away.
So my off hand guess is that these are caused by orphaned system mailboxes.
For issue number six I have posted to this existing thread where there is so far no resolution:
https://social.technet.microsoft.com/Forums/exchange/en-US/dff62411-fad8-4d0c-9bdb-037374644845/event-1033-msexchangeactivesync-warning?forum=exchangesvrmobility
So for the remainder of this thread we can try and tackle issue number two which is the perf counters.
The exact same 5 perf counter were coming up and this had been true each time I have uninstalled and reinstalled Exchange 2013CU7.
Actually to be more accurate a LOT of perf counter errors come up after the initial install, but reloading the perf counters using the script I posted above reduces it to the same five.
Using all of your suggestions so far has not removed these 5 remaining errors either. Since there is no discernible impact other than these errors at boot I am not seriously bothered by them but as will all event log errors, I would prefer
to make them go away if possible. -
Exchange 2013 SP1 CU8 installation stuck
Good Morning,
I'm just installing CU8 for Exchange 2013 on a DAG Member (only mailbox role installed), and setup is stuck at 49% of "Mailbox Role: Client Access service" for more than 2 hours now.
The ExchangeSetup logfile says:
[04/15/2015 06:44:20.0582] [2] Active Directory session settings for 'New-PerfCounters' are: View Entire Forest: 'True', Configuration Domain Controller: 'srv-dc02.oostvogels.com', Preferred Global Catalog: 'dc02.contoso.com', Preferred Domain Controllers: '{ dc02.contoso.com }'
[04/15/2015 06:44:20.0582] [2] User specified parameters: -DefinitionFileName:'ServiceProxyPoolCounters.xml'
[04/15/2015 06:44:20.0582] [2] Beginning processing new-PerfCounters
[04/15/2015 06:44:20.0582] [2] Processing file: C:\Program Files\Microsoft\Exchange Server\V15\Setup\Perf\ServiceProxyPoolCounters.xml
[04/15/2015 06:44:20.0582] [2] Performance counter name is Proxy Instance Count, type is NumberOfItems32.
[04/15/2015 06:44:20.0582] [2] Performance counter name is Current Outstanding Calls, type is NumberOfItems32.
[04/15/2015 06:44:20.0582] [2] Performance counter name is Total Number of Calls, type is NumberOfItems32.
[04/15/2015 06:44:20.0582] [2] Performance counter name is Calls/sec, type is RateOfCountsPerSecond32.
[04/15/2015 06:44:20.0582] [2] Performance counter name is Average Latency, type is AverageCount64.
[04/15/2015 06:44:20.0582] [2] Performance counter name is Base for Average Latency, type is AverageBase.
[04/15/2015 06:44:20.0582] [2] Performance counter category name is 'MSExchange ServiceProxyPool'.
[04/15/2015 06:44:20.0738] [2] Performance counter category name is 'MSExchange ServiceProxyPool'.
[04/15/2015 06:44:22.0255] [2] Ending processing new-PerfCounters
Does anyone have any suggestions or did you experience a similar issue?
I also can see some events like this:
Cmdlet failed. Cmdlet New-PerfCounters, parameters -DefinitionFileName "ADDriverCachePerformanceCounters.xml".
Thanks and best regards,
SebastianHi,
According to your post, I understand that install Exchange 2013 SP1 CU8 in a DAG with MBX role failed with error “Cmdlet failed. Cmdlet New-PerfCounters, parameters -DefinitionFileName ‘ADDriverCachePerformanceCounters.xml’”.
If I misunderstand your concern, please do not hesitate to let me know.
I want to double confirm whether you deploy clean install or implement upgrade an existing Exchange Server 2013 installation to Cumulative Update 8.
To rebuild all Performance counters including extensible and third-party counters, type the following commands at an Administrative command prompt. Press ENTER after each command:
1. Rebuilding the counters:
cd c:\windows\system32
lodctr /R
2. Resyncing the counters with Windows Management Instrumentation (WMI):
WINMGMT.EXE /RESYNCPERF
3. Stop and restart the Performance Logs and Alerts service.
4. Stop and restart the Windows Management Instrumentation service.
If the issue persists, please run to reload all the perf counters. For your reference:
http://blogs.technet.com/b/mikelag/archive/2010/09/10/how-to-unload-reload-performance-counters-on-exchange-2010.aspx
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support -
Exchange 2013 SP1 readiness check failing
Trying to install our first Exchange 2013 SP1 server on Windows 2012 R2 in our datacentre, the readiness check fails with:
Error:
The Active Directory schema isn't up-to-date, and this user account isn't a member of the 'Schema Admins' and/or 'Enterprise Admins' groups.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.SchemaUpdateRequired.aspx
There are many more errors relating to Enterprise admin rights etc.
Please note that:
My account is Domain admin, Schema admin and Enterprise admin member, it always has been.
I tried the built-in AD Administrator which of course is part of the groups as well, no difference.
Active Directory is at 2008 R2 for domain and forest functional levels.
I tried rejoining the new Exchange designated server to the domain
I've installed RSAT-ADDS, the Managed API 4.0 and all the other windows roles via powershell
There is a local domain controller that is a global catalog server on the new Exchange server subnet
I tried running the Exchange Setup on a different server on the same subnet as where the active 2010 Exchange server resides as well as the FSMO AD role holder resides, this works fine. I even did the AD prep from there no problem, that made no difference
on the datacentre server
AD replicates fine between the FSMO role holder and the Datacentre (no errors in dcdiag or repadmin /showrepl)
This error is in the event log:
The description for Event ID 4027 from source MSExchange ADAccess cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
ExSetupUI.exe
6724
Get Servers for domain.local
TopologyClientTcpEndpoint (localhost)
3
System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://localhost:890/Microsoft.Exchange.Directory.TopologyService. The connection attempt lasted for a time span of 00:00:02.0475315. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:890. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:890
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
--- End of inner exception stack trace ---
Server stack trace:
at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at System.ServiceModel.ICommunicationObject.Open()
at Microsoft.Exchange.Net.ServiceProxyPool`1.GetClient(Boolean useCache)
at Microsoft.Exchange.Net.ServiceProxyPool`1.TryCallServiceWithRetry(Action`1 action, String debugMessage, WCFConnectionStateTuple proxyToUse, Int32 numberOfRetries, Boolean doNotReturnProxyOnSuccess, Exception& exception)
the message resource is present but the message is not found in the string/message tableSo I decided to re-install the OS, worked perfectly now. Only difference from before would be:
SCCM hasn't pushed SCEP 2012 to the new build of the same server yet
The original server was installed in a different AD site and then it was physically mode and reassigned to an new AD site and subnet
I might have installed the pre-reqs in a slightly different order (RSAT-ADDS, all the IIS etc things via powershell
and then the UCM API 4.0. (saw few comments that the order of how you install them matters in other forums).
10 or so Microsoft Windows updates haven't installed on the new OS build yet.
Other than that, its identical. But if its not broken don't fix it, perhaps the above can help someone else though. -
Exchange 2013 SP1 on Windows Server 2008 R2 Enterprise - BSOD after DAG creation
Hi,
We are running Exchange 2007 SP3 RU13 on Windows 2003 R2 with SP2 in a 2003 native AD environment and recently decided to upgrade to Exchange 2013. We installed a pair of new DELL R420 servers running Windows 2008 R2 Enterprise then threw Exchange 2013 SP1
onto them. This all went fine and the servers are running stable.
We connected the second NIC of each server to the other via a separate switch, the second NIC has Client for MS Networks and File/Printer Sharing disabled plus a totally separate subnet with no DNS or GW address assigned. DAG setup was run and completed
OK. I created the DAG network in Exchange and enabled replication, I also left replication enabled across the production LAN. Finally, I went into the advanced network settings and made sure the replication network was below the production network in the binding
order.
After an hour or two the BSOD's started.. both servers would crash within a few minutes of each other and reboot with a Kernel Panic. I have attached the contents of the dump file below. This seems to happen every few hours and it always seems to be the
server hosting the passive DB copies crashes first, followed by the server hosting the active copies. Note that if we disable the replication NIC on both servers they do not crash.
I got the impression from somewhere that perhaps the servers had mixed up the binding order and were trying to use the replication network as primary, losing access to AD and rebooting (which I have read is the behaviour for Exchange now). It appears the
Exchange Health service has killed WININIT which causes the crash.
Thanks!!!
The crash dump text is below:
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa80192ebb30, Terminating object
Arg3: fffffa80192ebe10, Process image file name
Arg4: fffff80001dc37b0, Explanatory message (ascii)
Debugging Details:
PROCESS_OBJECT: fffffa80192ebb30
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: wininit
FAULTING_MODULE: 0000000000000000
PROCESS_NAME: MSExchangeHMWo
BUGCHECK_STR: 0xF4_MSExchangeHMWo
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80001e4cab2 to fffff80001abebc0
STACK_TEXT:
fffff880`0d7f39c8 fffff800`01e4cab2 : 00000000`000000f4 00000000`00000003 fffffa80`192ebb30 fffffa80`192ebe10 : nt!KeBugCheckEx
fffff880`0d7f39d0 fffff800`01df7abb : ffffffff`ffffffff fffffa80`1bcf3060 fffffa80`192ebb30 fffffa80`383ea060 : nt!PspCatchCriticalBreak+0x92
fffff880`0d7f3a10 fffff800`01d77674 : ffffffff`ffffffff 00000000`00000001 fffffa80`192ebb30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486
fffff880`0d7f3a60 fffff800`01abde53 : fffffa80`192ebb30 fffff880`ffffffff fffffa80`1bcf3060 00000000`00000000 : nt!NtTerminateProcess+0xf4
fffff880`0d7f3ae0 00000000`7772157a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`34eed638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7772157a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: wininit.exe
FAILURE_BUCKET_ID: X64_0xF4_MSExchangeHMWo_IMAGE_wininit.exe
BUCKET_ID: X64_0xF4_MSExchangeHMWo_IMAGE_wininit.exe
Followup: MachineOwnerHi Darrkon,
I suggest checking the status of the HealthMailbox on each of servers.
Also try to re-create the mailbox. You can safely delete and recreate health mailboxes.
Be aware that any local Managed Availability probes that are using the these mailboxes will fail until the Microsoft Exchange Health Manager is restarted. Once that service is restarted, it will recreate any mailboxes that it needs.
More details in the following similar thread, just for your reference:
BSOD after creating DAG
http://social.technet.microsoft.com/Forums/exchange/en-US/44d1cd98-cba1-4ed0-b0e7-8aa76ee3eabc/bsod-after-creating-dag
Thanks
Mavis
Mavis Huang
TechNet Community Support -
BSOD after upgrading to exchange 2013 SP1
Hi,
I Have 4 servers, x2 Mailbox and x2 CAS, all with 2008 r2 OS, Mailboxes with DAG. Problem started after I upgraded all servers from Exchange 2013 CU3 to Ex13 SP1. All Servers are in Vmware, same hardware.
All servers getting BSOD, error is same as some other posts in Internet about:
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8007ab4890, Terminating object
Arg3: fffffa8007ab4b70, Process image file name
Arg4: fffff800019de7b0, Explanatory message (ascii)
Debugging Details:
PROCESS_OBJECT: fffffa8007ab4890
IMAGE_NAME: wininit.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: wininit
FAULTING_MODULE: 0000000000000000
PROCESS_NAME: MSExchangeHMWo
BUGCHECK_STR: 0xF4_MSExchangeHMWo
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
LAST_CONTROL_TRANSFER: from fffff80001a67ab2 to fffff800016d9bc0
LOGS:
RecoveryActionLogs: ForceReboot-ServerName -ActiveDirectoryConnectivityServerReboot: Throttling rejected the operation
RecoveryActionLogs: ForceReboot-ServerName -ActiveDirectoryConnectivityConfigDCServerReboot: Throttling
rejected the operation
Recovery Action Failed. (ActionId=RestartService, ResourceName=ServerName.contoso.com, Requester=ActiveDirectoryConnectivityRestart,
InstanceId=140408.062707.65292.001, ActualStartTime=2014-04-08T15:27:07.6529270Z, ActualEndTime=2014-04-08T15:27:07.7777262Z, ErrorMessage=Service ServerName.contoso.com was not found on computer '.'.)
when Server restarts, logs show
Bugcheck action reported by server 'ServerName' initiated by responder 'ActiveDirectoryConnectivityServerReboot'
Recovery Action Started. (ActionId=ForceReboot, ResourceName=ServerName, Requester=ActiveDirectoryConnectivityServerReboot, InstanceId=140408.063307.93261.004, ExpectedToFinishAt=2014-04-08T15:38:07.9326175Z
Recovery Action Succeeded. (ActionId=ForceReboot, ResourceName=ServerName, Requester=ActiveDirectoryConnectivityServerReboot, InstanceId=140408.063307.93261.004, ActualStartTime=2014-04-08T15:33:07.9326175Z, ActualEndTime=2014-04-08T15:35:07.0828500Z)
I found that it could restart like many times in a day, but
Throttling does not let it, just one restart per day.
I already spent four days trying to find problem but no luck.
Try'ed to add override
Add-GlobalMonitoringOverride
-Identity Exchange\ActiveDirectoryConnectivityConfigDCServerReboot -ItemType Responder -PropertyName Enabled -PropertyValue 0 -Duration 60.00:00:00
but
after
(Get-WinEvent
-LogName Microsoft-Exchange-ActiveMonitoring/responderdefinition | % {[XML]$_.toXml()}).event.userData.eventXml | ?{$_.Name -like “ActiveDirectoryConnectivityConfigDCServerReboot"} | ft name,enabled
still shows propertyValue 1, and servers are restarting no matter what, I just dont want to disable HealtManager
Service.
Try'ed to recreate all performance counters, did'nt worked
Try'ed to create prefered domain controller, did'nt worked
Try'ed to play with healthSet 'AD', but there is almost no information about it in TechNet, so I just looked which services are unhealthy, sometimes it shows ActiveDirectoryConnectivityServer
or ActiveDirectoryConnectivityConfigDCServer as unhealthy, but after few minutes it goes to
healthy, problem that Exchange could already restart the server
mainly reason I think is:
The AD Health Set has detected a problem with Server.contoso.com at 2014.04.09 06:33:11. The Health Manager is reporting that ActiveDirectoryConnectivityProbe/Server.contoso.com
Failed with Error message: Search took 1518 ms. Threshold 800 ms. Attempts to auto-recover from this condition have failed and requires Administrator attention. Exception Details: System.Exception: Search took 1518 ms. Threshold 800 ms
I really need some new ideas...
EDIT: Exchange 2013 sp1 works perfectly in test lab, there are cloned machines from production, the only difference is DomainController, there is just one (server), no replications, and no subdomains (production domain have subdomain).
Running DCDiag shows no errorsHello Everyone,
We have 2 CAS and 4 Mailbox server that were installed from SP1 and seeing the same issue. This is a clean install still with no mailboxes migrated over as of yet. Opened a case with MS. also ran:
Add-GlobalMonitoringOverride
-Identity Exchange\ActiveDirectoryConnectivityConfigDCServerReboot -ItemType Responder -PropertyName Enabled -PropertyValue 0 -Duration 60.00:00:00
Waiting
for MS to get back and to see how this workaround does. Seems like the original issue was not resolved completely?
Will
post back when we get an update. Changing the DirectoryActiveMonitoringContext.xml and the above workaround do not seem suitable for us. We would like to see a complete resolution for this.
Good
luck! -
Installing Exchange 2013 SP1 - Errors MSExchange ADAccess & MSExchange Common
The topology first:
AD-server + Exchange-server
What I am trying to do is just install a full version of Exchange 2013 sp1.
But the problem is that install wizard freezes on the "initializing setup" page. Also eventviewer gives 2 different error messages, MSExchange ADAccess & MSExchange Common.
MSExchange ADAccess:
The description for Event ID 4027 from source MSExchange ADAccess cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local
computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
ExSetup.exe
2964
Get Servers for mydomain.com
TopologyClientTcpEndpoint (localhost)
3
System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://localhost:890/Microsoft.Exchange.Directory.TopologyService. The connection attempt lasted for a time span of 00:00:01.9984949. TCP error code 10061: No connection could be made because
the target machine actively refused it 127.0.0.1:890. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:890
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
--- End of inner exception stack trace ---
Server stack trace:
at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at System.ServiceModel.ICommunicationObject.Open()
at Microsoft.Exchange.Net.ServiceProxyPool`1.GetClient(Boolean useCache)
at Microsoft.Exchange.Net.ServiceProxyPool`1.TryCallServiceWithRetry(Action`1 action, String debugMessage, WCFConnectionStateTuple proxyToUse, Int32 numberOfRetries, Boolean doNotReturnProxyOnSuccess, Exception& exception)
the message resource is present but the message is not found in the string/message table
MSExchange Common:
The description for Event ID 106 from source MSExchange Common cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
2
Time in Resource per second
MSExchange Activity Context Resources
The exception thrown is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
at System.Diagnostics.PerformanceCounter.InitializeImpl()
at System.Diagnostics.PerformanceCounter.get_RawValue()
at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.get_RawValue()
Last worker process info : Last worker process info not available!
Processes running while Performance counter failed to update:
1044 VSSVC
1064 spoolsv
4032 notepad
1416 svchost
700 dwm
3100 SMSvcHost
3616 msdtc
2564 csrss
336 csrss
424 winlogon
244 smss
688 LogonUI
2556 Taskmgr
596 svchost
1124 inetinfo
1920 svchost
1652 SMSvcHost
1400 svchost
2916 taskhostex
492 lsass
2688 dwm
396 wininit
484 services
1104 svchost
388 csrss
384 svchost
1896 svchost
3052 svchost
744 svchost
1180 mmc
3404 conhost
1800 explorer
3668 Setup
552 svchost
712 svchost
2864 svchost
2964 ExSetup
2948 rdpclip
2592 winlogon
900 svchost
808 svchost
4 System
1164 mqsvc
0 Idle
Performance Counters Layout information: FileMappingNotFoundException for category MSExchange Activity Context Resources : Microsoft.Exchange.Diagnostics.FileMappingNotFoundException: Cound not open File mapping for name Global\netfxcustomperfcounters.1.0msexchange
activity context resources. Error Details: 2
at Microsoft.Exchange.Diagnostics.FileMapping..ctor(String name, Boolean writable)
at Microsoft.Exchange.Diagnostics.PerformanceCounterMemoryMappedFile.Initialize(String fileMappingName, Boolean writable)
at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetAllInstancesLayout(String categoryName)
the message resource is present but the message is not found in the string/message tableI solved this problem or at least managed to get a workaround for it.
I tried to install Exchange using rdp connection and the installation media was mapped on my local computer. After I copied it to server itself, everything started to work and now I am able to send emails. -
What happend New-MailboxExportRequest cmdlet in exchange 2013 SP1 is missing?
Cmdlet New-MailboxExportRequest is not recognize cmdlet in Exchange 2013 SP1
How can i do export mailbox to pst file in exchange 2013 SP1?You might be facing this issue because of not having the rights to execute the New-MailboxExportRequest CMDLET.
Follow the steps given below in order to export the mailboxes into PST file
1. Open the Exchange Console and run:
New-ManagementRoleAssignment -Name "Import Export PST" -SecurityGroup "Organization Management" -Role “Mailbox Import Export"
This will generate a new role group called Import Export PST to the Oranization Management group with the role Mailbox Import Export.
You should Close and Restart the Exchange Management System again so that the changes made will get reflected in the settings, otherwise you will still get the same erroriIf not
restarted. Now move to the next steps.
2. Assign “Mailbox Import Export” role to it.
3. Add Desired Users to Role Group
4. Create Network Share ( Exchange Trusted Subsystem group has read/write permission to NTFS Permissions)
5. Run PS New-MailboxExportRequest
6. Monitor New-MailboxExportRequest
Verify PST File has been created on the network Share and you are done.
If you get the same error again, then there will be some hardware or software issues due to which you are not able to export mailboxes into PST files. In that case, you can make
use of any third party tool like Stellar Phoenix EDB To PST converter, which will help you to export your exchange database files to PST files easily and quickly. You can try this software by downloading its demo directly from their site http://www.stellarinfo.com/email-repair/edb-pst-converter.php -
Here is the scenario:
Legacy Host: Windows 2008 R2
Guest VM: Windows 2008 R2 with Exchange 2013 SP1 DAG cluster.
After importing the VM (2008 R2 and Exchange 2013 DAG) into a 2012 R2 host (Cluster). (copy VM files to new 2012 R2host) Everything works fine.
Then upgrading "Installation Services" (for Windows 2012 R2 host) on the imported VM runs fine with no errors to the "Restart" prompt. VM than shows: "Configuring Windows updates 32% complete. Do not turn
of your computer." Hangs there for about 20 minutes until is says "shutting down". Hangs there for 20 minutes until power off. Restart to normal start; "Preparing to configure Windows. Do not turnoff your computer." proceeds slowly
to "Configuring Windows updates 32% complete. Do not turn of your computer." hangs there again indefinite. Sometime hangs at shutdown cycle and "Configuring Windows updates 32% complete. Do not turn of your computer." indefinitely.
I moved 20 other machines from a 2008 R2 host to new Windows 2012 R2 hosts all of these machines install the 2012 R2 Integration services just fine on the 2008 R2 VM. Just the 2008 R2 VMs clustered (DAG) and Exchange 2013 SP1 do not take the Integration
Services upgrade.
Any advise from Microsoft? I know I could decommission the DAG and Exchange machines and install Integration services on the native box before Exchange and DAG and that would sure work, but I'd rather avoid that amount of work for a simple integration layer
upgrade.
Thanks
Gerhard Waterkamp ACSLA Inc.Hi,
Could you try use the following method to fix this issue first?
1. Run the System Update Readiness Tool, then check if there is any error in the Checksur.log and checksur.persist.log.
1. Please run the System Update Readiness Tool on this affected server. Please download this tool from the following Microsoft article:
Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, and for Windows 7
http://support.microsoft.com/kb/947821/en-us
2. The System Update Readiness Tool creates the log files that captures any issues that the tool found or fixed. The log files are located at the following location:
%SYSTEMROOT%\Logs\CBS\
3. Please paste the checksur.log here for analysis.
If there is no error found, please try the following step.
==================================
2. Use Fix it tool to reset the Windows Update components.
1. Open the following link.
http://support.microsoft.com/kb/971058/en-nz
2. Select Windows 8.1, Windows 8 and Windows 7 in the product selection box.
3. Click “Run Now” to reset the Windows Update components.
Note: We can reset the Windows Updates manually by following the steps in the KB above.
3. Use the System File Checker tool to repair missing or corrupted system files
1. Open the command promote with Administrators.
2. At the command prompt, type the following command, and then press ENTER:
sfc /scannow
Any errors are found in the steps above, please let me know.
Hope this helpful.
Best Regards,
Jason Zeng
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. -
Exchange 2013 SP1 | Another HTTP 500.0.0 Error
Help!
We are in the middle of migrating from Exchange 2010 SP3 to Exchange 2013 SP1 and we are being plagued with HTTP 500 errors on every Exchange 2013 server now.
I have two Client Access servers installed (EXCHFE01 & EXCHFE02) and one backend mailbox server (EXCHMB03) with the Client Access role also installed (for troubleshooting purposes). Once I get everything working I'll install two backend 2013 servers
with the mailbox role only for production (load-balanced, clustered, etc). I still have two Exchange 2010 mailbox servers left since one has a single large mailbox left on it and the other hosts public folders. I'll get to migrating those later. All Exchange
2013 servers are running Windows Server 2012. All are on the same LAN and no firewalls are between them.
On all three 2013 servers (EXCHFE01, EXCHFE02, EXCHMB03) I'm getting the dreaded HTTP 500 error whether I try to get to OWA or ECP. This did work at one point where I could at least login to the mailbox server (EXCHMB03) and migrate all my mailboxes over
to it. Sometime this morning after the two Client Access servers were installed the mailbox server stopped working (HTTP 500 errors). This is very frustrating because I can't even login to a console to manage Exchange from any server at this point.
Both Client Access servers aren't really showing anything of value in the event logs or the IIS logs. The mailbox server (EXCHMB03) does show the following event 3002:
Protocol /Microsoft-Server-ActiveSync failed to process request from identity NT AUTHORITY\SYSTEM. Exception: Microsoft.Exchange.Security.Authentication.BackendRehydrationException: Rehydration failed. Reason: Source server 'NT AUTHORITY\SYSTEM' does not have token serialization permission.
at Microsoft.Exchange.Security.Authentication.BackendRehydrationModule.ProcessRequest(HttpContext httpContext)
at Microsoft.Exchange.Security.Authentication.BackendRehydrationModule.OnAuthenticateRequest(Object source, EventArgs args).
...and I get the following when I run the Exchange Management Shell tool on the same mailbox server (along with lots of other red HTML text):
More Information:
This error means that there was a problem while processing the request. The request was received by the Web server, but during processing a fatal error occurred, causing the 500 error.
The Client Access servers show the following errors:
Performance counter updating error. Counter name is Location cache update time, category name is MSExchange Active Manager Client. Optional code: 3. Exception: The exception thrown is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
at System.Diagnostics.PerformanceCounter.InitializeImpl()
at System.Diagnostics.PerformanceCounter.set_RawValue(Int64 value)
at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)
Last worker process info : System.ArgumentException: Process with an Id of 4040 is not running.
at System.Diagnostics.Process.GetProcessById(Int32 processId)
at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
Processes running while Performance counter failed to update:
888 svchost
264 smss
532 conhost
2576 Microsoft.Exchange.UM.CallRouter
1596 WMSvc
3932 dllhost
4020 svchost
2308 dwm
5060 taskhostex
844 svchost
1972 Microsoft.Exchange.Directory.TopologyService
1228 inetinfo
1316 vmtoolsd
3896 svchost
780 svchost
1580 rundll32
1668 mqsvc
816 dwm
3840 slui
3532 rdpclip
3980 WmiPrvSE
4200 SppExtComObj
4288 winlogon
2140 SMSvcHost
676 svchost
1564 svchost
1296 Microsoft.Exchange.Diagnostics.Service
1472 Microsoft.Exchange.ServiceHost
1204 svchost
1292 ServerManagerLauncher
488 winlogon
664 svchost
572 lsass
3236 dllhost
2972 WmiPrvSE
4484 w3wp
388 csrss
1600 rundll32
564 services
1260 msdtc
5032 sppsvc
1448 MSExchangeHMHost
824 LogonUI
4204 VSSVC
2524 userinit
2700 MSExchangeFrontendTransport
1708 SMSvcHost
728 svchost
460 wininit
904 svchost
992 svchost
4996 TSTheme
4240 slui
4904 taskhost
452 csrss
4340 csrss
4 System
1164 spoolsv
1988 slClient
2760 MSExchangeHMWorker
0 Idle
Performance Counters Layout information: FileMappingNotFoundException for category MSExchange Active Manager Client : Microsoft.Exchange.Diagnostics.FileMappingNotFoundException: Cound not open File mapping for name Global\netfxcustomperfcounters.1.0msexchange active manager client. Error Details: 2
at Microsoft.Exchange.Diagnostics.FileMapping.OpenFileMapping(String name, Boolean writable)
at Microsoft.Exchange.Diagnostics.PerformanceCounterMemoryMappedFile.Initialize(String fileMappingName, Boolean writable)
at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetAllInstancesLayout(String categoryName)
... and...
A transient failure has occurred. The problem may resolve itself. Diagnostic information:
Microsoft.Exchange.Data.DataSourceOperationException: The request failed. The remote server returned an error: (503) Server Unavailable. ---> Microsoft.Exchange.WebServices.Data.ServiceRequestException: The request failed. The remote server returned an error: (503) Server Unavailable. ---> System.Net.WebException: The remote server returned an error: (503) Server Unavailable.
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.Exchange.WebServices.Data.EwsHttpWebRequest.Microsoft.Exchange.WebServices.Data.IEwsHttpWebRequest.GetResponse()
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
--- End of inner exception stack trace ---
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ValidateAndEmitRequest(IEwsHttpWebRequest& request)
at Microsoft.Exchange.WebServices.Data.ExchangeService.InternalFindFolders(IEnumerable`1 parentFolderIds, SearchFilter searchFilter, FolderView view, ServiceErrorHandling errorHandlingMode)
at Microsoft.Exchange.WebServices.Data.ExchangeService.FindFolders(FolderId parentFolderId, SearchFilter searchFilter, FolderView view)
at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.InvokeServiceCall[T](Func`1 callback)
--- End of inner exception stack trace ---
at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.InvokeServiceCall[T](Func`1 callback)
at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.GetOrCreateFolderCore(String folderName, FolderId parentFolder, Func`1 creator)
at Microsoft.Exchange.Data.Storage.Management.AsyncOperationNotificationDataProvider.GetDefaultFolder()
at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.<>c__DisplayClass1b`1.<InternalFindPaged>b__13()
at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.InvokeServiceCall[T](Func`1 callback)
at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.<InternalFindPaged>d__21`1.MoveNext()
at Microsoft.Exchange.Data.Storage.Management.AsyncOperationNotificationDataProvider.<GetNotificationDetails>d__4.MoveNext()
at System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext()
at Microsoft.Exchange.Servicelets.CertificateNotificationServicelet.RemoveAllNotification()
at Microsoft.Exchange.Servicelets.CertificateNotificationServicelet.UpdateDataInMbx(List`1 certificates)
at Microsoft.Exchange.Servicelets.CertificateNotificationServicelet.Work()
I've tried all sorts of recommended fixes but none have worked so far:
ADSIEdit and remove msExchCanaryData0 data
Reinstall Exchange multiple times
Rebooted multiple times
This article: http://social.technet.microsoft.com/Forums/exchange/en-US/08d3777c-dc03-4411-8c87-7db37d2f406a/exchange-2013-owa-login-error-http-500?forum=exchangesvrclients
Rebooted DCs multiple times (no exchange servers are DCs)
I'm sure I've left out a few troubleshooting steps since I've been working at this for two days. Can anybody offer any advice? I'm at my wits end here...Hi,
Please check whether the mail.mydomain.com is pointed to your Exchange 2010 or Exchange 2013. Please run the following command to check your OWA virtual directores and ECP virtual directories:
Get-OwaVirtualDirectory -ShowMailboxVirtualDirectories | Select Identity,name,Internalurl,ExternalUrl,*auth*
Get-EcpVirtualDirectory -ShowMailboxVirtualDirectories | Select Identity,name,Internalurl,ExternalUrl,*auth*
In IIS manager > Default Web Site, please make sure Anonymous Authentication is Enabled in Authentication. Confirm that "Require SSL" is checked on the SSL Settings of the default web site.
Regards,
Winnie Liang
TechNet Community Support -
Exchange 2013 SP1 and SCOM 2012 R2
Hi there,
Hopefully someone can assist me with this issue, if it is one...
I am halfway through an Exchange migration, from Exchange 2010 SP3 on Server 2008 R2 to Exchange 2013 SP1 on Server 2012 R2.
76 users in total, roughly 80GB of Public Folders.
I have configured the 2013 environment with a cross datacenter DAG, also increased all of the timeouts of the cluster to take this into consideration, and everything appears to function as expected.
Added both 2013 machines to SCOM 2012 R2 for at least a week with no active users on it, and all monitoring reported ok, no issues.
Exchange 2010 is configured to use webmail.company.com for RPC over HTTP, which is what I have configured 2013 to use as well.
Implemented Microsoft ARR for client access to Exchange 2013, as opposed to ISA we've used for Exchange 2010.
A week ago, changed the DNS records for webmail.company.com from ISA to ARR, and all clients connected perfect.
Thought, ok, now we can start the migration. So far everything "seems" to be going perfect with the mailbox moves, however, SCOM is really noisy.
Attempted to reran the probe for EWS and got the error below:
Is there perhaps anyone that can assist me with these errors?
CheersFYI... IIS ARR is not supported for Exchange Server.
Check in event log if you are getting anything related to the issue.
About Outlook POP UP to end users. Check the event log on 2010/2013 for MRS events.
Are those mailboxes still moving or in move request?
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com Twitter:
LinkedIn:
Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose. -
Exchange 2013 SP1 Readiness Checks: No Exchange 2007 server detected
Hi there,
We are planning to upgrade our current Exchange 2007 server with the new Exchange 2013 SP1. I have been following Exchange Server Deployment Assistant to assist me with this task. Only schema update (setup /PrepareSchema) had been done so
far. I didn’t run setup /PrepareAD command manually because I wasn’t sure if I need to provide ‘Organisation Name’ with it or not?! I have installed all of the prerequisites as noted in the Microsoft documentation.
Now, I am a bit confuse with the ‘Readiness Checks’ page during graphical user installation of Exchange 2013 SP1 setup on Windows 2012 R2. Windows 2012 R2 server has all available updates applied.
===
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
===
I get the message why setup wants to run preparation for the Ex2013 with the ‘Setup /PrepareAD’. But, why ‘No Exchange 2010 server role have been detected in this topology’?! Ok, in my case setup doesn’t detect Exchange 2007 server. Is that ok to proceed
with the installation or something else needs to be done first?
Thanks in advance.I need Exchange guru advice here please. Since we already have Exchange 2007 SP3 RU 10 in our Windows 2008R2 Active Directory domain here I need to be 100% confident that pushing Exchange 2013 SP1 “Install” will not override our existing Ex2007 environment.
That would be a huge disaster!
Microsoft is saying that: “Microsoft Exchange Server 2013 Setup displayed this warning because
no Exchange Server 2010 or Exchange Server 2007 server roles exist in the organization.”
http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
Ok, I get the message about if I continue with Exchange Server 2013 installation, I won’t be able to add Exchange 2010 or Exchange 2007 servers to the organization at a future date..., and why would I need to do that anyway?!
Microsoft wording about “some solutions may require the use...” are very confusing since we will require to consider “Coexistence or migration requirements"
Perhaps, before running Exchange 2013 SP1 setup I need to run setup for preparing AD without “Organisation Name” parameter?! Something like this:
setup /PrepareAD /IAcceptExchangeServerLicenseTerms -
Error in moving exchange 2010 mailboxes to Exchange 2013 SP1 during migration
Dear All,
We were running Exchange 2010 SP3 with MBX/HT/CAS role in single server. Now we are migrating our exchange 2010 to Exchange 2013 SP1. After configuring co-existence and during the mailbox move from Exchange 2010 to Exchange 2013 SP1, we are facing below
error. Please help to troubleshot. As per our search on net, people were suggesting that it can be due to not able to resolve NetBIOS name. We checked same and we are able to ping both servers by NetBIOS and FQDN names.
[PS] C:\Windows\system32>New-MoveRequest -Identity
'[email protected]' -TargetDatabase "CI-DB01"
MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)
Diagnostic context:
Lid: 14744 dwParam: 0x0 Msg: EEInfo: Status: 1722
Lid: 9624 dwParam: 0x0 Msg: EEInfo: Detection location: 323
Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
Lid: 62184
Lid: 16280 dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
Lid: 8600 dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
Lid: 12696 dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
Lid: 10648 dwParam: 0x0 Msg: EEInfo: Generating component: 18
Lid: 14744 dwParam: 0x0 Msg: EEInfo: Status: 1237
Lid: 9624 dwParam: 0x0 Msg: EEInfo: Detection location: 313
Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
Lid: 62184
Lid: 16280 dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
Lid: 8600 dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
Lid: 12696 dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
Lid: 10648 dwParam: 0x0 Msg: EEInfo: Generating component: 18
Lid: 14744 dwParam: 0x0 Msg: EEInfo: Status: 10060
Lid: 9624 dwParam: 0x0 Msg: EEInfo: Detection location: 311
Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 3
Lid: 12952 dwParam: 0x0 Msg: EEInfo: prm[0]: Long val: 22964
Lid: 15000 dwParam: 0x0 Msg: EEInfo: prm[1]: Pointer val: 0x0
Lid: 15000 dwParam: 0x0 Msg: EEInfo: prm[2]: Pointer val: 0xFE01A8C000000000
Lid: 62184
Lid: 16280 dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
Lid: 8600 dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
Lid: 12696 dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
Lid: 10648 dwParam: 0x0 Msg: EEInfo: Generating component: 18
Lid: 14744 dwParam: 0x0 Msg: EEInfo: Status: 10060
Lid: 9624 dwParam: 0x0 Msg: EEInfo: Detection location: 318
Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
Lid: 53361 StoreEc: 0x977
Lid: 51859
Lid: 33649 StoreEc: 0x977
Lid: 43315
Lid: 58225 StoreEc: 0x977
Lid: 39912 StoreEc: 0x977
Lid: 54129 StoreEc: 0x977
Lid: 50519
Lid: 59735 StoreEc: 0x977
Lid: 59199
Lid: 27356 StoreEc: 0x977
Lid: 65279
Lid: 52465 StoreEc: 0x977
Lid: 60065
Lid: 33777 StoreEc: 0x977
Lid: 59805
Lid: 52487 StoreEc: 0x977
Lid: 19778
Lid: 27970 StoreEc: 0x977
Lid: 17730
Lid: 25922 StoreEc: 0x977
+ CategoryInfo : NotSpecified: (:) [New-MoveRequest], RemoteTransientException
+ FullyQualifiedErrorId : [Server=Exch01,RequestId=f6886977-92f1-4148-991b-aa76b449aff5,TimeStamp=8/21/2014 9:1
0:43 AM] [FailureCategory=Cmdlet-RemoteTransientException] 7FCC37,Microsoft.Exchange.Management.RecipientTasks.New
MoveRequest
+ PSComputerName : Exch01.domain.local
Please help as we are stuck here!!
Thanks in advance!!Can yo ping server by name not by FQDN? e.g. ping server1.
Make sure firewall/antivirus not blocking communication. Disable antivirus and try
Thanks,
MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. -
Outlook 2013 can't connect to Exchange 2013 SP1
Hello,
I've already asked that question on Exchange 2013, now I'd like to ask it again in regard to Exchange 2013 SP1.
The question i s very easy: suppose I have just installed Exchange 2013 SP1 (in a Win2012 R2 domain) with three mailboxes (user1, user2, user3). I can successfully run ecp and owa for all users...
...but when I'm starting Outlook 2013 and trying to set up a profile manually, for example, [email protected], Exchange 2013 Sp1 keeps saying "Outlook can't log on...The name cannot be resolved."
In Exchange 2013 this could be fixed by adding the server's ip address to its Hosts file, but I thought it was a bug and it would be corrected later or sooner... Now the same problem with Exchange 2013SP1...
Would anybody please tell me is there anything special I must do to connect to Exchange 2013SP1 via Outlook 2013 (not Outlook 2013SP1 - without MAPI over HTTP)??? If yes what articles can I read about it?
Thank you in advance,
MichaelHi,
When we automatically configure the account, Autodiscover service will help Outlook find the new type and we don't need to run the command to get the mailbox GUID until we manually configure the profile.
For more information, you can refer to the following article:
http://technet.microsoft.com/en-us/library/bb124251(v=exchg.150).aspx
"Through the Autodiscover service, Outlook finds a new connection point made up of the user’s mailbox GUID + @ + the domain portion of the user’s primary SMTP address."
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Angela Shi
TechNet Community Support -
Uninstalling Exchange 2013 SP1 failed on Step 8 Lanugage
Hello,
I am trying to uninstall Exchange 2013 SP1 but it is failing while uninstalling Language step # 8 the error is;
Error:
The following error was generated when "$error.Clear();
$regPath='HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall';
$PackageGUIDRegEx = "{DEDFFB[0-9a-fA-F]{2}-42EC-4E26-[0-9a-fA-F]{4}-430E86DF378C}";
$InstallPath = (Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\ExchangeServer\v15\setup').MsiInstallPath;
if(test-path ($regPath))
Write-ExchangeSetupLog -info ("Removing " + $RoleLanguagePackType + " Language Packs.");
Get-ChildItem ($regPath) | foreach{
if($_ -match "(?<ProductCode>$PackageGUIDRegEx)") {
$langPackPackageCode = $matches['ProductCode'];
if($langPackPackageCode -ne $null -and $langPackPackageCode.Length -ne
0) {
Write-ExchangeSetupLog -info ("Removing package
$langPackPackageCode");
$language = $langPackPackageCode.Substring(20,4);
$logFilePath = [IO.Path]::Combine($RoleLogFilePath,"Uninstall")
+ '.' + $language + '.' + "Client" + "." + $RoleLogDateTime + ".msilog";
uninstall-MsiPackage -ProductCode ($langPackPackageCode)
-LogFile ($logFilePath);
Get-Childitem -Path $InstallPath -include "*.Localized.js","*.Localized.min.js" -recurse | foreach
($_) {remove-item $_.fullname};
Write-ExchangeSetupLog -info "Remove Language Packs completed.";
" was run: "The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.".
I am also attaching the snapshots. Please guide me how to uninstall Exchange 2013. I had some issue with Exchange Server and it need to uninstall and re-install the Exchange Server." was run: "The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.".
Hi,
Based on this error, possible cause may the path of language package is too long. Please check the following things:
Where is your language package installed? Please check it.
Under 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{DEDFFB[0-9a-fA-F]{2}-42EC-4E26-[0-9a-fA-F]{4}-430E86DF378C}", please check the following entries. By default, it should be like this.
InstallSource (Z:\Applications\Server\Exchange\2013\64-Bit\RTM\en\)
ModifyPath (MsiExec.exe /X{DEDFFB64-42EC-4E26-0409-430E86DF378C})
UninstallString MsiExec.exe /X{DEDFFB64-42EC-4E26-0409-430E86DF378C}
Under 'HKLM:\SOFTWARE\Microsoft\ExchangeServer\v15\setup, check this entry MsiInstallPath. By default, the value should be “C:\Program Files\Microsoft\Exchange Server\V15\”
Best Regartds.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Lynn-Li
TechNet Community Support
Maybe you are looking for
-
Ipod touch does not show up in itunes since upgrading to lion
after installing 10.7.2 my ipod touch stopped showing up in my itunes window. please help..itunes is updated.
-
I am working on changing My ap1231's to Lwapp and ran into an issue. The upgrade of the 1231 works great, but when it goes to create the CSV file, it's empty. When I see the message that tells me to 'save' the CSV file, I clicked on 'config' and that
-
Hello everyone. For a custom project I've created a PhotoViewer, that simply shows images and fades them in and out along with a title and some text. I wanted to create a dashed border to put around these images and created my own implementation of a
-
Hi Experts, Can any one tell me in sap-bi i had created the role "zbcs_reports" under this role it is having the options for to execute the consolidations reports .this role consists of the folder's like consolidations under cons
-
Print SapScript. urgent
Dear All , How to change the allignment of characters , for printing form from portrait to lanscape format.(before that the form is in portrait format now i changed it accords to landscape format but characters are printing as per portrait format