SCA import fails with "illegal xml character"

Hello all,
since 4 days the import to SCA is failing with this message:
“2016-01-19 04:01:26 (+0:00:00.012) ERROR: Sequel::DatabaseError: Java::ComMicrosoftSqlserverJdbc::SQLServerException: XML parsing: line 111, character 4841, illegal xml character
com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(com/microsoft/sqlserver/jdbc/SQLServerException.java:216)”

Any idea/hint welcome.

Thanks, Michael

First lines out of Import Log:
Logfile created on 2016-01-19 04:00:40 +0000 by logger.rb/v1.2.7
2016-01-19 04:00:40 (+0:00:00.000) INFO: TEMA version: 1.6.139
2016-01-19 04:00:41 (+0:00:00.725) INFO: ETL before snapshot task: Calling all Model.before_snapshot blocks: Start
2016-01-19 04:00:43 (+0:00:01.753) INFO: ETL before snapshot task: Calling all Model.before_snapshot blocks: Success
2016-01-19 04:00:43 (+0:00:00.005) INFO: ETL task: Initialize datasource IEM: Start
2016-01-19 04:00:43 (+0:00:00.068) INFO: ETL task: Initialize datasource IEM: Success
2016-01-19 04:00:43 (+0:00:00.001) INFO: ETL Datasource task: from IEM - DatasourceSite (0x000000000C5F4FDE - N/A): Start
2016-01-19 04:00:43 (+0:00:00.446) INFO: DatasourceSite items: 9
2016-01-19 04:00:43 (+0:00:00.013) INFO: ETL Datasource task: from IEM - DatasourceSite (0x000000000C5F4FDE - 0x000000000CA4797E): Success
2016-01-19 04:00:43 (+0:00:00.000) INFO: ETL Datasource task: from IEM - RawDatasourceAnalysisActivation (0x000000000C5F4FDE - N/A): Start
2016-01-19 04:00:43 (+0:00:00.022) INFO: ETL Datasource task: from IEM - RawDatasourceAnalysisActivation (0x000000000C5F4FDE - 0x000000000CA4797E): Success
2016-01-19 04:00:43 (+0:00:00.001) INFO: ETL Datasource task: from IEM - RawDatasourceAnalysis (0x000000000C5F4FDE - N/A): Start
2016-01-19 04:00:54 (+0:00:10.192) INFO: ETL Datasource task: from IEM - RawDatasourceAnalysis (0x000000000C5F4FDE - 0x000000000CA4797E): Success
2016-01-19 04:00:54 (+0:00:00.001) INFO: ETL Datasource task: from IEM - DatasourceAnalysis (0x000000000C5F4FDE - N/A): Start
2016-01-19 04:00:55 (+0:00:01.532) INFO: DatasourceAnalysis items: 123
2016-01-19 04:00:55 (+0:00:00.012) INFO: ETL Datasource task: from IEM - DatasourceAnalysis (0x000000000C5F4FDE - 0x000000000CA4797E): Success
2016-01-19 04:00:55 (+0:00:00.001) INFO: ETL Datasource task: from IEM - DatasourceProperty (0x000000000C5F4FDE - N/A): Start
2016-01-19 04:01:00 (+0:00:05.002) INFO: DatasourceProperty items: 128
2016-01-19 04:01:00 (+0:00:00.012) INFO: ETL Datasource task: from IEM - DatasourceProperty (0x000000000C5F4FDE - 0x000000000CA4797E): Success
2016-01-19 04:01:00 (+0:00:00.001) INFO: ETL Datasource task: from IEM - RawComputerId (0x000000000C5F4FDE - N/A): Start
2016-01-19 04:01:00 (+0:00:00.301) INFO: ETL Datasource task: from IEM - RawComputerId (0x000000000C5F4FDE - 0x000000000CA4797E): Success
2016-01-19 04:01:00 (+0:00:00.001) INFO: ETL Datasource task: from IEM - Computer (0x000000000C5F4FDE - N/A): Start
2016-01-19 04:01:01 (+0:00:00.621) INFO: Computer items: 19
2016-01-19 04:01:01 (+0:00:00.013) INFO: ETL Datasource task: from IEM - Computer (0x000000000C5F4FDE - 0x000000000CA4797E): Success
2016-01-19 04:01:01 (+0:00:00.000) INFO: ETL Datasource task: from IEM - ComputerPropertyValue (0x000000000C5F4FDE - N/A): Start
2016-01-19 04:01:01 (+0:00:00.373) INFO: ETL Datasource task: from IEM - ComputerPropertyValue (0x000000000C5F4FDE - 0x000000000CA4797E): Success
2016-01-19 04:01:01 (+0:00:00.001) INFO: ETL Datasource task: from IEM - ComputerDimension (0x000000000C5F4FDE - N/A): Start
2016-01-19 04:01:02 (+0:00:00.472) INFO: ETL Datasource task: from IEM - ComputerDimension (0x000000000C5F4FDE - 0x000000000CA4797E): Success
2016-01-19 04:01:02 (+0:00:00.000) INFO: ETL Datasource task: from IEM - RawDatasourceFixlet (0x000000000C5F4FDE - N/A): Start
2016-01-19 04:01:03 (+0:00:00.969) ERROR: SQL: {call [dbo].etl_raw_datasource_fixlets}
2016-01-19 04:01:03 (+0:00:00.001) ERROR: Batch execution error:
2016-01-19 04:01:26 (+0:00:23.194) INFO: ETL Datasource task: from IEM - RawDatasourceFixlet (0x000000000C5F4FDE - 0x000000000CA4797E): Failed
2016-01-19 04:01:26 (+0:00:00.012) ERROR: Sequel::DatabaseError: Java::ComMicrosoftSqlserverJdbc::SQLServerException: XML parsing: line 111, character 4841, illegal xml character
com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(com/microsoft/sqlserver/jdbc/SQLServerException.java:216)
com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(com/microsoft/sqlserver/jdbc/SQLServerStatement.java:1515)
com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatementBatch(com/microsoft/sqlserver/jdbc/SQLServerPreparedStatement.java:1299)
com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtBatchExecCmd.doExecute(com/microsoft/sqlserver/jdbc/SQLServerPreparedStatement.java:1209)

I’m guessing one of the fixlets in your environment since 4 days ago has some kind of unexpected thing in it that’s tripping up our parser. Did you add any new sites or custom sites 4 days ago?

Thanks for the hint. Will seach in this direction.