jhfry

I realize that this is an old thread, but I just spent 4 days working through the exact issue with Premiere support, who was mostly worthless, and finally discovered the cause and a solution. This was the only place I found a similar issue posted, so I wanted to add an answer in case someone else runs into it. In our case, we observed the problem a few days after upgrading SCCM to 2012 R2 SP1. First we noticed that all of the stored procedures starting with 'p' and 'd' were missing from the database, we were even able to confirm they were deleted by the setup by querying dbo.dbschema (I think thats the table). We had one other, seemingly minor, error in our log. It was a unique key violation trying to add some bitlocker data to the dbo.GroupMap table. Even Microsoft didn't think it was worth looking into until we got the stored procedures back. This error turned out to be the key to all of our problems. It turns out that upgrades delete these stored procedures out of the database, and all of the hardware inventory procedures are created dynamically when the inventory data loader starts for the first time. But in our case, this wasn't happening. To make a very long story short, the issue was caused by a custom inventory class we created over a year ago to collect bitlocker details with hardware inventory. Appearently, when we upgraded, we now had two classes with identical names "Bitlocker.Details.Data", and it would fail every time it tried to do the second one (due to the unique key violation), and never made it far enough to create any of the stored procedures. We simply deleted the custom class from our hardware inventory configuration under client settings, and the next time it tried, it created everything. If anyone ever sees this, I highly recommend looking at any custom inventory classes you have. Export them and delete them and see if it fixes your issue, you can always restore them.