Marcs Updater
There have been some reports about issues with the Updater not updating anymore. Please try the latest beta version and switch to another IP Check provider instead of the previous default dnsomatic.com. For some reason they are rate-limiting the number of requests to their service. The new IP Check provider selection allows you to choose another provider in such cases. You can test the functionality with the new "Test" panel.
If you want to add a custom provider to the unstable testing version, store a JSON file like the following under %PROGRAMDATA%\Marcs Updater\ServiceProviders\dyndns.json:
{
"name": "DynDNS.org (Test)",
"endpoint": "https://members.dyndns.org/nic/update",
"method": "GET",
"queryString": "hostname={HOSTNAME}&myip={MYIP}",
"dataPayload": "",
"defaults": {
"username": "test",
"password": "test",
"hostname": "test1.customtest.dyndns.org"
}
}Supported query and payload tags are {USERNAME}, {PASSWORD}, {HOSTNAME} and {MYIP}. Restart the background service and foreground application to apply any changes.
Discussion created on
Posted on
Marc wrote:
Released version 1.5.0.248
- Fixed balloon behavior.
- Fixed bug report URL.
- Fixed updatelog progressbar.
And updates are now hosted on an SSL-secured server!
Posted on
tayiper wrote:
Hey Marc, I need to report back that I get an error (similar to the one that I was getting on an upgrade a few versions back; though if I recall correctly in that case the
program was updated anyway, but this time the .exe file version is still
1.5.0.247), and no mather what I cannot seem to successfully update the program. So far I tried updating the program with service not running (of course, before each attempt I deleted all the entries under HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager\PendingFileRenameOperations so that the notice about restarting the computer doesn't re-appear) and eliminated a few other possible causes. Here below is the first part of text from the error.
A program error was detected:
Application: Marcs Updater.exe
Build: 247
Error Message: Invalid memory access
Error Code: -1073741819
Code Address: 2089880089
Target Address: 1342308352
Sourcecode line: 110
Sourcecode file: update.pb
I am also adding a link to screenshot of the windows displaying the error message: http://i.imgur.com/QlZLo.png
Posted on
Marc wrote:
Hey Tadej, thanks for the report. This error is really annoying and I have not been able to reproduce it. It worked at some point, because I made the installer kill the crashed prozess to continue installation. But it only does that for build 135 and 136, because I thought the bug was fixed.
Could you please give a detailed description about what happened before the crash? It's important for me to know if any Marcs Updater windows or processes were active at the time. I also need to know the operating system, like Windows 7 64bit.
Thanks in advance!
Posted on
tayiper wrote:
Hey, regarding what happened before the crash, I really don't know what to tell you in this case. I just clicked on the balloon tip that says that update is available (or in other instance in some blue icon in the tray saying that update is available). Then the update window appears and you see it downloading the update in progress bar and then the installer starts (and you see messages about installing the service etc.) and everything looks ok until the installer exists and you see in the underlaying window (the one that was showing the download progress bar) that its title changed to "Application Error" and you see that annoying red circle with white cross in the middle :(
In regards to processes were active at the time, it's just "Marcs Updater.exe" (service and GUI) and all the .tmp processes (I saw in Process Explorer: http://technet.microsoft.com/e... that one creates another as a child, so there're more than one launced one after another) created under Temp directory (e.g. the last time "_iu14D2N.tmp"), and also after the failed install there is always a file with .tmp extension created under C:\Program Files\Marcs Updater\ (I have now two, one is named "is-HJSKG.tmp" and the other "is-ORMNB.tmp").
I am running 32-bit version of Windows XP Profesional SP3.
1
Posted on
tayiper wrote:
Oh Marc sorry, I don't know why I haven't thought of this earlier... Now that I was re-checking the Temp directory I saw all the downloaded setup packages (with names like "update339720970.tmp.exe", "update496083002.tmp.exe", "update1048423697.tmp.exe") from the previous unsuccessful attempts and I just launched one "directly" (i.e. by double clicking it), while I closed the service and exit the GUI process beforehand. And I happy to report that this time of course everything went smoothly! :)
P.S. I somehow got the idea for this when I remembered the "because I made the installer kill the crashed prozess to continue installation" part from your reply above. I mean I realized that it must be "Marcs Updater.exe" that is the culprit for the error (if it's running during the upgrade/installation), and so if you launch installed directly it just might work. And indeed it did! :)
Posted on
Marc wrote:
I was finally able to isolate the problems source on my XP VM. The fix will ship with the next version and I will make the installer kill the processes for all previous versions. Thanks for your help, Tadej.