That looks good and works at this end. I think we have some kind of issue relating to updating of DLLs, which would explain why the extra trace didn’t appear and you are still getting this problem. This is probably because I forgot to ask you to stop and restart the servers, and also SmartsIntegratorDal.dll needs to go in the GAC. I think the easiest fix for this is for you to uninstall SmartsIntegrator and then reinstall it from http://www.smartsintegrator.com/download.aspx, if you are happy to do so. You won’t lose any data in this process.
Alternatively, if you’d rather fix things up manually, please update the attached DLLs in your installation folder. You will also need to update SmartsIntegratorDAL.dll in the GAC, by dragging it into C:\Windows\Assembly or executing GACUTIL.EXE /i SmartsIntegratorDAL.dll (GACUTIL.EXE is in the .Net Framework directory, or just search for it on your machine). And then I’d recommend a reboot or at least stopping and starting all SmartsIntegrator services. [If this GAC stuff makes no sense to you, go for the uninstall and reinstall option instead!]
In this latest build / update, the extra FTP trace is now set up via a registry entry. Please launch regedit.exe, and navigate to HKEY_LOCAL_MACHINE/Software/SmartsIntegrator. Right click in the right hand pane, and select New String Value. Name the string value FTPLogFile2, and set its’ value to be the full path to a file on your machine, to which the SmartsIntegrator service running your FTP receive port has write access. This will contain the extra FTP trace.
Once our builds are synchronized, I believe the Database problem will go away, and the extra trace will help us nail the FTP issue.
Thanks,
Ben.
Ben Jackson
SmartsIntegrator Technical Support