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

Show posts

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.

Show posts Menu

Messages - fgn

Hi Adam,
I am sorry, I've been sleeping on this for way too long. Thanks for the clarification. It works now just like expected!
Thank you very much.
Hi everyone,

I tried to download the recent TeamViewer Update and noticed it won't download.
According to the logs, the download location is referenced as "localhost"

QuoteSyncUpdate: 127015bb-e26c-4bd3-af9e-7abffc3c04f7 - Downloading file: 'file://localhost/PatchMyPCRepository/TeamViewer_Full.msi' to 'C:\Program Files\Microsoft Configuration Manager\ISVTemp\xluyykgi.2fc\TeamViewer_Full.msi'.   SMS_ISVUPDATES_SYNCAGENT   18.05.2021 16:23:16   7100 (0x1BBC)
SyncUpdate: An unexpected error ocurred attempting to download content from 'file://localhost/PatchMyPCRepository/TeamViewer_Full.msi':   SMS_ISVUPDATES_SYNCAGENT   18.05.2021 16:23:16   3916 (0x0F4C)
SyncUpdate: ==================== Exception Detail Start =======================   SMS_ISVUPDATES_SYNCAGENT   18.05.2021 16:23:16   3916 (0x0F4C)
SyncUpdate: Exception type: WebException   SMS_ISVUPDATES_SYNCAGENT   18.05.2021 16:23:16   3916 (0x0F4C)
SyncUpdate: Exception HRESULT: -2146233079   SMS_ISVUPDATES_SYNCAGENT   18.05.2021 16:23:16   3916 (0x0F4C)
SyncUpdate: Exception Message: The network name cannot be found.   SMS_ISVUPDATES_SYNCAGENT   18.05.2021 16:23:16   3916 (0x0F4C)
SyncUpdate: Exception source System   SMS_ISVUPDATES_SYNCAGENT   18.05.2021 16:23:16   3916 (0x0F4C)
SyncUpdate: Exception TargetSite System.Net.WebResponse EndGetResponse(System.IAsyncResult)   SMS_ISVUPDATES_SYNCAGENT   18.05.2021 16:23:16   3916 (0x0F4C)
SyncUpdate: Stack    at System.Net.FileWebRequest.EndGetResponse(IAsyncResult asyncResult)~~   at System.Net.WebClient.GetWebResponse(WebRequest request, IAsyncResult result)~~   at System.Net.WebClient.DownloadBitsResponseCallback(IAsyncResult result)~~--- End of stack trace from previous location where exception was thrown ---~~   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()~~   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)~~   at Microsoft.ConfigurationManager.ISVUpdatesSyncAgent.DownloadManager.Request.<DownloadFileAsync>d__24.MoveNext()   SMS_ISVUPDATES_SYNCAGENT   18.05.2021 16:23:16   3916 (0x0F4C)
SyncUpdate: ===================== Exception Detail End ========================   SMS_ISVUPDATES_SYNCAGENT   18.05.2021 16:23:16   3916 (0x0F4C)
SyncUpdate: WebException status : 'UnknownError   SMS_ISVUPDATES_SYNCAGENT   18.05.2021 16:23:16   3916 (0x0F4C)
SyncUpdate: 127015bb-e26c-4bd3-af9e-7abffc3c04f7 - Download of update 127015bb-e26c-4bd3-af9e-7abffc3c04f7 failed, unable to continue   SMS_ISVUPDATES_SYNCAGENT   18.05.2021 16:23:16   3916 (0x0F4C)

Catalog was updated just before the the log was created

I guess I can't fix that on my side.

Thank you!
Just wanted to post a follow up as I have found the issue.

The issue is related to the different installations (.exe and .msi).
As we are using .msi installer to customize our installation the provided update is not applicable as they are using different registry keys.

MSI installer for example "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{36A33BB9-E44B-45EA-A4FD-E861A103FF97}"
and for .exe

Unfortunately there's no chance we can use the .exe installer as customization on install is needed.

Thank you Cody for your offer to schedule a support session, but I guess there's nothing to support right now so we can cancel it. Not quite sure how to cancel as I haven't received any inviation or anything else after I scheduled a call via the link.

For now we probably need to wait until you support the update for msi installers as well.

Regarding the different installation states on other clients. Seems that those guys have just manually installed an exe-version and the update applied correctly.
Hi Cody,

actually I am not able to figure it out and have now spent way too much time on it.

I am testing the update on two devices. Both have TeamViewer 15 installed but are having different minor versions. On one of the devices I have tried multiple minor versions to see if it makes any change. It doesn't.
So right now I am stuck with an installed version (15.6.7) but the reports (e.q. Compliance 8) are reporting the update as "not required" and therefore wouldn't show up. I quadruple checked the applicability rules / registry.
There's a Key (HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{36A33BB9-E44B-45EA-A4FD-E861A103FF97}) with DisplayName set to "TeamViewer" and DisplayVersion to "".

Both clients just work / report fine to any SCCM component, no obvious issue present in log files related to software updates.
As I have tested my application deployment of the new version on both of those clients before the testing of the update it may have corrupted something.
Therefore I went and tried another client which had an even older version installed (15.1.3937.0). The update was available to install yet the registry key never changed to anything newer than 15.1.3937.0. However the local TeamViewer.exe showed 15.8.3 in the files' details tab. Checking the client with the "Client Center for Configuration Manager" (3rd Party Tool by Rob Zander) there is no TeamViewer 15.8.3 Update marked as applicable or installed. But there's an update for TeamViewer 12(!) marked as installed.

At the moment I think there is something really weird happening on our side and it has nothing to do with your published updates.

My last idea until I'll just deploy the latest version as an application:
We are using the msi installer with options for management assignments (API token etc.) - are there any known problems with patching the MSI versions with the updates provided by you? I would have thought it was working, but obviously things are bit different.

Best regards
Hi Cody,

thanks for the explanation, I didn't know that. I just compared the most recent ones to the older ones we automatically installed and in those rules, Wow6432Node was always written out.
Gotta have to find another reason why it is reported as not required.

Thanks you anyways!

Best regards

I just tried to debug why the Update wouldn't showed up and checked the Applicability Rule:

  <bar:RegValueExists Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\TeamViewer" Type="REG_SZ" RegType32="true" />
    <bar:RegSz Comparison="EqualTo" Data="Teamviewer Host" Value="DisplayName" Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\TeamViewer" RegType32="true" />
  <bar:RegSzToVersion Comparison="LessThan" Data="" Value="DisplayVersion" Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\TeamViewer" RegType32="true" />
  <bar:RegSzToVersion Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\TeamViewer" Value="DisplayVersion" Comparison="GreaterThanOrEqualTo" Data="" Key="HKEY_LOCAL_MACHINE" RegType32="true" />

It seems that it was missing from the two prior versions as well.
Has there been any major change that I've missed or is that just an issue on your side?

Hi mitchelw,

thanks for your reply. Indeed I did not realize that there is a new version out despite checking the rss feed.

What doesn't make sense for me yet though is, as the catalog sync wasn't done yet, the 'old' update has not been marked as superseded / expired. So I would assume the update would install fine over the currently installed one (9.1.x).

Can someone please enlighten me about how the detection / applicable rule is working as I may see some issues with rolling out updates like that.
If I deploy an update of any kind of software it usually takes some time until every client has been online and installed the update.
So if the update gets superseded (or not applicable) without synchronizing my SUP I will have a deployment that runs into errors for every client that is not updated yet.

In my understanding an update was applicable until SUP is synchronized again and it will receive the updated metadata.

Thank you

Best regards

i am not quite sure if this is really an issue of Patch My PC update package but I am unable to successfully install above update (DL-9.2M2).
After successfully publishing the update I try to install it on a test client via Software Center (as it is reported as I needed update). Unfortunately it is running into error 0x80240017(-2145124329) which translates to Update not applicable according to google.
I cannot see any messages in event log or in any CCM log that is relevant (to my knowledge).
Also I tested with some other clients (different models) with no success.

If I run the exe installer that is downloaded into my ccmcache folder manually I can successfully run the update with no further issue.

So my question is regarding the rules of the update package and where to find any further details about why it isn't running anything.

Thanks for your help.

Best regards