Just echoing the same issue. I received a security violation notice today from our internal security team when they found that this is running on EOL software and the requirement that we move it off the SQL Server Compact 3.5 platform.
1 of 1 people found this helpful
We have spent more than 50 hours in identifying that compact version 4 does not work well with
Orion Platform 2017.1.3 SP3, NPM 12.1, SAM 6.4.0 and
Orion Platform 2018.2.1 SP1, NPM 12.3, SAM 6.6.1
I am going to open a support case to identify support version matrix for SQL compact engine
I got the response from Solarwind support.
Currently we only support 3.5 even for NPM 12.3
There is already a request to have CE 4 and our developers are now looking into it.
We don't have ETA for that yet because this will be on the architectural level.
SolarWinds Technical Support | Unexpected Simplicity
aLTeReGo - I am tagging you for bringing this to your attention. 3.5 has already reached EOL and security teams are giving tough time to keep this version running. Latest version 4.0 SP1 is not going well with Orion platform. I will request your support to prioritize this work. I am sure this will become a big security risk item in my company.
There is currently no way in which to get SQL CE 4.0 SP1 to work with Orion. Rest assured, however, that there are zero known vulnerabilities with SQL CE 3.5 and therefore poses no security risk. We are aware of SQL CE 3.5 being EoL and are actively taking action to address.
We have the same EoL flag showing up on our vulnerability assessment.
I understand there are no known vulnerabilities with SQL CE 3.5 but that is no excuse for SolarWinds to ignore the end of life date, is it too early to inform them that CE 4.0 was released in 2011 and extended support ends in 2021?