Loader ODBC Error

Support for DataSlave

Moderators: Tom, ian

Loader ODBC Error

Postby swjmckay » Fri Apr 20, 2012 3:36 pm

Up until recently we have had a version of Loader running on a server checking files on a network drive mapped to another server and ODBC pointing at our iSeries.
This week I have installed another copy of loader onto a new server, set up ODBC exactly the same as before but now get the following error when running the Loader.

Failed to execute write ODBC1: Error [42000] [IBM][iSeries Access ODBC Driver] [DB2 UDB]SQL0104 - Token [ was not valid. Valid tokens : <IDENTIFIER>.

The only differences are 1) Loader runs on a different server. 2) Files are now located on same server as Loader but process still uses mapped drive to check.

The imagelist.dbm runs successfully on the original server but not on the new one (with relevant changes made to file location etc)

Any thought or pointers would be much appreciated.

OS is Windows 2003. iSeries is V5R3
swjmckay
 
Posts: 4
Joined: Fri Apr 20, 2012 3:19 pm

Re: Loader ODBC Error

Postby ian » Fri Apr 20, 2012 4:09 pm

I cannot immediately see a cause. I will refer to other members of the team.

However can you confirm a few things:

    The version of DataSlave is the same in both cases
    The version of ODBC is the same in both cases
    The user account is the same in both cases

Also what was the operating system on the machine that worked?
Can you also confirm that you can read data from the server using ODBC

Do you have DataSlave Pro on the machine? It might be interesting to run a test from the Map Editor.
ian
 
Posts: 364
Joined: Sat Dec 18, 2004 8:13 am
Location: UK

Re: Loader ODBC Error

Postby swjmckay » Fri Apr 20, 2012 4:17 pm

Loader version that works fine on original server is 2.2.4.118
Loader version on new server is 2.2.4.130

ODBC drivers are exactly the same on both servers.
User accounts are identical on both servers.

Both servers run Windows 2003 Standard Edition SP2
I assume the server to be read from is the one that is failing? If so then yes (if I understand you correctly) as when the new loader file runs from the original server it reads correctly.

DataSlave Pro is not installed on either of the servers but is on 2 desktops in IT.
swjmckay
 
Posts: 4
Joined: Fri Apr 20, 2012 3:19 pm

Re: Loader ODBC Error

Postby ian » Fri Apr 20, 2012 6:41 pm

Can you please make sure that the map editor used to create the map and the version of loader running the map are the same version. If not this may cause a problem. If you want to roll back to the earlier build they are found at:

http://www.baycastle.co.uk/products/dat ... _Setup.exe
http://www.baycastle.co.uk/products/dat ... _Setup.exe
ian
 
Posts: 364
Joined: Sat Dec 18, 2004 8:13 am
Location: UK

Re: Loader ODBC Error

Postby swjmckay » Mon Apr 23, 2012 12:43 pm

Map Editor is 2.2.4 and states no current updates available through menu option.
swjmckay
 
Posts: 4
Joined: Fri Apr 20, 2012 3:19 pm

Re: Loader ODBC Error

Postby swjmckay » Wed Apr 25, 2012 12:32 pm

Any further thoughts?
swjmckay
 
Posts: 4
Joined: Fri Apr 20, 2012 3:19 pm

Re: Loader ODBC Error

Postby ian » Wed Apr 25, 2012 4:15 pm

I am sorry, I should have been clearer. Please check the version of the following files bu using the right-click menu to show properties and then go to the details tab:

C:\Program Files\Baycastle Software Ltd\DataSlave\Map Editor\DataSlave.MapEditor.exe
C:\Program Files\Baycastle Software Ltd\DataSlave\Map Loader\DataSlave.MapLoader.exe

This will show the build number in the format of 2.2.4.130

Thank you
ian
 
Posts: 364
Joined: Sat Dec 18, 2004 8:13 am
Location: UK


Return to Support

Who is online

Users browsing this forum: No registered users and 2 guests

cron