Error message on LDAP discovery

[Dan Munns]

Hi all, 

I am getting this error on an adhoc LDAP discovery job:

09:40:40 Process Error: 1 - Unable to load LDAP attribute mappings: D:\dev\build\esp\EspServer\Instance\__TargetFolder\idata\instance_conf_template\conf\LdapAttributesMapping.xml
Process Error: 1 - Unable to load LDAP attribute mappings: D:\dev\build\esp\EspServer\Instance\__TargetFolder\idata\instance_conf_template\conf\LdapAttributesMapping.xml

Looks like a remote server issue rather than anything local. Any ideas/help?

@Gerry I get the feeling you are going to be adding me to your mute list before too long :) 

[Graham]

Dan

Yes, rather embarrassingly, that's a configuration error on our part . However, it is going to require a software update at your end to resolve, and we'll get that to you just as soon as we can.

In the meantime, would running discoveries against a Windows domain via ADSI get you going?

Graham

[Gerry]

@Dan Munns

Lol not at all, bring it on.  That error looks suspiciously like a Hornbill blunder, I think we appear to have left a hard-coded path normally used for developer in the release build :/ I will post internally to see and to get this sorted, we can probably hot-fix this

Gerry

[Dan Munns]

@Graham  @Gerry

Yeah I did an ADSI discovery scan on one OU to add some test machines.

Strangely this found the 9 machines and pinged 7 of them successfully.

Managed to get DNS lookups for 5 and imported them into the Inventory but i can only see 3. Running the scan again show the 2 missing ones as being added again but they still dont show up. 

Also as a QoL change, can we have a view which shows both managed and unmanaged assets in the same list. With a column to show the managed state of the device.

[Steve G]

Hi @Dan Munns,

I think your missing inventory items may be due to WinRM and missing mandatory data not being returned during the discovery. Could you try the ADSI discovery again please, but select DCOM as the protocol instead of auto and let us know if it adds your missing items?

Cheers,

Steve

[Dan Munns]

@Steve G setting forced DCOM has added one of the missing machines.

I will have to look a little deeper into the missing machine. I can ping it from the server, can get WMI info via Powershell and it has a complete DNS record.

Probably something on our end.

[AndyHill]

So I am having problems with ldap discovery due to the OU structure at my company. 

If i run a discovery on the following location it works: Princes.co.uk/CI Project/Desktops

However, if i run the discovery on a location with additional spaces in the name such as: Princes.co.uk/CI Project/Desktops Windows 7 it fails with The supplied username  BLAH could not be validated against the Windows 7 domain. The user name or password is incorrect.

For whatever reason it seems unable to interpret the second space however it has no issue with the first space. Tried surrounding it in different quotes but with no luck. Any ideas?

[Graham]

@AndyHill 

Andy,
Thanks for bringing this to our attention. It's not an issue we're aware of, but we are investigating it now, and I'll post back when we have some more information for you.

Graham

[Graham]

@AndyHill

Andy,

We've now identified the problem, and the fix is undergoing internal testing. I would expect this to be included in the next release.

Graham

[AndyHill]

@Graham Thanks. Looking forward to it. 

[AndyHill]

Did the issue with the additional spaces in the path ever get rolled in to a new revision or is it still being looked into?

[AndyHill]

@Graham Hey Graham, hope you are keeping well. Is there any update on updating the release to fix the extra spaces in the OU path?

[Graham]

@AndyHill Andrew, I've just run a quick test here to be sure and yes, that has now been fixed.If it still doesn't work, then there's something else weird going on!