Hello,

I'm trying to add some Lenovo drivers to CM 2012 R2. I import the drivers normally and create a driver package for them. Import process starts and after it finishes I receive two errors (same error twice):

Error: Some driver package(s) are updated on distribution points successfully. But some are not.

1 Driver Package Name - The SMS Provider reported an error

What could be wrong and what logfiles I should check? I tryid to read smsprov.log but I didn't find anything interesting (IMO). When I check the folder where driver package is placed there is nothing in this folder after import process.

This also can not be a permission issue because content location is in the same server as CM and system hass full access permissions (at share level there is full control / everybody).

There errors in smsprov.log after import process:

Error setting property (InUse) 0x80041002! SMS Provider 11760 (0x2DF0)
Error setting property (IsBroken) 0x80041002! SMS Provider 11760 (0x2DF0)
Error setting property (IsChild) 0x80041002! SMS Provider 11760 (0x2DF0)

Also, why is the driver importing so slow? Could it indicate somekind of an issue?

Those logs are taken out of context and do not help at all. Which error code/message does the console display?

Console displays this after the import process

Error: Some driver package(s) are updated on distribution points successfully. But some are not.

1 Driver Package Name - The SMS Provider reported an error

After I go and look the driver package folder in disk, it's empty.

Hi,

Please make sure all the up-to date drivers, and their location is correct.

Here's an excelent tool you can use to 'grab' the needed drivers from the installed OS to be used with ConfigMgr:http://gallery.technet.microsoft.com/ConfigMgr-Driver-Injector-aae7d17d

Thanks Xin

Some of the drivers had a source path that didn't exist anymore and that caused the issue when importin new drivers. 

I had the same problem and have been beating on it for a while now. I found the source of the issue and a (slow but effective) way to fix it.

Some of the drivers you are importing are most likely already in SCCM and are referenced by other driver packages. Some of those arent in the location that SCCM expects them to be in. 
I went thru the import driver wizard and just told it not to import duplicates. It gave me a results screen with a listing of all the drivers it did not import. I copied that and pasted it into notepad.

Next I went to Drivers in SCCM and did a search for the drivers that it reported as already in the system. Each time it returned a handful. I looked specifically for the ones in the category I had created (Lenovo Tablet10 x64 for example)

Right click each driver - properties and look at the source path. Another way to do it is to add the column in SCCM - Drivers of "Content Source Path". Also, hit the yellow info bar about too many results and allow it to display all the drivers you have in inventory. Content Source Path is where it will tell you where it expects to find the actual file. In all of my cases, the folder or file was not there (had been moved etc). I deleted those drivers with the rogue info and reimported the drivers successfully.

I was able to get the driver package added and distributed successfully.

Hope this helps someone in the future. I was looking at the driver packages source and it looked ok, so that is where my confusion came from. It's not very clear.

I can confirm, at least, that when I was experiencing this issue that StevenLoumakis' solution and reasoning as to why it's occurring is correct. There was an SCCM administrator before me that setup OSD for a client and they haphazardly placed their driver sources in random locations and nothing was uniform or had any rhyme or reason, it seemed. After I rearranged the driver source folder and tried to import a couple driver updates, I was getting this error. I was able to confirm, though, that new drivers their SCCM environment never knew about was able to import and build a new driver package successfully.