• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 404
  • Last Modified:

ODBC connection failing

We are running ACT 2010; MS ACCESS 2007 on Win 7 PC's.  ACCESS has been programed using ACCESS and Visual Basic to link to data from ACT.  ACT is resident database; ACCESS is the reporting tool for Data.

ACT/ACCESS marriage worked perfectly on a Win 2003 server environment.  We recently upgraded PDC to Win 2008.  All converted perfectly but ACT/ACCESS.  Took some time to get SQL happy.  ACT is now working OK (although much slower than previously).  ACCESS is issue.  We cannot get ACCESS to stay connected to the ODBC.  Connection is inconsistent from user to user / desktop to desktop.  Error msg:  cannot connect to ODBC.  Sometimes you get error - other times you don't.  If you click OK (once or numerous time) you may evenutally connect.  Sometimes you can connect to the application ok, but when you navigate to a different section of the application, the connection fails.

IT have given up and say it is NOT server related.  The ACCESS programmer cannot find anyting correct or wrong with the coding.

All are frustrated and at a loss.  Help
0
max-a-million
Asked:
max-a-million
  • 3
  • 2
1 Solution
 
Netman66Commented:
Try recreating the ODBC connection using the 32-bit tool found here:  C:\Windows\SysWOW64\odbcad32.exe


I suspect it's a 64-bit to 32-bit app issue.

0
 
max-a-millionAuthor Commented:
Thank you for responding.  I'll try this this morning and get back to you. This issue has some very GOOD IT pros totally stumped.
0
 
Mike LazarusAct! Evangelist - CRM ConsultantCommented:
If that didn't help:
1. What full version of server OS - SP1, R2, x32 or x64?
2. What version of SQL - 2005Ex (as shipped) or x64 or 2008?
3. What ver/build of ACT! (from Help About)? If not 12.1, apply SP1. If 12.1, but not hotfix 5, apply hotfix5... note ALL systems sharing database (LAN or Sync) must be on same build

Also, is that the full error?
Any error in event log (client or server)?

Any reason you're using ODBC? OLEDB is usually easier
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
max-a-millionAuthor Commented:
Thank you for your comments.  As it turns out, the problem was identified and resolved as follows.
IT had already considered the 32/64 bit conflict.  Appreciate your response.

                This problem occurs because the TCP Chimney Offload feature is enabled on the server. The TCP Chimney Offload feature is enabled by the Windows Server 2003 Scalable Networking Pack.
Typically, this problem occurs when the network adapter uses the Broadcom 5708 chipset. For example, the following network adapters use the Broadcom 5708 chipset:
•      Broadcom NetXtreme II
•      Hewlett-Packard NC373i Multifunction Gigabit Server Adapter
0
 
max-a-millionAuthor Commented:
I was the one who solved the issue.
0

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now