This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Garmin Connect and Forerunner 205

Former Member
Former Member
Hi there,

I use a Forerunner 205 for running and orienteering and, until about a month ago, was happily using Motion Based to analyse my runs.

I "upgraded" to Garmin Connect in mid-July and have experienced several problems since. I'm not sure whether these are on the Garmin Connect side or on the Forerunner side.

I'm going to list my problems below and if any of you have any advice for me I would be extremely grateful.

1. When I try to log in I get an "Internal Server Error" message.
2. I tried to upload the Garmin Communicator a second time (just to be sure my connection problems weren't caused by that) and even though I'd closed my web browser I kept on getting an error message saying the browser was open.
3. When I do log in successfully, I'm told the firmware on my 205 needs updating. If I do that will I lose all the information on it?
4. Uploading is often incomplete.
5. There are over 70 runs saved on the watch at this stage, how do I delete them and create more space on the watch?
6. I cannot save to my user account. The last race I saved I ran on 31st July. When I try to save, I get an internal server error.
7. It is not clear from the website how to save a race.


Thanks,

Sarah Ni Ruairc
  • kept on getting an error message saying the browser was open.


    Are you using IE and Windows? If so, when you get that message press control+shift+esc to open the task manger. On the processes tab right click on iexpore.exe and select end process tree. Then continue with the installation of communicator

    3. When I do log in successfully, I'm told the firmware on my 205 needs updating. If I do that will I lose all the information on it?


    No.

    5. There are over 70 runs saved on the watch at this stage


    This is probably the crux of most of your problems. If you've saved all of these activities to Training Center or Garmin Connect or MB, then you can delete all history by going to History> Running> Delete> Delete All> Yes
  • Former Member
    0 Former Member over 15 years ago
    Garmin Connect and Forerunner 205

    Hello all,

    Many thanks for replying to my post below.

    I tried some of the tips listed below, installed the newest version of the Communicator and updated the firmware, just to be sure to be sure.

    I'm still having difficulty signing in.

    I get the following error message when I try to sign in:

    HTTP Status 500 -

    --------------------------------------------------------------------------------

    type Exception report

    message

    description The server encountered an internal error () that prevented it from fulfilling this request.

    exception

    javax.faces.application.ViewExpiredException: viewId:/page/user/signin.faces - View /page/user/signin.faces could not be restored.
    com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:187)
    com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251)
    com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117)
    javax.faces.webapp.FacesServlet.service(FacesServlet.java:244)
    org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
    org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
    org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:390)
    org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:517)
    org.tuckey.web.filters.urlrewrite.NormalRewrittenUrl.doRewrite(NormalRewrittenUrl.java:195)
    org.tuckey.web.filters.urlrewrite.RuleChain.handleRewrite(RuleChain.java:159)
    org.tuckey.web.filters.urlrewrite.RuleChain.doRules(RuleChain.java:141)
    org.tuckey.web.filters.urlrewrite.UrlRewriter.processRequest(UrlRewriter.java:90)
    org.tuckey.web.filters.urlrewrite.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:406)
    com.garmin.connect.filter.UTF8Filter.doFilter(UTF8Filter.java:21)
    org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)


    note The full stack trace of the root cause is available in the JBossWeb/2.0.0.GA logs.

    How can this be resolved? It appears to be a server problem rather than a watch problem.

    I was advised to delete some of the runs from the watch to ease uploading by going to History>Running>Delete>Delete All>Yes. Where is the "History" command/drop down menu?

    Thanks,

    Sarah