Basic Troubleshooting Guide - Data Translation Services - Real Time Processing

Version 5

    Verified Product Versions

    Endpoint Manager 9.6Endpoint Manager 2016.xEndpoint Manager 2018.x

    This article covers what's most commonly occurs when there are issues with Real Time Processing and how to narrow down specific issues that may occur.

        A DTS Rule works when ran manually but does not work when inventory scans come in.

    Solutions to this problem will vary dramatically depending on what kind of rule you are working with. (ie. B2B connector, LDAP Import, Import Data, Map Data, etc... )

    Here's a quick check list of what that could be:

    1. Is the Real Time Processing Button red or green? (ie. It should look like this: ss+(2015-01-05+at+12.19.33).png)
      • If the button is red then you should be able to simply click the button and it should turn green.
        • Once clicked it will change your Inventory Advanced setting called Intermediate File Extension from "SCN" to "MP".
    2. Is the rule active?
      • If the rule is not active then you should be able to simply right click on your rule and select Set Active.
    3. Is the Login Credentials used correct?
      • There are multiple locations in which you can store a username and password in rules you configure in DA. If you right click on the rule and edit it you can click through the wizard and change your credentials there.
      • Rules that need to execute additional processes on your core (which is most of the rules available in DA) will need to have a service account configured for the Managed Planet Core Scan Processor service.
        • To configure this you can open services by right clicking on the Managed Planet Core Scan Processor service in the Services window, selecting Log On, and changing the Log on as setting to your service account of choice. You may already have a service account configured for your LANDESK Global Scheduler service which also requires domain admin privileges, so it will likely be easier to just us that account.
    4. Is the rule doing what you're expecting? (ie. The rule was configured to send data to one location in inventory, but an unfortunate typo causes it to actually go somewhere else.)
      • Make sure to test running the rule manually and ensure that it works as expected.
    5. Is the rule configured with a Target? If so, is the target correct?
      • You can right click on any of your rules and select Set Target to configure this setting.
        • If you are using a query to resolve specific machine types, then you may want to confirm that your query is showing the machine's you're expecting when ran before using it in a rule.

        MPCore.exe is taking all of my available CPU and RAM.

    This is most often caused by a issue with one of the rules and how it's configured. If you don't know what rule is causing this then here are a few things you can do to address it:

      1. Inactivate all of your currently Active rules.
      2. Click the Real Time Processing Button to disable the service.(ss+(2015-01-05+at+02.11.41).pngDisabled)
      3. Click again to re-enable Real Time Processing.(ss+(2015-01-05+at+12.19.33).pngEnabled)

    Once these steps are complete, you can start to re-enable rules one by one, until you find one that seems to cause your resources to start spiking again. Please allow some time for those rules to run and keep an eye on your resources so you can have a better idea of which rule is causing the issue. You may have to repeat this process multiple times to narrow down which rules are causing you the most trouble. At this point you may want to review these rules and ensure that they are configured correctly as is possible that a rule may be running infinitely as a result of your rule's configuration.


        Here are a couple quick intermediate troubleshooting tips you can use for confirming if Real Time Processing is running:

      1. Enable Core Scan Debugging and Data Analytics Logging
        • Check a "processed" inventory scan.
          • Disable Do DB in your advanced inventory settings. This will cause the scans to be ran by DA but not be inserted into the database, as a result you should see .SCN files in your ldscan folder you can review. (Note: Generally the lines that DA adds are at the very end of the file.)