Ssis-948 |link| Jun 2026

Developers can filter these messages in the SSIS logging UI or via the catalog.event_message view.

| Scenario | Why It Happens | |----------|----------------| | | Typo, missing server name, wrong database, or wrong provider. | | Credential Issues | The connection uses Windows Authentication and the executing account does not have rights, or the SQL login/password is expired/disabled. | | Package Configuration Overwrites | A configuration file/environment variable replaces a working connection string with an invalid one at runtime. | | Connection Manager Set to “DelayValidation” = False | Validation occurs before runtime variables are populated, causing a temporary invalid state. | | 64‑bit vs 32‑bit Provider Mismatch | The package runs in 64‑bit mode but the required provider (e.g., Jet OLEDB for Excel) is only 32‑bit. | | Network Issues | DNS resolution failure, firewall blocks, VPN disconnects, or the remote server is down. | | Concurrent Connections Limit Exceeded | Some data sources (e.g., Oracle, SAP) limit the number of simultaneous connections; SSIS may exceed the limit during a bulk load. | | Package Deployed to SSISDB with “Project Parameters” Overridden Incorrectly | Parameters that feed connection strings are mis‑typed or left blank in the catalog. | | Run‑time User Context Change | Using Execute Process Task or Impersonation that switches to a user without the needed privileges. | ssis-948

Sure! I’d be happy to put together the content you need for To make sure it’s exactly what you’re looking for, could you let me know a few details? Developers can filter these messages in the SSIS

The sits between source and downstream components. It is a runtime service injected into the data‑flow pipeline, not a new component that must be dragged onto the design surface. | | Package Configuration Overwrites | A configuration

Moving databases between environments with different SQL Server versions causes the 948 "version error".