WinSCP and Firefox Fail with Error 0x80070002

DVK · March 22, 2019, 09:04:44 AM

Same issue with 5.13.9

Justin Chalfant (Patch My PC) · March 23, 2019, 02:35:18 PM

Hmm, maybe it's still an SCCM issue. Have you tried publishing using our service?

DVK · March 27, 2019, 03:11:21 AM

Is it compatible with 1806+ functionality? I mean, using both the 1806+ and the publishing service.

Justin Chalfant (Patch My PC) · March 27, 2019, 04:48:24 AM

Yeah, that should be ok. I would only enable this problematic product in the publishing service if you still want to use SCCM.

DVK · April 01, 2019, 10:31:17 AM

It worked! Thx!

nlopezs74 · May 14, 2019, 06:58:31 AM

Merged Topics

Hello everyone,

I am new to third party catalogs. I am testing the trial catalog which includes Firefox. I am getting error 0x800700002. DP looks good. Any help is appreciated.

Justin Chalfant (Patch My PC) · May 14, 2019, 09:19:56 AM

I believe you may have just opened a case via the technical support email page? If so, we can take this case there, and I'll follow up on this post with the resolution.

nlopezs74 · May 14, 2019, 11:09:37 AM

Yes, I did. I was not sure if I could get support

Thanks

Justin Chalfant (Patch My PC) · May 14, 2019, 11:24:05 AM

We will always provide support for anyone interested in our product

nlopezs74 · 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.

Justin Chalfant (Patch My PC) · May 16, 2019, 09:42:54 AM

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 · May 16, 2019, 09:53:21 AM

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

Justin Chalfant (Patch My PC) · May 16, 2019, 09:54:33 AM

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

Justin Chalfant (Patch My PC) · May 16, 2019, 10:01:47 AM

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 · May 16, 2019, 11:02:29 AM

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

Thanks