Quantcast
Channel: Exchange Server 2013 - Setup, Deployment, Updates, and Migration 论坛
Viewing all 7008 articles
Browse latest View live

Exchange Server component Mailbox role: Mailbox service failed.

$
0
0
After Migration Exchange 2010 to 2013. And uninstall Exchange 2010 from the directory I can not install another exchange for below error. 
Error:
The following error was generated when "$error.Clear(); 
          if (($RoleIsDatacenter -ne $true) -and ($RoleIsDatacenterDedicated -ne $true))
          {
            if (test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
            {
              # upgrade the discovery mailboxes to R5 version, this will fix the RecipientDisplayType property of the discovery mailbox which was wrong in R4.
              get-mailbox -RecipientTypeDetails DiscoveryMailbox -DomainController $RoleDomainController | where {$_.IsValid -eq $false} | set-mailbox -DomainController $RoleDomainController
              $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName;
              $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
              $mbxs = @( get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 );
              if ( $mbxs.length -eq 0) 
              {
                $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
                if($dbs.Length -ne 0) 
                {
                  $mbxUser = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
                  if ($mbxUser.Length -ne 0) 
                  {
                    enable-mailbox -Discovery -identity $mbxUser[0] -DisplayName $dispname -database $dbs[0].Identity;
                  }
                }
              }
            }
            else
            {
              write-exchangesetuplog -info "Skipping creating Discovery Search Mailbox because of insufficient permission."
            }  
          }
        " was run: "Database is mandatory on UserMailbox.".

Error:
The following error was generated when "$error.Clear(); 
          if (($RoleIsDatacenter -ne $true) -and ($RoleIsDatacenterDedicated -ne $true))
          {
            if (test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
            {
              # upgrade the discovery mailboxes to R5 version, this will fix the RecipientDisplayType property of the discovery mailbox which was wrong in R4.
              get-mailbox -RecipientTypeDetails DiscoveryMailbox -DomainController $RoleDomainController | where {$_.IsValid -eq $false} | set-mailbox -DomainController $RoleDomainController
              $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName;
              $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
              $mbxs = @( get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 );
              if ( $mbxs.length -eq 0) 
              {
                $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
                if($dbs.Length -ne 0) 
                {
                  $mbxUser = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
                  if ($mbxUser.Length -ne 0) 
                  {
                    enable-mailbox -Discovery -identity $mbxUser[0] -DisplayName $dispname -database $dbs[0].Identity;
                  }
                }
              }
            }
            else
            {
              write-exchangesetuplog -info "Skipping creating Discovery Search Mailbox because of insufficient permission."
            }  
          }
        " was run: "Database is mandatory on UserMailbox.".
 

Md. Ramin Hossain


RPC over HTTP trouble Exchange 2013/2007 coexistence, 2013 RPCProxy cannot ping GC.

$
0
0

I currently have an Exchange 2013/2007 coexistence scenario which gives me trouble with the RPC over HTTP part with users with a 2007 mailbox. the MS RCA website performs 2 tests with the MAPI address book endpoints, once against a 2007 mailbox server and once a against a GC/DC, the last one fails. The logs are from our test domain, but the exact same happens in the production domain. running CU8 (recently upgraded, but problem was exactly the same with CU7)

Testing the MAPI Address Book endpoint on the Exchange server.
 The address book endpoint was tested successfully.
 
Additional Details
 Elapsed Time: 7872 ms.
 
Test Steps
 
Attempting to ping the MAPI Address Book endpoint with identity: exmb11.domain.test:6004.
 The endpoint was pinged successfully.
 
Additional Details
 
The endpoint responded in 156 ms.
Elapsed Time: 4153 ms.


Testing the MAPI Address Book endpoint on the Exchange server.
 An error occurred while testing the address book endpoint.
 
Additional Details
 Elapsed Time: 3079 ms.
 
Test Steps
 
Attempting to ping the MAPI Address Book endpoint with identity: tdc01421.domain.test:6004.
 The attempt to ping the endpoint failed.
  <label for="testSelectWizard_ctl12_ctl06_ctl02_ctl09_ctl00_tmmArrow">Tell me more about this issue and how to resolve it</label>
 
Additional Details
 
The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.
Elapsed Time: 3079 ms.



---
texmb11 = ex2007 mailbox
texfr11 = ex2007 CAS
tdc01421 = DC/GC
texch31 = 2013 multirole
---

other symptoms :

Browser test
https://texch31.domain.test/rpc/rpcproxy.dll?texmb11:6004 --> 503 (which is correct)
https://texch31.domain.test/rpc/rpcproxy.dll?tdc01421:6004 --> 404.0 Not Found

RPCPing
rpcping -t ncacn_http -s texmb11 -o RpcProxy=texch31.domain.test -P "user,dom,*" -I "user,dom,*" -H 2 -u 9 -a connect -F 3 -v 3 -e 6004
Success

rpcping -t ncacn_http -s tdc01421 -o RpcProxy=texch31.domain.test -P "user,dom,*" -I "user,dom,*" -H 2 -u 9 -a connect -F 3 -v 3 -e 6004
Fails!

so the Ex2013 RPCProxy doesn't proxy to the DC/GC, but the RPCProxy to an ex2007 mailbox server works fine, so the authentication methods configured are correct i'd say..

the same tests using the ex2007CAS server as RPC proxy all succeed!:

MS RCA is all green

https://texfr11.domain.test/rpc/rpcproxy.dll?texmb11:6004 --> 503
https://texfr11.domain.test/rpc/rpcproxy.dll?tdc01421:6004 --> 503 

rpcping -t ncacn_http -s texmb11 -o RpcProxy=texfr11.domain.test -P "user,dom,*" -I "user,dom,*" -H 2 -u 9 -a connect -F 3 -v 3 -e 6004
Success

rpcping -t ncacn_http -s tdc01421 -o RpcProxy=texfr11.domain.test -P "user,dom,*" -I "user,dom,*" -H 2 -u 9 -a connect -F 3 -v 3 -e 6004
Success!!

Logs

all tries against the 2013 CAS server generate '404' log entries in several logs int the Logging directory, the most explicit being the one in Program Files\Microsoft\Exchange Server\V15\Logging\HttpProxy\RpcHttp : HttpProxy_xxxxxx.LOG

2015-04-30T19:58:00.153Z,895cdf07-f2eb-4beb-b787-da02ba11b0c2,15,0,1076,0,,RpcHttp,webmail.domain.test,/rpc/rpcproxy.dll,,Basic,true,DOM\user,,,MSRPC,10.10.142.132,TEXCH31,404,,MailboxGuidWithDomainNotFound,RPC_IN_DATA,,,,,,,,,4,,,,1,,,0,,0,,0,0,,0,2,0,,,,,,,,,1,1,0,,1,,2,2,,?TDC01422.domain.test:6004,,BeginRequest=2015-04-30T19:58:00.153Z;CorrelationID=<empty>;ProxyState-Run=None;ProxyState-Complete=CalculateBackEnd;EndRequest=2015-04-30T19:58:00.153Z;,HttpProxyException=Microsoft.Exchange.HttpProxy.HttpProxyException:RPC server name passed in by client could not be resolved: TDC01422.domain.test   at Microsoft.Exchange.HttpProxy.RpcHttpProxyRequestHandler.ResolveToDefaultAnchorMailbox(String originalRpcServerName  String reason)    at Microsoft.Exchange.HttpProxy.RpcHttpProxyRequestHandler.ResolveAnchorMailbox()    at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.InternalBeginCalculateTargetBackEnd(AnchorMailbox& anchorMailbox)    at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.<BeginCalculateTargetBackEnd>b__3b();

the error suggests the name could not be resolved. but nslookup works fine. i can ping the tdc01421 correctly form texch31, it returns me the ipv4 address. i can telnet to port 6004 from texch31 server to tdc01421 giving me the correct 'ncacn_http' answer..

i look at the 'ValidPorts' and ValidPorts_Autoconfig_Exchange reg keys and filled them with the same i have on the 2007cas servers (all ex servers, all dc/gc's, all of them with netbios & fqdn ports 6001,6002 & 6004..) but also no success.

im out of ideas by now..

Exchange 2003 Upgrade / Windows 2003 Upgrade Dilema

$
0
0

Our current Active Directory domain consists of 3 Windows 2003 domain controllers.  The FFL and DFL are Windows 2003. In the domain, we have a member server running Exchange 2003 Server for messaging and another Windows 2008 member server running MOSS 2007.

We have been given a budget for an IT refresh and would like to upgrade to the latest versions of these products where possible.  I have read various blogs that advise that an Exchange 2003 messaging environment is not supported in a Windows 2012 domain.  My dilema is where to start  I want to upgrade Active Directory to 2012 and also Exchange to Exchange Server 2013.  Is there a recommended approach to this without breaking the system?

Thanks

Public Folder Migration from Exchange 2007 to 2013 fails RelinquishedWlmStall budget limitations

$
0
0

I have been trying to migrate approx 50 public folders from Exchange 2007 to Exchange 2013 for several months.  I have followed every link I can find on how to do the migration properly.  It will stay in a queued state for hours until the MRS is restarted.  It will then start copying messages.  After reaching 28% I get RelinquishedWlmStall as Status Detail.  Running the Get-PublicFolderMigrationRequestStatistics -IncludeReport | fl command I get the following: (truncated)

Status                           : InProgress

FailureTimestamp                 :
IsValid                          : True
ValidationMessage                :
OrganizationId                   :
RequestGuid                      : ff4af794-f31e-4334-959f-7d6c4ccbe310
RequestQueue                     : PublicFolders
ExchangeGuid                     : b12c1f83-c4ae-46bb-a26a-0422d90800e4
Identity                         : eddf983d-5827-4a2a-98ef-820321ebebd0\ff4af794-f31e-4334-959f-7d6c4ccbe310
DiagnosticInfo                   :
Report                           
                                   4/23/2015 8:49:37 AM [pionexxxx] Request processing started.
                                   4/23/2015 8:49:37 AM [pionexxxxx] Cleared sync state for request
                                   00000000-0000-0000-0000-000000000000 due to 'CleanupOrphanedMailbox'.
                                   4/23/2015 8:49:38 AM [pionexxxxxx] Stage: CreatingFolderHierarchy. Percent complete:
                                   10.
                                   4/23/2015 8:49:38 AM [pionexxxxxx] Initializing folder hierarchy from mailbox '': 50
                                   folders total.
                                   4/23/2015 8:49:38 AM [pionexxxx] Folder creation progress: 0 folders created in
                                   mailbox 'b12c1f83-c4ae-46bb-a26a-0422d90800e4'.
                                   4/23/2015 8:49:38 AM [pionexxxxx] Warning: Failed to find or link recipient object
                                   'FF-D5-EF-1A-0A-95-D7-4B-89-02-A6-9E-DA-4D-23-4B' in active directory for mail
                                   enabled public folder 'Public Root/IPM_SUBTREE/AccountingFaxes' with EntryId '00-00
                                   00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-3B-C3-C1-30-22-E0-BE-4E
                                   98-03-B9-14-4F-B4-12-C1-00-00-00-0F-C3-4C-00-00'. This folder can be linked
                                   manually by running Enable-MailPublicFolder cmdlet after the migration completes.
                                   4/23/2015 8:49:39 AM [pionexxxx] Warning: Failed to find or link recipient object
                                   'D8-46-09-BE-0B-3D-6E-4A-95-10-8F-C5-AA-0B-88-50' in active directory for mail
                                   enabled public folder 'Public Root/IPM_SUBTREE/AccountingFaxes/CashRec/Inventory'
                                   with EntryId '00-00-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-3B-
                                   3-C1-30-22-E0-BE-4E-98-03-B9-14-4F-B4-12-C1-00-00-00-12-6A-F5-00-00'. This folder
                                   can be linked manually by running Enable-MailPublicFolder cmdlet after the
                                   migration completes.
                                   4/23/2015 8:49:39 AM [pionexxxx] Warning: Failed to find or link recipient object
                                   'A6-12-DA-05-7D-21-DE-44-90-61-64-23-8C-62-41-F4' in active directory for mail
                                   enabled public folder 'Public Root/IPM_SUBTREE/AccountingFaxes/CashRec/Ulysses'
                                   with EntryId '00-00-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-3B-
                                   3-C1-30-22-E0-BE-4E-98-03-B9-14-4F-B4-12-C1-00-00-00-0F-C3-7C-00-00'. This folder
                                   can be linked manually by running Enable-MailPublicFolder cmdlet after the
                                   migration completes.
                                   4/23/2015 8:49:40 AM [pionexxxx] Warning: Failed to find or link recipient object
                                   '96-76-90-F1-A5-B7-DB-41-A7-A3-D6-8D-86-AE-45-A5' in active directory for mail
                                   enabled public folder 'Public Root/IPM_SUBTREE/CSR Schedule' with EntryId '00-00-00
                                   00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-3B-C3-C1-30-22-E0-BE-4E-98
                                   03-B9-14-4F-B4-12-C1-00-00-00-0E-34-FF-00-00'. This folder can be linked manually
                                   by running Enable-MailPublicFolder cmdlet after the migration completes.
                                   4/23/2015 8:49:40 AM [pionexxxx] Warning: Failed to find or link recipient object
                                   '82-72-47-AA-D7-68-85-4C-91-92-41-45-8A-20-EA-6D' in active directory for mail
                                   enabled public folder 'Public Root/IPM_SUBTREE/DC 24 Hr Schedule' with EntryId '00-
                                   0-00-00-1A-44-73-90-AA-66-11-CD-9B-C8-00-AA-00-2F-C4-5A-03-00-85-62-89-2A-52-C3-92-
                                   5-93-F8-5A-6F-56-5D-D1-D4-00-00-00-00-27-37-00-00'. This folder can be linked
                                   manually by running Enable-MailPublicFolder cmdlet after the migration completes.
                                   4/23/2015 8:49:41 AM [pionexxxx] Folder hierarchy initialized for mailbox
                                   'b12c1f83-c4ae-46bb-a26a-0422d90800e4': 46 folders created.
                                   4/23/2015 8:49:41 AM [pionexxxx] Stage: CreatingInitialSyncCheckpoint. Percent
                                   complete: 15.
                                   4/23/2015 8:49:41 AM [pionexxxx] Initial sync checkpoint progress: 0/50 folders
                                   processed. Currently processing mailbox 'b12c1f83-c4ae-46bb-a26a-0422d90800e4'.
                                   4/23/2015 8:49:42 AM [pionexxxx] Initial sync checkpoint completed: 46 folders
                                   processed.
                                   4/23/2015 8:49:42 AM [pionexxxx] Stage: LoadingMessages. Percent complete: 20.
                                   4/23/2015 8:49:43 AM [pionexxxx] Messages have been enumerated successfully. 40607
                                   items loaded. Total size: 149 MB (156,253,810 bytes).
                                   4/23/2015 8:49:43 AM [pionexxxx] Stage: CopyingMessages. Percent complete: 25.
                                   4/23/2015 8:49:43 AM [pionexxxx] Copy progress: 0/40607 messages, 0 B (0
                                   bytes)/149 MB (156,253,810 bytes), 11/50 folders completed.
                                   4/23/2015 9:04:37 AM [pionexxxx] Stage: CopyingMessages. Percent complete: 28.
                                   4/23/2015 9:04:37 AM [pionexxxxx] Copy progress: 3660/40607 messages, 7.015 MB
                                   (7,355,409 bytes)/149 MB (156,253,810 bytes), 11/50 folders completed.
                                   4/23/2015 9:04:37 AM [pionexxxx] Relinquishing job because of large delays due to
                                   unfavorable server health or budget limitations.

ItemsTransferred                 : 3660
PercentComplete                  : 25
4/23/2015 9:04:37 AM [pionexxxx] Relinquishing job because of large delays due to
unfavorable server health or budget limitations.

It never tries to restart.  Can anyone please help?  The server checks for health all come back ok.   I will be more than glad to include further information.  

Setup Error Reinstallin Exchange 2013

$
0
0
Trying to reinstalling Exchange 2013 after removing Exchange from ADSI, IIS, Registry, and Active Directory. Receiving the following error when attempting AD Prep. ERROR: Method Not found:  Boolean Microsoft.Exchange.Data.Mime.MimeAddressParser.IsValidDomain(System.String, Int32, Boolean)'. and the setup fails.  This occurs whether I try Schema Prep, ADPrep or just trying to load Exchange.  This is a lab environment.  Any suggestions to correct the install?

Exchange 2013 Storage

$
0
0

Hi,

I am currently redesigning a customers small Hyper V Deployment and am looking for some advice on how to set up the Exchange storage.

Ive looked at TechNet and it seems to assume that you are using physical hardware when talking about storage although I may be reading it wrong.

My customer has 2 Hyper V hosts which are standalone at the moment. I plan to cluster these to make them more highly available.

The restriction I have is on the storage side, they are using a Dell server with a load of disks and FreeNas installed on it. It is configured in a RAID 6 across all disks and I wont be able to change this.

What would be the best way to set this up? I was thinking about just creating a separate VHDX disk which was going to house the Logs and Database presented to the host via iSCSI (not the guest)

What do you guys think?

Legacy Email Address Polcies - Delete or Upgrade?

$
0
0

I've just completed a migration of 300 users to Exchange Online from Exchange 2007.  I've got an on-prem Hybrid Server (Exchange 2013) along with a DirSync server.  I now want to decommission the Exchange 2007 server infrastructure.

The problem is the legacy (Exchange 2003) Email Address Policies on the Exchange 2007 Server.  There are several Policies and they are all unwanted including the default Email Address Policy which applies incorrect attributes.

My question is this: Can I simply delete ALL Email Address Policies on the Exchange 2007 server?  I can view the policies on the 2013 Hybrid server.  They cannot be edited on the 2007 Exchange server without first being upgraded, but I seem to be able to delete them (successfully delete 2 that are known to be obsolete).

I've read TechNet articles about upgrading the Policies but I'm concerned that incorrect attributes will be applied in the process of upgrading. I'd prefer to just delete them.  Is there anything I should know before deleting the Default Email Address Policy, or any other Email Address Policy?  I assume I can just create a new Default Email Address policy on the Exchange 2013 server once the defunct legacy Policies have been deleted.  Is this correct?

Mailbox moves extremely slow and stopping with StalledDueToCI status

$
0
0
I am migrating mailboxes from Exchange 2007 to Exchange 2013.  I have an Exchange 2013 DAG.  Previously I was running Exchange 2013 CU2 and had no issues with migrations, they were migrating fast and had no issues.  After upgrading Exchange 2013 to SP1 I have had very slow migrations and they eventually halt with the StalledDueToCI status.  I was originally doing batch migrations, I dropped it down to a single move request and even migrating a single mailbox from one database to another on the same Exchange 2013 server and I still have the same issue.  I've also tried moving a mailbox to a database that is not part of the DAG and I still have the same issue.  I have the ContentSubmitters group so that's not the issue.  Once it stalls I have to restart the MRS and it kicks off again but then it stalls again with the same error.  ALL of my databases have a "Healthy" status for the content index.  Any help would be appreciated.  Thanks.

INSUFF_ACCESS_RIGHTS in forest

$
0
0

i have test network with two domain (main.domain, new.domain) in one forest.

main.domain contains Exchange 2013 SP1 CU8.

I can successfully create any objects in new.domain as Main\administrator

when i try to create or add mailbox to exist user in new.domain then i got error:

i added "MAIN\Exchange trusted subsystem" into new.domain with Full permissions, and then i still receive error, but account is created without password and disabled:

i compared permission on MAIN.domain and NEW.domain, and MAIN contains more permissions for Exchange.

How i can automatically create same/necessary permissions in NEW.domain?

i did in NEW.domain "setup /PrepareAD / PrepareSchema" - doesn't help.

Thank you!



CU8 questions

$
0
0

I have 3 on-premise Exchange 2013 systems, I use 2 for active mailboxes and one for testing and backup if 1 of the others fails.

Ideally I'd like to install CU8 on the 3 system first, how long before I do systems 1 and 2.

Thoughts or ideas?

Migration to 2013 from 2007 with new names.

$
0
0

We are planning a migration to Exchange 2013 from 2007. We do not currently use OWA externally but publish both EWS and Outlook Anywhere externally through ISA 2006. With 2013 we are not planning to use ISA but just point to the load balancer. We are also planning to use different names than what we use now.

Will I need to have existing name on my certificate as well as the new names?

Are there any other gotchas I might encounter as a result of using different names for Outlook Anywhere and EWS or will autodiscover take care of that for me?

Thanks a lot.


Kenny

Exchange Server 2013 migration and high avalability

$
0
0

Hello,

We are using Office 365 online and will be migrating onto an in-house Exchange Server 2013 on a new Windows Server box.

I have two questions:

1. What is the best way to migrate everything from the Office 365 to the in house server? Do I setup a hybrid environment and then move the mailboxes and then remove the hybrid environment?

2. What is the best way to setup high availability for the in-house Exchange server? I found out that in order to setup Exchange 2013 as high availability it needs to run on Windows server 2012 STD or Windows server 2008 Enterprise.

Please let me know and provide links to step by step instructions if possible.

Thank you, Karel


Thank you. Karel Grulich, MCSE, SBS

Outlook attempts connection to old Exchange server - even for new accounts

$
0
0

Scenario:

Client contacted me to implement Exchange 2013 in their existing organisation.

Old server is Exchange 2007 installed on a Windows 2003 x64 server

The old server is also a Domain Controller (the only DC)

A UC certificate has been purchased & installed on the new server.

All clients are running Outlook 2010

Problem:

The problem is that after moving mailboxes - the outlook client still attempts to connect to the Old server.

A new user with a new mailbox created on the New Exchange 2013 has the same issue, autodiscover resolves OK, but the SSL error that is presented shows the self-signed cert on the old server.

Accessing the mailbox via OWA is OK indicating that the mailbox is working & mail flow is OK (all mail is routed via the Exchange 2013)

Running "Get-ClientAccessServer |fl identity,autodiscoverserviceinternaluri" on the Exchange 2013 gives the correcthttps://autodiscover.domain.com.au/Autodiscover/Autodiscover.xml for the Exchange server and reports https://oldserver.domain.local/Autodiscover/Autodiscover.xmlfor the old server.

There is a DNS zone to the domain.com.au on the internal DNS server and there is an entry for autodiscover that resolves to the Exchange 2013 server.

Cannot install Exchange 2013 on Server 2012 R2

$
0
0

I receive the following error when attempting to install Exchange Server 2013 on the same machine running Windows Server 2012 R2 Essentials:

"An unsupported operating system was detected. Exchange Server 2013 Client Access and Mailbox Server roles support Windows Server 2008 R2 SP1 or later and Windows Server 2012"

SP1 for Exchange Server 2013 was released but I'm not sure how to integrate it or whether or not I even need to. Please let me know if there is a fix or workaround.

Thank you.

Error when adding the Mailbox Role to what was a CAS only Server (Ex 2013)

$
0
0

We have a server that was just hosting the CAS role, Exchange 2013 CU7, Server 2012.  The need to add the Mailbox Role presented itself, which seems like a fairly easy task to accomplish.  During the install (using the CU7 install media) the following error occurred and failed the entire install. 

Any help would be appreciated.  If it looks to be too involved, I might end up exercising a TechNet support session but would prefer not to if it's a fairly easy fix. 

This is a production environment, all 2013 Exchange Servers.

During Step 1 of 5:  Mailbox Role: Client Access service

Error:

The following error was generated when "$error.Clear();

          $BEVdirIdentity = $RoleNetBIOSName + "\OWA (Exchange Back End)";

          new-OwaVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomainController;

          set-OwaVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;

        " was run: "System.InvalidOperationException: An error occurred while creating the IIS virtual directory 'IIS://XXXXX.domain.local/W3SVC/2/ROOT/owa' on '<server name>'. ---> System.Runtime.InteropServices.COMException: Cannot create a file when that file already exists. (Exception from HRESULT: 0x800700B7)

   at System.DirectoryServices.Interop.UnsafeNativeMethods.IAdsContainer.Create(String className, String relativeName)

   at System.DirectoryServices.DirectoryEntries.Add(String name, String schemaClassName)

   at Microsoft.Exchange.Management.Metabase.IisUtility.CreateWebDirObject(String parent, String path, String vdirName)

   at Microsoft.Exchange.Management.Metabase.CreateVirtualDirectory.Execute()

   at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.CreateToMetabase()

   at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalProcessRecord()

   --- End of inner exception stack trace ---

   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)

   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)

   at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalProcessRecord()

   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()

   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Error:

The following error was generated when "$error.Clear();

          $BEVdirIdentity = $RoleNetBIOSName + "\OWA (Exchange Back End)";

          new-OwaVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomainController;

          set-OwaVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;

        " was run: "Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: The operation couldn't be performed because object 'EMAILGW2013\OWA (Exchange Back End)' couldn't be found on 'WPB08DC1.autec.pvt'.

   at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.GetDataObject[TObject](IIdentityParameter id, IConfigDataProvider session, ObjectId rootID, OptionalIdentityData optionalData, Nullable`1 notFoundError, Nullable`1 multipleFoundError, ExchangeErrorCategory errorCategory)

   at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.GetDataObject[TObject](IIdentityParameter id, IConfigDataProvider session, ObjectId rootID, OptionalIdentityData optionalData, Nullable`1 notFoundError, Nullable`1 multipleFoundError)

   at Microsoft.Exchange.Configuration.Tasks.SetObjectWithIdentityTaskBase`3.ResolveDataObject()

   at Microsoft.Exchange.Configuration.Tasks.SetSystemConfigurationObjectTask`3.ResolveDataObject()

   at Microsoft.Exchange.Configuration.Tasks.SetObjectTaskBase`2.PrepareDataObject()

   at Microsoft.Exchange.Management.SystemConfigurationTasks.SetVirtualDirectory`1.PrepareDataObject()

   at Microsoft.Exchange.Management.SystemConfigurationTasks.SetExchangeVirtualDirectory`1.PrepareDataObject()

   at Microsoft.Exchange.Management.SystemConfigurationTasks.SetWebAppVirtualDirectory`1.PrepareDataObject()

   at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()

   at Microsoft.Exchange.Configuration.Tasks.SetSystemConfigurationObjectTask`3.InternalValidate()

   at Microsoft.Exchange.Management.SystemConfigurationTasks.SetExchangeVirtualDirectory`1.InternalValidate()

   at Microsoft.Exchange.Management.SystemConfigurationTasks.SetWebAppVirtualDirectory`1.InternalValidate()

   at Microsoft.Exchange.Management.SystemConfigurationTasks.SetOwaVirtualDirectory.InternalValidate()

   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()

   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

The Setup logs also show the following:

[05/06/2015 13:44:07.0723] [1] [ERROR] The operation couldn't be performed because object '<ServerName\OWA (Exchange Back End)' couldn't be found on '<DCname.domain.local'.
[05/06/2015 13:44:07.0723] [1] [ERROR-REFERENCE] Id=ClientAccessOwaComponent___62bd834915a7470798aa47ba1f2b6800 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[05/06/2015 13:44:07.0723] [1] Setup is stopping now because of one or more critical errors.
[05/06/2015 13:44:07.0723] [1] Finished executing component tasks.
[05/06/2015 13:44:07.0754] [1] Ending processing Install-ClientAccessRole

Thanks!

Chris


Best Practice For Assigning Exchange Services to Certificates

$
0
0

Good Morning Everybody,

I am in the process of doing an Exchange 2010 > 2013 migration and had a question about assigning Exchange services to server certificates.  In the current setup, all services are assigned to the third party (Entrust) certificate.  Is this best practice.  I have seen some posts where people state to keep the SMTP service assigned to a self-signed cert.  Just curious what the best practice is.  Any guidance would be greatly appreciated.

--Scott

Autodiscover HTTP 400 Bad request

$
0
0

Fresh install running in coexistence mode, created test user on exchange 2013 mbx1, can not get autodiscover to work... it keeps returning HTTP error 400 Bad request. Any suggestions ?


[PS] C:\Program Files\Microsoft\Exchange Server\V15\Scripts>Test-OutlookWebServices | fl
Creating a new session for implicit remoting of "Test-OutlookWebServices" command...


RunspaceId          : a3a825b3-f752-4b7d-b461-9cdc263f0398
Source              : MBX1.domain.com
ServiceEndpoint     : mail.domain.com
Scenario            : AutoDiscoverOutlookProvider
ScenarioDescription : Autodiscover: Outlook Provider
Result              : Failure
Latency             : 411
Error               : System.Net.WebException: The remote server returned an error: (400) Bad Request.
                         at System.Net.HttpWebRequest.GetResponse()
                         at
                      Microsoft.Exchange.Management.SystemConfigurationTasks.ServiceValidatorBase.InternalInvoke()
                         at Microsoft.Exchange.Management.SystemConfigurationTasks.ServiceValidatorBase.Invoke()
Verbose             : [2013-05-06 18:42:58Z] Autodiscover connecting to
                      'https://mail.domain.com/autodiscover/autodiscover.xml'.
                      [2013-05-06 18:42:58Z] Test account:extest_47f5c08502074@domain.com Password: ******
                      [2013-05-06 18:42:58Z] Autodiscover request:
                      User-Agent:MBX1/Test-OutlookWebServices/extest_47f5c08502074@domain.com
                      Content-Type: text/xml; charset=utf-8
                      Host: mail.domain.com
                      [2013-05-06 18:42:58Z] Autodiscover request:
                      <?xml version="1.0"?>
                      <Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema"
                      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                      xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/requestschema/2006">
                        <Request>
                          <EMailAddress>extest_47f5c08502074@domain.com</EMailAddress>
                          <AcceptableResponseSchema>http://schemas.microsoft.com/exchange/autodiscover/outlook/response
                      schema/2006a</AcceptableResponseSchema>
                        </Request>
                      </Autodiscover>
                      [2013-05-06 18:42:58Z] Autodiscover response:
                      Connection: Keep-Alive
                      Content-Length: 11
                      Content-Type: text/html
                      Date: Mon, 06 May 2013 18:42:58 GMT
                      Server: Microsoft-IIS/7.5
                      X-Powered-By: ASP.NET
                      [2013-05-06 18:42:58Z] Autodiscover response:
                      System.Net.WebException: The remote server returned an error: (400) Bad Request.
                         at System.Net.HttpWebRequest.GetResponse()
                         at
                      Microsoft.Exchange.Management.SystemConfigurationTasks.ServiceValidatorBase.InternalInvoke()
                         at Microsoft.Exchange.Management.SystemConfigurationTasks.ServiceValidatorBase.Invoke()
MonitoringEventId   : 6001

Problem with migrating from Exchange 2007

$
0
0

I'm trying to migrate users from Exchange 2007 to Office 365. For last few months all new users were created on Office 365 but it is time to move existing ones there as well. I also have Exchange 2013 on premises with group of users migrated there from 2007 and they will stay there. Emails are still sent using 2007 through Edge server (legacy.mydomain.com) and OWA is going to 2013 through Sonicwall (mail.mydomain.com).

When I test Outlook connectivity on testconnectivity.microsoft.com I have error Testing RPC over HTTP connectivity to server mail.mydomain.com RPC over HTTP connectivity failed.

Attempting to ping RPC proxy mail.mydomain.com
     RPC Proxy can't be pinged.
     
    Additional Details
     
An unexpected network-level exception was encountered. Exception details:
Message: The remote server returned an error: (404) Not Found.
Type: Microsoft.Exchange.Tools.ExRca.Extensions.MapiTransportException
Stack trace:
at Microsoft.Exchange.Tools.ExRca.Extensions.MapiRpcTestClient.PingProtocolProxy(String endpointIdentifier)
at Microsoft.Exchange.Tools.ExRca.Tests.MapiPingProxyTest.PerformTestReally()
Exception details:
Message: The remote server returned an error: (404) Not Found.
Type: System.Net.WebException
Stack trace:
at System.Net.HttpWebRequest.GetResponse()
at RpcPingLib.RpcPing.PingProxy(String internalServerFqdn, String endpoint)
at Microsoft.Exchange.Tools.ExRca.Extensions.MapiRpcTestClient.PingProtocolProxy(String endpointIdentifier)
Elapsed Time: 94 ms.

It is trying to use mail.mydomain.com and this email is on old Exchange 2007 (legacy.mydomain.com).

Office 365 migration uses Outlook anywhere to set up the migration endpoint. There should be something wrong with configuration of Outlook anywhere.

Any help would be appreciated.

Sizing requirements and real world best practices Exchange 2013

$
0
0

Greetings all,

Let me first start off by saying I work in an environment where I wear a variety of hats.  Network Administration, System Administration, Infrastructure design and implementation, backups, Email admin(by no means am I an exchange admin, but have recovered from outages etc..).  You name it I do it.  With that said its tough to focus on one area, but at this point I need to.  We currently host Exchange 2007, we have about 230 mailboxes with a 5G quota. Currently we are using about 284 GB of space with regards to our databases.  I am in the process of getting together the sizing requirements for our 2013 Exchange build.

We currently run our exchange servers (1 mailbox server, 1 CAS + HUB) on VMware.  We would like to have our new environment run on VMware as well.   From my research and using the sizing calculator, I am getting a bit confused on best practices. 

I am going to run in a multi-server role configuration for the new build.

Question 1:  Should my logs be on the same volume as my OS?  I prefer to separate this out.  Exchange calculator has recommended the following: 2 volumes for DB's, 4 DB' per volume and 2 volume's for my logs.  I would assume and additional volume for my OS?  This is what I have come up with: 2TB for database volumes, 350 GB for logs, and 120 OS volume. This assumes growth for the next 5 years with 10% growth year over year.

Question 2:  I don't have a separate site but would like to have some form of HA.  When I fill out the calculator and another mailbox server and DAG it appears my volume requirement grows to nearly 7TB.  I expected my size requirements to double for my secondary server and adding a file share witness.  I expected more like a 5TB volume requirement between both servers.  Also, it switches to a 2 volume requirement per server, putting a 1 DB+logs on each volume.  This would make my databases huge.

 What am I missing?  

I feel my implementation being relatively small.  A single mulit-server role configuration is tempting for simplicity, but I feel HA is to good to pass up. 

Thanks for any advice or recommendations

Joe

Public Folder MIgration Exchange 2007 -> Exchange 2013

$
0
0

Hello,

I am having some major issues here. I just want to give a quick background of what is occurring. All user mailboxes have been migrated to new Exchange 2013 environment. I started the process to migrate public folders to new environment, I ended up getting to the final phase which was to import the public folders into the newly created PF Mailboxes. It failed at 10 percent. Issue looks to of been because of whitespaces and so on. I made some changes and cleared the migration and tried again and it failed again at 10 percent which is fine I can understand that. I need to do some more formatting on the old public folders.

After this occurred I deleted the PF Mailboxes I created. I also deleted the Database. I created a new Database and here is the issue when I try to create PF Mailboxes again I receive this error - "Active Directory operation failed on DC. This error is not retriable. Additional information:
Access is denied."

I do not believe it is any permission issue as I was just able to create PF mailboxes before. Plus I am part of the correct permission groups. I have read a lot of fixes out there on the net but they don't seem to relate to my issue exactly.

But again this issue occurred after I deleted the PF mailboxes and also deleted the Database and recreated the database and while trying to create new PF mailboxes I receive error message as I have indicated above.

I hope someone can assist.

Thanks

Viewing all 7008 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>