Correctif cumulatif 2 Exchange 2010 SP3

Good day ,
I did migration from exchange 2003 to exchange 2010 SP3 everything work fine except the Public folder migration didn't work When I find the MSExchange Store Driver 1020 Event recomend to install correctif cumulatif 2 Exchange 2010 SP3 to
fix the problem
http://support.microsoft.com/kb/2855083
If I install I don't have any impact about my configuration of exchange 2010 it's safe ?
Regards
e

Hi,
Firstly, I’d like to explain, it’s safe to install the Update Rollup 2 for Exchange Server 2010 SP3.
Alternatively, since the error is always caused by an empty server container, we can remove the container to resolve the issue:
1.Start the ADSI Edit tool. To do this, click Start , click Run , type adsiedit.msc , and then click OK
2.Expand Configuration Container [servername.domainname.com] , and then expand CN=Configuration,DC=DomainName,DC=com
3.Expand CN=Services, expand CN=Microsoft Exchange, and then expand CN=OrganizationName where OrganizationName is the name of your Exchange organization.
4.You will see the empty Administrative Group. Expand the CN=AdministrativeGroupName
5.Expand CN=Servers
6.Verify there are no server objects listed under the Servers container
7.Right click on the emtpy CN=Servers Container and choose Delete.
http://support.microsoft.com/kb/2487271
http://blogs.technet.com/b/exchange/archive/2010/05/05/3409916.aspx
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Similar Messages

Sharepoint 2013 vs Exchange 2010 SP3 search (Error while crawling LOB contents)

Hi there:
We are trying to solve the problem: ERROR CRAWLING LOB CONTENTS when we wish to search Exchange 2010 SP3 public folder content on Sharepoint 2013 Foundation.
Quick briefing:
Followed this instructions:
http://technet.microsoft.com/en-us/library/jj591608(v=office.15).aspx
* Created CRAWL RULE
- Used Domain Admin for content access ---> IS THIS WRONG?
- Domain Admin can access public folder thru Outlook Web Access (checked)
- Included all items in this path
PRINTSCREEN 1
* Added a content source for Exchange Server public folders
- Logged to Outlook Web Access with domain admin, expanded Public folders and opened 1st subfolder in new window and copied the address
- Logged to Outlook Web Access with domain admin, expanded Public folders and opened 2nd subfolder in new window and copied the address
PRINTSCREEN2
* Did a FULL CRAWL
PROBLEM:
- Search results does not throw "correct data". Some items are not being found
CRAWL LOG is reporting: Error while crawling LOB contents
Detailed error message:
https://mail.domain.com/OWA/?ae=Folder&id=PSF.LgAAAAAaRHOQqmYRzZvIAKoAL8RaAwAnt2ed15IATLg8XoXLNj4EAAAAXsN8AAAB&t=IPF.Note
Error while crawling LOB contents.
Error caused by exception: Microsoft.BusinessData.Infrastructure.BdcException
The shim execution failed unexpectedly - Exception has been thrown by the target of an invocation..:
System.InvalidOperationException An internal server error occurred.
Try again later.; SearchID = 4E8542D3-48EF-404E-8025-8D9AAEFE777A )
We thought it's a throttling issue / found possible solution:
http://powersearching.wordpress.com/2013/07/23/exchange-public-folders-search-fail-error-while-crawling-lob-contents/
Tried it, still same Error messages, problem not resolved.
Any hints? Please advise.
With best regards
bostjanc

Hi Bostjan,
From the error message, the issue might be caused by throttling policy on Exchange side. And the article you posted provides the right solution, some modification to the solution and please try again.
For throttling policy part
1.Execute the command for Set-ThrottlingPolicy
Set-ThrottlingPolicy SharePoint -RCAMaxConcurrency Unlimited -EWSMaxConcurrency Unlimited -EWSMaxSubscriptions Unlimited -CPAMaxConcurrency Unlimited -EwsCutoffBalance Unlimited -EwsMaxBurst Unlimited -EwsRechargeRate Unlimited
2.Execute the command Get-ThrottlingPolicy SharePoint to double confirm the policy setting has been successfully executed
For registry key part
1. Start Registry Editor (regedit).
2. Navigate to the following registry subkey:
\\HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
3. Right-click ParametersSystem, point to New, and then click Key.
A new key is created in the console tree.
4. Rename the key MaxObjsPerMapiSession, and then press Enter.
5. Right-click MaxObjsPerMapiSession, point to New, and then click DWORD (32-bit) Value.
The new value is created in the result pane.
6. Rename the key to <Object_type>, where <Object_type> is the name of the registry object type that you're modifying. For example, to modify the number of messages that can be opened, use objtMessage. Press Enter.
7. Right-click the newly created key, and then click Modify.
8. In the Value data box, type the number of objects that you want to limit this entry to, and then click OK. For example, type 350 to increase the value for the object.
9. Restart the Microsoft Exchange Information Store service.
If it still doesn’t help, please check ULS log for related error message.
Regards,
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] .
Rebecca Tu
TechNet Community Support

[SOLVED] Can't add a node to the cluster with error (Exchange 2010 SP3 DAG Windows Server 2012)

Hi there!
I have a problem which makes me very angry already :)
I have two servers Exchange 2010 SP3 with MB role started on Windows Server 2012. I decided to create a DAG.
I have created the prestaged AD object for the cluster called msc-co-exc-01c, assigned necessary permissions and disabled it. Allowed through the Windows Firewall traffic between nodes and prepared the File Share Witness server.
Then I have tried to add nodes. The first node has been added successfully, but the second node doesn't want to be added :). Now I can add only one node to the DAG. I tried to add different servers first, but only the first one was added.
LOGS on the second nodes:
Application Log
"Failed to initialize cluster with error 0x80004005." (MSExchangeIS)
Failover Clustering Diagnostic Log
"[VER] Could not read version data from database for node msc-co-exc-04v (id 1)."
CMDLET Error:
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:06:21
MSC-CO-EXC-02V
Failed
Error:
A database availability group administrative operation failed. Error: The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode()
(MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed. [Server: msc-co-exc-04v.int.krls.ru]
An Active Manager operation failed. Error An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed..
This operation returned because the timeout period expired
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.174.1&t=exchgf1&e=ms.exch.err.ExC9C315
Warning:
Network name 'msc-co-exc-01c' is not online. Please check that the IP address configuration for the database availability group is correct.
Warning:
The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2014-11-17_13-54-56.543_add-databaseavailabiltygroupserver.log".
Exchange Management Shell command attempted:
Add-DatabaseAvailabilityGroupServer -MailboxServer 'MSC-CO-EXC-02V' -Identity 'msc-co-exc-01c'
Elapsed Time: 00:06:21
UPD:
when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
on both nodes.
It's confused me, because there is normal connectivity between these DAG members through the main interface.
Please, help me if you can.

Hi, Jared! Thank you for the reply.
Of course I did it already :) I have new info:
when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
on both nodes.
It's confused me, because there is normal connectivity between these DAG members through the main interface.

Exchange 2010 SP3 - Delayed emails with XLSM attachments...

Running Exchange 2010 SP3 Rollup 5. Clients running Windows 7 and Office 2010 Pro Plus SP2. Have one specific user / client that when sending emails with an XLSM attachment around 5:30AM, the email is delayed getting to the Exchange server and
is delayed up to 16 hours. Unfortunately, this is a random occurrence, and not necessarily easy to duplicate.
The Sent Items on the Outlook client reflect the correct sent time, but the Message Tracking Log on the Exchange server shows the server did not receive the email until approximately 12 to 16 hours later.
The desktop is a shared system and this issue appears to be isolated to the user's profile, AD account, or Exchange. I've literally blown away the users local profile and reconfigured it with no resolution.
Any suggestions are greatly appreciated.
Fuel

Hi,
Please verify whether there is any error/warning/information message left in App log. If yes, please paste the details without sensitive information.
I suggest re-send a .xlsm attachment for testing to verify whether it delays.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2010 SP1 Update Rollup 6 to Exchange 2010 SP3

Hi there,
I am planning to install Exchange 2010 SP3 next week and after reading some of the related comments on this site I got a little worried.
Our current Exchange environment consists of the following:
1 x CAS/HT Server
2 x Mailbox Server (members of a DAG)
The OS of the 3 servers is Windows Server 2008 R2 SP1. All servers are running Exchange 2010 SP1 Update Rollup 6.
The Execution Policies on our Exchange servers are set as follows:
– CAS/HT Server:
Scope ExecutionPolicy
MachinePolicy Undefined
UserPolicy Undefined
Process Undefined
CurrentUser Undefined
LocalMachine Unrestricted
– Mailbox Servers:
Scope ExecutionPolicy
MachinePolicy Undefined
UserPolicy Undefined
Process Undefined
CurrentUser Undefined
LocalMachine RemoteSigned
Please note that we do not have any Group Policies that defined the PowerShell script execution policy.
I would be very grateful if you (or any of the kind readers) could help me with following questions:
1- Do I have to change the execution policy on our Exchange servers before installing SP3? If I have to change a policy, what should I change? And how would you recommend I should do this?
2- After installing SP3 on a server, can I install the latest rollup update on this server before moving to the next server? For example, can I do the following:
i. Install SP3 followed by RU 5 on the CAS/HT server -> Apply the our custom settings
ii. Install SP3 followed by RU 5 on the first mailbox server
iii. Install SP3 followed by RU 5 on the second mailbox server
Many thanks,
M

Hi Amit,
Many thanks for the swift reply.
That's correct. We didn't set the Powershell execution policy via Group Policy. We only configured the execution policy of "LocalMachine" to "Unrestricted" on the CAS/HT server using the "Set-ExecutionPolicy" command on the server.
The mailbox servers' execution policies have not been changed and are set to those values by default.
I must admit, I go event more confused when I read the "http://support.microsoft.com/kb/2668686" and "http://support.microsoft.com/kb/2810617" articles.
But it looks like I shouldn't worry as our current Powershell execution policies shouldn't affect the upgrade. Right?

Exchange 2010 SP3 Rollup 8 and Rollup 7

Hi
I have a customer with a Small Business Server 2010 with Exchange 2010 SP3.
The Customer installed updates on the server 10/12/2014 where Rollup 8 for Exchange was included.
After that the Customer has a lot of problems with connection from Outlook to Exchange and they phoned us.
We have looked on the problem and found a Microsoft article about rollup 8 where they said DO NOT INSTALL
We ran Windows Update again on the 13/12/2014 where Rollup 7 was installed
The customers still has problems with connection from Outlook.
One of the errors:
From: Systemadministrator
Sent: 15. december 2014 10:54
Subject: Unable to be delivered: Test
This message did not reach one or all of the recipients.
      Subject:     Test
      Sent:15-12-2014 10:54
Unable to deliver to the following recipient(s):
      MST the 15-12-2014 10:54
            This message could not be sent. Try to send the message again later, or contact the networkadministrator. Error [0x80004005-00000000-00000000].
Another error in Application log:
Log Name:      Application
Source:        MSExchange Common
Date:          16-12-2014 08:09:00
Event ID:      4999
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      <servername>.<domain>.local
Description:
Watson report about to be sent for process id: 9340, with parameters: E12, c-RTL-AMD64, 14.03.0224.001, M.E.RpcClientAccess.Service, M.E.RpcClientAccess.Handler, M.E.R.H.ViewCache.IsRowWithinUnreadCache, System.IndexOutOfRangeException, 8e38, 14.03.0224.001.
ErrorReportingEnabled: False
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSExchange Common" />
    <EventID Qualifiers="16388">4999</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-12-16T07:09:00.000000000Z" />
    <EventRecordID>174679</EventRecordID>
    <Channel>Application</Channel>
    <Computer><servername>.<domain>.local</Computer>
    <Security />
</System>
<EventData>
    <Data>9340</Data>
    <Data>E12</Data>
    <Data>c-RTL-AMD64</Data>
    <Data>14.03.0224.001</Data>
    <Data>M.E.RpcClientAccess.Service</Data>
    <Data>M.E.RpcClientAccess.Handler</Data>
    <Data>M.E.R.H.ViewCache.IsRowWithinUnreadCache</Data>
    <Data>System.IndexOutOfRangeException</Data>
    <Data>8e38</Data>
    <Data>14.03.0224.001</Data>
    <Data>False</Data>
    <Data>
    </Data>
</EventData>
</Event>
What to do ?
Best Regards
John B

Hi John,
Please type
outlook /safe in RUN to start Outlook in safe mode and then check if this issue still exists. Meanwhile, please run Exchange Best Practices Analyzer and check if find relevant issues.
à
This message could not be sent. Try to send the message again later, or contact the networkadministrator.
Error [0x80004005-00000000-00000000].
The issue typically occurs if send messages to a large number of recipients.
When this issue occurred, did you check if send message successfully via OWA?
à
We have looked on the problem and found a Microsoft article about rollup 8 where they said DO NOT INSTALL
Did you mean this article:
Exchange releases: December 2014?
à
We ran Windows Update again on the 13/12/2014 where Rollup 7 was installed
From the Event ID 4999, I noticed that point to
14.03.0224.001, it should mean the old Exchange Server 2010 SP3 Update Rollup 8. From above
mentioned article (Exchange releases: December 2014),
Exchange Server 2010 SP3 Update Rollup 8 has been re-released to the Microsoft download center resolving a regression discovered in the initial release. The update RU8 package
corrects the issue which impacted users connecting to Exchange from Outlook. The updated RU8 package is version number 14.03.0224.002. Just a confirmation, did you
reinstall that re-released Exchange Server 2010 SP3 Update Rollup 8? Any difference?
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu
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 Support, contact [email protected]

Exchange 2010 SP3 RU7 - additionals mailboxes does not refresh automatically

Hello
On Exchange 2010 SP3 RU7 , my additionals mailboxes does not refresh automatically (Outlook 2010 up-to-date).
i need to perform "send/receive" and "update the folder" to get the mail.
Primary mailbox is running correctly and new mails are displayed .
Thanks

Hi,
Based on the description, you added additional mailboxes from Outlook, but messges sent to these additional mailboxes didn't show until you tried the option "update the folder".
How many additional mailboxes did you add?
Did this issue affect all users?
If possible, please remove these additional mailboxes and then re-add them. I recommend you add one additional mailbox first to check if the issue occurs. Then you can add another additional mailbox to check result.
Best regards,
Belinda Ma
TechNet Community Support

Exchange 2013 Sp1 Coexistence with Exchange 2010 SP3 CU5 HTTP 500

I`m trying to make working OWA coexistence between Exchange 2013 SP1 and Exchange 2010 SP3 CU5.
When user login in to OWA where his mailbox is located on Exchange 2013 server it logon successful and owa opened. When i try to login to the same url with user whose mailbox is located on Exchange 2010 server i get Error http 50
The website cannot display the page : HTTP 500 »https://URLEXCHANGE2013/owa/auth.owa«
The same is, when i use https:// URLEXCHANGE2013/ecp?ExchClientVer=14
URL on Exchange 2013 are different as fro Exchange 2010.
I even tried to setup Internal URL for Exchange 2010 to bi set to »null ,Saem error
Exchange server 2013 Sp1 is installed on Windows server 2012 R2.

Assumption is correct. I have even enable verbose logging, and i can see MSExchange Front End HTTP Proxy , that successfully connect to Exchange 2010 server.
But remember Exchange 2013 is fresh installation on Windows server 2012 R2.
IIS LOG
2014-03-04 08:52:53 fe80::99d1:f542:a4d3:b469%12 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6001&CorrelationID=<empty>;&RequestId=391fd8b3-2b98-494a-8812-d38feda2e5a0&cafeReqId=391fd8b3-2b98-494a-8812-d38feda2e5a0;
443 companyNT\SM_9c071c4922fd420fb fe80::99d1:f542:a4d3:b469%12 MSRPC - 200 0 0 5484
2014-03-04 08:52:53 fe80::99d1:f542:a4d3:b469%12 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6001&CorrelationID=<empty>;&RequestId=27cfafa2-8224-4563-918b-0b228c6ee8d4&cafeReqId=27cfafa2-8224-4563-918b-0b228c6ee8d4;
443 - fe80::99d1:f542:a4d3:b469%12 MSRPC - 401 1 2148074254 0
2014-03-04 08:52:53 fe80::99d1:f542:a4d3:b469%12 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6001&CorrelationID=<empty>;&RequestId=6d930bcd-7bbc-415a-a25a-8d6488e91401&cafeReqId=6d930bcd-7bbc-415a-a25a-8d6488e91401;
443 - fe80::99d1:f542:a4d3:b469%12 MSRPC - 401 1 2148074254 15
2014-03-04 08:52:55 10.1.0.36 GET /owa/ &CorrelationID=<empty>;&cafeReqId=551cfdd9-18ac-42d8-aea3-cbb546c9d9fb; 443 - 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+6.3;+WOW64;+Trident/7.0;+.NET4.0E;+.NET4.0C) https://OWA.company.com/
302 0 0 9937
2014-03-04 08:52:56 10.1.0.36 GET /owa/auth/logon.aspx url=https%3a%2f%2fOWA.company.com%2fowa%2f&reason=0&CorrelationID=<empty>;&cafeReqId=c1b97df9-ec56-4906-b2f5-965551b720ae; 443 - 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+6.3;+WOW64;+Trident/7.0;+.NET4.0E;+.NET4.0C)
https://OWA.company.com/ 200 0 0 1015
2014-03-04 08:52:56 10.1.0.36 GET /owa/auth/logon.aspx replaceCurrent=1&url=https%3a%2f%2fOWA.company.com%2fowa%2f&CorrelationID=<empty>;&cafeReqId=b92ca682-04f4-4d4f-931e-9a95680ab9ea; 443 - 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+6.3;+WOW64;+Trident/7.0;+.NET4.0E;+.NET4.0C)
- 200 0 0 671
2014-03-04 08:52:58 10.1.0.36 GET /ecp/ &CorrelationID=<empty>;&cafeReqId=093bd01a-de59-4519-80f6-067484122091; 443 - 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING) - 302 0 0 0
2014-03-04 08:52:58 10.1.0.36 GET /owa/auth/logon.aspx url=https%3a%2f%2fEXCH2013%2fecp%2f&reason=0&CorrelationID=<empty>;&cafeReqId=c2f7565d-ee6a-48f8-8d86-16d5d3ca65c1; 443 - 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING)
- 200 0 0 0
2014-03-04 08:52:58 10.1.0.36 GET /ecp/ &CorrelationID=<empty>;&cafeReqId=ba633030-2376-4bad-a32f-8f160bd87bd4; 443 - 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING) - 302 0 0 0
2014-03-04 08:52:58 10.1.0.36 GET /owa/auth/logon.aspx url=https%3a%2f%2fEXCH2013%2fecp%2f&reason=0&CorrelationID=<empty>;&cafeReqId=5e94172c-d97c-46a9-a602-6030d6f7da2c; 443 - 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING)
- 200 0 0 0
2014-03-04 08:52:58 10.1.0.36 GET /owa/auth/logon.aspx replaceCurrent=1&url=https%3a%2f%2fEXCH2013%2fecp%2f&CorrelationID=<empty>;&cafeReqId=9ba2caf3-2a03-44a2-8477-2724689e139c; 443 - 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING)
- 200 0 0 46
2014-03-04 08:52:58 10.1.0.36 GET /owa/auth/15.0.847/scripts/premium/flogon.js &CorrelationID=<empty>;&cafeReqId=62bb4655-3bfa-4e07-aa62-27c93e7e8b4d; 443 - 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING)
- 200 0 0 0
2014-03-04 08:52:59 10.1.0.36 POST /owa/auth.owa &CorrelationID=<empty>;&cafeReqId=9d52ec1a-2ee1-4954-85e6-89e7e5df407a; 443 [email protected] 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING)
- 302 0 0 812
2014-03-04 08:52:59 ::1 GET /OWA/Calendar/[email protected]/calendar/calendar.html &CorrelationID=<empty>;&cafeReqId=4ea66475-9a47-41a4-81cb-6b569715d0d6; 443 - ::1 AMProbe/Local/ClientAccess - 200 0 0 8859
2014-03-04 08:53:01 10.1.0.36 POST /owa/auth.owa &CorrelationID=<empty>;&cafeReqId=b3db7480-2192-436c-b01d-29d0e528cfec; 443 UseronEX2010 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+6.3;+WOW64;+Trident/7.0;+.NET4.0E;+.NET4.0C) https://OWA.company.com/owa/auth/logon.aspx?replaceCurrent=1&url=https%3a%2f%2fOWA.company.com%2fowa%2f
500 0 0 187
2014-03-04 08:53:04 127.0.0.1 GET /Microsoft-Server-ActiveSync/default.eas &CorrelationID=<empty>;&cafeReqId=2e2a655b-00b9-42ae-8789-1e452e6579c3; 443 [email protected] 127.0.0.1 AMProbe/Local/ClientAccess
- 200 0 0 8265
2014-03-04 08:53:14 10.1.0.36 GET /ecp/ &CorrelationID=<empty>;&cafeReqId=8741886f-b9b1-46f9-8c15-baf35809a12c; 443 [email protected] 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING)
- 200 0 0 15265
2014-03-04 08:53:14 127.0.0.1 GET /OWA/auth.owa &CorrelationID=<empty>;&cafeReqId=8ad938fb-f2c3-42bf-8718-da62b122422c; 443 - 127.0.0.1 AMProbe/Local/ClientAccess - 302 0 0 15
HTTPERR LOG :
2014-03-04 08:51:48 10.1.0.36 13937 10.1.0.36 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?EXCH2013.companyNT.local:6001 400 2 BadRequest MSExchangeRpcProxyAppPool
2014-03-04 08:51:48 fe80::99d1:f542:a4d3:b469%12 13872 fe80::99d1:f542:a4d3:b469%12 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?EXCH2013.companyNT.local:6001 400 2 BadRequest MSExchangeRpcProxyAppPool
2014-03-04 08:52:25 10.1.0.36 13937 10.1.0.36 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?EXCH2013.companyNT.local:6001 400 2 Connection_Dropped MSExchangeRpcProxyAppPool
2014-03-04 08:52:25 fe80::99d1:f542:a4d3:b469%12 13872 fe80::99d1:f542:a4d3:b469%12 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?EXCH2013.companyNT.local:6001 400 2 Connection_Dropped MSExchangeRpcProxyAppPool
2014-03-04 08:52:30 127.0.0.1 14122 127.0.0.1 443 HTTP/1.1 GET /RPC/[email protected] 404 - NotFound -
2014-03-04 08:52:30 ::1%0 14121 ::1%0 443 HTTP/1.1 GET /ecp/ReportingWebService/ 404 - NotFound -
2014-03-04 08:54:42 ::1%0 14117 ::1%0 444 - - - - - Timer_ConnectionIdle -
2014-03-04 08:54:48 10.1.0.36 14211 10.1.0.36 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?EXCH2013.companyNT.local:6001 400 2 BadRequest MSExchangeRpcProxyAppPool
2014-03-04 08:54:48 fe80::99d1:f542:a4d3:b469%12 14285 fe80::99d1:f542:a4d3:b469%12 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?EXCH2013.companyNT.local:6001 400 2 BadRequest MSExchangeRpcProxyAppPool
2014-03-04 08:55:35 10.1.0.36 14211 10.1.0.36 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?EXCH2013.companyNT.local:6001 400 2 Connection_Dropped MSExchangeRpcProxyAppPool
2014-03-04 08:55:35 fe80::99d1:f542:a4d3:b469%12 14285 fe80::99d1:f542:a4d3:b469%12 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?EXCH2013.companyNT.local:6001 400 2 Connection_Dropped MSExchangeRpcProxyAppPool
Trace login, ok it is xml, so print is..
-Request Summary
Site
1
Process
8232
Failure Reason
STATUS_CODE
Trigger Status
500
Final Status
500
Time Taken
500 msec
Url
http://EXCH2013.companyNT.local:80/powershell?clientApplication=ActiveMonitor;PSVersion=4.0&sessionID=Version_15.0_(Build_846.0)=rJqNiZqNgZuQkpqT0pqH0ZuQkpqTkYvRk5CcnpOBzsbLzsbGyczJyIHPzNDPy9DNz87L38/Gxc/KxcrJ
App Pool
MSExchangePowerShellFrontEndAppPool
Authentication
Kerberos
User from token
companyNT\SM_9c071c4922fd420fb
Activity ID
{8000134C-0001-E300-B63F-84710C7967BB}
-Errors & Warnings
No.↓
Severity
Event
Module Name
157. view trace
Warning
-MODULE_SET_RESPONSE_ERROR_STATUS
ModuleName
ManagedPipelineHandler
Notification
EXECUTE_REQUEST_HANDLER
HttpStatus
500
HttpReason
Request Failed
HttpSubStatus
0
ErrorCode
The operation completed successfully.
(0x0)
ConfigExceptionInfo
ManagedPipelineHandler
See all events for the request

Exchange 2010 SP3 DAG Flip Flop File Share Witness Issue

Hi All,
We are facing one strange issue with Exchange 2010 SP3.
Our environment is as below
a single DAG spanned accross 2 AD sites with 6 MBX server.
Each site have 3 MBx server.
File Share Witness is on Hub server in primary site.
Note: The DAG IP is from Primary DC VLAN and which cant be streched accross DC due to network restrictions/limitations.
It was working fine till date.
But, yesterday onwards we are facing issue.
All DB dismounted and DAG name disappear from EMC and while doing refresh its giving error as below
Exception type: Microsoft.Exchange.Data.DataValidationException
Exception message: Could not convert property WitnessServer to type UncFileSharePath. Error while converting string 'vesthub700.mydomain.com\DAG1.mydomain.com' to result type Microsoft.Exchange.Data.UncFileSharePath: "vesthub700.mydomain.com\DAG1.mydomain.com"
is not an acceptable path. You must use an absolute, local, long file path, that doesn't contain '~', or a UNC path. Parameter name: path
We are not able to execute any cmdlets related to databaseavailabilitygroup from EMS and its giving same error.
Failover Cluster DAG resource is Flip/Flip continuously.
Its only become stable after reboot of the hub server holding FSW and the 1st mailbox server.(Cluster Owner)
We are even not able to move cluster group to different server.
Performed ExBPA no such issues found which related to DAG.
Performed clsuter validation.
Only generic cluster events in Mailbox servers.
Observation:
Its only become stabe if we remove the msExchFileShareWitness Value for DAG1 using ADSIEdit.
And the problem recurs if we set it back again.
Any help or suggestion is appreciated.
Thanks,
soumen
Soumen Ghosh

Hi Belinda,
Thanks! I have checked the Mailbox Server Application Log and found few 2155 Event Id generated at the time of the issue occured.
Process Microsoft.Exchange.ServiceHost.exe () (PID=9312). Configuration object CN=DAG1,CN=Database Availability Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=xxxxxx,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=mydomain,DC=com
read from DCTDK35.mydomain.com failed validation. DataValidationException will be thrown. Set event logging level for Validation category to Expert to get additional events about each failure.
One update is that the DAG is stable now after we set an alternate FSW last night.
Regarding the 2nd IP assignment for DAG for the 2nd subnet, we have gone through technet and other sites which refering to add the same from EMC or EMS.
Is it sufficinet to simply adding the 2nd IP to DAG from EMC or EMS? Or do we need to take any other special consideration.
Also, adding another IP it will create one more IP address resource to Failover Cluster, but I belive at a time both the IP wont be online. Do we need to keep it offline manually or its automatically taken care by Exchange.
Please suggest.
Also, regarding executing the CollectOverMetrics.ps1 we are following
http://www.msexchange.org/articles-tutorials/exchange-server-2010/monitoring-operations/monitor-dag-database-failover.html
but failed to execute. Can you suggest the correct parameter.
Thanks,
Soumen
Soumen Ghosh

Exchange 2010 SP3 RU8

I am trying to rollback Exchange 2010 SP3 RU8. When I uninstall the update the installer asks for exchangeserver.msi for Exchange 2010 SP3 RU7. I downloaded RU7 from the Microsoft website. It did not accept it as the correct msi. I ran the Exchange 2010
SP3 RU7 update I download and it comes up as RU8. I need the exchangeserver.msi from Exchange 2010 SP3 RU7. Thank you for your help.

You may need the original SP3 binaries located here:
http://www.microsoft.com/en-us/download/details.aspx?id=36768
See this thread for more ideas about rolling back:
https://social.technet.microsoft.com/Forums/en-US/1be9b816-b0ab-40ea-a43a-446239f8eae3/outlook-client-issues-following-exchange-2010-rollup-8
Update:Microsoft has released version 2 of SP3 RU8 today. The link should be live soon.
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2010 SP3 Rollup 7 not showing right version

I have installed Rollup 7. I can see it in programs installed / updates
but when I check the version number via the shell or console it show the number corresponding to sp3 no rollups
tried to re install rollup7, but it fails

There is:
Update Rollup 8 for Exchange Server 2010 SP2,
and Update Rollup 8 for Exchange Server 2010 SP1
But, as far as I know, there is no Update Rollup 8 for Exchange Server 2010
SP3 yet.
Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.
That's correct Idan. Exchange 2010 SP3 RU7 is the latest - released in August this year:
http://blogs.technet.com/b/rmilne/archive/2014/08/26/exchange-2010-sp3-ru7-released.aspx
Just like in Exchange 2003 & 2007 only service packs increment the version # you see in the management console and shell. Check the exsetup file as mentioned in the first post Idan linked.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2010 SP3 mailbox role installation error

Hello.
I can't install the Mailbox role on a Windows 2008 R2 server, the first Exchange in the domain and forest (2 dcs in the domain).
Client Access Role and Hub Transport Role installed correctly.
Setup preparations - without an error.
Started the Exchange 2010 SP3 Installation, which start correctly, all prerequisites are seems to be ok. When arriving on the Mailbox Roles it make this error:
02.05.2014 13:42:46.0634] [2] [ERROR] Active Directory operation failed on <dc fqdn>. This error is not retriable. Additional information: An attempt was made to modify an object to include an attribute that is not legal for its class.
Active directory response: 0000207D: UpdErr: DSID-0315121C, problem 6002 (OBJ_CLASS_VIOLATION), data -1731808180
[02.05.2014 13:42:46.0634] [2] [ERROR] An object class violation occurred.
[02.05.2014 13:42:46.0634] [2] Ending processing enable-mailbox
[02.05.2014 13:42:46.0649] [1] The following 1 error(s) occurred during task execution:
[02.05.2014 13:42:46.0649] [1] 0. ErrorRecord: Active Directory operation failed on <dc fqdn>. This error is not retriable. Additional information: An attempt was made to modify an object to include an attribute that is not legal for its class.
Active directory response: 0000207D: UpdErr: DSID-0315121C, problem 6002 (OBJ_CLASS_VIOLATION), data -1731808180
[02.05.2014 13:42:46.0649] [1] 0. ErrorRecord: Microsoft.Exchange.Data.Directory.ADOperationException: Active Directory operation failed on <dc fqdn>. This error is not retriable. Additional information: An attempt was made to modify an object to
include an attribute that is not legal for its class.
Active directory response: 0000207D: UpdErr: DSID-0315121C, problem 6002 (OBJ_CLASS_VIOLATION), data -1731808180
---> System.DirectoryServices.Protocols.DirectoryOperationException: An object class violation occurred.
   at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
   at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
   at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation, IAccountingObject budget, Nullable`1 clientSideSearchTimeout)
   at Microsoft.Exchange.Data.Directory.ADSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Data.Directory.ADSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)
   at Microsoft.Exchange.Data.Directory.ADSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)
   at Microsoft.Exchange.Data.Directory.ADSession.Save(ADObject instanceToSave, IEnumerable`1 properties)
   at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientSession.Microsoft.Exchange.Data.IConfigDataProvider.Save(IConfigurable instance)
   at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalProcessRecord()
   at Microsoft.Exchange.Management.RecipientTasks.EnableMailbox.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
[02.05.2014 13:42:46.0649] [1] [ERROR] The following error was generated when "$error.Clear();
          if (!$RoleIsDatacenter)
            $arbUsers = @(get-user -Filter {lastname -eq "MSExchApproval 1f05a927-3be2-4fb9-aa03-b59fe3b56f4c"} -IgnoreDefaultScope -ResultSize 1);
            if ($arbUsers.Length -ne 0)
              $mbxname = $arbUsers[0].name;
              $mbxs = @( get-mailbox -arbitration -Filter {name -eq $mbxname} -IgnoreDefaultScope -resultSize 1 );
              if ( $mbxs.length -eq 0)
                $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
                if ($dbs.Length -ne 0)
                  enable-mailbox -Arbitration -identity $arbUsers[0] -database $dbs[0].Identity;
        " was run: "Active Directory operation failed on <dc fqdn>. This error is not retriable. Additional information: An attempt was made to modify an object to include an attribute that is not legal for
its class.
Active directory response: 0000207D: UpdErr: DSID-0315121C, problem 6002 (OBJ_CLASS_VIOLATION), data -1731808180
[02.05.2014 13:42:46.0649] [1] [ERROR] Active Directory operation failed on <dc fqdn>. This error is not retriable. Additional information: An attempt was made to modify an object to include an attribute that is not legal for its class.
Active directory response: 0000207D: UpdErr: DSID-0315121C, problem 6002 (OBJ_CLASS_VIOLATION), data -1731808180
[02.05.2014 13:42:46.0649] [1] [ERROR] An object class violation occurred.
[02.05.2014 13:42:46.0649] [1] [ERROR-REFERENCE] Id=SystemAttendantDependent___04bbd8c4a86b4d2c9403cdddf5b39579 Component=EXCHANGE14:\Current\Release\Transport\BCM\Moderated Transport
[02.05.2014 13:42:46.0649] [1] Setup is stopping now because of one or more critical errors.
[02.05.2014 13:42:46.0649] [1] Finished executing component tasks.
[02.05.2014 13:42:46.0712] [1] Ending processing Install-MailboxRole
Any help would be appreciate.
Thanks,
Igor K.

Hi,
The above error may occur when the federated built-in e-mail account that links to the computer account no longer exists or the federated built-in e-mail account in the Active Directory service is corrupted.
I recommend you follow the steps below for troubleshooting:
1. Remove the FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 e-mail account by using the ADSIEdit tool.
a. Run adsiedit.msc.
b. Locate the Default Naming Context node, and then locate to the CN=Users container.
c. Locate and then right-click the CN=FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 container. Then, click Delete.
2.Rerun the Exchange Server 2010 Mailbox role setup application.
3.Create a new federated e-mail account by using the following cmdlet:
New-Mailbox -Arbitration -Name FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 -UserPrincipalName
FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042@<Default_Accepted_Domain>
Hope it helps.
If you need further assistance, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Latest Update Rollup for Exchange 2010 SP3

Hi
Currently we are using RU2 for Exchange 2010 SP3. We are facing an issue with OWA through IE 11 (no support for premium). To correct this issue it's recommended to install RU3. Here we are asking the expert opinion about installing RU7
on all Exchange 2010 servers and whether it makes any different issues or is it enough to install RU3
Thanks in advance
LMS

Hi
Currently we are using RU2 for Exchange 2010 SP3. We are facing an issue with OWA through IE 11 (no support for premium). To correct this issue it's recommended to install RU3. Here we are asking the expert opinion about installing RU7
on all Exchange 2010 servers and whether it makes any different issues or is it enough to install RU3
Thanks in advance
LMS
Personally, if you are going to update the servers, you should apply the latest RU regardless. So I would go with RU7.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Install Exchange 2010 Sp3 on Windows 2012 R2

Dear All,
From Microsoft Exchange support matrix, I can tell that Exchange 2010 Sp3 is not listed on supported page. However when I run the setup, the prerequisite setup check, dose not list any warnings or issues with the setup, all check are green. Is it possible
that the support OS matrix has not been updated? Is Exchange 2010 Sp3 supported on Windows 2012 R2?
http://blogs.technet.com/b/rmilne/archive/2013/09/17/exchange-support-for-windows-server-2012-r2.aspx
Thank you

The prerequisite check is checking that the required Windows components are installed. Exchange 2010 is still not supported on Windows Server 2012 R2.

After Exchange 2010 SP3 upgrade, UAG publised OWA is throwing a "You do not have permissions to view this folder or page" error

Hi,
We have an issue with our OWA page. We are currently publishing OWA via UAG.
We recently upgraded to Exchange 2010 SP3 and then SP3 Rollup7. Since the upgrade, we are keep getting the following error after entering our credentials on the login page. I've tried with every possible browser.
You do not have permissions to view this folder or page
Strangely enough, the mobile phones are sending and receiving emails just fine, the phones use the same OWA link, so it's not an authentication issue, the phones login into the UAG servers with no issues. I can see this on the Active Sessions screen
on Web Monitor.
I've attempted to connect to the OWA by bypassing the UAG server, so putting in the local OWA address of one of my Exchange servers, it works... so the OWA page is up and running.
No error logs get generated on Web Monitor when we receive the permission error, I think this is because it's past authentication, it's on the Exchange layer.
Any insight would be helpful? I'm assuming something changed on the Exchange side after the upgrade.
Just in case, I've upgraded the UAG and TMG servers to the latest SP and Rollup packets.
UAG > SP4
TMG > SP2 Rollup 5

I've found a solution; UAG requires Basic Authentication over OWA. For some reason Integrated Windows Authentication got turned on after the SP3 upgrade.
http://technet.microsoft.com/en-us/library/ee921443.aspx
Turning Integrated Windows Authentication off via the Client Access OWA settings resolved the issue. Though beware, you
have do this on all your Client Access servers.

Correctif cumulatif 2 Exchange 2010 SP3

Similar Messages

Maybe you are looking for