We are having an issue with our DAG. We have two servers in a mailbox/CAS role setup (server A and server B). When I log into server A, I can access the ECP site with my admin credentials and I can access OWA with my normal cred. When I log into server B, I get a Error 500 message when attempting to log into ECP and I am unable to log into owa I get a Page cannot be displayed error after entering my credentials.
Any ideas?
We have two multirole servers (mailbox/cas). We are running in a hybrid environment with Exchange 2007 with only 6 people, for testing purposes, on the new Exchange 2013 infrastructure.
As a test we turned off the mailbox server that was actively hosting the mailbox stores. The second server was up and all services responded OK when checking the .htm statuses. We are using a single name space on CAS on both servers. Despite that, internally Outlook 2013 did not re-establish a connection to the second server. Despite closing outlook, flushing DNS and clearing the arp.
A connection wasn't re-established until the first server was turned back on AND the mailbox stores were once again actively hosted by this server.
Any thoughts on what I should too as preventing communication from happening with the second server?
Additional notes:
Windows firewall is off.
The second server no longer has the initial database that was created during setup
I was able to remote to the second server and access the webpages it hosts eg. owa. I was also able to verify the statuses of all servers as up using the health check url.
Our Exchange infrastructure working and now I am just writing up the documentation. What I can’t seem to find a straight forward answer for is this. We have 2 mailbox/CAS (DAG) and 2 CAS only with a load balancer as well. 1 MB/CAS and 1 CAS only reside in CityA and 1MB/CAS reside in CityB. The DR scenario is a flood in CityA (which has actually happened) causes immediate shutdown of the MB/CAS and CAS in that City before a clean shutdown can be performed and the MB/CAS retains its vote, the file witness is also in this City. The result would be that the mailbox stores are taken offline as quorum is lost. What do you have to do in order to mount the databases on the one working server?
Hello,
The disk that hosts the exchange database is almost full (90%!) I would like to upgrade to more storage....soon!
I have a 2 member DAG running Ex2013sp1. It's being backed up with DPM 2012 R2. The database is on its own drive (E:) and mirrored. The logs are on the D: drive and on a separate LUN. The servers are backing up fine every night and everything seems healthy.
My questions are: Can I put one of the servers in maintenance mode, blow away the mirror and create a larger raid volume with more storage, make it the E: drive and take it out of maintenance and let the DAG autoreseed? Or should I take a backup and restore to the new E: volume? Can I do something fancy with DPM 2012 R2? Will this even work? It almost sounds too easy and I'm skeptical.
Thanks in advance!
Hello,
I currently have 3 locations one being my DR site. I have setup a DAG between Site A and Site C.
Site A
Site B
Site C (DR)
Site B also contains Exchange 2013 Mailbox databases and I am wondering if I am able to add Site B's mailbox server to the existing DAG group and have Site B mailbox DB replicated over to Site C as well?
Any clarification on this is appreciated.
Cheers
Does one absolutely have to use Forefront Identity Manager to perform cross-forest email flow sharing a single public FQDN?
I have two forests internally. domain1.com and newdomain2.com as an example.
I want to store mailboxes in both forests but allow both forests to send email on behalf of myonlypublicdomain.com (mail.mypublicdomain.com) address.
I do not want to incur additional expenses for this GAL sharing stuff by having to deal with forefront since once the migration (Is slowly completed) I am getting rid of domain1.com forest....
I have 1000 mailboxes to move over (Which is why I don't want to do all of them at once!)
So everything is in domain1.com forest right now including the spam / encryption appliances that forward mail to an exchange server 2013 availability group composed of several servers in the domain1.com forest.
We setup new Exchange 2013 availability group in the newdomain2.com forest and I am already able to move accounts and mailboxes over to the new forest using powershell.
Now we just need a way to allow the domain users that are moved over to newdomain2.com to be able to send / forward and receive mail for the mypublicdomain.com domain from the domain1.com forest.
There are guides for send / receive connectors out there but I have not had much luck. Any info would be helpful.
Dear all;
I have two Exchange 2013 Std running in DAG mode, EX1 and EX2. I got the following problems since my DC have tomstone life time and replication issue but this replication issue is fixed.
Problem 1 : new created user mailbox cannot move from exchange database MX01 to MX02.
I created two new mailbox on Exchange after the DC problem fixed. However, I found the problem during database migration test from database MX01 to MX02 where the MX01 is on EX1 server and MX02 is on EX2 server. The error message is this...
Error: MigrationPermanentException: Cannot find a recipient that has mailbox GUID '86297174-0ccc-439d-9ea3-4a02ec34bf8f'. --> Cannot find a recipient that has mailbox GUID '86297174-0ccc-439d-9ea3-4a02ec34bf8f'.
However; when I migrate the old mailbox which was created before the DC problem, the migration for old mailbox is success.
I tried to compare the "ShowInAddressBook" attribute of the problem user account in ADSIEdit with the healthy user mailbox. I do not see any entries missing or incorrect.
Also; I will get this error "Name Could Not be Matched to a Name in the Address List" when open Outlook to create a new Outlook profile, I need keep trying to make it work.
For this problem, how can I fix?
Problem 2: Outlook access issue for the same problem user mailbox.
I logon to a RDP server with using the mailbox user account, and open the Outlook 2013, when I open the outlook for this user who has the problem 1 mentioned above. I got this message
"Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. Microsoft Exchange is not available. Either there are network problems or Exchange server is down for maintenance." but when I keep trying keep trying; it will able to open Outlook.
I tried the OWA for this problem mailbox, no issue to open in OWA.
These two problems only impact those new created mailbox after our disaster.
Can someone help?
thx!
KW - CNE,MCSE,VCP5
currently testing Exchange 2013 DR.
we have a stretched DAG over 2 AD sites.
when all nodes are up and running, all is perfect.
as soon as the Primary Site goes down (including DCs and MBX Servers), i can no longer connect to the EMS on the DR site. the DR site has one Multi role 2013 Server and one DC, so all should be fine for testing a datacenter switchover.
Bringing the active site back online instantly allows EMS to connect to the Exchange Server on the DR site.
any help is greatly appreciated
12:17:29] [FailureCategory=Cafe-HttpProxyException] Server Locator Service call timed out. For more information, see
the about_Remote_Troubleshooting Help Topic.
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
gTransportException
+ FullyQualifiedErrorId : -2144108477,PSSessionOpenFailed
Hello
Can I delete all files in c:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Temp
I wonder why does it happen and is this normal?
And can I safely delete content of this folder?
Has anybody already tried to delete it ?
On Premise.
In the EAC when I go to user mailbox properties and click on mailbox delegation I get this error:
You request couldn't be completed.Please try again in a few minutes.
Tried few tweaks found on the internet but no luck,
thank you
Hello,
I have just setup a muti-site DAG for Exchange 2013. My setup if pretty basic but I have run into an issue with one of the nodes.
I have separated out MAPI and Replication traffic between the two nodes. One of my nodes is reporting that the adapter I have assigned for replication traffic is "DOWN" I can ping the interface locally so I know its not a hardware issue and I am using a virtual adapter (vmxnet3) from VMware.
My DR site where I have the other Exchange node is configured identically, minus the IP Address assignment. In the primary site I also noticed that the "Cluster network 2" interface that reporting down, is also showing Cluster and Client for "Cluster Use" column.
When I attempt to change it to "Cluster Only" I get a dialog box that reads, "The network is no longer available for client to connect to clustered roles. The IP Address resources that are still using the network should be removed"
I am at a loss right now as to why this network interface is reporting down in the Cluster Manager.
I want to send mail between two forests. I've created mail-enabled contacts in both domains for users that are sitting on both sides of the forest. I want to send mail to some test accounts whose mailboxes live in forest1 to forest2 and vice versa.
I tried this:
http://www.techrid.com/exchange-server-2010/mailflow/configure-a-cross-forest-send-connector-using-ems/
It did not work. I tried modifying connectors many times, authentication methods etc. etc. and I cannot get mail to flow between the domains. I keep getting the following error sending from my main forest to the new forest:
Remote
Server returned '550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found'<o:p></o:p>
From the new forest to the old forest the mail just sits in the queue and never leaves the mail server.
I can't find anything relating to Exchange 2013 to Exchange 2013 send / receive connector configuration for two domains sharing the same FQDN for email. IE mydomainname.com has exchange servers in both forests and both forests have users that receive / send mail for mydomainname.com
Any info would be helpful.
Hi,
One of my client has two Exchange 2013 CU 9 nodes and a DAG configured. But they have used only single network adapter for each server for server communication and Mailbox replication. They are planing to go for a DR site and we have installed Additional Domain Controller & One Exchange 2013 CU 9 server in DR Site. This is a different IP Subnet and this is separated from PR in Active Directory Sites and services. ALL PR and DR servers are virtual servers (Hyper-V). In DR Exchange server also we have used only one network adapter.
But when we trying to add new Exchange 2013 (DR ) Node to the DAG, it gave below error.
A server-side database availability group administrative operation failed. Error The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API failed: "AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired". [Server: xxxx-02.xx.lk]
Then after a lot of research i have disabled below parameters from all network adapters. (Hosts & guests)
IPv4 Checsum Offload Disabled
Large Send Offload Ver. 2 (ipV4) Disabled
Large Send Offload Ver. 2 (ipV6) Disabled
TCP Checksum Offload (ipv4) Disabled
TCP Checksum Offload (ipv6) Disabled
UDP Checksum Offload (ipv4) Disabled
UDP Checksum Offload (ipv6) Disabled
I have configured a witness server and a share in primary site and secondary witness server in DR site and also a additional IP for DR.
Now when we trying to add new Exchange 2013 node it will successfully added to the DAG but show as "not operational". (DAG settings) and also it will dismount the only database in the server.
Please help me to sort this out.
Thanks.
Hi All,
I'm looking at setting up a 2 node Win2k8 R2 failover cluster with a quorum as a disk witness.
Upon setting up this cluster, I would like to install Exchange 2013 to co-exist with my current
Exchange 2007 server.
Is there anyone there that could point me in the right direction of the steps I should take to accomplish this task?
I have googled and all I can find in terms of an informative video is on how this can be done for MS SQL databases.
Kind Regards
GMSS
I receive and email from the internet. All the headers are intact when I check.
I attach that email as an attachment to another email and send it to my Hotmail account. When I see the headers of that attachment I notice some headers have been removed. Any ideas why or how to fix?
Dear All,
We are running exchange 2013 and 2010 in co-existence mode both are in different subnets ,recently the network team has implemented data center firewall but both the exchange 2010 and 2013 have all ports open for communication ,i have found that after the implementation of data center firewall the status of all the database of exchange 2010 shows as unknown but the the exchange 0213 database shows the database base as mounted but only for exchange 2010 databases it shows as unknown could it be due to data center firewall.
TechGUy,System Administrator.
I am configuring Auto Reseed with the following parameters. Each volume contains two databases.
AutoDagDatabaseCopiesPerDatabase: 1
AutoDagDatabaseCopiesPerVolume: 2
AutoDagDatabasesRootFolderPath: c:\exchDBs
AutoDagVolumesRootFolderPath: c:\exchVols
AutoDagAutoReseedEnabled: True
AutoDagDiskReclaimerEnabled: True
Navigating to c:\exchVols\ExVol1 shows:
DAG1-01a.db (directory)
DAG1-01a.log (directory)
DAG1-01b.db (directory)
DAG1-01b.log (directory)
Navigating to either c:\exchDbs\DAG1-01a OR c:\exchDbs\DAG1-01b shows:
DAG1-01a.db (directory)
DAG1-01a.log (directory)
DAG1-01b.db (directory)
DAG1-01b.log (directory)
Event Viewer > Applications > Microsoft > Exchange > HighAvailability > Seeding
I see error event 1187
The Volume Manager found misconfigured volume "\\?\Volume{volume GUID here}\' mounted at 'C:\exchVols\ExVol1\'. It does not have the expected number of database directories. There may be older database files still present on this volume that were not cleaned up by the Disk Reclaimer.
In testing, Auto-Reseed works (starts after an hour) and fails over to a working volume. I don't understand this error. Following MS convention for auto-reseed, each DB mount point is supposed to have the .db and .log directories. Two DBs in one volume will mean that four directories should be seen. If I reconfigure to show only two directories (with DB and LOG as deeper subdirectories), the error seems to stop but then I get an event error 1111 that the directory structure is incorrect and that Automatic Reseed is not supported with an invalid path naming convention.
Anyone familiar with this?
I have a stretched DAG spanning two sites, SiteA and SiteB.
SiteA has two mailbox servers MBX1 and MBX2 and SiteB has MBX3. I need the databases in SiteA to never mount in SiteB. So basically I only need the databases to fail-over within their site only. So I need to run the below commands.
Set-MailboxServer –Identity MBX1 – DatabaseCopyAutoActivationPolicy IntrasiteOnly
Set-MailboxServer –Identity MBX2 – DatabaseCopyAutoActivationPolicy IntrasiteOnly
My question is: Do I need to run the same command on MBX3 as well?
Set-MailboxServer –Identity MBX3 – DatabaseCopyAutoActivationPolicy IntrasiteOnly