From what i can see in your log it looks like libtdsodbc.so.0 is missing, i had this exact same problem, i solved it by:
1 Googling the actual file name (libtdsodbc.so.0)
2. I found a download of the rpm (freetds .64-7)
ftp://rpmfind.net/linux/fedora/relea...7.fc8.i386.rpm
3. Once the rpm downloaded i moved it to the CentOS desktop by using winSCP.
4. in the centos machine i right clicked the rpm and opened it with archive manager.
5. once the rpm opened I extracted libtdsodbc.so.0.0.0 to the desktop and renamed it to libtdsodbc.so.0.
6. once it was renamed I moveed it to /root/ep2/usr/lib.
7. I cleared my logs and restarted the cabal services.
thats what stopped the DB connect errors for me..
The getq errors in my experience are a result of the DB errors, once the server is able to connect to your DB the getq and port listen errors (if you have any) should stop, if not a service cabal restart should fix it..
also i just fixed my provider string in SQL (as my earlier post describes) what i did was
DRIVER={SQL Server};SERVER="Windows IP Here";UID=;PWD=;
not too sure how much help i can be but im a quick learner and know how i fixed my own problems at least :P