If you have activated SSIS PowerPack License on a clustered environment, you may experience below issue in while running SSIS Packages via SQL Agent Job.
When you run SSIS Package via SQL Agent Job you may get License not found error or your Jobs running as Trial license (Log entries not detecting full license).
NOTE: Few other errors documented here. But we will talk one specific error on this page
If you are running SQL Agent Job on a clustered environment where Trial License worked fined but Paid License is failing
Job is reporting Trial license and not detecting Activated FULL license then it could be below reason.
When you register a License on a Clustered Node, it uses Node Machine name to generate Machine Hash Code for License Key. For many customers we found that when Job runs under Default SQL Agent Account on a Clustered environment Environment.MachineName function call reports Cluster Name (i.e. Virtual name) rather than Node Name.
Due to this difference wrong Machine hash code is generated at runtime and license validation fails.
To fix inconsistent behavior of Environment.MachineName function you can use following work around. When you do below steps you will always get Node Name as Machine Name and thus Machine Hash matches.
- Create Proxy Account for SQL Agents Jobs using ZappySys SSIS Tasks / Components.
- Change Job Step to run under Proxy account rather than default Job Owner
- Run the job see it starts using FULL License rather than Trial.
We found that when JOB runs under Default SQL Agent Account Service Account it reports Cluster Name as MachineName but when License is registered on a Node its tied with Node Machine Name. Running JOB under Proxy account starts reporting Actual Node name as MachineName and license issue goes away.