Scan Data does not reach AssetExplorer/ServicedeskPlus from UEM Product even after successful integration on both sides

Scan Data does not reach AssetExplorer/ServicedeskPlus from UEM Product even after successful integration on both sides

Case 1:  This case applies for AE and SDP :
Following exception trace can be seen in sdpintegrationlog of UEM product
[15:33:20:130]|[02-09-2023]|[SDPIntegrationLog]|[SEVERE]|[371]|[eca222d0-d0c9-41ee-bb46-edbee85ad6ca]: Error while posting data| 
java.io.IOException: Server returned HTTP response code: 403 for URL:/discoveryServlet/ScanDataServlet?machineId=24499&HANDSHAKE_KEY=APIKEY&agent=desktopcentral
at com.adventnet.sym.server.inventory.standalone.SDPInvDataPostImpl.postDataToSDP(SDPInvDataPostImpl.java:94)
at com.adventnet.sym.server.inventory.SDPInvDataPost.postDataToSDP(SDPInvDataPost.java:193)
at com.adventnet.sym.server.inventory.SDPInvDataPost.postXMLContent(SDPInvDataPost.java:120)
at com.adventnet.sym.server.inventory.SDPInvDataProcessor.desktopDataPost(SDPInvDataProcessor.java:281)
at com.adventnet.sym.server.inventory.SDPInvDataProcessor.processData(SDPInvDataProcessor.java:75)
at com.me.devicemanagement
[15:33:34:089]|[02-09-2023]|[SDPIntegrationLog]|[INFO]|[331]|[05e14b60-d6f9-45d2-9345-f799f744edc8]: Exception while getting sdp build no| 
java.lang.NumberFormatException: For input string: ""
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Long.parseLong(Long.java:601)
at java.lang.Long.parseLong(Long.java:631)

Solution : 
Please ask the cx to upgrade the DC to build versions above 11.2.2315.1 in all NLs (Possibly ask them to upgrade DC to latest version based on compatibility from below sheet)
If the cx is in the EC versions greater than the above versions but still they are facing this issue, then please get the information from cx whether the cx previously integrated EC with any other AE already (or) whether the EC is bundled with AE and then integrates with SDP now. We had a similar issue in this ticket #9172893.
Please get the above information from the cx as well, and revert to us.

Case 2: 
This means the integration key used in UEM product UI, sdp server settings This means the integration key used in UEM product UI, sdp server settings This means the integration key used in UEM product UI, sdp server settings The following exception trace can be seen UEM product's SDPIntegrationlog
Error while posting data| 
java.io.IOException: Server returned HTTP response code: 403 for URL:/api/v3/ScanDataServlet?machineId=24499&HANDSHAKE_KEY=APIKEY&agent=desktopcentral
This means the integration key used in UEM product UI, sdp server settings belongs to a user without scan now and inventory permissions.
The following exception trace can be seen UEM product's SDPIntegrationlog
Error while posting data| 
java.io.IOException: Server returned HTTP response code: 401 for URL:/api/v3/ScanDataServlet?machineId=24499&HANDSHAKE_KEY=APIKEY&agent=desktopcentral
This means the integration key used in UEM product UI, sdp server settings is incorrect.
Solution:
Please ask the cx to use the following steps for integration:
1. In SDP/AEo to Admin > Developer Space > Integration key and create an integration key with SDAdmin role. 
2. In the UEM product, go to Servicedeskplus settings, edit and add the api key generated in step 1 to the api key field and click save.
3. In SDP/AE -->go to UEM Products and re-integrate on Servicedeskplus by giving server credentials
4. Try scan again.
In this method you can always go back to the Integration key page, view and verify the key api key and make sure it is tied to the right role.

Case 3:
Following exception trace can be seen in sdpintegrationlog of UEM product
[15:33:20:130]|[02-09-2023]|[SDPIntegrationLog]|[SEVERE]|[371]|[eca222d0-d0c9-41ee-bb46-edbee85ad6ca]: Error while posting data| 
java.io.IOException: Server returned HTTP response code: 403 for URL:/discoveryServlet/ScanDataServlet?machineId=24499&HANDSHAKE_KEY=APIKEY&agent=desktopcentral
at com.adventnet.sym.server.inventory.standalone.SDPInvDataPostImpl.postDataToSDP(SDPInvDataPostImpl.java:94)
at com.adventnet.sym.server.inventory.SDPInvDataPost.postDataToSDP(SDPInvDataPost.java:193)
at com.adventnet.sym.server.inventory.SDPInvDataPost.postXMLContent(SDPInvDataPost.java:120)
at com.adventnet.sym.server.inventory.SDPInvDataProcessor.desktopDataPost(SDPInvDataProcessor.java:281)
at com.adventnet.sym.server.inventory.SDPInvDataProcessor.processData(SDPInvDataProcessor.java:75)
at com.me.devicemanagement
[15:33:34:089]|[02-09-2023]|[SDPIntegrationLog]|[INFO]|[331]|[05e14b60-d6f9-45d2-9345-f799f744edc8]: Exception while getting sdp build no| 
java.lang.NumberFormatException: For input string: ""
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Long.parseLong(Long.java:601)
at java.lang.Long.parseLong(Long.java:631)

This exception trace is same as case 1,but this case can be seen in SDP builds also. This could be because UEM is unable to get the build number from SDP/AE with the url /api/v3/app_resources/build_info because the throttle limit must have exceeded. , you will see a throttle exception for /api/v3/app_resources/build_info in securitylog for assetexplorer and serverout log for SDP.
Solution : Go to <SDP/AE_installation directory>/webapps/ROOT/WE_INF/security/security-authentication.xml, in this line  <throttle duration="1m" threshold="100" lock-period="1m"/> increase the threshold, restart AE/SDP service and reintegrate on UEM product side



      New to M365 Manager Plus?
      New to M365 Manager Plus?
        New to RecoveryManager Plus?
        New to RecoveryManager Plus?
          New to Exchange Reporter Plus?
          New to Exchange Reporter Plus?
            New to SharePoint Manager Plus?
            New to SharePoint Manager Plus?
                See all integrations
                New to ADManager Plus?
                See all integrations
                New to ADManager Plus?

                  New to ADSelfService Plus?

                  Start your free trial
                  Start your free trial

                    • Related Articles

                    • Inventory method when another UEM product exists

                      When the user is using another ManageEngine Product that belongs to the UEM Family, they would have already deployed the UEM Agent, that we had now bundled with ServiceDesk Plus. With that being said, this KB deals with 3 cases - 1. The customer ...

                    • SDP Scan offerings a glance

                      There are several use cases to be addressed to scan user machines. Here are the solutions available with SDP now. - User machine rarely reaches the organization domain / Network (user login once a week using VPN and other times using local ...

                    • 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 ...

                    • 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 ...

                      Related Products