Proposed solution works well 
. Thank you Jiri S.
. Thank you Jiri S.
- Welcome to Support Forum: Get Support for Patch My PC Products and Services.
Patch My PC Support
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages1
#1
Report Publishing/Download/Hash Issues (Enterprises Using ConfigMgr and Intune) / Re: Issue with publish full content of any update by Patch My PC (and also by SCUP)
July 04, 2019, 01:38:47 AM #2
Report Publishing/Download/Hash Issues (Enterprises Using ConfigMgr and Intune) / Re: Issue with publish full content of any update by Patch My PC (and also by SCUP)
June 28, 2019, 05:25:51 AM
Hi,
I'll try this solution and let you know. I read the post, but as there is no mentioned precisely this error code I didn't try it.
Thank you
Jiri S.
I'll try this solution and let you know. I read the post, but as there is no mentioned precisely this error code I didn't try it.
Thank you
Jiri S.
#3
Report Publishing/Download/Hash Issues (Enterprises Using ConfigMgr and Intune) / Issue with publish full content of any update by Patch My PC (and also by SCUP)
June 27, 2019, 07:39:57 AM
Hi,
Could you please help me with issue in our test environment?
We have more than one environments, and in real testing, without any restriction all work like charm, but on that with FW restrictions (which I unfortunately cant manage) is probably timestamp blocked.
I'm getting this error in patchmypc.log:
An error occurred while publishing an update to WSUS: Failed to sign package; error was: 2149122449
Unauthorized (401).
Source: Windows
And if I cleanup address for timestamp, I'm getting this error in patchmypc.log:
An error occurred while publishing an update to WSUS: Failed to sign package; error was: 2147942487
The parameter is incorrect.
Source: Windows
I mentioned SCUP as there is option for turn off timestamp and I had same issue since I didn't turn off the timestamping.
So, my questions are: Is there any option for turn off timestamp in PMPC? Or am I absolutely wrong, and error is connected with anything else?
Thank you
Jiri S.
Could you please help me with issue in our test environment?
We have more than one environments, and in real testing, without any restriction all work like charm, but on that with FW restrictions (which I unfortunately cant manage) is probably timestamp blocked.
I'm getting this error in patchmypc.log:
An error occurred while publishing an update to WSUS: Failed to sign package; error was: 2149122449
Unauthorized (401).
Source: Windows
And if I cleanup address for timestamp, I'm getting this error in patchmypc.log:
An error occurred while publishing an update to WSUS: Failed to sign package; error was: 2147942487
The parameter is incorrect.
Source: Windows
I mentioned SCUP as there is option for turn off timestamp and I had same issue since I didn't turn off the timestamping.
So, my questions are: Is there any option for turn off timestamp in PMPC? Or am I absolutely wrong, and error is connected with anything else?
Thank you
Jiri S.
Pages1