unable to grab geocoin from cache

[scidawg]

I recently hid my first cache. Before it was published I dropped a geocoin in it which I had found earlier. The second finder of the cache grabbed the coin, but he emailed me that he is unable to log it as retrieved from the cache. I tried to mark it missing, so he could then grab it but that didnt work either. Any ideas what is going on?

[jholly]

I recently hid my first cache. Before it was published I dropped a geocoin in it which I had found earlier. The second finder of the cache grabbed the coin, but he emailed me that he is unable to log it as retrieved from the cache. I tried to mark it missing, so he could then grab it but that didnt work either. Any ideas what is going on?

 

look on the coin's page. Where does it say that it is?

 

Jim

[Moun10Bike]

I just tested retrieval of the geocoin with a basic membership and had no problems. Is it certain that the finder is entering the correct tracking number?

 

I didn't test the marking the coin missing after my first test worked properly.

[+BlueDeuce]

Any chance you still have the tracking number? You might want to verify he is entering it in correctly.

 

otherwise we'll need to know what error he is getting.

[+Kealia]

Likely that he is confusing "o" for "0" or "5" for "s" or something similar.

[stebu]

A bit off-topic (and might be a known problem).

Anyhow, I'm not able to enter more than 6 characters in the input box "Visit another travel bug:" on the url: http://www.geocaching.com/track/log.aspx?LUID=xxx....

 

And there are bugs with id like TB12345.

[OpinioNate]

A bit off-topic (and might be a known problem).

Anyhow, I'm not able to enter more than 6 characters in the input box "Visit another travel bug:" on the url: http://www.geocaching.com/track/log.aspx?LUID=xxx....

 

And there are bugs with id like TB12345.

 

Nice catch; that is definitely a bug. It should also read "trackable" instead of "travel bug". Thanks.