Driver error - Shared printer install fails with 0x000000cb
When trying the share my printer the installation fails with error 0x000000cb right at the end. The log returns:
Error ExtractCabinetFiles: SetupIterateCabinet failed with GetLastError code = 2
Error CopyFilesToInstallLocation: Failed extracting files from the cabinet file ss#base_2022.2.0.0.cab
I tried using older driver versions, different computers/windows versions, I even reinstalled Windows on both client and printer server, but I can't find a solution. I will be grateful for any help you can provide.
-
I remember something similar on a customer's site a little while back. We could not work out what was happening at the time as it was only one PC that had this issue but I think the solution we used was to install the device on the PC as a local device first using the same driver build and then connect up to the shared network printer
0 -
Funny thing is, the driver is installed but the operation fails at right at the end regardless. Or so I thought, what threw me away was that the driver is said to be installed but actually has some files missing. Adding the files manually and a few register changes later, the printer gets installed... but doesn't actually prints.
Anyway, I resolved my issue using a older version of the Elgin driver (2020.4), not sure if I could make it work without it, installing physically on the client machine was not a option.
I suspect the fact that the client runs Windows 10 Single Language (non English) may be the cause, just mentioning it in case a dev would like to investigate.
0 -
I have registered just to respond here in case someone finds this helpful.
2022.2 has definitely introduced a regression where trying to add a network share printer results in a failure with code 0x000000cb. The problem does not exist in 2022.1. Downgrading to 2022.1 on the host machine and removing the buggy driver from Print Management on the client machine (do not skip this step as the client system will try to use the already installed driver otherwise) results in a successful attempt.
0 -
That is odd as 2022.2 was not available when we encountered the issue and we were using 2021.1 at the time
0 -
I'm not sure about 2021.1, but the second I removed 2022.2 and installed 2022.1 everything did work fine for me.
0 -
I second this, I remember version 2021.1 giving me the same error. Nevertheless, it's clearly a case of a faulty driver.
0 -
Not sure on the faulty driver, as the error did not occur on every PC and some installed correctly first time.
0 -
Maybe it's a combination of the driver version and host/client operation systems? In my setup, the host runs Windows 7 and the client runs Windows 10.
0
Vous devez vous connecter pour laisser un commentaire.
Commentaires
8 commentaires