Dynamics Community Forum Thread Details

Management Reporter 2012 CU7 - An expression of non-boolean type specified in a context where a condition is expected, near 'ON'.

I had this error and wanted to share in the community that this is a known bug in MR 2012 CU7. MS Support helped me figure out the right path and after installing a hotfix, we stopped getting this error.

Original Problem:

Microsoft.Dynamics.Performance.DataProvider.Core.RequestException: The source system request did not complete successfully. ---> System.Data.SqlClient.SqlException: An expression of non-boolean type specified in a context where a condition is expected, near 'ON'.

at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)

at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)

at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)

at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()

at System.Data.SqlClient.SqlDataReader.get_MetaData()

at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)

at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)

at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)

at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)

at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)

at System.Data.SqlClient.SqlCommand.ExecuteReader()

at Microsoft.Dynamics.Performance.DataProvider.GeneralLedger.DataMart.Data.DataMartReader.Open()

at Microsoft.Dynamics.Performance.DataProvider.GeneralLedger.GLBalanceResult..ctor(GLSystemProvider provider, GLBalanceRequest request, GLDataReaderCollection readers, Object[] sharedResources)

at Microsoft.Dynamics.Performance.DataProvider.GeneralLedger.DataMart.GLProvider.HandleBalanceRequest(GLBalanceRequest request)

at Microsoft.Dynamics.Performance.DataProvider.GeneralLedger.GLSystemProvider.HandleRequest(GLBalanceRequest request)

at Microsoft.Dynamics.Performance.DataProvider.Core.SourceSystemRequest.Handle[TRequest](SourceSystemProvider provider, TRequest request)

at Microsoft.Dynamics.Performance.DataProvider.Core.SourceSystemProvider.SubmitRequest(SourceSystemRequest request)

--- End of inner exception stack trace ---

at Microsoft.Dynamics.Performance.DataProvider.Core.SourceSystemProvider.SubmitRequest(SourceSystemRequest request)

at Microsoft.Dynamics.Performance.DataProvider.Core.SourceSystemProvider.HandleSubmit(SourceSystemRequest request)

at Microsoft.Dynamics.Performance.DataProvider.Core.SourceSystemConnection.Submit(SourceSystemRequest request)

at Microsoft.Dynamics.Performance.Reporting.DataProvider.Server.DirectLinkService.SubmitRequestDirect(SourceSystemConnection connection, GLRequest request)

at Microsoft.Dynamics.Performance.Reporting.Engine.Server.ProviderLink.SubmitRequest(GLRequest request, ProviderConnection context)

at Microsoft.Dynamics.Performance.Reporting.Engine.Server.ProviderLink.SubmitBalanceRequest(ProviderConnection context, GLBalanceRequest balanceRequest)

at Microsoft.Dynamics.Performance.Reporting.Engine.Server.GLLinkAdapter.RetrieveGLDataBatch(Int32 rowNumber)

at Microsoft.Dynamics.Performance.Reporting.Engine.Server.GLLinkAdapter.GetData()

It turns out this is a known bug in MR 2012 CU7 (2.1.7044.43).

There are unfortunately two separate bugs that you are likely running into, as it depends on if you are using the "Legacy" provider or the data mart (DDM) provider for your Management Reporter 2012 companies. These errors are logged as only happening with CU7 for Management Reporter 2012, so I am assuming you have this version installed. The CU7 version number is 2.1.7044.43.

You can determine which provider is being used by looking in the Configuration Console under the "Companies" section in the navigation pane. Locate the company the report is generated for, and look at the "Source System". If it says "Microsoft Dynamics GP", then it is the legacy provider; if it says "Management Reporter data mart", then it is the DDM provider.

Below is the information on the two bugs:

1. Bug 881394 with the legacy provider - Consolidated report containing companies with different functional currencies fails

This occurs when generating a report for multiple companies which have different functional currencies defined. Unfortunately, there is no fix for this issue at this time. The solution is to revert back to CU6 or wait for CU8, which is scheduled to include Currency Translation in the data mart. CU8 is tentatively scheduled for Jan/Feb 2014.

2. If you are using the data mart provider for the reports, then you are encountering bug:

Bug 881381 - Consolidated report containing companies with different functional currencies fails when using data mart provider

This bug does have a hotfix available for it. It will NOT fix bug 881394 with the legacy provider mentioned above. Note that this hotfix can only be applied to an existing install of Management Reporter 2012 with CU7. Also note that the hotfix is a server-only hotfix and will only update the Configuration Console and Management Reporter services. Be sure that you test the hotfix in a test environment prior to installing it in a production environment.

There are no real installation instructions for the hotfix, other than to make sure you have a current backup of the Management Reporter 2012 database, and then double-click the .msp version that matches the OS for the Management Reporter server (32-bit or 64-bit).

Note that this hotfix does also includes a fix for the following bug:

Bug 877367 - Fact Task grows SQL tempdb until it uses all disk space and fails

It is unlikely that you ran into bug 877367 with Management Reporter 2012 as you would have had problems when it was first set up, so you will not really notice any changes with the fix for this bug.

Contact Microsoft Dynamics support to get the hotfix if you need it. Otherwise, CU8 will include the fix when it comes out soon.

Quick Links