Error writing file to local server

I am having trouble writing a file to a server on our network (using IPA file access node). If I run the flow from my desktop, it writes the file. If I upload the flow and run it, I get this error:

File Access FileAccess220: Failed with error java.io.IOException: Logon failure: unknown user name or bad password return message

I have had our network admin add the 'lawson' user to the local server, but I still get the same error. I also added a system configuration (ftp) with the ip address and Lawson user and pwd. I get the same results with that too.

Find more posts tagged with

Process Automation (IPA) - General Discussions

Comments

russel-cornelson

Good morning,

In order to resolve that issue I would say we probably need some more information. What configuration set is your File Access node configured to use? What server are you trying to save the file on? LSF or Landmark server? If LSF, is your File Access Configuration set to be remote?

john-miller

I have a ticket open with Infor for a very similar issue. In my research I've found that it doesn't appear that IPA uses the local Lawson account when moving files between Windows Servers. (even though doing a syscommand of whoami shows it is local Lawson) To work around at least temporarily, I've mapped a drive using the syscommand node and then moving the file. The command on the node being: net use X: <\ServerNameFolder> /user:<DomainUser Password>

unknown

The server is neither LSF or Landmark, it is another server on our network. On my file access node I don't have an option to specify 'remote'. I have built an ftp system configuration in rich client and specify that in my file access node. I don't have a 'remote' option in my ftp configuration either. It has the ip address of this server on our network. If I run from my desktop, my file access works (writes to server on network) whether I specify the configuration or leave it blank.

russel-cornelson

@lbunchek

That would be the problem, the file access node is capable of accessing only the Landmark Server and the LSF server. This node uses delivered lawson functionality to authenticate and gain access to the file system. If the server you are attempting to access is a 3rd party server you will need to use FTP to move/access files.

This requires the use of the FTP node instead of the File Access node.

russel-cornelson

@JD Miller

JD, I strongly encourage you to not use a UNC drive or mapped drive with Process Flow for accessing the LSF system.

When the File Access node is configured to be "Local" aka "Not Remote", the user that owns the java.exe process which IPA is running as, aka by default locallawson, it uses that local user to access the file system.

When the File Access node is configured to be "Remote" aka the LSF Server, the system connects the PFI RMI Server that is running on the LSF server and after authentication it uses that Java process to access the LSF system. Typically that owner for a Windows system tends to be the Local System account if LSF itself is started as a windows system.

You can configure the PFI RMI server and PFI Event Manager to run as a specific user by adding a pfirmi.cfg and pfirmi.cfg file to LAWDIR/system in LSF that specifies the user you wish to run as. Then ensure that user has NTFS file security to access the LSF system.

I recommend setting this up and avoiding UNC/mapped drives.

unknown

I use the syscmd node to execute a bat file that contains the ftp commands. This would be a way to do it without having to configure something. The nice thing about it is you can create the bat file in a previous node if needed.

russel-cornelson

System command may work for some; but I believe you are then tied to ftp as I don't think Windows System Command is capable of handling sftp.

bhillz

If the lawson account is a local (windows) account it's generally/usable know only to the local server. The copy will fail unless EITHER 1: the remote server had a trust relationship with the local server/account, OR 2: the lawson account is a domain account (i.e. NOT local), and has resources authorized on the remote server.

russel-cornelson

CGaware: For a file access, the account on Landmark can still be a local user. Infor Process Automation does not attempt to use this account to write remotely. It establishes a connection to an RMI server on the remote machine, and uses the user that owns that RMI process to access the file system.

Copyright © 2025 Infor. All rights reserved.