cancel
Showing results for 
Search instead for 
Did you mean: 
New Contributor

Re: GTM Error - "Technical Difficulties"

Calling in for support is likely to be inefficient, since I am hard of hearing.  (I question GoToMeeting's decision to eliminate e-mail or chat support.) I will communicate your recommendations to our IT group, and hope they can figure things out.

New Contributor

Re: GTM Error - "Technical Difficulties"

It's going to be under LogMeIn and GoToMeeting.
New Contributor

Re: GTM Error - "Technical Difficulties"

Those folders did not appear anywhere. But I did a search for both strings under the AppData folder.  I only found files related to the Outlook plugin, some log files, and some authentication tokens, and I deleted all I could.  Then tried reinstalling.  No change.

New Contributor

Re: GTM Error - "Technical Difficulties"

I tried posting some log file contents here, but for some reason the posts are not showing up. Here is the end of one: 

2019-02-19 11:46:40.975 PST i: [g2mcomm] <Main> Creating process: "...\g2mlauncher.exe" "StartID={71093914-3379-4173-B8F4-0424A58E6B9A}&Debug=Off&Stat=On&StatDb=On&Index=0"
2019-02-19 11:47:25.988 PST E: [g2mcomm] <Main> Error at , commagentapp.cpp:494
(2024) "ECError::eTimeout"
"g2mlauncher.exe" process did not respond within 45 seconds.
Error returned at , ipcpluginhost.cpp:198
Error returned at , pluginprovider.cpp:61
Error returned at , commagentapp.cpp:138

New Contributor

Re: GTM Error - "Technical Difficulties"

And here is another:

2019-02-19 11:44:19.433 PST i: [g2mstart.exe] <Loader> Microsoft Windows 10 Professional x64 Edition (Build 17134)
2019-02-19 11:44:19.437 PST d: [g2mstart.exe] <Loader> Created event COMM_AGENT_EXIT_OK_2840
2019-02-19 11:44:19.441 PST d: [g2mstart.exe] <Loader> Created event G2M_Launcher_Shut_Down_2840
2019-02-19 11:44:19.445 PST d: [g2mstart.exe] <Loader> Created event g2m_2840
2019-02-19 11:44:19.456 PST d: [g2mstart.exe] <LogManager> CLoaderLogManager::run() - less than 10 log directories exist. No management needed.
2019-02-19 11:44:19.495 PST d: [g2mstart.exe] <Watcher> ResetableThread::run() - ready event signaled.
2019-02-19 11:44:19.500 PST d: [g2mstart.exe] <Watcher> CLoaderWatchdog::waitOnProcess() - waiting for the Comm Agent to exit (pid=2376)
2019-02-19 11:44:20.800 PST i: [g2mstart.exe] <RegMonitor> Registry change detected.
2019-02-19 11:45:06.159 PST d: [g2mstart.exe] <Watcher> The Comm Agent Exit event was not signaled.
2019-02-19 11:45:06.159 PST W: [g2mstart.exe] <Loader> The Comm Agent exited with code [0x7E8]
2019-02-19 11:45:06.159 PST i: [g2mstart.exe] <Loader> Attempting to reload the Comm Agent and Initial Plug-in.
2019-02-19 11:45:06.165 PST d: [g2mstart.exe] <Watcher> ResetableThread::run() - ready event signaled.
2019-02-19 11:45:06.165 PST d: [g2mstart.exe] <Watcher> CLoaderWatchdog::waitOnProcess() - waiting for the Comm Agent to exit (pid=14744)
2019-02-19 11:45:52.822 PST d: [g2mstart.exe] <Watcher> The Comm Agent Exit event was not signaled.
2019-02-19 11:45:52.822 PST W: [g2mstart.exe] <Loader> The Comm Agent exited with code [0x7E8]
2019-02-19 11:45:52.823 PST i: [g2mstart.exe] <Loader> Attempting to reload the Comm Agent and Initial Plug-in.
2019-02-19 11:45:52.828 PST d: [g2mstart.exe] <Watcher> ResetableThread::run() - ready event signaled.
2019-02-19 11:45:52.829 PST d: [g2mstart.exe] <Watcher> CLoaderWatchdog::waitOnProcess() - waiting for the Comm Agent to exit (pid=256)
2019-02-19 11:46:39.466 PST d: [g2mstart.exe] <Watcher> The Comm Agent Exit event was not signaled.
2019-02-19 11:46:39.466 PST W: [g2mstart.exe] <Loader> The Comm Agent exited with code [0x7E8]
2019-02-19 11:46:39.466 PST i: [g2mstart.exe] <Loader> Attempting to reload the Comm Agent and Initial Plug-in.
2019-02-19 11:46:39.472 PST d: [g2mstart.exe] <Watcher> ResetableThread::run() - ready event signaled.
2019-02-19 11:46:39.472 PST d: [g2mstart.exe] <Watcher> CLoaderWatchdog::waitOnProcess() - waiting for the Comm Agent to exit (pid=20468)
2019-02-19 11:47:26.127 PST d: [g2mstart.exe] <Watcher> The Comm Agent Exit event was not signaled.
2019-02-19 11:47:26.128 PST W: [g2mstart.exe] <Loader> The Comm Agent exited with code [0x7E8]
2019-02-19 11:47:26.128 PST d: [g2mstart.exe] <Loader> Exit error default case (2024).
2019-02-19 11:47:26.128 PST E: [g2mstart.exe] <Loader> Exiting with errors - failed to run GoToMeeting.
2019-02-19 11:47:31.010 PST i: [g2mstart.exe] <Loader> Loader complete... exiting
2019-02-19 11:47:31.010 PST d: [g2mstart.exe] <RegMonitor> signalStop detected.

LogMeIn Manager

Re: GTM Error - "Technical Difficulties"

Hi @rjonessoar 

 

Thank you for providing the log file details. In my experience, the (2024) "ECError::eTimeout" message in the beginning typically points towards a network issue. I would suggest having your IT try running our Connection Wizard on your PC as a test, it may give them a clue as to where the issue is happening.

 

Glenn is a member of the LogMeIn Community Care Team.

Was your question answered? Please mark it as an Accepted Solution.
Was a post helpful or informative? Give it a Kudo!
New Contributor

Re: GTM Error - "Technical Difficulties"

Thanks for the suggestion.  I downloaded the Connection Wizard and ran it.  It said it "found connection settings" but when I tried to start a meeting it still failed.

 

Is there somebody I can send the G2MWizardReport.zip file to for diagnosis?  I can send it to my IT group, as well.

LogMeIn Manager

Re: GTM Error - "Technical Difficulties"

I will PM you an email address.
Glenn is a member of the LogMeIn Community Care Team.

Was your question answered? Please mark it as an Accepted Solution.
Was a post helpful or informative? Give it a Kudo!
New Contributor

Re: GTM Error - "Technical Difficulties"

Were you able to resolve the issue? I've been experiencing the same issue since the update to Win10 1809.

New Contributor

Re: GTM Error - "Technical Difficulties"

Thanks you @GlennD , I emailed the ZIP file to the address you sent me.