Exchange 2010 SP3 Prerequisites

Trying to run Exchange 2010 SP3 and the prerequisite check indicates I need the following:
Error:
Install hotfix Microsoft Knowledge Base article 982867 from http://code.msdn.microsoft.com/KB982867.
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex28883C&l=0&cl=cp
As far as I can tell that Hotifx is no longer offered. How do I get this hotfix so I can install Exchange 2010 SP3?

Is it Windows 2008 R2 SP1 with .NET Framework 3.5 Service Pack 1? Install this...
http://support.microsoft.com/kb/2637518/en-us
Blog |
Get Your Exchange Powershell Tip of the Day from here

Similar Messages

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.

Exchange 2010 SP3 - Can DAG member be on OS 2012 R2 STD?

Hi guys.
We have Exchange 2010 SP3 on 2008 r2 enterprise.
now we are thinking about having DAG. I know that recommendations is to have the same OS on 2nd Exchange server but still is it possible to make DAG between: Exchange 2010 SP3 on 2008 r2 enterprise and on other side Exchange 2010 SP3 on 2012 R2 STD?
with best regards,
bostjanc

Hi guys.
We have Exchange 2010 SP3 on 2008 r2 enterprise.
now we are thinking about having DAG. I know that recommendations is to have the same OS on 2nd Exchange server but still is it possible to make DAG between: Exchange 2010 SP3 on 2008 r2 enterprise and on other side Exchange 2010 SP3 on 2012 R2 STD?
with best regards,
bostjanc
No. It wont let you do that.
http://technet.microsoft.com/en-us/library/dd638104(v=exchg.141).aspx
DAGs are available in both Exchange 2010 Standard Edition and Exchange 2010 Enterprise Edition. In addition, a DAG can contain a mix of servers running Exchange 2010 Standard Edition and Exchange 2010 Enterprise Edition.
Each member of the DAG must also be running the same operating system. Exchange 2010 is supported on both the Windows Server 2008 and Windows Server 2008 R2 operating systems. All members of a DAG must run either Windows Server 2008 or Windows Server 2008
R2. They can't contain a combination of both Windows Server 2008 and Windows Server 2008 R2.
In addition to meeting the prerequisites for installing Exchange 2010, there are operating system requirements that must be met. DAGs use Windows Failover Clustering technology, and as a result, they require the Enterprise version of Windows.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

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

Exchange 2010 SP3 upgrade

Dear Exchange admin,
We tried to upgrade Exchange 2010 SP1 to Exchange 2010 SP3 .In HQ site all preparation finished smoothly.
But in DR we are unable to do even preparation.We are getting the following error.
Please advice me how can proceed.
Summary: 4 item(s). 2 succeeded, 2 failed.
Elapsed time: 00:00:37
Configuring Prerequisites
Completed
Elapsed Time: 00:00:00
Organization Prerequisites
Failed
Error:
Setup needs to contact the Active Directory schema master but this computer is not in the same Active Directory site as the schema master (Default-First-Site-Name).
Click here for help... http://go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.14&id=2376fec1-b9ce-44db-beb6-cb9ac4788988
Error:
Setup encountered a problem while validating the state of Active Directory: Exchange organization-level objects have not been created, and setup cannot create them because the local computer is not in the same domain and site as the schema master. Run
setup with the /prepareAD parameter on a computer in the domain kfupm and site Default-First-Site-Name, and wait for replication to complete.
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex28883C&l=0&cl=cp
Elapsed Time: 00:00:14
Languages Prerequisites
Completed
Elapsed Time: 00:00:04
Mailbox Role Prerequisites
Failed
Error:
Setup encountered a problem while validating the state of Active Directory: Exchange organization-level objects have not been created, and setup cannot create them because the local computer is not in the same domain and site as the schema master. Run
setup with the /prepareAD parameter on a computer in the domain kfupm and site Default-First-Site-Name, and wait for replication to complete.
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex28883C&l=0&cl=cp
Error:
Setup cannot continue with the upgrade because the 'mmc' () process (ID: 4508) has open files. Close the process and restart Setup.
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex28883C&l=0&cl=cp
Error:
Setup cannot continue with the upgrade because the 'powershell' () process (ID: 3808) has open files. Close the process and restart Setup.
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex28883C&l=0&cl=cp
Error:
Setup cannot continue with the upgrade because the 'mmc' (4508) process (ID: ) has 'Microsoft.Exchange.Management.SnapIn.Esm.dll' loaded. Close the process and restart setup.
Click here for help... http://go.microsoft.com/fwlink/?linkid=30939&l=en&v=ExBPA.14&id=f0d3f291-5a52-43ea-9121-24aa7cd0c30e
Warning:
Install hotfix Microsoft Knowledge Base article 2550886 from http://support.microsoft.com/kb/2550886 to improve Windows Failover Cluster transient communication instability when deploying stretched Database Availability Groups across datacenters.
Elapsed Time: 00:00:18
Ashraf

Hi Ashraf
Thank you for your question.
Exchange update cannot continue because the computer that is running update is not in the same Active Directory site or domain as the server that is assigned the domain schema master role, also known as flexible single master operations or FSMO.
You can refer to the following link to change exchange site schema:
http://technet.microsoft.com/en-US/us-cn/zh-hans-cn/library/2376fec1-b9ce-44db-beb6-cb9ac4788988.aspx
You also notice the order for updated:
1.Client Access servers (beginning with the internet-facing site)
2.Hub Transport and Edge Transport servers
3.Mailbox servers
4.Unified Messaging servers
You can refer to the following link to update:
http://exchangeserverpro.com/installing-exchange-server-2010-service-pack-3/
If there are any questions, please let me know.
Best Regard,
Jim

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

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.

[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.

Is WMF3 or WMF4 supported in Exchange 2010 SP3 UR5 installed on Server 2008 R2 SP1?

We'd like to upgrade WMF (aka powershell) on our Exchange 2010 servers but I haven't been able to find any updated information on support with the most recent servicepack/update rollup.
Is installing WMF3 or WMF4 supported on Server 2008 R2 SP1 w/ Exchange 2010 SP3 UR5?

WindowsPowerShell 3.0 is supported. Haven't seen 4.0 running for exchange 2010 on 2008 R2
http://blogs.technet.com/b/heyscriptingguy/archive/2013/11/30/weekend-scripter-wmf-powershell-and-exchange-server-compatibility.aspx
http://blog.crayon.no/blogs/janegil/archive/2013/11/17/how_2D00_to_2D00_install_2D00_windows_2D00_powershell_2D00_4_2D00_0.aspx
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
Gulab,
Where did you read that WMF3 is supported on Exchange 2010 SP3 on Server 2008 R2?
Neither of the links you pasted suggest that and in fact explicitly say "There has been no testing with ExchangeServer 2010 SP3 and WMF 3.0 installed on Windows Server 2008 R2."
My Bad, that was TYPO...
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Problems with OWA after installing Exchange 2010 SP3

Hi,
I just installed Exchange 2010 SP3 on a SBS 2011 machine. The installation completed successfully, but after the installation OWA isn't working anymore. When I browse to OWA I get the following message:
I did a reset for the OWA vritual directory, but nothing helps..
Stack Trace:
[NullReferenceException: Object reference not set to an instance of an object.]
Microsoft.Exchange.Clients.Owa.Core.Logon..ctor() +28
ASP.auth_logon_aspx..ctor() +17
__ASP.FastObjectFactory_app_web_9ficbu1h.Create_ASP_auth_logon_aspx() +30
System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp, Boolean noAssert) +137
System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath) +49
System.Web.MaterializeHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +424
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +262

Hi Alelieveld,
When you reset a virtual directory, the virtual directory is removed and a new virtual directory with default settings is created.
After you reset the VD, did you restart IIS?
For more information, please see:
Reset Client Access Virtual Directories
http://technet.microsoft.com/en-us/library/ff629372(v=exchg.141).aspx
Frank Wang
TechNet Community Support

SME 7.1 not working with Exchange 2010 SP3 UR8v2 and OnTap 8.2.3 7mode

Followed IMT and installed software that NetApp said would work.Ontap 8.2.3 7-modevmWare 5.0 SP3Microsoft Windows Server 2008 R2 SP1Exchange 2010 SP3 UR8v2NetApp Host Tools 6.0.2SnapDrive 7.1.1SME 7.1 Everything connects fine. SnapDrive sees my drives. SME connects to Exchange Server. However in the process of configuring SME, I get the following error. I have followed knowledge base article and increased the timeout of DFM connection in registry, but that has not solved the problem. Has anyone run into this before? SME 6.1 works fine, but is not compatible with SnapDrive 7.1.1 (causes verifications to fail because server can't mount clone) and lower SnapDrive versions are not compatible with Ontap 8.2.3. I am in a real bind here. Thanks in advance.

the following configuration for SME 7.1 is no longer supported: Windows Server 2008 R2Exchange 2010 SP3 RU1 – RU5WMF/PowerShell 3.0SME 7.1 The supported configuration will now be: Windows Server 2008 R2Exchange 2010 SP3 RU5WMF/PowerShell 4.0SME 7.1 this is because Microsoft does not support WMF 3.0 on Server 2008 R2 running Exchange 2010 SP3, with any RU version.SME 7.1 requires a minimum of PowerShell 3.0 (part of WMF 3.0) in order to run. Feel free to review the Exchange Server Supportability Matrix located here: https://technet.microsoft.com/en-us/library/ff728623%28v=exchg.150%29.aspx. All existing documentation (ISG, Admin Guide, IMT) will be updated shortly to reflect this change in requirements. hope that helps,Domenico.

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 SP3 UR9 OWA users cannot open mail items

We recently had users reporting unable to open items in OWA. Issue is confirmed across all CAS servers.
Issue started while on Exchange 2010 SP3 UR8v2, we upgraded to Exchange Server 2010 SP3 UR9 during troubleshooting.
3 AD Site DAG, multi-role servers
So far we have done the following to troubleshoot:
* Check security propagation for account permissions.
* Check security on all virtual directories.
* Check permissions on web.config
* Re-run PrepareAD
* Uninstall and reinstall CAS role
Please review the errors below and let me know if you have any words of wisdom on this issue. Thanks!
Errors:
Request
Url: https://domain.com:443/owa/forms/premium/SubPageEventHandler.aspx?ae=Item&a=Preview&t=IPM.Conversation&id=CID.K5jy5dmxQru9sRoituQBvQ%3d%3d.LgAAAAD5wKVzMPRWToarE%2bpbowlJAQAqvhe3P6jjT4tregHxbY2pANbZjrf2AAAB.1DEA1tmOt%2fIAAAAAiIUWAAAAAAA%3d&calist=&canary=BV_LDf9RIkOwB1AREM0QuJ6gLZ_9QNIIWwpFOZKWH-iRvFnaQLhvOrQQBEkvAoafNX8eyWt3pOI.&SP=1&pfmk=M46%3a1427993956363&subpage=ReadConversation.ascx
User: user
EX Address: /o=company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=user
SMTP Address: [email protected]
OWA version: 14.3.235.1
Mailbox server: server.domain.com
Exception
Exception type: System.UriFormatException
Exception message: Invalid URI: The format of the URI could not be determined.
Call stack
System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
Microsoft.Exchange.Security.RightsManagement.DrmClientUtils.GetServiceLocation(SafeRightsManagementSessionHandle sessionHandle, ServiceType serviceType, ServiceLocation serviceLocation, String issuanceLicense)
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.GetOnPremiseRmsServerUri()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.GetRmsServerActiveCryptoMode()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.DrmEnvironment.InitializeEnvironment()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.Initialize()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.InitializeIfNeeded()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.get_IRMConfig()
Microsoft.Exchange.Clients.Owa.Core.UserContext.get_IsIrmEnabled()
Microsoft.Exchange.Clients.Owa.Premium.ConversationUtilities.LoadConversation(UserContext userContext, OwaStoreObjectId owaConversationId, PropertyDefinition[] requestedProperties)
Microsoft.Exchange.Clients.Owa.Premium.ReadConversation.OnLoad(EventArgs e)
System.Web.UI.Control.LoadRecursive()
System.Web.UI.Control.LoadRecursive()
System.Web.UI.Control.LoadRecursive()
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Request
Url: https://domain.com:443/owa/forms/premium/SubPageContainer.aspx?ae=Item&a=Open&t=IPM.Note&id=RgAAAAD5wKVzMPRWToarE%2bpbowlJBwAqvhe3P6jjT4tregHxbY2pANbZjrf4AACsvITjR9r%2fQaXcC90BhfOwAI8oXwgBAAAJ&pspid=_1427993955843_521407833&subpage=ReadMessage.ascx
User: user
EX Address: /o=company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=user
SMTP Address: [email protected]
OWA version: 14.3.235.1
Mailbox server: server.domain.com
Exception
Exception type: System.UriFormatException
Exception message: Invalid URI: The format of the URI could not be determined.
Call stack
System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
Microsoft.Exchange.Security.RightsManagement.DrmClientUtils.GetServiceLocation(SafeRightsManagementSessionHandle sessionHandle, ServiceType serviceType, ServiceLocation serviceLocation, String issuanceLicense)
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.GetOnPremiseRmsServerUri()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.GetRmsServerActiveCryptoMode()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.DrmEnvironment.InitializeEnvironment()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.Initialize()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.InitializeIfNeeded()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.get_IRMConfig()
Microsoft.Exchange.Clients.Owa.Core.UserContext.get_IsIrmEnabled()
Microsoft.Exchange.Clients.Owa.Premium.ReadMessage.AddIrmMessageToInfobar()
Microsoft.Exchange.Clients.Owa.Premium.ReadMessage.AddMessagesToInfobar()
Microsoft.Exchange.Clients.Owa.Premium.ReadMessage.OnLoad(EventArgs e)
System.Web.UI.Control.LoadRecursive()
System.Web.UI.Control.LoadRecursive()
System.Web.UI.Control.LoadRecursive()
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Hi Noel,
Base on my search, it may be due to IRM feature been enabled for OWA.
I recommend you use the following command to check if the value of IRMEnabled parameter is true:
Get-OWAVirtualDirectory – Identity “servername\owa (default web site)” |FL name,IRMEnabled
If the value is true, you can use "Set-OWAVirtualDirectory" cmdlt to change it to false, and check if any helps.
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Niko Cheng
TechNet Community Support

Exchange 2010 SP3 Create Dynamic DL for Direct Reports

I am not sure this is possible but if there is a will there is a way I guess.
System: Exchange 2010 SP3 on Windows Server 2008 R2
I am trying to see if there is a way to create dynamic DLs for Manager(s) direct reports.
Example: Manager has 5 people that report directly to them, is there a way to make an dynamic email distribution list that will poll the direct reports as people leave or hired.
I know I can create one manually but some depts. may have high turnover rates which increase overhead so I am just trying to simplify the process. I of course googled my question but not getting the results I intended.
Thanks.

hi,
as from above i understand you are asking about creating an custom attribute and then referencing them .. if yes please check below command
Get-Mailbox -OrganizationalUnit Sales | Set-Mailbox CustomAttribute1 "SalesOU"Now you can create an e-mail address policy for all recipients that have the CustomAttribute1 property that equals SalesOU, as shown in this example.
New-EmailAddressPolicy -Name "Sales" -RecipientFilter { CustomAttribute1 -eq "SalesOU"} -EnabledEmailAddressTemplates "SMTP:%s%[email protected] check this.. http://technet.microsoft.com/en-us/library/ee423541%28v=exchg.150%29.aspx
MARK AS USEFUL/ANSWER IF IT DID
Thanks
Happiness Always
Jatin

Outlook 2013 Category view not updating after Exchange 2010 SP3 RU3

After updating to Exchange 2010 SP3 RU3 last night, users who use categories view in Outlook 2013 are complaining that the view does not update. The alert is received in the notification area and the unread message count next to Inbox updates appropriately.
The view can be force updated by switching between All and Unread, by using Reset View, or closing and opening Outlook. It seems anything that forces a 'redraw' of the view will update it - except for the actual reception of email. I easily replicated
this issue. For reference:
Exchange 2010 SP3 RU3
Windows 7 x64 Ent
Outlook 2013 (15.0.4551.1004) 32-bit
I do see that SP3 RU4 has been released, however the only change listed is a security patch.
Thank you for any ideas.

Hi, Everyone –
This has been a known issue for a very long time – we have people at our workplace that are very disappointed since a feature as great as categorizing email (not using tasks) has become broken and has not even been considered to be fixed for
over half a year. It was not fixed in the updates for Patch Tuesday this week.
I would like to confirm that this is an issue with Outlook 2010 and 2013 when running the latest Exchange 2010 and there is NO FIX
– I have scoured the internet for a solution – all proposed "textbook" solutions do not work and I am positive that the issue can be recreated; however, everyone from Microsoft does not mention trying to recreate the issue at all.
The workaround of creating a rule to send new emails to a category could break other pre-existing rules and cause more frustration and wasted time for users/IT before and after the issue is fixed.
Please fix this issue sooner than later, as the Categories view is completely broken and unusable at this point in time.
Regards,
IT Helper

Exchange 2010 SP3 Prerequisites

Similar Messages

Maybe you are looking for