[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2193
  • Last Modified:

Access 2010 - DIAG [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed (0)

Hello Friends,

Both of my coworkers in our Accounting department have been running into this error message whenever they would run a query within Access 2010 against our ERP SQL database:  Microsoft Access ODBC—call failed. [Microsoft] [ODBC SQL Server Driver][SQL Server] Incorrect syntax near ‘POFVM’. (#102).

I’ve checked that they have the correct System DSN installed.  Also, I ran a trace in which this line caught my attention:  DIAG [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed (0).
 
I’d really appreciate any assistance or pointers in troubleshooting this issue.  Below are the components involved:

      Domain: Windows 2003 Native.
Client:  Windows 7 32-bit with Office 2010 Pro Suite.
      SQL Server:  Windows 2008 Standard Server with SP2 (32-bit)
      SQL Server Info: Microsoft SQL Server Management Studio                                    10.0.1600.22 ((SQL_PreRelease).080709-1414)
Microsoft Analysis Services Client Tools      2007.0100.1600.022 ((SQL_PreRelease).080709-1414)
Microsoft Data Access Components (MDAC)      6.0.6002.18005 (lh_sp2rtm.090410-1830)
Microsoft MSXML                  3.0 4.0 5.0 6.0
Microsoft Internet Explorer            9.0.8112.16421
Microsoft .NET Framework            2.0.50727.4234
Operating System                  6.0.6002

Regards,

Under_Pressure
0
Under_Pressure
Asked:
Under_Pressure
  • 2
  • 2
2 Solutions
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
<<Incorrect syntax near ‘POFVM’. (#102).>>

 A SQL string is being sent to the driver and the syntax is incorrect.

 Most likely a SQL statement that is being constructed on the fly in code in the app, but it could also be an Access bug, or settings for the driver (like quoted identifiers)

  They should note what they were doing just before the error (ie. running a report), and what if any options or operations they were doing to help pin it down.

  Also double check the DSN setup between them and another machine and make sure their identical.

Jim.
0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
Also, if you can generate the error on demand, then turn on ODBC tracing through the ODBC admin applet.

The resulting log will let you see exactly what is being sent to the driver and will give information about what's going on.

If it's a more sporadic error, you might want to leave it on for a few hours to try and catch it.  Just be aware that the log file can grow in size quickly.

Jim.
0
 
Under_PressureAuthor Commented:
Thank you Jim.  I will act on your suggestions this morning and will update you on what transpires.
0
 
Under_PressureAuthor Commented:
Jim,
Thank you for your insight.  By taking your suggestion of making sure that the DSN configurations were identical, we wouldn’t have noticed the 2 boxes under SQL Server DSN Configuration:  Use ANSI quoted identifiers and Use ANSI nulls, paddings and warnings.  When we had unchecked those 2 boxes and ran test queries, they completed successfully without a hitch!  I’m very appreciative and, therefore, awarding you all of the points available.
Regards,
Ray
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

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