djcanter
asked on
Exchange 2010 SP2 - Rollup Update 5-V2 (and Rollup Update 4 - V2) - Brokern OWA Search
I installed Exchange SP2 Rollup Update 5 V2 to address a few bugs I was experiencing. Now when searching from OWA (at both the local fqdn and external fqdn) I receive the following error. Reverting to SP2 without either Update Rollup resolves the issue, but I am hoping someone can point me in the right direction. I have 1 Exchange server, and no ssl offloading. I am running on Server 2012, but per my call to MSFT 2 weeks ago for the issue addressed in Rollup 5, this is supported.
I have already run the resetsearchindex.ps1 -all
Request
Url: https://exch1.company.com:443/owa/ev.owa?oeh=1&ns=MsgVLV2&ev=LoadFresh&pfmk=M23:1356969497411
User host address: 10.254.1.5
User: Darrell Canter
EX Address: /o=company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recip ients/cn=d canter
SMTP Address: dcanter@company.com
OWA version: 14.2.328.9
Mailbox server: EXCH1.company.com
Exception
Exception type: System.TypeInitializationE xception
Exception message: The type initializer for 'Microsoft.Exchange.Data.S earch.AqsP arser.AqsP arser' threw an exception.
Call stack
Microsoft.Exchange.Data.Se arch.AqsPa rser.AqsPa rser.Parse AndBuildQu ery(String query, ParseOption parseOption, CultureInfo culture, Boolean isContentIndexingEnabled, RescopedAll rescopedAll, IRecipientResolver recipientResolver, IPolicyTagProvider policyTagProvider)
Microsoft.Exchange.Clients .Owa.Core. SearchFilt erGenerato r.Execute( String searchString, Boolean isContentIndexingEnabled, Folder folder, SearchScope searchScope)
Microsoft.Exchange.Clients .Owa.Core. SearchFilt erGenerato r.Execute( String searchString, Boolean isContentIndexingEnabled, CultureInfo userCultureInfo, IPolicyTagProvider policyTagProvider, Folder folder, SearchScope searchScope, QueryFilter advancedQueryFilter)
Microsoft.Exchange.Clients .Owa.Core. FolderSear ch.Execute (UserConte xt userContext, Folder folder, SearchScope searchScope, String searchString, Boolean newSearch, Boolean asyncSearch)
Microsoft.Exchange.Clients .Owa.Premi um.FolderV irtualList ViewEventH andler2.Bi ndToFolder ()
Microsoft.Exchange.Clients .Owa.Premi um.Message VirtualLis tViewEvent Handler2.G etListView ()
Microsoft.Exchange.Clients .Owa.Premi um.Virtual ListViewEv entHandler 2.Internal LoadFresh( Boolean renderHeaders)
Microsoft.Exchange.Clients .Owa.Premi um.Message VirtualLis tViewEvent Handler2.L oadFresh()
Inner Exception
Exception type: Microsoft.StructuredQuery. Structured QueryExcep tion
Exception message: Exception of type 'Microsoft.StructuredQuery .Structure dQueryExce ption' was thrown.
Call stack
Microsoft.StructuredQuery. Parser.Par se(String strQuery, List`1 lstCustomProperties)
Microsoft.Exchange.Data.Se arch.AqsPa rser.AqsPa rser..ccto r()
I have already run the resetsearchindex.ps1 -all
Request
Url: https://exch1.company.com:443/owa/ev.owa?oeh=1&ns=MsgVLV2&ev=LoadFresh&pfmk=M23:1356969497411
User host address: 10.254.1.5
User: Darrell Canter
EX Address: /o=company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recip
SMTP Address: dcanter@company.com
OWA version: 14.2.328.9
Mailbox server: EXCH1.company.com
Exception
Exception type: System.TypeInitializationE
Exception message: The type initializer for 'Microsoft.Exchange.Data.S
Call stack
Microsoft.Exchange.Data.Se
Microsoft.Exchange.Clients
Microsoft.Exchange.Clients
Microsoft.Exchange.Clients
Microsoft.Exchange.Clients
Microsoft.Exchange.Clients
Microsoft.Exchange.Clients
Microsoft.Exchange.Clients
Inner Exception
Exception type: Microsoft.StructuredQuery.
Exception message: Exception of type 'Microsoft.StructuredQuery
Call stack
Microsoft.StructuredQuery.
Microsoft.Exchange.Data.Se
You mentioned that you are running exchange on Windows Server 2012.. So far only exchange 2013 is informed as supported on Windows 2012. Exchange 2010 SP2 needs to be installed only on Windows 2008 or Windows Server 2008 R2
ASKER
As noted above, per Microsoft Support, this configuration is supported.
Not sure why they didnt announce it officially
http://blogs.technet.com/b/exchange/archive/2012/09/14/windows-server-2012-and-exchange.aspx
http://blogs.technet.com/b/exchange/archive/2012/09/14/windows-server-2012-and-exchange.aspx
ASKER
if you dont have anything constructive to contribute, please refrain from participating.
Hi djcanter,
If you find anything wrong on my update.. Please be sorry for that.
If you find anything wrong on my update.. Please be sorry for that.
You have been given the wrong information by Microsoft support. If you want to send me the case number then I will ensure that the support rep who told you that gets corrected.
Exchange 2010 is NOT supported on Windows 2012 until Exchange 2010 SP3 is released. The latest rollup does not introduce support, as the Powershell commandlets have to be modified, among other things.
For example, PowerShell 3.0 (part of Windows 2012) is not supported:
http://blogs.technet.com/b/exchange/archive/2012/12/14/windows-management-framework-3-0-on-exchange-2007-and-exchange-2010.aspx
So you are in an unsupported configuration.
Simon.
Exchange 2010 is NOT supported on Windows 2012 until Exchange 2010 SP3 is released. The latest rollup does not introduce support, as the Powershell commandlets have to be modified, among other things.
For example, PowerShell 3.0 (part of Windows 2012) is not supported:
http://blogs.technet.com/b/exchange/archive/2012/12/14/windows-management-framework-3-0-on-exchange-2007-and-exchange-2010.aspx
So you are in an unsupported configuration.
Simon.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
My configuration was identified as supported on a previous issue with Microsoft. This issue is documented on other forums as occuring on Server 2008 R2 also with no known resolution. The only answer given on this question was that I had an unsupported installation.
After installing SP3 which officeially adds support for Server 2012, this issue still occurs. I therefore used the workaround above.
After installing SP3 which officeially adds support for Server 2012, this issue still occurs. I therefore used the workaround above.
ASKER
http://exchangeblog.pl/en/2012/10/exchange-2010-sp2-rollup-4-errors-after-update-msftesql-and-mapiexceptionunexpectedmailboxstate/
I will be performing this action tonight .