Bookmark this page:
- website--mygarmin--mysupport-errors
- 05-15-2008
If you were Registered and logged in, you could reply and use other advanced thread options
is it just me... or has the Garmin website been down for maint
or having errors when trying to display info from the MyGarmin section ?
I've tried to display the email/message section - mysupport -
and when I try to display any of the "answered" questions,
this is what I get in the window....
HTTP Status 500 -
--------------------------------------------------------------------------------
type Exception report
message
description The server encountered an internal error () that prevented it
from fulfilling this request.
exception
org.apache.jasper.JasperException: Unable to compile class for JSP
An error occurred at line: 28 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserLanguage cannot be resolved
An error occurred at line: 28 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserCountry cannot be resolved
An error occurred at line: 39 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserLanguage cannot be resolved
An error occurred at line: 39 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserCountry cannot be resolved
An error occurred at line: 51 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserLanguage cannot be resolved
An error occurred at line: 51 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserCountry cannot be resolved
An error occurred at line: 52 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserLanguage cannot be resolved
An error occurred at line: 52 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserCountry cannot be resolved
An error occurred at line: 56 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserLanguage cannot be resolved
An error occurred at line: 56 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserCountry cannot be resolved
An error occurred at line: 57 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserLanguage cannot be resolved
An error occurred at line: 57 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserCountry cannot be resolved
An error occurred at line: 61 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserLanguage cannot be resolved
An error occurred at line: 61 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserCountry cannot be resolved
An error occurred at line: 69 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserLanguage cannot be resolved
An error occurred at line: 69 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserCountry cannot be resolved
An error occurred at line: 150 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserLanguage cannot be resolved
An error occurred at line: 150 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserCountry cannot be resolved
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:510)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:375)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
com.garmin.iq.security.GarminSecurityFilter.doFilter(GarminSecurityFilter.java:86)
com.silknet.ebiz.silkrequest.server.gateway.SetCharacterEncodingFilter.doFilter(Unknown
Source)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
root cause
org.apache.jasper.JasperException: Unable to compile class for JSP
An error occurred at line: 28 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserLanguage cannot be resolved
An error occurred at line: 28 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserCountry cannot be resolved
An error occurred at line: 39 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserLanguage cannot be resolved
An error occurred at line: 39 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserCountry cannot be resolved
An error occurred at line: 51 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserLanguage cannot be resolved
An error occurred at line: 51 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserCountry cannot be resolved
An error occurred at line: 52 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserLanguage cannot be resolved
An error occurred at line: 52 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserCountry cannot be resolved
An error occurred at line: 56 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserLanguage cannot be resolved
An error occurred at line: 56 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserCountry cannot be resolved
An error occurred at line: 57 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserLanguage cannot be resolved
An error occurred at line: 57 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserCountry cannot be resolved
An error occurred at line: 61 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserLanguage cannot be resolved
An error occurred at line: 61 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserCountry cannot be resolved
An error occurred at line: 69 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserLanguage cannot be resolved
An error occurred at line: 69 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserCountry cannot be resolved
An error occurred at line: 150 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserLanguage cannot be resolved
An error occurred at line: 150 in the jsp file:
/KODSelfService/contactsLog.jsp
Generated servlet error:
browserCountry cannot be resolved
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:84)
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:328)
org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:414)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:297)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:276)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:264)
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:563)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:303)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
com.garmin.iq.security.GarminSecurityFilter.doFilter(GarminSecurityFilter.java:86)
com.silknet.ebiz.silkrequest.server.gateway.SetCharacterEncodingFilter.doFilter(Unknown
Source)
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
note The full stack trace of the root cause is available in the Apache
Tomcat/5.5.17 logs.
--------------------------------------------------------------------------------
Apache Tomcat/5.5.17
.
--
----------------------------------
"If everything seems to be going well,
you have obviously overlooked something." - Steven Wright
They are in the process of upgrading I think. At least that's what the
page said last night when I tried to register my Nuvi 760.
"ICU812" wrote
They've been in the process for at least a week... I've been checking it
daily including just now.
> "ICU812" =A0 wrote
> They've been in the process for at least a week... I've been checking it
> daily including just now.
> They've been in the process for at least a week... I've been checking it
> daily including just now.
They put a 2 Gig download for the CNNA 2009 NT update that is bound
to be extremely popular on their web site, offered as the only
alternative a DVD which they will ship in the record time of 4 to 6
weeks for a hefty shipping and handling charge of $10 (which cynical
me thinks they did to push people toward the download), and if that
weren=92t enough, they put a 30-day expiration on the download so that
even if someone didn=92t care about getting it immediately, Garmin
created a sense of urgency about getting it. Apparently, they vastly
underestimated the demand this would place on their web site and now
it's all but shut down. They have some real geniuses making decisions.
>> "ICU812" wrote
>> They've been in the process for at least a week... I've been checking it
>> daily including just now.
>> They've been in the process for at least a week... I've been checking it
>> daily including just now.
> They put a 2 Gig download for the CNNA 2009 NT update that is bound
> to be extremely popular on their web site, offered as the only
> alternative a DVD which they will ship in the record time of 4 to 6
> weeks for a hefty shipping and handling charge of $10 (which cynical
> me thinks they did to push people toward the download), and if that
> weren’t enough, they put a 30-day expiration on the download so that
> even if someone didn’t care about getting it immediately, Garmin
> created a sense of urgency about getting it. Apparently, they vastly
> underestimated the demand this would place on their web site and now
> it's all but shut down. They have some real geniuses making decisions.
> to be extremely popular on their web site, offered as the only
> alternative a DVD which they will ship in the record time of 4 to 6
> weeks for a hefty shipping and handling charge of $10 (which cynical
> me thinks they did to push people toward the download), and if that
> weren’t enough, they put a 30-day expiration on the download so that
> even if someone didn’t care about getting it immediately, Garmin
> created a sense of urgency about getting it. Apparently, they vastly
> underestimated the demand this would place on their web site and now
> it's all but shut down. They have some real geniuses making decisions.
Just checked Garmin and it said "site upgrades in progress". I guess the
rush they created crashed the map update site.
It looks like the trend these days for companies is to let excessive greed
jump ahead of customer service.
MR
- Webupdater vs myGarmin dashboard
- Garmin GPS
- 2010-02-10
- Sample Map on Garmin website?
- Garmin GPS
- 2010-11-04
- Mygarmin site borked?
- Garmin GPS
- 2008-02-21
- Nuvi map errors, how fixed?
- Garmin GPS
- 2007-06-02
- Garmin website
- Garmin GPS
- 2008-06-16
- Help with sound after updating roadmate 700 to version 3.32 for Magellan's website
- Magellan GPS
- 2008-03-21
- GPS website
- Geographic Information Systems (GIS)
- 2007-06-05
> page said last night when I tried to register my Nuvi 760.