: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'UTC/0.0/no DST' instead in /home/groups/p/pd/pdesk/htdocs/NewDB/drupal-4.3.2/includes/common.inc on line 836.

: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'UTC/0.0/no DST' instead in /home/groups/p/pd/pdesk/htdocs/NewDB/drupal-4.3.2/includes/common.inc on line 836.

: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'UTC/0.0/no DST' instead in /home/groups/p/pd/pdesk/htdocs/NewDB/drupal-4.3.2/includes/common.inc on line 836.

: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'UTC/0.0/no DST' instead in /home/groups/p/pd/pdesk/htdocs/NewDB/drupal-4.3.2/includes/common.inc on line 836.

: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'UTC/0.0/no DST' instead in /home/groups/p/pd/pdesk/htdocs/NewDB/drupal-4.3.2/includes/common.inc on line 833.

: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'UTC' for 'UTC/0.0/no DST' instead in /home/groups/p/pd/pdesk/htdocs/NewDB/drupal-4.3.2/includes/common.inc on line 833.

Sync fails or PDesk exits: log shows: socket.error: (10048, 'Address already in use')
Submitted by Judd on Friday, April 30, 2004 - 08:23	FAQ | Problem | Windows
This FAQ addresses a known problem with PDesk which sometimes causes PDesk to just exit and sometimes causes a sync to fail. If you see this message in the PDesk log: socket.error: (10048, 'Address already in use') then you have this problem. One note: 10048 is the error number and not the port already in use. PDesk has a companion C program which manages the integration with the Palm Desktop. PDesk and this program communicate via socket 9999. Other programs might be using this same port. This can cause PDesk to exit or, if the port is in use when you sync, your sync could fail. netstat -a will list all the ports in use. See if 9999 is on the list. This is windows specific as there is no Palm Desktop for any other OS so the integration code only runs on windows. The following programs are know to have caused this conflict: K9 spam filter previous next up Put the PDesk icon in the Palm Desktop Support
[ printer-friendly version | login or register to post comments ]