Keith Stevenson Posted January 19, 2022 Share Posted January 19, 2022 From the 1st March 2022 , only the data import tool with version 3.12.0 will be supported. To prevent older versions we will change the Name of Any LDAP import using older versions on the 1st March, preventing your onsite Import From running (Unless you are running the 3.12.0 or above). To prevent this you should update to the latest version https://wiki.hornbill.com/index.php?title=LDAP_User_ImportHaving reviewed existing versions our customers are using this should be a drop in EXE change, however we strongly recommend you read the release notes for the versions between yours and 3.12.0 and run the import with the DRYRUN option after replacing the exe to confirm Download the x64 Binary or x86 Binary - https://github.com/hornbill/goLDAPUserImportRename you existing Binary to ldap_user_import.old , drop in the file from above to the folder you would like the application to run from e.g. C:\LDAP_Import\Open Command Line Prompt as AdministratorChange Directory to the folder with ldap_user_import.exe C:\LDAP_Import\Run the command ldap_user_import.exe -dryrun true -instance $INSTANCEID -apikey $APIKEY If you have any queries on this or the update to the latest version please respond below. 1 Link to comment Share on other sites More sharing options...
John C Posted January 19, 2022 Share Posted January 19, 2022 @Keith Stevenson hello... How can we identify that the current version we have installed is? Will July 2021 suffice or how can I tell which version we have? Nothing under the tabs at the top.... Thanks Link to comment Share on other sites More sharing options...
Keith Stevenson Posted January 19, 2022 Author Share Posted January 19, 2022 @John C This will be in the log at the top. Have checked your version and it is ,"=== XMLMC LDAP Import Utility V3.9.5 ===" The below URL should also show previous versionshttps://github.com/hornbill/goLDAPUserImport/tags The date for 3.12.0 is 21st Dec 2021 Kind Regards Keith Stevenson Link to comment Share on other sites More sharing options...
John C Posted January 19, 2022 Share Posted January 19, 2022 @Keith Stevenson that's great, thank you...sorted now, will wait for the scheduled sync to happen tonight and check... Link to comment Share on other sites More sharing options...
Adam Knee Posted January 19, 2022 Share Posted January 19, 2022 I didn't originally setup this system and I cannot find any notes on the LDAP import tool internally. Is there somewhere within the hornbill system config where I can determine the IP of the internal server running this tool? The logs state that we are running XMLMC LDAP Import Utility V3.9.1 so we need to upgrade. Link to comment Share on other sites More sharing options...
Alberto M Posted January 19, 2022 Share Posted January 19, 2022 @Keith Stevenson, we already have the have the 3.12.0 for a few weeks but I'd like to refer - for users to be aware of this - that, after installing it, I had to remove the blank roles in the import definition as they were causing an error when running the imports this version (they were not causing the error in previous versions). 1 Link to comment Share on other sites More sharing options...
Keith Stevenson Posted January 19, 2022 Author Share Posted January 19, 2022 @Adam Knee We only have the IP of the gateway (ie your corporate firewall) . We would not know where you run this from. Your Internal IT team\firewall team should be able to tell you where a request to Hornbill occurs from (especially if its at silly oclock at night\morning) @Alberto M Thanks for the feeback. Hopefully that is of some use to others (Not sure of the issue or how wide spread it was). But seems easy enough fix. Kind Regards Keith Stevenson 1 Link to comment Share on other sites More sharing options...
Adam Knee Posted January 19, 2022 Share Posted January 19, 2022 @Keith Stevenson no worries, I've sussed it out and I've now upgraded the component, the logs are now showing the following: 1 Link to comment Share on other sites More sharing options...
Keith Stevenson Posted January 19, 2022 Author Share Posted January 19, 2022 @Adam KneeOutstanding. Cheers Link to comment Share on other sites More sharing options...
Oscar Stankard Posted January 21, 2022 Share Posted January 21, 2022 Hi there, Have recieved email notification that the old version will stop working soon and am trying to update the executable and run a dry run but the executable does not run on my DC stating it's an invalid win32 application. I can't see details of compatability/dependencies on the Hornbill or GitHub sites so does anyone know what they are? Kind regards, Oscar Link to comment Share on other sites More sharing options...
Keith Stevenson Posted January 21, 2022 Author Share Posted January 21, 2022 Oscar, Thanks for the reply. Can you confirm the version you downloaded (x86?) and the size of exe and zip (in Bytes) Kind Regards Link to comment Share on other sites More sharing options...
Oscar Stankard Posted January 26, 2022 Share Posted January 26, 2022 Hi there, It's 3.12.0 x86 version, 6909KB/3902KB, have had a few tries since and seems to work OK on 2012 but not 2008 so presume that's the answer. Link to comment Share on other sites More sharing options...
Keith Stevenson Posted January 26, 2022 Author Share Posted January 26, 2022 Oscar, 2008 is not a supported Operating System by Microsoft since 2020.. (Even 2012 R2 is only valid for another 16 months). The solution is to move the data import tool to a machine later operating system Kind Regards Link to comment Share on other sites More sharing options...
Brhow Posted February 2, 2022 Share Posted February 2, 2022 Hello, I've downloaded the x64 version of the exe but when i try to extract it is says cannot open file as archive and is 0 bytes, just wondering if someone can check it, thanks Link to comment Share on other sites More sharing options...
Steve Giller Posted February 2, 2022 Share Posted February 2, 2022 @Brhow That indicates that the download was not successful. I've just downloaded to my machine and the archive is intact, so I'd suggest deleting the file with the error and re-downloading it. Link to comment Share on other sites More sharing options...
Brhow Posted February 2, 2022 Share Posted February 2, 2022 thank you Link to comment Share on other sites More sharing options...
Salman Posted February 22, 2022 Share Posted February 22, 2022 Updating the LDAP Import Tool to v3.12.0, I'm getting the below error when running it (I've just marked out the InstanceID and APIKey): 2022/02/22 13:46:45 [MESSAGE] ---- LDAP Import Utility v3.12.0 ---- 2022/02/22 13:46:45 [MESSAGE] Flag - config ldap-import 2022/02/22 13:46:45 [MESSAGE] Flag - logprefix 2022/02/22 13:46:45 [MESSAGE] Flag - dryrun false 2022/02/22 13:46:45 [MESSAGE] Flag - instanceid **************** 2022/02/22 13:46:45 [MESSAGE] Flag - apikey **************** 2022/02/22 13:46:45 [MESSAGE] Flag - apitimeout 60 2022/02/22 13:46:45 [MESSAGE] Flag - workers 1 2022/02/22 13:46:45 [MESSAGE] Flag - forcerun false 2022/02/22 13:47:06 [ERROR] Unable to check utility version against Github repository: Get "https://api.github.com/repos/hornbill/goLDAPUserImport/tags": dial tcp 140.82.121.6:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. 2022/02/22 13:47:06 [MESSAGE] Loading Configuration Data: ldap-import 2022/02/22 13:47:27 Error Loading Zone Info File: Get "https://files.hornbill.com/instances/miltonkeynescouncil/zoneinfo": dial tcp 78.129.173.124:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. 2022/02/22 13:47:48 Error Loading Zone Info File: Get "https://files.hornbill.co/instances/miltonkeynescouncil/zoneinfo": dial tcp 83.126.54.45:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. 2022/02/22 13:47:48 [ERROR] 107: Unable to read your instance information from Hornbill. Check your connectivity to Hornbill and/or command line proxy access: Get "https://files.hornbill.co/instances/miltonkeynescouncil/zoneinfo": dial tcp 83.126.54.45:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. --------------- Replacing back to our previous version 3.9.0 runs the import successfully. Am I missing something? Thanks, Salman Link to comment Share on other sites More sharing options...
Keith Stevenson Posted February 22, 2022 Author Share Posted February 22, 2022 @Salman That looks like your local firewall or network firewall (Guess would be Windows firewall) blocking and you only allowed the OLD exe Kind Regards Link to comment Share on other sites More sharing options...
Salman Posted February 22, 2022 Share Posted February 22, 2022 49 minutes ago, Keith Stevenson said: @Salman That looks like your local firewall or network firewall (Guess would be Windows firewall) blocking and you only allowed the OLD exe Kind Regards Thanks Keith. I could not see anything within Windows Firewall to be blocking. I've also checked with our network team and all the below URLs are whitelisted: https://files.hornbill.com/instances/INSTANCENAME/zoneinfo https://files.hornbill.co/instances/INSTANCENAME/zoneinfo https://eurapi.hornbill.com/INSTANCENAME/xmlmc/ https://api.github.com/repos/hornbill/goLDAPUserImport/tags When I rename v3.9.0 to ldap_user_import.exe and run, it imports fine but when I rename v3.12.0 to ldap_user_import.exe, I get the connection error. Do you know what's changed in v3.12 which will help me look into this further? Many thanks, Salman Link to comment Share on other sites More sharing options...
Keith Stevenson Posted February 22, 2022 Author Share Posted February 22, 2022 @Salman Thanks for the reply. Cant think of anything that would cause that other than firewall\virus scanner or proxy In Windows if you add a program - ie ldap_user_import.exe, it takes a MD5 or similar so that if you overwrite it with a newer version it wont be allowed through. Can you try adding an exception for this specific program. Same for any Virus scanner etc on the machine. Kind Regards Link to comment Share on other sites More sharing options...
Salman Posted February 23, 2022 Share Posted February 23, 2022 17 hours ago, Keith Stevenson said: @Salman Thanks for the reply. Cant think of anything that would cause that other than firewall\virus scanner or proxy In Windows if you add a program - ie ldap_user_import.exe, it takes a MD5 or similar so that if you overwrite it with a newer version it wont be allowed through. Can you try adding an exception for this specific program. Same for any Virus scanner etc on the machine. Kind Regards *** FIXED *** Morning Keith, Thank you for your response. Had a further look this morning and it was the proxy settings that was blocking our connections. I noticed in the change log regarding the change in version 3.9.5:- Rebuilt using latest version of goApiLib, to fix possible issue with connections via a proxy Previously we used to point to the http proxy but needed amending to point to the https proxy. Once I did that and used the LDAP Import tool, the imports ran fine. Thanks again for your advise. Kind regards, Salman 1 Link to comment Share on other sites More sharing options...
Keith Stevenson Posted February 23, 2022 Author Share Posted February 23, 2022 @Salman Excellent news Kind Regards Link to comment Share on other sites More sharing options...
Ketan.lakhani Posted November 11, 2022 Share Posted November 11, 2022 Have downloaded Version 3.13 today but the Error started appearing. [ERROR] Bind Error: LDAP Result Code 49 "Invalid Credentials": 80090308: LdapErr: DSID-0C090447, comment: AcceptSecurityContext error, data 532, v3839 Has anyone seen this error? Link to comment Share on other sites More sharing options...
Steve Giller Posted November 11, 2022 Share Posted November 11, 2022 From the LDAP wiki I see: So the error may be coincidental and the credentials you are using to connect to LDAP may need updating. Link to comment Share on other sites More sharing options...
Ketan.lakhani Posted November 11, 2022 Share Posted November 11, 2022 The password has checked and its not expired. 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