More detail is needed about the message. Is there a message identifier? A return code? Anything that identifies it. Is the host database server started on the AS/400? Can any other user succeed with a transfer request? When the failing user runs CWBPING from a Windows command line, what messages result? Some useful information would be helpful. — Tom

There is no msg identifier or code.Only a single user is facing this error?the database server is already started.User performed CWBPING with the following msgs:-Successfully connected to server application : Central ClientSuccessfully connected to server application : Network FileSuccessfully connected to server application : Data AccessSuccessfully connected to server application : Data QueuesSuccessfully connected to server application : Remote CommandSuccessfully connected to server application : SecuritySuccessfully connected to server application : DDMCWBCO1011 – Remote Port could not be resolvedCWBCO1008 – Unable to connect to server application Telnet, returned 8407Successfully connected to server application : Management CentralCWBCO1015 – Connection verified to system 10.113.4.145, but there were warnings.

The basic items seem okay. Can you create a different transfer request on that PC that works? I.e., do all transfers give the same error for that user? — Tom

Well…User didnt try to transfer anything…Problem arises after he put login credentials iSeries. I try to explain it through below steps:-1. User opened iSeries Data Transfer.           2. Putting the Login Credentials.3. Error Prompts:- Unable to Start Database ServerIf there had been the link to attach screenshot then definitely I would do it.For more information 

The CWBPING results seem only to complain about telnet. I briefly wondered earlier if this was a ‘Data Transfer’ or ‘Receive file from host’ transfer. An emulator transfer can’t be selected until after signing on, so it has to be the Data Transfer facility as you said.
 
I haven’t found a combination that gives that message. All errors include a message ID. There might be a test, though.
 
From a Windows command, have the user run:
 
CWBLOGON serverName /c
 
That should clear cached credentials for that server. Then run:
 
CWBLOGON serverName /u userID /p password
 
Have the user type in the same user ID and password that is used for the file transfer. Report results here. Also, please post the installed version of iSeries Access and its service level.
 
Tom

Just a thought, but has the user disabled their profile?  You could have someone else try the transfer from the same machine and see if they get the same error. If they do then it’s with the transfer utility, if not it’s a user profile issue. The only other thing I can think of has there been a recent upgrade to either system? There may be compatibility issues.

Hi Todd,Thanks for your inputs.Yeah User profile got disabled couple of times but I re-enabled it and asked him to try again but no resolution.Only a single user is facing this problem, others are having good luck with it.We didnt have any upgrade so far, but yeah in coming weeks it will be.I will ask user to perform steps told by Tom.Lets See what happens.Thanks Again.

Hi Tom,User performed the steps stated by you.CWBLOGON 10.113.4.145 /cUserId and Password information cleared from iSeries Access for Windows Cache.CWBLOGON 10.113.4.145 /u LEWISW /p WALDRON4UserId and Password successfully stored in iSeries Access for Windows Cache.

These posts are taking so long to show up that it’s hard to catch them quickly. I should have responded a couple hours ago. Now you might not see this for another couple hours.
 
Okay, the user can clear cache and set a cache profile and password. It looks as if most basic components are available. Now to test if iSeries Access can send the correct profile and password. We only use iSeries Access tools on the PC so that we isolate where the problem is.
 
Clear the cache with the first CWBLOGON. Then set the desired user and password with the second CWBLOGON. Then test the cache this way:
 
RMTCMD  sndmsg testing123 userID //serverName
 
That should send a test message to the userID message queue on system serverName. You can look at the message queue to verify that the message arrived, but all you really want to know is if RMTCMD asks for a user or password to be entered.
 
If it does, something is wrong with the values that were cached and we can focus on those. If it doesn’t, then the values are correct and the server accepts them. We can then focus on some other areas. (We can look at those areas after we know a little more.)
 
Do the above steps make sense? It would be easier if these comments weren’t being delayed for some reason.
 
Tom

Tom,User doesn’t have command line access (Limit Capabilities = *Yes).Not sure how will he check his msgs?

First, anyone can check the user’s messages. It doesn’t have to be the user. If you can sign on, you can check for the user.
Second, (Limit Capabilities = *Yes) should not stop a user from checking messages.
Third, it’s not necessary to check unless you want to verify that the message was sent. The important part is what shows on a Windows command line when RMTCMD runs. It’s important to see if there are any errors about the userID or password in the cache.
Tom

Sorry, for the confusion.User tried to send the msg by trying the below steps and it prompted for user id and password!

1. Was the userID/password accepted as valid by RMTCMD?
2. We still need verification of the iSeries Access version that is installed on the PC along with the iAccess service level on that PC.
3. Can you also give us the cume PTF package level on the server?
 
Tom

And 4. What is the PC OS?
 
Tom