I created several Data Reviewer batch jobs in 10.2 with no problems. We upgraded both ArcGIS Desktop and Data Reviewer to 10.6.1 and now I've run into this issue, regardless of whether I'm creating a new Data Reviewer batch job or updating one originally written in 10.2.
All my source data is in SDE on SQL server. I create the batch job while attached to the default DB version. When I want to run the batch job against another DB version, some of the layers do not automatically switch their source to that version. I can go in and manually "Change Data Source" in the batch job, but I would have to do that each time. After investigating all the options, I opened the rbj file in Notepadd++ and saw that some of the database names were saved using upper case and some had lower case (ex: VBDB9999 vs. vbdb9999). As an experiment, I did a Replace on all the upper case to make them lower case. The batch file ran fine after that. But every time I add or change the batch file using Data Reviewer, it changes some to upper case again. I made sure my server name in my ArcCatalog connection and in my ODBC connection are both lower case. It didn't make any difference. Does anyone know what Data Reviewer uses to get the connection name? Here is a sample of the code as it shows in Notepad++:
GDB_DPU.GDB_DPU.sManhole SERVER=vbdb9999;INSTANCE=sde:sqlserver:vbdb9999;DBCLIENT=sqlserver;DB_CONNECTION_PROPERTIES=vbdb9999;DATABASE=GDB_DPU;VERSION=GDB_DPU.Base;AUTHENTICATION_MODE=OSA, Type: 2</Value></PropertySetProperty><PropertySetProperty xsi:type='esri:PropertySetProperty'><Key>{B67B1462-6D93-4D4B-872B-E174DD3FF85B}</Key><Value xsi:type='xs:string'>GDB_DPU.GDB_DPU.sPumpStation SERVER=vbdb9999;INSTANCE=sde:sqlserver:vbdb9999;DBCLIENT=sqlserver;DB_CONNECTION_PROPERTIES=vbdb9999;DATABASE=GDB_DPU;VERSION=GDB_DPU.Base;AUTHENTICATION_MODE=OSA, Type: 3</Value></PropertySetProperty><PropertySetProperty xsi:type='esri:PropertySetProperty'><Key>{B6B7936E-414D-4BC4-8369-E219C44CD960}</Key><Value xsi:type='xs:string'>GDB_DPU.GDB_DPU.sBend SERVER=VBDB9999;INSTANCE=sde:sqlserver:VBDB9999;DBCLIENT=sqlserver;DB_CONNECTION_PROPERTIES=VBDB9999;DATABASE=GDB_DPU;VERSION=GDB_DPU.Base;AUTHENTICATION_MODE=OSA, Type: 2</Value></PropertySetProperty><PropertySetProperty xsi:type='esri:PropertySetProperty'><Key>{BB776E14-0EE5-44FC-A9BF-69B796AC17A3}</Key><Value xsi:type='xs:string'>GDB_DPU.GDB_DPU.sFitting SERVER=VBDB9999;INSTANCE=sde:sqlserver:VBDB9999;DBCLIENT=sqlserver;DB_CONNECTION_PROPERTIES=VBDB9999;DATABASE=GDB_DPU;VERSION=GDB_DPU.Base;AUTHENTICATION_MODE=OSA, Type: 2</Value></PropertySetProperty><PropertySetProperty xsi:type='esri:PropertySetProperty'><Key>{BD4EF450-0434-4894-8E90-FD13F7144D4D}</Key><Value xsi:type='xs:string'>GDB_DPU.GDB_DPU.sCasing SERVER=vbdb9999;INSTANCE=sde:sqlserver:vbdb9999;DBCLIENT=sqlserver;DB_CONNECTION_PROPERTIES=vbdb9999;DATABASE=GDB_DPU;VERSION=GDB_DPU.Base;AUTHENTICATION_MODE=OSA, Type: 2</Value></PropertySetProperty><PropertySetProperty xsi:type='esri:PropertySetProperty'><Key>{BD81A164-F813-416D-A3FC-8814742AB446}</Key><Value xsi:type='xs:string'>GDB_DPU.GDB_DPU.sBend SERVER=VBDB9999;INSTANCE=sde:sqlserver:VBDB9999;DBCLIENT=sqlserver;DB_CONNECTION_PROPERTIES=VBDB9999;DATABASE=GDB_DPU;VERSION=GDB_DPU.Base;AUTHENTICATION_MODE=OSA, Type: 2