OWA Exchange 2013 SP1 Security Update KB3011140 December 2014

After performing this update on our server, I noticed now users can no longer recover items from deleted items in OWA. The page always errors out now.
The KB installed was KB3011140
something went wrong
Sorry, we can't get that information right now. Please try again later. If the problem continues, contact your helpdesk.
X-OWA-Error: ClientError;exMsg=Sys.ArgumentException: Value does not fall within the expected range.Parameter name: Unknown type _d.$Vq was requested;file=$7CD@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.1.mouse.js:1:1170608_t.PopoutStartupViewModelFactory.prototype.$E/<@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.1.mouse.js:1:1171022_a.$Z0.prototype.$5V3/<@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:294125_a.$2r.$5e5@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:601482_a.$2r.$iS@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:600669_a.$Sd.$9lW@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:369272$1mX@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:27237$4pt@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:27789_js.$J.prototype.$6Kk@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:32733Function.createDelegate/<@https://whatever.com/OWA/prem/15.0.847.34/scripts/preboot.js:34:39109_a.$2r.$5e5@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:601482_a.$2r.$iS@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:600669_a.$Sd.$9lW@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:369272$1mX@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:27237$2gl/s@https://whatever.com/OWA/prem/15.0.847.34/scripts/boot.0.mouse.js:91:28216:1170608
X-OWA-Version: 15.0.847.34
X-FEServer: SERVERNAME
X-BEServer: null
Date: 1/2/1601 3:22:42 PM

Hi,
From the above description, "Something went wrong" error shows an incorrect date. The date information is calculated based on the date of the Exchange server to which the user is connected. In some scenarios, such as network connectivity failure,
the Outlook Web App client-side script is unable to connect to the server to obtain the correct date. When this occurs, a generic "1/2/1601" date is used. In order to resolve this issue, you need to install the Cumulative Update 6 for Exchange
Server 2013.
For more information, here is a KB for your reference.
"Something went wrong" error in Outlook Web App may show an incorrect date
https://support.microsoft.com/kb/2961715?wa=wsignin1.0
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Similar Messages

Notice field from a task in OWA (Exchange 2013 SP1) and Outlook 2013 are not the synchronizend correclty

Hello,
if I create a new task from OWA, I can't see the the information of the notice field in Outlook 2013
But when I create a new task in Outlook 2013, I can see the Information of the notice field in OWA and then when I edit this task in OWA the information field will be empty after Change this field there.
This is a very strange issue, please help!
Regards
Bernd

Hi,
To work around this issue, use one of the following methods to verify the quota status of mailboxes.
Method 1: Use Exchange Admin Console (EAC)
If you want to verify the status of individual mailbox quotas, follow these steps: 1.Log on to EAC by using a user account that is assigned at least the Mail Recipients role.
2.In the feature pane, click recipients. A list of mailboxes is displayed.
3.Select the mailbox of which you want to verify the quota status, and then click the Edit button on the toolbar.
4.Click mailbox usage. The mailbox quota usage is displayed.
Method 2: Use Exchange Management Shell
If you want to verify the status of individual mailbox quota, run the following command in Exchange Management Shell:
Get-MailboxStatistics DisplayName | ft *quota*,*size -AutoSize –Wrap
If you want to verify the status of the mailbox quota for all the mailboxes that are hosted on a database, run the following command:
Get-MailboxStatistics -Database DatabaseName | ft displayname,*quota*,*size -AutoSize –Wrap
Thanks,
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]
Simon Wu
TechNet Community Support

Exchange 2013 SP1 & Custom OWA Theme

On Friday of last week we updated from Exchange 2013 CU2 to Exchange 2013 SP1. Since updating our custom OWA theme no longer works. We configured it according to the following guide:
http://technet.microsoft.com/en-us/library/bb201700(v=exchg.150).aspx
The theme we customized was stored in the following location:
\Client Access\OWA\version\Owa2\resources\themes\"title of our theme"
Themes no longer appear to be stored in this location and I am uncertain as to where they have moved and how to apply them. Has anyone else run into this issue?

Hi,
Can we try to re-importing the theme again?
Thanks
Mavis
Mavis Huang
TechNet Community Support

Cannot write email body in OWA with Exchange 2013 SP1 CU6

Hi,
I have a problem with Exchange 2013 SP1 with CU6.
All of OWA user cannot write in the body of email. They can write the Object and the recipient but they cannot select body and write the body message. We have try with multiple Web brother and desactivate all Add-on but the problem still there...
The only way that works is to respond to an email, and in that case, it's working, we can write normally in the body of email.
Have you an idea ?
Thanks in advance!
Sebastien

Hi,
After contacting Microsoft support, we have found the solution.
The problem appear after we have recently install the patch described in this KB 2997209:
https://support.microsoft.com/kb/2997209?wa=wsignin1.0
But on 2013 Mailbox Server, Echange is not installed in the default path C:\ but on D:\
So we have to manually copy the content of folder D:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\prem\15.0.995.29 in the folder 15.0.995.31 (MAKE a BACKUP of FOLDER BEFORE!)
No need to reboot, or restart IIS, it's working after that!
@+
Sébastien

Exchange 2013 Sp1 says that it is 'Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup'

So, I have decompressed my brand new download of Exchange 2013 SP1. This was downloaded from the link at the bottom of the post.
So to start my upgrade I have tried to start by running the schema preparation which then advises me that I am welcomed to:
'Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup'
Is this poor QA or was the incorrect file uploaded?
http://www.microsoft.com/en-us/download/details.aspx?id=41994

Hello,
Powershell need full path to file you want to run.
So you should run .\setup.exe instead of just setup.exe.
Hope this help.
Regards, Pavel.

Migrating a mailbox cross forest from exchange 2013 Sp1 to exchange 2010 SP2 Update rollup 8

I can migrate a mailbox fine from exchange 2010 sp2 update rollup 8 to exchange 2013 sp1 or Cu2.
I was testing today migrating cross forest from 2010 sp2 udpate rollup 8 back to exchange 2010 sp2 but I get the below error. Is this even possible? I cannot find any documentation on this scenario yet.
VERBOSE: [21:52:47.622 GMT] New-MoveRequest : The remote server doesn't support client 'casservername.domain.com'
version (14.2.341.0 caps:05FEFF). Missing functionality: 'TenantHint'.
VERBOSE: [21:52:47.637 GMT] New-MoveRequest : Admin Audit Log: Entered Handler:OnComplete.
The remote server doesn't support client 'casservername.domain.com' version (14.2.341.0 caps:05FEFF). Missing functionality: 'TenantHint'.
+ CategoryInfo : NotSpecified: (0:Int32) [New-MoveRequest], RemotePermanentException
+ FullyQualifiedErrorId : 782D22F0,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest

Hi Steve,
I'm a little confused what you are saying. Here is my understanding:
When you migrate mailboxes from Exchange 2013 back to Exchange 2007, the above error occurs.
If I have misunderstood your concern, please let me know.
For migrating mailboxes back to Exchange 2007, there is a simple and straightforward method. Please use the New-MailboxExportRequest cmdlet to convert all mailboxes into pst files. And then use the Import-Mailbox cmdlet to import all pst files into Exchange
2007.
Hope it helps.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Viewing attachments in Public Folders in Exchange 2013 SP1 OWA

Hello!
Tell me please should the file preview work in Public Folders (for example for docx files) in OWA 2013 SP1? This file can be easily opened in MS Word but clicking the
Preview leads to the following error:
Thank you in advance,
Michael

Hi Jessie,
Thank you for your help!
"To preview these files in Inbox in OWA, Exchange 2013 could has its own process to achieve this function. I tried it in Exchange 2013 CU1 environment, it is also working when previewing these files in the Inbox
in OWA." - that's the only possible explanation... but it means this article is not correct:
http://technet.microsoft.com/library/2591b1be-92c4-4192-9f5e-e4e6b319170a"
"By default, the following file types are displayed
using Office Web Apps Server:
Word documents (doc, docx, dotx, dot, dotm extensions)
Excel documents (xls, xlsx, xlsm, xlm, xlsb extensions)
PowerPoint documents (ppt, pptx, pps, ppsx, potx, pot, pptm, potm, ppsm extensions)
...cause I can preview files without Office Web Apps Server. Why there's no corresponding information on technet?
To put it mildly, documentation for Exchange 2013 is rather strange...
Regards,
Michael

Exchange 2013 SP1 | Another HTTP 500.0.0 Error

Help!
We are in the middle of migrating from Exchange 2010 SP3 to Exchange 2013 SP1 and we are being plagued with HTTP 500 errors on every Exchange 2013 server now.
I have two Client Access servers installed (EXCHFE01 & EXCHFE02) and one backend mailbox server (EXCHMB03) with the Client Access role also installed (for troubleshooting purposes). Once I get everything working I'll install two backend 2013 servers
with the mailbox role only for production (load-balanced, clustered, etc). I still have two Exchange 2010 mailbox servers left since one has a single large mailbox left on it and the other hosts public folders. I'll get to migrating those later. All Exchange
2013 servers are running Windows Server 2012. All are on the same LAN and no firewalls are between them.
On all three 2013 servers (EXCHFE01, EXCHFE02, EXCHMB03) I'm getting the dreaded HTTP 500 error whether I try to get to OWA or ECP. This did work at one point where I could at least login to the mailbox server (EXCHMB03) and migrate all my mailboxes over
to it. Sometime this morning after the two Client Access servers were installed the mailbox server stopped working (HTTP 500 errors). This is very frustrating because I can't even login to a console to manage Exchange from any server at this point.
Both Client Access servers aren't really showing anything of value in the event logs or the IIS logs. The mailbox server (EXCHMB03) does show the following event 3002:
Protocol /Microsoft-Server-ActiveSync failed to process request from identity NT AUTHORITY\SYSTEM. Exception: Microsoft.Exchange.Security.Authentication.BackendRehydrationException: Rehydration failed. Reason: Source server 'NT AUTHORITY\SYSTEM' does not have token serialization permission.
at Microsoft.Exchange.Security.Authentication.BackendRehydrationModule.ProcessRequest(HttpContext httpContext)
at Microsoft.Exchange.Security.Authentication.BackendRehydrationModule.OnAuthenticateRequest(Object source, EventArgs args).
...and I get the following when I run the Exchange Management Shell tool on the same mailbox server (along with lots of other red HTML text):
More Information:
This error means that there was a problem while processing the request. The request was received by the Web server, but during processing a fatal error occurred, causing the 500 error.
The Client Access servers show the following errors:
Performance counter updating error. Counter name is Location cache update time, category name is MSExchange Active Manager Client. 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 4040 is not running.
at System.Diagnostics.Process.GetProcessById(Int32 processId)
at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
Processes running while Performance counter failed to update:
888 svchost
264 smss
532 conhost
2576 Microsoft.Exchange.UM.CallRouter
1596 WMSvc
3932 dllhost
4020 svchost
2308 dwm
5060 taskhostex
844 svchost
1972 Microsoft.Exchange.Directory.TopologyService
1228 inetinfo
1316 vmtoolsd
3896 svchost
780 svchost
1580 rundll32
1668 mqsvc
816 dwm
3840 slui
3532 rdpclip
3980 WmiPrvSE
4200 SppExtComObj
4288 winlogon
2140 SMSvcHost
676 svchost
1564 svchost
1296 Microsoft.Exchange.Diagnostics.Service
1472 Microsoft.Exchange.ServiceHost
1204 svchost
1292 ServerManagerLauncher
488 winlogon
664 svchost
572 lsass
3236 dllhost
2972 WmiPrvSE
4484 w3wp
388 csrss
1600 rundll32
564 services
1260 msdtc
5032 sppsvc
1448 MSExchangeHMHost
824 LogonUI
4204 VSSVC
2524 userinit
2700 MSExchangeFrontendTransport
1708 SMSvcHost
728 svchost
460 wininit
904 svchost
992 svchost
4996 TSTheme
4240 slui
4904 taskhost
452 csrss
4340 csrss
4 System
1164 spoolsv
1988 slClient
2760 MSExchangeHMWorker
0 Idle
Performance Counters Layout information: FileMappingNotFoundException for category MSExchange Active Manager Client : Microsoft.Exchange.Diagnostics.FileMappingNotFoundException: Cound not open File mapping for name Global\netfxcustomperfcounters.1.0msexchange active manager client. Error Details: 2
at Microsoft.Exchange.Diagnostics.FileMapping.OpenFileMapping(String name, Boolean writable)
at Microsoft.Exchange.Diagnostics.PerformanceCounterMemoryMappedFile.Initialize(String fileMappingName, Boolean writable)
at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetAllInstancesLayout(String categoryName)
... and...
A transient failure has occurred. The problem may resolve itself. Diagnostic information:
Microsoft.Exchange.Data.DataSourceOperationException: The request failed. The remote server returned an error: (503) Server Unavailable. ---> Microsoft.Exchange.WebServices.Data.ServiceRequestException: The request failed. The remote server returned an error: (503) Server Unavailable. ---> System.Net.WebException: The remote server returned an error: (503) Server Unavailable.
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.Exchange.WebServices.Data.EwsHttpWebRequest.Microsoft.Exchange.WebServices.Data.IEwsHttpWebRequest.GetResponse()
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
--- End of inner exception stack trace ---
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request)
at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ValidateAndEmitRequest(IEwsHttpWebRequest& request)
at Microsoft.Exchange.WebServices.Data.ExchangeService.InternalFindFolders(IEnumerable`1 parentFolderIds, SearchFilter searchFilter, FolderView view, ServiceErrorHandling errorHandlingMode)
at Microsoft.Exchange.WebServices.Data.ExchangeService.FindFolders(FolderId parentFolderId, SearchFilter searchFilter, FolderView view)
at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.InvokeServiceCall[T](Func`1 callback)
--- End of inner exception stack trace ---
at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.InvokeServiceCall[T](Func`1 callback)
at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.GetOrCreateFolderCore(String folderName, FolderId parentFolder, Func`1 creator)
at Microsoft.Exchange.Data.Storage.Management.AsyncOperationNotificationDataProvider.GetDefaultFolder()
at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.<>c__DisplayClass1b`1.<InternalFindPaged>b__13()
at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.InvokeServiceCall[T](Func`1 callback)
at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.<InternalFindPaged>d__21`1.MoveNext()
at Microsoft.Exchange.Data.Storage.Management.AsyncOperationNotificationDataProvider.<GetNotificationDetails>d__4.MoveNext()
at System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext()
at Microsoft.Exchange.Servicelets.CertificateNotificationServicelet.RemoveAllNotification()
at Microsoft.Exchange.Servicelets.CertificateNotificationServicelet.UpdateDataInMbx(List`1 certificates)
at Microsoft.Exchange.Servicelets.CertificateNotificationServicelet.Work()
I've tried all sorts of recommended fixes but none have worked so far:
ADSIEdit and remove msExchCanaryData0 data
Reinstall Exchange multiple times
Rebooted multiple times
This article: http://social.technet.microsoft.com/Forums/exchange/en-US/08d3777c-dc03-4411-8c87-7db37d2f406a/exchange-2013-owa-login-error-http-500?forum=exchangesvrclients
Rebooted DCs multiple times (no exchange servers are DCs)
I'm sure I've left out a few troubleshooting steps since I've been working at this for two days. Can anybody offer any advice? I'm at my wits end here...

Hi,
Please check whether the mail.mydomain.com is pointed to your Exchange 2010 or Exchange 2013. Please run the following command to check your OWA virtual directores and ECP virtual directories:
Get-OwaVirtualDirectory -ShowMailboxVirtualDirectories | Select Identity,name,Internalurl,ExternalUrl,*auth*
Get-EcpVirtualDirectory -ShowMailboxVirtualDirectories | Select Identity,name,Internalurl,ExternalUrl,*auth*
In IIS manager > Default Web Site, please make sure Anonymous Authentication is Enabled in Authentication. Confirm that "Require SSL" is checked on the SSL Settings of the default web site.
Regards,
Winnie Liang
TechNet Community Support

ActiveSync is not working properly after migrating to new Exchange 2013 SP1 server?!

Few weeks ago we have added new Exchange 2013 SP1 onto our existing Exchange 2007 environment. I have migrated my mailbox to the new Ex2013 server. Everything (send/receive - internally/externally, OWA, OutlookAnywhere) for me and the existing Ex2007
users works fine. The only thing I have trouble with is the ActiveSync! After migrating to the new Ex2013 server my phone stops getting new emails…, existing Ex2007 users don’t have any problems with their mobile phones.
I did ActiveSync test for my user account with ActiveSync Tester and here is what I have:
As you can see from the error above ActiveSync Tester detects ActiveSync on Ex2013 server however something wrong there with form-based auth?! I can’t see any differences in settings for ActiveSync virtual folders in Ex2007 and Ex2013
virtual folders?!
What I’m missing here?! Please help.

Check if the Exchange Servers group does not have the appropriate permission to the mailbox object in Active Directory.
To check whether inheritance is disabled on the user:
1.Open Active Directory Users and Computers.
2.On the menu at the top of the console, click View > Advanced Features.
3.Locate and right-click the mailbox account in the console, and then click Properties.
4.Click the Security tab.
5.Click Advanced.
6.Make sure that the check box for "Include inheritable permissions from this object's parent" is selected.
Ref:
http://technet.microsoft.com/en-us/library/dd439375(v=exchg.80).aspx
Also check the Virtual directory authentication
Microsoft-Server-ActiveSync
•Basic authentication
•SSL required
•Requires 128-bit encryption
Ref:
http://technet.microsoft.com/en-us/library/gg247612(v=exchg.150).aspx
Check the IIS log if you are able to find any error message on it
Exchange Queries

OWA (Exchange 2013) on iOS 8

We've been experiencing a few problems in OWA with devices where people have upgraded to iOS 8.0.2 and 8.1
For example, the calendar does not display any events, nor does it display any shared calendars on the left hand side.
Admittedly, we are still on Exchange 2013 SP1 mainly because we are in a 2007 mixed environment and CU6 would give us more than a few headaches.
Having looked through the KB articles for CU5 and CU6, there doesn't seem to be anything that would directly relate to changes to the rendering that could alleviate this problem.
Has anyone else experienced this and does anyone know if either of the CUs would resolve the issue?
Thanks
Andy

Not sure if its related but my exchange server OWA also took a dump. I reinstalled the entire server because hey worked before and now it doesn't. -- Only thing could be my custom code that I injected into OWA virtual directories right? right?! Anyway long
story short I didn't grab a snapshot/backup. So after importing and recreating everything same problem! Turns out Chrome has removed PopupModeDialog -- look into if Safari has done the same or if they directly use their most updated framework.
This was removed from Chrome earlier this month.
Custom code for the fix is here, although I have not tested it. I am waiting for CU7, or a chrome update.
http://windowssystemspecialist.blogspot.ie/2014/10/fixing-blank-calendar-with-chrome-38.html
Let me know!
Bug is listed here:
https://productforums.google.com/forum/#!topic/chrome/4fns56FokxY%5B1-25-false%5D
Mike k

Exchange 2013-SP1/Outlook 2013 connectivity issue.

We couldn't make Outlook 2013 (latest updates) to connect to our Exchange 2013-SP1 through the Internet.
Any PC inside the LAN (on the domain or outside the domain) can connect normally.
Any PC outside the LAN (WAN) cannot connect, it keep showing this error:
"The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
OWA is working fine from the WAN, smartphones (Android & Apple) are also working fine from the WAN.
Port 443 is open on the firewall.
So what we are missing!

Hi,
Firstly, I'd like to say, in Exchange 2013 SP1, Outlook 2013 SP1 clients may use MAPI over HTTP to connect to the server.
Before going further, let's confirm if they use MAPI over HTTP: Get-OrganizationConfig | FL MapiHttpEnabled
If the value of the above property is true, I recommend the following troubleshooting:
1. Check if your Exchange 2013 SP1 server is running on Windows Server 2012 R2.
2. Check MAPI virtual directory settings: get-MapiVirtualDirectory |fl
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

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.

Error while adding member to the dag in exchange 2013 sp1

I have Windows Server 2012 Std Edition with Exchange 2013 SP1 and get the following error while adding member to the dag either i do it using EAC or the powershell
Senior Technical Consultant, MDS Computers

When running set-databaseavailabilitygroup Exchange-dag without parameters, it crashes again:
[PS] C:\Windows\system32>Set-DatabaseAvailabilityGroup exchange-dag
WARNING: An unexpected error has occurred and a Watson dump is being generated: Some or all identity references could not be translated. Some or all identity references could not be translated.
+ CategoryInfo : NotSpecified: (:) [Set-DatabaseAvailabilityGroup], IdentityNotMappedException
+ FullyQualifiedErrorId : System.Security.Principal.IdentityNotMappedException,Microsoft.Exchange.Management.Syste
mConfigurationTasks.SetDatabaseAvailabilityGroup
+ PSComputerName : <server>
Also, this is logged in the eventlog:
Watson report about to be sent for process id: 7424, with parameters: E12, c-RTL-AMD64, 15.00.0847.032, w3wp#MSExchangePowerShellAppPool, M.Exchange.Management, M.E.M.C.FileShareWitness.Create, S.S.Principal.IdentityNotMappedException, 3e5c, 15.00.0847.031.
ErrorReportingEnabled: True
Definitely looks like a problem creating the filewitness share.
Frank.

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 Installation Errors I Cannot Resolve

Good Afternoon All -
Note: I updated this post an hour after posting. Still no solution, but please see updated info at end of this post)
I'm trying to introduce Exchange into an existing, small environment. The server I'm trying to install it onto is an SBS 2011 server (single server.) Even though SBS comes with Exchange, I found out that it's installation was corrupted and someone
had attempted to uninstall it before. Yes, it's being installed onto a server with a DC. I considered creating a Hyper-V VM on the server for Exchange, but thought it may be better to try to install directly onto server instead.
Before I started, I made sure all Exchange data had been removed. I checked for and deleted (if present) all Exchange-related objects in ADSI, ADU&C, files, and registry entries.
When I try to install Exchange 2013 SP1, I get the below errors. I know that some are easily resolved by installing pre-requisites - however - others aren't - especially the pending reboot one. I've restarted the server many times when making
changes or applying various updates and still get flagged to restart during installation. I've tried the SBS 2011 repair disc as well, but had many issues with it. In all honesty, the whole server needs to be wiped and re-installed, but
cannot do at this point.
Besides the errors below, I've zipped up the ExchangeSetupLogs folder and placed them in the link below. Also below are system specs. The only edit I made in them is a find/replace for server and domain name.
ExchangeSetupLogs Folder
System Specs
Xeon E31270 3.4Ghz
16gb RAM
Windows Server 2011 SBS x64 (Domain Controller Role Installed & Used)
C:\ - RAID 1 = 500gb
D:\ - SATA HDD = 320gb
E:\ - SATA HDD = 320GB
Should I perhaps try to install to a VM on the server or think that would use too many unnecessary resources?
Any help would be appreciated - Thanks!
Error:
This computer requires the update described in Microsoft Knowledge Base article KB2619234 (http://go.microsoft.com/fwlink/?LinkId=262359).
Without this update, the Outlook Anywhere feature may not work reliably.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.Win7RpcHttpAssocCookieGuidUpdateNotInstalled.aspx
Error:
There is a pending reboot from a previous installation of a Windows Server role or feature. Please restart the computer and then
run Setup again.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.PendingRebootWindowsComponents.aspx
Error:
The Windows component RSAT-Clustering isn't installed on this computer and needs to be installed before Exchange Setup can begin.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.RsatClusteringInstalled.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:
An unsupported operating system was detected. Exchange Server 2013 Client Access, Mailbox, and Edge Transport server roles support
Windows Server 2008 R2 SP1 or later and Windows Server 2012.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ValidOSVersion.aspx
Warning:
Installing Exchange Server on a domain controller will elevate the permissions for Exchange Trusted Subsystem to domain administrators.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarningInstallExchangeRolesOnDomainController.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
Ben K.
UPDATE
I just tried fixing a few things and tried again. Still no luck. Below is what I changed as well as the errors received. Only option was Retry. Can I just not install it onto this environment?
What I Changed
Installed Unified Comm Managed API 4.0 (Required Uninstalling Speech Analysis app before it would install)
Installed KB2619234 for Outlook Anywhere
Installed 12 updates - Server fully patched
Exchange Setup Errors
Error:
An unsupported operating system was detected. Exchange Server 2013 Client Access, Mailbox, and Edge Transport server roles support
Windows Server 2008 R2 SP1 or later and Windows Server 2012.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ValidOSVersion.aspx
Warning:
Installing Exchange Server on a domain controller will elevate the permissions for Exchange Trusted Subsystem to domain administrators.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarningInstallExchangeRolesOnDomainController.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
Thanks Guys -

Hi,
Agree. Windows Server 2011 SBS x64 can be the problem.
Thanks,
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]
Simon Wu
TechNet Community Support

OWA Exchange 2013 SP1 Security Update KB3011140 December 2014

Similar Messages

Maybe you are looking for