Driver Import Wizard after upgrade to CU2

[adblunt]

Hi All,

 

I'm wondering if anyone may have come across something similar to this or may have any advice on where else I can look for clues.

 

I've just upgraded our SCCM 2012 R2 SP1 site to CU2 (skipping CU1) and now am experiencing problems importing drivers. Running the wizard I give it the source folder as normal and click next, once it completes validating file permissions etc and asks which drivers to import there are no drivers offered. This happens whether it's new or old drivers, it doesn't seem to matter. SMSProv.log shows the following for each driver it finds:

CExtUserContext::EnterThread : User=AD\nnnnnn Sid=0x010500000000000515000000E79E30632337F7BBC4F57EB503220200 Caching IWbemContextPtr=0000009DFEF4D5C0 in Process 0xcd4 (3284)	SMS Provider	18/11/2015 22:15:33	3440 (0x0D70)
Context: SMSAppName=Configuration Manager Administrator console	SMS Provider	18/11/2015 22:15:33	3440 (0x0D70)
Context: MachineName=nnnnnn.domain.nn	SMS Provider	18/11/2015 22:15:33	3440 (0x0D70)
Context: UserName=AD\nnnnnn	SMS Provider	18/11/2015 22:15:33	3440 (0x0D70)
Context: ObjectLockContext=4dec651d-0d4b-4e54-838a-b633f8b0ee9e	SMS Provider	18/11/2015 22:15:33	3440 (0x0D70)
Context: ApplicationName=Microsoft.ConfigurationManagement.exe	SMS Provider	18/11/2015 22:15:33	3440 (0x0D70)
Context: ApplicationVersion=5.0.8239.1301	SMS Provider	18/11/2015 22:15:33	3440 (0x0D70)
Context: LocaleID=MS\0x409	SMS Provider	18/11/2015 22:15:33	3440 (0x0D70)
Context: __ProviderArchitecture=32	SMS Provider	18/11/2015 22:15:33	3440 (0x0D70)
Context: __RequiredArchitecture=0 (Bool)	SMS Provider	18/11/2015 22:15:33	3440 (0x0D70)
Context: __ClientPreferredLanguages=en-US,en	SMS Provider	18/11/2015 22:15:33	3440 (0x0D70)
Context: __CorrelationId={DC20BE3B-2244-0003-3E6B-21DC4422D101}	SMS Provider	18/11/2015 22:15:33	3440 (0x0D70)
Context: __GroupOperationId=65199	SMS Provider	18/11/2015 22:15:33	3440 (0x0D70)
Context: __WBEM_CLIENT_AUTHENTICATION_LEVEL=6	SMS Provider	18/11/2015 22:15:33	3440 (0x0D70)
CExtUserContext : Set ThreadLocaleID OK to: 1033	SMS Provider	18/11/2015 22:15:33	3440 (0x0D70)
CSspClassManager::PreCallAction, dbname=CM_UN2	SMS Provider	18/11/2015 22:15:33	3440 (0x0D70)
ExecMethodAsync : SMS_Driver::CreateFromINF	SMS Provider	18/11/2015 22:15:33	3440 (0x0D70)
Requested class =SMS_Driver	SMS Provider	18/11/2015 22:15:33	3440 (0x0D70)
Requested num keys =0	SMS Provider	18/11/2015 22:15:33	3440 (0x0D70)
CExtProviderClassObject::DoExecuteMethod CreateFromINF	SMS Provider	18/11/2015 22:15:33	3440 (0x0D70)
*~*~e:\qfe\nts\sms\siteserver\sdk_provider\smsprov\sspdriverci.cpp(683) : Could not load OSDDriverCatalog.dll~*~*	SMS Provider	18/11/2015 22:15:33	3440 (0x0D70)
*~*~Could not load OSDDriverCatalog.dll ~*~*	SMS Provider	18/11/2015 22:15:33	3440 (0x0D70)
CExtUserContext::LeaveThread : Releasing IWbemContextPtr=-17508928	SMS Provider	18/11/2015 22:15:33	3440 (0x0D70)

As far as I can tell OSDDriverCatalog.dll exists in the right place and wasn't even changed by CU2. The only registry entry I can find for it looks good and matches a test environment I have which works fine on CU2.

 

Please help!!

 

Thanks

Andy

[adblunt]

In case anyone else ever gets this... I replaced the dll file with the same file on a working site server and rebooted, which also applied Windows updates at the same time. One of the two seems to have got it working again!