Corrupted user id passed to iSeries ODBC connection from scheduled agent

Did you enable ODBC logging, to find out what data is passed and what generates the error?

What O/S is the Domino server running on? What Domino server and Notes releases do you use?

Yes:  IBM][iSeries Access ODBC Driver]Communication link failure. comm rc=8001 - CWBSY0001 - User  UNNINFO on server [blah] does not exist, Password length = 8, Prompt Mode = Never, System IP Address = [blah]

The user passed was actually GUNNINFO but is being received as  UNNINFO  (with a leading space)

when we tried a different id GUNNINFORM  it was passed as GUNNINF RM  with a space in the middle.

The server is 6.5.3  and running on windows 2000 SP4.
I am currently looking into a possible mismatch between the release level of the ODBC driver and client access on the iSeries

You're also loggin locally, on the Domino-server? Or are source and destination server one and the same?

The destination server is separate.  It is an iSeries (AS/400). The domino server is running on Windoows 2000.  Thanks for your help.  

So which log says that one letter is missing, the one on the iSeries or the one on the Domino server? Or do they both say the same?

They log on the domino server. I can't find any related errors in the iSeries log just an entry for attempting to process the signon request for UNNINFO

For what it's worth...

http://www-03.ibm.com/servers/eserver/iseries/access/supportedos.html

Please check the DSN configuration again on the iSeries.  So there is a DSN configuration on the iSeries, and an ODBC connection on the client or domino server?  

I've run into a few cases where I need double authentication and the odbc port enabled on the firewall before it would work.   Even though the Domino ID was correct, if you're getting a failed login  with no corresponding error on the Domino log, then it's not domino failing you, its your Active Directory, server permissions and ODBC Port permissions.

Thanks I am getting an error on the Domino log,  but only when running from a scheduled agent,  not when run directly or even as a runonserver agent

Ah, then the user Id needs to have permission to run unrestricted agents.  If you set your events.nsf to capture agent errors, you will see the exact error on the Domino side.  Most of the time it is because the userID needs to have permission to run unrestricted agents (that access the file structure) on the server.  Go to server documents: security section, and make sure that the user ID is added to the appropriate agent permissions.  If the Id is misspelled, then recreate the ID using the same name (tell it not to recreate the mail file, if that is a problem.  I usually create one ID just to do these things).

If you're not logging agent errors, then you need to turn these on so you can see them as they occur.  

I think I have to agree with you that it must be some version conflict. Did you already try to re-install the ODBC drivers?

Just a sidebar, when running manually or runonserver, the agent uses the current user's permissions.   Scheduled, it's using whoever signed the agent, to run on the Domino server, plus whoever is configured in the Domino Server's ODBC  DSN configuration (Advanced Options) for the login name and password.  When you configure the system ODBC, you can test the connectivity.

so how are we doing?

Hi,  Sorry for the delay replying.

Unfortunately,  the agent is signed by the domino administrator which is the same ID that I am using to run it manually.

I tried replacing the ODBC DLL,  but that caused an error,  I am going to try and reinstall the drivers properly.

Thanks for all your input.

We got a workaround, though not a solution to this issue by reducing the size of the user id to 5 characters