After Upgrading from Snow License Manager 8 to Snow License Manager 9; the Data Update Job (DUJ) fails to run successfully.

• Snow License Manager (SLM) 9.x

After reviewing the log files & running Select * from tblErrorlog the Snow License Manager database - the following error was present:

Error #3930 in procedure UpdateQuarantinetblComputer line 366. [The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction.]

Trying a reset on the DUJ was unsuccessful as it seems to fail on UpdateQuarantinetblComputer; so after digging a bit deeper - The procedure inv.UpdateQuarantinetblComputer utilizes NotificationComputerAdd in its procedure and previously in Snow License Manager 8 - it has been continuing with the data update job even though errors existed.

Now in SLM 9 it stops the whole thing. We can see previous error:

Error #9420 in procedure NotificationComputerAdd line 111. [XML parsing: line 1, character 253, illegal xml character] [An error occurred when running quarantine management for CID 1. The job will continue.]

It looks like this used to appear when the customer was on SLM 8 but the job would proceed.  We only saw an general error in the logs about the DUJ stopping and this error, which just seems to cover up the real error message happening in the background:

The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction. 

The Computer we found had an incorrect Model below in SLM seen below:

After deleting the computer & ensuring the Data Update Job (DUJ) is stopped the job was monitored & successful.

In Snow License Manager 9; when running the Data Update Job; illegal characters will cause the job to fail.