Exchange 2013 Services pack 1 installation Error

Hey Guys ,
I'm facing an issue while installing exchange 2013 on server 2012 R2 , below are the details . I'm installing it on test bed however i'm failing at organisation preparation stage.
Error:
The following error was generated when "$error.Clear();
install-RuleCollection -Name:"ClassificationDefinitions" -DomainController $RoleDomainController;
New-ClassificationRuleCollection -InstallDefaultCollection
" was run: "Unable to continue processing classification rule collection payload for decryption or further validations. Payload may contain invalid data.".
Please Help me
Sandy Carlos

Hi,
I got a error when i run this command
Setup.exe /PrepareAD /OrganizationName:<name> /IAcceptExchangeServerLicenseTerms
then i got a error
on Organization Configuration Step.
and i got same error when run the setup when setup is going for Organization Preparation.
Thanks

Similar Messages

Office 2013 with Service Pack 1 installation error about "search path"

I have an automated installation technique that has worked fine with Office 2010 Pro Plus (32-bit), incorporating the latest Service Pack into the network administrative installation point (under \updates), adding 10 foreign languages to the network administrative
installation point, creating a custom .msp with the OCT (that goes into \updates too), editing the config.xml files, and then running setup.exe from that network administrative installation point. This works on 32-bit Windows XP clients and on 32- and 64-bit
Windows 7 clients.
For Office 2013 Pro Plus, I have built the network administrative installation point exactly the same way (original DVD files + languages + SP1 updates + config.xml updates), but the installation is failing with every type of client, all with
the same error message. The network administrative installation point is readable by the normal installing account, but I even get the same error when I login as me and initiate setup.exe manually, and I have all rights to this point.
Here's the critical point from a log file:
2014/03/11 11:53:49:691::[2372] DistributionPoint parsed. The distribution point is now set to: \\archive.ads.college.edu\archive\KBOXalt\Office2013
2014/03/11 11:53:49:691::[2372] COMPANYNAME specified in config.xml.
2014/03/11 11:53:49:691::[2372] USERNAME specified in config.xml.
2014/03/11 11:53:49:800::[2372] Setupexe Resiliency Mode is set to [PerformIfApplicable]; thus Resiliency is [disabled] for the [InstallExecutionMode]
2014/03/11 11:53:49:910::[2372] Searching for default versions of resource files under the folder [\\archive.ads.college.edu\archive\KBOXalt\Office2013].
2014/03/11 11:53:50:019::[2372] Error: GetDirectories: search path \\archive.ads.college.edu\archive\KBOXalt\Office2013 does not exist
ErrorCode: 0(0x0). Failed final attempt to load a setupexe resource file.
2014/03/11 11:53:50:019::[2372] Error: GetDirectories: search path \\archive.ads.college.edu\archive\KBOXalt\Office2013 does not exist
Type: 34::InvalidDirectory.
2014/03/11 11:53:50:019::[2372] WER element [SuppressModal] is set to value [true]
2014/03/11 11:53:50:019::[2372] WER element [P4] is set to value [InvalidDirectory]
2014/03/11 11:53:50:019::[2372] Catalyst execution finished: 03/11/2014 11:53:50. Return code: 30034. Exception caught: InvalidDirectory.
2014/03/11 11:53:50:019::[2372] PERF: TickCount=894821 Name=RunSetup Description=End function
I cannot find any references to this exact error anywhere on the Internet. Can anyone tell me what this means, and how I fix it?

As automated, the utility that runs setup.exe maps a drive letter to
\\archive.ads.college.edu\archive\KBOXalt using a kboxmap AD account, which has read access to the whole \KBOXalt tree. I used that same kboxmap AD account manually to simulate what the utility does, and hit the same problem. But here's what's
odd: right next to that
\\archive.ads.college.edu\archive\KBOXalt\Office2013 directory is an
\\archive.ads.college.edu\archive\KBOXalt\Office2010 directory, both created the same way, and the Office 2010 installation has always worked perfectly using the kboxmap AD account. I don't understand why Office 2013 is only working for an account with
read/write access, where Office 2010 worked fine for an account with only read access. Especially when the Office 2013 resource kit documentation clearly states that the account running the installation should only have read access, nothing more. (All this
KBOX stuff comes from the fact that our deployment environment is a Dell KACE KBOX 1000. However, that plays no part in the problem: ignoring the KBOX 1000, I can manually recreate the problem every time.)

Office 2013 Service Pack 1 installation causes shim error in Windows 8.1 Enterprise

On a clean install of Windows 8.1 Enterprise and Office 2013 I installed RSAT and everything works fine initially. When I install the Office 2013 Server Pack 1 update (categorized as an "Important" update) I then get the following
errors when attempting to open Server Manager:
(I attempted to include an image of the error and a link to the KB article but it wouldn't allow that saying my account must be verified although there appears to be no way to actually verify my account. The "Verify Your Account 13" thread
doesn't help by the way.)
ServerManager.exe - This application could not be started. Do you want to view information about the issue?
Which if I click Yes it takes me to the page for this KB article:
KB2715633
The KB page refers to three different SHIM errors. The second two don’t apply to this scenario but the first seems to. Unfortunately the info on this one is:
“The app is not configured in a way that makes it possible to determine the appropriate version of the .NET Framework runtime.
You can't fix the configuration problem yourself. Contact the app vendor to resolve the issue.”
I've re-installed Windows twice and have been able to replicate the problem each time (Clean Win 8.1 install, Office 2013 install, RSAT, everything works, install Office 2013 SP1).
It says in the KB to "Contact the app vendor". In this case that would be Microsoft.

1. What is you install W 8.1 ENT + all important updates -> Office 2013 > Office 2013 SP1 > RSAT ?
2. Make sure that .NET 3.51 and 4.51 are installed.
3. Make sure that there is no coincidence with issues
http://support.microsoft.com/kb/2817430
4. Try to sesolve problem with Process Explorer and Process Monitor
HTH
Milos

Error in Configuration Wizard after installing SharePoint 2013 Service Pack 1

Windows Server 2012 with latest updates and SharePoint 2013 with latest updates:
I installed SharePoint 2013 Service Pack 1 and when I run the configuration Wizard i get this error:
Error in Configuration Wizard
Resource id to be retrieved is PostSetupConfigurationFailedEventLog for language English (United States)
Resource retrieved id PostSetupConfigurationFailedEventLog is Configuration of SharePoint Products failed. Configuration must be performed in order for this product to operate properly. To diagnose the problem, review the extended error information
located at {0}, fix the problem, and run this configuration wizard again.
Leaving function StringResourceManager.GetResourceString
Configuration of SharePoint Products failed. Configuration must be performed in order for this product to operate properly. To diagnose the problem, review the extended error information located at C:\Program Files\Common Files\Microsoft Shared\Web
Server Extensions\15\LOGS\PSCDiagnostics_3_8_2014_23_55_49_686_1872915373.log, fix the problem, and run this configuration wizard again.
In event view I see this two errors:
1) First error
System
Provider
[ Name]
SharePoint 2010 Products Configuration Wizard
EventID
104
[ Qualifiers]
0
Level
2
Task
0
Keywords
0x80000000000000
TimeCreated
[ SystemTime]
2014-03-08T21:41:59.000000000Z
EventRecordID
135580
Channel
Application
Computer
ABC-SRV-WEB01.abc.local
Security
EventData
Failed to initiate the upgrade sequence. An exception of type System.MissingMethodException was thrown. Additional exception information: Method not found: 'Void Microsoft.SharePoint.WorkflowServices.IWorkflowService.Upgrade(System.Object,
System.String, Microsoft.SharePoint.Upgrade.SPLog)'. System.MissingMethodException: Method not found: 'Void Microsoft.SharePoint.WorkflowServices.IWorkflowService.Upgrade(System.Object, System.String, Microsoft.SharePoint.Upgrade.SPLog)'. at System.RuntimeTypeHandle.GetTypeByName(String
name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMarkHandle stackMark, IntPtr pPrivHostBinder, Boolean loadTypeFromPartialName, ObjectHandleOnStack type) at System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError,
Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean loadTypeFromPartialName) at System.Type.GetType(String typeName) at Microsoft.SharePoint.Utilities.SPTypeSerializer.DeserializeType(String typeName,
Guid classId, Boolean bResolveMissingTypes) at Microsoft.SharePoint.Administration.SPConfigurationDatabase.ResolveObjectAndClassVersions(SPLog log) at Microsoft.SharePoint.Upgrade.SPManager.BootStrap(Guid sessionId, SPUpgradeOperationFlags flags) at Microsoft.SharePoint.PostSetupConfiguration.UpgradeBootstrapTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
2) Second error
System
Provider
[ Name]
SharePoint 2010 Products Configuration Wizard
EventID
100
[ Qualifiers]
0
Level
2
Task
0
Keywords
0x80000000000000
TimeCreated
[ SystemTime]
2014-03-08T21:41:59.000000000Z
EventRecordID
135581
Channel
Application
Computer
ABC-SRV-WEB01.abc.local
Security
EventData
Configuration of SharePoint Products failed. Configuration must be performed in order for this product to operate properly. To diagnose the problem, review the extended error information located at C:\Program Files\Common Files\Microsoft Shared\Web Server
Extensions\15\LOGS\PSCDiagnostics_3_8_2014_23_41_9_710_572545016.log, fix the problem, and run this configuration wizard again.
Please advise on next steps.
How can I successfully install SP1?
Thanks,
Alex

could you please share the upgrade log file, so that we understand the error?
did you reboot your server after the installation of SP1?
also try to clear the Config cache on the servers and then try again?
you can run this command on the server its failing
Get-SPProduct -local
PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

Exchange Server 2013 Service Pack Upgrade - Outlook connectivity issue

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

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

Cannot download Office 2013 Service Pack 1 (KB2850036)

I'm using SCCM 2012 Config Manager. I've created a software update date for Office 2013 - Service Pack 1. It contains only 1 update, and that's the Office 2013 SP1 (KB2850036).
The standalone installer for this KB is around 640MB, according to the following link.
http://support.microsoft.com/kb/2817430/en-us
When I choose to Download this update with SCCM, it starts the normal "Provisioning Update" process but sits at 0%. The deployment package directory grows to 334 folders, 329 files taking 3,707,522,416 bytes on the hard drive, and then eventually
throws the following error in SCCM.
Error: Service pack 1 for Microsoft Office 2013 (KB2850036) 32-Bit Edition. Failed to download content id 16844655. Invalid certificate signature.
I've tried the download a couple of times, and I get the same thing.
Any suggestions?

WSUS does not use the stand-alone installer for any updates. For this update in specific, because I had a battle with it, there are something like 700 different files that are part of the update and something like 800GB of data - those are ballpark numbers
based on my spotty memory; IOW, lots. Your best bet is just to right-click on the update itself and select download again.
If that still doesn't work at all, you can click on the update and go to the content tab, you'll see all of the files listed. You can individually copy the URLs (using Ctrl+C) and download them manually if there are one or two that won't download.
Jason | http://blog.configmgrftw.com

Seemingly successful install of Exchange 2013 SP1 turns into many errors in event logs after upgrade to CU7

I have a new Exchange 2013 server with plans to migrate from my current Exchange 2007 Server.
I installed Exchange 2013 SP1 and the only errors I saw in the event log seemed to be long standing known issues that did not indicate an actual problem (based on what I read online).
I updated to CU7 and now lots of errors have appeared (although the old ones seem to have been fixed so I have that going for me).
Currently the Exchange 2013 server is not in use and clients are still hitting the 2007 server.
Issue 1)
After each reboot I get a Kernel-EventTracing 2 error. I cannot find anything on this on the internet so I have no idea what it is.
Session "FastDocTracingSession" failed to start with the following error: 0xC0000035
I did read other accounts of this error with a different name in the quotes but still can’t tell what this is or where it is coming from.
Issue 2)
I am still getting 5 MSExchange Common 106 errors even after reregistering all of the perf counters per this page:
https://support.microsoft.com/kb/2870416?wa=wsignin1.0
One of the perf counters fails to register using the script from the link above.
66 C:\Program Files\Microsoft\Exchange Server\V15\Setup\Perf\InfoWorkerMultiMailboxSearchPerformanceCounters.xml
New-PerfCounters : The performance counter definition file is invalid.
At C:\Users\administrator.<my domain>\Downloads\script\ReloadPerfCounters.ps1:19 char:4
+    New-PerfCounters -DefinitionFileName $f
+    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo
: InvalidData: (:) [New-PerfCounters], TaskException
    + FullyQualifiedErrorId : [Server=VALIS,RequestId=71b6bcde-d73e-4c14-9a32-03f06e3b2607,TimeStamp=12/18/2014 10:09:
   12 PM] [FailureCategory=Cmdlet-TaskException] 33EBD286,Microsoft.Exchange.Management.Tasks.NewPerfCounters
But that one seems unrelated to the ones that still throw errors.
Three of the remaining five errors are (the forum is removing my spacing between the error text so it looks like a wall of text - sorry):
Performance counter updating error. Counter name is Count Matched LowFidelity FingerPrint, but missed HighFidelity FingerPrint, category name is MSExchange Anti-Malware Datacenter Perfcounters. Optional code: 3. Exception: The
exception thrown is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
   at System.Diagnostics.PerformanceCounter.InitializeImpl()
   at System.Diagnostics.PerformanceCounter.set_RawValue(Int64 value)
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)
Last worker process info : System.ArgumentException: Process with an Id of 7384 is not running.
   at System.Diagnostics.Process.GetProcessById(Int32 processId)
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
Performance counter updating error. Counter name is Number of items, item is matched with finger printing cache, category name is MSExchange Anti-Malware Datacenter Perfcounters. Optional code: 3. Exception: The exception thrown
is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
   at System.Diagnostics.PerformanceCounter.InitializeImpl()
   at System.Diagnostics.PerformanceCounter.set_RawValue(Int64 value)
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)
Last worker process info : System.ArgumentException: Process with an Id of 7384 is not running.
   at System.Diagnostics.Process.GetProcessById(Int32 processId)
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
Performance counter updating error. Counter name is Number of items in Malware Fingerprint cache, category name is MSExchange Anti-Malware Datacenter Perfcounters. Optional code: 3. Exception: The exception thrown is : System.InvalidOperationException:
The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
   at System.Diagnostics.PerformanceCounter.InitializeImpl()
   at System.Diagnostics.PerformanceCounter.set_RawValue(Int64 value)
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)
Last worker process info : System.ArgumentException: Process with an Id of 7384 is not running.
   at System.Diagnostics.Process.GetProcessById(Int32 processId)
   at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
Issue 3)
I appear to have some issues related to the healthmailboxes.
I get MSExchangeTransport 1025 errors for multiple healthmailboxes.
SMTP rejected a (P1) mail from 'HealthMailbox23b10b91745648819139ee691dc97eb6@<my domain>.local' with 'Client Proxy <my server>' connector and the user authenticated as 'HealthMailbox23b10b91745648819139ee691dc97eb6'. The Active Directory
lookup for the sender address returned validation errors. Microsoft.Exchange.Data.ProviderError
I reran setup /prepareAD to try and remedy this but I am still getting some.
Issue 4)
I am getting an MSExchange RBAC 74 error.
(Process w3wp.exe, PID 984) Connection leak detected for key <my domain>.local/Admins/Administrator in Microsoft.Exchange.Configuration.Authorization.WSManBudgetManager class. Leaked Value 1.
Issue 5)
I am getting MSExchange Assistants 9042 warnings on both databases.
Service MSExchangeMailboxAssistants. Probe Time Based Assistant for database Database02 (c83dbd91-7cc4-4412-912e-1b87ca6eb0ab) is exiting a work cycle. No mailboxes were successfully processed. 2 mailboxes were skipped due to errors. 0 mailboxes were
skipped due to failure to open a store session. 0 mailboxes were retried. There are 0 mailboxes in this database remaining to be processed.
Some research suggested this may be related to deleted mailboxes however I have never had any actual user mailboxes on this server.
If they are healthmailboxes or arbitration mailboxes that might make sense but I am unsure of what to do on this.
Issue 6)
At boot I am getting an MSExchange ActiveSync warning 1033
The setting SupportedIPMTypes in the Web.Config file was missing.
Using default value of System.Collections.Generic.List`1[System.String].
I don't know why but this forum is removing some of my spacing that would make parts of this easier to read.

Hi Eric
Yes I have uninstalled and reinstalled Exchange 2013 CU7 for the 3<sup>rd</sup> time.
I realize you said one issue per forum thread but since I already started this thread with many issues I will at least post what I have discovered on them in case someone finds their way here from a web search.
I have an existing Exchange 2007 server in the environment so I am unable to create email address policies that are defined by “recipient container”.
If I try and do so I get “You can't specify the recipient container because legacy servers are detected.”
So I cannot create a normal email address policy and restrict it to an OU without resorting to some fancy filtering.
Instead what I have done is use PS to modify extensionAttribute1 (otherwise known as Custom Attribute 1 to exchange) for all of my users.
I then applied an address policy to them and gave it the highest priority.
Then I set a default email address policy for the entire organization.
After reinstalling Exchange all of my system mailboxes were created with the internal domain name.
So issue number 3 above has not come up.
For issue number one above I have created a new thread:
https://social.technet.microsoft.com/Forums/office/en-US/7eb12b89-ae9b-46b2-bd34-e50cd52a4c15/microsoftwindowskerneleventtracing-error-2-happens-twice-at-boot-ex2013cu7?forum=exchangesvrdeploy
For issue number four I have posted to this existing thread where there is so far no resolution:
https://social.technet.microsoft.com/Forums/exchange/en-US/2343730c-7303-4067-ae1a-b106cffc3583/exchange-error-id-74-connection-leak-detected-for-key?forum=exchangesvradmin
Issue number Five I have managed to recreate and get rid of in more than one way.
If I create a new database in ECP and set the database and log paths where I want, then this error will appear.
If I create the database in the default location and then use EMS to move it and set the log path, then the error will not appear.
The error will also appear (along with other errors) if I delete the health mailboxes and let them get recreated by restarting the server or the Health Manager service.
If I then go and set the retention period for deleted mailboxes to 0 days and wait a little while, these will all go away.
So my off hand guess is that these are caused by orphaned system mailboxes.
For issue number six I have posted to this existing thread where there is so far no resolution:
https://social.technet.microsoft.com/Forums/exchange/en-US/dff62411-fad8-4d0c-9bdb-037374644845/event-1033-msexchangeactivesync-warning?forum=exchangesvrmobility
So for the remainder of this thread we can try and tackle issue number two which is the perf counters.
The exact same 5 perf counter were coming up and this had been true each time I have uninstalled and reinstalled Exchange 2013CU7.
Actually to be more accurate a LOT of perf counter errors come up after the initial install, but reloading the perf counters using the script I posted above reduces it to the same five.
Using all of your suggestions so far has not removed these 5 remaining errors either. Since there is no discernible impact other than these errors at boot I am not seriously bothered by them but as will all event log errors, I would prefer
to make them go away if possible.

SharePoint 2013 Service Pack 1 broke Explorer View (WebDAV)?

We recently installed SharePoint 2013 Service Pack 1 and have since been troubled by Explorer View. Very often Explorer View doesn't work. This error often appears:
"We're having a problem opening this location in File Explorer. Add this web site to your Trusted Sites list and try again."
The weird thing is that sometimes the Explorer View works just fine, but more often it doesn't. There's are a lot of blogs / topics about this on the internet, but they all didn't help resolve this issue. We use persistent cookies for our STS (AllowSessionCookies
== false), we've added the site to Trusted Sites, made sure WebClient service is running on the clients, cleared cookie caches, etc., etc.
Explorer View works fine when we connect to Office 365 instances. But our local farm has these problems. We use ADFS auth.
Our problems actually resemble the problems this guy had:
http://blog.skadefro.dk/2011/09/sharepoint-2010-and-webdav.html
But his fix doesn't seem to apply to us.
This all started after installing Service Pack 1, so could this be a Service Pack 1 issue?

Hi LZandman,
There is a KB article, it provides that:
Issue 2
Assume that you access the date in a SharePoint Document Library. Then, you click Open with Explorer View when you view a SharePoint Document Library in Internet Explorer 10. In this situation, the operation fails, and you receive one of the following error
messages.
Error message 2
We're having a problem opening this location in File Explorer. Add this web site to your Trusted Sites list and try again.
Notes
These issues occur only when the SharePoint server is configured for cookie-based authentication, such as SharePoint Online.
You may encounter a similar issue when you use other Web Distributed Authoring and Versioning (WebDAV) servers that are configured for cookie-based authentication.
Please take a look at :
http://support.microsoft.com/kb/2846960/en-us , and download and install the hotfix, compare the result.
I hope this helps.
Thanks,
Wendy
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Wendy Li
TechNet Community Support

TypeLoadException after install SharePoint 2013 Service Pack 1

After install SharePoint 2013 Service Pack 1 Russian I got the following error (approximate translation from Russian):
TypeLoadException: Method 'Upgrade' does not implemented in 'WorkflowServiceApplicationProxy'
Any ideas how to workaround it?

Hi,
Please post your ULS logs here.
Please remember to click 'Mark as Answer' on the answer if it helps you

Compatibility between Exchange 2007 service packs

Hi all, I have 5 servers Exchange:
- 3 Servers CAS and HUB
- 2 Servers Mailbox server in Microsoft Failover Cluster (MSCS)
Domain Controllers are all
Windows Server 2003 SP2
The versions of Exchange 2007 SP1 servers are all:
8.1 Build 240.6
I have thought about installing SP3 and RU13 in all 5 servers for Exchange, but I'm going to install SP3 and RU13 on 2 servers CAS / HUB and the following week at the other CAS / HUB server.
Finally, the following week in the two Mailbox Servers.
Is there any problem if I miss 2 servers CAS / HUB with SP3 RU13 and the other CAS / HUB in SP1, this will only be for a few days?
Is there any problem if I leave the servidors Mailbox Servers in SP1 while CAS / HUB are in SP3 RU13, this will only be for a few days?
regards
Microsoft Certified IT Professional Server Administrator

Hi Yupikaiey.
Only thing you should be concerned is if you have CAS-CAS proxy or the Mailbox Cluster part.
Your current plan looks good. Just stay alert for any uncommon issues popping up, which would normally mean due to the difference.
If you upgrade your servers in this order, you may avoid potential service interruptions.
Details below:
Version Constrains are more of between roles of 2007-2010-2013 and not between same version SPs or RUs.
Exchange 2013 Server Role Architecture
The Past: Exchange 2007 and Exchange 2010
Our goal was to make these server roles autonomous units. Unfortunately, that goal did not materialize in either Exchange 2007 or Exchange 2010. The server roles were tightly coupled along four key dimensions:
2.This also necessitated a tight versioning alignment – a down-level Hub Transport or Client Access shouldn’t communicate with a higher version Mailbox server; in some cases this was enforced (e.g., Exchange 2007 Hub Transport servers cannot deliver messages
to Exchange 2010 Mailbox servers), but in other cases they were not (e.g., an Exchange 2010 SP1 Client Access server can render data from an Exchange 2010 SP2 Mailbox server).
The versioning restriction also meant that you could not simply upgrade a single server role to take advantage of new functionality – you had to upgrade all of them.
The Present: Exchange Server 2013
If I upgrade the Mailbox server with a service pack or cumulative update, then for a given mailbox hosted on that server, all data rendering and content conversions for that mailbox will be local, thus removing version constraints and functionality issues
that arose in previous releases.
Exchange 2007 Servicing
http://technet.microsoft.com/en-in/library/dd421853(v=exchg.80).aspx
Deployment Order
Our test infrastructure guarantees that Exchange hotfixes work across multiple server roles. The order in which you apply the update rollup to the servers is not important except if you are deploying CAS-CAS proxying. Because the update rollups are not segmented
for different Exchange server roles or for specific file configurations, apply each update rollup package to all Exchange 2007 servers in your environment.
If you have multiple Active Directory sites, and if you deploy a Client Access server in the proxy sites that do not face the Internet, you must
apply the update rollup to the Internet-facing Client Access servers
and to the non-Internet-facing Client Access servers in the proxy site simultaneously. For other Exchange 2007 configurations, we recommend that you
apply the update rollup package to the Client Access servers before
you apply it to servers that are running other Exchange 2007 server roles, such as the Mailbox server role, the Hub Transport server role, and the Edge Transport server role.
Note:
Applying service packs and update rollups to clustered Mailbox servers requires specific planning and application steps. For more information about how to apply service packs to Exchange 2007 clustered Mailbox servers, see
Upgrading Clustered Mailbox Servers to Exchange 2007 SP1 or later. For more information about how to apply update rollups to Exchange 2007 clustered Mailbox servers, see
Applying Exchange 2007 Update Rollups to Clustered Mailbox Servers.
For Patching and compatibility between versions:
Determine the service pack level of Exchange.
Update rollups are service pack dependent. For example, an Update Rollup 5 package is available for Exchange 2007 and for Exchange 2007 Service Pack 1. To determine the service pack level of Exchange, examine the
ExchangeVersion property. For more information about how to view the
ExchangeVersion property and about the build number that is associated with each Exchange version, see
Exchange Server 2007: Platforms, Editions, and Versions.
References:
How to Install the Latest Service Pack or Update Rollup for Exchange 2007
Exchange Server Updates: build numbers and release dates
We are looking at doing the roll-up to SP3
Coexistence of Exchange2007 SP1 and Exchange 2007 SP3
Regards,
Satyajit
Please “Vote As Helpful”
if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

Error when uninstalling App-V RDS client: Product: Microsoft Application Virtualization (App-V) Client for Remote Desktop Services 5.0 Service Pack 2 x64 -- Error 1324. The folder path 'C:' contains an invalid character

Issue: experienced when attempting to uninstall the App-V 5.0 SP2 RDS client.
Event Log: Product: Microsoft Application Virtualization (App-V) Client for Remote Desktop Services 5.0 Service Pack 2 x64 -- Error 1324. The folder
path 'C:' contains an invalid character
Symptoms (when in this current state):
Unable to uninstall the SP2 client
You can upgrade the client (via hotfix) and uninstall the hotfix, but you will not be able to remove the SP2 client
AppvVfs filter driver will not create an instance, therefore applications will not be able to read into existing streamed VFS content, or trigger sparse files to stream content. (you can still stream the content via other means, like the UI or powershell)
Because of the AppvVfs filter driver not instantiating, applications that depend on licences that exist in VFS will not be able to be read causing certain applications to react as if the license does not exist or is an incorrect format

Resolution:
Check for the existence of a hidden folder named %appdata% in the C:\Program Files\Microsoft Application Virtualization\Client folder. (You will need to un-check the folder options box in windows explorer for "Hide
protected operating system files" to see it)
If the hidden %appdata% folder exists, delete it.
Proceed to uninstall the App-V client
After a clean uninstall and removal of remnants of the client, reinstall the client again and apply the latest hotfix available (Hotfix 2 for SP2 at a minimum).

Windows Server 2008 R2 Service Pack 1 installation failed with error code 0x800f0a12

Hello,
I'm facing problem to install windows server 2008 R2 SP1. I cannot install SP1. In this server have running Exchange 2010 server. to update Win2008 R2 SP1 facing the following error:
1. Service Pack installation failed with error code 0x800f0a12.
2. Installation Failure: Windows failed to install the following update with error 0x80070643: Windows Server 2008 R2 Service Pack 1 for x64-based Systems (KB976932).
Please suggest

Please run the system update readiness tool.
http://windows.microsoft.com/en-us/windows7/What-is-the-System-Update-Readiness-Tool?SignedIn=1
Then post the complete contents of;
%SYSTEMROOT%\Logs\CBS\CheckSUR.log
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Exchange 2013 Services Will Not Start

Server is a new setup with Server 2012 Standard. Installed Exchange 2013. Got everything up and running correctly.
Installed MySQL in prep for another application that required MySQL. MySQL installed C++ 2010 and required CGI for IIS. E-mail immediately stopped flowing. Restarted the server and now to just get to the log in screen takes 30+ minutes and most of the Exchange
services fail to start.
I removed MySQL and the C++ 2010. Ran a repair on C++2012 and still takes forever to get to the log in screen and the Exchange services are still failing.
Any ideas on what is going on?
Level Date and Time
Source Event ID
Task Category
Error 11/7/2012 2:51:14 PM
Service Control Manager 7031
None The Microsoft Exchange Information Store service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.
Error 11/7/2012 2:51:14 PM
Service Control Manager 7023
None "The Microsoft Exchange Information Store service terminated with the following error:
%%2414"
Information 11/7/2012 2:51:14 PM
Service Control Manager 7036
None The Microsoft Exchange Information Store service entered the stopped state.
Error 11/7/2012 2:51:14 PM
Service Control Manager 7031
None The Microsoft Exchange Frontend Transport service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.
Error 11/7/2012 2:51:06 PM
Service Control Manager 7031
None The Microsoft Exchange Information Store service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.
Error 11/7/2012 2:51:06 PM
Service Control Manager 7023
None "The Microsoft Exchange Information Store service terminated with the following error:
%%2414"
Information 11/7/2012 2:51:06 PM
Service Control Manager 7036
None The Microsoft Exchange Information Store service entered the stopped state.
Error 11/7/2012 2:51:05 PM
Service Control Manager 7031
None The Microsoft Exchange Throttling service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.
Information 11/7/2012 2:51:01 PM
Service Control Manager 7036
None The Software Protection service entered the stopped state.
Error 11/7/2012 2:50:57 PM
Service Control Manager 7031
None The Microsoft Exchange Information Store service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.
Error 11/7/2012 2:50:57 PM
Service Control Manager 7023
None "The Microsoft Exchange Information Store service terminated with the following error:
%%2414"
Information 11/7/2012 2:50:57 PM
Service Control Manager 7036
None The Microsoft Exchange Information Store service entered the stopped state.
Information 11/7/2012 2:50:56 PM
Service Control Manager 7036
None The Device Setup Manager service entered the stopped state.
Information 11/7/2012 2:50:56 PM
Service Control Manager 7036
None The Windows Modules Installer service entered the stopped state.
Information 11/7/2012 2:50:51 PM
Service Control Manager 7036
None The Portable Device Enumerator Service service entered the stopped state.
Error 11/7/2012 2:50:48 PM
Service Control Manager 7031
None The Microsoft Exchange Information Store service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.
Error 11/7/2012 2:50:48 PM
Service Control Manager 7023
None "The Microsoft Exchange Information Store service terminated with the following error:
%%2414"
Information 11/7/2012 2:50:48 PM
Service Control Manager 7036
None The Microsoft Exchange Information Store service entered the stopped state.
Error 11/7/2012 2:50:47 PM
Service Control Manager 7031
None The Microsoft Exchange Throttling service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.
Error 11/7/2012 2:50:46 PM
Service Control Manager 7031
None The Microsoft Exchange Mailbox Transport Delivery service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.
Error 11/7/2012 2:50:39 PM
Service Control Manager 7031
None The Microsoft Exchange Information Store service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.
Error 11/7/2012 2:50:39 PM
Service Control Manager 7023
None "The Microsoft Exchange Information Store service terminated with the following error:
%%2414"
Information 11/7/2012 2:50:39 PM
Service Control Manager 7036
None The Microsoft Exchange Information Store service entered the stopped state.
Information 11/7/2012 2:50:31 PM
Service Control Manager 7036
None The Windows Remote Management (WS-Management) service entered the running state.
Error 11/7/2012 2:50:31 PM
Service Control Manager 7031
None The Microsoft Exchange Information Store service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.
Error 11/7/2012 2:50:31 PM
Service Control Manager 7023
None "The Microsoft Exchange Information Store service terminated with the following error:
%%2414"
Information 11/7/2012 2:50:31 PM
Service Control Manager 7036
None The Microsoft Exchange Information Store service entered the stopped state.
Information 11/7/2012 2:50:31 PM
Service Control Manager 7036
None The User Access Logging Service service entered the running state.
Warning 11/7/2012 2:50:31 PM
Microsoft-Windows-WinRM 10154
None "The WinRM service failed to create the following SPNs: WSMAN/mail.XXXXXXX.net; WSMAN/mail.
Additional Data
The error received was 8344: %%8344.
User Action
The SPNs can be created by an administrator using setspn.exe utility."
Information 11/7/2012 2:50:31 PM
Microsoft-Windows-WinRM 10148
None "The WinRM service is listening for WS-Management requests.
User Action
Use the following command to see the specific IPs on which WinRM is listening:
winrm enumerate winrm/config/listener"
Information 11/7/2012 2:50:28 PM
Service Control Manager 7036
None The Software Protection service entered the running state.
Error 11/7/2012 2:50:28 PM
Service Control Manager 7031
None The Microsoft Exchange Throttling service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 5000 milliseconds: Restart the service.

It still applies to Exchange 2013 SP1 and Server 2012 R2.
Thank you so much. You really saved my day!

Vista Service Pack 2 install error message and Realtek incompatibility

Just want to inform that service pack 2 install gave me an error message when I installed it on a clean rebuild of my Toshiba laptop. Something about an incompatible driver. As I had already installed the latest drivers from Toshiba pages, I choose the 'ignore and continue' action at install, and the update successfully completed.
I then ran the Windows Upgrade advisor utility (just search a Microsoft website to find it) which checks for hardware/driver compliance with Vista.
Their report says that the Realtek RTL8187B wireless adapter driver has an issue with Vista, and recommends that the latest driver be installed. Since I do have the latest Toshiba driver installed, what is the procedure to follow?
The wifi connection with this laptop functions well, with the only 'problem' being a 45 second delay when waking up from sleep mode to being able to open a new web page. This is the time it takes to establish a connection to my router/modem.

> Their report says that the Realtek RTL8187B wireless adapter driver has an issue with Vista, and recommends that the latest driver be installed. Since I do have the latest Toshiba driver installed, what is the procedure to follow?
You could try the Realtek WLan driver from the Realtek driver page.
There you can find the latest Realtek drivers for different Realtek chips.
But to be honest I would not be worried about this massage.
Something like that can happens always after any installations of the Microsoft service packs.
I remember that many drivers were not supported by SP1 but they ran properly
So take it easy ;)

FYI: TrendMicro antivirus prevents Transport Service from starting after installing Echange Server 2013 Service Pack 1

I installed Exchange Server 2013 SP1 in my test environment. After that mail flow between internal and external mail servers completely stopped. In the end I discovered that Transport Service on both of the mailbox servers refused to start (or, to be more
exact, stopped shortly after starting).
The following events appeared in the System event log:
Event ID 1052 (error)
Source: MSExchange Extensibility
Message: Failed to create agent factory for the agent 'ScanMail SMTP Receive Agent' with error 'Failed to create type 'TrendMicro.SMEX.hookE12TransportAgent.hookE12SmtpReceiveAgentFactory' from assembly 'C:\Program Files\Trend Micro\Smex\hookE12TransportAgent.dll'
due to error 'type not found'.'. Please verify the corresponding transport agent assembly and dependencies with correct version are installed.
Event ID 16023 (error)
Source: MSExchangeTransport
Message: Microsoft Exchange couldn't start transport agents. The Microsoft Exchange Transport service will be stopped. Exception details: Failed to create type 'TrendMicro.SMEX.hookE12TransportAgent.hookE12SmtpReceiveAgentFactory' from assembly 'C:\Program
Files\Trend Micro\Smex\hookE12TransportAgent.dll' due to error 'type not found'. : Microsoft.Exchange.Data.ExchangeConfigurationException: Failed to create type 'TrendMicro.SMEX.hookE12TransportAgent.hookE12SmtpReceiveAgentFactory' from assembly 'C:\Program
Files\Trend Micro\Smex\hookE12TransportAgent.dll' due to error 'type not found'.
   at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.FactoryTable.CreateAgentFactory(AgentInfo agentInfo)
   at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.FactoryTable..ctor(IEnumerable agents, FactoryInitializer factoryInitializer)
   at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.RuntimeSettings..ctor(MExConfiguration config, String agentGroup, FactoryInitializer factoryInitializer)
   at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.MExRuntime.Initialize(String configFile, String agentGroup, ProcessTransportRole processTransportRole, String installPath, FactoryInitializer factoryInitializer)
   at Microsoft.Exchange.Transport.Extensibility.AgentComponent.Load()
Event ID 701 (informational)
Source: MSExchangeTransport
Message: The service will be stopped. Reason: Microsoft.Exchange.Transport.TransportComponentLoadFailedException: Loading of component 'SmtpReceiveAgents' failed. ---> Microsoft.Exchange.Transport.TransportComponentLoadFailedException: The agent component
failed to load. ---> Microsoft.Exchange.Data.ExchangeConfigurationException: Failed to create type 'TrendMicro.SMEX.hookE12TransportAgent.hookE12SmtpReceiveAgentFactory' from assembly 'C:\Program Files\Trend Micro\Smex\hookE12TransportAgent.dll' due to
error 'type not found'.
   at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.FactoryTable.CreateAgentFactory(AgentInfo agentInfo)
   at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.FactoryTable..ctor(IEnumerable agents, FactoryInitializer factoryInitializer)
   at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.RuntimeSettings..ctor(MExConfiguration config, String agentGroup, FactoryInitializer factoryInitializer)
   at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.MExRuntime.Initialize(String configFile, String agentGroup, ProcessTransportRole processTransportRole, String installPath, FactoryInitializer factoryInitializer)
   at Microsoft.Exchange.Transport.Extensibility.AgentComponent.Load()
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Transport.Extensibility.AgentComponent.Load()
   at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.RunADOperation(ADOperation adOperation, Int32 retryCount)
   at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.TryRunADOperation(ADOperation adOperation, Int32 retryCount)
   at Microsoft.Exchange.Transport.SequentialTransportComponent.Load()
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Transport.SequentialTransportComponent.Load()
   at Microsoft.Exchange.Transport.Components.Activate()
The reason for that behavior was TrendMicro ScanMail for Exchange 11. Seems that it was unable to work with the new SP properly and prevented the entire Transport Service from starting. Uninstallation of the antivirus eliminated the issue.

Actually, you can just disable the agents until TrendMicro releases a patch and then enable them again:
http://community.trendmicro.com/...
BTW, a similar problem (high CPU utilization and services not starting) is hitting the AVG package:
http://forums.avg.com/..
Step by Step Screencasts and Video Tutorials

Exchange 2013 Services pack 1 installation Error

Similar Messages

Maybe you are looking for