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

EX2013 CU13 Setup crashes

$
0
0

Currently running EX2013 CU11. Downloaded EX2013 CU13. When I launch Setup, shortly after I select the default "Check for Updates" and click "Next", Setup closes with no error messages. This is logged in Application log:

Log Name:      Application
Source:        MSExchange Common
Date:          7/19/2016 3:30:37 PM
Event ID:      4999
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      computer.domain.local
Description:
Watson report about to be sent for process id: 24404, with parameters: E12IIS, c-RTL-AMD64, 15.00.1210.002, ExSetupUI, M.E.Setup.AcquireLanguagePack, M.E.S.A.LanguagePackXmlHelper.GetDownloadFileInfoFromXml, System.ArgumentException, a588, 15.00.1210.002.
ErrorReportingEnabled: True

Log Name:      Application
Source:        Windows Error Reporting
Date:          7/19/2016 3:30:38 PM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      computer.domain.local
Description:
Fault bucket 126585538899, type 5
Event Name: E12IIS
Response: Not available
Cab Id: 0

Problem signature:
P1: c-RTL-AMD64
P2: 15.00.1210.002
P3: ExSetupUI
P4: M.E.Setup.AcquireLanguagePack
P5: M.E.S.A.LanguagePackXmlHelper.GetDownloadFileInfoFromXml
P6: System.ArgumentException
P7: a588
P8: 15.00.1210.002
P9:
P10:

Attached files:
C:\ExchangeSetupLogs\ExchangeSetupWatson.log
C:\ExchangeSetupLogs\ExchangeSetup.msilog
C:\Users\crescent\AppData\Local\Temp\7f84a5e7-c77c-4c31-85c7-1a91951f7b10\report.txt
C:\Users\crescent\AppData\Local\Temp\7f84a5e7-c77c-4c31-85c7-1a91951f7b10\report.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_c-RTL-AMD64_56526c72eec815b072d8559d2e5921ebdf3191_75d3c5af

Analysis symbol:
Rechecking for solution: 0
Report Id: a681aa11-4def-11e6-9438-00155d01de00
Report Status: 0
Hashed bucket: cf32413a69388d6fded3fa3ae89f6ae2

Log Name:      Application
Source:        Windows Error Reporting
Date:          7/19/2016 3:30:38 PM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      AVSI-EX2013.AVSIAV
Description:
Fault bucket 126585538899, type 5
Event Name: E12IIS
Response: Not available
Cab Id: 0

Problem signature:
P1: c-RTL-AMD64
P2: 15.00.1210.002
P3: ExSetupUI
P4: M.E.Setup.AcquireLanguagePack
P5: M.E.S.A.LanguagePackXmlHelper.GetDownloadFileInfoFromXml
P6: System.ArgumentException
P7: a588
P8: 15.00.1210.002
P9:
P10:

Attached files:
C:\ExchangeSetupLogs\ExchangeSetupWatson.log
C:\ExchangeSetupLogs\ExchangeSetup.msilog
C:\Users\crescent\AppData\Local\Temp\7f84a5e7-c77c-4c31-85c7-1a91951f7b10\report.txt
C:\Users\crescent\AppData\Local\Temp\7f84a5e7-c77c-4c31-85c7-1a91951f7b10\report.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_c-RTL-AMD64_56526c72eec815b072d8559d2e5921ebdf3191_75d3c5af

Analysis symbol:
Rechecking for solution: 0
Report Id: a681aa11-4def-11e6-9438-00155d01de00
Report Status: 0
Hashed bucket: cf32413a69388d6fded3fa3ae89f6ae2

The 2 ExchangeSetupLog files only have data from past installs. The folder in %temp% doesn't exist. None of the files are available in the WER folder. So all I have to go by is the Application log events.

If I elect not to check for updates, Setup proceeds.

If it's not an easy fix I'll proceed without checking for updates, but any idea what I should be looking for?

TIA


Error 8207 when trying to install SP3 on Exchange2010

$
0
0

Upgrade stacks always at the same point and gives the following error. cannot proceed. Can you assist?

Failed Error: The following error was generated when "$error.Clear(); install-ExchangeSchema -LdapFileName ($roleInstallPath + "Setup\Data\"+$RoleSchemaPrefix+ "schema3.ldf") " was run: "There was an error while running 'ldifde.exe' to import the schema file 'C:\Windows\Temp\ExchangeSetup\Setup\Data\PostExchange2003_schema3.ldf'. The error code is: 8207. More details can be found in the error file: 'C:\Users\administrator\AppData\Local\Temp\2\ldif.err'". There was an error while running 'ldifde.exe' to import the schema file 'C:\Windows\Temp\ExchangeSetup\Setup\Data\PostExchange2003_schema3.ldf'.The error code is: 8207. More details can be found in the error file: 'C:\Users\administrator\AppData\Local\Temp\2\ldif.err' Click here for help...

I have two email domains say A.com and B.com in one exchange organization, need to hide contacts synchronized from domain C from Domain A

$
0
0
I have two email domains say  A.com and B.com in one exchange organization, I am synchronizing contacts from another company say C.com. In this case only A.com email users should see C.com, but B.com users should not see the synchronized contacts. How to achieve it?

Exchange 2013 CAS WNLB and DAG on existing single CAS and Mailbox

$
0
0

Hi,

Exchange 2013 single CAS and Single Mailbox server is running in virtualization in Hyper-V. I am planning to install another instance of CAS server on VM and configure WNLB and same for Mailbox instance on VM and create DAG server.

Kindly guide that it is possible to install and configure WNLB service on existing CAS and same allow create DAG on existing Mailbox server.

Thanks

Office 365 migration data transfer

$
0
0

Hi,

We have an Exchange 2010 environment with an Exchange 2013 hybrid server over an ExpressRoute connection. Migrations to Office 365 is running smoothly, albeit a bit slow, but in general it's working well.

My question is around the type of data that is being sent between the hybrid server and O365 during the migration process. We have been asked to report on ExpressRoute utilisation, but all our network monitoring tools as well as those of the ISP shows no significant line utilisation during migration. Based on data volume (GB's) on the ExpressRoute we can see that data is traveling the correct way, but apart from the normal working hours spike, we cannot see any data.

Does the migration use a different file type or protocol for migrations, or is the packets just so small that it doesn't show significant data?

Thomas


Exchange 2013 SSL Certs

$
0
0
My exchange Servers have lost all SSL Certs, We are in testing so we are just using self signed certs, My first exchange server is giving me error on the WEB Management Service and wont allow it to start, the error i find is

Microsoft Exchange could not load the certificate with thumbprint of E53D989B8A448375E903A0AB7CCC823A42B0F076 from the personal store on the local computer. This certificate was configured for authentication with other Exchange servers. Mail flow to other Exchange servers could be affected by this error. If the certificate with this thumbprint still exists in the personal store, run Enable-ExchangeCertificate E53D989B8A448375E903A0AB7CCC823A42B0F076 -Services SMTP to resolve the issue. If the certificate does not exist in the personal store, restore it from backup by using the Import-ExchangeCertificate cmdlet, or create a new certificate for the FQDN or the server enabled for SMTP by running the following command: New-ExchangeCertificate -DomainName serverfqdn -Services SMTP. Meanwhile, the certificate with thumbprint 0186F48794A78EA5E7CE3F9351B3E394D1AF63A7 is being used. I have recreated self signed certs in the EAC with the server FQDN as well as the externam FQDN, but this did not solve my issue, I am very new to exchange and am learing as i go so any help with this issue would be much appriciated.

Thanks


Devin Berard I.T Support Renfrew Victoria Hospital, Renfrew ON berardd@renfrewhosp.com

Change the Internal URL for Exchange server 2010.

$
0
0

Hi Guys,

For the Migration of the Exchange server 2010 , I need to change the Internal URL for exchange services.

Current Setup: EX2010: CAS

                         EX2010B: Mailbox, HubTransport

At the Moment my Internal URL are like this.

https://svv-ex2010.domain.com/owa
https://svv-ex2010.domain.com/ecp
https://svv-ex2010.domain.com/OAB
https://svv-ex2010.domain.com/Micorsoft-Server-ActiveSync
https://svv-ex2010.domain.com/Autodiscover/Autodiscover.xml

and i am Planning to have more than 2 Client access server and since this is the migration of Exchange 2010 server. I want to change the Internal URL's with

https://mail.domain.com/owa
https://mail.domain.com/ecp
https://mail.domain.com/OAB
https://mail.domain.com/Micorsoft-Server-ActiveSync
https://mail.domain.com/Autodiscover/Autodiscover.xml

So for that I have created the DNS A Records with the Current Client Access ServerIP :192.168.1.10

I have also made the DNS-Resolve query to to check if i get the result or not and here is the Output.


PS C:\Users\test_admin> Resolve-DnsName imail

Name                                           Type   TTL   Section    IPAddress
----                                           ----   ---   -------    ---------
mail.domain.com                                A      3600  Answer     192.168.1.10(Current Ex )
mail.domain.com                                A      3600  Answer     192.168.1.11 (In future)


so i think i am ready with the New Namespace. (mail.domain.com) and later i can assign this Name spaces to all the services.

But my Problem comes at the Point of SSL Certificate. For Internal Clients we are using Self Signed Certificate with Private CA.we have Internal AD CS Services.

the Current SSL certificate which is being used at the moment doesn't have themail.domain.com as SAN Name.

so I am bit confused with Whole Process, how should i start here.

As far as i understood i need to re-request the certificate and then use the new Certificate with new SAN Name: mail.domain.com.

and then change the Internal URL of the Exchange server.

Guys,Please Help me and give me some tips , My problem is really complicated for me. i dont want to disturb the running workflow, therefore i am trying to prepared for all small issue.

it will be really nice if you guys can give me some tips about requesting the New Certificate with Correct SAN name and change the Internal URL for the migration.





2010 -> 2013 Public Folder migration failed - Property Expression isn't valid

$
0
0

We just migrated from 2003 to 2010, and now on to 2013.  I have Exchange 2013 CU3 installed, and all mailboxes moved.  When trying to move the public folders, I'm getting an error about DataValidationException.  Property expression <PF Name with spaces> isn't valid......

Many articles refer to a mail-enabled public folder with spaces can't have spaces in the alias.  This is NOT a mail-enabled public folder, so there isn't an alias that I can find.

Any ideas?

Thanks!

--Kent


Exchange Migration Project

$
0
0

Good Day,

We are experiencing some issues with a migration we are doing, as such I figured I would post here with hopes that some of you can assist me with some of the problems we are having. In an effort to provide some insight we are attempting to migrate from a 2010 (2 CAS, 2 MBX) environment, to that of a 2013 (2 CAS, 2 MBX). the 2010 environment has been inherited, and was built before my time.

To date I have built out the new environment (2013) to where it co-exists within the existing infrastructure, I have migrated all settings and policies associated within the infrastructure to the new environment, all of this has been done without incident. I have configured mail flow to allow for the sending and receiving of mail from a mailbox within the 2013 environment. The problem we appear to be having is with proxying back to the legacy environment when pointed to the new (the modification of local hosts file to point to new exchange servers). It doesn’t work, I cannot connect to a mailbox that lives in the 2010 environment when pointed to the new…it continually prompts for credentials.

Another issue we appear to be having is this, I built a new outlook (2013) profile and pointed to the mailbox that lives on the 2013 servers, while it connects it is not without incident….it consistently prompts for credentials even though it shows as connected, I can cancel out of this and remain connected I’m just wondering why this happens (side note, I understand why it would prompt for credentials as I’m not logged on to the computer as that user, I don’t understand why it continues to prompt).

Regarding the proxy issue, I reached out to Microsoft Support and got some guidance (some of which I don’t fully understand, hence part of the reason I am writing this). What we found was that the legacy environment was built with a cas array. From what I am told in order for the proxying back to the legacy environment when a client is pointed to the new the cas array will need to be severed. I have never worked with cas array’s throughout my career, given that I am told that breaking this will sever connectivity to some of our legacy clients (outlook 2007 / 2010) I am a little intimidated by this.

Has anyone here encountered anything like this?, if so what steps did you take to resolve? 

Exchange 2013 upgrade failed on un-resolvable MSExchangeADTopology error

$
0
0

We have two domain controller in the building, that are all our servers.

I have exchange 2013 CU6 installed on one domain controller.

when I tried to upgrade to CU12, failed on the error below. After that, exchange server cannot start at all.

Had to use server bare metal recovery to get server back.

Tried again with CU13, failed again with same error.

can any expert help on get this upgrade?

thank you so much for your help.

BTW, there was Anti-virus program on the server when I installed CU12. After it failed, I uninstalled anti-virus app. Failed again on 2nd try with CU13.

Error:
The following error was generated when “$error.Clear();
if (!(get-service MSExchangeADTopology* | where {$_.name -eq “MSExchangeADTopology”}))
{
Install-ADTopologyService
}
else
{
Update-ServiceExecutable -ServiceName:MSExchangeADTopology -Executable:”Microsoft.Exchange.Directory.TopologyService.exe”
invoke-expression “sc.exe config MSExchangeADTopology depend= NetTcpPortSharing”
Uninstall-TopologyService
}
” was run: “System.Management.Automation.CommandNotFoundException: The term ‘sc.exe’ 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 System.Management.Automation.CommandDiscovery.LookupCommandInfo(String commandName, CommandTypes commandTypes, SearchResolutionOptions searchResolutionOptions, CommandOrigin commandOrigin, ExecutionContext context)
at System.Management.Automation.CommandDiscovery.LookupCommandProcessor(String commandName, CommandOrigin commandOrigin, Nullable`1 useLocalScope)
at System.Management.Automation.ExecutionContext.CreateCommand(String command, Boolean dotSource)
at System.Management.Automation.PipelineOps.AddCommand(PipelineProcessor pipe, CommandParameterInternal[] commandElements, CommandBaseAst commandBaseAst, CommandRedirection[] redirections, ExecutionContext context)
at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)
at System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame frame)
at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)”.


The local domain needs to be prepared using Setup /PrepareDomain before server roles can be installed

$
0
0

Hello Everyone,

I've been installing Exchange servers since Exchange 5.5. I'm now installing Exchange 2013 with SP1 that will coexist with one Exchange 2010 SP3 server. I'm installing it on 2012 R2 Enterprise Edition. There is a root domain and one child domain. The Exchange Server is in the child domain.  Even though I've run the .\setup PrepareSchema, AD and domain and all were successful I still get the message below when running Exchange setup. If I look at what /preparedomain does it seems like it has done what is needed. I've run the /prepareschema, /preparead and /preparealldomains in the root domain & have even run /preparedomain over and over in the child domain. Like I said everytime I run these they are successful. Oh and my account belongs to all the right groups needed to run these. Any ideas would be appreciated!

The local domain needs to be prepared using Setup /PrepareDomain before server roles can be installed.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DomainPrepRequired.aspx


Exchange 2013 DAG - Complete failover fail

$
0
0

OS: Windows 2012r2

Exchange 2013

I have setup a DAG group between 2 servers. I am able to failover the database onto the other server without any issues.

The issue I am having is complete server failover which does not seem to work. When the primary server is shutdown our email clients lose connection.

The Test-ReplicationHealth tests have passed everything on both servers.

Do you have any pointers?

Imap and pop3 outlook connectivity issue.

$
0
0

Team,

I am having a problem while configuring pop3 setting on user desktop. Its giving my error for outgoing smtp server connection.

Please help to fixup.

Exchange 2013 CAS not proxying connections to Exchange 2010 during coexistence

$
0
0

Hello all,

for the second time, I am performing an Exchange 2010 to 2013 migration. For the second time, coexistence is not working as it should.

I have followed the migration assistant at https://technet.microsoft.com/en-us/exdeploy2013 to the T and it did not work. I did a reinstall of Exchange 2013 and followed other guides with no avail.

The environment is Exchange 2010 SP3 along side of Exchange 2013 SP1 (I will spare reasons for not going beyond SP1).

The most notable symptom of this problem is that when I access OWA on the 2013 CAS, I sign in using 2010 Credentials. I am then taken to https://mail.domain.com/owa/auth.owa -- where it hangs on a blank white page in Google Chrome, or the "This page can't be displayed" in IE.

OutlookAnywhere IS configured on Exchange 2010 in this scenario.

Does anyone have any suggestions or tips on where to look for something wrong?

Download link for Exchange server 2013

$
0
0

Hi Guys,

I am in the process to migrate from exchange 2010 to exchange 2013 and I have downloaded the Exchange server from

https://www.microsoft.com/en-us/evalcenter/evaluate-exchange-server-2013

and after that i have also done the active directory Preparation for the Exchange 2013 and all went fine without any Problem.

but when i check the Object version and schema upper range i got this Values.

Exchange 2013 RTM
15.00.0516.0321513713236

and i think this Value belongs to the Exchange 2013 RTM but there is Already exchnage server 2013 CU 12 on the Microsoft.

so i am confused with RTM version, Will i have to again update the Exchange server with CU 12 or i have downloaded the Wrong Version.

can someone please enlighten me,

thanks


Installing CU on Exchange 2013

$
0
0
I have a single Exchange 2013-  one server, no DAG
If I am installing CU 13 after hours, is it necessary to put the server in maintenance mode first?
Or can I just perform the update without maintenance mode?
thanks.

Migrate old data to archive

$
0
0

Hi guys,

Scenario question

Current environment Exchange 2013 with large mailboxes and very old emails

New environment Exchange 2016 with Default MRM Policy / Personal 1 year move to archive policy

1) Is that policy configured on user, databaser or server level?

2) Will the old emails migrated to an in-place archive since it was originally received in the old environment for over 1 year ago or will the 1 year trigger from when it was migrated into the new environment?

3) is it possible to migrate emails newer than one year to the primary mailbox and emails older than 1 year directly into the in-place archive? (if the policy makes this separation one might not have to filter this migration, everything goes into the primary mailbox)

thanks!

Move Request not happening in EMS-CAS Servers but working fine in EMS-MBX Servers

$
0
0

Hi Folks,

I am doing a Exchange implementation project from Exch 2010 to Exch 2013. Few days before the move-request command working properly on EMS-CAS Servers, now it showing this error if we execute the New-MoveRequest command

Error

The call to 'net.tcp://cas01.domain.local/Microsoft.Exchange.MailboxReplicationService' failed because no
service was listening on the specified endpoint. Error details: Could not connect to
net.tcp://cas01.domain.local/Microsoft.Exchange.MailboxReplicationService. The connection attempt lasted for a
time span of 00:00:03.0711355. TCP error code 10061: No connection could be made because the target machine actively
refused it 192.168.5.102:808.  --> No connection could be made because the target machine actively refused it
192.168.5.102:808
    + CategoryInfo          : NotSpecified: (:) [New-MoveRequest], EndpointNotFoundTransientException
    + FullyQualifiedErrorId : [Server=CAS01,RequestId=97edb4ac-93b6-405a-896f-37b112c2d1f9,TimeStamp=7/27/2016 1
   2:21:31 PM] [FailureCategory=Cmdlet-EndpointNotFoundTransientException] ED63AA8,Microsoft.Exchange.Management.Reci
  pientTasks.NewMoveRequest
    + PSComputerName        : cas01.domain.local

Generally, From EMS we can execute commands related to both CAS and MBX servers. 

But i execute the Move-Request command in MBX Servers its working fine now. How to troubleshoot. Kindly help me.


Sabarish B

Security alert certificate message about connecting to old exchange 2010 when using exchange 2013

$
0
0

Hello All,

 

This question is related to a previous question I had posted. We have recently migrated from Exchange 2010 to Exchange 2013 and most things are working correctly. Before removing the Exchange 2010 servers from our environment, I turn them off so I can see if there are any issues. The main issue, which is now solved, was distribution lists trying to use the old Exchange 2010 to send emails. The second issue, which is not affecting mail flow, is that periodically our users will see a security alert asking them about a certificate and if they want to proceed. Now, the issue is not them getting the security alert but that the security alert is referring to one of our 2010 servers which it shouldn’t be used at this point.

Our pre-migration Exchange environment consisted of two Exchange 2010 servers, Eastend and DREastend, in a DAG. Our post-migration Exchange environment consists of one Exchange 2013 server with the Exchange 2010 DAG removed and both Exchange 2010 servers running but not participating in the sending or receiving of email.

My question is why are people getting the security message about connecting to one of the old Exchange 2010 servers when they shouldn’t be involved in the sending of emails?

The security alert message that we are seeing is:

Sorry for the long post.

Thank you,

Andy


Andy Richards

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


Viewing all 7129 articles
Browse latest View live


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