[cifs-protocol] [REG:118092719108783] Clarification on parsing printer driver inf failure - MSPAR RPC InstallPrinterDriverFromPackage

[Edgar Olougouna]

[+ case number, cc casemail, bcc dochelp]
Hello Justin, The case number 118092719108783 has been created for this inquiry. One of our engineers will follow-up soon.

Regards,
Edgar

From: Justin Stephenson <jstephen at redhat.com>
Sent: Thursday, September 27, 2018 1:17 PM
To: Interoperability Documentation Help <dochelp at microsoft.com>
Cc: cifs-protocol at lists.samba.org
Subject: Clarification on parsing printer driver inf failure - MSPAR RPC InstallPrinterDriverFromPackage

Hello,

I am writing code which calls InstallPrinterDriverFromPackage() against Windows Server 2016 providing a valid pszInfPath retrieved from the output of a successful UploadPrinterDriverPackage() call. The upload is successful but the RPC InstallPrinterDriverFromPackage consistently fails with HRESULT 0x80070705(ERROR_UNKNOWN_PRINTER_DRIVER).

Upon the failure, event ID Number 213 is logged in the PrintService Operational event viewer with the following message:

Parsing inf (C:\Windows\System32\DriverStore\FileRepository\xeroxglobalprintdriver_pcl6.inf_amd64_37d0e6a31ac96d78\xerosglobalprintdriver_pcl6.inf) for printer driver testdriver failed (processor architecture Windows x64), error code 0x705, HRESULT 0x80070705.

The UserData details show:
  SetupParseInf
    Label: ParseInfAndCommitFileQueue
    Message: PreSelectDriverEx failed
    InfPath: C:\Windows\System32\DriverStore\FileRepository\xeroxglobalprintdriver_pcl6.inf_amd64_37d0e6a31ac96d78\xerosglobalprintdriver_pcl6.inf
    DriverName: testdriver
    InstallSection: -
    ProcessorArchitecture: Windows x64
    LastError: 0x705
    HResult: 0x80070705

From a Windows 10 Client, I am able to install this printer driver using the same .inf file onto the remote Print Server manually without any issues.

I ran the InfVerif.exe tool from the Windows Developer Kit against the provided inf file and only a single warning was issued about an unused string. I would like to know why the inf parsing is failing, or if there some way to validate a user-provided inf file in the same way that is performed internally by this RPC install method.

I am attaching a packet capture taken on the Windows Server during the failure and also the .inf file used(excluding the several other driver installation files and directories).

Any other ideas what is happening here would be appreciated.

Thank you.

Justin Stephenson
Red Hat
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.samba.org/pipermail/cifs-protocol/attachments/20180927/4d88442f/attachment.html>