Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

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

Posted on 2013-01-22
4
Medium Priority
?
2,163 Views
Last Modified: 2013-01-24
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
Comment
Question by:Under_Pressure
  • 2
  • 2
4 Comments
 
LVL 58

Accepted Solution

by:
Jim Dettman (Microsoft MVP/ EE MVE) earned 2000 total points
ID: 38809721
<<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
 
LVL 58

Assisted Solution

by:Jim Dettman (Microsoft MVP/ EE MVE)
Jim Dettman (Microsoft MVP/ EE MVE) earned 2000 total points
ID: 38809736
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
 

Author Comment

by:Under_Pressure
ID: 38810928
Thank you Jim.  I will act on your suggestions this morning and will update you on what transpires.
0
 

Author Closing Comment

by:Under_Pressure
ID: 38816857
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

Independent Software Vendors: 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!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

As with any other System Center product, the installation for the Authoring Tool can be quite a pain sometimes. This article serves to help you avoid making these mistakes and hopefully save you a ton of time on troubleshooting :)  Step 1: Make sur…
Technology opened people to different means of presenting information, but PowerPoint remains to be above competition. Know why PPT still works today.
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

926 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question