The service LOGINventory9-DataService must be running to ensure that the data generated by the different acquisition methods can be entered correctly in the respective database. This service synchronizes the information of a device with the database and always saves only the changes to the previous scan, which makes very efficient use of the storage space. Normally, the data is entered in exactly one database, the entry behavior of the multi-client capable version with several databases is described below.
There may be only exactly one instance of the service LOGINventory9-DataService per database, which enters the data into the database. This is the only way to ensure that deadlocks do not occur when entering data into the database. A configuration of several parallel complete LOGINventory installations (including Dataservice) is not supported.
Entry Behavior of the Normal End-User Version
In order for the data to be successfully entered into the configured database, the .inv files
resulting from the acquisition must be stored in the data directory. Normally this is done automatically, only when using a USB stick the .inv files have to be copied here manually. The directory location can be adjusted in the settings, by default this is the path
C:\Users\Public\Documents\LOGIN\LOGINventory 9\Data. The service LOGINventory9-DataService also adds an icon in the taskbar to inform about the current status. It can be used to jump to the data directory or, for example, to open the LOGINventory event log.
If a .inv file contains incorrect data, it cannot be entered into the database. Instead a .diag.inv file is created in the "Failed" subdirectory. This is readable and can give hints for troubleshooting. If additional help is needed, this file can also be sent to LOGINventory support for further analysis. In addition, the icon in the taskbar indicates that the entry was incorrect. The incorrect entry can have various reasons, e.g.
- Not enough LOGINventory licenses available
- Invalid commands were added to the LOGINfo.script file
- Newer data already exists in the database (for example, if the service was stopped)
- The database has reached its maximum size (10 GB for SQL Server Express Edition)
In the settings there is also the possibility to specify a folder in which the processed .inv files should be moved. This is intended, for example, if this data is also to be entered into another database (for example, also at the main site of your company).
If the data has been entered successfully, you can start with the Data analysis itself.
Behavior of the Multitenancy Version
If several clients have been created, a separate data directory exists for each client. All .inv files created by the respective recording methods must be written into this directory (e.g.
C:\Users\Public\Documents\LOGIN\LOGINventory9\Customer_A, etc.). The service LOGINventory9-DataService monitors all directories of the different mandates and enters the data into the appropriate database. Otherwise, the behavior is the same as the normal end-user version.