Home > IT Answers > Microsoft Windows > MS Query – Client Access DSN error
Jsimmons
0 pts.
 MS Query – Client Access DSN error
Microsoft Office, UDB for iSeries/i5
I'm receiving SQL0901 error when I establish a connection through MS Query to the 400. The job log failure is QQQISVSU (level 40) stating "Attributes of value number 2 in field HVR0002 not valid" I've disabled query wizard in hopes that the SQL request would not be made and it gives the same error. I'm not getting any help from MS because they consider it a ODBC driver problem. I can't find anything referencing this on IBM's support site either. This started happening when the 400 OS was upgraded to V5R3. I'm using MS Office 2000 on Win XP Pro. I've uninstalled and re-installed Office and Client Access and loaded the appropriate service pack.

Software/Hardware used:
ASKED: February 21, 2005  10:35 AM
UPDATED: January 4, 2011  6:14 PM
RELATED QUESTIONS
Answer Wiki:
This is a guess. Check what version of MDAC (Microsoft Data Access Components) the AS400 upgrade recommends. The most recent is 2.8. It may be the solution. Sometimes a non-MS vendor supports a specific version like 2.6 or 2.7. All of these can be downloaded from the Microsoft web site.
Last Wiki Answer Submitted:  February 23, 2005  9:11 am  by  Stuers   0 pts.
All Answer Wiki Contributors:  Stuers   0 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

 

I was getting that same SQL0901 error returned and “Attributes of value number 2 in field HVR0002 not valid” in my job log file.

This fixed it…BUT it doesn’t seem right from the AS400 side.

In the ODBC data source on the Sever tab I put the library name in the “Library List” box but in the “SQL default Library” box I put my primary physical file name.

I also used a fully qualified file name for the physical file in my SQL statement.

Drchris
 10 pts.