Issue 114356 in chromium: Google Update Services (gupdate & gupdatem)

2,046 views
Skip to first unread message

chro...@googlecode.com

unread,
Feb 15, 2012, 8:15:38 AM2/15/12
to chromi...@chromium.org
Status: Unconfirmed
Owner: ----
Labels: Type-Bug Pri-2 Feature-Enterprise

New issue 114356 by riede...@gmail.com: Google Update Services (gupdate &
gupdatem)
http://code.google.com/p/chromium/issues/detail?id=114356

Version of Google Chrome (Wrench-> About Google Chrome): first try with
16.0.912.75 but also reproduced with 17.0.963.46
Version of MSI (if applicable):
Using group policy settings? Yes/No

When installing Chrome with the "GoogleChromeStandaloneEnterprise.msi"
setup, wether over GPOs or by manual installation, after the install is
complete there are two Google Update Services (gupdate & gupdatem)
installed under the Windows services.

The gupdate is linked to %PROGRAMFILES%\Google\Update\GoogleUpdate.exe /svc
The gupdatem is linked to %PROGRAMFILES%\Google\Update\GoogleUpdate.exe
/medsvc

Every time after I click on Wrench-> About Google Chrome I find the
following log entries from both services in the Windows eventlog:


Log Name: Application
Source: gupdate
Date: 2/15/2012 11:06:00 AM
Event ID: 0
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: TEST-PC
Description:
The description for Event ID 0 from source gupdate cannot be found. Either
the component that raises this event is not installed on your local
computer or the installation is corrupted. You can install or repair the
component on the local computer.

If the event originated on another computer, the display information had to
be saved with the event.

The following information was included with the event:

Service started

The same behavior I recognize also when I install Chrome with
the "ChromeStandaloneSetup.exe" setup.

My question now is, for what purpose are these two services? I thought that
the scheduled tasks "GoogleUpdateTaskMachineCore"
and "GoogleUpdateTaskMachineUA" are for the periodic update process.

chro...@googlecode.com

unread,
Feb 16, 2012, 4:24:04 AM2/16/12
to chromi...@chromium.org

Comment #3 on issue 114356 by riede...@gmail.com: Google Update Services

Ok, sounds convincing. But how does it come, that the two serivces don't
get installed when I used the Chrome consumer edition? And Chrome is
updating properly with the two scheduled tasks?

chro...@googlecode.com

unread,
Jun 23, 2012, 7:05:43 PM6/23/12
to chromi...@chromium.org

Comment #6 on issue 114356 by peterr...@gmail.com: Google Update Services
Status is "WontFix"? Seems like someone didn't code this correctly. There
should never be an event description "not found". Please refer to
Microsoft documentation
(http://msdn.microsoft.com/en-us/library/ff664639(v=PandP.50).aspx) or read
this:
http://www.eventlogblog.com/blog/2008/04/event-log-message-files-the-de.html

... "The description for Event ID ( 50 ) in Source ( SomeService ) cannot
be found.". The Windows Event Viewer logs this message for one of the
following reasons:

* No message file is registered for the source (e.g. SomeService)
* The registered message file does not exist or cannot be accessed
* The specified event id is not included in the message file


chro...@googlecode.com

unread,
Jun 25, 2012, 4:56:22 PM6/25/12
to chromi...@chromium.org

Comment #7 on issue 114356 by ryan...@google.com: Google Update Services
It's a side effect of Google Update using the XP-era Windows Event Log
code. (This is an intentional choice; the Crimson log APIs has a tendency
to hold an open handle on the DLL containing the message resources, which
complicates self-updates.)

If you scroll down in the error message, it'll have the text message. It's
purely a cosmetic issue.

Reply all
Reply to author
Forward
0 new messages