cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

10365
Views
10
Helpful
12
Replies

Webex failed to connect to server

Hi all,

 

I have a long running issue trying to log into webex (teams) on my pc, my colleagues pcs are fine. The error presents itself as the message "failed to connect to the server. sorry about that" however the problem is not one of network connectivity. Examining the logs I see the following message when connectivity is successful on other pcs and the subsequent message upon failure on mine. Does anyone have any clue as to what the underlying problem could be? 

 

success

2021-02-04T06:51:22.203Z <Info> [9372] LifecycleManager.cpp:225 LifecycleManager::attemptToLoginWithCachedUser:[Login] Attempting to login based on previously logged in credentials.
2021-02-04T06:51:22.204Z <Debug> [9372] LifecycleManager.cpp:232 LifecycleManager::attemptToLoginWithCachedUser::<lambda_9d327e99e37f871ef3f63dbcf08aa861>::operator ():[Login] Found user configuration location.
 
failure
2021-02-04T06:57:11.384Z <Info> [9240] LifecycleManager.cpp:225 LifecycleManager::attemptToLoginWithCachedUser:[Login] Attempting to login based on previously logged in credentials.
2021-02-04T06:57:11.385Z <Debug> [9240] LifecycleManager.cpp:329 LifecycleManager::attemptToLoginWithCachedUser::<lambda_9d327e99e37f871ef3f63dbcf08aa861>::operator ():[Login] Could not find previous user in the shared database.
12 REPLIES 12
Fritz_H
Rising star

@christopher.green 

some quick ideas...

* Did you try to log off from the Webex-Client and log on again?  (not just quit and restart the application)
* Does logon work on the Web-Interface (web.webex.com)?
* You may try to reset the local database of the Webex-Client (Help > Health Checker > Reset Database)

 

Hi and thank you for your responses.
Yes, I've tried the log off.
The web interface works fine.
I can't get beyond the login screen so the help option is not available to me.

@christopher.green 

Thanks for your quick response.

Since the Web-Interface does work, we may consider your Webex-Account as "OK".

next guess:
perhaps the local Client-Application is broken.
Since all data (Chat-History, Content, Teams, Spaces etc..) is stored in the Cisco-Cloud I do not see much risk in un-installing and re-installing the Client-Application.  (by default no admin-privileges required)
Perhaps you may want to check/note/memorize your Client settings first (notification-settings, A/V-settings etc.. ) since they are not stored in the cloud (AFAIK).

Thank you Fritz, I have tried re installing the client app many times and the problem persists.

@christopher.green 

Last idea...just to make sure:
some forum-members suggest to remove and install the client-software - not just run the installer again while the Client still is installed.

Thank you Fritz, I have done this and sadly I get the same error

did you ever manage to fix this @chriss 

 

i have the same problem.

No I didn't sadly, I have to depend on the web version which is quite limited in functionality.

@chr 

 

just worked with tac and we fixed it

 

open your cmd (with admin privilege) - and then run the command below and then give it some time - shut the app and try again

 

fixed my issue - all the best

 

netsh winhttp reset proxy

 

basically some proxy info. cached is the issue.

@christopher.green  let me know how you go with the below fix.

 

just worked with tac and we fixed it

 

open your cmd (with admin privilege) - and then run the command below and then give it some time - shut the app and try again

 

fixed my issue - all the best

 

netsh winhttp reset proxy

 

basically some proxy info. cached is the issue.