2 Posts
0
4306
Dell Command System Driver Library Import - Error processing the driver package(s)
Is anyone else seeing a issue with the Dell Driver Library Import Wizard for Configuration Manager? When I try to import the drivers for the OptiPlex 5000. The wizard attempts to download the drivers but ultimately ends up failing. When checking the logs the software states it is a permissions issue with the user folder but I have reviewed those. The administrators, users, and domain admins all have full control of user folders. I need help figuring out why this won't import. I am running 5.2 version of the software and 2111 of SCCM. I have tried upgrading the Dell software but it does not fix it by doing that.
# 9/15/2022 8:28:28 AM #
SOI-SI19: The Installed Components XML file was not found: C:\ProgramData\Dell\CommandIntegrationSuite\Logs\_ComponentsInstalled.xml. Creating a new file
SUTILS-GDP02: Successfully retrieved distribution points: 4
# 9/15/2022 8:32:31 AM #
OSDLIB-EFC04: Successfully constructed path to manifest file: C:\Users\ \AppData\Local\Temp\my02e1un
Error (System.UnauthorizedAccessException) at OSMLIB-PDL04:
Access to the path 'C:\Users\ \AppData\Local\Temp\my02e1un' is denied.
Error (System.UnauthorizedAccessException) at OSMLIB-CCDP01:
Access to the path 'C:\Users\ \AppData\Local\Temp\my02e1un' is denied.
DLMUI-DIPE01: An exception occurred: Access to the path 'C:\Users\ \AppData\Local\Temp\my02e1un' is denied.
RedGoldSupport
2 Posts
0
September 20th, 2022 13:00
I was finally able to find a solution. I had to run Dell Integration Suite 6.1 with SCCM 2111 in order to get it to work. I kept installing 6.2 with 2111 and it was not supported. According to Dell documentation, Integration Suite 6.2 is supported for SCCM 2203 and above. You should be fine with your current build.
DELL-Cares
Moderator
Moderator
•
25.6K Posts
0
September 15th, 2022 23:00
We tried reaching you on a private message asking for the Service Tag number to ascertain the warranty but did not receive a response. Please feel free to reply to the private message whenever you are available.
FlyEaglesFly2022
3 Posts
0
September 20th, 2022 11:00
I'm having the same issue, using SCCM 2207 and Dell Command Integration Suite for System Center version 6.2.0.137. Did you ever find a fix or a workaround?
FlyEaglesFly2022
3 Posts
0
September 20th, 2022 13:00
hmm sounds like we need an updated version for 2207
FlyEaglesFly2022
3 Posts
0
September 22nd, 2022 11:00
After applying the Configuration Manager 2207 Hotfix (KB15498768) it appears that it also fixed the issue with the import process for the Dell Integration Suite
DELL-Cares
Moderator
Moderator
•
25.6K Posts
0
June 2nd, 2023 01:00
Hello. How can we assist you? What do you mean, you can't import driver packages?
tjacobs42
13 Posts
0
June 2nd, 2023 01:00
We have exaclty this same problem since 2 years: it is not possible to import driver packages that are based on EXE. Only CAB-file based packages can be importet.
We also had a DELL case open, but they were not able to help us: 148049373
MesaITMan
1 Rookie
1 Rookie
•
2 Posts
0
December 6th, 2023 14:59
@tjacobs42 I can confirm that this is still an issue. Were you ever able to resolve the issue?
Robert R.
2 Posts
0
February 29th, 2024 23:38
Fixed my issue occurring on MECM 2309 when using Dell Command | Integration Suite for Microsoft System Center 6.5.1 (Released January 2024)
Dell doesn't officially support 2309 yet, but it still works after making the below SQL modification. I searched for two days looking for an answer, and I finally made the association with SQL after seeing this article. The Dell tool is doing what you might manually do otherwise, and this fixed my specific issue.
Running this query against the MECM DB is what solved my issue (where DB name is your MECM DB):
ALTER DATABASE [database name] SET COMPATIBILITY_LEVEL = 150
Supported SQL Server versions - Configuration Manager | Microsoft Learn - the setting is mentioned in the Microsoft documentation as well, but it is easily overlooked.
Making the connection between the SQL database and the failed driver imports is a bit weird but trust me this minor change from 160 to 150 is what worked in my scenario, and it's documented as correct by Microsoft.
(edited)