- The following error message appears in the TE_TEMP mark_bad files:
- [NG14570] Unknown database error
- The files in TE_TEMP are not available when browsing through WebVision
- NuGenesis 8 SDMS
FIX or WORKAROUND
- Look for *.mark_bad files in TE_TEMP.
- Open the most recent .mark_bad file, scroll to the bottom, and look for errors and warnings within the file.
- Troubleshoot the Managed Storage Location setup:
- Obtain the name of the project to which the TE is trying to add the files
- Open a mark_bad file, and then look for the line "DataBaseName" in the file; the name of the project is to the right of this line
- In SDMS Administrator, open this project's properties, and confirm the Managed Storage Location for this project
- Click the "Managed Storage" button in the toolbar to see the details for all Managed Storage locations
- The problem is often an obsolete password entered here for the username
- Open a command prompt and attempt to connect to each FTP server
- C:\> ftp.exe
- ftp> open servername port#
- example: open SDMSFTP 2121
- Use the username and password from the SDMS configuration to log in to each FTP server
- If the FTP server rejects the connection, but the netstat command on the FTP server shows that the FTP site is listening on that port, then a firewall is likely the issue
- Determine if you can reach the FTP location in SDMS Administrator from your File Capture machine while logged in as the Windows user running the RPC service, and if you can create and delete files on that drive.
- If this is not the case, check with your IT department about the corresponding privileges.
- Also, verify that the listed FTP site is active; that it has enough disk space; that it has Anonymous Access disabled and Read & Write Access enabled; and, if it stores the files for the site on another computer, that the other computer is active and that the credentials stored for the other computer are valid.
- Check the log files in %WINDIR%\system32\LogFiles\MSFTPSVC1 for any 400- or 500-series FTP error codes
- If you find 400 or 500-series error codes in the FTP log file, look for it's corresponding substatus code and Windows error code. These numbers will be in the same line of the log file as the FTP error code. Look up the FTP code and substatus code on Microsoft's reference page (linked above) and the Windows error code to get information about the root cause of the error
When you set FTP ports for use with a firewall you have to restart the Microsoft FTP service, not just hit the restart button in IIS manager.
The most common FTP error code for this issues is 530, "Not logged in". The substatus and Windows codes will help you identify the precise cause for the 530 error. The most common reasons are that an invalid password is entered into the Managed Storage location configuration in SDMS Administrator or the user account is locked out.