NT4 unable to access sql whilst W2K works  | |
March 13th, 2003, 07:05 AM
|
#1 (permalink)
| | Retired mostly.
Join Date: Oct 2001 Location: Finland
Posts: 5,144
| NT4 unable to access sql whilst W2K works
Ok, here's the problem. I'll try to explain it as good as possible but SQL isn't my trade.
A person here has created MS Access database, that retrieves information from AS400 via IBM Client Access Express.
The database works fine in w2k, but not in NT4.
The w2k is w2k sp2 fi.
The nt is nt4sp6 fi.
I have installed the latest (dated few years old) sp for cae and tried multiple mdac updates from MS. None of them help.
I'll attach here logs from nt4 and w2k archived. Please examine them (and let me know if they contain something that shouldn't be available public and I'll edit  ), and see if you can figure out what's wrong.
//edit: I won't, rar's are not allowed 
I'll store it in my website, check out here -> http://juppi.merikoski.edu.ouka.fi/~mahonen/sql/sql.rar
-M |
| |
March 13th, 2003, 09:33 PM
|
#2 (permalink)
| | Banned
Join Date: Oct 2001
Posts: 447
|
Right, I'll peruse your logs... May or may not find problem. BTW, what is the problem/error, exactly. How exactly does it not work?
Do NT and XP have the same client/file privileges?
Can you run the CAE (which may not be supported by IBM anymore) segment on each box?
Is each box pointing to the correct AccessDB? Is it local or networked?
Can each box use CAE to see the AS400? Can each box see the AccessDB? If so what is the error/problem, exactly? |
| |
March 14th, 2003, 12:49 AM
|
#3 (permalink)
| | Member
Join Date: Sep 2002
Posts: 364
|
It could be using a system DSN to connect to the AS400 on the 2K box, or a file DSN on a network drive that the NT box does not have permissions for. |
| |
March 14th, 2003, 02:37 AM
|
#4 (permalink)
| | Retired mostly.
Join Date: Oct 2001 Location: Finland
Posts: 5,144
|
This is the exact error, however as it is in finnish I doubt it's much use for you. I'll try to translate it correctly
DIAG [22003] [IBM][Client Access Express -ohjelmiston ODBC-ohjain (32-bittinen)][DB2/400 SQL]Numero ei ole sallituissa
rajoissa. (1)
Translation:
DIAG [22003] [IBM][Client Access Express -softwares ODBC-driver (32-bit)[DB2/400 SQL]Number isn't in allowed boundary. (1)
And access will show '#' in all the cells.
CAE works fine in both computers as they are very able to access movex (for which the as400 is used) well.
Both have the same privileges, logged in locally as administrator and to the as400 as myself.
The accessdb is a local mdb file.
Hope this clears up a little the mess 
-M |
| |
March 15th, 2003, 06:21 PM
|
#5 (permalink)
| | Member
Join Date: Sep 2002
Posts: 364
|
I don't know. I would try testing it by making a new ODBC DSN, and connecting to another file in another library...see if it works at all. |
| |
March 16th, 2003, 10:09 PM
|
#6 (permalink)
| | Banned
Join Date: Oct 2001
Posts: 447
| Quote: |
Number isn't in allowed boundary
| or:
"Numero ei ole sallituissa
rajoissa. (1)"
Should point you to CAE as where problem is located, and maybe (1) is the row? number...
Seems obvious to me the IBM client has found a something it thinks is a:
number (could be string?, something else?)
or
number 'bigger' than expected. Check the datatypes on the CAE and AccessDB's.
May (no duh) have mismatch? A null value could even cause this problem... |
| |
March 17th, 2003, 03:23 AM
|
#7 (permalink)
| | Retired mostly.
Join Date: Oct 2001 Location: Finland
Posts: 5,144
|
C??p.
I don't understand your respones 
And I have no idea where to make the repairs.
So I will suggest the users to update from nt4 to w2k, seems it's the easiest way to correct the problem.
Thank you both creosote and qball for helping me.
-M |
| | | Thread Tools | Search this Thread | | | | |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | | | | Most Active Discussions | | | | | Recent Discussions  | | | | | |