PC Suite Synchronisation problem with 62301

Windows XP Professional SP2
PC Suite 6.7 & 6.8
6230i via Bluetooth and/or IrDA
I have been using the above to successfully synchronise my Outlook Contacts & Calendar for some time. All of a sudden the following problem has appeared...
On selecting Synchronise Now in the Nokia PC Sync dialog, the blue & green bubbles continue to rotate and the message 'Connecting to 6230i' continues to flash for some 5 mins. The message then changes to 'Waiting for the mobile phone to send data'. This continues for approx. 3 mins, where upon synchronisation stops and the message Synchronisation Completed appears. However, 0 entries have been updated, despite several updates to contacts.
Previously, having pressed the Synchronise Now button, synchronisation would take typically less than a minute and all updates would be transferred OK.
I have tried everything I can think of. Included, completely de-pairing the phone from the PC, uninstalling PC Suite, installing again from scratch and re-establishing the connection. I have also updated from 6.7 to 6.8 of PC Suite and have tried via Bluetooth and IrDA with the same effect.
All other functions in PC Suite work. For example, I can send a text to myself, then synchronise my messages and view the newly received message; I can view files; etc.
However, if I try and synchronise my Contacts through File Manager, the synchronisation again runs for many minutes and does not update any contacts.
I'm not sure, but it appears to me as if something has corrupted on the phone, which is specifically related to synchronisation.
I'd be grateful for any thoughts/ideas?

Problem solved!
I had already tried switching the phone off then on without success.
However, I have now tried switching off, removing the battery for 1 min, replacing and switching back on. That worked!
Oh! The joys of owning a Nokia!!

Similar Messages

  • PC Suite has problem with 3120

    PC Suite has problem with 3120

    I also have detected the problem. It is not any physical malfunction according to me. It occures with my phone when I unplug it and plug it again. Sometimes is useful to change the USB port and afterwards to move back to the previous one. Try it and also try it combined with PC restart. It is a weird problem!?

  • Synchronisation problem with LifeBlog

    Since about 2 weeks now, I cannot synchronise the stuff from my 6630 Lifeblog onto the PC Lifeblog. I keep getting the following message:
    "Lifeblog encounters problems transferring items. Please check the connection and try again. If the problem persists, restart Lifeblog and/or the PC and try again.
    Possible reasons: An item that you are trying to transfer may be opened in an application on your phone or PC, the multimedia card (MMC) on your phone or your PC hard disk may be full.
    For more information see Lifeblog Online Help, Troubleshooting, Transfer Problems."
    In the course of this problem I had done the followings:
    * Restart the computer and try again
    * Restart the 6630 and try again
    * Restart both the PC and the 6630 and try again
    * Check both the MMC (354 MB free) and my PC hard disk (16 GB free), restart both and try again
    * Uninstall Nokia PC-Suite and reinstall it and try again
    * Went to see the "Troubleshooting" which wasn't any help at all
    * Updated the firmware and try again
    * Re-installing PC-Suite (newest version), Lifeblog (newest version) on both phone and PC and try again
    All to no avail.
    Any help?
    Information:
    Phone:
    Nokia 6630
    Firmware version 6.03.08
    Operating system:
    Microsoft Windows XP
    Service Pack 2
    Nokia PC Suite:
    Version 6.81.13.0
    Language: English
    Connectivity Cable Drivers:
    Version 6.81.1.2

    23-Aug-2006
    10:01 AM
    elemmaciltur wrote:
    Since about 2 weeks now, I cannot synchronise the stuff from my 6630 Lifeblog onto the PC Lifeblog. I keep getting the following message:
    "Lifeblog encounters problems transferring items. Please check the connection and try again. If the problem persists, restart Lifeblog and/or the PC and try again.
    Possible reasons: An item that you are trying to transfer may be opened in an application on your phone or PC, the multimedia card (MMC) on your phone or your PC hard disk may be full.
    For more information see Lifeblog Online Help, Troubleshooting, Transfer Problems."
    In the course of this problem I had done the followings:
    * Restart the computer and try again
    * Restart the 6630 and try again
    * Restart both the PC and the 6630 and try again
    * Check both the MMC (354 MB free) and my PC hard disk (16 GB free), restart both and try again
    * Uninstall Nokia PC-Suite and reinstall it and try again
    * Went to see the "Troubleshooting" which wasn't any help at all
    * Updated the firmware and try again
    * Re-installing PC-Suite (newest version), Lifeblog (newest version) on both phone and PC and try again
    All to no avail.
    Any help?
    Information:
    Phone:
    Nokia 6630
    Firmware version 6.03.08
    Operating system:
    Microsoft Windows XP
    Service Pack 2
    Nokia PC Suite:
    Version 6.81.13.0
    Language: English
    Connectivity Cable Drivers:
    Version 6.81.1.2
    I've occasionally had the same error message you experienced above and have been able to solve it although I have not been able to localise whereabouts the problem is occurring.
    As an aside, I don't think you mention what version of LifeBlog you are using but FYI (For Your Information) v2.1.131 is out.
    I've composed a list of things you should look at to find out why this is happening - these questions are only meant to find out where the problem lies - not apportion blame so please don't take them the wrong way !
    Things you need to look at to solve the problem or eliminate the potential cause of the problem :
    1) Upgrade to the latest version of LifeBlog if you aren't already using it - it can be found here - http://www.nokia.com/lifeblog - it may be possible that the problem you are having is a known issue which is solved in the latest release. At the very least I would recommend doing a complete uninstall of the old version and then rebooting, and installing the new version to ensure that you start from a clean configuration.
    2) Has LifeBlog ever worked ? If so, then when did it stop working ? What did you do previous to when it stopped working ? Did you install a new PC/mobile application ?
    3) Are you able to use the full capabilities of PC Suite successfully ? Can you backup the phone, synchronise data with Outlook or whatever compatible PIM you use ? The fact that you have done a software update etc. indicates you can connect successfully to the phone, but I thought I would put it here for completeness !
    4) Have you tried installing the LifeBlog software which is designed to run on the mobile phone - not the PC ? (If not - please do this - it will act as an useful potential problem indicator further below)
    5) Are you running any minimized software on your PC or phone whilst trying to do the PC Suite/LifeBlog update ? Disable any anti virus software JUST IN CASE FOR THIS TESTING ONLY. I once had an issue where I connected a camcorder via Firewire and I then couldn't surf the internet - this turned out to be a problem with the anti virus application I was using at the time - it only recognised one valid TCP/IP interface at a time - when the FireWire connection became active, it shut the interface to my network card down ! Also make sure any firewall software is temporarily disabled just in case as well.
    You sound technically proficient, but again I thought I'd put this in for completeness.
    The thing that should happen if you have PC Suite living in your system tray (next to your clock) and you plug you phone in is as follows. You should get a little bublle pop up saying "6680 connected via USB" or something similar - the white cross in a red background should change to a green shape - can't remember what the shape is off the top of my head.
    Once that happens it pretty much means that your phone and PC are talking correctly. At this point PC Suite (e.g. backup) should work - if it doesn't then you will need to resolve this issue before LifeBlog will work.
    Presuming PC Suite works, and the problem is indeed localised to LifeBlog, the next stage of diagnostics would be to load LifeBlog for your mobile. When you load the LifeBlog software on your mobile, you should see a chronological list of pictures you have taken and text messages you have sent - check this is the case and that it is up to date - send yourself a text message and check if you can see it being sent and received in LifeBlog - if not, then click the options button and select Update Timeline (or something similar) and try again - does it appear now ? If it doesn't then it indicates LifeBlog isn't working correctly - I would recommend that you uninstall LifeBlog on your mobile and power cycle your mobile and reinstall it. This is the particular issue I was having - when I got LifeBlog on my mobile working - it worked on my PC - sometimes I find if they get out of sync they're not particularly happy (even though they should be independent of each other).
    I'm pretty sure from the log files, that LifeBlog uses a database of sometime to collate the LifeBlog information and sometimes it can get a bit confused - the "Update TimeLine" option should help solve this.
    Hope this helps - let me know how you get on !
    Regards,
    Edward

  • How do I investigate and solve Pages, Notes, Mail intermittent 'offline' and failure to synchronise problems with Mountain Lion after waking from Sleep

    When I wake up my iMac after sleep, i get a variety of intermittent - but mostly FREQUENT and FRUSTRATING problems including:
    Notes app is offline - as stated by a message in the window bar. If I close Notes and reopen, the app appears to be online. However, Notes does NOT update with items I know are on my iPad or in the web iCloud. Furthermore, if I create a new note on my iMac, the new Note does not upload to iCloud. This is IRRITATING!
    Pages and Numbers - similar situation. I can edit a Pages or Numbers document on my iMac (stored on the iCloud). But then the Pages doc doesn't ALWAYS get uploaded to the iCloud. Then I end up with conflicted versions of the file in the cloud, my iPad, and the two iMacs I use. Then I get CONFUSED and FRUSTRATED. For example, consider these steps:
    Open Pages on my iMac, edit an iCloud file, then save and close file
    Pages/File/Open/iCloud - I note in the iCloud file list the edited file has a little 'cloud' icon against its name. From experience this warns me of TROUBLE - namely that the file has NOT yet been uploaded to the iCloud. However, I just checked the new Beta iCloud on the web, and to my surprise, the file edited on my iMac is apparently in the icloud. But now, I edit the iCloud version, and the changes DO NOT appear on my iMac pages version. OK I realise its in Beta version...
    So now, I open my iPad, open Pages. I note the iCloud version of my edited document updates to my iPad, as indicated by a blue download line. 'It just works' as Steve Jobs claimed at Apple Developers Conference a couple of years back. Again, the edited version form my iPad is now 'up in the cloud' correctly....
    Oh - and now mysteriously the Pages version on my Imac has become synchronised with my iPad/iCloud version! Luck ... but that's about all I can say. It doesn't always happen. I'm LUCKY today.
    Meanwhile, the Note I created on my iMac (Item 1 above) has still not yet appeared on my iPad or iCloud... even though I HOPE it would be given that Pages on my iMac, iPad and iCloud are chatting nicely now! The Note says it's in my iCloud - but  NOT. Similarly, notes updated or added on my iPad, which appear in iCloud, are NOT on my iMac.
    Mail - last but NOT LEAST! and MOST INFURIATING!!! My Gmail, Vodafone NZ and Orcon accounts (in Mail) are all active and receiving after the night's sleep. However, my iCloud mail account has the dreaded offline.
    The message on Mail is "There may be a problem with the mail server or network. Verify the settings for account “ICloud - [email protected]” or try again. The server returned the error: The server “p03-imap.mail.me.com” cannot be contacted on port 993." Despite the message, mail was received this morning at 8:59 am ... some time before I woke-up my computer (a late start this morning).
    If I sent an email FROM my .me iCloud account TO my Vodafone account, the message whooshes away, it's in my SENT box. But it doesn't get delivered to my Vodafone account on my iMac Mail, or anywhere else, Despite the message being listed in my 'Sent' mailbox!!!
    In contrast, a message sent from my Gmail account to my Vodafone account (in Mail) gets sent and received almost instantly on  my iMac and iPad.
    All of the above mishaps are extremely frustrating, as I rush off from working on my iMac at home, get to my iMac at work and find documents I have been updating on my home iMac not available correctly on my work iMac ... or even my iPad. I expect these things from Apple to 'just work'. Furthermore, emails I THINK I have sent (as indicated by them appearing in the Sent folder on my home iMac) ... have not actually been despatched.
    Frankly, I can no longer rely or recommend the Apple iCloud stuff, so I am converting more and more to relying on DropBox and Google.
    These problems only became apparent since I updated to one of the Mountain Lion versions... I can't say when.
    Oh - if I shutdown and restart the computer my Mail works OK. Guess what, I don't want to do that each time I want to use Mail!
    Technicals:
    My iMac is connected by Ethernet cable to my Apple TimeCapsule. The TimeCapsule is connected by Ethernet cable to my Orcon Genius Modem.
    Obviously, my internet connection is A-OK, as I am able to use Firefox to make this posting!
    Mountain Lion 10.8.4
    iMac 27 inch, mid 2010, Intel Core i5 16 Gb

    I've returned to my sleeping iMac after a few days away. Tis time, ALL MAIL accoiunts are offline. I will follow you next set of instructions. In the meantime, here is the DETAIL from MAIL CONNECTION DOCTOR:
    LevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
    19.10827 STATUS [Gmail]/Trash (UIDNEXT UNSEEN HIGHESTMODSEQ)
    WROTE Sep 30 08:35:11.179 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
    20.10827 STATUS INBOX (UIDNEXT UNSEEN HIGHESTMODSEQ)
    WROTE Sep 30 08:35:11.202 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
    21.10827 STATUS "Sent Messages" (UIDNEXT UNSEEN HIGHESTMODSEQ)
    WROTE Sep 30 08:35:11.226 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
    22.10827 STATUS "Deleted Messages" (UIDNEXT UNSEEN HIGHESTMODSEQ)
    READ Sep 30 08:35:11.254 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
    * STATUS "[Gmail]/All Mail" (HIGHESTMODSEQ 561701 UIDNEXT 1666 UNSEEN 105)
    13.10827 OK Success
    READ Sep 30 08:35:11.494 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
    * STATUS "[Gmail]/Drafts" (HIGHESTMODSEQ 561701 UIDNEXT 1 UNSEEN 0)
    14.10827 OK Success
    READ Sep 30 08:35:11.514 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc31616b9d0
    * STATUS "[Gmail]/Important" (HIGHESTMODSEQ 561701 UIDNEXT 731 UNSEEN 8)
    15.10827 OK Success
    * STATUS "[Gmail]/Sent Mail" (HIGHESTMODSEQ 561701 UIDNEXT 532 UNSEEN 2)
    16.10827 OK Success
    * STATUS "[Gmail]/Spam" (HIGHESTMODSEQ 561701 UIDNEXT 16 UNSEEN 2)
    17.10827 OK Success
    * STATUS "[Gmail]/Starred" (HIGHESTMODSEQ 561701 UIDNEXT 19 UNSEEN 0)
    18.10827 OK Success
    * STATUS "[Gmail]/Trash" (HIGHESTMODSEQ 561701 UIDNEXT 546 UNSEEN 0)
    19.10827 OK Success
    * STATUS "INBOX" (HIGHESTMODSEQ 561701 UIDNEXT 603 UNSEEN 64)
    20.10827 OK Success
    * STATUS "Sent Messages" (HIGHESTMODSEQ 561701 UIDNEXT 138 UNSEEN 0)
    21.10827 OK Success
    * STATUS "Deleted Messages" (HIGHESTMODSEQ 561701 UIDNEXT 89 UNSEEN 0)
    22.10827 OK Success
    WROTE Sep 30 08:35:11.537 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc3186cf640
    23.10827 IDLE
    READ Sep 30 08:35:11.927 [kCFStreamSocketSecurityLevelTLSv1SSLv3]  -- host:imap.gmail.com -- port:993 -- socket:0x7fc3182ee310 -- thread:0x7fc3186cf640
    + idling
    READ Sep 30 08:35:15.472 [kCFStreamSocketSecurityLevelNone]  -- host:smtp.mail.me.com -- port:587 -- socket:0x7fc31855c470 -- thread:0x7fc31858ada0
    220 st11p00mm-asmtp002.mac.com -- Server ESMTP (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013))
    WROTE Sep 30 08:35:24.784 [kCFStreamSocketSecurityLevelNone]  -- host:mail.orcon.net.nz -- port:25 -- socket:0x7fc3161a1b00 -- thread:0x7fc315d05050
    EHLO [10.1.1.4]
    WROTE Sep 30 08:35:24.822 [kCFStreamSocketSecurityLevelNone]  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x7fc316e72a70 -- thread:0x7fc31850bec0
    EHLO [10.1.1.4]
    WROTE Sep 30 08:35:34.080 [kCFStreamSocketSecurityLevelNone]  -- host:smtp.mail.me.com -- port:587 -- socket:0x7fc31855c470 -- thread:0x7fc31858ada0
    EHLO [10.1.1.4]
    INITIATING CONNECTION Sep 30 08:35:47.175  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc316fc30e0
    INITIATING CONNECTION Sep 30 08:35:47.175  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc31a6fa8a0
    INITIATING CONNECTION Sep 30 08:35:47.175  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc316197890
    INITIATING CONNECTION Sep 30 08:35:47.175  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc316e813d0
    INITIATING CONNECTION Sep 30 08:35:47.175  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0350
    INITIATING CONNECTION Sep 30 08:35:47.175  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc3185c0410
    INITIATING CONNECTION Sep 30 08:35:47.175  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc315ded870
    INITIATING CONNECTION Sep 30 08:35:47.193  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316e729b0
    INITIATING CONNECTION Sep 30 08:35:47.198  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3167d2380
    INITIATING CONNECTION Sep 30 08:35:47.377  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3167d2380
    INITIATING CONNECTION Sep 30 08:36:40.352  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc318203720
    INITIATING CONNECTION Sep 30 08:36:40.352  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc312c8dbc0
    INITIATING CONNECTION Sep 30 08:36:40.353  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc31617f290
    INITIATING CONNECTION Sep 30 08:36:40.353  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc316e729b0
    INITIATING CONNECTION Sep 30 08:36:40.353  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc31615a390
    INITIATING CONNECTION Sep 30 08:36:40.353  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316e3bbc0
    INITIATING CONNECTION Sep 30 08:36:40.353  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc316e0cfa0
    INITIATING CONNECTION Sep 30 08:36:40.368  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31829f120
    INITIATING CONNECTION Sep 30 08:36:40.403  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc312c8dbc0
    INITIATING CONNECTION Sep 30 08:36:40.412  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
    INITIATING CONNECTION Sep 30 08:36:40.565  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc312c8dbc0
    INITIATING CONNECTION Sep 30 08:36:40.595  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
    INITIATING CONNECTION Sep 30 08:36:40.633  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
    INITIATING CONNECTION Sep 30 08:36:40.687  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
    INITIATING CONNECTION Sep 30 08:36:40.708  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
    INITIATING CONNECTION Sep 30 08:36:40.729  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc318203720
    INITIATING CONNECTION Sep 30 08:37:33.322  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc3183339e0
    INITIATING CONNECTION Sep 30 08:37:33.322  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3186f07e0
    INITIATING CONNECTION Sep 30 08:37:33.322  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc315a9b630
    INITIATING CONNECTION Sep 30 08:37:33.322  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc3163e7dd0
    INITIATING CONNECTION Sep 30 08:37:33.322  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3172f6e70
    INITIATING CONNECTION Sep 30 08:37:33.322  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc31616b9d0
    INITIATING CONNECTION Sep 30 08:37:33.323  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc315d14150
    INITIATING CONNECTION Sep 30 08:37:33.336  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316e03950
    INITIATING CONNECTION Sep 30 08:37:33.462  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
    INITIATING CONNECTION Sep 30 08:37:33.463  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3163e7dd0
    INITIATING CONNECTION Sep 30 08:37:33.509  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
    INITIATING CONNECTION Sep 30 08:37:33.528  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3163e7dd0
    INITIATING CONNECTION Sep 30 08:37:33.557  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
    INITIATING CONNECTION Sep 30 08:37:33.598  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
    INITIATING CONNECTION Sep 30 08:37:33.624  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
    INITIATING CONNECTION Sep 30 08:37:33.646  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315d14150
    INITIATING CONNECTION Sep 30 08:38:26.315  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc31686fa30
    INITIATING CONNECTION Sep 30 08:38:26.316  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316fcc7d0
    INITIATING CONNECTION Sep 30 08:38:26.316  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3170d8a90
    INITIATING CONNECTION Sep 30 08:38:26.317  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc318521490
    INITIATING CONNECTION Sep 30 08:38:26.317  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc316e81b30
    INITIATING CONNECTION Sep 30 08:38:26.317  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc316fdf410
    INITIATING CONNECTION Sep 30 08:38:26.318  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc315d3a890
    INITIATING CONNECTION Sep 30 08:38:26.320  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316774270
    INITIATING CONNECTION Sep 30 08:38:26.350  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316728a90
    INITIATING CONNECTION Sep 30 08:38:26.350  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
    INITIATING CONNECTION Sep 30 08:38:26.495  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316774270
    INITIATING CONNECTION Sep 30 08:38:26.538  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
    INITIATING CONNECTION Sep 30 08:38:26.591  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
    INITIATING CONNECTION Sep 30 08:38:26.619  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
    INITIATING CONNECTION Sep 30 08:38:26.642  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
    INITIATING CONNECTION Sep 30 08:38:26.666  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316fdaa30
    INITIATING CONNECTION Sep 30 08:39:19.257  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc31662a980
    INITIATING CONNECTION Sep 30 08:39:19.258  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc3182e6150
    INITIATING CONNECTION Sep 30 08:39:19.258  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc31605c330
    INITIATING CONNECTION Sep 30 08:39:19.258  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc3184b79c0
    INITIATING CONNECTION Sep 30 08:39:19.258  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc31658f5b0
    INITIATING CONNECTION Sep 30 08:39:19.259  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc316e03950
    INITIATING CONNECTION Sep 30 08:39:19.259  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3160d8c80
    INITIATING CONNECTION Sep 30 08:39:19.265  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc31662b000
    INITIATING CONNECTION Sep 30 08:39:19.287  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316073530
    INITIATING CONNECTION Sep 30 08:39:19.287  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
    INITIATING CONNECTION Sep 30 08:39:19.420  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc31662b000
    INITIATING CONNECTION Sep 30 08:39:19.457  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
    INITIATING CONNECTION Sep 30 08:39:19.505  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
    INITIATING CONNECTION Sep 30 08:39:19.531  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
    INITIATING CONNECTION Sep 30 08:39:19.552  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
    INITIATING CONNECTION Sep 30 08:39:19.573  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316c23cd0
    INITIATING CONNECTION Sep 30 08:40:11.346  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3161c6e50
    INITIATING CONNECTION Sep 30 08:40:11.347  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc316becee0
    INITIATING CONNECTION Sep 30 08:40:11.348  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc31679c620
    INITIATING CONNECTION Sep 30 08:40:11.349  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc3144ad030
    INITIATING CONNECTION Sep 30 08:40:11.349  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc31b8d0250
    INITIATING CONNECTION Sep 30 08:40:11.349  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc3158e5b50
    INITIATING CONNECTION Sep 30 08:40:11.349  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc316728a90
    INITIATING CONNECTION Sep 30 08:40:11.363  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315c576d0
    INITIATING CONNECTION Sep 30 08:40:11.518  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
    INITIATING CONNECTION Sep 30 08:40:11.518  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3168cf630
    INITIATING CONNECTION Sep 30 08:40:11.548  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
    INITIATING CONNECTION Sep 30 08:40:11.568  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3168cf630
    INITIATING CONNECTION Sep 30 08:40:11.597  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
    INITIATING CONNECTION Sep 30 08:40:11.638  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
    INITIATING CONNECTION Sep 30 08:40:11.660  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
    INITIATING CONNECTION Sep 30 08:40:11.683  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b8d0250
    INITIATING CONNECTION Sep 30 08:41:06.173  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc318297540
    INITIATING CONNECTION Sep 30 08:41:06.175  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc31b9c7b90
    INITIATING CONNECTION Sep 30 08:41:06.175  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc314144080
    INITIATING CONNECTION Sep 30 08:41:06.175  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc315d435e0
    INITIATING CONNECTION Sep 30 08:41:06.175  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc3167306a0
    INITIATING CONNECTION Sep 30 08:41:06.175  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc31680f3e0
    INITIATING CONNECTION Sep 30 08:41:06.175  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc3170d8a90
    INITIATING CONNECTION Sep 30 08:41:06.197  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31671e630
    INITIATING CONNECTION Sep 30 08:41:06.223  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
    INITIATING CONNECTION Sep 30 08:41:06.223  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc318569a40
    INITIATING CONNECTION Sep 30 08:41:06.376  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
    INITIATING CONNECTION Sep 30 08:41:06.396  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc318569a40
    INITIATING CONNECTION Sep 30 08:41:06.431  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
    INITIATING CONNECTION Sep 30 08:41:06.475  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
    INITIATING CONNECTION Sep 30 08:41:06.503  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
    INITIATING CONNECTION Sep 30 08:41:06.527  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31b9c7b90
    INITIATING CONNECTION Sep 30 08:41:59.159  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc3160bc120
    INITIATING CONNECTION Sep 30 08:41:59.160  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316e16c90
    INITIATING CONNECTION Sep 30 08:41:59.160  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3161e71f0
    INITIATING CONNECTION Sep 30 08:41:59.161  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc315f45120
    INITIATING CONNECTION Sep 30 08:41:59.161  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc3170d94c0
    INITIATING CONNECTION Sep 30 08:41:59.161  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc3174bc990
    INITIATING CONNECTION Sep 30 08:41:59.161  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc31820b7d0
    INITIATING CONNECTION Sep 30 08:41:59.174  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3162884e0
    INITIATING CONNECTION Sep 30 08:41:59.189  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316c2b240
    INITIATING CONNECTION Sep 30 08:41:59.189  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
    INITIATING CONNECTION Sep 30 08:41:59.344  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316c2b240
    INITIATING CONNECTION Sep 30 08:41:59.363  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
    INITIATING CONNECTION Sep 30 08:41:59.409  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
    INITIATING CONNECTION Sep 30 08:41:59.430  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
    INITIATING CONNECTION Sep 30 08:41:59.450  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
    INITIATING CONNECTION Sep 30 08:41:59.471  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3160bc120
    INITIATING CONNECTION Sep 30 08:42:51.209  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc31a613830
    INITIATING CONNECTION Sep 30 08:42:51.210  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3168ae8d0
    INITIATING CONNECTION Sep 30 08:42:51.210  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc3161d6110
    INITIATING CONNECTION Sep 30 08:42:51.211  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc315de6190
    INITIATING CONNECTION Sep 30 08:42:51.211  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc316482400
    INITIATING CONNECTION Sep 30 08:42:51.211  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc3167069e0
    INITIATING CONNECTION Sep 30 08:42:51.211  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc31829f120
    INITIATING CONNECTION Sep 30 08:42:51.224  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3159e76e0
    INITIATING CONNECTION Sep 30 08:42:51.372  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316c2b240
    INITIATING CONNECTION Sep 30 08:42:51.372  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
    INITIATING CONNECTION Sep 30 08:42:51.402  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316c2b240
    INITIATING CONNECTION Sep 30 08:42:51.421  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
    INITIATING CONNECTION Sep 30 08:42:51.466  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
    INITIATING CONNECTION Sep 30 08:42:51.492  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
    INITIATING CONNECTION Sep 30 08:42:51.514  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
    INITIATING CONNECTION Sep 30 08:42:51.536  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3167069e0
    INITIATING CONNECTION Sep 30 09:43:23.246  -- host:smtp.mail.me.com -- port:587 -- socket:0x0 -- thread:0x7fc315d40d90
    INITIATING CONNECTION Sep 30 09:43:23.246  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc315ad1930
    INITIATING CONNECTION Sep 30 09:43:23.246  -- host:mail.orcon.net.nz -- port:25 -- socket:0x0 -- thread:0x7fc316c27e30
    INITIATING CONNECTION Sep 30 09:43:23.246  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc315adf230
    INITIATING CONNECTION Sep 30 09:43:23.246  -- host:smtp.vodafone.co.nz -- port:25 -- socket:0x0 -- thread:0x7fc315d49010
    INITIATING CONNECTION Sep 30 09:43:23.246  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3159a1ea0
    INITIATING CONNECTION Sep 30 09:43:23.246  -- host:smtp.gmail.com -- port:587 -- socket:0x0 -- thread:0x7fc318691eb0
    INITIATING CONNECTION Sep 30 09:43:23.250  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc315f45120
    INITIATING CONNECTION Sep 30 09:43:23.311  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316e1b2d0
    INITIATING CONNECTION Sep 30 09:43:23.311  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
    INITIATING CONNECTION Sep 30 09:43:23.427  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc315f45120
    INITIATING CONNECTION Sep 30 09:43:23.471  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
    INITIATING CONNECTION Sep 30 09:43:23.524  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
    INITIATING CONNECTION Sep 30 09:43:23.547  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
    INITIATING CONNECTION Sep 30 09:43:23.574  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
    INITIATING CONNECTION Sep 30 09:43:23.598  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31869d090
    INITIATING CONNECTION Sep 30 10:06:17.592  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3159227c0
    INITIATING CONNECTION Sep 30 10:06:17.596  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3174e7bd0
    INITIATING CONNECTION Sep 30 10:06:17.598  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc315e08640
    INITIATING CONNECTION Sep 30 10:06:18.674  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
    INITIATING CONNECTION Sep 30 10:06:19.483  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc318462600
    INITIATING CONNECTION Sep 30 10:06:19.539  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3162d4270
    INITIATING CONNECTION Sep 30 10:06:19.564  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3159227c0
    INITIATING CONNECTION Sep 30 10:06:19.582  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
    INITIATING CONNECTION Sep 30 10:06:19.653  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
    INITIATING CONNECTION Sep 30 10:06:19.674  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
    INITIATING CONNECTION Sep 30 10:06:19.725  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
    INITIATING CONNECTION Sep 30 10:06:19.747  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc316a42ed0
    INITIATING CONNECTION Sep 30 10:07:19.496  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316491d10
    INITIATING CONNECTION Sep 30 10:07:19.523  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc3144bad30
    INITIATING CONNECTION Sep 30 10:07:19.531  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
    INITIATING CONNECTION Sep 30 10:07:19.534  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3172b7640
    INITIATING CONNECTION Sep 30 10:07:19.550  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc315cbb960
    INITIATING CONNECTION Sep 30 10:07:19.626  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc315842910
    INITIATING CONNECTION Sep 30 10:07:19.665  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc316491d10
    INITIATING CONNECTION Sep 30 10:07:19.715  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
    INITIATING CONNECTION Sep 30 10:07:19.805  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
    INITIATING CONNECTION Sep 30 10:07:19.854  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
    INITIATING CONNECTION Sep 30 10:07:19.892  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
    INITIATING CONNECTION Sep 30 10:07:19.915  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31613c6b0
    INITIATING CONNECTION Sep 30 10:08:19.527  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3162aa260
    INITIATING CONNECTION Sep 30 10:08:19.553  -- host:mail.orcon.net.nz -- port:995 -- socket:0x0 -- thread:0x7fc3162e8510
    INITIATING CONNECTION Sep 30 10:08:19.555  -- host:pop.vodafone.co.nz -- port:110 -- socket:0x0 -- thread:0x7fc315ac9950
    INITIATING CONNECTION Sep 30 10:08:19.564  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0
    INITIATING CONNECTION Sep 30 10:08:19.582  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3146b1020
    INITIATING CONNECTION Sep 30 10:08:19.685  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc3163d82c0
    INITIATING CONNECTION Sep 30 10:08:19.705  -- host:imap.gmail.com -- port:993 -- socket:0x0 -- thread:0x7fc3162aa260
    INITIATING CONNECTION Sep 30 10:08:19.756  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0
    INITIATING CONNECTION Sep 30 10:08:19.800  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0
    INITIATING CONNECTION Sep 30 10:08:19.852  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0
    INITIATING CONNECTION Sep 30 10:08:19.876  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0
    INITIATING CONNECTION Sep 30 10:08:19.898  -- host:p03-imap.mail.me.com -- port:993 -- socket:0x0 -- thread:0x7fc31643e6f0

  • Creative Suite CS4: Problems with font managing software

    It seems that there are some issues of the applications of the creative suite CS4 with the font managing software MainType (http://www.high-logic.com/maintype.html).
    With standard settings, CS4 no longer recognizes PostScript Type 1 Fonts loaded by MainType (which did not occur with CS3 and older versions). The only solution so far is this workaround:  Within MainType enable under "Tools -> Options" the option "Copy Type 1 Postscript fonts to Windows fonts folder" and CS4 will load these fonts again.
    This seems to be a bug of CS4. Are there problems with other font managing programs?
    regards
    fabian

    After reading tons of forums about this issue, it does seem to be an issue with CS4 not recognizing fonts the way that CS3 did. Wish they had mentioned that little feature when they released it. They even go as far as to say they do not support certain programs for type handling in Windows. Copying them to the system folder is a workaround, but it is not available easily in programs like Extensis' Suitcase, which is long overdue an upgrade. LinoType beta tested a new application for Windows, but when I sent an email to them asking about the release date for the their final version, their ignorant customer support sent me a link to their website pointing out that it is not yet available, and not answering my initial question of when.
    I don't entirely blame Adobe, it seems as though a lot of companies have dropped the ball on this issue, and since many people have Type 1 fonts they've been using for years, they will have to repurchase (if available) those fonts in the newer OTF format which everyone seems to support. OTF is a much nicer format and more portable cross-platform, but it's simply inconvenient to not be able to use all of your fonts at your own discretion easily. I'm not sure what the big deal was with not including support for Type 1 fonts, unless that's most of the reason that the Adobe apps were crashing before... corrupt versions of the fonts they talked us into purchasing, etc... Adobe used to make ATM for managing postscript fonts, but it doesn't work on Vista to my knowledge. It would be nice if they would recommend a font manager other than the Windows system folder.
    I figure Adobe was hoping that it would not be a major issue since their wonderful PDF format has taken hold for printing. Print shops do not have to install fonts before printing a piece anymore. Most people will read in these forums about the loss of support, throw up their hands and shake their heads, but do nothing about it. After all they too probably purchased the CS4 suite without knowing about this issue and have already spent their money. It doesn't look as though it's an issue on the Mac, but by the time you throw $3000 at an entry level Mac workstation and $1600 at the basic adobe apps, that's not a solution either. Especially when you have to go out and buy all new fonts anyhow, since the macs will not support the Windows postscript typeface formats either.
    After doing a little price shopping for typefaces, I'm trying to try to keep using the few OTF and TTF fonts I've purchased since they're still working, since the prices of fonts these days are astronomical. I've installed a few fonts in the system folder, but too many and Acrobat distiller crashes. It's not cost effective to spend all of your income from design on $1600 font family sets, just to make changes to a document where you might have used a postscript face. Especially in this economy... It's another case of the investor getting rewarded for the release of an application and the customer is left holding the bag. Hopefully it's a bug, but not likely. It's probably some mandated decision by the higher ups in Adobe.
    I'm sure larger companies with hundreds of employees probably have site licenses for typefaces in the OTF format, so for them it's not a problem, and since most people using PCs to do design opted for that platform because of the cost issue, Adobe probably doesn't care about them either. Maybe a solution will arise in the future, but it doesn't look likely. You will probably have to get the new formats of typefaces one by one.

  • Synchronisation problem with deleting an appointment from an iterating appointment

    Hello,
    I have a problem with the synchronisation of appointments from iCal (Mac OS X 10.7.3) to my iPhone 3GS (iOS 5.1) with iTunes (10.6.1 (7)).
    Scenario:
    I create an iterating appointment (e.g. each week) in iCal. Than I synchronise these appointments with my iPhone. After that I delete one specific appointment (not the whole iterating appointments) in iCal and synchronise the calendar via iTunes again.
    Now the appointment I deleted in iCal still exists on my iPhone. If I choose the option "replace all appointments on my iPhone" in iTunes it doesn't work and the deleted appointment still exists in my iPhone calendar.
    Any solutions for this problem? Or is it a known bug?

    Hi,
       try to make the request status into red in monitor and then delete. if the request deletion taking long time try to change the QM status in to green. i think then the delete box will dissaper. again start from begin convert the status to RED in monitor for that particular request. and then delete it.

  • PC Suite connectivity problem with Motorola Blueto...

    My Nokia PC Suite is unable to found installed bluetooth hardware as usually my phone (Nokia E72) too. I'm using Motorola "Bluetooth 2.1+EDR USB Device", which comes with Lenovo S10-3C Netbook. I can pair my phone with my netbook normally and transfer files, connect bluetooth mouse, surf internet  easily. in this combination is it possible to connect with PC Suite without inserting any external USB Bluetooth Adapter ? Please Help me to solve this problem.
    ==============================================
    Nokia PC Suite version 7.1.50.2, English
    PC Connectivity Solution:
    Version 10.21.0.0
    Nokia Connectivity Cable Driver:
    Version 7.1.29.0
    Operating system:
    Microsoft Windows XP 32-bit Edition, Service Pack 3, v.3264
    Language: English
    Language for non-Unicode programs: English
    Detected Internet browsers:
    - Microsoft Internet Explorer 7.0 (Default browser)
    - Mozilla Firefox 3.6
    Detected Bluetooth stacks:
    - Microsoft (Version: 5.1.2600, Build: 3264)
    Motorola "Bluetooth 2.1+EDR USB Device"
    Motorola Bluetooth Software version 3.0.1.237
    vid&pid as details :
    idVendor:           0x0DB0
    idProduct:          0x3801
    ==============================================
    Thank you in advance

    i am having the same problem with my laptop -.-

  • Synchronisation problems with FK

    Hi,
    i'am trying to use Data Modeler and encountered problem:
    At first i imported Data Directory (Oracle 11). Right after that i try to synchronize Model to Data Directory. And i get differences (but nothing is changed in Database or in Model). Every FK in my Model is marked with (!). Why is so? this is bug, or i made something wrong?
    In model compare Every FK has "Primary Key" colored in red and checkbox checked.
    In these links you will find screen shots:
    http://imageshack.us/photo/my-images/827/comparew.jpg/
    http://imageshack.us/photo/my-images/197/ddlot.jpg/
    Also notice the sequence of FK columns in DDL preview! they are wrong!! i tried the same actions in Oracle 9 the problem with differences is the same but, order of columns in FK ddl is right(at least in table i checked).

    Hi,
    Thanks for reporting these problems.
    I assume you are using the latest 3.1.2 patch version. The FK being highlighted incorrectly is an unexpected side effect of an update that went into that release.
    I have logged a bug on the incorrect order of FK columns in the DDL Preview for the Compare/Merge.
    It appears that this problem occurs if the Columns of the referenced Primary Key are not in the same order as in the Table definition.
    David

  • 6230i synchronisation problems with Outlook calend...

    My PC is running Windows XP Professional SP2 PC suite ver is 6.6.18 and I'm connecting via usb cable. My problem is that I can interrogate the phone memory fine, moving files in both directions and synchronise the calendar...... but I can not synchronise recurring events. The events show on the pc calendar but only the first entry is synchronised with the phone any ideas?
    Ian

    The only thing that I can think of is the synchronisation range. When you created the synchronisation settings and selected the calendar items to be included in the synchronisation, what kind of synchronisation range did you specify?
    Perhaps it could help if you specified a longer time period into the future and tried to re-synchronise? Please let us know if this does not help! Then someone else might find another possible solution

  • Synchronisation problem with 3500c (usb)

    Hello,
    I'm using Win XP Home 2002 SP3 and Nokia PC Suite 7.0.8.2 to (try to) synchronise my 3500c with Microsoft Outlook (usb) but it doesn't work. It doesn't give a reason either... just 'could not synchronise'. I used to synchronise my 6230 without any problem the last couple of years. (I did reinstall PC Suite since then so the 6230 is not in the phone list anymore).
    Even if I can't synchronise, I have a connection because I CAN do SMS, MMS, and file transfer using PC Suite...
    I updated my phone software to v7.0 (19-08-08) but this doesn't solve my problem.

    Hello again,
    See this:
    KB16471 BlackBerry Desktop Software prompts that an Internet connection is required to configure synchronization
    Hopefully it contains something useful.
    Good luck!
    Occam's Razor nearly always applies when troubleshooting technology issues!
    If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
    Join our BBM Channels
    BSCF General Channel
    PIN: C0001B7B4   Display/Scan Bar Code
    Knowledge Base Updates
    PIN: C0005A9AA   Display/Scan Bar Code

  • Switching phones synchronisation problem with E71?

    I was using an E71 and i was switching over to use 6500 slide. I tried to transfer all my notes, calender entries, contacts and text messages to the 6500 slide through the "switch phones" synchronisation option. most of them transferred fine, but half the text messages i had didn't. they still remained on the E71 so i could try retransfer but it wasn't a big deal. The problem was that i had 31 notes. and it reported that 1 sent and 30 were deleted. it deleted all 30 notes without any confirmation and so i can't even attempt to re-send it.  so now i don't know how to get the deleted notes back D:
    is there a way to find and restore them ? and why did it suddenly delete? (even though half the text messages sent, HALF the text in each of them were cut off.)
    i've never backed it up on computer or anywhere else too because i didn't expect the notes to ever disappear without confirmation of deletion or anything of that sort .
    i'd be glad if anyone could help T^T

    DO NOT DRAIN your batteries completely, this is anew generation of batteries and it actually is potentially harmful to them to drain empty. it also REDUCES the life of your battery. when the battery gives you the first signs of low batt indication this is a good time with modern batteries to charge. charge it until it says it is full. no need to charge any further than that. batteries come partially charged out of the box these days. plug one into the phone and use it until batt low, charge it to full again and repeat the first three to four times. after that battery is good to go and you no longer have to worry about it. you can charge it as you please, just keep one thing in mind, do not let it discharge completely. 
    You know what I love about you the most, the fact that you are not me ! In love with technology and all that it can offer. Join me in discovery....

  • Synchronisation problems with Outlook

    I installed iCloud on my laptop and synchro with Outlook 2007. A nightmare all my contacts and calender entries were moved from my Personal agenda to iCloud agenda. So I removed iCloud.
    Synchro of contacts is OK but problems for calendar.
    Got the message "CRTanRec::GetLinkedRecordId : Invalid linked Record ID" when I syncronise in both ways.
    And the same message when I do from computer to device of all entries with replace all entries on your device

    The only thing that I can think of is the synchronisation range. When you created the synchronisation settings and selected the calendar items to be included in the synchronisation, what kind of synchronisation range did you specify?
    Perhaps it could help if you specified a longer time period into the future and tried to re-synchronise? Please let us know if this does not help! Then someone else might find another possible solution

  • PC suite syncing problem with nokia 3500

    Hi
    My PC suite connects but is unable to read the phone messages or contacts
    I am unable to sync, take a back-up
    In short I can NOT use the PC suite.. It only says me connected but it does not help me in doing any of the above..
    Can some1 Please help me.. I really love using PC suite since It very convenient ..
    Thanks
    Hoping for a reply soon
    WINDOWS Version- windows 7
    PC suite version-7.1.40.6
    Type of connection- Cable
    I have updated the phone software so sure it not related to updating..

    I also have detected the problem. It is not any physical malfunction according to me. It occures with my phone when I unplug it and plug it again. Sometimes is useful to change the USB port and afterwards to move back to the previous one. Try it and also try it combined with PC restart. It is a weird problem!?

  • Hello, using abode creative cs6 desgin standard suite, face problem with ctlr t tools

    while facing ctrl+t problem i have been advised by the it guy to uninstall adobe photoshop
    from now, i am not able to re-install photoshop as far as abode is not recognizing the serial number
    please help

    Unfortunately, only Adobe customer service can assist you with your issue. These are user forums; you are not addressing Adobe here.
    Click on the link below, and after that click on "Still need Help? Contact us."
    Then on the next page, click Chat
    There is also a phone option.
    http://helpx.adobe.com/contact.html?step=PHXS_downloading-installing-setting-up_licensing- activation

  • PC suite connection problem with 701.

    Hi,
    I've Nokia 701.
    The Nokia PC suite version is 7.1, I'm unable to connect my 701 to PC suite.
    I tried on the desktop and a laptop but it doesn't detect properly. It detects the phone as some "port_something"!
    It could be because of fp2?
    -------------------If this post helped you, click on accept as solution.------------------
    -----------------------------Appreciate by clicking on white star.----------------------------
    Solved!
    Go to Solution.

    @aspergerguy, Thanks for your reply. Everything works fine except on my friends desktop and laptop!
     It did work with my desktop and my laptop this morning,
    On my desktop(Win7 ultimate)
    and on laptop(Win7 HB)
    I wonder why it coulnot work on my friends laptop and desktop, I've installed pc suite myself (version 7.1.51.0) !!?
    On my friends laptop it worked for the first time and on the second day it coulnot work!!!
    -------------------If this post helped you, click on accept as solution.------------------
    -----------------------------Appreciate by clicking on white star.----------------------------

Maybe you are looking for

  • Ipod not being recognised by itunes..but by pc

    Gosh..it seems like a lot of us have problems!! I had everything working fine. Tonight I imported some cds - then I plugged in my mini...ping...(ie connected)..but it's not showing up in itunes. It does show up as an 'e'drive in my computer. I've rei

  • Can someone help me correct this sql statement in a jsp page?

    ive been getting the java.sql.SQLException: Incorrect syntax error for one of my sql nested statements. i cant seem to find similar egs online, so reckon if anyone here could help, really appreciate it. as im putting the nested sql in jsp page, it ha

  • Trouble transferring files etc from old iMac to G4.

    My friend has an old CRT iMac, not sure of the precise model but it's one the fruit coloured ones running OS 10.1. She's upgrading to my old flat panel G4 iMac running 10.4.11 but we've had trouble transferring her files, settings etc. First we tried

  • PO release strategy on effective price

    Dear Experts, Currently PO release strategy is on net price. need to change this to effective price(net price +taxes). can you please give detail steps to change and any impact, if we change now.

  • JDeveloper 11g timeout exception -- 30 seconds limit

    I'm running a long running process and getting the following exception: Caught exception, message is : Transaction Rolledback.; nested exception is:      weblogic.transaction.internal.TimedOutException: Transaction timed out after 32 seconds BEA1-000