Giuseppe Iannacone Posted April 19, 2019 Share Posted April 19, 2019 I have a couple of data import task freezed, how can i stop them from running? Link to comment Share on other sites More sharing options...
Victor Posted April 22, 2019 Share Posted April 22, 2019 The info you see there is not always entirely accurate. Well it is but in reality it isn’t... I’ll try and explain. When an import starts running, the LDAP import tool will inform Hornbill that the import started. This will change that Status to Started. Then the import does its bit, finishes at which point it will again inform Hornbill that the import is complete. Again, this will change that Status to Complete. What happened here is that the LDAP import tool never communicated back about the import being complete, for whatever reason. So as far as Hornbill is concerned the import still runs but it might very well be the case that it actually does not (on the machine where the tool runs). If you are certain there is no import running, the tool does not run on your machine, then you can “force” a fresh import by running it with the “force flag” parameter turned on. This will run a new import and will clear previous statuses. Link to comment Share on other sites More sharing options...
Giuseppe Iannacone Posted April 22, 2019 Author Share Posted April 22, 2019 @Victor thank you for explaining, so I was thinking the issue we are experiencing was due to this pending status... but it's not. so why we often receive this error (account loaded 0/XXXX): sometimes when retrying it works, sometimes not... I would like to be sure it is working Link to comment Share on other sites More sharing options...
Victor Posted April 24, 2019 Share Posted April 24, 2019 The message says to check the log file so.... have you checked the log file? Is any more information in there? Link to comment Share on other sites More sharing options...
Giuseppe Iannacone Posted May 2, 2019 Author Share Posted May 2, 2019 @Victor sorry for the late reply, i was out of office... yes the log has nothing relevant on it Link to comment Share on other sites More sharing options...
Victor Posted May 2, 2019 Share Posted May 2, 2019 @Giuseppe Iannacone change the log level to "Error", run the import again then we can have a look at the error recorded in the import logs... Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now