Security Update for exchange 2013 SP1 (KB3040856) failed mid-way / power problem mailbox server disconnected

While applying todays security update for exchange 2013 (KB3040856) there was a power issue (sad story) and the update was interrupted halfway through. A bunch of service were left deactivated and I beleive I brought them back.
At this point the exchange admin center brings me to the login and when I do login, I get an enable to display page msg after the login.
I have an ActiveSync error log "cannot access the mailbox because the mail box server is disconnected" translated from french.
I also have ASP.NET 4.0 error "MapiExceptionMdbOffline"
What could be the next step in fixing this if it is at all possible ? I am not an expert in cmdlet but can manage if pointed in the right direction.
Any help would be greatly appreciated.
Thank you.

I ran update KB3040856, and it disabled all Exchange services, and a few others besides (IIS and filtering). I ran the test-servicehealth cmdlet and eventually got all the services set to automatic and all running.
This is really a stupid thing for an update to do, what is going on? Exchange 2013 is trouble enough already, we really do not need this sort of agro.

Similar Messages

Security Update for exchange server 2013SP1 KB3011140 Stops all services and failes to install

Hi All,
Over the past 2 days this update has tried to run on the server in the evening but ends up failing. When it fails it is causing all of our exchange services to stop working and when we try to check e-mails the following day we find out the e-mail service
has been offline since the update.
Is there anything specific we need to do before running this update?
Cheers,

Hi,
As what Hotaka says, this update is available from
Windows Update. If it fails, we can also download and install the updates manually. The following stand-alone file is available for download from the Microsoft Download Center:
Download the security update for Exchange 2013 Service Pack 1 package now.
Download the security update for Exchange 2013 Cumulative Update 6 package now.
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 SP1 Setup fails

I am getting very frustrated. It really shouldn't take over a week to install Exchange.
I have two domain controllers, Windows 2003 and Windows 2008 R2. The 2008 is now all Operations Masters for all roles.
I have a clean install of W2K8 R2 SP1 installed under Hyper-V on a separate physical W2K8 server. Before starting the install I used ADSIEdit to ensure there was nothing left in the AD of prior Exchange install attempts. This is the first and only installation
of Exchange.
I am running the install as the Domain\Administrator and naturally that account is a member of all the appropriate security groups. RSAT are installed on the Exchange server and using them to access Users and Computers clearly shows this. The install fails
with the errors below, all of which appear to be incorrect.
*** BEGIN ERROR ***
Error:
Global updates need to be made to Active Directory, and this user account isn't a member of the 'Enterprise Admins' group.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalUpdateRequired.aspx
Error:
You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFrontendTransportFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailboxFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClientAccessFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifiedMessagingFirstInstall.aspx
Error:
Setup encountered a problem while validating the state of Active Directory: Couldn't find the Enterprise Organization container. See the Exchange setup log for more information on this error.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx
Error:
The forest functional level of the current Active Directory forest is not Windows Server 2003 native or later. To install Exchange Server 2013, the forest functional level must be at least Windows Server 2003 native.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ForestLevelNotWin2003Native.aspx
Error:
This computer requires the Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit. Please install the software from http://go.microsoft.com/fwlink/?LinkId=260990.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.UcmaRedistMsi.aspx
Error:
This computer requires the update described in Microsoft Knowledge Base article KB974405 (http://go.microsoft.com/fwlink/?LinkId=262357). Please install the update, and then restart Setup.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.Win7WindowsIdentityFoundationUpdateNotInstalled.aspx
Error:
Either Active Directory doesn't exist, or it can't be contacted.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.aspx
Warning:
Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
*** END ERROR
Why can't Exchange installation see the AD when everything else can?

It appears that these error messages are pure fiction. I went back to ADSI Edit and removed some MS Exchange container and then reran setup /prepareschema again followed by setup /preparead and finally setup /mosde:install /role:clientaccess,mailbox and
it churned away for a long time, apparently working.
It appears than when it says you aren't a member of Schema Admins and that it can't access Active Directory, what it really means is it could find the AD just fine, but didn't like what it saw.
My guess would be very sloppy programming in which the low level error doesn't bubble up and so when something fails it just assumed you didn't have permissions.
It's not quite finished yet, but I am beginning to believe it will finish. So that's almost 6 days of non stop effort to install Exchange. It's hard top believe they are allowed to charge for this stuff.

Upgrade of Integation Services (Windows 2012 R2) on Windows 2008 R2 with Exchange 2013 SP1 DAG fails

Here is the scenario:
Legacy Host: Windows 2008 R2
Guest VM: Windows 2008 R2 with Exchange 2013 SP1 DAG cluster.
After importing the VM (2008 R2 and Exchange 2013 DAG) into a 2012 R2 host (Cluster). (copy VM files to new 2012 R2host) Everything works fine.
Then upgrading "Installation Services" (for Windows 2012 R2 host) on the imported VM runs fine with no errors to the "Restart" prompt. VM than shows: "Configuring Windows updates 32% complete. Do not turn
of your computer." Hangs there for about 20 minutes until is says "shutting down". Hangs there for 20 minutes until power off. Restart to normal start; "Preparing to configure Windows. Do not turnoff your computer." proceeds slowly
to "Configuring Windows updates 32% complete. Do not turn of your computer." hangs there again indefinite. Sometime hangs at shutdown cycle and "Configuring Windows updates 32% complete. Do not turn of your computer." indefinitely.
I moved 20 other machines from a 2008 R2 host to new Windows 2012 R2 hosts all of these machines install the 2012 R2 Integration services just fine on the 2008 R2 VM. Just the 2008 R2 VMs clustered (DAG) and Exchange 2013 SP1 do not take the Integration
Services upgrade.
Any advise from Microsoft? I know I could decommission the DAG and Exchange machines and install Integration services on the native box before Exchange and DAG and that would sure work, but I'd rather avoid that amount of work for a simple integration layer
upgrade.
Thanks
Gerhard Waterkamp ACSLA Inc.

Hi,
Could you try use the following method to fix this issue first?
1. Run the System Update Readiness Tool, then check if there is any error in the Checksur.log and checksur.persist.log.
1. Please run the System Update Readiness Tool on this affected server. Please download this tool from the following Microsoft article:
Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, and for Windows 7
http://support.microsoft.com/kb/947821/en-us
2. The System Update Readiness Tool creates the log files that captures any issues that the tool found or fixed. The log files are located at the following location:
%SYSTEMROOT%\Logs\CBS\
3. Please paste the checksur.log here for analysis.
If there is no error found, please try the following step.
==================================
2. Use Fix it tool to reset the Windows Update components.
1. Open the following link.
http://support.microsoft.com/kb/971058/en-nz
2. Select Windows 8.1, Windows 8 and Windows 7 in the product selection box.
3. Click “Run Now” to reset the Windows Update components.
Note: We can reset the Windows Updates manually by following the steps in the KB above.
3. Use the System File Checker tool to repair missing or corrupted system files
1. Open the command promote with Administrators.
2. At the command prompt, type the following command, and then press ENTER:
sfc /scannow
Any errors are found in the steps above, please let me know.
Hope this helpful.
Best Regards,
Jason Zeng
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Exchange 2013 SP1 - healthsets failing

Hi,
I have recently installed two Exchange 2013 SP1 servers in different environments and are experiencing issues on both. Issues that I haven't seen on Exchange 2013 without SP1.
I have 6 healthsets which are unhealthy.
Autodiscover...
ActiveSync.P...
EWS.Proxy
OAB.Proxy
Outlook.Proxy
OutlookMapiH...
I found this article:
http://technet.microsoft.com/en-us/library/ms.exch.scom.ecp.proxy(v=exchg.150).aspx
Which describes, that try to restart the app pool, then an iisreset - and lastly reboot the server. Tried all and none of them helped.
But then I found this error in the Exchang event log:
RecycleApplicationPool-MSExchangePowerShellAppPool-RpsDeepTestPSProxyRestart: Throttling rejected the operation
Which fails almost every minute.
And I guess that this could be the issue. But I can't figure out which throttling that is causing this.
Any one else with this issue on Exchange 2013 SP1?
Thanks in advance.
/Kim

Hi,
I have seen a lot of similar issues with health manager service. For IIS services, we can safely ignore these warnings. Personal experience, we just need to monitor whether there are related
error reports in event log.
Thanks,
Simon Wu
TechNet Community Support

Exchange 2013 SP1 setup fails at prerequisite Analysis

I installed a completely new server network with Hyper-v 2012R2
I installed two virtual 2012R2 servers: DC01 as the Domain Controller of "testdomain.local" and EX01 as the Exchange server.
EX01 is joined the domain "testdomain" from DC01
I log in on EX01 with an in AD created testdomain\exadmin account who is member of domain admins, enterprise admins, schema admins, administrators and group policy creator owners.
I have run the command Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience,
NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing,
Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression,
Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation, Telnet-Client, RSAT-ADDS
on EX01
I have installed the Microsoft Unified Communications Managed API 4.0
Then I run the Exchange 2013 SP1 setup and the prerequisite check gives the following errors:
Error:
You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFrontendTransportFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailboxFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClientAccessFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifiedMessagingFirstInstall.aspx
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.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx
Error:
Either Active Directory doesn't exist, or it can't be contacted.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx
I can connect with the Active Directory Sites and Domains and other applets to the AD. So Why these errors???
HELP!
Regards, Manu
Manu van Winkel

Hi, thanks for the answer.
I restarted the server and did the "run as administrator": same result.
The first errormessage in the exchangesetup.log is:
[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.
When I run dcdiag /s:DC01 from EX01 it passes all tests except:
DFSREvent "The RPC server is unavailable"
KccEvent "The RPC server is unavailable."
SystemLog "The RPC server is unavailable."
Could these be of any influence?
Running dcdiag on DC01 passes all tests.
The only thing I changed after setting up DC01, was changing the fixed IP-adres from 192.168.25.3 to 192.168.25.2, but I ran ipconfig /flushdns and ipconfig /registerdns and dcdiag /fix afterwards.
The only roles installed on DC01 are AD DS (I tried installing exchange before and after adding the AD DS role), AD, DNS, DHCP and Fileservices
I don't know where to look anymore....
Manu van Winkel

Applying CU4 for Exchange 2013 SP1 in a mixed 2010 / 2013 Environment

We're planning to apply Exchange 2013 SP1 CU in our mixed 2010 / 2013 environment. We'd also like to apply Exchange 2010 SP3 Rollup 5 as well. Are there any gotchas or best practices on what update to apply first?
Orange County District Attorney

We are planning to update our 2013 from CU5 to CU8
and 2010 SP3 to Rollup 9
I cant find any official documentation from MS concerning the upgrade path. Example.
Exchange 2013 first, then 2010. Like the above post outline.
I see 2010 being upgraded first thus bring version numbers closer together, reducing incompatibilities.
Do you still feel this is the appropriate install procedure?
Have you done this?
Djoe

Exchange 2013 SP1 Install fails on step 5 of 9: Mailbox Role: Mailbox Service

We have exchange installed on a windows 2008 R2 box.
We keep getting the following error when we try to install the update:
Error:
The following error was generated when "$error.Clear();
if ($RoleIsDatacenter -ne $true -and $RoleIsDatacenterDedicated -ne $true)
if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
$sysMbx = $null;
$name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
$dispName = "Microsoft Exchange";
Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
$mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
if ($mbxs.Length -eq 0)
Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
$dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
if ($dbs.Length -ne 0)
Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
$arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
if ($arbUsers.Length -ne 0)
Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
$sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
else
if ($mbxs[0].DisplayName -ne $dispName )
Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
$sysMbx = $mbxs[0];
# Set the Organization Capabilities needed for this mailbox
if ($sysMbx -ne $null)
# We need 1 GB for uploading large OAB files to the organization mailbox
Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions:$true -MailRouting:$true -MessageTracking:$true -PstProvider:$true -MaxSendSize 1GB -Force;
else
Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
else
Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
" was run: "Database is mandatory on UserMailbox.".
Error:
The following error was generated when "$error.Clear();
if ($RoleIsDatacenter -ne $true -and $RoleIsDatacenterDedicated -ne $true)
if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
$sysMbx = $null;
$name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
$dispName = "Microsoft Exchange";
Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
$mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
if ($mbxs.Length -eq 0)
Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
$dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
if ($dbs.Length -ne 0)
Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
$arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
if ($arbUsers.Length -ne 0)
Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
$sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
else
if ($mbxs[0].DisplayName -ne $dispName )
Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
$sysMbx = $mbxs[0];
# Set the Organization Capabilities needed for this mailbox
if ($sysMbx -ne $null)
# We need 1 GB for uploading large OAB files to the organization mailbox
Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions:$true -MailRouting:$true -MessageTracking:$true -PstProvider:$true -MaxSendSize 1GB -Force;
else
Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
else
Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
" was run: "Database is mandatory on UserMailbox.".
Any help would be greatly appreciated!
Thanks,
Wes

Hello,
Please make sure you do exchange server upgrading or a clean exchange 2013 installation. If you do a upgrading, please refer to the similar thread to assign a database to the arbitration mailbox "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}".
http://social.technet.microsoft.com/Forums/en-US/239cb4a6-4a07-4b9a-800c-974573bbff32/error-installing-step-12-mailbox-role-service-on-exchange-2013-cu2?forum=exchangesvrdeploy
Please make sure you have these permission "Schema Admins, Domain Admins and Enterprise Admins" to install exchange 2013 server.
If this is a clean exchange 2013 installation, please try to recreate the system mailbox to check the result.
Cara Chen
TechNet Community Support

Cannot Adding Mailbox Server for Database Copy for Exchange 2013 SP1

Before I upgraded to 2013 SP1 everything works find but after I upgrade to SP1 I cannot add database copy. the details are...
I have 2 sites
Site 1 : 4 Mailboxes (Mailbox01,Mailbox02,Mailbox03,Mailbox04)   + 2 CAS
Site 2 : 2 Mailboxes (Mailbox05,Mailbox06)   + 2 CAS (just for standby site)
So I have 2 DAG group  (6 Mailboxes separate to 3 Mailboxes for 1 DAG group Mailbox01,Mailbox02,Mailbox05 for DAG1 and Mailbox03,Mailbox04,Mailbox06 for DAG2)
After I upgrade Exchange 2013 to SP1 , I try to create new database on Mailbox01 and after that I try to add mailbox02 and mailbox05 to database copy of new database that I created.
"Mailbox05 can added to be database copy but Mailbox02 cannot add database copy for it , Error "Network path not found" occur" but Im very sure that path is the same for each mailbox database server.
so I try to create new database on Mailbox 03 and add database copy on mailbox04 and mailbox06.... the result is the same only Mailbox06 can add mailbox copy of database.
It look like I cannot have 2 mailbox in site 1 for database copy of each new database (I already try to create new database on Mailbox 02 and add database copy on mailbox01 and mailbox05 , the result is only mailbox05 can be database copy of database).
Please help me to fix this out.

Hi,
I recommend you check if the Remote Registry service is running on Mailbox01, Mailbox02, Mailbox03 and Mailbox04. If not, please start it and then add mailbox database copy to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Update from Exchange 2013 SP1 to CU8 error

hi,
i've got problem when update to cu8.
the file 'c:\program files\microsoft\exchange server\v15\transportroles\agents\hygiene\asdat.msi' is not a valid installation package for the product microsoft exchange 2007 standard anti-spam filter updates. try to find the installation package 'asdat.msi'
in a folder from which you can install microsoft exchange 2007 standard anti-spam filter updates.
please help me..

hi,
i've got problem when update to cu8.
the file 'c:\program files\microsoft\exchange server\v15\transportroles\agents\hygiene\asdat.msi' is not a valid installation package for the product microsoft exchange 2007 standard anti-spam filter updates. try to find the installation package 'asdat.msi'
in a folder from which you can install microsoft exchange 2007 standard anti-spam filter updates.
please help me..
     The following error was generated when "$error.Clear();
          uninstall-MsiPackage -ProductCode '{C3F10D8C-BD70-4516-B2B4-BF69019807
41}' -LogFile ($RoleSetupLoggingPath + "\UninstallASDat.msilog")
        " was run: "Microsoft.Exchange.Configuration.Tasks.TaskException: Couldn
't remove product with code c3f10d8c-bd70-4516-b2b4-bf6901980741. The installati
on source for this product is not available. Verify that the source exists and t
hat you can access it. Error code is 1612. ---> System.ComponentModel.Win32Excep
tion: The installation source for this product is not available. Verify that the
source exists and that you can access it
   --- 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.Deployment.UninstallMsi.RemoveProductCode(Gu
id productCode)
   at Microsoft.Exchange.Management.Deployment.UninstallMsi.InternalProcessRecor
d()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String fun
cName, Action func, Boolean terminatePipelineIfFailed)".
The Exchange Server setup operation didn't complete. More details can be found
in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.

Remote managment Exchange 2013 SP1 from C# code using Power-Shell.

Hello,
Sorry if I am describing something wrong, but it is first time I am using Microsoft development forum.
I am trying to built library that will manage Exchange remotely using C# code (VS 2012) and Power-Shell ver.4.0. My workstation and the actual Exchange server physically placed in different domains. In order to test functionalities I am using
user that is member of all administrating and management groups in the appropriative domain. Remote Power-Shell is enabled on Exchange.
In order to connect to the Service I am using that part of code :
internal static bool RedirectionUrlValidationCallback(string redirectionUrl)
bool result = false;
var redirectionUri = new Uri(redirectionUrl);
if (redirectionUri.Scheme.Equals("https"))
result = true;
return result;
internal static ExchangeService ConnectToService(ExchangeVersion version,
string userName,
string emailAddress,
string password,
string domainName,
ref Uri autodiscoverUrl)
ExchangeService service;
try
service = new ExchangeService(version);
service.Credentials = new WebCredentials(userName, password, domainName);
if (autodiscoverUrl.IsNull())
var ads = new AutodiscoverService();
// Enable tracing.
ads.TraceEnabled = true;
// Set the credentials.
ads.Credentials = service.Credentials;
// Prevent the AutodiscoverService from looking in the local Active Directory
// for the Exchange Web Services Services SCP.
ads.EnableScpLookup = false;
// Specify a redirection URL validation
//callback that returns true for valid URLs.
ads.RedirectionUrlValidationCallback = RedirectionUrlValidationCallback;
// Get the Exchange Web Services URL for the user’s mailbox.
var response = ads.GetUserSettings(emailAddress, UserSettingName.InternalEwsUrl);
// Extract the Exchange Web Services URL from the response.
autodiscoverUrl = new Uri(response.Settings[UserSettingName.InternalEwsUrl].ToString());
// Update Service Url
service.Url = autodiscoverUrl;
else
service.Url = autodiscoverUrl;
catch (FormatException fe) // The user principal name(email) is in a bad format. UPN format is needed.
LoggingFactory.LogException(fe);
return null;
catch (AutodiscoverLocalException ale)
LoggingFactory.LogException(ale);
return null;
catch (Exception e)
LoggingFactory.LogException(e);
return null;
return service;
Then I am trying to reach existing mailbox of that user, using this part of code :
try
var runSpace = getRunspace();
var pwShell = PowerShell.Create();
pwShell.Runspace = runSpace;
var command = new PSCommand();
command.AddCommand("Get-Mailbox");
command.AddParameter("Identity", userPrincipalName);
command.AddParameter("RecipientTypeDetails", recipientType);
pwShell.Commands = command;
var result = pwShell.Invoke();
if (result.IsNotNull() && result.Any())
// TODO : fill appropriative DTO and return it.
else
// TODO : send back appropriative error.
closeRunSpace(runSpace);
catch (Exception e)
// TODO : log the exception and send back appropriative error.
private Runspace getRunspace()
var runSpaceConfig = RunspaceConfiguration.Create();
var runSpace = RunspaceFactory.CreateRunspace(runSpaceConfig);
PSSnapInException snapEx;
var psInfo = runSpaceConfig.AddPSSnapIn("Microsoft.Exchange.Management.PowerShell.E2010", out snapEx);
runSpace.Open();
return runSpace;
private void closeRunSpace(Runspace runSpace)
runSpace.Close();
runSpace.Dispose();
With this part I had problem. I received exception that appropriative Snap-in is not installed on my computer. I had no installation disk of Exchange in order to install Management Tool (as I understand this is the way to add needed part) so I changed run
space activation to that part of code :
private Runspace getRunspace()
var newCredentials = (PSCredential)null;
var connectionInfo = new WSManConnectionInfo(new Uri("http://exchange.domainname.local/powershell?serializationLevel=Full"),
"http://schemas.microsoft.com/powershell/Microsoft.Exchange",
newCredentials);
connectionInfo.AuthenticationMechanism = AuthenticationMechanism.Kerberos;
var runSpace = RunspaceFactory.CreateRunspace(connectionInfo);
runSpace.Open();
return runSpace;
Now I am receiving exception :
"Connecting to remote server exchange.domainname.local failed with the following error message :
[ClientAccessServer=exchange,BackEndServer=exchange.domainname.local,RequestId=....,TimeStamp=...]
Access is denied. For more information, see the about_Remote_Troubleshooting Help topic."
Please help me to understand what I am doing wrong.
Thank you.
Alexander.

In Exchange 2010 you should be using Remote Powershell not local powershell and the snap-in. Here is a sample that may help you:
http://blogs.msdn.com/b/dvespa/archive/2009/10/22/how-to-call-exchange-2010-cmdlet-s-using-remote-powershell-in-code.aspx

Exchange 2013 SP1 EDGE role content filtering ?

Hello,
Have Exchange 2013 SP1 with CU5 with antispam enabled on mailbox role server. And i wonder if i deploy 2013 Edge role, will i get more granular content filter control, like there is in Office 365? For example: i want to treat empty messages as not
spam.
I have read that control of Edge server is done ONLY by powershell. So if edge role is deployed, still there is no content filter control in ECP (like in office365) ??

Hi,
The Content Filter agent assigns a spam confidence level (SCL) rating to each message. The SCL rating is a number between 0 and 9. A higher SCL rating indicates that a message is more likely to be spam.
Based on my knowledge, I'm afraid we can't filter the empty messages and treat them as not spam.
Here is an article about content filtering in Exchange 2013 for your reference.
Content Filtering
http://technet.microsoft.com/en-us/library/bb124739(v=exchg.150).aspx
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Update reports exchange 2013

Becouse updates for exchange 2013 ar not in wsus
Is there page in can monitor by rss feed that just reports updates of exchange 2013 ?
I know the exchange team blog, there are alot more post.
I want to be triggerd only when there is an update voor exchange 2013
With kind regards, Bas van den Dikkenberg

Actually there is one option and it's best available option.
You can use Exchange Team Blog
http://blogs.technet.com/b/exchange/
All the updates for new release comes here first.
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

SP1 for Exchange 2013 install fails with ECP virtual directory issues and now transport service won't start and mail is unavailable

SP1 for Exchange 2013 install failed on me with ECP virtual directory issues:
Error:
The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ecp (name)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
          if ($be -eq $null)
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
        " was run: "The virtual directory 'ecp' already exists under 'server/name'.
Parameter name: VirtualDirectoryName".
Error:
The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ECP (name)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
          if ($be -eq $null)
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
        " was run: "The operation couldn't be performed because object 'server\ECP (name)' couldn't be found on 'DC0xx.domain.com'.".
Error:
The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ECP (name)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
          if ($be -eq $null)
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
        " was run: "The operation couldn't be performed because object 'server\ECP (name)' couldn't be found on 'DC0xx.domain.com'.".
!! And now transport service won't start and mail is unavailable !!
Any help would be appreciated.
I have removed the ecp site from default site and attempting to rerun SP1 now. I do not have high hopes. :(

Hi,
Thanks for your response.
From the error description, you need to manually remove the ECP with IIS manager in both the Default Web Site and the Exchange Back End firstly. And then continue the upgrade to check the result.
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Exchange 2013 SP1: Fix for failing MSExchangeTransport service

We had a newly updated Exchange 2013 SP1 that would not start the Transport service
"Netstat -b" showed that a service was listening to port 25 on all IP's (0.0.0.0:25) and when the service could not get the port, it would die, and Exchange would attempt to restart it over and over.
After many tears, I found this solution:
Through the console or the ECP, check the Frontend receive connectors and find the one that is listening on 0.0.0.0:25, which is probably the Default Frontend Receive. Disable it.
Restart the MSExchangeTransport and MSExchangeTransportFrontEnd services.
If both services restart normally, troubleshooting is complete.
We use several custom connectors carried forward from the previous installation, which was SBS 2008. If this applies to you, take notice.

Normally, the Default Frontend Receive Connector (0.0.0.0:25) is the messaging entry point for your organization (I am assuming that you have a single MBX/CAS server).
1. If you disable the Default Frontend Receive Connector (0.0.0.0:25), you block inbound email.
2. Most probably, the cause for your problem are the Custom Receive Connectors. Check their type, and if it is Hub Transport, delete and re-create them as Front End Receive connectors.
Step by Step Screencasts and Video Tutorials

Security Update for exchange 2013 SP1 (KB3040856) failed mid-way / power problem mailbox server disconnected

Similar Messages

Maybe you are looking for