![]() If you have any trouble at all getting in touch, please let me know. The most direct way to get in touch is the call the number on this page: Contact QuickBooks TimeĪlternatively, you can initiate a live chat through the QB Time web app by clicking the blue Question Mark icon at the bottom left of the page. I'm confident that our QB Time team will be able to help find a suitable resolution. I understand it's been difficult to communicate with support so far, but our live support team has the tools and secure connection necessary to make account and billing changes that we can not do through the Community. Since that isn't an option for you at this time, the best thing will be to get in touch with one of our QuickBooks Time support agents to discuss that credit and any updated workarounds. At this time, the best solution is still to transition to the Web Connector. I've been keeping a close eye on INV-254 and see that they are still working toward a permanent resolution. Good afternoon Thank you so much for reaching back out. How much longer before this is fixed? I don't want to be tied to my desktop for the entire summer AND I must be able to reliably make payroll. Non-QBD flavor 'wc' is already installed." It will be time to run payroll again soon. Upon attempting to sync QBTime and QB I now get the message "Cannot complete integration. Since I have all three products: QB, QBTime and QBPayroll, I expect them to work together without paying ADDITIONAL money for support for a break that QB acknowledges is their fault. I asked to speack to a supervisor, and one was scheduled to call the next day, but I never heard from them. They also would not offer a credit for not being able to use the product because I didn't have a support plan. They refused to get online with me through logmein, saying they would lose their job for helping me because I hadn't purchased additional support. Since I risked 'totally broken' for 'broken sometimes' I did not make the change. When I consulted with support, they actually told me to get rid of the web connector the previous support person helped me install. Then web connector does not transfer over. Workaround 3 - web connector works.but ONLY if you do not try to back up and restore QB on another device. Workaround 2 - updates have made no difference I have followed them exactly and end up seeing my login name and no way to get into QB Time. Workaround 1 - the instructions do not make sense. Hi there, having same problem, and offer these comments - would appreciate a response from the QB team. I want to ensure that all of your concerns are addressed so that you're able to get back to running your business. Let me know how the phone call or chat goes if you do get in touch with our support team again. I know that you didn't get the help you needed before, but I'm confident mentioning the INV specifically will steer support in the right direction and get you set up successfully. (You'll need support to work with you on these steps) Update QuickBooks Desktop to the latest version and try syncing again.Ĭonnect via Web Connector. Choose My Company and sign in at the top right of the window.In addition, here are some workarounds that could help: The best way to get added to the list of affected users and get updates about this issue via email is by getting in touch with our Customer Support Team. However, there's a resolution that's in progress for the investigation ( INV-00254). Qbs.BeginSession(string.Empty, ENOpenMode.omDontCare) Īny ideas? This is my first QB SDK application, so please let me know if I've perhaps missed an obvious step.Good morning, for joining in on this thread. I never like to hear that our customers had a less than ideal interaction with our Support. ![]() Qbs.OpenConnection2("Application Name", "Application Name", ENConnectionType.ctLocalQBD) IMsgSetRequest requests = qbs.CreateMsgSetRequest("US", 8, 0) QBSessionManager qbs = new QBSessionManager() ![]() The COM exception throws when I try to create an instance of QBSessionManager. I've ensured QBFC is installed and my assemblies are all compiled targeting the x86 platform. ![]() I can't seem to find the common denominator here. This error has been reproduced on various other machines, but I've also had success on various other machines. When spinning up a fresh VM (again with Windows 7, 圆4), I get a COM exception with HRESULT 80040154. In my dev environment (Windows 7, 圆4) everything works as expected. I have a very simple application that connects to QuickBooks, runs a customer query, then disconnects.
0 Comments
Leave a Reply. |