Loading
Is it possible to force a data update job?
It appears that while our devices are scanning, not all are reporting back into #SLM. For example, 40% of our active devices that are scanned daily are now showing with a last scanned date as November 26th. I have confirmed that these devices are active and appear to be scanning based on the log files. But the agent log file for one of the devices states: 2018-11-29T08:29:54-5:00; Verbose; snowagent; client\endpointhandler.cpp; Client::EndPointHandler::TrySendToKnownEndPoints; Endpoint is unreachable   2018-11-29T08:29:54-5:00; ERROR; snowagent; client\messageloop.cpp; Client::MessageLoop::Handshake; Handshake failed. Cannot connect to server. No endpoint can establish a connection to the server. So I restarted both our Inventory server and Snow License Manager server to see if this helps. Do I have to wait until our daily update job or can I force one to see the results in SLM quicker?  

  • Detlev Eufinger (Flexera Software)

    Hi Laura, yes you can trigger the dataupdate Job outsite your normal schedule. Go to your Snow Server via RDP and open the Snow Management Configuration Center Tool (SMACC) Sign In with your credentials and got to DataUpdateJob Here you can start the Job manually. BTW: You can test if your Endpoint is available Open a browser and try to reach your endpoint, e.g. http://endpoint.dom.net:80 from your Agent Computers The following page is displayed.
    Expand Post
    • Thank you! I was able to successfully start the job based on your reply. Unfortunately I am still seeing the same results. I am also still able to reach the endpoint as you mentioned. Not sure what the problem could be so I'll need to reach out to support.
      • Hi Laura, I'm not yet an expert and I don't have all information, but... I got a similar problem. In our case, these are the things which happened: on http we could reach the endpoint (inventory server) without any problem. But the connection was set up to work via https. So the connection failed because the FW rules were not yet adapted to make an https connection. In another case, the local certificate to allow the https connection from a system was saved in the wrong location, so the agent was not able to get it. Maybe in your case the certificate is expired? Hope this helps. Anyway, if you find a solution, please drop here the answer so that we can learn from each other. Kind regards!
        Expand Post

Related  Product Forums


                     → Flexera One



                      → Snow Atlas



                      → FlexNet Manager



                      → Snow License Manager



                       → App Broker


       Need help finding an answer?


        Ask a Question →


Loading
Is it possible to force a data update job?