Views:
When in the MR Configuration Console and you click the link in the gray box at the top right corner of the screen to ‘Run ERP Data Validation’ the process takes approximately 5-30 seconds to complete and then the Config Console screen updates the date/time on the Validation task and says ‘with success’. 

Manually running the Diagnostic4.sql script on the SL app db’s to check for validation errors returns numerous errors (curyacct with no accthist, etc.) that would typically cause this validation process to fail, yet it says ‘with success’ on the Config Console screen.

Microsoft has confirmed that the behavior with Management Reporter and the validation not running correctly with SL 2018 CU2 specifically is a bug.  It looks like the validation process does not like the new version number for SL2018 CU2. There is a getversion stored proc in the SL system database that verifies that the SL version installed matches the database version. The proc for SL2018 CU2 is 10.02.30430. When the proc is changed to the CU1 version 10.01.21108, the validation then runs properly.  

 

**Note - As a precaution confirm recent backups of the SL databases exist before proceeding.

Run the following against the SL System database to alter the existing getversion proc.  It alters the proc so that if it sees that MR (or more specifically SLGLADAPTER) is calling the getversion proc, then it returns the SL 2018 CU1 build number (satisfying the MR validation process), else if it is the SL login calling the get version proc for example, it returns the proper SL 2018 CU2 build number.  Once altered, we can leave this proc in place and access SL AND allow the MR validation process to run all at the same time.

ALTER Proc [dbo].[getVersion] as
If APP_NAME() = 'SLGLADAPTER'
    select '10.01.30430    '
else
    select '10.02.30430    '
GO

 

  1. Run the above alter proc script against the SL System db.
  2. Kick off the MR ERP Data Validation process in the MR Configuration Console screen. Wait for it to return ‘-with success’ or with errors. If errors are returned resolve them before proceeding.
  3. Remove and reconfigure the MR data mart integration/database.
Keywords: MR, management, reporter, ERP, date, validation, false, success