-
Title
Source File Location "Test Connection" results in "General error" with IIS setup -
Description
Trying to setup Stat 6.3 for the first time, we have both Windows and Linux servers in the network environment. When testing access to file locations on the Windows servers we are getting a "General error" message.
Looking at the server.log, the path is confirmed to be correct. We are also able to FTP to the location from the Stat Central Server (SCA), however, it is unable to change the directory. For Linux everything is working just fine, as expected.
We tried some troubleshooting steps but nothing has worked. We also tried putting in an obvious wrong location path (as a troubleshooting test) and a different error message appears. The Test Connection button for the File Server works as expected and placing the file location path in there will work, it just does not work for the Source File Location (please view sample screenshots below). We are kind of stuck at this point.
-
Cause
The cause is likely due to a specific IIS configuration. Please check the options below.
-
Resolution
Under the IIS File Logs directory (%SystemDrive%\Inetpub\Logs\Logfiles), the associated log file may display similar lines as shown below:
2021-02-16 14:10:07 ZZZ.ZZZ.ZZZ.ZZZ FTP-SERVERNAME\USERNAME YYY.YYY.YYY.YYY 21 PORT ZZZ,ZZZ,ZZZ,ZZZ,151,197 200 0 0 4337c6db-cb1c-6ef0-8baf-3a873c47f7fd
2021-02-16 14:10:28 ZZZ.ZZZ.ZZZ.ZZZ FTP-SERVERNAME\USERNAME YYY.YYY.YYY.YYY 21 NLST - 550 4294967295 0 4337c6db-cb1c-6ef0-8baf-3a873c47f7fd /apps/psoft/fxxxv/fxxxv_psapp/sqr- Check the NLST code from the log with Microsoft's "The FTP status codes in IIS 7.0 and later versions" list to help identify the cause.
- Was IIS configured in any special way that is unique to a normal setup? Was it configured correctly? Setting up an FTP server on Windows Server 2016.
- Microsoft also has a reference guide, Creating a New FTP Site and Configuring an IIS 7 Manager Account. Test a new FTP site with the generic setup to help troubleshoot the basic settings.
- Verify the File and Folder Permissions. The FTP user account must have at least READ and WRITE privileges for the directory and any subdirectories within the FTP path.
- There might be a firewall involved in the network environment with IIS configuration. This typically does not work well against active mode file transfer and requires passive mode file transfer. The File Servers settings could be configured for active mode, go ahead and check the "Passive" box and run the Test Connection under the Source File Location again.
