Skip to content

Commit b3d218b

Browse files
authored
Update links as per Joseph
1 parent b1cc852 commit b3d218b

1 file changed

Lines changed: 4 additions & 2 deletions

File tree

support/sql/integration-services/ssis-package-doesnt-run-when-called-job-step.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -113,6 +113,8 @@ Log: Name: OnError Computer: COMPUTERNAME Operator: DOMAINNAME\username Source N
113113

114114
## References
115115

116+
- For more information about a similar problem, see [You receive an "Error loading" error message when you try to run a SQL Server 2005 Integration Services package in SQL Server 2005](../integration-services/error-loading-message-run-integration-services-package.md).
116117
- [How to create a package template in SQL Server Business Intelligence Development Studio](https://support.microsoft.com/help/908018)
117-
118-
- [Connectivity error 0x80004005 occurs when you run an SSIS package as a SQL Agent job](../database-engine/connect/sql-server-faces-connectivity-issue-ssispack-fail.md)
118+
- [Connectivity error 0x80004005 occurs when you run an SSIS package as a SQL Agent job](../database-engine/connect/sql-server-faces-connectivity-issue-ssispack-fail.md)
119+
- For more information about how to create package templates, see [Create a package in SQL Server Data Tools using the Package Template](/sql/integration-services/create-packages-in-sql-server-data-tools#create-a-package-in-sql-server-data-tools-using-the-package-template).
120+
- For more information about SSIS package security and the `ProtectionLevel` property, see [Protection Level Setting and the SSISDB Catalog](/sql/integration-services/security/access-control-for-sensitive-data-in-packages#protection-level-setting-and-the-ssisdb-catalog).

0 commit comments

Comments
 (0)