Application inventory not working

durrante asked a question.

February 25, 2019 at 8:00 AM

hi guys,

We're running version 8.3 revision 07 build 6968, I'm having issues with application inventory on new devices, essentially the snow agent is regularly checking in and inventorying all sections except for applications, here's an example, all tabs are present with data except applications: any ideas? All agents are running the same version.

Portal User
7 years ago
Hi Alex, my mistake, I just assumed you ran Inventory agent version 5.x, not 3. The config is very different between those versions, that is why you could not find the segment i mentioned. I cannot see anything strange with neither the configuration nor the log. The log does not contain any scan events, so it's still hard to tell what happens. Do you have a lot of *.INV files in the subfolder DATA? you can trigger a manual scan and send by opening a command prompt, go to c:\program files\inventoryclient\ and type client64.exe -scan When that is complete, a INV file will be created in the data subfolder and directly sent to the inventory server. After that you should see an updated record in Inventory server. (Takes another day for changes to show in SLM though.) Are you running inventory server 3 or 5? Do you have an IDR / IDP installation, or just the inventory server?
Expand Post
- durrante
  7 years ago
  Hi Martin, No worries, I'm not familiar with SNOW at all so been dropped in the deep end to hopefully get this working. I haven't got any .inv files in the data location that you mentioned but I do have snow-met files: I will try using the command you mentioned and go from there. In terms of the inventory record on the server, where would this be? Anyway I can check the inventory server to see if the client is uploading data? Not sure on the products but I can see these in the add\remove programs on the snow server, hopefully this answers your question:
  Expand Post
  - Portal User
    7 years ago
    Perfect Alex, that gives us plenty to work with. So you are running Inventory 3 agents with Inventory 3 server, in combination with IDR (Inventory data reciever) and IDP (Inventory data processor.) The MET files are nothing to worry about, they will come and go and is just a temp storage for usage data. The timestamp on those tells me that the inventory agent is alive and kicking, so that is good. The fact that you do not have INV files here is most likely good. It means that either the client was able to send the scan result to the server ( good) or that the client was unable to perofrm a scan at all (bad). I think a look at the IDP (iniventory data processor) logs would be a good next step. The IDP is processing all files (*.INV) from your inventory clients, and if something goes wrong there it will write that to the processing log.   You will find it here: c:\ program files\Snow Software\Inventory Data Processor Any errors in that one? Also, on the inventory server, can you access the program called Snow Inventory and the view "Inventory Overview" ?
    Expand Post
    durrante
    7 years ago
    Hi Martin, Looking at the log now, there is a lot of warnings regarding duplicate inventory files and a couple of errors. I've uploaded the log to my OneDrive if you wish to take a look: https://hybritservices-my.sharepoint.com/:f:/g/personal/alex_durrant_hybrit_co_uk/Eomfo-50rPNFvzCe69BuycIB7qwI5QEuspVPnd… I can't see an entry for the device I've been using as a test though (HS001LAP60190) this device had the agent reinstalled this morning. Also, I noticed in the config.ini file, does this mean that all clients won't upload their data to the snow server until 15:00 every day? UpdateDayOfMonth=1 UpdateDayOfWeek=1 UpdateDelay=1 UpdateRandomize=no UpdateSchedule=DAILY UpdateServer= UpdateStartTime=15:00 If that's the case, surely we would see some INV files as you mentioned? Cheers EDIT - sorry Martin didn't see your comment regarding the Snow inventory, strange one, I have it in my start menu, nothing happens when I select it, the target is pointing to: "D:\Program Files (x86)\Snow Software\Snow Inventory\UNWISE.EXE" /W1 "D:\Program Files (x86)\Snow Software\Snow Inventory\INSTALL.LOG" Does that sound right to you? EDIT2 - Martin, I have just ran client.exe -scan manually on the test device and I've uploaded the logs to the same onedrive location as above, folder is called 'AfterClient.exe-scan'
    Expand Post
    Portal User
    7 years ago
    Hi Alex,   I think the logs generally looks ok, there is a few files that cannot be processed becasue of bad characters in the scan result, but they do not explain the behaviour you experience. The agent scan log you attached is also fine, the scanner is traversing your file system, creates a INV file and sends it without issues. The path to the inventory admin console should be ( C:\ program files(x86)\ Snow Software \Snow Inventory \Admin \Admin.exe by the way, or possibly D:. Are you able to start this program, and log in when asked for credentials?
    Expand Post
    durrante
    7 years ago
    Hi Martin, Yes, I'm in and looks like the data is there for the test client I've been using: However from the web portal, still nothing: At least the data is there! Any ideas?
    Expand Post
    Portal User
    7 years ago
    Ah, data IS in the inventory server then! Following the dataflow forward would mean checking the Data Update Job, which transfers the data from Inventory DB to License Manager DB. Do you have access to the SQL server? Can you run a couple of queries against the License Manager Database?   Use SnowLicenseManager Select * from tblerrorlog Select * from tbl joblog By the way, I recommend that you file a ticket with the Snow Support team if you haven't already done that. If the tblErrorLog reports recent problems with the job you might need to clean out some bad data from the DB in a screen sharing session with the Snow Support.
    Expand Post
    durrante
    7 years ago
    Hi Martin, I've uploaded an excel spreadsheet with the results of your queries, separated by sheets to the same location as yesterday. There's quite a few entries in the tblerrorlog! Yes I have logged a ticket, ID: CS0029536 Thanks for your help with this so far!
    Expand Post
    Portal User
    7 years ago
    Hi Alex, I had a look at the logs, and there is something there that I think might cause this. The most recent errors you have in the tblErrorLog "Adding a value to a 'datetime' column caused an overflow", which you have had for a while might cause the job to stop prematurely. This error message is connected to user updates, and right after that comes the computer software update steps, and I can't see that these has been running. The error is caused by some incorrect dates in the user tables in SNOWDB which needs to be fixed. I suggest you ask support to help you adjust this, and then run the Data Update Job again to see if it completes this time. (Send them the excel you gave me, that will help them find the culprit.) I will also put an internal note on the case to help them find similar cases and internal KB:s. I think this will solve the issue, at least this error is something you want to get rid of as it will lead to other problems with user updates too. :-)
    Expand Post
    durrante
    7 years ago
    Hi Martin, Thanks for this, I've also noticed the issue with the primary filegroup lack of disk space so I've sorted that out this morning. I have asked support to take a look into this for me. Thanks for your help on this. Regards, Alex.
    Expand Post

10 of 17