Mark (ESC) Posted September 20, 2021 Share Posted September 20, 2021 Have noticed that our LDAP User Import which creates new Hornbill User Accounts and update existing ones has decided to stop on the 9th September. What basic steps do I need to follow to resolve this issue. Thanks as always. All sensitive data has been blanked out with the awful snipping tool chisel pen Link to comment Share on other sites More sharing options...
Victor Posted September 20, 2021 Share Posted September 20, 2021 @Mark (ESC) check the machine that you use to run that import. Perhaps a scheduled task that completed (e.g. was only set to run until 9th)? Given there is no record that the import was even attempted after 9th suggests that the machine responsible for running the import tool, for that specific config, never did... Link to comment Share on other sites More sharing options...
Mark (ESC) Posted September 20, 2021 Author Share Posted September 20, 2021 @Victor Thank you for your reply. Just taken a look at the history, something I should have looked at initially. Actually looks as though the LDAP User Import is still running from the 9th September at 20:00, as it is not showing a completed time. Link to comment Share on other sites More sharing options...
Victor Posted September 20, 2021 Share Posted September 20, 2021 1 minute ago, Mark (ESC) said: Actually looks as though the LDAP User Import is still running from the 9th September at 20:00, as it is not showing a completed time I would be surprised if is still running ... What I think it happened (most likely) is that the import started on the 9th at 8 PM the it ended (most likely ungracefully) but Hornbill never received a notification that it was completed (with success or failure/error). So that is what Hornbill admin tool is showing. I would say to check the machine that runs the import and see if there is still an active process for this or what is the status with the import tool there... 1 Link to comment Share on other sites More sharing options...
SamS Posted September 20, 2021 Share Posted September 20, 2021 Hi @Mark (ESC), You should be able to run the script with the -forcerun parameter - that should close off the old log. Another issue might be that the API key has expired, you might want to double-check that - as well as perhaps the local log file. 1 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