• Welcome to Support Forum: Get Support for Patch My PC Products and Services.
 

WinSCP and Firefox Fail with Error 0x80070002

Started by wokkeltje, January 04, 2019, 01:09:33 AM

Previous topic - Next topic

Support Team (Patch My PC)

We are also looking into repro-ing the issue and will reach our to the SCCM product group if it's still a problem in the latest 1902 build.

Quote from: nlopezs74 on May 16, 2019, 09:41:34 AM
The workaround works. Publishing the update with the Publishing tool instead of publishing with SCCM. There is a bug with spaces in the deployment name with SCCM publishing.

nlopezs74

Yes, it is still a problem with SCCM version 1902. That would be awesome. Thanks for taking the request for a non-paying customer and finding a solution. I will be testing other deployments for a month or two.

Thanks again

Support Team (Patch My PC)

Was the update published from 1902 or did you upgrade to 1902 after the update was previously published?

Support Team (Patch My PC)

We have a repro in SCCM 1904 TP. We will report to the engineering team at MSFT to make sure they are tracking this issue.

nlopezs74

It was the original created with 1810. I am going to try re-creating it with current version.

Thanks

Support Team (Patch My PC)

The issue will still exist in 1902 we can confirm that.


Support Team (Patch My PC)

#32
Merged a few similar topics.

A Little Background


  • SCCM 1806 originally had a bug where the in-consolep publishing of a download URL that contained a space such as http://download-installer-origin.cdn.mozilla.net/pub/firefox/releases/66.0.3/win64/en-US/Firefox Setup 66.0.3.exe would fail to publish with full-content. This bug was fixed in CB 1810.
  • SCCM 1810 and 1902 resolved the publishing bug with spaces, but it now seems there is another issue on the client side where any update where the installer filename contains a space such as "Firefox Setup 66.0.3 x64.exe" will fail on the client side with error (0x80070002 = The system cannot find the file specified.) We reported this to the SCCM product group on 05/17/2019 and hope for a resolution in a future current branch build.

Workaround for this Issue:

UPDATE: See workaround in the post below.

The current workaround for this is to re-publish affected updates (Current known updates with issues is WinSCP and Firefox) using our publishing service https://patchmypc.com/publishing-service-setup-documentation as it is not affected by this issue.

More info on how to republish updates with our service at:

When, Why, and How to Republish Update(s) - https://patchmypc.com/faq-scup-catalog#republishing-updates

Support Team (Patch My PC)

#33
UPDATE: Workaround Fix Released on May 23, 2019

After working with the Microsoft Configuration Manager product group and digging deeper into why this 80070002 (The system cannot find the file specified.) actually occurs. We were able to modify the filename in the SDP to match the downloaded filename from the vendor until a more permanent resolution is added into a future Configuration Manager current branch update.

We have created new updates that were released on May 23, 2019, at 8:30 PM that should resolve the 80070002 error on the client side. This updates will supersede the previous UpdateIDs with the same title name.


  • WinSCP 5.15.1                                 UpdateID: 3e2aa875-ad20-4053-a653-63e8b2dce8f0
  • Mozilla Firefox 67.0.0 (x64)              UpdateID: 286bda43-2fc1-4f7d-8053-446b4f4a0cba
  • Mozilla Firefox 67.0.0 (x86)              UpdateID: 9b386b70-6fbc-4e24-803d-e270a4dea9e2
  • Mozilla Firefox ESR 60.7.0 (x64)        UpdateID: 4ed2b277-bfba-477d-b578-002ccf056179
  • Mozilla Firefox ESR 60.7.0 (x86)        UpdateID: cdea1ad7-e060-4b03-8fc2-7b95544b45b2