omaha - Project Hosting on Google Code

Last 7 days Dec 28, 2009 DeveloperSetupGuide (Instructions for how to set up a build environment for Omaha) Wiki page edited by ddor...@google.com - Revision r96 Fixed the WiX link. Revision r96 Fixed the WiX link. Last 30 days Dec 22, 2009 issue 13 (ChromeSetup.exe fails with error code 0xc00ce56f) Status changed by gan...@google.com - The fix is in 1.2.183.13. Status: Verified The fix is in 1.2.183.13. Status: Verified Dec 20, 2009 DeveloperSetupGuide (Instructions for how to set up a build environment for Omaha) Wiki page commented on by amckern - The link to WiX is broken - consider this one instead http://sourceforge.net/projects/wix/files/ The link to WiX is broken - consider this one instead http://sourceforge.net/projects/wix/files/ Dec 17, 2009 issue 16 (Compilation failure -SConstruct file not found) Status changed by ddor...@google.com - Status: Invalid Status: Invalid Dec 16, 2009 issue 16 (Compilation failure -SConstruct file not found) commented on by ranjanmagotra - This resolved the issue, Thanks alot This resolved the issue, Thanks alot Dec 15, 2009 issue 16 (Compilation failure -SConstruct file not found) commented on by ddor...@google.com - Make sure you are running "hammer" from the main "omaha\" directory where main.scons is. I can reproduce the error by running "omaha\hammer" from the parent directory. Make sure you are running "hammer" from the main "omaha\" directory where main.scons is. I can reproduce the error by running "omaha\hammer" from the parent directory. Dec 15, 2009 issue 16 (Compilation failure -SConstruct file not found) reported by ranjanmagotra - What steps will reproduce the problem? 1.After setting up the Omaha environment as per the developer setup guide. When I run hammer.bat,it gives following error scons: * No SConstruct file found. File "C:\OmahaProgramFiles\Python24\Lib\site-packages\scons- 1.2.0\SCons\Script\Main.py", line 826, in _main What is the expected output? What do you see instead? It should get Compiled What version of the product are you using? On what operating system? I am building on windows XP with Visual Studio 2008 installed. Please provide any additional information below. What steps will reproduce the problem? 1.After setting up the Omaha environment as per the developer setup guide. When I run hammer.bat,it gives following error scons: * No SConstruct file found. File "C:\OmahaProgramFiles\Python24\Lib\site-packages\scons- 1.2.0\SCons\Script\Main.py", line 826, in _main What is the expected output? What do you see instead? It should get Compiled What version of the product are you using? On what operating system? I am building on windows XP with Visual Studio 2008 installed. Please provide any additional information below. Earlier this year Oct 09, 2009 ServerProtocol (Protocol Omaha uses to communicate with the update server) Wiki page edited by mevis...@google.com - Revision r95 Added link to CUP in protocol doc. Revision r95 Added link to CUP in protocol doc. Oct 05, 2009 issue 15 (You should be able to (permanently) deinstall update checker) commented on by stalle - I second this motion. I see no use in having it run either in the background or as a scheduled task. If it should run, it should be at startup of the program to update and be opt in at first start and in the program settings I second this motion. I see no use in having it run either in the background or as a scheduled task. If it should run, it should be at startup of the program to update and be opt in at first start and in the program settings Sep 28, 2009 issue 13 (ChromeSetup.exe fails with error code 0xc00ce56f) commented on by naesten - Update for other users: I was sent a gears installer to test, it worked, and I replied to the email to which it was attached saying as much. Hopefully, the fix will find it's way into all of the various Google Installers sometime in the near future ... Update for other users: I was sent a gears installer to test, it worked, and I replied to the email to which it was attached saying as much. Hopefully, the fix will find it's way into all of the various Google Installers sometime in the near future ... Sep 23, 2009 UsingOmaha (Using Omaha once you've built it) Wiki page edited by ddor...@google.com - Revision r93 Edited wiki page through web user interface. Revision r93 Edited wiki page through web user interface. Sep 23, 2009 UsingOmaha (Using Omaha once you've built it) Wiki page edited by ddor...@google.com - Revision r92 Edited wiki page through web user interface. Revision r92 Edited wiki page through web user interface. Sep 23, 2009 3 Wiki pages changed by ddor...@google.com - Revision r91 Renamed ApplyingTags to TaggedMetainstallers. Added TaggedMetainstallers">TaggedMetainstallers Edited UsingOmaha">UsingOmaha Deleted ApplyingTags Revision r91 Renamed ApplyingTags to TaggedMetainstallers. Added TaggedMetainstallers">TaggedMetainstallers Edited UsingOmaha">UsingOmaha Deleted ApplyingTags Sep 23, 2009 CustomizingOmaha (How to customize Omaha for your application or organization.) Wiki page edited by ddor...@google.com - Revision r90 Edited wiki page through web user interface. Revision r90 Edited wiki page through web user interface. Sep 23, 2009 CustomizingOmaha (How to customize Omaha for your application or organization.) Wiki page edited by ddor...@google.com - Revision r89 Edited wiki page through web user interface. Revision r89 Edited wiki page through web user interface. Sep 23, 2009 CustomizingOmaha (How to customize Omaha for your application or organization.) Wiki page added by ddor...@google.com - Revision r88 Created wiki page through web user interface. Revision r88 Created wiki page through web user interface. Sep 23, 2009 ApplyingTags (Tagged metainstallers and how to create them) Wiki page edited by ddor...@google.com - Revision r87 Edited wiki page through web user interface. Revision r87 Edited wiki page through web user interface. Sep 23, 2009 UsingOmaha (Using Omaha once you've built it) Wiki page edited by ddor...@google.com - Revision r86 Edited wiki page through web user interface. Revision r86 Edited wiki page through web user interface. Sep 23, 2009 ApplyingTags (Applying tags to the metainstaller) Wiki page added by ddor...@google.com - Revision r85 Created wiki page through web user interface. Revision r85 Created wiki page through web user interface. Sep 23, 2009 UsingOmaha (Using Omaha once you've built it) Wiki page edited by ddor...@google.com - Revision r84 Edited wiki page through web user interface. Revision r84 Edited wiki page through web user interface. Sep 23, 2009 UsingOmaha (Using Omaha once you've built it) Wiki page added by ddor...@google.com - Revision r83 Created wiki page through web user interface. Revision r83 Created wiki page through web user interface. Sep 22, 2009 DeveloperSetupGuide (Instructions for how to set up a build environment for Omaha) Wiki page edited by ddor...@google.com - Revision r82 Edited wiki page through web user interface. Revision r82 Edited wiki page through web user interface. Sep 22, 2009 DeveloperSetupGuide (Instructions for how to set up a build environment for Omaha) Wiki page edited by ddor...@google.com - Revision r81 Added instructions for setting TestSource. Revision r81 Added instructions for setting TestSource. Sep 22, 2009 OmahaOverview (Brief overview of how Omaha works) Wiki page edited by ddor...@google.com - Revision r80 Made Overview page featured. Revision r80 Made Overview page featured. Sep 21, 2009 r79 (Update the timestamped test file.) committed by ddor...@google.com - Update the timestamped test file. Update the timestamped test file. Sep 15, 2009 issue 13 (ChromeSetup.exe fails with error code 0xc00ce56f) commented on by naesten - Ping. The same thing happens when I try to install gears here, too. Anything you'd like me to test? Ping. The same thing happens when I try to install gears here, too. Anything you'd like me to test? Sep 11, 2009 ServerProtocol (Protocol Omaha uses to communicate with the update server) Wiki page edited by ddor...@google.com - Revision r78 Edited wiki page through web user interface. Revision r78 Edited wiki page through web user interface. Aug 14, 2009 ServerProtocol (Protocol Omaha uses to communicate with the update server) Wiki page edited by mevis...@google.com - Revision r77 Updated ServerProtocol to correct image link. Revision r77 Updated ServerProtocol to correct image link. Aug 14, 2009 ServerProtocol (Protocol Omaha uses to communicate with the update server) Wiki page edited by mevis...@google.com - Revision r74 Added overview image to ServerProtocol Revision r74 Added overview image to ServerProtocol Aug 14, 2009 ServerProtocol (Protocol Omaha uses to communicate with the update server) Wiki page edited by mevis...@google.com - Revision r73 Edited wiki page through web user interface. Actual protocol documentation included. Revision r73 Edited wiki page through web user interface. Actual protocol documentation included. Aug 12, 2009 issue 15 (You should be able to (permanently) deinstall update checker) reported by fam....@live.nl - What steps will reproduce the problem? 1. Go to the control panel - add/remove programs 2. No Google Update Checker in it What is the expected output? What do you see instead? To be able to remove it on that way What version of the product are you using? On what operating system? OS: Vista SP2; Version: 1.2.183.7 Please provide any additional information below. What steps will reproduce the problem? 1. Go to the control panel - add/remove programs 2. No Google Update Checker in it What is the expected output? What do you see instead? To be able to remove it on that way What version of the product are you using? On what operating system? OS: Vista SP2; Version: 1.2.183.7 Please provide any additional information below. Jul 31, 2009 issue 14 (Proxy support) reported by shoelzer - My comments below pertain to GoogleUpdate.exe, not GoogleUpdater.exe (notice the "r"). Hopefully this is right place for this issue. What steps will reproduce the problem? 1. Install Google Chrome using the stand alone installer. Google Update is installed at the same time. Configure Chrome to use a proxy with the --proxy- server switch. 2. Browse the web and be happy. 3. Go to "About Google Chrome" and notice that a new version of Chrome is available. Click "Update". What is the expected output? What do you see instead? I expected the update to work, but it failed because Google Update does not use Chrome's proxy. Even worse, there is no way to specify a proxy for Google Update. Note that GoogleUpdater.exe (notice the "r") can be configured to use a proxy. GoogleUpdate.exe should also have that option. My comments below pertain to GoogleUpdate.exe, not GoogleUpdater.exe (notice the "r"). Hopefully this is right place for this issue. What steps will reproduce the problem? 1. Install Google Chrome using the stand alone installer. Google Update is installed at the same time. Configure Chrome to use a proxy with the --proxy- server switch. 2. Browse the web and be happy. 3. Go to "About Google Chrome" and notice that a new version of Chrome is available. Click "Update". What is the expected output? What do you see instead? I expected the update to work, but it failed because Google Update does not use Chrome's proxy. Even worse, there is no way to specify a proxy for Google Update. Note that GoogleUpdater.exe (notice the "r") can be configured to use a proxy. GoogleUpdate.exe should also have that option. Jul 29, 2009 OmahaOverview (Brief overview of how Omaha works) Wiki page edited by ddor...@google.com Jul 29, 2009 PageName Wiki page deleted by ddor...@google.com Jul 29, 2009 ClientUpdateProtocol (Design doc for the Client Update Protocol (CUP) used to secu...) Wiki page added by ddor...@google.com Jul 17, 2009 issue 13 (ChromeSetup.exe fails with error code 0xc00ce56f) commented on by naesten - Yeah, it looks like the "goopdate" DllMain fails on DLL_PROCESS_ATTACH for me. I finally realized the other day that another program was being launched, which helped me to get somewhere with it under OllyDbg ... Would be nice if it was more obvious what code was failing, and that it was open source and therefore possible to attempt reading! Yeah, it looks like the "goopdate" DllMain fails on DLL_PROCESS_ATTACH for me. I finally realized the other day that another program was being launched, which helped me to get somewhere with it under OllyDbg ... Would be nice if it was more obvious what code was failing, and that it was open source and therefore possible to attempt reading! Jul 17, 2009 issue 12 (GoogleUpdate.exe runs continuously after 14 days without an ...) commented on by ddor...@google.com - The workaround for AutoUpdateCheckPeriodMinutes > 14 days is to set to less than 14 days. Workaround options for update checks disabled (AutoUpdateCheckPeriodMinutes == 0) include: * Checking for updates once every 14 days. * Enabling update checks but setting the default update behavior to manual only. This has essentially the same effect in disabling automatic silent updates. * Update the LastChecked value in Software\Google\Update (in the HKLM and/or HKCU hive) to the current "Unix time". Note: If a user has disabled update checks, he or she may not have received the version that does not run continuously anyway. The workaround for AutoUpdateCheckPeriodMinutes > 14 days is to set to less than 14 days. Workaround options for update checks disabled (AutoUpdateCheckPeriodMinutes == 0) include: * Checking for updates once every 14 days. * Enabling update checks but setting the default update behavior to manual only. This has essentially the same effect in disabling automatic silent updates. * Update the LastChecked value in Software\Google\Update (in the HKLM and/or HKCU hive) to the current "Unix time". Note: If a user has disabled update checks, he or she may not have received the version that does not run continuously anyway. Jul 17, 2009 issue 13 (ChromeSetup.exe fails with error code 0xc00ce56f) commented on by ddor...@google.com - More information about this error code from http://msdn.microsoft.com/en- us/library/ms762295.aspx: XML_E_INVALIDSWITCH Switch from current encoding to specified encoding not supported. More information about this error code from http://msdn.microsoft.com/en- us/library/ms762295.aspx: XML_E_INVALIDSWITCH Switch from current encoding to specified encoding not supported. Jul 17, 2009 issue 13 (ChromeSetup.exe fails with error code 0xc00ce56f) reported by kuchhal@chromium.org - http://code.google.com/p/chromium/issues/detail?id=8513# A computer behind a NAT server (custom?) fails with this error code while trying to install Chrome. The error code looks like from Omaha. I don't think the actual Chrome installer is even getting launched. Can someone from Google Update team take a look? http://code.google.com/p/chromium/issues/detail?id=8513# A computer behind a NAT server (custom?) fails with this error code while trying to install Chrome. The error code looks like from Omaha. I don't think the actual Chrome installer is even getting launched. Can someone from Google Update team take a look? Jul 17, 2009 issue 12 (GoogleUpdate.exe runs continuously after 14 days without an ...) reported by ddor...@google.com - As part of the fallbacks to help ensure the new version of Omaha (1.2.183.7) is as reliable as when the core ran continuously, Omaha checks whether it has been more than 14 days since the last successful update check. If so, it falls back to running continuously as before. The problem is that it does not take into consideration that there may be a legitimate reason for not having a successful update check in the last 14 days. The legitimate reason is that a user or network administrator have set the AutoUpdateCheckPeriodMinutes Policy to > 14 days or 0 (update checks disabled). Reproduction Steps: 1. Install Omaha 2. Apply Group Policy to disable update checks using GoogleUpdate.adm in Group Policy Editor. 3. Move the clock ahead 15 days. 4. Run the core scheduled task Other variations: * Set the update check period to 20 days in step 2 instead of disabling updates checks. * Swap steps 1 and 2. Expected Result: The GoogleUpdate.exe /c process exits. As part of the fallbacks to help ensure the new version of Omaha (1.2.183.7) is as reliable as when the core ran continuously, Omaha checks whether it has been more than 14 days since the last successful update check. If so, it falls back to running continuously as before. The problem is that it does not take into consideration that there may be a legitimate reason for not having a successful update check in the last 14 days. The legitimate reason is that a user or network administrator have set the AutoUpdateCheckPeriodMinutes Policy to > 14 days or 0 (update checks disabled). Reproduction Steps: 1. Install Omaha 2. Apply Group Policy to disable update checks using GoogleUpdate.adm in Group Policy Editor. 3. Move the clock ahead 15 days. 4. Run the core scheduled task Other variations: * Set the update check period to 20 days in step 2 instead of disabling updates checks. * Swap steps 1 and 2. Expected Result: The GoogleUpdate.exe /c process exits. Jul 17, 2009 issue 11 (Crash - application failed to initialize properly (0xc000014...) commented on by ddor...@google.com - 0xc0000142 is STATUS_DLL_INIT_FAILED. I wonder if this is caused by the Task Scheduler, which is known to display errors in some cases when the task process fails. Omaha has code to avoid returning errors from these processes, but if goopdate.dll is the failing DLL, that code will never execute. 0xc0000142 is STATUS_DLL_INIT_FAILED. I wonder if this is caused by the Task Scheduler, which is known to display errors in some cases when the task process fails. Omaha has code to avoid returning errors from these processes, but if goopdate.dll is the failing DLL, that code will never execute. Jul 16, 2009 issue 11 (Crash - application failed to initialize properly (0xc000014...) reported by phajdan...@chromium.org - This is reporting http://crbug.com/15509 upstream. I frequently encounter this error on a Windows XP machine. An error dialog box pops up with title "GoogleUpdate.exe - ApplicationError" and message "The application failed to initialize properly (0xc0000142). Click on OK to terminate the application.". It seems to appear periodically, with frequency of ~2 hours (very approximate). The error disappeared after running Windows Update, so unfortunately I don't have a good reproduction case for now. But maybe you can extract something from this comment by dhw: I found this article from Microsoft that mentions error 0xc0000142 on XP; I don't know if it applies. The article mentions for console-based applications. I wonder if GoogleUpdate.exe is considered a console-based application? The article is: http://support.microsoft.com/kb/950312 In short, the article includes a hotfix for Winsrv.dll for XP SP2 and SP3 systems "that are experiencing this specific problem". This is reporting http://crbug.com/15509 upstream. I frequently encounter this error on a Windows XP machine. An error dialog box pops up with title "GoogleUpdate.exe - ApplicationError" and message "The application failed to initialize properly (0xc0000142). Click on OK to terminate the application.". It seems to appear periodically, with frequency of ~2 hours (very approximate). The error disappeared after running Windows Update, so unfortunately I don't have a good reproduction case for now. But maybe you can extract something from this comment by dhw: I found this article from Microsoft that mentions error 0xc0000142 on XP; I don't know if it applies. The article mentions for console-based applications. I wonder if GoogleUpdate.exe is considered a console-based application? The article is: http://support.microsoft.com/kb/950312 In short, the article includes a hotfix for Winsrv.dll for XP SP2 and SP3 systems "that are experiencing this specific problem". Jul 15, 2009 issue 7 (Needs a way to disable permanently, or get user consent befo...) commented on by ddor...@google.com - The issue of GoogleUpdate.exe running 24/7 has been addressed for most users. See Issue 2 . Update Engine is the open source name of the updater for Mac OS X. It should run on a schedule on Max OS X 10.5 and later. See http://www.google.com/support/installer/bin/answer.py?answer=155069. If you want to disable updates for one or more applications, see http://google- opensource.blogspot.com/2009/05/google-update-releases-update-controls.html. The issue of GoogleUpdate.exe running 24/7 has been addressed for most users. See Issue 2 . Update Engine is the open source name of the updater for Mac OS X. It should run on a schedule on Max OS X 10.5 and later. See http://www.google.com/support/installer/bin/answer.py?answer=155069. If you want to disable updates for one or more applications, see http://google- opensource.blogspot.com/2009/05/google-update-releases-update-controls.html. Jul 13, 2009 DeveloperSetupGuide (Instructions for how to set up a build environment for Omaha) Wiki page commented on by ddor...@google.com - The server is not open source. I've added some information about the protocol to the wiki: http://code.google.com/p/omaha/wiki/ServerProtocol. The server is not open source. I've added some information about the protocol to the wiki: http://code.google.com/p/omaha/wiki/ServerProtocol. Jul 13, 2009 ServerProtocol (Protocol Omaha uses to communicate with the update server) Wiki page edited by ddor...@google.com Jul 13, 2009 ServerProtocol (Protocol Omaha uses to communicate with the update server) Wiki page added by ddor...@google.com Jul 12, 2009 DeveloperSetupGuide (Instructions for how to set up a build environment for Omaha) Wiki page commented on by 2828628 - where is the server source code? where is the server source code? Jul 07, 2009 issue 2 (updater should run as a scheduled task and not as a service) changed by ddor...@google.com - As of version 1.2.183.7, Google Update uses the Task Scheduler instead of running all the time in most cases. See http://google-opensource.blogspot.com/2009/07/google-update-regularly- scheduled.html for the announcement and http://code.google.com/p/omaha/wiki/GoogleUpdateOnAScheduleOverview for an overview of the design. Status: Fixed Owner: gan...@google.com As of version 1.2.183.7, Google Update uses the Task Scheduler instead of running all the time in most cases. See http://google-opensource.blogspot.com/2009/07/google-update-regularly- scheduled.html for the announcement and http://code.google.com/p/omaha/wiki/GoogleUpdateOnAScheduleOverview for an overview of the design. Status: Fixed Owner: gan...@google.com Jul 07, 2009 issue 2 (updater should run as a scheduled task and not as a service) commented on by ddor...@google.com - Issue 6 has been merged into this issue. Issue 6 has been merged into this issue. Jul 07, 2009 issue 6 (Lacks option to "only update manually") changed by ddor...@google.com - Most of the discussion in this issue seems to be related to the long-running GoogleUpdate.exe, so I'm marking it as a duplicate of Issue 2 . Changing the interval of update checks and how specific apps are updated is addressed by the features described by http://google-opensource.blogspot.com/2009/05/google- update-releases-update- controls.html as mentioned above. Those features do not control how GoogleUpdate.exe runs. As of version 1.2.183.7, Google Update uses the Task Scheduler instead of running all the time in most cases. See http://code.google.com/p/omaha/wiki/GoogleUpdateOnAScheduleOverview. Status: Duplicate Most of the discussion in this issue seems to be related to the long-running GoogleUpdate.exe, so I'm marking it as a duplicate of Issue 2 . Changing the interval of update checks and how specific apps are updated is addressed by the features described by http://google-opensource.blogspot.com/2009/05/google- update-releases-update- controls.html as mentioned above. Those features do not control how GoogleUpdate.exe runs. As of version 1.2.183.7, Google Update uses the Task Scheduler instead of running all the time in most cases. See http://code.google.com/p/omaha/wiki/GoogleUpdateOnAScheduleOverview. Status: Duplicate

issue 11 (Crash - application failed to initialize properly (0xc000014...) reported by phajdan...@chromium.org - This is reporting http://crbug.com/15509 upstream. I frequently encounter this error on a Windows XP machine. An error dialog box pops up with title "GoogleUpdate.exe - ApplicationError" and message "The application failed to initialize properly (0xc0000142). Click on OK to terminate the application.". It seems to appear periodically, with frequency of ~2 hours (very approximate). The error disappeared after running Windows Update, so unfortunately I don't have a good reproduction case for now. But maybe you can extract something from this comment by dhw: I found this article from Microsoft that mentions error 0xc0000142 on XP; I don't know if it applies. The article mentions for console-based applications. I wonder if GoogleUpdate.exe is considered a console-based application? The article is: http://support.microsoft.com/kb/950312 In short, the article includes a hotfix for Winsrv.dll for XP SP2 and SP3 systems "that are experiencing this specific problem".

This is reporting http://crbug.com/15509 upstream. I frequently encounter this error on a Windows XP machine. An error dialog box pops up with title "GoogleUpdate.exe - ApplicationError" and message "The application failed to initialize properly (0xc0000142). Click on OK to terminate the application.". It seems to appear periodically, with frequency of ~2 hours (very approximate). The error disappeared after running Windows Update, so unfortunately I don't have a good reproduction case for now. But maybe you can extract something from this comment by dhw: I found this article from Microsoft that mentions error 0xc0000142 on XP; I don't know if it applies. The article mentions for console-based applications. I wonder if GoogleUpdate.exe is considered a console-based application? The article is: http://support.microsoft.com/kb/950312 In short, the article includes a hotfix for Winsrv.dll for XP SP2 and SP3 systems "that are experiencing this specific problem".

Last 7 days

Last 30 days

Earlier this year