Exchange Server 2013 OWA Related Issue

Hi everyone,
we installed exchange server 2013 for our new organisation.
Everything works fine except OWA Version, it shows as 2010.
Any suggestion to resolve this issue.
Regards
Kart26

Could be that you are still running an early build of Exchange 2013
and are using IE11 - That would load OWA Light that looks exactly the way it did in Exchange 2010.
Resolution: Install Exchange 2013
CU3
or as a workaround, add the domain to the compatibility view in IE.
Martina Miskovic

Similar Messages

Using Outlook Web App Web Parts in Exchange Server 2013 - OWA ? Possible?

Using Outlook Web App Web Parts in Exchange Server 2013 - OWA ? Possible?
We recently upgraded from Exchange 2010 to Exchange 2013.
The links that used OWA Web parts have completely stopped working and generate the " :( something went wrong contact your help desk" screen for domain Authenticated users other than myself. The links accessed content of a Shared Account of which
I am an owner and can set the necessary permissions using the Outlook 2013 client.
Using the example from the link provided below we were able to provide calendar access to all authenticated users in our area. The link for calendar still works for me but for noone else. Additionally, all navigation menus are missing when I use this link.
<server>/owa/<SMTP address>/?cmd=contents&module=calendar&view=weekly name
Another crafted link provided web access to our group's task list. This has completely stopped working for anyone including myself. However, when I use "open another mailbox" I am able to navigate to the needed pages.
<server name>/owa/<SMTP address>/?cmd=contents&module=tasks
These links were crafted using advice provided from this provided link.
technet.microsoft.com/en-us/library/bb232199(v=exchg.141).aspx
Is it still possible to use Outlook Web App Web Parts in Exchange Server 2013 - OWA?
Or
Is this a misconfiguration of some sort?
My IT support has given up and closed out the ticket stating that maybe Microsoft will fix this someday...

Hello,
At present, there is no official article to verify whether we can use Outlook Web App Web Parts in Exchange Server 2013. In exchange online, the Outlook Web App Parts is supported.
Cara Chen
TechNet Community Support
Hi, you said this feature is supported in Exchange Online (I understand you're referring to Office 365). Can you please point me to some documentation as I was trying to use it with my E3 account and it doesn't seem to work?
What I'm trying to acomplish is something similar to our old URL (Exchange 2010) in Office 365:
https://ourserver.mydomain.com/owa/[email protected]/?cmd=contents&module=calendar&view=monthly
The best I can do in Office 365 is this:
https://outlook.com/owa/mydomain.com/[email protected]/#path=/calendar
But it's clearly not the same and Office 365 ignores all the information I add to the URL. I would greatly appreciate something in the line of the document referred by 'MarquetteENG' (technet.microsoft.com/en-us/library/bb232199(v=exchg.141).aspx)
Thanks.
Paulo.
Paulo Dias - IT Pro Evangelist

Exchange Server 2013: Internal Certificate Issue

Dear All,
I have MS Exchange 2013 with domain name: Exchange.local (fqdn: ex001.exchange.local).
I had created the accepted domain for xyz.com. I bought the Wildcard Certificate for *xyz.com. I had issued the certificate to my MS Exchange server.
External/Internet users: they can setting up and connected with MS Outlook
but I had problem with internal. when I setup account to MS Outlook. it failed and cannot connected to MS Exchange server because invalid ex001.exchange.local.
Do you have best solution and commend on this issue for internal users?
BR,
KH
[email protected]

Hi khemarin,
Did you set correctly the internal url´s for the services?
For Autodiscover URL:
If you are using a single server or all servers are in the same AD site, then the following commands can be used:
Get-ClientAccessServer | Set-ClientAccessServer -AutodiscoverServiceInternalUri https://mail.example.net/autodiscover/autodiscover.xml
However if you are using multiple servers in multiple AD sites, then you need to set the commands as per the box below, replacing "CAS-Server" with the real name of the server that holds the CAS role.
Set-ClientAccessServer -Identity "CAS-Server" -AutodiscoverServiceInternalUri https://mail.example.net/autodiscover/autodiscover.xml
For Webservices URL:
As with Autodiscover, if you are using a single server then the following commands can be used:
Get-WebServicesVirtualDirectory | Set-WebServicesVirtualDirectory -InternalUrl https://mail.example.net/ews/exchange.asmx -ExternalUrl https://mail.example.net/ews/exchange.asmx
However if you are using multiple servers, then you need to set the commands as per the box below, replacing "CAS-Server" with the real name of the server that holds the CAS role.
Set-WebServicesVirtualDirectory -Identity "CAS-Server\EWS (Default Web Site)" -InternalUrl https://mail.example.net/ews/exchange.asmx -ExternalUrl https://mail.example.net/ews/exchange.asmx
For Outlook Anywhere URL:
Right click on the Client Access Server and choose Properties. Click on the tab Outlook Anywhere and adjust the URL to match the external name on the SSL certificate.
You should also need to check OAB Virtual Directory on IIS and see if it is enabled for SSL.
And you should have a Split DNS in this case.
I hope it helps.
David Paris Vicente

Exchange Server 2013 Outlook Anywhere issue

I am working on an issue with Outlook Anywhere in Exchange 2013 where external users cannot connect. This is a new server co-existing with an Exchange
2010 server that will soon be decommissioned.
When I run an Outlook Connectivity test on testexchangeconnectivity.com I get the following error. I am not seeing anything in the application or system logs.
I already applied CU 6 (which was released today) and am seeing the same results. Port 443 is exposed directly to the web (no TMG, load balancer, proxy server, or SSL accelerator). Any help would be greatly appreciated!
Attempting to ping RPC proxy <external Exchange URL>.
RPC Proxy can't be pinged.
Additional Details
An unexpected network-level exception was encountered. Exception details:
Message: The remote server returned an error: (500) Internal Server Error.
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: (500) Internal Server Error.
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: 290 ms.

Hi,
Does the issue only happen to your Exchange 2013 external users? How about Exchange 2010 users?
Please make sure the external host name in your external Exchange URL is pointed to your Exchange 2013 in public DNS. For your coexistence environment, please make sure the Outlook Anywhere configurations are correct in both Exchange 2010 and Exchange 2013.
We can run the following command to check it:
Get-OutlookAnywhere | FL
If the configuration is not correct, we can run the following command to set it(supposing the mail.domain.com is your External host name):
For Exchange 2010:
Set-OutlookAnywhere -Identity “E14-01\Rpc (Default Web Site)” -ClientAuthenticationMethod Basic -SSLOffloading $False -ExternalHostName mail.domain.com -IISAuthenticationMethods NTLM, Basic
For Exchange 2013:
Set-OutlookAnywhere -Identity "E15-01\Rpc (Default Web Site)" -InternalHostname mail.domain.com -ExternalHostname mail.domain.com -InternalClientAuthenticationMethod Ntlm -ExternalClientAuthenticationMethod Basic -ExternalClientsRequireSsl
$True -InternalClientsRequireSsl $true
After all settings, please recycle MS Exchange RPCProxy AppPools and Default AppPools on both Exchange 2013 and Exchange 2010. Then restart IIS service by running IISReset /noforce from a command prompt window.
Regards,
Winnie Liang
TechNet Community Support

Exchange Server 2013 CU7 Installation Issue

Error:
The following error was generated when "$error.Clear();
            if ($RoleProductPlatform -eq "amd64")
                try
                    # Need to configure the ETL traces before the fast service is installed. This will ensure that when the service comes up
                    # it will have the necessary trace session setting available to read from the registry
                    $fastPerfEtlTraceFolderPath = Join-Path -Path $RoleBinPath -ChildPath "\Search\Ceres\Diagnostics\ETLTraces"
                    $fastDiagnosticTracingRegKeyPath = 'HKLM:\SOFTWARE\Microsoft\Office Server\16.0\Search\Diagnostics\Tracing'
                    if(-not(Test-Path -Path $fastPerfEtlTraceFolderPath))
                        $null = New-Item $fastPerfEtlTraceFolderPath -Type 'Directory' -Force
                    if (-not(Test-Path -Path $fastDiagnosticTracingRegKeyPath))
                        $null = New-Item -Path $fastDiagnosticTracingRegKeyPath -Force
                    $null = New-ItemProperty -Path $fastDiagnosticTracingRegKeyPath -Name 'TracingPath' -PropertyType 'string' -Value $fastPerfEtlTraceFolderPath
-Force
                    $null = New-ItemProperty -Path $fastDiagnosticTracingRegKeyPath -Name 'TracingFileName' -PropertyType 'string' -Value 'DocumentProcessingTrace'
-Force
                    $null = New-ItemProperty -Path $fastDiagnosticTracingRegKeyPath -Name 'DocumentParserSuccessLogMessage' -PropertyType 'Dword' -Value 1 -Force
                    $null = New-ItemProperty -Path $fastDiagnosticTracingRegKeyPath -Name 'DocumentParserLoggingNoInitialisation' -PropertyType 'Dword' -Value 1 -Force
                    # Max trace folder size 50 * 100 = 5GB
                    $null = New-ItemProperty -Path $fastDiagnosticTracingRegKeyPath -Name 'MaxTraceFileSize' -PropertyType 'Dword' -Value 50 -Force
                    $null = New-ItemProperty -Path $fastDiagnosticTracingRegKeyPath -Name 'MaxTraceFileCount' -PropertyType 'Dword' -Value 100 -Force
                    $null = New-ItemProperty -Path $fastDiagnosticTracingRegKeyPath -Name 'UseGeneralSwitch' -PropertyType 'Dword' -Value 1 -Force
                    $null = New-ItemProperty -Path $fastDiagnosticTracingRegKeyPath -Name 'GeneralSwitch' -PropertyType 'Dword' -Value 1 -Force
                catch
                    # ETl tracing is not critical. Info only log
                    Write-ExchangeSetupLog -Info ("An exception ocurred while trying to Configure the FAST ETL traces. Exception: " + $_.Exception.Message);
                try
                    $fastFusionRegKeyPath = 'HKLM:\SOFTWARE\Microsoft\Office Server\16.0\Search\FlightControl'
                    if (Test-Path -Path $fastFusionRegKeyPath)
                        Remove-ItemProperty -Path $fastFusionRegKeyPath -Name 'fusion_new_enabled' -Force -ErrorAction SilentlyContinue
                        Remove-ItemProperty -Path $fastFusionRegKeyPath -Name 'fusion_old_enabled' -Force -ErrorAction SilentlyContinue
                        Remove-ItemProperty -Path $fastFusionRegKeyPath -Name 'fusion_compare_outputs' -Force -ErrorAction SilentlyContinue
                catch
                    # Removing new fusion keys is not critical. Info only log
                    Write-ExchangeSetupLog -Info ("An exception ocurred while trying to remove the fast new fusion reg keys. Exception: " + $_.Exception.Message);
                $fastInstallConfigPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\Installer";
                $command = Join-Path -Path $fastInstallConfigPath -ChildPath "InstallConfig.ps1";
                $dataFolderPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\HostController\Data";
                # Remove previous SearchFoundation configuration
                &$command -action u -silent;
                try
                    if ([System.IO.Directory]::Exists($dataFolderPath))
                        [System.IO.Directory]::Delete($dataFolderPath, $true);
                catch
                    $deleteErrorMsg = "Failure cleaning up SearchFoundation Data folder. - " + $dataFolderPath + " - " + $_.Exception.Message;
                    Write-ExchangeSetupLog -Error $deleteErrorMsg;
                # Re-add the SearchFoundation configuration
                try
                    # the BasePort value MUST be kept in sync with dev\Search\src\OperatorSchema\SearchConfig.cs
                    &$command -action i -baseport 3800 -dataFolder $dataFolderPath -silent;
                catch
                    $errorMsg = "Failure configuring SearchFoundation through installconfig.ps1 - " + $_.Exception.Message;
                    Write-ExchangeSetupLog -Error $errorMsg;
                    # Clean up the failed configuration attempt.
                    &$command -action u -silent;
                    try
                        if ([System.IO.Directory]::Exists($dataFolderPath))
                            [System.IO.Directory]::Delete($dataFolderPath, $true);
                    catch
                        $deleteErrorMsg = "Failure cleaning up SearchFoundation Data folder. - " + $dataFolderPath + "
- " + $_.Exception.Message;
                        Write-ExchangeSetupLog -Error $deleteErrorMsg;
                # Set the PowerShell Snap-in's public key tokens
                try
                    $PowerShellSnapinsPath = "HKLM:\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns\";
                    $FastSnapinNames = @("EnginePSSnapin", "HostControllerPSSnapIn", "InteractionEnginePSSnapIn", "JunoPSSnapin",
"SearchCorePSSnapIn");
                    $officePublicKey = "71E9BCE111E9429C";
                    $exchangePublicKey = "31bf3856ad364e35";
                    foreach ($fastSnapinName in $FastSnapinNames)
                        $fastSnapinPath = $PowerShellSnapinsPath + $fastSnapinName;
                        $assemblyNameProperty = Get-ItemProperty -Path $fastSnapinPath -Name "AssemblyName" -ErrorAction SilentlyContinue;
                        if ($assemblyNameProperty -ne $null -and (-not [string]::IsNullOrEmpty($assemblyNameProperty.AssemblyName)))
                            $newAssemblyName = $assemblyNameProperty.AssemblyName -ireplace ($officePublicKey, $exchangePublicKey);
                            Set-ItemProperty -Path $fastSnapinPath -Name "AssemblyName" -Value $newAssemblyName;
                catch
                    # Info only log
                    Write-ExchangeSetupLog -Info ("An exception ocurred while configuring Search Foundation PowerShell Snapin. Exception: " + $_.Exception.Message);
        " was run: "System.Exception: Failure configuring SearchFoundation through installconfig.ps1 - Error occurred while configuring Search Foundation for Exchange.System.ServiceModel.EndpointNotFoundException:
Could not connect to net.tcp://exchange.domain.com:3803/Management/InteractionEngine. The connection attempt lasted for a time span of 00:00:02.0470060. TCP error code 10061: No connection could be made because the target machine actively refused it 192.168.0.0:3803.
---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 192.168.0.0:3803
   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)
   at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)
   at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
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 Microsoft.Ceres.CoreServices.Admin.INodeOperationsManagementAgent.AddNamedNode(String node)
   at Microsoft.Ceres.Exchange.PostSetup.NodeManager.DeployInterationEngineNode()
   at Microsoft.Ceres.Exchange.PostSetup.DeploymentManager.Install(String installDirectory, String dataDirectoryPath, Int32 basePort, String logFile, Boolean singleNode, String systemName, Boolean attachedMode)
   at CallSite.Target(Closure , CallSite , RuntimeType , Object , Object , Object , Object , Object , Object , Boolean )
   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
Al

Hi,
Agree with ED.
The key message is “Could not connect to net.tcp://exchange.domain.com:3803/Management/InteractionEngine.
The connection attempt lasted for a time span of 00:00:02.0470060. TCP error code 10061: No connection could be made because the target machine actively refused it 192.168.0.0:3803”
You need to check why it’s block. Any firewall or the port is listened by other processes.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Issues with setting up Exchange Server 2013

Hi All
Not sure what im doing wrong yet i am having issues with exchange server 2013.
Currently I have got general SMTP Mail flow working. as long as i log onto the local servers OWA (https://10.x.x.x/owa) i can log into a users mailbox. i have tested sending and recieving mail using this and it works.
My main issue now is with accessing the OWA externally via our website. (owa.xx.xx.au/owa) or connecting ANY Outlook to the server.
When i connect to the exchange server via outlook it asks for the password again multiple times never authenticating it then time's out and says:
" the action cannot be completed. the connection to microsoft exchange is unavailable, outlook must be online or
connected to complete this action "
then when i click on OK it goes to the General Tab and under microsoft exchange server: the name for it appears as
[email protected]
with mailbox set as:
=SMTP:[email protected]
Currantly on our DNS i have
mx= 10 mail.xx.xx.au
CNAME= autodiscover = mail.xx.xx.au
CNAME= OWA = mail.xx.xx.au
A = mail = 12.34.56.78
On our modem/router i have set one-to-one nat to our firewall IP
On our firewall i have
SMTP SAT and NAT to Exchange server
HTTPS Sat and NAT to exchange Server
HTTP Sat and Nat to exchange Server
Port 587 SAT and Nat to exchange server
pop SAT and NAt to exchange server
Im willing to bet its something stupid i have overlooked but i was wondering if anyone would be able to help me out
Regards
Sibsy

Hello,
Firstly, please follow the Shadab's suggestion to check related virtual directory settings.
Please make sure you use certificate that's created by a CA that's trusted by the client computer's operating system.
Please use get-outlookanywhere | fl cmdlet to check ExternalClientAuthenticationMethod. By default, the authentication is Negotiate.
Cara Chen
TechNet Community Support

Exchange server 2013 - cannot send / receive external emails - we can access owa -we can send/receive internal emails

Exchange server 2013 in Windows server 2012 VM
It was working fine then start the issue.
Firewall is managed externally and the last report said:
"I checked the firewall logs, which shows traffic being allowed through port 25 from 10.10.10.10 to 4.28.237.225: Log Number 116 Last Activity 2014-08-28 23:48:33 Status [accept] Src 10.10.10.10 Dst 4.28.237.225 Service SMTP Policy ID 1 Src Port 64081
Dst Port 25 While I showed one log, there were multiple log entries showing the same: traffic being accepted through port 25 from 10.10.10.10 to 4.28.237.225.
Can you verify that the mail server is set up so as to allow port 25? "
Today I was able to telnet the server from home: successfully
220 DTALL-EXCSRV002.DTC.dualtemp.com Microsoft ESMTP MAIL Service ready at Sat, 30 Aug 2014 16:31:16 -0400 ehlo 250-DTALL-EXCSRV002.DTC.dualtemp.com Hello [70.44.124.141] 250-SIZE 37748736 250-PIPELINING 250-DSN 250-ENHANCEDSTATUSCODES 250-STARTTLS 250-X-ANONYMOUSTLS
250-AUTH NTLM 250-X-EXPS GSSAPI NTLM 250-8BITMIME 250-BINARYMIME 250-CHUNKING 250 XRDST
Also the receive - send connectors seems ok
Mx record point to Microsoft protection:
dualtemp-com.mail.protection.outlook.com.
Again, OWA is able to access and send/receive emails internal but never external even no bounceback just it never arrive.
Help me please. This is my first admin chaos...

Hi,
Is there any update with your issue?
If the CAS and Mailbox servers are collocated on the same server, the SMTP Receive connection for the Transport service will listen on 2525 instead of 25. If you install the CAS and Mailbox on the same server, please make sure that port 2525 is open.
For more information about Exchange 2013 mail flow, here is a blog for your reference.
Exchange 2013 Mail Flow Demystified…Hopefully
http://blogs.technet.com/b/rischwen/archive/2013/03/13/exchange-2013-mail-flow-demystified-hopefully.aspx
Hope this can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Issues connecting Outlook 2011 for Mac to Exchange Server 2013

Could someone help me with the bellow please:
I have a Mac with outlook 2011 on it.
We have recently set up Exchange Server 2013, and all of the Windows Workstation just required the trusted root certificate to be installed and they were working.
However I have spent hours reading different forums trying to get this working on the Mac and no luck.
The auto discover does not work when setting up the exchange email, therefore I have also tried setting up manually but it still will not connect to the server.

Hi,
Please check if the links below help:
How the Autodiscover service works with Outlook for Mac 2011:
http://technet.microsoft.com/en-us/library/jj984202(v=office.14).aspx
A great tool for troubleshooting Autodiscover and Outlook 2011 for Mac connectivity issue:
http://blogs.technet.com/b/johnmak/archive/2012/04/01/a-great-tool-for-troubleshooting-autodiscover-and-outlook-2011-for-mac-connectivity-issue.aspx
Since this forum is for general questions and feedback related to Outlook for Windows, it's better to post your question to the forum for Exchange or for Mac:
Exchange forum:
http://social.technet.microsoft.com/Forums/exchange/en-US/home?category=exchangeserver
Office for Mac forum:
http://answers.microsoft.com/en-us/mac/forum/macoffice2011?tab=Threads
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly
can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Steve Fan
TechNet Community Support

Issues trying to recover failed Exchange Server 2013 in a DAG

Having several issues attempting to recover a failed Exchange Server 2013. To start out, the failed server was mounted on a virtual server using hyper-v. The virtual server failed due to some hard drive partition issues and would no longer boot. As there
really was no purpose to having Exchange on a Virtual Server I decided to rename the host to the same name as the virtual server. I reset the name in AD and proceeded to rename the server. Then made sure all the necessary things were installed and proceeded
to do a recovery installation. I neglected to properly delete the old databases belonging to that server. I simply deleted the files off the hard drive instead of doing it properly. I should mention this is a two node plus witness server installation.Now,
it seems I cannot delete the former server in either ECP or command line. I have attempted to clean up the mess with the old databases but there is one that was mounted only on the failed server that I cannot remove. It seems until I can remove that, I cannot
remove the failed server from the DAG and do a recovery install. The steps shown in the tech net articles to remove a failed database have also failed. At this point I am wondering if I should just give up on the server name and do an install on a new server
name or if someone can give me some information on how to clean up the mess, that would be better I am sure. Here is a list of the things I have tried.
https://technet.microsoft.com/en-us/library/dd876880(v=exchg.150).aspx and in this article, the item mentioned is not in ADSIedit.
http://exchangeserverpro.com/unable-remove-failed-server-dag-exchange-server-2010/
http://exchangeserverpro.com/exchange-2013-how-to-remove-dag-member/ This
article describes one of the problems I am having but the solution is not there.
Thanks to any and all who can offer advice.
Ronald C. Pope

Thank you for your answer. Running that command results in the following:
[PS] C:\Windows\system32>Remove-MailboxDatabase "Mailbox Database 0939719168"
This mailbox database contains one or more mailboxes, mailbox plans, archive mailboxes, public folder mailboxes or
arbitration mailboxes. To get a list of all mailboxes in this database, run the command Get-Mailbox -Database"Mailbox Database 0939719168". To get a list of all mailbox plans in this database, run the command Get-MailboxPlan. To get a list of
archive mailboxes in this database, run the command Get-Mailbox -Database "Mailbox Database 0939719168" -Archive. To get a list of all
public folder mailboxes in this database, run the command Get-Mailbox -Database "Mailbox Database 0939719168" -PublicFolder. To get a
list of all arbitration mailboxes in this database, run the command Get-Mailbox -Database "Mailbox Database 0939719168" -Arbitration.
To disable a non-arbitration mailbox so that you can delete the mailbox database, run the command Disable-Mailbox
<Mailbox ID>. To disable an archive mailbox so you can delete the mailbox database, run the command Disable-Mailbox
<Mailbox ID> -Archive. To disable a public folder mailbox so that you can delete the mailbox database, run the command
Disable-Mailbox <Mailbox ID> -PublicFolder. Arbitration mailboxes should be moved to another server; to do this, run
the command New-MoveRequest <parameters>. If this is the last server in the organization, run the command
Disable-Mailbox <Mailbox ID> -Arbitration -DisableLastArbitrationMailboxAllowed to disable the arbitration mailbox.
Mailbox plans should be moved to another server; to do this, run the command Set-MailboxPlan <MailboxPlan ID>
-Database "Mailbox Database 0939719168".
    + CategoryInfo          : InvalidOperation: (Mailbox Database 0939719168:DatabaseIdParameter) [Remove-MailboxDatab
   ase], AssociatedUserMailboxExistException
    + FullyQualifiedErrorId : [Server=EX01,RequestId=69b60793-fc4f-4dac-beb9-8c9afe381a36,TimeStamp=1/26/2015 6:28:34
   PM] 2BA41E0C,Microsoft.Exchange.Management.SystemConfigurationTasks.RemoveMailboxDatabase
    + PSComputerName        : ex01.<domain>com
I was able to disable the one mailbox that was listed for the database. I got the following error when attempting the command Get-Mailbox -Database"Mailbox Database 0939719168"
[PS] C:\Windows\system32>Get-MailboxPlan Database "Mailbox Database 0939719168"
Get-MailboxPlan : The term 'Get-MailboxPlan' is not recognized as the name of a cmdlet, function, script file, or
operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
again.
At line:1 char:1
+ Get-MailboxPlan Database "Mailbox Database 0939719168"
+ ~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Get-MailboxPlan:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
the public folder and archive switch simply return a command prompt leading me to believe that there are no public or archive boxes on that database.
Ron

Exchange Server 2013: Outook Clients and OWA keeps on disconnecting/connecting every 5-10 mins

We have a new exchange server 2013 installed but also has exchange 2007 up.
MX records are now pointing to the new exchange server, all were working ok after DNS records were changed but after the weekend it Outlook clients and OWA keeps on disconnecting and reconnecting from exchange.
Exchange 2013 CU6
Anybody else experienced the same?

hi Jheycie,
can you please check if you have .local and .com (different internal and external domain)
almost similar thread.. it worked for me
http://social.technet.microsoft.com/Forums/office/en-US/cc7d2300-0e1f-499f-a8f1-97f84687b6cc/emails-stuck-in-outlook-have-to-restart-transport-service?forum=exchangesvrgeneral
http://social.technet.microsoft.com/Forums/office/en-US/9b9bf607-f882-4f73-a7b2-611ace3f3115/users-unable-to-connect-to-exchange-unless-they-close-and-reopen-outlook?forum=exchangesvrgeneral
MARK AS USEFUL/ANSWER IF IT DID
Thanks
Happiness Always
Jatin

Exchange Server 2013 Service Pack Upgrade - Outlook connectivity issue

Hi,
After upgrading to Exchange Server 2013 service pack 1, we are unable to connect via Outlook 2010 or Outlook 2013. Outlook Web Access is working fine though. We have followed all the instructions, and have applied Outlook upgrades, but the issue remain the
same. Outlook was working fine before the upgrade.
Have we missed out something. I would highly appreciate if someone can help out? I'm not sure if this is the known issue as I can't seem to find anything on the internet.
Already applied the transport fix.
Thanks in advance!

Hi,
According to your description, your Outlook 2010 and Outlook 2013 come across the connectivity issue.
To narrow down the issue, I’d like to recommend the following troubleshooting:
1. Check if the issue happens on all Outlook users
2. Check the Outlook Anywhere connectivity by using ExRCA:
https://testconnectivity.microsoft.com/
Additionally, MAPI over HTTP is only supported when you use Outlook 2013 sp1 and Exchange 2013 sp1 at the same time. Since the issue also happens on Outlook 2010 client, we can firstly try the above troubleshooting.
If you have any question , please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Exchange server 2013 Installation issue

Dear Experts,
Thanks in advance...
I am not able to Install Exchange server 2013. I have tried my best to Install but not success. Please find my system configuration.
Dell Laptop Intel I5 1.7 GHZ
RAM -8GB
Vmware workstation 9.
Steps I followed
Created a VM inside Vmware and Installed windows 2012 Std. Edition
Memory assigned to VM is 1 GB
All prerequisites completed and tried to Install Exchange server 2013 SP1
During installation it asked me to select the role to Install and I selected Mailbox server role and CAS
Exchange setup process started at 3 P.M till 9 P.M setup was not finished finally setup process halt and I got the error setup could not completed .
Please find the logs for your reference.............
04/13/2015 08:41:02.0303] [0] **********************************************
[04/13/2015 08:41:02.0303] [0] Starting Microsoft Exchange Server 2013 Service Pack 1 Setup
[04/13/2015 08:41:02.0303] [0] **********************************************
[04/13/2015 08:41:02.0303] [0] Local time zone: (UTC+05:30) Chennai, Kolkata, Mumbai, New Delhi.
[04/13/2015 08:41:02.0303] [0] Operating system version: Microsoft Windows NT 6.2.9200.0.
[04/13/2015 08:41:02.0328] [0] Setup version: 15.0.847.32.
[04/13/2015 08:41:02.0328] [0] Logged on user: WIN-4D2C2JMF5R1\Administrator.
[04/13/2015 08:41:02.0336] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[04/13/2015 08:41:02.0368] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[04/13/2015 08:41:02.0600] [0] Command Line Parameter Name='sourcedir', Value='C:\Softwares\Exch-13'.
[04/13/2015 08:41:02.0615] [0] Command Line Parameter Name='mode', Value='Install'.
[04/13/2015 08:41:02.0632] [0] RuntimeAssembly was started with the following command: '/sourcedir:C:\Softwares\Exch-13 /mode:Install'.
[04/13/2015 08:41:02.0632] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
[04/13/2015 08:41:05.0504] [0] Finished loading screen CheckForUpdatesPage.
[04/13/2015 08:41:13.0567] [0] Starting file's copying...
[04/13/2015 08:41:13.0599] [0] Setup copy files from 'C:\Softwares\Exch-13\Setup\ServerRoles\Common' to 'C:\Windows\Temp\ExchangeSetup'
[04/13/2015 08:41:13.0794] [0] Finished loading screen CopyFilesPage.
[04/13/2015 08:41:15.0033] [0] Disk space required: 1826493368 bytes.
[04/13/2015 08:41:15.0033] [0] Disk space available: 46620041216 bytes.
[04/13/2015 08:42:55.0484] [0] Finished loading screen InitializingSetupPage.
[04/13/2015 08:42:55.0484] [0] File's copying finished.
[04/13/2015 08:43:13.0922] [0] Setup is choosing the domain controller to use
[04/13/2015 08:43:28.0885] [0] Setup is choosing a local domain controller...
[04/13/2015 08:43:32.0221] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: Active Directory server
is not available. Error message: Active directory response: The LDAP server is unavailable.
See the Exchange setup log for more information on this error.
[04/13/2015 08:43:32.0335] [0] [ERROR] Active Directory server
is not available. Error message: Active directory response: The LDAP server is unavailable.
[04/13/2015 08:43:32.0366] [0] [ERROR] The LDAP server is unavailable.
[04/13/2015 08:43:32.0366] [0] Setup will use the domain controller ''.
[04/13/2015 08:43:32.0366] [0] Setup will use the global catalog ''.
[04/13/2015 08:43:32.0596] [0] No Exchange configuration container was found for the organization. Message: 'Active Directory server
is not available. Error message: Active directory response: The LDAP server is unavailable.'.
[04/13/2015 08:43:32.0707] [0] The following roles have been unpacked:
[04/13/2015 08:43:32.0721] [0] The following datacenter roles are unpacked:
[04/13/2015 08:43:32.0739] [0] The following roles are installed:
[04/13/2015 08:43:32.0739] [0] The local server does not have any Exchange files installed.
[04/13/2015 08:43:32.0834] [0] Server Name=WIN-4D2C2JMF5R1
[04/13/2015 08:43:33.0032] [0] Setup will use the path 'C:\Softwares\Exch-13' for installing Exchange.
[04/13/2015 08:43:33.0084] [0] The installation mode is set to: 'Install'.
[04/13/2015 08:43:51.0460] [0] Exchange organization name is required for this mode.
[04/13/2015 08:43:51.0460] [0] Active Directory Initialization status : 'False'.
[04/13/2015 08:43:51.0472] [0] Schema Update Required Status : 'False'.
[04/13/2015 08:43:51.0472] [0] Organization Configuration Update Required Status : 'False'.
[04/13/2015 08:43:51.0472] [0] Domain Configuration Update Required Status : 'False'.
[04/13/2015 08:43:51.0536] [0] Applying default role selection state
[04/13/2015 08:43:51.0565] [0] Setup is determining what organization-level operations to perform.
[04/13/2015 08:43:51.0565] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
[04/13/2015 08:43:51.0565] [0] InstallModeDataHandler has 0 DataHandlers
[04/13/2015 08:43:51.0565] [0] RootDataHandler has 1 DataHandlers
[04/13/2015 08:43:52.0848] [0] CurrentResult launcherbase.maincore:90: 0
[04/13/2015 08:43:53.0067] [0] Finished loading screen WelcomePage.
[04/13/2015 08:44:06.0654] [0] Finished loading screen EULAPage.
[04/13/2015 08:44:10.0679] [0] Finished loading screen RecommendedSettingsPage.
[04/13/2015 08:44:13.0814] [0] Setup is determining what organization-level operations to perform.
[04/13/2015 08:44:13.0814] [0] Because the value was specified, setup is setting the argument OrganizationName to the value First Organization.
[04/13/2015 08:44:13.0814] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
[04/13/2015 08:44:13.0844] [0] InstallModeDataHandler has 8 DataHandlers
[04/13/2015 08:44:14.0048] [0] Finished loading screen RoleSelectionPage.
[04/13/2015 08:44:18.0619] [0] Setup is determining what organization-level operations to perform.
[04/13/2015 08:44:18.0619] [0] Because the value was specified, setup is setting the argument OrganizationName to the value First Organization.
[04/13/2015 08:44:18.0619] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
[04/13/2015 08:44:18.0632] [0] InstallModeDataHandler has 9 DataHandlers
[04/13/2015 08:44:18.0632] [0] Setup is determining what organization-level operations to perform.
[04/13/2015 08:44:18.0632] [0] Because the value was specified, setup is setting the argument OrganizationName to the value First Organization.
[04/13/2015 08:44:18.0632] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
[04/13/2015 08:44:18.0632] [0] InstallModeDataHandler has 10 DataHandlers
[04/13/2015 08:44:18.0632] [0] Setup is determining what organization-level operations to perform.
[04/13/2015 08:44:18.0632] [0] Because the value was specified, setup is setting the argument OrganizationName to the value First Organization.
[04/13/2015 08:44:18.0632] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
[04/13/2015 08:44:18.0632] [0] InstallModeDataHandler has 11 DataHandlers
[04/13/2015 08:44:18.0648] [0] Setup is determining what organization-level operations to perform.
[04/13/2015 08:44:18.0648] [0] Because the value was specified, setup is setting the argument OrganizationName to the value First Organization.
[04/13/2015 08:44:18.0648] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
[04/13/2015 08:44:18.0648] [0] InstallModeDataHandler has 12 DataHandlers
[04/13/2015 08:44:22.0644] [0] Setup is determining what organization-level operations to perform.
[04/13/2015 08:44:22.0644] [0] Because the value was specified, setup is setting the argument OrganizationName to the value First Organization.
[04/13/2015 08:44:22.0644] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
[04/13/2015 08:44:22.0644] [0] InstallModeDataHandler has 13 DataHandlers
[04/13/2015 08:44:22.0644] [0] Setup is determining what organization-level operations to perform.
[04/13/2015 08:44:22.0644] [0] Because the value was specified, setup is setting the argument OrganizationName to the value First Organization.
[04/13/2015 08:44:22.0644] [0] Setup will run from path 'C:\Windows\Temp\ExchangeSetup'.
[04/13/2015 08:44:22.0656] [0] InstallModeDataHandler has 14 DataHandlers
[04/13/2015 08:46:00.0423] [0] Finished loading screen InstallationSpaceAndLocationPage.
[04/13/2015 08:46:28.0427] [0] Finished loading screen ExchangeOrganizationPage.
[04/13/2015 08:46:30.0221] [0] Finished loading screen
Regards
Biswajeet

Hi,
Please find the DC Health check report.
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\Users\Administrator>dcdiag
Directory Server Diagnosis
Performing initial setup:
   Trying to find home server...
   Home Server = EX-13
   * Identified AD Forest.
   Done gathering initial info.
Doing initial required tests
   Testing server: Default-First-Site-Name\EX-13
      Starting test: Connectivity
         ......................... EX-13 passed test Connectivity
Doing primary tests
   Testing server: Default-First-Site-Name\EX-13
      Starting test: Advertising
         ......................... EX-13 passed test Advertising
      Starting test: FrsEvent
         ......................... EX-13 passed test FrsEvent
      Starting test: DFSREvent
         ......................... EX-13 passed test DFSREvent
      Starting test: SysVolCheck
         ......................... EX-13 passed test SysVolCheck
      Starting test: KccEvent
         ......................... EX-13 passed test KccEvent
      Starting test: KnowsOfRoleHolders
         ......................... EX-13 passed test KnowsOfRoleHolders
      Starting test: MachineAccount
         ......................... EX-13 passed test MachineAccount
      Starting test: NCSecDesc
         ......................... EX-13 passed test NCSecDesc
      Starting test: NetLogons
         ......................... EX-13 passed test NetLogons
      Starting test: ObjectsReplicated
         ......................... EX-13 passed test ObjectsReplicated
      Starting test: Replications
         ......................... EX-13 passed test Replications
      Starting test: RidManager
         ......................... EX-13 passed test RidManager
      Starting test: Services
         ......................... EX-13 passed test Services
      Starting test: SystemLog
         An error event occurred. EventID: 0x0000272C
            Time Generated: 04/14/2015   18:01:37
            Event String:
            DCOM was unable to communicate with the computer fec0:0:0:ffff::1 us
ing any of the configured protocols; requested by PID      4e4 (C:\Windows\syste
m32\dcdiag.exe).
         An error event occurred. EventID: 0x0000272C
            Time Generated: 04/14/2015   18:01:49
            Event String:
            DCOM was unable to communicate with the computer fec0:0:0:ffff::2 us
ing any of the configured protocols; requested by PID      4e4 (C:\Windows\syste
m32\dcdiag.exe).
         An error event occurred. EventID: 0x0000272C
            Time Generated: 04/14/2015   18:02:02
            Event String:
            DCOM was unable to communicate with the computer fec0:0:0:ffff::3 us
ing any of the configured protocols; requested by PID      4e4 (C:\Windows\syste
m32\dcdiag.exe).
         ......................... EX-13 failed test SystemLog
      Starting test: VerifyReferences
         ......................... EX-13 passed test VerifyReferences
   Running partition tests on : ForestDnsZones
      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test
         CrossRefValidation
   Running partition tests on : DomainDnsZones
      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test
         CrossRefValidation
   Running partition tests on : Schema
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
   Running partition tests on : Configuration
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
   Running partition tests on : NETMAGIC
      Starting test: CheckSDRefDom
         ......................... NETMAGIC passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... NETMAGIC passed test CrossRefValidation
   Running enterprise tests on : NETMAGIC.IN
      Starting test: LocatorCheck
         ......................... NETMAGIC.IN passed test LocatorCheck
      Starting test: Intersite
         ......................... NETMAGIC.IN passed test Intersite
Regards
Biswajeet

Exchange server 2013 send and received issue

Hi Support,
I have install Exchange Server 2013 with server 2012 ( my domain not resisted but mail send & received in local for practice then live ) but few days back some changes in dns and ecp and mail stop sending and receiving. how to verify my exchange server
2013 working fine. Please give the step check perpoes.

dear Pardeep, you said it was working fine then you did some DNS changes..
i would suggest you best troubleshooting step is to go to exrca.com and perform the tests and from there we take it up.
Secondly you can verify your config from the below link.
http://www.techieshelp.com/exchange-2013-step-by-step-configuration/
in DNS you need to make sure you have atleast MX and A record done for your server having email services installed.
for ECP... i would we would take this later lets check the mail sending and receiving first. use the above links
MARK AS USEFUL/ANSWER IF IT DID
Thanks
Happiness Always
Jatin

Exchange Server 2013 to 2010 mailbox proxy is not working

I have exchange server 2013 and exchange server 2010 in co-exist. I have 3 cas server and 3 mbx server 2013 on windows server 2012 standard, 2 hub/cas server and 2 mbx server 2010 on windows server 2008 r2. when I try to access owa of exchange server 2010
mailbox using exchange 2013 url, I am getting the error as "something went wrong. sorry, we can't get that information right now, please try again later. If the problem continues please contact your helpdesk"
Vishal C. Kalal | MCITP: Exchange 2010-2007 | Windows Server 2008

Hi,
To narrow down the cause, I recommend the following troubleshooting:
Check if the issue happens on all users.
Try to directly login OWA 2010 and check if it works well.
Check the IIS log on CAS 2013 server and find the error related to OWA.
Thanks,
Angela Shi
TechNet Community Support

Exchange Server 2013 SP1 Standard: Installation failing can't progress

I'm trying to install Exchange Server 2013 and I keep getting this error and I am unable to progress, I can't find any support on the issue and frankly I don't want to/can't afford to spend $500 to ask Microsoft for technical support (what kind of racket
do they think they're running?).
The error message:
Error:
The following error was generated when "$error.Clear();
New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
" was run: "The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.".
Yet, I see no PushNotifications virtual directory or anything remotely related to that on IIS or in the inetpub folders and files. If I try to resume the set-up after this error I get:
Error:
The following error was generated when "$error.Clear();
New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
" was run: "The AD configuration for virtual directory 'PushNotifications' already exists in 'CN=PushNotifications (Exchange Back End),CN=HTTP,CN=Protocols,CN=SVR02,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OFFICE,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=OFFICE,DC=local', please remove this AD configuration manually.
Parameter name: VirtualDirectoryName".
And I have to remove this config using ADSI Edit, which just returns me to the first error.

1. Prodution
2. Just 1 DC for 1 site.
3. Setup.EXE
4. Matches SP1 version numbers
5. That's just what was made available to me via MSPP, the installer doesn't see any updates?
6. Here is the log files:
[03/23/2015 22:06:52.0940] [1] Setup failed previously while performing the action Install. Looking for the failed task with ID ClientAccessComponent___75f8c93d15314369983d33ec0742e189.
[03/23/2015 22:06:52.0941] [1] 131 tasks were found to run.
[03/23/2015 22:06:52.0941] [1] Processing component 'Client Access Configuration' (Configuring Mailbox role: Client Access service.).
[03/23/2015 22:06:52.0941] [1] Executing:
New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
[03/23/2015 22:06:52.0955] [2] Active Directory session settings for 'New-PushNotificationsVirtualDirectory' are: View Entire Forest: 'True', Configuration Domain Controller: 'SVR01.OFFICE.local', Preferred Global Catalog: 'SVR01.OFFICE.local', Preferred Domain Controllers: '{ SVR01.OFFICE.local }'
[03/23/2015 22:06:52.0956] [2] User specified parameters: -Role:'Mailbox' -DomainController:'SVR01.OFFICE.local'
[03/23/2015 22:06:52.0956] [2] Beginning processing New-PushNotificationsVirtualDirectory
[03/23/2015 22:06:52.0999] [2] Searching objects "SVR02.OFFICE.local" of type "Server" under the root "$null".
[03/23/2015 22:06:53.0066] [2] Previous operation run on domain controller 'SVR01.OFFICE.local'.
[03/23/2015 22:06:53.0068] [2] Processing object "SVR02\PushNotifications".
[03/23/2015 22:06:56.0763] [2] The properties changed on the object '' (CN=PushNotifications (Exchange Back End),CN=HTTP,CN=Protocols,CN=SVR02,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OFFICE,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=OFFICE,DC=local) are: "{ MetabasePath[msExchMetabasePath]='IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications', AuthenticationMethodFlags[msExchInternalAuthenticationMethods]='Ntlm, WindowsIntegrated', AuthenticationMethodFlags[msExchExternalAuthenticationMethods]='Ntlm, WindowsIntegrated', Id[distinguishedName]='SVR02\PushNotifications (Exchange Back End)', InternalAuthenticationMethods[msExchInternalAuthenticationMethods]={ 'Ntlm', 'WindowsIntegrated' }, ExternalAuthenticationMethods[msExchExternalAuthenticationMethods]={ 'Ntlm', 'WindowsIntegrated' }, OrganizationId[msExchOURoot, msExchCU]='' }".
[03/23/2015 22:06:56.0764] [2] Saving object "SVR02\PushNotifications (Exchange Back End)" of type "ADPushNotificationsVirtualDirectory" and state "New".
[03/23/2015 22:06:57.0073] [2] Previous operation run on domain controller 'SVR01.OFFICE.local'.
[03/23/2015 22:06:57.0587] [2] [ERROR] The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
[03/23/2015 22:06:57.0591] [2] [ERROR] Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
Line number: 630
Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
[03/23/2015 22:06:58.0378] [2] [ERROR] The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
[03/23/2015 22:06:58.0378] [2] [ERROR] Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
Line number: 630
Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
[03/23/2015 22:06:58.0386] [2] Ending processing New-PushNotificationsVirtualDirectory
[03/23/2015 22:06:58.0388] [1] The following 1 error(s) occurred during task execution:
[03/23/2015 22:06:58.0388] [1] 0. ErrorRecord: The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
[03/23/2015 22:06:58.0389] [1] 0. ErrorRecord: System.InvalidOperationException: The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it. ---> System.Runtime.InteropServices.COMException: Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
Line number: 630
Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
at Microsoft.Web.Administration.Interop.IAppHostAdminManager.GetAdminSection(String bstrSectionName, String bstrPath)
at Microsoft.Web.Administration.Configuration.GetSectionInternal(ConfigurationSection section, String sectionPath, String locationPath)
at Microsoft.Exchange.Management.SystemConfigurationTasks.ExchangeServiceVDirHelper.SetAuthModule(Boolean EnableModule, Boolean isChildVDirApplication, String moduleName, String moduleType, ExchangeVirtualDirectory advdir)
at Microsoft.Exchange.Management.SystemConfigurationTasks.ExchangeServiceVDirHelper.SetLiveIdBasicAuthModule(Boolean EnableModule, Boolean isChildVDirApplication, ADExchangeServiceVirtualDirectory advdir)
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeServiceVirtualDirectory`1.InternalProcessComplete()
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewPushNotificationsVirtualDirectory.InternalProcessComplete()
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()
[03/23/2015 22:06:58.0389] [1] [ERROR] The following error was generated when "$error.Clear();
New-PushNotificationsVirtualDirectory -Role Mailbox -DomainController $RoleDomainController;
" was run: "The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.".
[03/23/2015 22:06:58.0389] [1] [ERROR] The Active Directory object for virtual directory 'IIS://SVR02.OFFICE.local/W3SVC/24/ROOT/PushNotifications' on 'SVR02' could not be created. This might be because the object already exists in Active Directory. Remove the object from Active Directory, then re-create it.
[03/23/2015 22:06:58.0389] [1] [ERROR] Filename: \\?\C:\Windows\system32\inetsrv\config\applicationHost.config
Line number: 630
Error: Can not log on locally to C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PushNotifications as user OFFICE\Administrator with virtual directory password
[03/23/2015 22:06:58.0390] [1] [ERROR-REFERENCE] Id=ClientAccessComponent___75f8c93d15314369983d33ec0742e189 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[03/23/2015 22:06:58.0390] [1] Setup is stopping now because of one or more critical errors.
[03/23/2015 22:06:58.0390] [1] Finished executing component tasks.
[03/23/2015 22:06:58.0406] [1] Ending processing Install-ClientAccessRole
It says it can not log on with the supplied details, but the account is an Administrator account with full privileges so I can't see why this would be the case.

Exchange Server 2013 OWA Related Issue

Similar Messages

Maybe you are looking for