Database Asset Import error - invalid request path

[samwoo]

Hello,

We are looking to import into Hornbill from SCCM.
https://github.com/hornbill/goDBAssetImport

@Aaron Summers and I have managed to connect to our SCCM database no problem using the Database Asset Import, and whilst is working for the most part (via a dry run) it is throwing an error related to the user name API call.

PROBLEM 1
[ERROR] Unable to Search for Customer [######]: Post https://eurapi.hornbill.com//xmlmc//apps/com.hornbill.servicemanager/?method=shrGetCustomerDetails: invalid request :path "//xmlmc//apps/com.hornbill.servicemanager/?method=shrGetCustomerDetails"

Looking up the username (which i've replaced with the hashes) - they are clearly set up in Hornbill when looking in the Admin Tool.
 

PROBLEM 2
Also this might just be a misunderstanding but why does it say "Create Asset" in the log file, when the asset already exists in Hornbill with that name? For example:

2018/08/10 11:01:46 [DEBUG] API Call XML: <params><application>com.hornbill.servicemanager</application><entity>Asset</entity><searchFilter><h_name>###-VSINTRANET</h_name></searchFilter><maxResults>1</maxResults></params>
2018/08/10 11:01:46 [DEBUG] Create Asset: ###-VSINTRANET
2018/08/10 11:01:46 [DEBUG] Asset Create XML # XML DELETED BY MYSELF #
2018/08/10 11:01:46 [ERROR] API Call failed when searching instance for existing Asset:Post https://eurapi.hornbill.com//xmlmc//data/?method=entityBrowseRecords: invalid request :path "//xmlmc//data/?method=entityBrowseRecords"

Thanks,

Samuel

[samwoo]

Just at a glance, it looks like these are old API calls (entityBrowseRecords should be entityBrowseRecords2 for example)

[Victor]

@samwoo or @Aaron Summers if you still encounter this error, please raise a support request so we can investigate

[Hornbill Staff DR]

@samwoo I think I may be able to offer some advice in relation to the errors you posted above:

https://eurapi.hornbill.com//xmlmc//apps/com.hornbill.servicemanager/?method=shrGetCustomerDetails: invalid request :path "//xmlmc//apps/com.hornbill.servicemanager/?method=shrGetCustomerDetails" .

When you see an error stating "invalid request path", this will be most likely due to an incorrect or missing instance name in the conf.json file.

I would expect to see your instance name somewhere in the path as follows: https://eurapi.hornbill.com/<instanceName>/xmlmc//apps/com.hornbill.servicemanager/?method=shrGetCustomerDetails .

 

The reason why it goes onto say "Create" even though you know the asset exists in Hornbill is because the utility could not complete the search in Hornbill due to the invalid path. Basically, the utility did not receive any results from the search to confirm that the asset already existed, therefore it assumed it needed to create a record. This can be seen here: "API Call failed when searching instance for existing Asset:Post https://eurapi.hornbill.com//xmlmc//data/?method=entityBrowseRecords: invalid request :path "//xmlmc//data/?method=entityBrowseRecords""

Specifying a valid instance name and API key in the conf file should address these particular errors.

I hope that helps.

Dan