| ✅ Check | Why It Matters | |----------|----------------| | – at least SQL Server 2012 (SSISDB introduced) | Older versions use legacy file‑system deployment, which surfaces a different set of permissions. | | SSIS Catalog (SSISDB) created ( CREATE CATALOG ) | The error is usually thrown when the Catalog exists but the caller lacks rights. | | Windows account – the one you’ll run the package under (e.g., DOMAIN\ETLUser ) | Permissions are granted to Windows or SQL logins , not to AD groups unless you map them. | | SQL Server login – a login mapped to the Windows account (or a contained DB user) | The login must have a user in SSISDB with the needed role membership. | | SQL Server Agent proxy (if using Agent jobs) – proxy with a credential that stores the Windows account | Without a proxy, the job runs under the SQL Agent service account, which often lacks rights. | | Data source credentials – stored either in package connection managers, Project‑level Parameters , or SSISDB Environment Variables | The package may still fail later if those credentials are missing, even after fixing the Catalog permissions. |
-- 1. Is the login mapped? SELECT name, type_desc, is_disabled FROM sys.server_principals WHERE name = 'DOMAIN\ETLUser'; SSIS-661