There are various types of B2B connectors in Data Analytics and they implement different technology depending on the use case. This document will attempt to give you some basic troubleshooting techniques for each type of connector and also supply other documentation to review for deeper information on a particular topic, if necessary. If you're wondering about what type of connector we're troubleshooting, there are specific behaviors that you can look out for to figure out which type of b2b connector you're troubleshooting.
We have 3 types of B2B connectors:
- Universal B2B
- Web API
- Web Scraping
There are several connectors that use web scraping to gather data from vendors and import it into your Inventory. If you've already set up some of these and are wondering where you can find the data in inventory you can use the B2B column set that is in your list of public column sets (Administration > Column Sets > All Column Sets). This will show you a list of the most common columns used for B2B connectors and is an easy way to see if you have data imported for your devices.
Several Web services online now offer two-factor authentication. Please be aware that if you have two-factor authentication enabled that these web scraping technologies will not be able to log into the respective websites until one of the following happens:
- Disable Two-Factor on the specific website that's being scrapped.
- Use the Debugging window to log into the site manually and set it to remember the device.
Troubleshooting WebPull Connectors
Troubleshooting Web Scraping (aka. WebPull) Connectors generally takes the following steps to import your information into LDMS:
- Successfully log in to the website
- Use ALT-Tab (or use Task Manager and right-click and select bring to front) to find a hidden window called WebPull. Once open you can watch the process happen and even click in the window if you wish.
- Download a report from the respective website and store it in the MP_Temp directory under the appropriately labeled folder (Adobe, CDW, etc.)
- Use one of the predefined import data rules to import data into the appropriate inventory locations in your LDMS database.
During this time, when the rule is running it will save log information in the MP_Log folder. Usually, if you run these rules by hand it will have a log with the appropriate name based on the name of the rule you created. However, when scheduling these things the log is written to a generic file name like "MPRunSched_DATE.log". So with this in mind, it's generally best to run these rules by hand when troubleshooting the issue, by right-clicking on the rule name and selecting "Run Now".
Also, if you have a report that matches the format expected for rule your troubleshooting you can always place a copy of the report (usually a CSV or XLSX file) in the MP_Temp folder for the rule you're working with. Then all you'd need to do is run the rule and kill the ManagedPlanet WebPull process from task manager and it should attempt to import the file for you. However, you'd only do this if the website we were attempting to gather data wasn't working as expected.
Troubleshooting WebMacro Connectors
There is a subset of connectors that have been moved to a new Web Scraping technology that LANDESK has been implementing. This currently includes connectors like Microsoft VL, Insight, and there will be more in the future. Any B2B connector that uses the new WebMacro Technology, unfortunately, does not have a hidden window to troubleshoot with as they did in the past. Currently, the only way to invoke this is to do so by hand. Here are instructions on how to do that. Note that this will likely change in a future update.
- Right click on your respective rule and select "Run Now"
- DO NOT CLICK START
- Navigate to "InstallPath:\LANDESK\ManagementSuite\WEBPULL"
- Rename the file LANDESK.DataAnalytics.DTS.WebMacro.exe to LANDESK.DataAnalytics.DTS.WebMacro.bak
- Now click Start in the rule's popup window.
- Now you should see the rule fail or disappear. This is expected.
- Now you should have a new file under "InstallPath:\LANDESK\ManagementSuite\MP_Temp\MicrosoftVL\" (or whatever connector you're using) and the file should be named arandomnumber.web
- With the new file you've now generated you'll need to use it as an argument in a command prompt with the following syntax: LANDESK.DataAnalytics.DTS.WebMacro.exe "filename.web" /NO
- When the UI pop's up, press play.
Update: This can now be done with just adding a registry key!
- Add the following registry key:
- HKEY_LOCAL_MACHINE\SOFTWARE\Managed Planet\Data Translation Services
- Add a DWORD value to the new key you created called WebDebug. Setting the value to 1 = Debug, 0 = No Debug.
- Run rule and you'll be greeted with the WebMacro window with a button that says "Play". Click play, to watch DTS attempt to navigate to the website, and gather data.
Additionally, there are issues where you may not be able to log in to certain websites without taking additional steps. Unfortunately, the scripting does not detect if it was able to log in successfully, but you can verify this by using the debugging window mentioned in this document. As usual, you'll want to double check your log in details you've provided as well as if you have Two-Factor Authentication or not.
There are several Web API rules that are in place, these generally don't take a whole lot of manual troubleshooting as a result. First, you'll want to make sure that you use the previously mentioned B2B column set to ensure that data is being imported for your devices. If not, you can run the rule manually and inspect the log located in your MP_Log and MP_Temp folder. Usually, if you run these rules by hand it will have a log with the appropriate name based on the name of the rule you created. However, when scheduling these things the log is written to a generic file name like "MPRunSched_DATE.log". So with this in mind, it's generally best to run these rules by hand when troubleshooting the issue, by right-clicking on the rule name and selecting "Run Now".
In your log, we will generally leave the type of error occurred during the process. Most commonly you may see something like a 401 error, or something like that, in your log. These are usually responses received from the vendor's public API that was used. Sometimes you may run into situations where you are getting 401 messages stating that you've been prohibited access from their server. When you run into this error there are a number of possibilities as to why you would have gotten that error at that time here's a quick list of a few:
- There are too many requests to the site
- Your credentials are incorrect
- The endpoint could be down for maintenance
If you run into this error continuously even after trying at different at different times of day over a 24-48 hour period please contact support for further assistance.
The Universal B2B connector uses the same UI as the Import Data data rule and there is some documentation on that. I'd recommend reviewing the following documentation to get assistance with setting up one of these rules: