Exchange 2013 SP1 users not receiving quota warning email message

Hi,
We are on Exchange 2013 SP1 and Exchange 2010 SP3 co-existence mode and currently migrating users from Exchange 2010 to 2013. We have noticed that users are not receiving email message when their mailbox quota warning when its near to maximum limit.
If I log in via OWA it shows the notification (Pop up) that your mailbox is almost full but no message received in email. Most of the users do not log into OWA but only uses Outlook.
It looks like other people are also seeing this similar issue but I am unable to find any solution for it.
How users will know if their mailbox is almost full if they are traveling and only using Mobile phone for emails to send and receive.
Thanks,
Raman

Hi Thanks for your response. Our Quota is set on Database level. I am seeing these event ids as well.
Log Name: Application Source: MSExchangeIS Date: 12/31/2014 10:07:12 PM Event ID: 1077 Task Category: MAPI Level: Warning Keywords: Classic User: N/A Computer: Exch2013mail01.company.com Description: The mailbox e3d48b23-0740-46ab-89f7-3b035dacf28f on database
326f0997-4fe5-4b31-873b-6a3396e7a91c is approaching its storage limit. A notification has been sent to the user. This warning will not be sent again for at least twenty four hours.
========================
Log Name: Application Source: MSExchange Store Driver Submission Date: 12/31/2014 10:07:12 PM Event ID: 1012 Task Category: MSExchangeStoreDriverSubmission Level: Error Keywords: Classic User: N/A Computer: Exch2013mail01.company.com Description: The store
driver failed to submit event 8237691 mailbox e3d48b23-0740-46ab-89f7-3b035dacf28f MDB 326f0997-4fe5-4b31-873b-6a3396e7a91c and couldn't generate an NDR due to exception Microsoft.Exchange.MailboxTransport.StoreDriverCommon.InvalidSenderException at Microsoft.Exchange.MailboxTransport.Shared.SubmissionItem.SubmissionItemUtils.CopySenderTo(SubmissionItemBase
submissionItem, TransportMailItem message) at Microsoft.Exchange.MailboxTransport.Submission.StoreDriverSubmission.MailItemSubmitter.GenerateNdrMailItem() at Microsoft.Exchange.MailboxTransport.Submission.StoreDriverSubmission.MailItemSubmitter.<>c__DisplayClass1.<SubmitNdrForFailedSubmission>b__0()
at Microsoft.Exchange.MailboxTransport.StoreDriverCommon.StorageExceptionHandler.RunUnderTableBasedExceptionHandler(IMessageConverter converter, StoreDriverDelegate workerFunction).
Raman

Similar Messages

Exchange 2013 SP1 users randomly prompted with "The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook"

I got a call to check an issue with a Exchange Server 2013 SP1 environment recently. All server was upgraded from Exchange server 2013 CU2 to Exchange Server 2013 SP1. It was done successfully but many users were being randomly prompted with a popup in their outlook
client with the following message:-
“The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook”
Although there wasn’t any changes of late in the environment there were random popups like these for multiple users. As the behaviour was not consistent and effecting the entire upgration population
Please suggest us how to resolve the issue.
Regards, Md Ehteshamuddin Khan All the opinions expressed here is mine. This posting is provided "AS IS" with no warranties or guarantees and confers no rights.

Hi,
Does the issue happen to all Outlook 2013 users? Please create a new Outlook profile to have a try.
If it fails, please check the msExchHomePublicMDB value in ADSI Edit:
1. In Adsiedit, expand Configuration-->CN=Services -> CN=Microsoft Exchange -> CN=domain -> CN=Administrative Groups -> CN=Exchange Administrative Group -> CN=Databases.
2. Right-click the listed database > Properties.
3. Check whether the msExchHomePublicMDB value is set to an available value. Please change the value to <not set>.
4. Click OK.
Then check whether the issue persists.
Thanks,
Winnie Liang
TechNet Community Support

Exchange 2013 SP1 server working for several months now messages are getting stuck in drafts folder

This a small, simple environment. There is a MS Server 2012 R2 server hypervisor with a MS Server 2012 R2 VM running Exchange 2013 patched to SP1. This server has been deployed into production and passing mail without issues for several months.
Upon initial deployment, we experienced the issue that many have reported and that has been widely documented where Mail Flow works fine inbound, but outbound will stick in the drafts folder. We resolved the issue by manually configuring the IP Address of
our internal DNS server (which is an installed role on our hypervisior / base layer server). The issue was immediately resolved and mail was flowing in both directions without issue. We later installed SP1 and there was no issue. Mail has
been flowing normally all the while.
Now fast-forward through several weeks of reliable mail delivery... We experienced a power loss and a system shutdown and upon reboot, inbound is working and outbound goes to drafts. I've confirmed DNS Lookup settings in ECP still points to our internal
server as previously configured. Both servers have internet access, NSLOOKUP returns expected values, and DNS appears to be working normally.
I'm not sure if we had an MS Update that installed with the reboot that caused the breakage, if there was a lingering settings change that took effect on reboot, or what is causing the interruption. I'm looking for some fresh ideas on where to look
for answers, and all the information available on the drafts folder issue points to DNS settings that have already been put in place.
Any constructive ideas are welcome! Thanks in advance.
David

Amit,
Long story short, I'm not sure how or why, but there were a few automatic services that were not starting "automatically." I'm used to seeing some services that are triggered by the application to start and stop on their own, so I didn't necessarily
panic when there were a few automatic services that were stopped..
However, The MS Exchange Health Manager, and the Mailbox Submission services weren't running. After manually starting the services my drafts folder emptied and we are back in business.. Maybe not "innovative" as you said, but it certainly put us on
the right track. We were looking so hard at DNS because of all the reported cases of "stuck in drafts" being related to DNS, we totally overlooked the obvious, so THANKS!
Now the only question is, what stopped the services and why did they not restart automatically??

Office365 User not receiving Meeting Request Email (but shows in Calendar)

Hi,
We have one user (so far) who has successfully migrated from Exchange 2007 to 'Office365' but when you sent them an meeting request they do not get ANY email notification of it. No Spam, rules, junk email are affecting it. There are no delegates on the account.
I have removed the Office365 user license for them and then re-added it but made no difference.
If the user goes into the calendar they can actually 'see' the meeting and accept / decline it in there but we obviously need the user to get some email notification of it so they are aware of a meeting and now get a 'surprise' meeting they knew nothing about!
Other migrated users are able to receive email notifications of meeting requests without issue. There is just no trace of it for this user.

Hi Peter,
As per your description above, I understand that one user cannot receive meeting requests, instead, the meetings are placed on their calendar directly.
I would like to confirm that whether he/she configured the email account into any Outlook clients, or actually we are talking about the web-based Outlook in Office 365 portal?
If this is an issue in the Outlook desktop client, please check if you have ticked the option of
Automatically accept meeting requests and remove canceled meetings
under FILE>Options>Calendar>Auto Accept/Decline... Try untick it and verify again.
If Outlook client is not involved here, I would suggest you post your question in the forum of Office 365 Community - email and calendar, where you can get more experienced responses:
http://community.office365.com/en-us/f/158.aspx
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Hope this helps.
Regards,
Ethan Hua
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

IBot user not receiving dashboard alert/email not the case for other users

Hi,
I have a user who can create iBots and is able to deliver them to other users. However the user themselves cannot receive any iBot alerts on the dashboard or via email, even for iBots that they create themselves.
I've checked their account setting and their email is configured, they are part of the correct user groups etc. This user has never been able to receive any iBot alerts or any iBot content.
Can you let me know what else I can check as iBots are working for other users?
Regards,
AT

Thanks Jay,
They are part of the same group (in fact thety are part more groups as well) as other users for whom alerts and iBots work. They have the relevant priviliges under Delivers, their email is correct.
They have access to the relevant Subject Area as it is ther user themselves who create the report and try to send it out using and iBot, other users receive the report apart from themselves. They themselves don't receive any alerts or emails.
Rregards,
AT

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 Not Receiving e-mail

Hello,
Mail flow between Exchange 2010 sp3 & Exchange 2013 SP1 (update Cu5) not working.
Exchange 2013 setup is Exchange 2013 sp1 DVD
Exchange 2010 when sending mail to external it's ok.
Exchange 2010 when sending mail to exchange 2010 users it's ok.
Exchange 2013 when sending mail to External it's ok.
Exchange 2013 when sending mail to exchange 2010 users it's ok.
or
Exchange 2010 when sending mail to exchange 2013 not working
Exchange 2013 when sending mail to Exchange 2013 not working
From internet --> SMTP GW (exh edge) --> Exchange 2010 it's ok
From Internet --> SMTP GW (exh edge) --> Exchange 2013 not working.
organization;
1 AD site and 1 PDC (2012 R2) + 3 DC (1x 2008 R2 + 2 x 2003 Server) (Windows Server 2003 domain fl)
With Exchange 2010 exchange 2013 on the same subnet. Exchange 2010 physical machine, Exchange 2013 physical machine ( eth Microsoft Team Server 2012 R2 )
All server is region setting Turkey
Exchange 2010 error
451 4.7.0 Temporary server error. Please try again later. PRX4
Exchange 2013 error
451 4.4.0 primary target ip address responded with 501 5.5.4 Invalid arguments. attempted failover to alternative host, but that did not succeed. either there are no alternate host, or delivery failed to all alternate hosts. Th
thanks

Hi,
From your description, the Exchange 2013 server can't receive emails internally and externally. I recommend you follow the steps below for troubleshooting:
1. Please restart the Microsoft Exchange Frontend Transport service on CAS and the Microsoft Exchange Transport service on Mailbox and check the result.
2. Please make sure that the authentication on default receive connector is right. Here is the configuration in my environment for your reference:
Hope it helps.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Exchange 2013 SP1 and CUCM 9.1.2 - Exch not recognizing called extension

I think I'm almost there in getting Exchange 2013 SP1 UM working with CUCM 9.1.2...I've got two issues at the moment that I need a little help with.
1) When I dial my VM pilot (6040) from a UM enabled extension it prompts to enter an extension. When I dial the same extension and let it ring to VM, Exchange picks up and says "the person you are trying to reach does not have a valid voice mail box
on our system".
2) This just started happening this afternoon, when I dial my VM pilot (6040) exch3 picks up as thats what I have my route pattern pointing to. If I enter the extension of a mailbox on exch2, I get stuck in a endless loop.
I've followed this post as a guide but it hasn't resolved my issue.
https://supportforums.cisco.com/discussion/11914031/exchange-2013-um-and-cucm-86
My Exchange environment looks like this:
Site 1:
exch1 - CAS/Mailbox, used for mainly utility type work, journal, dedicated SMTP flows etc
exch2 - CAS/Mailbox, part DAG13
exch3 - CAS/Mailbox, part of DAG13
Site 2:
exch2dr - CAS/Mailbox, part of DAG13
exch3dr - CAS/Mailbox, part of DAG13
DAG13 is stretched between two sites, there are no users at our DR site so CUCM is pointing to Site 1 for UM. Each site has an internet facing CAS-only server for OWA/EAS etc.
Any help is greatly appreciated. I'd love to get rid of Unity.
EDIT:
I just found this event in the event logs:
The Microsoft Exchange Unified Messaging service on the Mailbox server received a diverted call with ID "d51600-3a3140c5-9b8-c1414ac@EXCH3-IPADDR" for extension "4099" on UM dial plan "CUCM" from UM IP gateway "CUCM IP",
but no UM-enabled mailbox for the corresponding extension could be found. Please check the extension and make sure that the corresponding mailbox is enabled for UM and associated with the correct UM dial plan.

9.1.2 I think it is, we upgraded to avoid the known DNS bug
I cant see how to PM you either
The crux of it was outlined below with some tweaks
http://blogs.technet.com/b/canitpro/archive/2014/04/30/step-by-step-integration-between-exchange-2013-um-and-cisco-unified-communication-manager.aspx
As we have multiple combined role servers, our trunks are set up as follows:
1. 1 x CAS Trunk - contains all CAS Servers on port 5060
2. 4 x MBX Trunks - contains Maibox Server with ports 5062-5068
On top of that, we had to Allow "Redirecting Diversion Header Delivery - Inbound (and Outbound)" on the CAS Trunk but DISABLE it on the Mailbox Trunks
Also, make sure that you are using Telephone Extension Dial plans in Exchange 2013 (Despite them being unable to be associated with a 13 Server - EX13 answers for all calls anyway)
Lastly, the MS documentation is a little strange - it says that as your last step of UM migration, you should point your Call Manager to 2013 - I don't agree with that statement, EX13 routes calls back to 2010 UM Servers perfectly fine, so treat it the same
as any other CAS based service - point to 2013, and it will handle the rest

Exchange 2013 sp1 smtp NTLM auth for child domain users

i have exchange organization with exchange 2007 sp 3 & exchange 2013 sp1.
there are all users in Exchange 2013 server (mail flow is through Exchange 2013 server)
i have single forest, 2 site (site1, site2), root domain root.local and 1 child domain ch.root.local
DC for child domain is located in site2 (dc.ch.root.local)
multirole exchange 2013 server is installed in root domain.
i am traing to configure smtp receive connector with NTLM auth and have one problem.
when user in child domain try send email through this receive connector i see in log
<,AUTH NTLM,
>,334 <authentication response>,
*,SMTPSubmit SMTPAcceptAnyRecipient BypassAntiSpam AcceptRoutingHeaders,Set Session Permissions
*,CH\user1,authenticated
*,,Setting up client proxy session failed with error: 535 5.7.3 Unable to proxy authenticated session because either the backend does not support it or failed to resolve the user
*,,"Setting up client proxy session failed with error: 451 4.4.0 Primary target IP address responded with: ""535 5.7.3 Unable to proxy authenticated session because either
the backend does not support it or failed to resolve the user."" Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was 192.168.1.15:465"
but authentication is succesfull for users from root domain.
why do it can be?
Thanks.

thanks for link
at smtp receive logs (Hub transport role) i've found the next:
Client Proxy EXMAIL2013,08D134DAF6CE1C51,49,192.168.1.15:465,
*,NT AUTHORITY\SYSTEM,authenticated
>,235 <authentication response>,
<,XPROXY SID=08D130D354F520D1 IP=192.168.1.21 PORT=57085 DOMAIN=[192.168.1.21] CAPABILITIES=0 SECID=Uy0xxx...
*,,Error while looking up SamAccountName chuser: The user name or password is incorrect.\r\n
*,None,Set Session Permissions
>,250 XProxy accepted but user identity could not be obtained,

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

Exchange 2013 SP1 RPC 404 Error Page Not Found

Anyone got any ideas why on my Exchange 2013 SP1 server I am getting a 404 error when trying to access the RPC URL?
I had a look in the CAS RPC logs and see the following HTTP POST events:
<snip>
2014-06-19T15:33:00.558Z,EX-CAS1,RpcHttp,"S:Stage=BeginRequest;S:OutlookSessionId=""{17FD197A-098A-4339-82E9-A480F6DD70F7}"";S:AuthType=Basic;S:HttpVerb=RPC_IN_DATA;S:UriQueryString=?pdc.internal.local:6004;S:RequestId=0acc9487-bf8f-4600-ae04-edf2ef00a90b;S:ClientIp=192.168.0.17"
2014-06-19T15:33:00.558Z,EX-CAS1,RpcHttp,"S:Stage=PostAuthorizeRequest;S:UserName=INTERNAL\SVC_BMA;S:OutlookSessionId=""{17FD197A-098A-4339-82E9-A480F6DD70F7}"";S:AuthType=Basic;S:HttpVerb=RPC_IN_DATA;S:UriQueryString=?pdc.internal.local:6004;S:RequestId=0acc9487-bf8f-4600-ae04-edf2ef00a90b;S:ClientIp=192.168.0.17"
2014-06-19T15:33:00.574Z,EX-CAS1,RpcHttp,"S:Stage=EndRequest;S:UserName=INTERNAL\SVC_BMA;S:OutlookSessionId=""{17FD197A-098A-4339-82E9-A480F6DD70F7}"";S:AuthType=Basic;S:Status=404 Not Found;S:HttpVerb=RPC_IN_DATA;S:UriQueryString=?pdc.internal.local:6004;S:RequestId=0acc9487-bf8f-4600-ae04-edf2ef00a90b;S:ClientIp=192.168.0.17"
</snip>
This works fine in Exchange 2010 SP3 so I am wondering if maybe Microsoft have removed the /rpc url functionality in Exchange 2013 SP1?

Hi JRA,
Is it possible to provide more info for your issue?
You receive as you said HTTP 404 error, can you provide the specific HTTP 404 error message?
For example:
HTTP/1.0 404 File Not Found
HTTP/1.0 404 Not Found
HTTP/1.0 404 Object Not Found
HTTP/1.0 404 Page Cannot Be Found
The page cannot be found. The page you are looking for might have been removed, had its name changed, or is temporarily unavailable
Also a screenshot will be very helpful
Regards,
CF

SME 7.1 not working with Exchange 2013 SP1 CU6

Hello, i tried upgrading to SME 7.1 on our Exchange 2013 SP1 CU6, but when trying to configure the Exchange Server in the SME management console using the configuration wizard, it gave an error before the LUN mapping page, saying "Failed to get Exchange information for server" and "The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.". I upgraded Snapdrive to 7.1, verfied all credentials according to the manuals, re-installed and rebooted multiple times (registry and filesystem cleaned, even tried to rename the existing SnapInfo directory, ...), stopped all other services on the server but without any change... Every time when trying to run the configuration wizard, the debug log shows no errors, lists all Exchange information and ends with the following lines:[11/18 12:51:58 155] Exit CSmeCDOExm::GetExchangeStructureInternal 0x0
[11/18 12:51:58 155] Exit CNtapSnapMgr::GetExchangeStructure: 0x0
[11/18 12:51:58 233] Enter CSmeServerBase::~CSmeServerBase ...
[11/18 12:51:58 248] m_ptrSnapShot released
[11/18 12:51:58 248] m_pISnapShot4 released
[11/18 12:51:58 248] m_pISnapShot5 released
[11/18 12:51:58 248] m_pISnapShot6 released
[11/18 12:51:58 248] m_pISnapShot7 released
[11/18 12:51:58 248] m_pISnapShot8 released
[11/18 12:51:58 248] m_pISnapShot9 released I ended up uninstalling SME 7.1 and re-installed SME 7.0 which is working. Exchange Server: ESXi 5.5 VM, Windows Server 2012 R2 (with current patches), Exchange 2013 SP1 CU6 - no DAG, single server installation (in co-existence with Exchange 2010), 4 iSCSI LUNs created with Snapdrive (1x Log, 3x Store), System drive and Exchange installation drive on vmdk Disks (via ESXi -> NFS store on the same NetApp)NetApp: FAS 2240-2 with Data ONTAP 8.1.4P1 7-mode (with complete license bundle) Anyone else got this problem or even better - a solution?

We could not reproduce the error with the upgrade workflow.Looking at the error and the relevant function, we could force the problem in following conditions: -SME is configured or ran at the DAG level-one of the following services is stopped or not responding on one nodes of the DAG Snapdrive Service, Snapmanager Service, Snapdrive Storage Management Service,Snapdrive Management Service. Would be good if we could get the output of following powershell cmdlet before and after the upgrade: Get-Service –ComputerName Node1, Node2, Node3 –name Snap*, SDMGMT*, SWSvc Best regards,Dan

Lync integration not working after Exchange 2013 SP1 is installed...

Hi,
I have two Exchange 2013 servers running and everything is fine, almost.
The problem is that on the first server we had OWA with Lync integration working before installing SP1, but after the installation of SP1, it doesn't Work any more.
The second server was installed with SP1 from the start, but we can't get the Lync integration to Work on this one either..
When we log in to OWA, it just starts to sign in but then says "there was a problem signing in, if this continues please contact your helpdesk"
I have checked the Exchange server for events, and i can see the event ID 112 everytime i recycle the Application Pool, so there are some connection between Exchange and Lync..
Have any of you Guys seen or experienced any thing like this?
Thanks in advance.
Regards
Kenneth

Hi,
I recommend that you refer to the following article to troubleshoot the issue:
Troubleshooting tips for Exchange 2013 OWA IM Integration to Lync 2013
This post describes how to configure Exchange 2013 OWA to have IM integration to Lync 2013. Here I would like to give some troubleshooting tips in case you can't get the integration to work.
In addition, here is a similar thread for your reference:
Lync 2013 with Exchange 2013 SP1 OWA integration failed
Hope this helps!
Thanks.
Niko Cheng
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.

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

Exchange 2013 SP1 users not receiving quota warning email message

Similar Messages

Maybe you are looking for