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

Exchange 2013 CU11 Setup Failing

$
0
0

Hi Everyone

I need some help, I have a problem installing Exchange 2013 CU11 in my current environment.

I have run PrepareAD and PrepareSchema from a Domain Controller and all successful. I can see the RangeUpper Value changed to Exchange 2013 value.

Here is the error:

[ERROR] Can't find the "Managed Availability Servers" universal security group by using its well-known GUID cf2e5202-8599-4a98-9232-056fc704cc8b.  Make sure that you have run Setup /PrepareAD.

So here is what I have done so far to troubleshoot:

 

I notice when PrepareAD was run a new Managed Availability group was created with a 1 appended at the end.

I have turned off AV, firewalls. I have created a VM on a totally different cluster.

I have verified AD replication is fine, I can create accounts or run PrepareAD and see the changes immediately.

I have turned off IPv6 as they are off on the DC’s. I have forced AD replication.

I have used 3 different accounts, all with permissions to setup Exchange and it all fails at the same point.

I created a brand new VM without using a template and the same problem.

I have tried CU11 and CU13. I am at a loss here, the logs just give the error above. I cannot see anything else.

I can remove the servers using ADSIEdit and from the machine remove exchange and start again and just re-produce the error.

Any assistance will be great.

Thanks


Migration Ex2010 --> EX2013 // Internal Mailflow stucks

$
0
0

I am going to migrate from existing single Server Exchange 2010 Server (Mailbox,Hubtransport,Clientaccess) to two Exchange 2013 Server (Mailbox,Hubtransport).

I installed the two Exchange 2013 Server and configure a DAG. Then i installed the CU13. After that i moved a testmailbox from Exchange 2010 to a database on the DAG (Exchange 2013).

My problem is, that i can´t send mail from the Exchange 2013 Mailbox to a Mailbox on Exchange 2010. The reverse way works

I can also send mails via Telnet in both ways.

If i send a mail from Exchange 2013 to Exchange 2010 Mailbox, i get this error:

Remote Server at ExchangeServer2010" (172.16.0.248) returned '400 4.4.7 Message delayed'
Remote Server at ExchangeServer2010.intern.domain.de (172.16.0.248) returned '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 172.16.0.248:25'

So then i googled this error, but did not find the a solution for my Problem. I think it´s a Problem with the existing receive connectors. Because the Exchange 2010 organization is not designed from myself, i did not know exactly why this Settings were chosen.

Receive connectors on Exchange 2010:

Name             : Default EXCHANGE2010
IsValid          : True
Bindings         : {:::25, 0.0.0.0:25}
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
PermissionGroups : AnonymousUsers, ExchangeUsers, ExchangeServers, ExchangeLegacyServers

Name             : Client EXCHANGE2010
IsValid          : True
Bindings         : {:::587, 0.0.0.0:587}
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
PermissionGroups : AnonymousUsers, ExchangeUsers

Name             : Internet
IsValid          : True
Bindings         : {10.0.0.4:25}
AuthMechanism    : None
PermissionGroups : AnonymousUsers, ExchangeUsers

Name             : intern
IsValid          : True
Bindings         : {172.16.0.248:25}
AuthMechanism    : ExternalAuthoritative
PermissionGroups : AnonymousUsers, ExchangeUsers, ExchangeServers

Any assistance would be appreciated. Thanks!

Ews:The remote server returned an error: (401) Unauthorized in Exchange 2016/2010 co-existence

$
0
0

Hi Team,

I have deployed Exchange 2016 with 2010 in co-existence. Everything works fine: outlook,owa,activesync,autodiscover, etc. However, EWS seems to not work at all. I have already followed: Client connectivity in Exchange 2016 co-existence env blog. The Namespace is pointing to Exchange 2016. However, still the issue persists. I get credential prompts while opening the ews url: https://namespace.domain.com/ews/exchange.asmx. Also, using a ews editor, i get this: The request failed. The remote server returned an error: (401) Unauthorized.

So, I tried to connect to the ip and fqdn of the individual exchange 2016 server instead of the namespace. It works as expected. Also, ews editor works. What could be the issue? Please suggest.

Setup new server that won't respond to Autodiscover requests?

$
0
0

Hi, all! Existing environment is Exchange 2013 CU13 DAG, two sites, each hosting their own active mailbox databases.  HA is managed right now thru DNS round-robin: mail & autodiscover records in DNS point to a server at both sites.  Config works perfectly and has been for years.

I'll be setting up a new Exchange 2013 server for the purpose of hosting inactive (but not ready to be deleted) mailboxes and in-place archive mailboxes for our existing infrastructure.  I have a couple questions re: the configuration---

First, the new server should not respond to any autodiscover requests.  We won't be adding any static DNS records for mail or autodiscover pointers in our DNS, so presumably that should prevent it, correct?

Second, since some of the mailboxes will still need to be logged into (from local OWA or Outlook), do I need to install our SSL cert on that new server?  We don't use wildcard certs, so we'll need to regen it, obviously, if installation is required.

Third, I know I need to prevent the other databases from failing over to this server (it's virtual and doesn't have the juice to operate as an online server hosting our current databases).  Are there any other settings I need to change to prevent it from behaving as a "normal" DAG member?  It's databases need to be able to fail over to the other onsite Ex2013 server, but the databases hosting our active user base cannot fail over to it.

Thoughts and suggestions welcome!

Steve in Reno

Disconnected Mailbox vanish after CU13 Update

$
0
0

Hello

i have made an Update of an Exchange 2013 CU11 DAG MultiRole Cluster to CU13 - Everything works perfect but after the Update i see that disconnected Mailbox are not available any more. i didn't see them in the GUI and also not in the Shell.

The are not soft deleted. I deactivate them 3-4 days before the update. 

Is the update responsible for this behaviour and is this normal ?

Thanks for help

skykitchen

Exchange 2013 DAG Multiple Sites - Office 365 Hybrid

$
0
0

Hello

i have the following scenario: 2 x MultiRole Exchange 2013 CU13 Server in One Site (Site A) und 2 x MultiRole Exchange Server in Site B.

In the near feature wie want to replace the Servers in Site B with Office 365 and want to Build up an Full Hybrid Szenario because the Servers in Site A should stay. 

Wenn i build up the hybrid szenario is there any kind of special configuration? I want to migrate all users from the Exchange Server in Site B to Office 365. 

Thx 4 your advice

skykitchen

Exchange 2013 Public Folders with O365 Hybrid

$
0
0

I am a little confused at which path I should go down with regards to giving both the online mail users and the on-premise mail users access to my on-premise Exhcange 2013 public folders.

At the moment I have migrated some but not all users over to O365. The users that have been migrated cannot see my Public Folders. I'm not sure if my Public Folders are classified as Legacy or not?

Do I need to 'mail-enable' them or are they ok the way they have been setup now?

I have run: Set-OrganizationConfig -PublicFoldersEnabled Remote -RemotePublicFolderMailboxes PF-Mailbox

As well as the Sync-MailPublicFolders.ps1 script.


But users still cannot see the public folders in Exchange Online. I have two calendars and a list of contacts that my users access on the Public Folders.

Thank you in advance.



Exchange Server : DNS entries in AD and External DNS

$
0
0

Hello Team,

need to know about the DNS entries should be created in AD and external DNS for the incoming mail flow.

My AD domain is ABC.local and Mail domain is ABCD.com , so i added ABCD.com as accepted domain in exchange 2013 and created email address policy according to this. now i am able to send emails to external email id but not receiving any mails from external email id's.

i have created a DNS zone in my AD (ABC.local) in the name of ABCD.com and added exchange server a host (A) record to resolve mail.abcd.com internally. and created MX record pointing to that host entry (inside ABCD.com dns zone)

please let me know what are other steps i need to establish external mail flow?


Client connectivity in Exchange 2010 and 2016 co-existence

$
0
0

Hi Team,

i am in a transition of exchange 2010 to 2016.

I am currently looking at the client connectivity. I already followed: https://blogs.technet.microsoft.com/exchange/2015/10/26/client-connectivity-in-an-exchange-2016-coexistence-environment-with-exchange-2010/

I know that for the Activesync and Outlook anywhere which is currently published externally and loadbalanced to the E2K10 environment, has to be changed to the E2K16 environment as per the article.

However, i am more concerned about the internal outlook and other URL connectivities.

Should i repoint everything to the Exchange 2016 as well for internal connections? If yes, what should be done for the CAS array since there is none in Exchange 2016, should the cas array continue to point to the 2010 env or is it point to the E2K16 loadbalancer env. Please shed some light.

Exchange 2016 / Office 365 not displaying all Room Mailboxes

$
0
0

Hi All,

Got a strange one, I have created 300 Room Mailboxes in 365/EXOnline and I can only see the first 30. What have I missed?

Thanks,

Ray


Ray :)

Error while installing exchange server 2013 CU13 on CAS server

$
0
0

Dear All,

I ran the exchnage 2013 CU13 on my Exchange, 2013 CAS server,the installation went smoothly but at the final stage i am receiving the below error,can someone shed some light on this.

full text of the error.

Error:
The following error was generated when "$error.Clear(); 
          $dependentAssemblyGeneratorExePath = [System.IO.Path]::Combine($RoleInstallPath, "bin", "DependentAssemblyGenerator.exe");
          $exchangeBinPath = [System.IO.Path]::Combine($RoleInstallPath, "bin");
          $frontEndPath = [System.IO.Path]::Combine($RoleInstallPath, "FrontEnd");
          $clientAccessPath = [System.IO.Path]::Combine($RoleInstallPath, "ClientAccess");
          $sharedWebConfig = [System.IO.Path]::Combine($RoleInstallPath, "FrontEnd", "HttpProxy", "SharedWebConfig.config");

          $a = &"$dependentAssemblyGeneratorExePath" -exchangePath "$exchangeBinPath" -exchangePath "$frontEndPath" -exchangePath "$clientAccessPath" -configFile "$sharedWebConfig";
          $a | % { if ($_.Length > 0) { Write-ExchangeSetupLog -Info "$_.ToString()" } }
          Start-SetupProcess -Name "iisreset" -Args "/timeout:120"
        " was run: "Microsoft.Exchange.Configuration.Tasks.TaskException: Process execution failed with exit code 1062.
   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   at Microsoft.Exchange.Management.Tasks.RunProcessBase.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Regards

JAck


TechGUy,System Administrator.


Does the September 2016 exchange security patches apply to 2013 cu7?

$
0
0

https://technet.microsoft.com/library/security/MS16-108?f=255&MSPPError=-2147217396

The security bulletin specifically mentions SP1, cu12 and 13, but not cu7 (and others). Does this mean the excluded cu's are not vulnerable?

Exchange Server 2013 Sizing for 500 User Mailbox

$
0
0

Hi Everyone,

Any one can help Exchange Server Sizing for 500 user mailbox.

I have a plan to deploy on single location.

Any response are really appreciate.

Regards,

Lin

exchange 2013 _ outlook connectivity broken _ after I modified the internal FQDN of Outlook Anywhere

$
0
0

Hi All,

We are planning to migrate 2010 environment to 2013 environment, therefore I was testing the behaviours in my lab.

I'm facing this issue in lab, however it is important to fix it, so I understand the concequences properly.

When I installed 2013 server , with the default configuration, outlook worked perfectly fine with autodiscover (domain joined client machine)

Later I changed the OutlookAnywhere internal hostname(default it was server fqdn) and External hostname(default it was blank) and immediately after this change , outlook connectivity stopped working, my outlook started saying this error "The connection to Microsoft Exchange is unavailable, outlook must be online or connected to complete this action" 

Therefore I changed the "Outlookanywhere" settings back to how it was before , however the error message continue to occur and I could not fix it.

I also tried to configure outlook manually , using the servers FQDN, still the same error happening.

what I wrote is the absolute things I did so far, Please advise is there any mistake I have done here.


Exchange 2013 CU2 will not install, Exchange is now in an unuseable state.

$
0
0

I have downloaded Exchange 2013 CU2 and attempted to install it from a local drive.  Exchange 2013 is installed on a Server 2012 Standard VM in Hyper-V.  I ran the two following commands before trying to install

setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms

Upon trying to run the installer, I recieve the following error.

Error:
The following error was generated when "$error.Clear();
                    & $RoleBinPath\ServiceControl.ps1 EnableServices Critical
                " was run: "AuthorizationManager check failed.".

During my first install attept, the error was on step 4 of 15. I have tried to rerun the setup with no luck.  I noticed the installer leaves all the Exchange services disabled, as well as winmgmt, remoteregistry, w3svc, iisadmin.  These four services are the critical services the errors refer to.  I have verified my execution policy is correct

PS C:\Windows\system32> Get-ExecutionPolicy -list

                                                      Scope                                             ExecutionPolicy
                                                      -----                                             ---------------
                                              MachinePolicy                                                Unrestricted
                                                 UserPolicy                                                   Undefined
                                                    Process                                                   Undefined
                                                CurrentUser                                                   Undefined
                                               LocalMachine                                                RemoteSigned

Upon trying to rerun the setup, I have ran the following commands in order to start the critical services manually

Get-Service-namewinmgmt,remoteregistry,w3svc,iisadmin|set-service-startuptypeautomatic

Get-Service-namewinmgmt,remoteregistry,w3svc,iisadmin|Start-Service

No matter what I do, the Exchange 2013 CU2 installer seems to fail.  I'd appreciate any possible help with this.

Thanks,

Chris

To add to what I posted, I also have the following error in the event log.

[07/22/2013 13:57:01.0279] [1] Executing:
                    & $RoleBinPath\ServiceControl.ps1 EnableServices Critical
                
[07/22/2013 13:57:01.0373] [1] The following 1 error(s) occurred during task execution:
[07/22/2013 13:57:01.0373] [1] 0.  ErrorRecord: AuthorizationManager check failed.
[07/22/2013
13:57:01.0373] [1] 0.  ErrorRecord:
System.Management.Automation.PSSecurityException: AuthorizationManager
check failed. ---> System.Runtime.InteropServices.COMException: The
service cannot be started, either because it is disabled or because it
has no enabled devices associated with it. (Exception from HRESULT:
0x80070422)
   at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
   at System.Management.ManagementScope.InitializeGuts(Object o)
   at System.Management.ManagementScope.Initialize()
   at System.Management.ManagementObject.Initialize(Boolean getObject)
   at System.Management.ManagementObject.Get()
   at System.Management.Automation.PsUtils.GetParentProcess(Process current)
   at System.Management.Automation.SecuritySupport.GetExecutionPolicy(String shellId, ExecutionPolicyScope scope)
   at System.Management.Automation.SecuritySupport.GetExecutionPolicy(String shellId)
   at Microsoft.PowerShell.PSAuthorizationManager.CheckPolicy(ExternalScriptInfo script, PSHost host, Exception& reason)
  
at Microsoft.PowerShell.PSAuthorizationManager.ShouldRun(CommandInfo
commandInfo, CommandOrigin origin, PSHost host, Exception& reason)
  
at
System.Management.Automation.AuthorizationManager.ShouldRunInternal(CommandInfo
commandInfo, CommandOrigin origin, PSHost host)
   --- End of inner exception stack trace ---
  
at
System.Management.Automation.AuthorizationManager.ShouldRunInternal(CommandInfo
commandInfo, CommandOrigin origin, PSHost host)
   at
System.Management.Automation.CommandDiscovery.ShouldRun(ExecutionContext
context, PSHost host, CommandInfo commandInfo, CommandOrigin
commandOrigin)
   at
System.Management.Automation.CommandDiscovery.LookupCommandProcessor(CommandInfo
commandInfo, CommandOrigin commandOrigin, Nullable`1 useLocalScope,
SessionStateInternal sessionState)
   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)
[07/22/2013 13:57:01.0373] [1] [ERROR] The following error was generated when "$error.Clear();
                    & $RoleBinPath\ServiceControl.ps1 EnableServices Critical
                " was run: "AuthorizationManager check failed.".
[07/22/2013 13:57:01.0373] [1] [ERROR] AuthorizationManager check failed.
[07/22/2013
13:57:01.0373] [1] [ERROR] The service cannot be started, either
because it is disabled or because it has no enabled devices associated
with it. (Exception from HRESULT: 0x80070422)
[07/22/2013
13:57:01.0388] [1] [ERROR-REFERENCE]
Id=AllRolesMidFileCopyComponent___af0f15afe35c4e7cba121e546f405214
Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[07/22/2013 13:57:01.0388] [1] Setup is stopping now because of one or more critical errors.
[07/22/2013 13:57:01.0388] [1] Finished executing component tasks.
[07/22/2013 13:57:01.0435] [1] Ending processing Start-MidFileCopy
[07/22/2013 13:58:09.0121] [0] End of Setup
[07/22/2013 13:58:09.0121] [0] **********************************************

I also have these two errors in event viewer that keep occuring. 

Event 2280, IIS-W3SVC-WP

The Module DLL C:\Program Files\Microsoft\Exchange Server\V15\Bin\kerbauth.dll failed to load.  The data is the error.

Event 2300, IIS-W3SVC-WP

The
worker process cannot access the CLR configuration file at 'C:\Program
Files\Microsoft\Exchange
Server\V15\bin\GenericAppPoolConfigWithGCServerEnabledFalse.config'. 
Verify that the file exists and that the worker process has read access
to the file.




Azure AD connect not picking one user to sync to Office 365

$
0
0

There is one user which we have created some days before and not able to sync to office 365.

There is no error anywhere i can see for that user also didnt find any duplicate proxy address and also i can see that user in metaverse search as well?

i have run forcesync after updating its phone no and the last name but nothing got picked up by any connector.

This user is on the same OU where rest of synced o365 users are.

Can anyone suggest where can i dig into?

Thanks

Weird Build Number\CU reporting from Exchange 2013

$
0
0

We are trying to install Exchange 2016 but we get the error indicating that an Exchange 2013 Server is not CU10 or higher.  All Exchange 2013 servers have had CU14 applied.  When I run Get-ExchangeServer on the particular box it is complaining about (MBCAS) it returns the correct build number.  Here is when it gets weird.  When I run it from any of the other servers I get a CU8 build number.

Here is Get-ExchangeServer on the MBCAS:

Name                : BAAL            AdminDisplayVersion : Version 15.0 (Build 1236.3)
Name                : CTHULHU      AdminDisplayVersion : Version 15.0 (Build 1236.3)
Name                : BEELZEBUB   AdminDisplayVersion : Version 15.0 (Build 1236.3)
Name                : MBCAS         AdminDisplayVersion : Version 15.0 (Build 1236.3)

Here is Get-ExchangeServer on BAAL:

Name                : BAAL            AdminDisplayVersion : Version 15.0 (Build 1236.3)
Name                : BEELZEBUB   AdminDisplayVersion : Version 15.0 (Build 1236.3)
Name                : CTHULHU      AdminDisplayVersion : Version 15.0 (Build 1236.3)
Name                : MBCAS          AdminDisplayVersion : Version 15.0 (Build 1076.9)


Here is the error when we try to install 2016:

All Exchange 2013 servers in the organization must have Exchange 2013 Cumulative Update 10 or later installed. The following servers don't meet this requirement: MBCAS.

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

We also tried this:

C:\about>$ExchangeServers = Get-ExchangeServer  | Sort-Object Name
C:\about>ForEach  ($Server in $ExchangeServers)
 {
Invoke-Command -ComputerName $Server.Name -ScriptBlock {Get-Command  Exsetup.exe | ForEach-Object {$_.FileversionInfo
}}
}

15.00.1236.003   15.00.1236.003   C:\Program Files\Microsoft\Exchange Ser... AMZMBCAS
15.00.1236.003   15.00.1236.003   C:\Program Files\Microsoft\Exchange Ser... BAAL
15.00.1236.003   15.00.1236.003   C:\Program Files\Microsoft\Exchange Ser... BEELZEBUB
15.00.1236.003   15.00.1236.003   C:\Program Files\Microsoft\Exchange Ser... CTHULHU


Exchange 2013 CU14 Installation crash on Mailbox role: Transport Service. Configuration.xml Root Element is missing

$
0
0

Hi

I need some help, very urgent.
I started cu14 Installation, and in the middle the Installation failed.

I've tried the resolution steps suggested in: https://social.technet.microsoft.com/Forums/office/en-US/b2f53158-3a75-4224-8826-1d92ef7b5922/exchange-2013-cu7-installation-crash-on-mailbox-role-transport-service?forum=exchangesvrdeploy with no luck, error keeps happening!

Error:

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

            # Apply XML Transforms to FIPS configuration file if schema changed

            Write-ExchangeSetupLog -Info "Applying XML Transforms to FIPS configuration";

            $FipsBinPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\bin");

            [Reflection.Assembly]::LoadFile([System.IO.Path]::Combine($FipsBinPath, "FSCConfigurationServerInterfaces.dll"));

            [Reflection.Assembly]::LoadFile([System.IO.Path]::Combine($FipsBinPath, "FSCConfigSupport.dll"));

            $configServer = New-Object Microsoft.FSC.Configuration.ConfigManagerClass;

            if(! $configServer)

            {

              Write-ExchangeSetupLog -Error "Configuration Server object could not be created.";

            }

            else

            {

              try

              {

                $configServer.Upgrade();

                Write-ExchangeSetupLog -Info "Configuration.xml was upgraded successfully";

              }

              catch

              {

                Write-ExchangeSetupLog -Error "Upgrade of Configuration.xml was unsuccessfull, $_";

              }

              # Stop the process if it is still running

              # We silently continue because if process has already exited, Stop-Process will throw error

              # Error is non-terminating and so can be suppressed

              Stop-Process -processname FSCConfigurationServer -Force -ErrorAction SilentlyContinue;

            }

          " was run: "System.Exception: Upgrade of Configuration.xml was unsuccessfull, Exception calling "Upgrade" with "0" argument(s): "Root element is missing."

   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.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)".

Regards,

Phill


Installation of CU13 on Exchange 2013 Mailbox Server Fails

$
0
0

Configuring Microsoft Exchange Server

    Restoring Services                                                                               COMPLETED
    Mailbox role: Transport service                                                                  COMPLETED
    Mailbox role: Client Access service                                                              COMPLETED
    Mailbox role: Unified Messaging service                                                           COMPLETED
    Mailbox role: Mailbox service                                                                    FAILED
     The following error was generated when "$error.Clear();
        buildToBuildUpgrade-ExsetdataAtom -AtomName SystemAttendant -DomainController $RoleDomainController

" was run: "Microsoft.Exchange.Management.Deployment.ExsetdataException: An error occurred with error code '3221685616'
and message 'The file or directory is corrupted and unreadable.'.
   at Microsoft.Exchange.Management.Deployment.ManageExsetdataAtom.HandleExsetdataReturnCode(UInt32 scErr)
   at Microsoft.Exchange.Management.Deployment.ManageExsetdataAtom.BuildToBuildUpgradeAtom(AtomID atomID)
   at Microsoft.Exchange.Management.Deployment.BuildToBuildUpgradeExsetdataAtom.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePip
elineIfFailed)".

This is the error I get...

outlook.com (can't log in)

$
0
0
The Outlook.com on Edge, or Explorer or any browser will not allow me to log in, because of certificate mismatch. Please tell Microsoft to fix it, since I seem to keep getting errors even trying to report this problem.
Viewing all 7129 articles
Browse latest View live


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