Asset Import/Update not completing

[Steve Giller]

The Asset Import does not appear to be completing consistently, so not all assets are being updated from SCCM.

The log file just stops: no errors or warnings.
Running at the command line the results are inconsistent, sometimes it goes through and completes, others it just stops and returns to the prompt.
There's no obvious reason - it doesn't run for a certain amount of time, or stop on a certain asset, or even in a certain section.
An example of the output where there's been a failure followed by a success would be:

C:\sw_tools\Assets>db_asset_import_w32.exe -file=conf_sccm_assetscomputer.json
[DEBUG] ---- XMLMC Database Asset Import Utility V1.2.1 ----
[DEBUG] Flag - Config File conf_sccm_assetscomputer.json
[DEBUG] Flag - Zone eur
[DEBUG] Flag - Dry Run false
[DEBUG] Connecting to Database Server: DC-HVSQL-01\SCCM
[DATABASE] Connection Successful
[DATABASE] Running database query for Server assets. Please wait...
21 / 24 [===================================================>-------] 87.50 % 0
C:\sw_tools\Assets>db_asset_import_w32.exe -file=conf_sccm_assetscomputer.json
[DEBUG] ---- XMLMC Database Asset Import Utility V1.2.1 ----
[DEBUG] Flag - Config File conf_sccm_assetscomputer.json
[DEBUG] Flag - Zone eur
[DEBUG] Flag - Dry Run false
[DEBUG] Connecting to Database Server: DC-HVSQL-01\SCCM
[DATABASE] Connection Successful
[DATABASE] Running database query for Server assets. Please wait...
24 / 24 [=========================================================] 100.00 % 6s
Processing Complete!
[DEBUG] Connecting to Database Server: DC-HVSQL-01\SCCM
[DATABASE] Connection Successful
[DATABASE] Running database query for Laptop assets. Please wait...
963 / 963 [====================================================] 100.00 % 4m48s
Processing Complete!
[DEBUG] Connecting to Database Server: DC-HVSQL-01\SCCM
[DATABASE] Connection Successful
[DATABASE] Running database query for Desktop assets. Please wait...
1850 / 1850 [=================================================] 100.00 % 15m44s
Processing Complete!
[DEBUG] Connecting to Database Server: DC-HVSQL-01\SCCM
[DATABASE] Connection Successful
[DATABASE] Running database query for Virtual Machine assets. Please wait...
438 / 438 [====================================================] 100.00 % 4m16s
Processing Complete!
[DEBUG] Updated: 1892
[DEBUG] Updated Skipped: 1380
[DEBUG] Created: 1
[DEBUG] Created Skipped: 2
[DEBUG] Time Taken: 24m58.6625914s
[DEBUG] ---- XMLMC Database Asset Import Complete ----

C:\sw_tools\Assets>

As you can see, the first run just halts shortly into the first stage, the second run sails through. When it does complete the results are as expected.

I've attached the config file in case that's causing a problem.

All suggestions gratefully received!

 

[Steve G]

Hi @DeadMeatGF,

Thanks for posting!

Firstly, from within your admin console, could you please delete the API key that you've been using to perform these imports, as you've posted the config file with this key to this public forum. We've removed the config file from the original post for you.

I've not come across this issue before unfortunately, and have run dozens of imports from SCCM data. The config looks good to me, there's nothing obvious in there to point to why this would be failing some times and not others. What is the last line written to the log file before the tool ends?

I've had a look at the code and there are areas within the tool where we could increase the level of logging to help debug what is happening to cause your import to fail. I'll update the Go code and provide another binary with advanced logging. Once this is done, I'll post the link to the Github release here so that you can download and give it a whirl, and feedback results.

Kind regards,

Steve

[Steve Giller]

Ooops! That's deleted, sorry about that.

There's nothing in the log file, one minute all is moving along nicely then it just stops - e.g.

2016/12/06 08:58:27 [DEBUG] Asset ID: DC-DOOR-ACCESS-
2016/12/06 08:58:27 [DEBUG] Update Asset: DC-DOOR-ACCESS-
2016/12/06 08:58:27 There are no values to update.
2016/12/06 08:58:27 [DEBUG] Asset ID: DC-HV-07
2016/12/06 08:58:27 [DEBUG] Update Asset: DC-HV-07
2016/12/06 08:58:28 There are no values to update.
2016/12/06 08:58:28 [DEBUG] Asset ID: DC-HV-03
2016/12/06 08:58:28 [DEBUG] Update Asset: DC-HV-03

I'll run the advanced logging when it's available and hopefully we can track it down.

[Steve Giller]

@steve_g Did you get the advanced logging in place, as I'm getting this issue again - the import just stops dead, no errors or other issues, no consistency in where it stops, and running from the cmd prompt the program just closes cleanly and returns so there's not really any opportunity to troubleshoot.

[Steve Giller]

Just as an update - I have noticed that the estimated time remaining counter freezes for a few seconds just before the import aborts, don't know if that will help?

[Steve G]

Improved logging capabilities have been added to the Database Asset Import tool, details of which can be found on our Github:

https://github.com/hornbill/goDBAssetImport

And Wiki page:

https://wiki.hornbill.com/index.php/Database_Asset_Import

Kind regards,

Steve