Issue when running SQL Server 2005 SSIS Package on Remote Server?

The ASP. Net Worker Process is typically setup to run under the Network Service account, or even the user on the page (if impersonation is turned on) and they don't have proper authority to access the tables specified.

I know the database account has sysadmin access to the application's database and within msdb database, It has also been added to dt_dtsadmin,dt_dtsltdser and dt_dtsoperator, public and db_datareader. I'm using impersonation to navigate through the website and the impersonated user and network service has access to both application's database and msdb database. – Kojof Sep 14 '10 at 16:07.

The table name for logging is sysdtslog90. It will be in the database that matches the database for the connection you specified in the logging. Also, you must have picked the Sql Server logging provider to use that table.

Once you track down this table and look at it, you should be able to see the messages that were sent when the application failed.

Thanks for clarifying that. The table is empty and I have chosen the sql server logging provider. Do you know why the database password is not passed on, even though the protection level on the package is 'DontSaveSensitive'.

– Kojof Sep 14 '10 at 20:11.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.