A Microsoft Dynamics SL System database that has only ever used SQL Authentication will cause dbinfo errors during the initial Management Reporter CU10 integration
This article provides a solution to dbinfo errors that occur during the initial Management Reporter CU10 integration.
Applies to: Microsoft Dynamics SL 2011, Microsoft Dynamics SL 2011 Service Pack 1, Microsoft Dynamics SL 2011 Service Pack 2, Microsoft Dynamics SL 2015
Original KB number: 3061492
Consider the following scenario when you do the initial integration for Management Reporter CU10:
You have a Microsoft Dynamics SL system database that has only used SQL Authentication.
During your initial integration of Management Reporter CU10, the Ledger to Scenario, Dimension Value, and Account to Account tasks fail with:
Value cannot be null.
Parameter name: dbInfo
There are two workarounds to stop receiving these errors:
Configure Windows Authentication with Microsoft Dynamics SL one time and then switch back to SQL Authentication.
Run the following SQL statement after you change the <system db> and <sql server> names:
INSERT INTO Domain ([CurrentPassword] ,[DatabaseName] ,[Description] ,[LocalDB] ,[RecordType] ,[RemoteAccess] ,[ServerName] ,[User1] ,[User2] ,[User3] ,[User4]) VALUES ('' ,'<system db>' ,'Report User Password',0 ,0,0,'<sql server>','','',0,0) GO