Sql-server – Error SQL Server 2005 Using Proxy to run Agent Job ConnGetProxyPassword

I seem to have stumbled upon the answer. It would appear that the original SQL server was an upgraded from 7 to 2000 to 2005! crazy but apparently has been in use for 8 years well before my time.

The problem seems to be related to the database compatibility, see the following msoft article

link text

"Databases set to compatibility level 70 or lower are not displayed"

I have tested this by changing the level to 90 and sure enough it now works.

thanks to all who replied, this site is going to be very useful.

The problem is related to the encryption warning but that is not the cause of the failure. When you encrypt with a user key then only that user can decrypt the password in the connection string, otherwise the connection string will have no password. When you don't save sensitive data the password will not be stored in the connection string so you need to set up an SSIS configuration to supply the proper connection string. Open the package and select SSIS, Package Configurations. In the next screen you will select new and then create an XML based configuration file. When asked which properties you want to configure select the connectionstring property of your oracle connection manager and create the dtsConfig file somewhere on your file system. After you create the file and the configuration you can remove it since you may not want the package to look in the same path for the file.

Edit the dtsConfig file and add the password to the connectionstring and then save the file. Put the file where you want it to live and then go into thte properties of the job step that runs the SSIS package. Select the configurations tab and then browse to the dtsConfig file. This should apply the configuration at runtime and the error about the null password should go away and be be replaced by either a different error or it will work.