Problem
For some users when you execute Package in Visual Studio it works ok but when deploy to the server and run from SSIS Catalog or Run via Job / You have Trial version you might get the following errors.
In the Package Execution Log
System tried to search for the following license types [SSIS_PP_ENT, SSIS_PP_PRO, …….., SSIS_PP_TRIAL]
under the following path [C:\ProgramData\ZappySys\SSISPowerPack] but no valid license found.
Additional information >>> LoggedInUser=MYDOMAIN\MYSERVICEACCOUNT >> RunAsUser=MYDOMAIN\MYSERVICEACCOUNT >>>
Path access=True >> >> TempFolder=C:\Windows\TEMP\ [Read/Write=OK,OK] >> License Files Scanned [2]
==> C:\ProgramData\ZappySys\SSISPowerPack\SSIS_PP_TRIAL.lic.130498499674709531 [Read=OK], .
Please read this link for more information => https://zappysys.com/links/?id=10021.
Inner error=> License type [SSIS_PP_TRIAL] not found or its expired.
You are running TRIAL build, if you have paid license then you must download full version
Also when you check system event log you might see DistributedCOM (DCOM) Permission error like below.
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2DC39BD2-9CFF-405D-A2FE-D246C976278C} and APPID {DB336D8E-32E5-42B9-B14B-58AAA87CEB06}
to the user DOMAIN\SOME_USER_ACCOUNT SID (S-1-5-21-xxxxxxxxxxxxxxx) from address LocalHost (Using LRPC)
running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component
Services administrative tool.
Possible Cause
Most possible cause for this error is you have deployed SSIS Packages under Package Deployment Model (Legacy Mode) rather than Project Model and you are using Trial License rather than Full License.
If you have trial license installed and when you run SSIS package via SSMS > SSISDB Catalog > Right click execute package, it uses DCOM Service to pass your local security context to the remote server and run package as you.
For Trial License it might access C:\ProgramData\ZappySys folder and Registry Hives like HKCR\CLSID or HKCU\Software\Classes\CLSID (Read and Write Permission Needed)
For Full License it just needs access C:\ProgramData\ZappySys
This is not an issue in most cases but if user has no access to remote machine or you have certain policies / restrictions in place via Domain / Group Policy then access to some registry key might fail and you will see DCOM error like below.
You can check System Event Log and you will see below error from DCOM Service. GUID Mentioned below errors are for Legacy Service (Package Deployment Model) but your GUID can be different depending on your SSIS Version.
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2DC39BD2-9CFF-405D-A2FE-D246C976278C} and APPID {DB336D8E-32E5-42B9-B14B-58AAA87CEB06}
to the user DOMAIN\SOME_USER_ACCOUNT SID (S-1-5-21-xxxxxxxxxxxxxxx) from address LocalHost (Using LRPC)
running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component
Services administrative tool.
Possible Solution
Solution#1 Uninstall the Trial version and download the full Installer and activate the full license so certain registry key access such as HKCR\CLSID is not invoked in DCOM context. If you are not a paid customer then contact ZappySys Support to obtain FULL Installer.
Solution#2 If you see DCOM Error in System Event Log then, try some workaround mentioned by Microsoft listed here and here
Solution#3 Convert your SSIS Project to use Project Deployment Model in case it's set as Package Deployment Model (Legacy). If you use DevOps Script for Deployment then check your script to make sure it's not deploying as Package Deployment Model.
Contact Us
If you have more question(s) feel free to contact us via Live chat or email to support@zappysys.com
Comments
0 comments
Please sign in to leave a comment.