#1563 Picasa. Error

1.1
open
nobody
picasa (1)
none
5
2013-10-30
2013-10-24
716 cats
No
0 up votes | 0 down votes | 0%
7 comments

error when trying to download a picasa

1 Attachments

Discussion

  • Jens Klingen
    Jens Klingen
    2013-10-24

    Hi there,

    Could you have a look into Greenshot's log file and upload it here? Or (if it is too large) at least the part of it that covers the time when the error occurred?

    There is probably some useful information in there.

    Thanks and best regards,
    Jens :)

     
  • 716 cats
    716 cats
    2013-10-25

    log

     
    Attachments
  • Jens Klingen
    Jens Klingen
    2013-10-27

    Thanks for the log. Did you encounter this just once? Or more often? Or always?

    The Picasa server responded with

    Timestamp is too far from current time: 1382679546

    Maybe your system time is not correctly set? Or for some reason Picasa authentication before upload simply took to long (for whatever reason)?

     
  • 716 cats
    716 cats
    2013-10-28

    I'll try to explain. I do not know will have to use Google translator.
    The problem started immediately after installing Greenshot. The system time of establishing the right (time zone +3). Window authorization in Picasa does not appear initially in contrast to, for example, BOX.net.

     
  • Robin Krom
    Robin Krom
    2013-10-28

    Your time is more than 60 seconds off, Picasa (google) returned their current time which was Fri Oct 25 2013 07:39:06 And your log was at 09:38:00 meaning you have a derivation > minute (I ignored the hours, as this is most likely a timezone thing). Although I am not 100% sure why this is important for Picasa, it might be the issue here.

    Try synchronizing your PC with an NTP server!

     
  • 716 cats
    716 cats
    2013-10-29

    It did not help unfortunately

     
  • Robin Krom
    Robin Krom
    2013-10-30

    Is your timezone set correctly? There seems to be a three-hour difference between the google answer of what it assumes is the current time and your time...

    This could be caused by wrong timezone settings and might have an influence!