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

Problem witch upgrade or clear instalation Exchange 2013 cu22 on SP1

$
0
0

Hello, i try upgrade Exchange 2013 SP1 to CU22 or CU21 and instalations end ever with error:

Error:
Installing product L:\Install\cu22\exchangeserver.msi failed. Fatal error during installation. Error code is 1603. Last error reported by the MSI package is 'Error reading from file: L:\Install\cu22\Setup\ServerRoles\ClientAccess\Sync\Bin\Microsoft.Exchange.AirSyncHandler.dll.   Verify that the file exists and that you can access it.'.

Same is on clear installed other server with this domain. This domain is only single name "domain" without fqdn. Domain have 2 site with dc 2008 R2 in Headquarter and 2012 R2 with hosting there is Exchange server on 2012 R2 too.

Instalation run domain administrator acc and dll file from error is in instalation folder. Tested on CU22 and CU21 .. and independ on location install folder.. C:\install or other. Server have all updates.


Disabling TLS 1.0 results in NO active sync mobile devices (Phones and ipads) connecting.

$
0
0

We are trying to come into compliance by disabling TLS 1.0 in our Exchange 2013 CU21 environment. When we update registry keys and restart the single server the mobile devices do not update. We use up to date iphones, ipads and android devices.

Thank you

Kevin Davis

Exchange 2013 cu 22 - in add remove program view cu 20 :)

$
0
0

is a small 'bug' ?

I installed the last exchnage 2013 cu, the 22, but in add remove programs view cu 20 


oasis in my heart

Exchange 2013 transition from 2010

$
0
0

I have installed a single 2013 CAS server and a single 2013 MB server in my testlab. I already have a 2010 cas server, Hub Server, and mb server in the testlab. After installing 2013, and redirecting my mail to the 2013 CAS server, mail is flowing to the 2013 MB server. In the Queue Viewer for the 2013 DB server, I see the message with the next hop being SITE:mysite; Version:14, Delivery Type is SMTP Relay to Mailbox Delivery Group; Status is Retry;

Error:

"Wednesday, June 19, 2013 12:11:19 PM" "[{LRT=6/19/2013 12:10:19 PM};{LED=451 4.4.0 Primary target IP address responded with: ""451 5.7.3 Cannot achieve Exchange Server authentication."" Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was (IP of 2010 Hub:25};{FQDN=2010 Hub Server FQDN};{IP=2010 Hub Server}]"
Submission Undefined Ready 0  

I am at a loss on how to correct this. Is there a jedi master out there that can help?

On premise Exchange server to Office 365

$
0
0

HI All,

I have an on-premise exchange server 2010 sp1 installed recently for one of our internal application notification because the application doesn't support o365 mail bursting to internal as well as external domains.

How we can send notification emails to internal and external domains from the on-premise exchange through office365.

Could you please help me with this.

Thank you

Exchange Server 2013 CU7 Installation Issue

$
0
0
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


New Exchange 2016 installation cannot access EAC

$
0
0

I have 1 Exchange 2013 server which is being replaced with 2016 CU12. After successfully completing the installation wizard I tried to login to the ECP but I get HTTP 500 error. I can login to the 2013 ECP and see the new server.

I've reset the virtual directories and reset forms authentication but that does have any affect on it.

New Edge Transport server - Exchange 2013

$
0
0

All,

I would like to replace my existing Edge Transport server that is running Win2008R2 to a Win2016. From what I'm reading, all I need to do is follow the ClonedConfig instructions as shown here - https://docs.microsoft.com/en-us/exchange/configure-edge-transport-server-using-cloned-configuration-exchange-2013-help. So my plan is to follow those instructions, and once it's up and running, just remove the role from the Win2008R2 server? Is there anything else I need to do to make sure it's removed properly? Any advice, comments are helpful

Thanks,

-S


How to migrate Zimbra to Exchange 2013?

$
0
0

Dear All,

Last year, we migrated Exchange 2010 to Zimbra and found it was difficult to handle.

So we want to move back to Exchange 2013. Exchange 2013 and Zimbra may co-exist in our organization.

We will deploy two Exchange Server,CAS+Mailbox.

We are considering if put Exchange as the smarthost.

Anyone has idea?

Besides, is there any wonderful migration tool?

Xiu


Hey, I am back

Troubleshoot autodiscover

$
0
0

Hi,

We use Exchange 2013 standard Version 15.0 ‎(Build 1395.4).

We do not have a routable upn domain name suffix. We have a domain.local in AD(Mailbox address policies and .com accepted domains are there). This is a set up I am newly introduced to. So do not have much information.

I have added just a domain.com suffix in ad and changed the suffix for one user to test.

When trying the command below.

Test-OutlookWebServices -identity: j.doe@domain.com –MailboxCredential (Get-Credential)

I get the below error.

RunspaceId          : f9d17969-ab1e-4d49-8f36-aed73697497b
Source              : EXCH01.domain.local
ServiceEndpoint     : autodiscover.domain.ae
Scenario            : AutoDiscoverOutlookProvider
ScenarioDescription : Autodiscover: Outlook Provider
Result              : Failure
Latency             : 0
Error               : System.Net.WebException: Unable to connect to the remote server --->
                      System.Net.Sockets.SocketException: A connection attempt failed because the connected party did
                      not properly respond after a period of time, or established connection failed because connected
                      host has failed to respond publicip:443
                         at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
                         at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket
                      s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult,
                      Exception& exception)
                         --- End of inner exception stack trace ---
                         at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
                         at System.Net.HttpWebRequest.GetRequestStream()
                         at
                      Microsoft.Exchange.Management.SystemConfigurationTasks.ServiceValidatorBase.InternalInvoke()
                         at Microsoft.Exchange.Management.SystemConfigurationTasks.ServiceValidatorBase.Invoke()
Verbose             : [2019-02-28 07:55:13Z] Autodiscover connecting to
                      'https://autodiscover.domain.ae/Autodiscover/Autodiscover.xml'.
                      [2019-02-28 07:55:13Z] Test account: test Password: ******
                      [2019-02-28 07:55:34Z] Autodiscover response:
                      System.Net.WebException: Unable to connect to the remote server --->
                      System.Net.Sockets.SocketException: A connection attempt failed because the connected party did
                      not properly respond after a period of time, or established connection failed because connected
                      host has failed to respond publicip:443
                         at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
                         at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket
                      s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult,
                      Exception& exception)
                         --- End of inner exception stack trace ---
                         at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
                         at System.Net.HttpWebRequest.GetRequestStream()
                         at
                      Microsoft.Exchange.Management.SystemConfigurationTasks.ServiceValidatorBase.InternalInvoke()
                         at Microsoft.Exchange.Management.SystemConfigurationTasks.ServiceValidatorBase.Invoke()
MonitoringEventId   : 6001

Skipped testing Exchange Web Services because the Autodiscover step failed.

Skipped testing Availability Service because the Autodiscover step failed.

Kindly help me troubleshoot this more.

I am posting in this forum, if not suitable, please move to required forum.

Update from CU12 to CU21

$
0
0

Hi all!

I currently in Exchange 2013 CU12 and would like to update to the latest CU21.

Is it dangerous to update directly (without updating previously to any other CU)? Do you suggest any other roadmap?

Thanks!

SomoIT.net

Not showing exchange databases in ECP

$
0
0

Hi,

I am not able to see my exchange databases in exchange console. Earlier I have migrated my exchange mailboxes from one exchange databaseto another database which was successful. Then I tried to remove older mailbox database which was not successful & after that I found the issue in ECP that I was not seeing databases.

While if I am going through exchange shell & running a command Get-mailboxdatabase -server <server name> then it is showing the new databases. but if I am running command Get-mailboxdatabase then it is showing below error.

Please help me to come out of it.




대구오피 [uuzoa2.com ] 〔유유닷컴〕 밤문화후기

In place hold after reinstallation

$
0
0

After Exchange reinstallation, my inplace hold disappeared. 
I can't find it with get-mailboxsearch

However, mailboxes still have GUID under inplaceholds property. I can see it here.

get-mailbox my_mailbox | ft InPlaceHolds

If user purges mail items from recycle bin, I can still find these items purged folder. Does it mean that in place hold works?

Should I recreate inplace hold and reassign it to users?

Supported Migration Patch from Exchnage 2010 to 2013

$
0
0

Hi.

We run a pair of exchange 2010 servers running on Windows Server 2008R2 and these need upgrading by the end of the year.

Does anyone have experience of this and can confirm whether upgrading exchange in-place folled by an upgrade of the OS to 2012R2 is a supported scenario and whether ther are any major issues to be aware of?


Supported Migration Patch from Exchange 2010 to 2013

$
0
0

Hi.

We run a pair of exchange 2010 servers running on Windows Server 2008R2 and these need upgrading by the end of the year.

Does anyone have experience of this and can confirm whether upgrading exchange in-place followed by an upgrade of the OS to 2012R2 is a supported scenario and whether ther are any major issues to be aware of?


Unable to download Hotfix KB2619234, For Exchange 2013 installation on Win 2008 R2

$
0
0

Trying to download Hotfix KB2619234 which is pre-req for exchnage 2013 installation on Win 2008 R2.

After providing the e-mail address and request hotfix....received error...The system is currently unavialable, Please try back later r contact support if you want immediate assitance.Seems like the HF is not available for download now, Any other option to get this HF?

Thanks,

Praveen

Transfer to R2

$
0
0

Hi,

We need to transfer our Exchange 2013 Server to a Windows 2016 or Windows 2012 R2 Hyper-V Virtual Machine from a Windows 2012 Std Hyper-v Virtual Machine. Is it possible?

Thanks.

Exchange CU 22 crashes during installation

$
0
0
During the Transport section of the installation the update crashed.  Exchange is up and running however after I started all of the services.  Any suggestions on how I should proceed?

Logon failure - Account Currently Disabled Event 4625 | W3WP.EXE | SYSTEM

$
0
0
I've been receiving failed login attempts, no IP no username or any useful information
The server has Exchange 2013  and IIS installed. Mailbox Server (MBX) Information Store component is installed on this server.
The Exchange server is working well.

After thorough investigation , it is found that an application pool is causing this .We found this by executing the command "appcmd list wps" and matching the output with the process ID in the event log.It is found that app pool "MSExchangeServicesAppPool" is the culprit causing this failed login events.

Kindly let us know what could be the issue in the configuration that is causing this issue.

Below is the event


An account failed to log on.

Subject:

      Security ID:            SYSTEM

      Account Name:           SERVER-EXCHANGE$

      Account Domain:         DOMAIN

      Logon ID:         0x3E7

Logon Type:             3

Account For Which Logon Failed:

      Security ID:            NULL SID

      Account Name:          

      Account Domain:        

Failure Information:

      Failure Reason:         Account currently disabled.

      Status:                 0xC000006E

      Sub Status:       0xC0000072

Process Information:

      Caller Process ID:      0x38cc

      Caller Process Name:    C:\Windows\System32\inetsrv\w3wp.exe

Network Information:

      Workstation Name: SERVER-EXCHANGE

      Source Network Address: -

      Source Port:            -

Detailed Authentication Information:

      Logon Process:          Authz  

      Authentication Package: Kerberos

      Transited Services:     -
Viewing all 7129 articles
Browse latest View live


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