SCCM 2012 - Blank column headers were found

[Frank1975]

Hi all,

we have done the SCCM2012 integration. So far so good. The scheduled import is every 4 hours.
Unfortunately, it looks like when the Import is kicking off, that the MID Server is not ready for the Computer Identity call and gives me an error which is "Blank column headers were found".

All other Imports just work fine. When i kick off a manual import, got the same error, but when i wait until the Import has been completed and the MID Server is still "awake" and start another Import, everything is working fine. Wondering if someone else has the same issue. The MID Server is dedicated to the SCCM Job, so no Discoveries are running on that MID Server.

Any ideas how to wake up the MID Server upfront and make it do the job beginning with the first task and not the second ?

And thoughts are appreciated.

Thanks

Frank

[esioson]

Hi Frank:

Looking at this post, you have probably bypassed and/or resolved the above issue.   However, I wanted to add as a reply for anyone else that may run into this same issue.

I ran into this issue via using JDBC as a data source via my mid-servers where the error resulted in Blank Column Headers were found.   I checked the source table (SQL Server) and there were no blank columns...ultimately, in my case, this was an issue with the mid server exceeding the time-out value of 300 seconds.   (Instance is running on Fuji Patch 6).   I spent at least an hour trying trolling over my source data because I figured it may be something in the actual data content itself as I was pulling in large note fields from the source with > 4000 bytes at an average.

Although the query had run before for previous imports, with this one erroring out, I added a new OR condition.   So, I ran the query against my SQL server source DB and sure enough, it took a long time to return.   I modified the query in the JDBC source so that it leveraged one of the existing indexes and this resolved my issue.

So, in my case, the error thrown had nothing to do with the actual issue.

Thanks!

- Ernadel

[Frank1975]

Hi Ernadel,

thanks for your update. Somewhere in the community i found that it could be related of a "noise area" the MID Server is in (would make sense about the time out.)

Since we decided to have SCCM as our source of truth for Windows Systems, i have disabled a lot of our discovery schedules and installed a dedicated MID Server Service for the SCCM Integration only. Since that time the error is no longer showing up.
We use now discovery only for SSH and SNMP only.

thanks

Frank