DC Scan failed (and) Problem while discovering workstation trace due to SWUSAGEINFO table. / 'Previous scan time does not match' trace in SDPIntegration trace found in logs
Issue:
Scan failed in UI with errors like 'Credential not configured' / 'The agent is taking longer than usual' / 'Scan has timed out' / 'Agent is not installed' (and) Problem while discovering workstation trace due to SWUSAGEINFO table.
This issue will occur while populating the Operating System Software from scan data while processing the scan data XML.
Trace:
SDP Serverout logs:
[com.manageengine.servicedesk.servlet.ScanDataServlet]|[INFO]|[56]: Delta scan failed to identify sync with previous scan and is rejected for workstation: <wsname>
.
.
.
Problem while discovering the workstation.|
com.adventnet.persistence.DataAccessException: [SWUsageInfo] Batch entry 0 INSERT INTO SWUsageInfo (SOFTWAREINFOID,SOFTWAREUSAGETYPEID,OVERALLRUNCOUNT,OVERALLRUNTIME) VALUES (<softwareinfoid>,3,0,'-') was aborted: ERROR: insert or update on table "swusageinfo" violates foreign key constraint "swusageinfo_fk1"
Detail: Key (softwareinfoid)=(896216) is not present in table "softwareinfo".
(or)
Problem while discovering the workstation.|
com.adventnet.persistence.DataAccessException: [SWUsageInfo] The INSERT statement conflicted with the FOREIGN KEY constraint "SWUsageInfo_FK1". The conflict occurred in database "<dbname>", table "dbo.SoftwareInfo", column 'SOFTWAREINFOID'.
at com.adventnet.persistence.DataAccess.createDataAccessException(DataAccess.java:3689)
at com.adventnet.persistence.DataAccess.insertRows(DataAccess.java:3151)
at com.adventnet.persistence.DataAccess.add(DataAccess.java:349)
at com.adventnet.persistence.DataAccess.add(DataAccess.java:292)
at com.adventnet.persistence.interceptor.CorePersistenceInterceptor.process(CorePersistenceInterceptor.java:53)
at com.adventnet.persistence.interceptor.NotificationPersistenceInterceptor.process(NotificationPersistenceInterceptor.java:224)
at com.manageengine.mdh.QueryInterceptor.process(QueryInterceptor.java:561)
at com.adventnet.authorization.interceptor.AuthorizationInterceptor.process(AuthorizationInterceptor.java:68)
at com.adventnet.persistence.PersistenceBean.process(PersistenceBean.java:633)
at com.adventnet.persistence.PersistenceBean.update(PersistenceBean.java:361)
at sun.reflect.GeneratedMethodAccessor86.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.adventnet.mfw.bean.BeanProxy.lambda$invoke$0(BeanProxy.java:51)
at com.zoho.mickey.api.DefaultCodeBlock.execute(CodeBlock.java:453)
at com.adventnet.mfw.bean.BeanProxy.invoke(BeanProxy.java:48)
at com.sun.proxy.$Proxy2.update(Unknown Source)
at com.adventnet.servicedesk.utils.ResourcesUtil.update(ResourcesUtil.java:604)
at com.adventnet.servicedesk.asset.util.AssetUtil.updateWorkstation(AssetUtil.java:5437)
at com.adventnet.servicedesk.asset.util.AssetUtil.handleScanData(AssetUtil.java:15415)
at com.adventnet.servicedesk.asset.discovery.NodeDiscovery.scanDevice(NodeDiscovery.java:1409)
at com.adventnet.servicedesk.asset.task.DiscoverNode.discover(DiscoverNode.java:213)
at com.manageengine.servicedesk.servlet.ScanDataServlet.populateXMLData(ScanDataServlet.java:509)
at com.manageengine.servicedesk.servlet.ScanDataServlet.scanDataProcess(ScanDataServlet.java:396)
at com.manageengine.servicedesk.servlet.ScanDataServlet.doPost(ScanDataServlet.java:100)
Trace from SdpIntegrationLog from DC logs:
Response form SDP {"response_status":{"messages":[{"statuscode":4011,"message":"Previous scan time does not match in database and delta data received. Please send full scan to make sure no data loss."}],"status":"Failed"}} ###################|Please find the consolidated fjars for the recent issues that we face frequently from build version above AE 7000 and SDP 14300:
SDP | AE | FJAR TO BE USED |
14300-14301 | 7000-7001 | 7000_7001_latest_fix.fjar |
14302 | 7002 | 7002_latest_fix.fjar |
14303 | 7003 | 7003_latest_fix.fjar |
14304 | 7004 | 7004_latest_fix.fjar |
Issues fixed :
-> Scan failure due to USBName is empty string, sent from DC
-> EC Incompatibility header message is shown in banner, eventhough both AE/SDP and EC are compatible.
-> Scan failed due to SWUSAGEINFO trace and SWMETERINGDATA traces
-> Manually created product types not included under schedule scan
-> Schedule scan jobs should not be closed in cleanup schedule.
-> Credentials not configured error while scanning
-> Error while calculating compliance for softwares.
-> OutOfMemory error due to SDPJOBSINFO table entries + Delete queries in the below KB: https://pitstop.manageengine.com/agent/manageengine/servicedesk-plus/knowledge-base/page?articlestatus=published&showAllArticles=true&rootcategoryId=24000242084181&categoryId=24000242084181&status=published#Solutions/dv/24002174069723/en
New to ADSelfService Plus?
Related Articles
Agent scan understanding
Agent scan in ServiceDesk plus happens in two way 1) Server to target machine 2) Agent from Machine to Server MODE 1: 1) Server to target machine -This scan happens when you login to ServiceDesk plus \ Asset explorer from your workstation or ..."General failure while fetching agent configuration" when accessing Agent Configuration page with "NatAddress" not found trace.
Issue: "General failure while fetching agent configuration" error message is showing up when accessing Agent Configuration page under Admin -> Discovery. This happens in two cases. Case 1: Build Version: DC - 11.1.2240.1 and above. Trace: SDP: ...How does Agent Scan work ?
When you install Agent for the first time, It will initiate the scan immediately and send the data via application port (8080 or 443 as you configured) to Server. But when you scan from the Application, It will first try to check whether the client ...Asset Scan Issues
1. Either access denied for the user or the remote DCOM option might be disabled in the workstation. 2. User does not have the access privileges to perform this operation. 3. One of the WMI components is not registered properly. 4. Execution failure ...Problem time spent
SELECT prob.PROBLEMID "Problem ID", prob.TITLE "Title", catadef.CATEGORYNAME "Category", LONGTODATE(prob.REPORTEDTIME) "Reported Date", ownaaa.FIRST_NAME "Technician", priodef.PRIORITYNAME "Priority", statdef.STATUSNAME "Status", ...