Jump to content


  • Posts

  • Joined

  • Last visited

Posts posted by LQ

  1. The logs still post to your account despite the error. I discovered that when I ended up triple logging a cache.

    Yes noticed that too finally. I didn't settle for three... :laughing: But any TB:s that you try to drop remain in your hands.



    Not able to log caches thru the wap site.


    Edit: noticed that the log actually succeeded despite the error messag, BUT selected travelbugs remained "in my hands".



    Server Error in '/' Application.



    The queue does not exist or you do not have sufficient permissions to perform the operation.

    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.


    Exception Details: System.Messaging.MessageQueueException: The queue does not exist or you do not have sufficient permissions to perform the operation.


    Source Error:


    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.


    Stack Trace:


    [MessageQueueException (0x80004005): The queue does not exist or you do not have sufficient permissions to perform the operation.]

    System.Messaging.MQCacheableInfo.get_WriteHandle() +204

    System.Messaging.MessageQueue.StaleSafeSendMessage(MQPROPS properties, IntPtr transaction) +96

    System.Messaging.MessageQueue.SendInternal(Object obj, MessageQueueTransaction internalTransaction, MessageQueueTransactionType transactionType) +310

    System.Messaging.MessageQueue.Send(Object obj, String label, MessageQueueTransaction transaction, MessageQueueTransactionType transactionType) +122

    System.Messaging.MessageQueue.Send(Object obj, String label) +12

    Groundspeak.Web.Messaging.MessageCenter.SendToMessageQueue(WptLog& Log) +198

    Groundspeak.Web.GPX.WptLog.Create(SimpleUser UserInfo, Guid LogGUID, ObjWpt WptRef, DateTime LogDate, WptLogType Type, String Note, Boolean IsEncrypted, Boolean OwnerCannotDelete, ObjWpt[] ObjWpt, Int32 DataSource, Double Latitude, Double Longitude) +1565

    geocaching_wap.UI.DefaultPage.CreateNewLog(Boolean CheckConfirm) +1323

    geocaching_wap.UI.DefaultPage.cmdLogWptSubmit_Click(Object sender, EventArgs e) +83

    System.Web.UI.MobileControls.Command.OnClick(EventArgs e) +109

    System.Web.UI.MobileControls.Command.RaisePostBackEvent(String argument) +82

    System.Web.UI.MobileControls.Command.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +4

    System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +13

    System.Web.UI.MobileControls.MobilePage.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +75

    System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +36

    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1565




    Version Information: Microsoft .NET Framework Version:2.0.50727.3082; ASP.NET Version:2.0.50727.3082

  3. Does anybody get Application Error whentrying to log in? I have tried the last two days and am getting a runtime exception.


    Haven't tried this lately, but have you tried:


    As a workaround I found out that I actually am logged in after the Vievstate Error, if I go back to wap.geocaching.com via a bookmark!


    If I try to look at a travelbug (or coin) thru a cache listing I'll get a Viewstate Error for which I haven't fond any workaround.


    Would be nice to get this fixed someday.

  4. By default it sorts by name. Other options are last log and distance.


    What I would like to have is chronological overview of trackable item activity for this cache. The sort by last log option shows the items ordered by there last log, which can or will put items at the top of the list, while they haven't been in the applicable cache for months/years.


    I support this idea!


    Another interesting sort option would be by distance from your home coordinates, not so useful for trackables by cache but interesting if you are trying to locate spesific icons. For example:


    (Here sort by last log does a good job, but this was only an example.)

  5. I'm sorry for the delay in responding. I did not mean to keep you waiting.


    We're aware of this issue and consider it a bug. I'm not sure when or why this change was implemented but we have been making a lot of changes to the way we handle emails recently. I will make sure this is hotfixed if possible, or included in the next release.

    Thank you for acknowledging this.


    As I said here this was 'broken' before Release 7/28/09, which according to my test fixed the issue. Exactly when it was broken again after that I don't know.



    Cache/Traveller owner gets a server error after deleting a log and the log owner doesn't get any notification, but the log IS deleted, or shoud I say archived.

  6. First of all: I tried to find an answer to this question by searching the forum. This was not possible due to the fact that all of the words that I sought for had to have at least 5 characters. Sigh!


    I usually log my caches in the same order that I found them. But when I look at the page All Geocaches By Username, they appear in another order. When I first joined Groundspeak they appeared in correct order but this has changed. Why? Is it a bug? Is it reported? Is a fix expected in a near future?


    Regards, The Strat


    I think there has to be a few threads on this subject, but apparently it doesn't get any priority from TPTB. Especially caches found within the same day are mostly listed in completely opposite order as logged, but sometimes this isn't consistent either.

    Your best bet for the right order would be here: http://www.geocaching.com/my/logs.aspx?s=1


    I also think that third party tools such as GSAK can produce the right order, provided that you logged in right order naturally. (Every log has it own increasing LUID number and those shold be available in a my finds pq.)

  7. IMO a cache is placed, when you place the "box". So if you can't trust the owner, then there's no way to tell for sure. The publish log tells when the cache was published give or take one day as it's forced to Groundspeak (Seattle) time zone. If you really need to know when a cache was published, you have to look at the timestamp in your publish notification email.


    I don't think this is a major issue, even if I don't like some usres habit to delete 'archive' and 'coordinate update' logs either.


    BTW before summer 2005 publishing a cache didn't generate any visible log.

  8. Lisätään nyt tännekin että sekä YSA että Wikipedia, johon YSA:n ylläpitäjä vetosi, ovat tältä osin korjattuja vastaamaan harrastajien piirissä vallitsevaa de facto käytäntöä.


    Googlen lukemat tällä hetkellä:

    geokätköily 26200

    g. kätkentä 2290


    Mutta tässä vielä yksi "hoidettava" asia: "Kielitoimiston sanakirjan uusin versio 2.0 - 18.2.2008 tuntee vain muodon qeokätkentä eikä lainkaan geokätköilyä"

  9. Mielenkiintoista, tästä:


    löytyy viiteluettelosta täälläinen kohta:

    Groundspeak forumin keskustelupalsta, (geokätkentä sanan suomenkielinen merkitys ja
    käyttötarkoitus) http://forums.Groundspeak.com/GC/index.php?showtopic=38990.

    Vuonna miekka ja kypärä tuolla termillä oli ehkä oma kannattajakuntansa ja oliskin ollut mielenkiintoista katsoa mitä silloin on keskusteltu. Mutta kyseinen linkki veikin jonnekin uusselantilaiselle osiolle jolla ei ole mitään tekemistä asian kanssa.


  10. As you can see from a separate thread. This very annoying (the part that the owner isn't notified) bug has surfaced again!


    July 09 Geocaching.com Code Release



    11232: Deletion of log on geocoin causing server error

    Fixed issue where attempting to delete a geocoin log results in a server error


    Noticed this behavior for cache logs, "attempting to delete" is a bit missleading

    the log actually got deleted, but the far more severe issue was that the owner of the

    deleted log never got any email notification about it!


    Verified that it works (for cache logs) again. Thanks for the fix.

  11. July 09 Geocaching.com Code Release



    11232: Deletion of log on geocoin causing server error

    Fixed issue where attempting to delete a geocoin log results in a server error


    Noticed this behavior for cache logs, "attempting to delete" is a bit missleading

    the log actually got deleted, but the far more severe issue was that the owner of the

    deleted log never got any email notification about it!


    Verified that it works (for cache logs) again. Thanks for the fix.

  12. Someone any idea how long it will take to get to WECA?

    GC1TF00 to GC1VF00 took about 28 days. So GC1VF00 to GC1WF00 will take about the same, and GC1WECA will go about an hour before. I'm going to guess 28th July, plus or minus a couple of days. But you'll need to be camped out in front on your PC.


    So, did you get it?


    28th July, was a reasonably well educated guess. Now it seems that "your" code was reserved 22 +/- 2 hours ago.


    And if you didn't get it, there still is litle hope. BUT you have to find out who reserved the code and convince them to adopt that cache description to you. (Naturally before it gets published, so there's a "slight" problem to get in touch with the current owner.)

  13. ... I was in Helsinki the last weekend. There i found a TB without a description of its Goal. Im new in Geocaching and i didn't know that it is possible that the Goal of a TB is only described on the Internetsite...


    It is possible, but in my opinion the TB owner shouldn't assume that you have/use internet access 'in the field'. I rarely check the web when I'm traveling.


    Is it this TB:

    !!!!!what i´m doing now in germany? someone is stupid? :-( can somebody please take me again back to finland? thank you

    If someone is stupid, I vote for the TB owner writing such into the TB description for a bug without the goal written on something robust attached to the bug itself.


    But, anyway I can act as your proxy here in Helsinki if you want to mail the TB. Just send an email thru the link on my profile page to sort out the details.

  14. Probably yes, but first you have to define what you mean by that...


    A pure 'finds per time unit' approach isn't very useful, as recently published caches with a lot of finds on the first day would keep populating the top of that list... Some reasonable minimum age of the candidates would be preferable.


    (Disclaimer: I don't have means (necessary input data in some handy format) to produce such a list.)

  15. The problem is simply that the 'second bratwurst' has been allowed to register essentialy the same username. At that time the usernames apparently have been CaSe SeNsItIvE. (Now you simply can't register the user name 'LQ', because 'lq' is already taken by me.)


    All these links returns my finds:


    ...and I guess, that would be the case even if someone had managed to get any of the other comnbinations registered. (Fortunately you can always see your own logs thru http://www.geocaching.com/my/logs.aspx?s=1 when logged in.


    It's even possible that the 'second bratwurst' isn't even capable to log in before the username is changed to something else, that isn't in conflict with any other username.


    But yes, emailing contact@... is probably the best way to go.


    Note that occasionally, a username turns out to be unsuitable for a variety of reasons. Should this happen, we will ask you to choose a new username; we also reserve the right to change usernames ourselves when necessary.

  16. Kuvittelen tietäväni mistä kätköstä tämä lanka on lähtenyt liikkeelle. Siinä ainakin kuvauksessa mainitaan mikä on tilanne ja että kätköilijät voivat käydä tai olla käymättä kätköllä oman harkintansa mukaan. Kun kävin paikan päällä illalla, niin ketään ei näkynyt missään, eikä nollapisteen lähellä ollut mitään varsinaista työmaata. Niin, ja mitään aitaa tms. ei tarvinnut ylittää/alittaa(/mennä läpi :( ).


    Lisäksi tulee mieleen pari suht tuoretta kätköä eräällä "työmaalla", jossa käynti voi tuntua hieman kyseenalaiselta, mutta en näe syytä niittenkään arkistointiin. Aika varmaan hoitaa sen ennemmin tai myöhemmin kuitenkin.


    Mutta, minähän olenkin niin rikollinen että saatan kävellä päin punaisia valoja, kun risteävää liikennettä ei näy. (Autolla päin punaisia ajaminen ei tulisi mieleenkään.)

  17. Kyllä särähtää...




    Geokätkentä, kyllä kalskahtaa korvaan. Ei tämä ole pelkkää piilottamista.


    Geocaching = Geokätköilyä

    Geocacher = Geokätköilijä


    Täytyy kompata ja täysillä. Toivottavasti jatkossa perusterminologia on väitöskirjassa oikein.


    Vahva "me too" munkin puolesta tähän.


    Viite 1. Huomaa että tuon jälkeen sekä Wikipedia että asiasanaluetteloa on korjattu!

    Hakutulos: (YSA)

    Asiasanaa geokätkentä ei käytetä.

    Käytettävä asiasana: geokätköily

    Huomautus: Ulkoiluharrastus, jossa piilotetaan ja etsitään geokätköiksi kutsuttuja rasioita GPS-paikantamislaitteen avulla

    Korvaa termit: geokätkentä

    Kuuluu ryhmiin: [98] Vapaa-aika. Harrastukset. Matkailu. Käsityöt

    Ruotsinkielinen asiasana: geocaching


    Geokätkentä on vähän niinkuin kätköilyn alkuaikoina käytetty englanninkielinen termi geostashing, joka pian vaihtui vähemmän negatiivisia assosiaatioita tuovaan geocachingiin.

  18. Pakko lisätä tähän listaan meidän kahden TB:n kohtaaminen Australiassa. TB Badge the Budgie lähti matkaan Hollannista joulukuussa 2003 ja päätyi monien mutkien (jäi mm. 'panttivangiksi' erään kätköilijän taskuun n. vuodeksi) jälkeen päämääräänsä eli Australiaan vuonna 2005. TB Rolle the Budgie puolestaan pääsi suoraan Australiaan Mikkozzz:n mukana vuonna 2004, jossa se on matkustellut siitä lähtien. Kaikkien näiden vuosien ja yhteensä lähes 70 000 matkatun kilometrin jälkeen kaksikko päätyi lopulta saman kätköilijän käsiin eilen Brisbanessa: :o




    Mission completed, Onneksi olkoon!

  • Create New...