Problem with PDF file after saving from MS Word

When I have an image in MS Word and I save to PDF, the page with the image becomes black as you can see the text at the bottom is black instead of white. Also, I have Replace Document Colors active to invert the PDF color. Anyone know why inserting an image messes with the text this way?

Not sure, but it may deal with transparencies if those were used.

Similar Messages

Problem store pdf file after downlod , message memery or store to little, the harddrive hav 1,3TB ;-

problem store pdf file after download from web. Message, store to littel from reader11. Where ist tht problem or the solution?
thanks

Dear Mr Willener
Thanks for the mail, that problem is soluted, press the botton, store as copy.I found it in secound read
A wish: In reader 9 is the solution better.
Regards from Ilmenau
L.Gleichmann
[signature and auto-quote removed by host]

When I attempt to open a PDF file I saved from a website, I get the message "There was an error opening this document. The file is damaged and could not be repaired." Is there any way to correct this problem?

When I attempt to open a PDF file I saved from a website using Safari, I get the message "There was an error opening this document. The file is damaged and could not be repaired." When I save the same PDF file using FireFox it opens up immediately. Is there any way to correct this problem with Safari?

Back up all data.
Triple-click the line of text below to select it, the copy the selected text to the Clipboard (command-C):
/Library/Internet Plug-ins
In the Finder, select
Go ▹ Go to Folder
from the menu bar, or press the key combination shift-command-G. Paste into the text box that opens (command-V), then press return.
From the folder that opens, remove any items that have the letters “PDF” in the name. You may be prompted for your login password. Then quit and relaunch Safari, and test.
The "Silverlight" web plugin distributed by Microsoft can also interfere with PDF display in Safari, so you may need to remove it as well, if it's present.
If you still have the issue, repeat with this line:
~/Library/Internet Plug-ins
If you don’t like the results of this procedure, restore the items from the backup you made before you started. Relaunch Safari again.

We have a mac laptop and dont have any problems with pdf files but our imac will not open them. any suggestions

we have a mac laptop and dont have any problems with pdf files but our imac will not open them. any suggestions?

Back up all data.
In the Finder, select Go ▹ Go to Folder from the menu bar, or press the key combination shift-command-G. Copy the line of text below into the box that opens, and press return:
/Library/Internet Plug-ins
From the folder that opens, remove any items that have the letters “PDF” in the name. You may be prompted for your login password. Then quit and relaunch Safari, and test.
If you still have the issue, repeat with this line:
~/Library/Internet Plug-ins
If you don’t like the results of this procedure, restore the items from the backup you made before you started. Relaunch Safari again.

Problem with PDF files

Hello Experts,
I am having trouble with PDF files corrupting the folder in
which they are contained. If this sounds familiar, and you might be
able to help, please see if the following steps give you an idea of
the problem and the fix.
I want to link to PDF files from a web page. The copy,
consisting of several files, was provided by my client as Word
documents, and converted to PDF by me from within Microsoft Word.
I copied the PDF files into their own folder in my site, and
found later, after leaving, then reopening Dreamweaver, that the
folder was corrupted and unreadable. I got a message to run chkdsk.
I tried working around the folder by repeating the process
above in a new file, with the intention of ignoring the corrupted
one. The second folder also became corrupted.
I don't know if chkdsk is a Dreamweaver utility, or a Windows
utility, or if this is a Windows, Acrobat or Dreamweaver problem.
Does anyone know how to run chkdsk?
Does this sound familiar to anyone? Any ideas?
Thanks so much in advance for the urgently needed support.
Richard

chkdsk used to be a DOS utility, now Windows. Depending on
the OS you have
and whether it's Mac or PC, you can run it several ways.
If XP > Start > Help and Support, type chkdsk in the
search
Other OSs, search for chkdsk.
Jo
"RTalbott" <[email protected]> wrote in
message
news:e91rg5$hkj$[email protected]..
> Hello Experts,
>
> I am having trouble with PDF files corrupting the folder
in which they are
> contained. If this sounds familiar, and you might be
able to help, please
> see
> if the following steps give you an idea of the problem
and the fix.
>
>
> I want to link to PDF files from a web page. The copy,
consisting of
> several
> files, was provided by my client as Word documents, and
converted to PDF
> by me
> from within Microsoft Word.
>
> I copied the PDF files into their own folder in my site,
and found later,
> after leaving, then reopening Dreamweaver, that the
folder was corrupted
> and
> unreadable. I got a message to run chkdsk.
>
> I tried working around the folder by repeating the
process above in a new
> file, with the intention of ignoring the corrupted one.
The second folder
> also
> became corrupted.
>
> I don't know if chkdsk is a Dreamweaver utility, or a
Windows utility, or
> if
> this is a Windows, Acrobat or Dreamweaver problem. Does
anyone know how
> to run
> chkdsk?
>
> Does this sound familiar to anyone? Any ideas?
>
> Thanks so much in advance for the urgently needed
support.
>
> Richard
>

Problems with IMAQ Vision after upgrading from Labview 6i to Labview 6.1

Hi,
We just upgraded from Labview 6i to 6.1.To do this,we uninstalled the 6i version as was suggested by NI and then installed the 6.1 version.Later when we tried to run the old vi's written using Imaq vision, we ran into different problems.Has anyone experienced any similar problems with IMaq vision after upgrading?If so please help me solve this issue.
Thanx
deepak

What kind of problems?
I would strongly suggest that you uninstall IMAQ (all elements) and reinstall them. They register with Windows, probably docked to 6i, and also must be recompiled, which I believe is done in installation.
This is your best bet.
If you still have problems, contact NI and ni.com/ask and start a support inquiry.

Problem with pdf files from ABBYY FineReader 11

I am using htc desire with Android 2.2 with latest update for PDF Viewer.
Recently I scaned book on FineReader 11 with recognition and save it on pdf format with setting to show page pictuire above recognized text. On desktop this file opening normaly, but on PDF Viewer for Android Version 1.00.1045 on my Android device it opening very very slowly and the following pages don't want to open at all. At the same time other pdf files downloaded from Net is opening normaly.
What is the matter of problem, on perfomance (1 Ghz), RAM capacity (512)?
How can I improve pdf files that I can read it on Android? Its imperative to have page picture above (with recognized text above its working very fast).

Please try it on Adobe Reader version 10.1.0 , Please note that this forum is for Adobe Reader on android and not for PDF Viewer.
-vaibhav

Issue with opening .PDF files after recalling from Symantec Enterprise Vault

Good Morning,
I am having issues with opening PDF files that have been recalled from Symantec Enterprise Vault and some of the files are anywhere from 3-4 years old. Some files open, while others return the error: Adobe Reader could not open filename.pdf because it is not a supported file type or might have been damaged. It is inconsistent as to which files it occurs with. I am not ready to believe that I have that many corrupt files out there. I am opening them on a Windows 7 Enterprise SP1 x64 desktop. Adobe 10.1.7. I have already configured the registry setting for bValidateBytesBeforeHeader that I found in another article to no avail.
The files are on a network share, but I also tried copying them to my local desktop and still received the error.
I have seen other posts regarding this error, but do not see a definitive solution and am hoping that in recent days someone has come up with a solution.
Thank You
Brian Dougherty

Not supported file type can (but not always) mean the PDF was created with an old enough version of Acrobat, that it isn't comaptible with reader X or XI.
Might have been damaged is pretty cut and dried in its meaning and interpretation.
There's a known issue with Mac OS and Safari Browser "breaking" PDFs as they download, but it's not so common for Windows. Since these are files you already had, it would be even less applicable.
You can try downloading an older version of Reader to check if it's a compatibility issue, but you'd have to uninstall the latest to do it and it'd be a lot of bother if they still don't open. It would also mean they are "broken" and cannot be repaired, that I know of.

Problem with PDF files opening up in code on IMac OS 10.6.6

Just bought a new IMac three weeks ago (my first Apple Computer after years of using a PC). I've been using their TextEdit program to create simple documents, and routinely save the documents as PDF's to make it easier to share with clients. Everything has worked fine until three days ago - now whenever I open a PDF file it shows up in code. This is happening to documents I created several weeks ago, it is happening to new documents I am creating, and it is happening to PDF files clients are sending to me. (For instance, today I received a PDF file attached to an email from a client - if I hit "quick look" I can view the document with no problem, but if I hit save, or double click the document in order to print, the document shows up in code (and prints in code). Eek! I just spent over an hour with Apple support trying to figure out a solution, but they ended up just as baffled as me, and directed me to call Adobe. Hoping someone can help me figure out what I need to do to resolve this. Thank you!

Thank you George for your response to my plea for help. Late yesterday I was able to get in touch with a friend familiar with Mac and PC and she figured out my main problem was trying to use TextEdit as a primary document program. (She also had me try to open some PDF files with preview, but they still came up as code.) She quickly realized I would be able to open these files in my documents file - I was trying to open them up in the TextEdit program. Anyway, the main thing I'm realizing is I need to get Microsoft Office to avoid these challenges in the future. As you can tell, I'm not up to speed on computer stuff, but my friend said the Apple support guy should have realized right away that using TextEdit the way I was attempting to use it was my real problem, not an issue with Adobe Reader.
Thanks again!

Problem with mp3 files after upgrading to iTunes 8.0

I have the following problem in iTunes after installing the 8.0 version:
I have noticed that certain (mp3 in this case) files do not play or download Album Cover from iTMS.
These files were in normal condition at least 1 day ago, before the update and I can still find them in my iPhone which has not been sync since the iTunes update.
Things I've done before posting:
1. Checked the files that they still exist in their original location as they are set in iTunes preferences.
2. Those files can be played either in Quick Time or in Finder Quick View (and Real Player and VLC).
3. I have restored the mp3 files from Time Machine but no solution found.
4. I have backed up and erased and created a new iTunes Library and tried to import them again on an empty library but nothing happened.
5. The files existed in iTunes (without Artwork which they did have previously) but I could not play them (double-click etc). Then I removed them, I cannot add them again (either by 'Add to Library' or by drag-drop)
6. Of course, I did a volume repair and permissions repair by booting from the OSX install DVD.
(edit) 7. I moved the files on my MacBook Pro and tried to add them in the iTunes there (completely empty and different library). This also had no result...
So after all these, the files are still not accepted in the iTunes but they still exist (and are playable) in my iPhone after yesterday's sync.
Any ideas? because i'm running short atm
Message was edited by: Periclesm

Had the same problem with the new update. I finally got back to my previous version by using system restore. After the restore I had to go to the "All Programs" list and click on Quicktime and iTunes individually to allow them to re-configure, then had to restart the computer again. After that all's well. My lbrary was intact.
I tried everything to get the newest version to work, including completely uninstalling my current versions of QT and iTunes, then downloading the latest directly from the Apple website, but, after 3 attempts, nothing worked. Guess I'll have to wait for the next update and try again.
By the way, your library is not actually stored in iTunes--it is stored in your Music folder, so you should not lose anything by uninstalling iTunes if you need to.

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

N9 and problem with pdf-files

The problem is: I download an pdf file from internet. Filename is containg skandinavian characters which are converted as "%D6 etc." When I try to open the file with N9 I get an error similar to: "file is corrupted, can not open the file". Yet the same file works fine with Nokia C5-00 and with my Macbook laptop. Any idea how to fix this problem?

is the device actually sold in your country of origin, or was it imported.
not that it should really matter, but sometimes could be an issue.
you could also try to rename the file and then try to open it.

Problems opening PDF files after upgrading file server to 2012 R2

Hi,
At the weekend we upgraded our main file server from Windows 2003 to 2012 R2.
Since the upgrade, users (including myself) can only open one PDF document at a time from the file server. If I double click a PDF file, it opens like normal, however If I double click another PDF file, the acrobat reader flashes (in task manager I can see another instance AcroRd32.exe starts and then exits) but the second document doesn't open.
If I close the first document down, and then try and open the second one, then it opens with no problems.
This only affected opening files on the new file server, opening multiple files on a local drive is fine.
If I disable 'enable protected mode at startup' then I can open up multiple documents from the file server. I'd prefer not to have to do this.
The users are using Acrobat Reader 11.0.10 on both Windows 7 64bit and Windows 2008 R2 Remote Desktop.
Does anyone have any ideas what may be causing this? And does anyone have a workaround other than disabling protected mode?
Thanks
Joe

An update...
The new fileserver has a different name than the old server. We have a CNAME alias pointing the old name to the new name.
I only get the problem when accessing the PDF documents with the old name, when accessing via the new name, everything works as expected.
However there are lots of shortcuts and other other links to the old name, so finding a workaround would still be good.
Cheers
Joe

Ouick Time problems with pdf files

Help!! I can't view web pages that contain pdf files in the pdf format; the QT logo appears and I just get a picture of the first page of the pdf. If a download option is available, I can usually get it to download, but if the link takes me to a page where the pfd resides I just get that first-page display. I have tried to keep Acrobat Reader open while accessing the content, but it doesn't help. This happens with Firefox, Safari & Opera.
I need to download some forms to print & fill out, so any help to solve this problem soon would be greatly appreciated!
Thanks all,
Bee

I don't how things got changed, but I have resolved this issue on my computer. After Googling and searching in other forums, etc., here's what I did. I had Reader open. Closed it and relaunched. When it opened I got a message that Adobe Reader was not configured as an "internet helper" and asked if I wanted to repair this. I said yes. Then...since I ticked and unticked various other preferences trying to resolve this, I had to go back to Safari prefs and make sure that Open Safe Files was turned on. I think I quit Safari and restarted. Then it worked!!! Clicked the PDF link and it downloaded as a PDF into my downloads folder. All is back to normal.
Diane Wordsmith
Message was edited by: Diane Wordsmith

HP Officejet100 Mobile L411a intermittent Bluetooth printing problems with PDF files

Hello,
Our company provides computer-hosted medical devices controlled by an application running on Windows7 computers we supply. We are currently using the HP Officejet 100 as a Bluetooth printer. In some of our customer offices, we experience printing problems using the printer in Bluetooth mode (there are never problems if the printer is connected by a USB cable.)
The printing problems typically affect PDF files printed through Adobe Reader 10, and the symptom is one of the following:
Send a print job to the printer. It doesn't print and eventually the print queue shows an "Error Printing" message. If any print jobs are removed and the printer is power-cycled, the problem goes away for the time being.
2. Same as above but power-cycling does not cure the problem and nothing will print, even a test page.
In either of these cases there are no problems if a USB cable is used.
The PDF files we are trying to print are typically 5 pages with 3 of the pages having a lot of graphics and the remainder being text only.
Has anyone seen this behavior and is there anything we can do about it?
Thanks.

I don't anything about this printer, but I do know that bluetooth is really flaky with large files since it's got a crappy transfer rate, could be that the transfer is dropping and freezing the printer up. Does it have encryption turned on?

Problem with PDF file after saving from MS Word

Similar Messages

Maybe you are looking for