No recent activity in DriverCatalog.log

From: [email protected] [mailto:[email protected]] On 
Behalf Of Wilbers, Scott
Sent: Thursday, November 19, 2015 10:07 AM
To: [email protected]
Subject: RE: [mssms] Driver import failing

Look at DriverCatalog.log file

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Murray, Mike
Sent: Thursday, November 19, 2015 11:50 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] Driver import failing

Errors I’m seeing:

Error setting property (TransformAnalysisDate) 0x80041002!        SMS Provider  
   11/19/2015 9:27:22 AM 8448 (0x2100)
Error setting property (TransformReadiness) 0x80041002!             SMS 
Provider     11/19/2015 9:27:22 AM 8448 (0x2100)

After Googling, someone said it might be a permissions issue on the share, but 
I checked that, it’s fine.

Mike

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Niall Brady
Sent: Thursday, November 19, 2015 9:30 AM
To: [email protected]<mailto:[email protected]>
Subject: Re: [mssms] Driver import failing

what does the smsprov.log tell you ?

On Thu, Nov 19, 2015 at 6:26 PM, Murray, Mike 
<[email protected]<mailto:[email protected]>> wrote:
Hey folks,

The last couple of times I’ve tried to import drivers from a Dell CAB, every 
one errors out. It goes through really fast. Any ideas?

[cid:[email protected]]


Best Regards,

Mike Murray
Desktop Management Coordinator - IT Support Services
California State University, Chico
530.898.4357
[email protected]<mailto:[email protected]>





********************************************************************************************
Note:
The information contained in this message may be privileged and confidential 
and protected from disclosure. If the reader of this message is not the 
intended recipient, or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any 
dissemination, distribution or copying of this communication is strictly 
prohibited. If you have received this communication in error, please notify us 
immediately by replying to the message and deleting it from your computer.
********************************************************************************************


Reply via email to