slayer leecher wont let me use it inless i load a proxy

The HKEY_CURRENT_USER registry keys are user-specific. A registry-based SSIS package configuration uses the HKEY_CURRENT_USER registry keys.

This scenario can also occur with any task that depends on the file connection manager, such as a SSIS file system task. For example, this scenario can occur with text log providers that do not use a login and a password.

File access fails because the current user does not have the required permissions to write to the file share that the connection manager accesses.

A SQL Server connection that uses integrated security fails because the current user does not have the required permissions.

This scenario can occur if the current account or the execution account differs from the original package author, and the package's ProtectionLevel property setting does not let the current user decrypt secrets in the package.

The current user cannot decrypt secrets from the package.

The package may not run in the following scenarios:

The user account does not have the required permissions to make connections or to access resources outside the SSIS package.

The user account that is used to run the package under SQL Server Agent differs from the original package author.

Reasons that the package may have failed are as follows: The most appropriate method depends on the environment and the reason that the package failed. To resolve this problem, use one of the following methods. However, if you do not modify the SSIS package, it will run successfully outside SQL Server Agent. When you call a Microsoft SQL Server Integration Services (SSIS) package from a SQL Server Agent job step, the SSIS package does not run.

Original product version: SQL Server Original KB number: 918760 Symptoms This article helps you resolve the problem that occurs when you call an SSIS package from a SQL Server Agent job step.

Slayer leecher wont let me use it inless i load a proxy