Quantcast
Channel: LANDESK User Community : Popular Discussions - Patch Manager
Viewing all articles
Browse latest Browse all 3522

The core (servername) received the vulnerability info but was unable to process it!

$
0
0

I have recently done a clean install of LDMS 8.8 SP3 onto a new server.

 

We have installed the new agent onto about 1000 machines, but have noticed that vulnerability scans are not getting through to the core server.

 

Inventory scans are getting through and scheduled tasks are working only vulscans seem to not be working.

 

Have tried running DBrepair and Coredbutil without any effect.

Have tried changing the application pools idenity to local system without any effect.

Have checked the permissions on the core server relating to the IIS virtual directories and file permissions as posted in another thread.

 

Any advice would be appreciated.

 

Thanks in advance.

 

Part of the vulscan log from a client is shown below:

 

1852    Patch is NOT installed
  1852 Checking vulnerability LD88-Invoker-20253-882, rule index 1
  1852 VUL: 'LD88-Invoker-20253-882' not detected.  No affected platforms were found.

  1852    Patch is NOT installed
  1852 ProcessRules: detected compliance=0
  1852 Sending scan results to core HQ-LANDESKAPP
Thu, 13 Aug 2009 14:01:14 HTTP POST: http://HQ-LANDESKAPP/incomingdata/postcgi.exe?prefix=ldlogon\VulScanResults\&name={171FCCCC-753D-FC45-934B-4842B058F93C}.3.vrz
Thu, 13 Aug 2009 14:01:14 Failed http://HQ-LANDESKAPP/incomingdata/postcgi.exe?prefix=ldlogon\VulScanResults\&name={171FCCCC-753D-FC45-934B-4842B058F93C}.3.vrz on server (0), server status: 404.
Thu, 13 Aug 2009 14:01:14 URL not found.  Giving up.
Thu, 13 Aug 2009 14:01:14 SendRequest: SOAPAction: "http://tempuri.org/PutResultsByFile"


Thu, 13 Aug 2009 14:01:14 Success
  1852 ERROR: The core (HQ-LANDESKAPP) received the vulnerability info but was unable to process it!  Device ID: {171FCCCC-753D-FC45-934B-4842B058F93C}
  1852 -------------------ProcessRules of type 4----------------------
  1852 Getting definition data from core HQ-LANDESKAPP
Thu, 13 Aug 2009 14:01:14 HTTP POST: http://HQ-LANDESKAPP/WSVulnerabilityCore/VulCore.asmx
Thu, 13 Aug 2009 14:01:14 Success
  1852 No scan results to report.  Returning a single blank entry.
  1852 ProcessRules: detected compliance=0
  1852 Sending scan results to core HQ-LANDESKAPP
Thu, 13 Aug 2009 14:01:14 HTTP POST: http://HQ-LANDESKAPP/incomingdata/postcgi.exe?prefix=ldlogon\VulScanResults\&name={171FCCCC-753D-FC45-934B-4842B058F93C}.4.vrz
Thu, 13 Aug 2009 14:01:15 Failed http://HQ-LANDESKAPP/incomingdata/postcgi.exe?prefix=ldlogon\VulScanResults\&name={171FCCCC-753D-FC45-934B-4842B058F93C}.4.vrz on server (0), server status: 404.
Thu, 13 Aug 2009 14:01:15 URL not found.  Giving up.
Thu, 13 Aug 2009 14:01:15 SendRequest: SOAPAction: "http://tempuri.org/PutResultsByFile"


Thu, 13 Aug 2009 14:01:15 Success
  1852 ERROR: The core (HQ-LANDESKAPP) received the vulnerability info but was unable to process it!  Device ID: {171FCCCC-753D-FC45-934B-4842B058F93C}
  1852 -------------------ProcessRules of type 6----------------------
  1852 Getting definition data from core HQ-LANDESKAPP
Thu, 13 Aug 2009 14:01:15 HTTP POST: http://HQ-LANDESKAPP/WSVulnerabilityCore/VulCore.asmx
Thu, 13 Aug 2009 14:01:15 Success
  1852 No scan results to report.  Returning a single blank entry.
  1852 ProcessRules: detected compliance=0
  1852 Sending scan results to core HQ-LANDESKAPP
Thu, 13 Aug 2009 14:01:15 HTTP POST: http://HQ-LANDESKAPP/incomingdata/postcgi.exe?prefix=ldlogon\VulScanResults\&name={171FCCCC-753D-FC45-934B-4842B058F93C}.6.vrz
Thu, 13 Aug 2009 14:01:15 Failed http://HQ-LANDESKAPP/incomingdata/postcgi.exe?prefix=ldlogon\VulScanResults\&name={171FCCCC-753D-FC45-934B-4842B058F93C}.6.vrz on server (0), server status: 404.
Thu, 13 Aug 2009 14:01:15 URL not found.  Giving up.
Thu, 13 Aug 2009 14:01:15 SendRequest: SOAPAction: "http://tempuri.org/PutResultsByFile"


Thu, 13 Aug 2009 14:01:16 Success
  1852 ERROR: The core (HQ-LANDESKAPP) received the vulnerability info but was unable to process it!  Device ID: {171FCCCC-753D-FC45-934B-4842B058F93C}
  1852 Skipping repair step because scan errors occurred.
  1852 Not unregistering script engine.  Other instances are running.
Thu, 13 Aug 2009 14:01:16 Exiting with return code 0x8db30196.


Viewing all articles
Browse latest Browse all 3522

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>