Hi All, I have a customer who is scheduling fme.exe from within Microsoft SSMS - because it has good logging functionality. The fme.exe command is taken from a desktop log file on the server machine. If they run the command in a shell it works, and scheduling with Task Scheduler works, but from inside SSMS as the sql_agent account they get 'FME license system failure: License dependency check failed. This FME suite license is dependent on another license which is not available. Program terminating. Transaction failed. Process exit code 2. The step failed. '. Does anyone have an idea what is the issue? SSMS scheduler has only the one user account available to run jobs, but I assume that could be changed. Thanks.
Question
Best practices in scheduling fme.exe in SSMS
+20- Enthusiast
Just to add to Bruce's note, the user is a SQL Server Agent Service account. It is the only option available when a step is created.
+19- Supporter
Just to add to Bruce's note, the user is a SQL Server Agent Service account. It is the only option available when a step is created.
...and the user has Data Interoperability licensed as concurrent user - thanks.