asked on

Is anybody familiar with T-HUB?

This is a long shot since it involves a little used application but I have a customer who is desperate. He has a Server 2008 R2 server uses an application called T-HUB which posts to QuickBooks POS. Or, rather, it used to. When Inuit upgraded POS to 18 the function stopped working from workstations, but continued to work on the server. T-HUB support worked for days on the issue and sent instructions for IT (that's the company I work for). The last thing on the list was to uninstalled and reinstalled QuickBooks POS. After that the two applications won't work together even on the server. I haven't called Intuit because it's really not a problem with their application. T-Hub support has pretty much abandoned it. I started to think maybe I could find some generic info on the failed SQL connection at the root of the problem but have had no luck. I'm weak on SQL. I've included the error messages from the T-HUB log ans the the FAQ they referred to. If anyone is familiar with this issue or can shed any light or point me in a direction. I would appreciate it and my customer would appreciate it.

Message: Can't connect to the database
at Interop.qbposfc2.IQBPOSSessionManager.BeginSession(String qbFile)
at Turbo.THUB.QBProcess.QBPOSSyncManager.OpenQBPOSSession()

Message: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

https://support.atandra.com/article/94-unable-to-connect-qb-pos-to-thub

Raja Jegan R

>> A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

Above error message is generic one and you can follow the steps mentioned in the below article to fix it out..
Kindly try the steps mentioned and let us know if you still have any connectivity issues to SQL Server.
https://www.mssqltips.com/sqlservertip/2340/resolving-could-not-open-a-connection-to-sql-server-errors/

Bill Bach

From a client side, you should be able to run a tool like Wireshark (wireshark.org) and see what types of network connection attempts it is making. Sadly, this is only haf of the picture -- you really need a clean, working system to compare it to. Perhaps the T-HUB people can get you a Wireshark trace from their own system, or you might need to set up a test environment with QB2017 Client and Server to see what it looks like when it is working correctly. Usually, you can see some sort of crucial difference in the connection.

Failing that, you can also look at internal accesses of files and the like, using a tool like Process Monitor (sysinternals.com). Again, compare a working and non-working system and see how they differ. It won't be easy or straightforward, but you might be able to divine some clue about the environment where these traces diverge.

Eric Thibodeaux

ASKER

I appreciate your response. I may be able to set up a standalone test environment.

This question needs an answer!

Become an EE member today

7 DAY FREE TRIAL

Members can start a 7-Day Free trial then enjoy unlimited access to the platform.

View membership options

Learn why we charge membership fees

We get it - no one likes a content blocker. Take one extra minute and find out why we block content.