Home Forums CoreObjX / DB Can't Connect to QB

This topic contains 11 replies, has 2 voices, and was last updated by  MariaHenderson 1 month, 2 weeks ago.

Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • #19001

    MariaHenderson
    Participant

    One of my customers just upgraded to a Server2016 server, with the latest QB Enterprise edition. I’m running Coreobjx70. It will connect with QB to ask for permission to access QB, but when I try to Connect, the company object comes back empty. Is there something new here that is making this not work?

    Attachments:
    You must be logged in to view attached files.
    #19008

    are you connecting to QB direct from CoreObjx70 or are you using another software to do so? Because it is giving an invalid certificate.

    #19011

    MariaHenderson
    Participant

    Yes, I’m using my application. But it’s never required a valid certificate before. I set up QB to not require it.

    #19013

    it is asking for:
    20170928.210250 I 4392 CertVerifier The file does not contain an Authenticode signature.

    #19034

    MariaHenderson
    Participant

    I reestablished the permissions in QB for my app to access the file. I went through all the steps, including saying OK when it asked for permission to allow an unsigned app. Does QB 2017 now require a certificate? We’ve never used one before, using Coreobjx for many years.

    #19036

    Can you screenshot the error and post it please?

    #19037

    MariaHenderson
    Participant

    It doesn’t come back with an error. It just doesn’t connect. The QBConnection object has empty company path, and the company object is null. I’m having trouble error trapping on the Connection object itself. My documentation is completely out of date, so it’s hard to figure out what to look for.

    #19038

    I will look into. I will keep you posted. Sorry for inconveniences.

    #19049

    MariaHenderson
    Participant

    I’ve been playing with different options:

    First I set up permissions in QB for my app to connect even when QB is not running, having it log in as the Admin QB user. I tried connecting while QB was still open. This is the qbsdklog:

    20171002.175723 I 7216 RequestProcessor ========= Started Connection =========
    20171002.175723 I 7216 RequestProcessor Request Processor, QBXMLRP2 v13.0
    20171002.175723 I 7216 RequestProcessor Connection opened by app named ‘shutterpro’
    20171002.175723 I 7216 CertVerifier The file does not contain an Authenticode signature.
    20171002.175724 I 7216 RequestProcessor OS: Microsoft Standard Edition (build 9200), 64-bit
    20171002.175724 I 7216 RequestProcessor Current User is in AdminGroup
    20171002.175724 I 7216 RequestProcessor Current Process Integrity Level : 2000
    20171002.175727 I 7216 RequestProcessor Getting the IUnknown COM instance of QB
    20171002.175727 I 7216 RequestProcessor Opening the file in the DoNotCare mode.
    20171002.175732 I 17312 CertVerifier The Authenticode signature validated OK.
    20171002.175734 I 7216 RequestProcessor Connection closed by app named ‘shutterpro’
    20171002.175734 I 7216 RequestProcessor ========== Ended Connection ==========
    20171002.175734 I 7216 RequestProcessor “EndSession” has not been called.

    Then I close QB and tried again:

    20171002.175739 I 7216 RequestProcessor ========= Started Connection =========
    20171002.175739 I 7216 RequestProcessor Request Processor, QBXMLRP2 v13.0
    20171002.175739 I 7216 RequestProcessor Connection opened by app named ‘shutterpro’
    20171002.175739 I 7216 CertVerifier The file does not contain an Authenticode signature.
    20171002.175739 I 7216 RequestProcessor OS: Microsoft Standard Edition (build 9200), 64-bit
    20171002.175739 I 7216 RequestProcessor Current User is in AdminGroup
    20171002.175739 I 7216 RequestProcessor Current Process Integrity Level : 2000
    20171002.175739 I 7216 RequestProcessor Quickbooks is not running currently
    20171002.175739 I 7216 RequestProcessor Launch a new instance of Quickbooks
    20171002.175741 I 7216 RequestProcessor Getting the IUnknown COM instance of QB
    20171002.175741 I 7216 RequestProcessor Opening the file in the DoNotCare mode.
    20171002.175748 I 31428 CertVerifier The Authenticode signature validated OK.
    20171002.175751 I 7216 RequestProcessor Connection closed by app named ‘shutterpro’
    20171002.175751 I 7216 RequestProcessor ========== Ended Connection ==========
    20171002.175751 I 7216 RequestProcessor “EndSession” has not been called.

    It looks like the certificate is not the problem.

    #19062

    MariaHenderson
    Participant

    Any ideas? My customer is getting anxious to close the month out!

    #19074

    TO be honest, I have no idea what is going on there. Your logs don’t say much. You will have to purchase a phone call support: http://synergration.com/support/

    Best Regards,

    #19086

    MariaHenderson
    Participant

    I purchased a phone call yesterday — when can I expect a response?

Viewing 12 posts - 1 through 12 (of 12 total)

You must be logged in to reply to this topic.