Processing

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.

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.

!!! info The service also processes csv files if a corresponding mapping was previously defined in the data import dialog.
The service recognizes which mapping is to be used based on the name of the file and the name pattern defined in the data import (if several have been defined).

Status of the Service

The service LOGINventory9-DataService adds an icon in the taskbar to inform about the current status. It can be used to jump to the data directory via right click (Show -> New Inventory Files*) or, for example, to open the LOGINventory Event Viewer.

The icon shows the current status using different overlays.

No overlay: Service is running and waiting for inv files.

If the service is running and there are currently no inv files or csv files in the data directory, there is nothing to process - the service is waiting for files.

Blue overlay: Data is being processed.

The data directory contains inv or csv files that are currently being processed.

Red overlay: Service is stopped.

Try to start the service via the task manager, for example. If this fails, the database can probably not be accessed. A corresponding message is then visible in the event viewer. If you use Windows authentication rather than SQL authentication in the database configuration, you must ensure that the services can access the database, e.g. by running the service under a different account.

Exclamation mark overlay: Errors have occurred while processing the data.

If an .inv file contains incorrect data, it cannot be entered into the database. Instead, a .diag.inv file is created in the “Failed” subdirectory. The reason why the file could not be entered is logged in the event viewer under the “Error” level, source “LOGINsertSvc”. If additional help is required, this file can also be sent to LOGINventory support for further analysis. The failed entry can have various reasons, e.g.

-the fingerprint procedure could not identify the exact device to be updated - the inv file was created with an older version (e.g. Offline Agent not updated), whereby the data model does not match the existing LOGINventory database - 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) - the database was temporarily unavailable (at the time of the entry attempt) - etc.

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.