I was able to figure this out on my own after some trial and error:
- I put together a query based upon configuration management.configuration item and included the title, LDMS ID, and the last updated attributes.
- Once I had these results, I exported to excel to have better sorting capabilities.
- After I sorted by last updated and ID, I found the last entry added in along with its LDMS ID (in my case it was 3612).
- Given this information, I searched for the next LDMS ID (3613) in line.
After excluding the specific computer with this ID in the system filter being used for the import, I had more results listed in the log, but still got the same error. After doing this process a second time and excluding a second computer, the import completed without error.
Other things to mention: I found the same occurring with our import for User CI's. I excluded the same two computers in the system filter for it, and this started working as well. I couldn't find any commonality between the two guilty computers. I will say that one of them was a dell computer, and we are primarily an HP shop.
Hope this helps someone else!