This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject

The Community is now in read-only mode to prepare for the launch of the new Flexera Community. During this time, you will be unable to register, log in, or access customer resources. Click here for more information.

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Spider 6.2: Problems with Employee synchronization

Summary

This article provides a resolution if the XObjectHistory table in the Spider Core database gets filled with data.

Symptoms

The XObjectHistory table in the Spider Core database gets filled with lots of data

 

 

Cause

The EmployeeParameterMapping for any key has been filled with FullName. This is not allowed since FullName is a calculated field and the Core service will evaluate it as different and create a history entry.

 

 

Resolution

Remove the Value FullName from the EmployeeParameterMapping in Spider Admin Tool:

 

  1. Open Spider Admin Tool
  2. Open Spider Core > Config
  3. Navigate to SoftwareRecognition> EmployeeParameterMapping
  4. Remove the FullName value from the list

 

Additional Information

Spider 6.2.15115.162 

on ‎Sep 21, 2018 07:48 PM - edited on ‎Aug 27, 2019 05:22 AM by Moderator Moderator

Labels:
No ratings
0 Kudos
Version history
Last update:
‎Aug 27, 2019 05:22 AM
Updated by:
Moderator Moderator