Exhcange 2003 on a 2003 server to exchange 2013 on a 2012 server - problems...

Hi
I removed my 2003 exhcange server physically and installed a 2012 server with exchange 2013 on it.
How do I get it to work? Where do I manage the exh 2013 server, through web interface only?
It installed, and worked for a few days (after i first had to remove the 2003 exchange server).
Now i only get "done" in the web interface after loggin in, outlook does'nt find the server when trying to connect to accounts and i can't access it through powershell (exchange management shell) and the Exchange Toolbox does not work neither... The
services are running though, but that's about it.
It won't uninstall cause there is mailboxes etc on the mailbox database..
My servers are on a standalone network, cut of from the internett..
How do I get a clean slate to install echange from scratch?? We only have a few users, so they won't mind..
Any help would be appreciated.. As of now, the server does nothing...

Hi andjohnsen,
What error did you get when you access it through EMS (exchange management shell)?
In addition, I recommend you remove all the exchange 2003 residual information and check if any helps:
Remove (legacy) Exchange server using ADSIEdit
Best regards,
Niko Cheng
TechNet Community Support

Similar Messages

Fresh Exchange 2013 install on 2012 R2

Hi Everyone-
I'm a bit confused on the steps to install Exchange 2013 SP1 on 2012 R2 in a new environment (no 2013 installed). I've seen many mixed install guides recommending I install non-sp1, preparing the domain/schema first, install CAS/MBX roles. Once
complete run the Sp1 upgrade starting with the domain/scheme upgrade, and then run the EXE.
I've also read that the 2013 SP1 download (http://www.microsoft.com/en-us/download/details.aspx?id=41994) is a full version of Exchange and can be ran as a clean install - so essentially just preparing the domain/schema and run the install once. I
find this hard to believe as the ISO I've downloaded from VLSC is 3.5gb, yet the SP1 exe is 1.5gb.
Can anyone confirm which is the correct path to take?
Thanks

Hi,
Can't think of a good reason to install any other build of Exchange 2013 then SP1. The EX13 SP1 download is a full install and the only one that is supported on 2012 R2. The bits is packed in a different way so the download is smaller.
Martina Miskovic

Migration; Exchange 2003 SP2 to Exchange 2013 on new Domain and DC

I wasn't prepared for this task, and it was thrown at me to do... Eyes are bleeding from planning reading and planning, would LOVE any input from you guys. First time posting, here and have heard great things about these forums. The Company
I work for obtained a new client and a network that is in a cluster at the moment, so I'm having to dig through everything and restructure..
Scenario:
Old Domain/Server: (To be decommissioned)
Server 2003 Standard SP2 (Domain: cosco.com; NETBIOS name: coscoex)
Exchange 2003 SP2 (6.5.7638.1)
Server is a domain controller and exchange server.
Migrating to:
Server 2012 R2 Datacenter (New Domain ad.cosco.com; NETBIOS name: cosco)
VM #1: Server 2012 R2 Domain Controller at 2012 R2 Functionality
VM #2: Server 2012 R2 with Exchange 2013 Standard (Not Yet Installed) Joined to ad.cosco.com domain
VM #3: Server 2012 R2 with Exchange 2010 (Not Yet Installed) joined to ad.cosco.com domain
These are probably not ideal conditions, but I have to work with what I'm given.
Host server (2012 R2) is in work group mode. Hyper V Installed with a VM of Server 2012 R2 and as a DC at a functionality level of Server 2012 R2. I had intended starting at a lower functionality level and raising
it later, but.... ya I forgot to change it. If needed I can spool up a new DC with a lower functional level.
DNS, AD and group policy is all jacked up on the 2003 DC so that doesn't matter, All user accounts are going to be created under the new domain. The concern is migrating the mailboxes from Exchange 2003 on the old domain to
Exchange 2013 on the new domain. The client is going to provide CSV of the AD accounts that are still valid (a lot of accounts are no longer used or are from people that no longer with the organization.)
I had some ideas, but I'm not sure if they will work. This is something I have never done before (Senior Engineer Quit).
My thoughts:
- Establish a two way trust relationship between the two domains.
- Create two VM's, one with Exchange 2010 and one with Exchange 2013 (They have a 2010 licence that was not used).
- Create the users on the new domain
- Use the double hop method from Exchange 2003 > Exchange 2010 > Exchange 2013
- Link Exchange accounts to the correct user accounts on the new DC.
Can this be done cleanly? Am I going about this the correct way? Any feedback would be GREATLY appreciated.
Note: We are forced to use ad.cosco.com (Obviously not the actual domain name)

Hi,
Base on my experience, your idea is feasible.
However, before getting started, you should note that Exchange 2010 (with any service pack or update rollups) is not (yet) supported to install on Windows 2012 R2. More details refer to the following link:
http://technet.microsoft.com/library/ff728623(v=exchg.150).aspx
After all the preparations complete, you can refer to the following articles to migration exchange 2003 to 2010, then to 2013:
Exchange 2003 to 2010 Cross-Forest Migration Step by Step Guide
Exchange 2010/2007 to 2013 Migration and Co-existence Guide
Best regards,
Niko Cheng
TechNet Community Support

Import Calendar Entries to Exchange 2013 Causes Outlook Calendar View Problems

Today I was working on a way to import company holidays for 2014 into people's calendars. We're running Exchange 2013. Most users have Outlook 2010, but I'm on the bleeding edge with Outlook 2013.
The best method I found online for adding events to everyone's calendar involved creating a calendar in a PST file that contained all of the company holidays and then using the Exchange 2013 Management Shell to import the PST file into people's calendars.
I created the calendar in a PST using Outlook 2013. Each holiday is an all day appointment. I then used the management shell to import those appointments into my calendar. Outlook was running when I ran the import.
After the import completed, I went to look at my calendar and Outlook 2013 crashed. I restarted it, clicked on my calendar and it crashed again. After some digging, I found a suggestion that I start Outlook with /cleanviews. That seems
to have corrected the problem. All appointments appear as expected. Well, that was ugly. But I'm the only one on Outlook 2013 right now, so it's not a showstopper.
I then found a victim running Outlook 2010 for my next import experiment. Outlook 2010 didn't crash. But the calendar view did reset to a list view instead of whatever the user was running before. Strange... I ran the test again with
another person and was able to reproduce the result. All appointments are present, but Outlook feels the need to change views?
Does anyone have a suggestion for how to import these appointments without the calendar view being reset? I don't want to think about all the support calls we're going to get when people's calendar view gets changed to a list view.
Thanks
Patrick

Hi Patrick,
Is the use able to change the calendar view manually? Please check whether all calendar items are in list view both in OWA and Outlook? Please try to import the PST file from Outlook side to check whether the issue persists.
Thanks,
Winnie Liang
TechNet Community Support

Exchange 2013 cu3 setup fails with 'problem... validating the state of Active Directory... supplied credential... invalid'

Windows Server 2013; Exchange Server 2013 with Cumulative Update 1
Cannot install Cumulative Update 3 for Exchange Server 2013. It fails with
[xxx] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: Active Directory operation failed on . The supplied credential for 'XXX\Xxx' is invalid. See the Exchange setup log for more information on this error.
[xxx] [0] [ERROR] Active Directory operation failed on . The supplied credential for 'XXX\Xxx' is invalid.
[xxx] [0] [ERROR] The supplied credential is invalid.
(Crosses - XXX - replace original values.)
I have found that a few others have experienced the same problem but found no solution, nor could come up with anything myself. If it is any hint, Event 40961 was logged in the Event Viewer around the same time on almost all installation attempts to be purely
conincidental:
The Security System could not establish a secured connection with the server
ldap/xxx.xxx/[email protected] No authentication protocol was available.
Both Windows Server and Exchange Server otherwise work OK, and do not recall any issues with Cumlative Update 1 installation.

Hi vhr1,
Based on my knowledge, the Event ID 40961 is a warning message.
This behavior occurs when we restart the server that was promoted to a DC. The Windows Time service tries to authenticate before Directory Services has started.
Found some resources for your reference even if the Exchange Version is mismatched:
http://blogs.technet.com/b/jhoward/archive/2005/04/20/403946.aspx
http://support.microsoft.com/kb/823712/en-us
About the error message, "Setup encountered a problem while validating the state of Active Directory: Active Directory operation failed on . The supplied credential for 'XXX\Xxx' is invalid."
The error message InvalidCredentials means: the wrong password was supplied or the SASL credentials cannot be processed.
Found a similar thread for your reference, hope it is helpful:
http://social.technet.microsoft.com/Forums/en-US/98e26ad6-8e43-4ef5-8ff9-e9fee6e76bda/bind-operation-is-invalid?forum=exchangesvrdeploylegacy
Feel free to contact me if there is any problem.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Upgrading Exchange Server 2003 to 2010 to 2013 is worth???

Hello there, I am planning to upgrade about 30 users from exchange server 2003 to 2010 and finally to 2013. Is it worth to upgrade in this way because this steps are hard and very time consuming. What if, if I just copy all the user mailboxes directly to
exchange server 2013 and configure 2013 as a new exchange server and decommission old exchange server 2003?
How to copy user mailboxes to fresh exchange server 2013?
Please help me out.
Thankx

Yes, Export the PST from User Mailbox and Import it into Exchange 2013 Mailbox. But the problem is, you can't install Exchange 2013 in your current Exchange 2003 environment.
Only option is to install Exchange 2010 first and migrate all the users to Exchange 2010. Also Replicate the Public Folders too(If you are using)
Decommission Exchange 2003 entirely. Install Exchange 2013 SP1 and Migrate the User to Exchange 2013.
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.

Migrating to Exchange 2013 from Exchange 2003, EV7, Office 2003 and XP

What is the best approach for migrating our 300 user Exchange 2003 organisation to Exchange 2013.? We use Enterprise vault v7.5 and the clients are Office 2003 on an XP desktop.
We are also planning to upgrade to Windows7 and Office 2013 this year so I am trying to understand the sequence. Should we just aim to upgrade to Exchange 2010 with Outlook 2010 instead?
Many thanks.

Hi,
You can't install Exchange 2013 until and unless you decommission your Exchange 2003. Coexistence of Exchange 2013 with Exchange 2003 is not supported. You first need to upgrade to Exchange 2010 SP3 and then move users to Exchange 2010 and decommission your
Exchange 2003 servers. Once you are done with the decommissioning of your Exchange 2003 server you will be able to install your first Exchange 2013 machine in your messaging infrastructure.
Kindly mark this as answer if it fulfill your requirements. Thanks.
Regards, Riaz Javed Butt Consultant Microsoft Professional Services MCITP, MCITP (Exchange), MCSE: Messaging, MCITP Office 365

New User cannot access OWA after migrate from Exchange 2007 to Exchange 2013

Dear all,
I recently migrate the Exchange server from Exchange 2007 on Windows Server 2003 to Exchange 2013 on Windows 2012 R2. I can open the mailbox moved from Exchange 2007 without any problem. However when I created a new user in Exchange 2013, the user cannot
login the OWA, the browser will throw out following screen. Can anyone help me in this case. Thanks a lot!

Hi Winnie,
Thank for your reply. Below is the result, please note there has four exchange servers, HKAD and HKEX are the existing Exchange 2007 server. HKCAS1 and HKCAS2 are the new Exchange Server 2013 - both of xchange server 2013 are using owa.ksi.com.hk
as the external URL.
Identity                      : HKAD\owa (Default Web Site)
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : True
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
Url                           : {}
SetPhotoURL                   :
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   :
https://hkad.ksi.com.hk/owa
ExternalUrl                   :
Identity                      : HKAD\Exchange (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
Url                           :
SetPhotoURL                   :
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   :
ExternalUrl                   :
Identity                      : HKAD\Public (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
Url                           :
SetPhotoURL                   :
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   :
ExternalUrl                   :
Identity                      : HKAD\Exchweb (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
Url                           :
SetPhotoURL                   :
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   :
ExternalUrl                   :
Identity                      : HKAD\Exadmin (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
Url                           :
SetPhotoURL                   :
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   :
ExternalUrl                   :
Identity                      : HKEX\owa (Default Web Site)
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : True
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
Url                           : {}
SetPhotoURL                   :
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   :
https://hkex.ksi.com.hk/owa
ExternalUrl                   :
Identity                      : HKEX\Exchange (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
Url                           :
SetPhotoURL                   :
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   :
ExternalUrl                   :
Identity                      : HKEX\Exadmin (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
Url                           :
SetPhotoURL                   :
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   :
ExternalUrl                   :
Identity                      : HKEX\Public (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
Url                           :
SetPhotoURL                   :
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   :
ExternalUrl                   :
Identity                      : HKEX\Exchweb (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
Url                           :
SetPhotoURL                   :
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   :
ExternalUrl                   :
Identity                      : HKCAS2\owa (Default Web Site)
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : True
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
Url                           : {}
SetPhotoURL                   :
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   :
https://hkcas2.ksi.com.hk/owa
ExternalUrl                   :
https://owa.ksi.com.hk/owa
Identity                      : HKCAS1\owa (Default Web Site)
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : True
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
Url                           : {}
SetPhotoURL                   :
Exchange2003Url               :
FailbackUrl                   :
InternalUrl                   :
https://hkcas1.ksi.com.hk/owa
ExternalUrl                   :
https://owa.ksi.com.hk/owa

Iphone user can't connect to Exchange 2013

Hi there,
i have Exchange 2013 on Windows 2012, PKI and certificate installed.
I have 4 users that can (must) connect to the server through iPhone. It works for all, except for ONE (the boss :-X)
I deactivate the mailbox, recreate it without import old mails. It still don't work.
Any idea?
Thanks.

Yes it's the first time on Exchange 2013.
Yes they have different OS.
The server just been installed so it never worked.
BUT I SOLVED MY PROBLEM with this article:
http://technet.microsoft.com/en-us/library/dd439375(v=exchg.80).aspx It concerne Exchange 2003 and 2010 but it worked for my configuration: Windows 2012 and Exchange 2013 and no error HTTP 500.
Actually my user is member of Administrators group and the inheritance is deactivate. I activate it and it's work!
Thanks to me and thanks to you for your answers!

Moving from SBS 2011 to Exchange 2013

Make sure you get a clean DCDIAG before you start any migration.

Hi fellow spiceworkers,
I am planning on migrating from SBS 2011 to 2012 r2/Exchange 2013 and having a separate 2012 R2 DC.
It has been mentioned and my understanding that it is important to raise the forest functional level (currently 2003) before installing Exchange 2013. My intention is to raise it to 2008.
Current configuration:
2011 SBS with FSMO ROLE and 2003 functional level.
2012 R2 DC.
3 x 2012 R2 DC's at various remote sites connected via VPN.
Should I move the FSMO role to the 2012 R2 DC first, wait to replicate, THEN raise the functional level or should I raise the functional level, wait for replication then move the FSMO role?
Also, would anyone have any other considerations I should take when doing this?
Thanks for any advice in advance.
Ralph
This topic first appeared in the Spiceworks Community

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 table

I 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.

2012 r2 -Microsoft Exchange 2013 DNS timed out

I just installed Microsoft Exchange 2013 on my 2012 r2 server. I just installed all of the Roles &features, then I went to my fire walls and then I disabled them (temporarily). I configuring my IP addressing, DNS Ip address and a dns suffix. Now I
can't access my Exchange via browser so I did some trouble shooting and sure enough I can't ping my DNS address. I can ping my IP address though. If anyone has any suggestions that would help then let me know. Thank you for any responses!

Hi Dallen,
>>Now I can't access my Exchange via browser so I did some trouble shooting and sure enough I can't ping my DNS address.
It is not a hyper-v issue , it's more like a network problem .
First , I would suggest you to disable firewall in DNS server for troubleshotting .
If firewall is truned off then you still can not ping the DNS server , you may check if the exchange server can ping other IP address in your LAN to check network conectivity .
If they are in different subnet ,you may try to check the configuration of the router .
Any further information please feel free to let us know .
BestRegards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Exchange 2007 migrate to Exchange 2013

Dear MS Support,
I did migrate Exchange 2007 to Exchange 2013
The install complete, the exchange 2007 and 2013 can work together successful
DAG has created and work fine
Below is capture on exchange group after migrate
The exchange 2007 work fine with outlook anywhere, all the users can connected and send and receive mail in 5 year
The cerificate enroll with
Alternative Names: mail.biendongpoc.vn
The autodiscover on exchange 2007:
[PS] C:\Windows\system32>Get-ClientAccessServer | ft Identity,*uri* -AutoSize
Creating a new session for implicit remoting of "Get-ClientAccessServer" command...
Identity AutoDiscoverServiceInternalUri
BDPOC-SERVER1 https://mail.biendongpoc.vn/Autodiscover/Autodiscover.xml
I have created new certificate for Two exchange 2013
The certificate enroll with
Alternative Names: cas.biendongpoc.vn
I have create cname cas point to dag on DNS server
I have create A record autodiscover.biendongpoc.vn point to IP of dag.biendongpoc.vn
I did migrate mailbox from exchange 2007 to exchange 2013, the migrate successful , the outlook can
connected to Exchange 2013 and working perfectly
Our problem, the account exchange 2007 work not stable ,
sometime it connect to mail.abc.com, sometime it connect to cas.abc.com
If the outlook connect to cas.biendongpoc.vn, the request put password and i can't connect to exchange 2007, if outlook connect to mail.biendongpoc.vn i can connect
It is not stable for current exchange 2007
Anyone who can help me ?
Thanks

Hi
huynhtrongnhatminh,
I suggest you please go through this article.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Please check this for step by step guide.
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
Please point your autodiscover and commonname to Exchange2013 CAS
Please configure your URLs. There is no CAS array in Exchange2013 but the concept of single name space remains.
You need to have an A record (e.g. legacy.domain.com) in yout external DNS and add that name (legacy.domain.com) in your certificate for exchange 2007 users to have access externally.
Configure your commonname URLs in Exchange2013. Point commonname and autodiscover to exchange2013 in both external and internal DNS servers
Configure URLshttp://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/
No CASARRAY in 2013http://exchangeserverpro.com/exchange-2013-client-access-server-high-availability/
Please configure splitdns or pinpoint DNS in your internal DNS server if not configured
http://exchange.sembee.mobi/network/split-dns.asp
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.

Re-install Exchange 2013

I started a basic install of Exchange 2013 on Windows 2012 on a network with an existing Exchange 2007 (SBS 2008) org.
Things went well with prerequisites and AD Prep but the actual install ended up freezing up. I ran it on a VM with 2GB RAM and all I can guess is that services couldn't start etc with only that much RAM. I did the install through a remote desktop session
and when I returned after kicking off the install process that session was completely frozen up with a black screen. All I could do was reboot the server. I noticed messages that implied the completely new/blank Exchange install was unhappy with 2GB so I raised
it to 10GB, but still things just didn't work. Most significantly I couldn't even load the Management Console replacement web site. I just would get 404 not found.
Thinking the original install never completed properly I simply deleted the VM, re-created a new one with the same config (and 10GB RAM) with the same name, joined the domain, installed pre-requisites and re-started the install, but now I'm getting
"Exchange Server in an inconsistent state. Only disaster recovery mode is available. Please use Setup /m:RecoverServer"...
Of course now I get other errors because "Disaster Recovery setup needs access to the mailbox database drive (prior install location)" etc. and of course I have no backups or anything because there was nothing but deployed install media on the
prior server.
How do I re-install? Do I need to clean up AD references to the prior install?
Regards,
Steve Ware

Hello,
Yes. You should check if the uncompleted exchange server is in AD. If it is in AD, please remove it and then reinstall it.
And you can remove the VM, and create a new VM, and then install new exchange server whose name is different from the uncompleted exchange server.
Additional article for your reference.
Install Exchange 2013 in an Existing Exchange 2007 Organization
http://technet.microsoft.com/en-us/library/jj898582(v=exchg.150).aspx
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Exchange 2013 Disk space alert on SCOM

Hi All,
We have received SCOM alert for one of our Exchange 2013 server where the disk space is 100 GB and free space is 99 GB still I got an alert saying threshold 200 GB. Please help me to solve this.
Monitor name >

Hi,
For this issue, you can just disable this alert with a SCOM override or you can modify the threshold in Managed availability.
For details, you can refer to the following article.
Monitoring Exchange 2013 with SCOM 2012 (Part 3)
http://www.msexchange.org/articles-tutorials/exchange-server-2013/management-administration/monitoring-exchange-2013-scom-2012-part3.html
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software
or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
Hope this can help you.
Best regards,
Belinda Ma
TechNet Community Support

Exhcange 2003 on a 2003 server to exchange 2013 on a 2012 server - problems...

Similar Messages

Maybe you are looking for