Problem with some queries after migration from MS Access

Hi everyone!
We've just finished a migration from a MS Access database and we notice some errors when running some queries like :
Query1:
SELECT A.field1, A.field2, B.field1 as FieldTmp
FROM A,B
where (B.field1 <=10);
Query2:
SELECT Query1.field1, Query1.field2, Query1.FieldTmp
FROM Query1 LEFT JOIN Table3
ON (Table3.field1 = Query1.Field2) AND
(Table3.field5 = Query1.FieldTmp)
WHERE ((Table3.field5) Is Null)
ORDER BY Query1.field1, Query1.FieldTmp;
The Query1 runs as expected, but when I try to run the Query2 I got a ORA-00904 error message. If I remove the (Table3.field5 = Query1.FieldTmp) statement or modify to compare with another field (as instance, field2) everything goes fine.
If I modify the first query to a make-table query, the Query2 request runs as desired too.
Is there anything that we can do to keep the queries statement as it is when using the MS Access DB?
Thanks in advance,
Elaine Viel Denadai

Hi Turloch! Thanks for your help!
Those SQL Statements were extracted from the MS Access application that we will continue to use to access the data , now on an Oracle Database.
I don't know what I can do to make this kind of statements works as it is on Access database. The first query, that I called Query1 works fine on Oracle, I just mentioned it because the 2nd Query , named Query2, use it.
I'm not able to understand why when I change the 1st. query to a "make-table" query the Query2 works as desired, but if I keep the Query1 and Query2 as it is on the MS Access Application I got the ODBC error message and the ORA-00904 error message , related (I think!) to the FieldTmp field used on the LEFT JOIN statement (AND).
As I told before, if I change the AND clause to compare to another field, as instance, field1 :
FROM Query1 LEFT JOIN Table3
ON (Table3.field1=Query1.Field2) AND
(Table3.field5 = Query1.Field1)
it works.
Please, is there anything that I can do to keep the MS Access Application unchanged?
Oracle = 8.1.6
Oracle ODBC Driver = 8.1.6.4
Oracle Migration Workbench = 1.3.1
Thanks in advance,
Elaine Viel Denadai

Similar Messages

  • Problems with german umlauts when Migration from MS Access to Oracle

    When I make a Migration from MS Access 97 to Oracle 8.1.5, I have Problem with the germans characters (umlauts). The Oracle is using the rigth character Set for german characters. What can I do? Is it e problem from the MS Access ODBC Driver or the Oracle ODBC Driver?

    Is your character set for Oracle set up to UTF8??

  • Problem with method action after migrating from TP2 to TP4

    Hi,
    we are migrating our application (ADF Faces, ADF BC) from TP2 to TP4. We have encountered several problems.
    The biggest that we could not solve is as following:
    In our View Object's RowImpl.java classes we have method void refreshLOVAccessorQueries(). In a number of View Objects that method is placed in client interface. In pageDefs of jspx pages that are bound to that View Objects we have method action like
    <methodAction IterBinding="TeeCronTtVOIterator"
    id="refreshLOVAccessorQueriesCron"
    InstanceName="bindings.TeeCronTtVOIterator.currentRow"
    DataControl="TradingAppModuleDataControl"
    RequiresUpdateModel="true" Action="invokeMethod"
    MethodName="refreshLOVAccessorQueries"
    IsViewObjectMethod="false" IsLocalObjectReference="true"/>
    and invoke action like
    <invokeAction id="refreshCronLOVs" Binds="refreshLOVAccessorQueriesCron"
    Refresh="prepareModel"
    RefreshCondition="#{!requestContext.postback and empty bindings.exceptionList}"/>
    When we are accessing such a jspx page the application rases error:
    "Method bindings.TeeCronTtVOIterator.currentRow.refreshLOVAccessorQueries() not supported "
    In TP2 everything worked fine. Now in TP4 for some VO that refresh is OK and for others just mentioned error is thrown. Confusing is that all View Objects and their java classes are created in the same manner and they are almost identical, and this counts for pageDefs too.
    What could be the reason of all this?
    Second thing is that in adfc-config.xml in backing bean defs we have managed-property like:
    <managed-bean>
    <managed-bean-name>regionBacking</managed-bean-name>
    <managed-bean-class>app.view.backing.RegionBacking</managed-bean-class>
    <managed-bean-scope>request</managed-bean-scope>
    <managed-property>
    <property-name>bindings</property-name>
    <value>#{bindings}</value>
    </managed-property>
    </managed-bean>
    JDeveloper warn us about that with: ' EL token bindings" is unknown '. Why is that? It looks that everything connected with that managed property works fine.
    Another problem is not severe but unpleasant
    After migration to TP4 nothing (not one element) is visible (shown) in the design view.
    The structure of the pages is similar as in the StoreFrontDemo and it shows just fine in TP2.
    Thanks!!!

    Thanks Frank,
    but working from beginning is to much work so, we have solved it in another way.
    Regard to first problem we discovered that it is happening only when there is no Rows in iterator for which we are invoking action. In invoke action we have changed refresh property to default value and the problem is solved.
    Second thing is warning that has no other effect so we will ignore it.
    About third problem, when we create new working copy of application in JDeveloper without system11.1..... directory, JDev works fine and all jspx pages are shown in design view. After some work, due to undiscovered reason design view is lost... What could cause this?
    Maxa

  • Problem with "missing" songs after migrating from Win PC to Macbook

    Hello,
    I'm trying to move my daughter's iTunes library from her old Win PC to her new Macbook Pro. I mostly got it right, but there are roughly 100 songs which do not play because they cannot be found. I can click through each and "find" them for iTunes, such that they will work, but is there a way to do this globally at once?
    I suspect it has something to do with "Consolidate Library", but I can't quite seem to make that work. How can I tell the Mac to search out ALL missing songs and reconnect them (or even move the files all to the iTunes folder)?
    I think I should have done a “Consolidate” on the old machine first, but is there a way to salvage this without starting completely from scratch?

    Authorize the computer.
    iTunes Store: About authorization and deauthorization - http://support.apple.com/kb/HT1420 - and another helpful post: https://discussions.apple.com/message/17828050

  • Problem with national fonts after migration 9i- 10g

    I'm after migration from Developer Suite 9i to 10g. I see that all Polish characters are replaced with '?'. This problem is only in 10g Designer (before migration all were OK).
    I've tried setting NATLNG to POLISH_POLAND.EE8MSWIN1250 in Forms Generator. In Windows registry is POLISH_POLAND.EE8MSWIN1250 (setting by DS10g setup).
    I've tried fonts via Options->Color/Font/Style - I see change on Display view but '?' are still after saving changes and generating form.

    Thanks knordstrand.
    Problem's resolved yet. You're right - wrong charset on bd.
    Close topic

  • 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.

  • Problems with time characteristics after migration to BI 7.0

    Hi,
    Our company migrated from BW 3.1 to BI 7.0 Netweaver 2004s recently.
    After the migration we have problems with various time characteristics like 0CALMONTH, 0CALQUARTER, etc. in the Query Designer.
    In the old BW3.1 Query Designer version we could choose at the properties of an time characteristic to display Key, Key and Text, Text and so on. After the migration to BI 7.0 we now can only choose Key.
    The InfoObject definion of the time Characteristics in RSD1 is the same in the old version and in the new version.
    I am very  grateful vor every hint how i can show again the other display options in the properties, so that our powerusers can build their queries in the way they are use too.
    Thanks
    Ralph Nist

    Hi Pom,
    thanks for your answer, but we are on FEP 10 already.
    So must be something else.
    Cheers
    Ralph
    Message was edited by:
            Ralph Nist

  • 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

  • Outlook can't connect with Exchange 2013 after migration from Exchange 2007

    <style type="text/css">P { margin-bottom: 0.21cm; }</style>
    Hello,
    recently we've done a Exchange 2007 sp3 to 2013 sp1. Users can conect perfectly with OWA and with his iphone clients.
    But the problem is they can't connect from his Outlook clients (2010, 2013), both internaly and externaly. Always fails with the message: The Connection to Exchange it is not avaliable.... Can't resolve the name of Exchange server.
    To try to resolve it we've done:
    - Check Outlook anywhere configuration en EAC: it is configure with and external url mail.company.com and internal server.domain.local. The security is the default Negociation, but we've tried all.
    - Check the internal dns, there are records for mail.company.com and exchangeserverdomain.local pointing to the exchange local ip. Also there is a public zone company.com with the record mail.caompany.com pointing to the exchange local ip. Also we've made
    records autodiscover.company.com and autodiscover.domain.local pointing to the exchange local ip.
    - In the public dns from our domain there is the record A and MX pointing our public ip. There aren't any record Autodiscover but we think that the manial conection should work.
    Check certificates: we've made a new self-signed certificate including all this internal and external domains and for all services.
    - Check Outlook Anywhere block: we've cheked.
    Currently server state:
    - Old Exchange 07 server can't start, it was in very bad state and we achieved migrate the mailbox to the new server, after that we tried to uninstall, but it crashes with a public folder replication error. We got uninstall all the roles
    unless the mailbox. After a restart it can't start.
    -The new Exchange 2013 looks great, there isn't any trail of the old server, or we haven't seen anything in the EAC or shell.
    I paste below the result of Microsoft Remote conectivity analaizer, with Outlook anywhere test. It is clear that there is a problem with that.
    Sorry because the test is in spanish and I translated it with google, from here I only can access the tool in spanish.
    We continue to try to resolve the problem.
    Thanks to all in advance!
    Testing RPC / HTTP connectivity.
    Error in testing RPC / HTTP.
    additional Details
    Elapsed time: 24295 ms.
    Test steps
    Connectivity Analyzer Microsoft is trying to test Autodiscover for [email protected] .
    Error in automatic detection test .
    additional Details
    Elapsed time: 24294 ms.
    Test steps
    Attempting each method of contacting the Autodiscover service .
    Failed to properly contact the Autodiscover service using all methods.
    additional Details
    Elapsed time: 24294 ms.
    Test steps
    Trying to prove possible Autodiscover URL https://empresa.com/AutoDiscover/AutoDiscover.xml
    Error in testing this potential Autodiscover URL .
    additional Details
    Elapsed time: 1509 ms.
    Test steps
    Attempting to resolve the host name in DNS empresa.com .
    The host name is resolved correctly .
    additional Details
    IP addresses returned : 80.36.252.194
    Elapsed time: 507 ms.
    Testing TCP port 443 on the host to ensure empresa.com listening or is open.
    The port was opened successfully.
    additional Details
    Elapsed time: 464 ms.
    Testing the SSL certificate to make sure it is valid.
    The SSL certificate is not exceeded one or more certificate validation checks .
    additional Details
    Elapsed time: 537 ms.
    Test steps
    Connectivity Analyzer Microsoft is attempting to obtain the SSL certificate from remote server on port 443 empresa.com .
    Connectivity Analyzer Microsoft successfully obtained the remote SSL certificate.
    additional Details
    Remote Certificate Subject : CN = mail.empresa.com , issuer : CN = mail.empresa.com .
    Elapsed time: 454 ms.
    Validating the certificate name .
    The certificate name was validated successfully .
    additional Details
    Hostname empresa.com was found at the entrance of the alternative subject name of the certificate.
    Elapsed time: 1 ms.
    Is validating the trusted certificate .
    Validation Error trusted certificate.
    Test steps
    Connectivity Analyzer Microsoft is trying to build certificate chains for certificate CN = ​​mail.empresa.com .
    Could not build a certificate chain for the certificate.
    Tell me more about this issue and how to resolve
    additional Details
    The certificate chain did not end in a trusted root . Root = CN = mail.empresa.com
    Elapsed time: 31 ms.
    Trying to prove possible Autodiscover URL https://autodiscover.empresa.com/AutoDiscover/AutoDiscover.xml
    Error in testing this potential Autodiscover URL .
    additional Details
    Elapsed time: 21723 ms.
    Test steps
    Attempting to resolve the host name in DNS autodiscover.empresa.com .
    The host name is resolved correctly .
    additional Details
    IP addresses returned : 46.16.56.40
    Elapsed time: 498 ms.
    Testing TCP port 443 on the host to ensure autodiscover.empresa.com listening or is open.
    The specified port is blocked , not listening or does not generate the expected response .
    Tell me more about this issue and how to resolve
    additional Details
    Network Error communicating with the remote host.
    Elapsed time: 21224 ms.
    Attempting to contact the Autodiscover service with the HTTP redirect method .
    Error when trying to contact the Autodiscover HTTP redirect method .
    additional Details
    Elapsed time: 606 ms.
    Test steps
    Attempting to resolve the host name in DNS autodiscover.empresa.com .
    The host name is resolved correctly .
    additional Details
    IP addresses returned : 46.16.56.40
    Elapsed time: 14 ms .
    Testing TCP port 80 on the host to ensure autodiscover.empresa.com listening or is open.
    The port was opened successfully.
    additional Details
    Elapsed time: 202 ms.
    Connectivity Analyzer Microsoft is checking the automatic detection of host empresa.com for an HTTP redirect to the Autodiscover service.
    Connectivity Analyzer Microsoft could not get a HTTP redirect response for Autodiscover .
    additional Details
    Web exception occurred because an HTTP 404 response was received - Unknown NotFound . Headers received: Connection : close Content- Length: 1209 Content- Type: text / html Date: Wed, 12 Mar 2014 15:27:58 GMT Server : Apache/2.2.9 (Debian ) PHP/5.2.6-1 +
    lenny3 with Suhosin -Patch X -Powered -By : PHP/5.2.6-1 + lenny3 HTTP Response Headers : Connection : close Content- Length: 1209 Content- Type: text / html Date: Wed, 12 Mar 2014 15:27: 58 GMT Server : Apache/2.2.9 (Debian ) PHP/5.2.6-1 + lenny3 with
    Suhosin -Patch X -Powered -By : PHP/5.2.6-1 + lenny3
    Elapsed time: 388 ms.
    Attempting to contact the Autodiscover service using the method of DNS SRV redirect server.
    Connectivity Analyzer Microsoft could not contact the Autodiscover service using the DNS SRV redirect method .
    additional Details
    Elapsed time: 186 ms.
    Test steps
    Trying to find the SRV record in DNS _autodiscover._tcp.empresa.com .
    Not the Autodiscover SRV record in DNS found .
    Tell me more about this issue and how to resolve
    additional Details
    Elapsed time: 186 ms.
    Checking for a CNAME record for Autodiscover in DNS for your domain " empresa.com " to Office 365.
    Could not validate the Autodiscover CNAME record in DNS. If your mailbox is not in Office 365 , you can ignore this warning.
    Tell me more about this issue and how to resolve
    additional Details
    No Autodiscover CNAME record for your domain ' empresa.com ' .
    Elapsed time: 268 ms.
    jspt

    Hello,
    We have the Self-signed certificate that comes with Exchange, and we've created a new self-signed including all our domains mail.company.com, domain.local, exchange13.domain.local, autodiscover.company.com, autodiscover.domain.local.
    below I print you the result os the comand Get-ClientAccesServer | fl . Now we've configured a SPC objetct folow the instructions of Wizard
    Exchange Server Deployment from Microsoft. We've executed the commands in our new Exchange 13, but can't did it in the old Exchange:
    $AutodiscoverHostName = "autodiscover.contoso.com"Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like "Version 8*") -And ($_.ServerRole -Like "*ClientAccess*")} | Set-ClientAccessServer -AutoDiscoverServiceInternalUri https://$AutodiscoverHostName/Autodiscover/Autodiscover.xmlThis is the result of
    RunspaceId                           : 89c86f8e-d156-4480-b31d-59215976879b
    Name                                 : EXCHANGE13
    Fqdn                                 : EXCHANGE13.domain.local
    ClientAccessArray                    :
    OutlookAnywhereEnabled               : True
    AutoDiscoverServiceCN                : EXCHANGE13
    AutoDiscoverServiceClassName         : ms-Exchange-AutoDiscover-Service
    AutoDiscoverServiceInternalUri       : https://autodiscover.company.com/Autodiscover/Autodiscover.xml
    AutoDiscoverServiceGuid              : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
    AutoDiscoverSiteScope                : {Nombre-predeterminado-primer-sitio}
    AlternateServiceAccountConfiguration :
    IsOutOfService                       : False
    WorkloadManagementPolicy             : DefaultWorkloadManagementPolicy_15.0.825.0
    Identity                             : EXCHANGE13
    IsValid                              : True
    ExchangeVersion                      : 0.1 (8.0.535.0)
    DistinguishedName                    : CN=EXCHANGE13,CN=Servers,CN=Exchange Administrative Group
                                           (FYDIBOHF23SPDLT),CN=Administrative
    Groups,CN=First Organization,CN=Microsoft
                                           Exchange,CN=Services,CN=Configuration,DC=domain,DC=local
    Guid                                 : e83055fe-217b-4ed6-9cd0-7711097baf99
    ObjectCategory                       : domain.local/Configuration/Schema/ms-Exch-Exchange-Server
    ObjectClass                          : {top, server, msExchExchangeServer}
    WhenChanged                          : 09/03/2014 12:46:07
    WhenCreated                          : 08/03/2014 19:15:54
    WhenChangedUTC                       : 09/03/2014 11:46:07
    WhenCreatedUTC                       : 08/03/2014 18:15:54
    OrganizationId                       :
    OriginatingServer                    : severdc.domain.local
    ObjectState                          : Unchanged
    I hope this stuff can help you.
    Thanks!!
    jspt

  • Performance issue with view selection after migration from oracle to MaxDb

    Hello,
    After the migration from oracle to MaxDb we have serious performance issues with a lot of our tableview selections.
    Does anybody know about this problem and how to solve it ??
    Best regards !!!
    Gert-Jan

    Hello Gert-Jan,
    most probably you need additional indexes to get better performance.
    Using the command monitor you can identify the long running SQL statements and check the optimizer access strategy. Then you can decide which indexes might help.
    If this is about an SAP system, you can find additional information about performance analysis in SAP notes 725489 and 819641.
    SAP Hosting provides the so-called service 'MaxDB Migration Support' to help you in such cases. The service description can be found here:
    http://www.saphosting.de/mediacenter/pdfs/solutionbriefs/MaxDB_de.pdf
    http://www.saphosting.com/mediacenter/pdfs/solutionbriefs/maxDB-migration-support_en.pdf.
    Best regards,
    Melanie Handreck

  • Problems with iTunes account after migrating to iCloud

    I've been using my iTunes account with a specific credit card for many years without any problem. After I migrated from MobileMe to iCloud aprox. 1 month ago every time I try to pay for an app, song or iBook I get an error message telling me that the postal code of my account doesn't match the one inth bank records. I've checked and the postal code is OK (is the same I've been using for years!). What could be the problem?

    The following article(s) may help you.
    Credit card security code or postcode issues.

  • Problems with custom authentication when migrating from 3.2 to 4.1.1

    Hi,
    we’re about to upgrade our APEX instances to 4.1.1 and to migrate our applications. I encountered some problems with our custom authentication schema.
    1.     Recognize already authenticated sessions: in 3.2 the sentry function could return false as long as the user was not authenticated. Public pages could still be displayed (including the login page). The result of the function apex_custom_auth.is_session_valid returned false until once the sentry function returned true. How can I recognize non authenticated sessions in 4.1.1? I looked for the test the Condition “User is the public user (user has not authenticated)” computes on a page but didn’t found the right one. It’s not what docu states here (comparison with the public user): http://docs.oracle.com/cd/E23903_01/doc/doc.41/e21674/condition001.htm#HTMDB25943. I replaced the test with p_authentication.username = ‘nobody’. It works. But that doesn’t seem to me to be the right way …
    2.     Post_logout lacks session context: the Post Logout Procedure does not receive a session_id and username. Neither the V(‘APP_SESSION’) nor p_authentication.session_id are set. This applies to both plugin authentication schemes and non-plugin custom authentication schemes. Is there another way to obtain the logged-out sessions infos or is this a bug?
    See apex.oracle.com for a demo, workspace WS_MW, gast/gast. Can someone please guide me the way?
    Michael

    Hello again,
    there are no replies until now .... I reviewed some posts regarding custom authentication again and did not find any solution for the issues. Found some that worked with APEX 3.2.1 but not with 4.1.1. I can only work around
    1.) in an insecure way, because the non documented (?) user "nobody" can change and all new sessions will be considered authenticated
    2.) in a way, that ends up in implementing the logout from the non apex environment outside the authentication schema or authentication plugin.
    May be I should contact support for at least the second issue because this doesn't work as documented or am I doing something wrong?
    Michael

  • Problem with Photoshop CS4 after migration to new Mac

    I just migrated from an old Mac to a new Macbook Pro running Mavericks. I'm having a problem with Photoshop CS4. Specifically, two things:
    1) When I open an image in Camera Raw, I get this error:
    Fatal error - missing component
    /Library/Application Support/Adobe/Adobe Version Cue CS4/Client/4.0.0/VersionCue.framework
    2) When I try to save anything, it tells me it can't because of a program error.
    I've looked around for a solution. Apparently I had to install Java, but that hasn't solved the issue. A couple of people mentioned that reinstalling would work for a similar problem. My problem with that is that my disk is on the other side of the world and my new macbook doesn't have a disk drive anyway. So I logged into my Adobe account hoping to see a download link for software I have licences for, but there isn't one.
    So my question is firstly, whether there is a simpler solution to the errors I am getting and, if not, if there's a solution to reinstalling Photoshop CS4 without the disk.
    Thanks!

    Did you use Apple's migration tool?  It misses a lot of support files, especially in the Application Support directories.
    You'll have to copy those files manually, or reinstall the app.

  • Problem with Java Script after upgrade from BW 3.5 to BI7

    Dear Colleagues,
    We're facing the issue with Java Script after upgrade of BW 3.5 to BI7.
    Just after update we checked the basic functionality and it occured that some of web templates that use Java Script don't work. They generate seelction screen, but after selection the screen becomes blank without any error messages.
    We're currently stucked since web templates weren't converted to BI7 version so they should work exactly as before the upgrade.
    We compared the Java code with other environment that was not upgraded - it's perfectly the same.
    The only explanation that comes to my mind is that some Java Script settings on the server level were changed during the upgrade but I have no idea where I can check that.
    Thanks in advance for any suggestions,
    Andrzej Bobula

    Hi Deepu,
    Thanks, it was great to read your reply and then few minutes later talk to you live on SDN Day!
    Unfortunately, http cache clean-up did not help. But there is another funny thing I found - for exactly the same 3.5 webtemplate html code returned from WebAS 3.5 was different then from 7.0.
    Unfortunately, this editor does not allow to paste complete code, even in CODE brackets, but here are main differences:
    <b>3.5</b>
       if (navigator.appName == "Microsoft Internet Explorer")
    <frame src="/sap/bw/BEx?SAP-LANGUAGE=E&PAGENO=1&REQUEST_NO=1&CMD=GET_TEMPLATE"
    name="Content">
    and
    <b>7.0</b>
       if (navigator.appName.indexOf("Microsoft Internet Explorer")!=-1)
    <frame src="/sap/bw/BEx?SAP-LANGUAGE=E&PAGENO=8&REQUEST_NO=0&CMD=GET_TEMPLATE"
    name="Content" 0nLoad="javascript:loadTitle()">
    (I intentionaly put 0 i/o o in 0nLoad, otherwise Forum's editor does not accept the text.
    How about SAP's claim that technical upgrade from 3.x to 7.0 changes nothing?
    Regards,
    Vitaliy

  • Problem with some apps after upgrade to 5.1 (can I downgrade it to 5.0 ??)

    Dear all,
    I'm experiencing some problems with apps after upgrading to 5.1, some of them just got stucked or not even start up. Is there a way of fixing this or downgrade to 5.0 ??
    Thanks

    you cannot downgrade, sorry.

Maybe you are looking for