You recently upgraded your CCS environment and now you see this error when running a data collection job on your Windows based assets.
16:53:03 | 1928 | 2d0c | src\SnapinLoader.cpp(35) | 0: Error: Loading failed for D:\Program Files\SymantecCCS\CCS\Reporting and Analytics\DPS\Control\Windows\NTBackEndSnapIn.dll.Error code code is = 7f
16:53:05 | 1928 | 2d0c | src\SnapinLoader.cpp(35) | 0: Error: Loading failed for D:\Program Files\SymantecCCS\CCS\Reporting and Analytics\DPS\Control\Oracle\BVOTypeIVSnapin.dll.Error code code is = 7e
16:53:05 | 1928 | 2d0c | src\SQLTreeBuilder.cpp(190) | 0: Exception: RoxieSQLQueryTranslator::Translate: Received an unknown exception.
16:53:05 | 1928 | 2d0c | src\DBMProcess.cpp(352) | 0: Warning: QueryProcessor::ExecuteQuery::Process() encountered an exception: The 'Symantec CCS MS Windows' data-collection module could not be initialized.
The upgrade failed to upgrade all files in the ..\Reporting and Analytics\DPS\Control\Windows\ directory during the upgrade. Most likely cause is that during the upgrade there was still a job running or there was an orphaned Blade.WorkerProcess*.exe process that still had some files "in use" and when the files were in use during the upgrade, they were not upgraded.
Option 1 is to try is to make sure no jobs are running on the CCS manager, open up task manager and kill any remaining "Blade.WorkerProcess*.exe" processes that might still be running and perform a repair from the add/remove programs section.
Option 2 is to reinstall the CCS manager altogether.
Option 3 is more direct and involves having a second CCS manager, at the same version level that does not show the problem. If that scenario applies than the quickest way to recover from this issue is to copy the known good files from the working CCS manager to the corrupted CCS manager. Usually there are three files involved: NTBackEndSnapin.dll, BVNTObjects.dll and BVNTError.dll
Steps to be performed for Option 3:
stop any running CCS jobs showing as running in the CCS console, make sure the next hour or so no new jobs are scheduled to kick off.
stop "Symantec CCS manager" and "Symantec Data Processing Service" services on the affected CCS manager
open up task manager and kill any remaining (and thus orphaned) "Blade.WorkerProcess*.exe" processes that might still be running.
On the manager exhibiting the errors...rename NTBackEndSnapin.dll, BVNTObjects.dll and BVNTError.dll with a ".old" extension.
copy NTBackEndSnapin.dll, BVNTObjects.dll and BVNTError.dll from ..\Reporting and Analytics\DPS\control\Windows of the "good " CCS manager to the "bad" CCS manager into ..\Reporting and Analytics\DPS\control\Windows - overwriting the old ones.
start "Symantec CCS manager" and "Symantec Data Processing Service" services.
run a data collection again and confirm the error no longer shows.
Subscribing will provide email updates when this Article is updated. Login is required.