CS2001 Missing AssemblyAttributes.cs when Executing SSIS Package Deployed on Server

Question

I created SSIS packages and used the Integration Services Deployment Wizard to deploy it to the server. I manually navigate to the Integration Services directory through SQL Server 2012 and right-click and execute my package.

However, the package continues to work with an error, and I get the following errors when checking execution report messages.

They seem to fail in data tasks where I have script components.

Assign: Error: CS2001 - Source file 'C: \ Windows \ TEMP.NETFramework, Version = v4.0.AssemblyAttributes.cs' not found, CSC, 0, 0

Assign: Error: Failed to compile the scripts contained in the package. Open the package in the SSIS constructor and resolve compilation errors.

Answer 1

This answer is a more verbose version of UberDoodles answer.

In Windows Explorer.

• Go to C:\Windows\Temp\
• Right-click the folder and select properties
• Go to Security tab, select Advanced
• In the default Permissions tab, select Change Permissions
• For the appropriate permission entry, select edit .
• By default, I allowed 'allow' for Traverse folder / execute file , Create files / write data and Create folders / append data .
• Also check the 'allow' for List folder / read data and Take ownership .
• Click OK, the window closes
• Click "Apply" and confirm everything you need.

In addition, the registered user already had full control, but when I changed it to write "Users", it worked for me.

(based on file / folder permissions for Microsoft ).

Answer 2

I studied the same problem and I found a solution here:

https://social.msdn.microsoft.com/Forums/vstudio/en-US/73e67f3a-c575-4c73-a71d-ed7a2aeabb50/csc-error-cs2001-source-file-cwindowstempnetframeworkversionv40assemblyattributescs?forum=msbuild

In principle, the account in which the package runs must have full permissions for the C: \ Windows \ Temp \ folder so that it can create temporary classes.

It worked for me :)

Answer 3

I had the same problem today, just in SQL 2016. For me, it helped to change the version of the destination server in the properties of the Visual Studio project from SQL Server 2012 to SQL Server 2016.

Answer 4

I had the same problem. I first used Eric G.'s answer and added List and Read permissions to c:\windows\temp . After I got everything, I came back and removed this permission. Then I redistributed my solution from Visual Studio, this time designating the deployment target as SQL Server 2014 (which was the environment I used) using Martin's solution. Then I repeated the process and it worked with the remote List and Read .

I saved it using Martin's solution, because I don't like special permissions if I don't need them.

Luck