Error Message: Object reference not set to an instance of an object - When TargetServerVersion set to SQL Server 2012.
Action:
After switching the TargetServerVersion in Visual Studio to SQL Server 2012, I received the following error message. (This is reproduceable in VS2019 and VS2017.)
Error Message:
"Object reference not set to an instance of an object"
Solution:
Resolution: Please check if you have duplicate mappings in the DTS folders under C:\Program Files (x86)\Microsoft SQL Server\, as Visual Studio doesn't handle such errors gracefully. A quick way to do that is to add the problematic package that targets SQL Server 2012 to a project that targets a later version (e.g. SQL Server 2019) and inspect the popup that shows a list of warnings.
NOTE: Some of our clients have had problems with the KinsgwaySoft components. If you see a warning about duplicate KinsgwaySoft mappings, please remove KingswaySoft.UpgradeMapping.*.xml files residing in folders C:\Program Files (x86)\Microsoft SQL Server\vvv\DTS\UpgradeMappings where vvv is 110, 120, 130, 140, 150.
Book a Presales Call
Are you new to COZYROC and evaluating our solutions?
Book a Presales Call with us now and get 5% off SSIS+.
Book a Presales Call with us now and get 5% off SSIS+.
Related Articles
Why do I get the following error when executing a package under a SQL Server Agent job: "Failed to decrypt protected XML node "ServerPassword" with error 0x8009000B..."?
The Execute method on the task returned error code 0x80004003 (Object reference not set to an instance of an object.). The Execute method must succeed, and indicate the result using an "out" parameter. ... and also: Failed to decrypt protected XML ...How to change the TargetServerVersion property for an SSIS project.
TargetServerVersion is a deployment property that identifies the expected version of SQL Server Integration Services that is installed on the target report server. To change the TargetServerVersion property for and SSIS project follow these steps: 1. ...Error Message: "Could not initialize component for use in the designer."
Action: While creating a new CRM destination, the following error is encountered. Error Message: TITLE: Microsoft Visual Studio ------------------------------ The component could not be added to the Data Flow task. Verify that this component is ...Error Message: "Unable to generate a temporary class (result=1). error CS2001: Source file 'C:\Windows\TEMP\...' could not be found error CS2008: No inputs specified"
Action: When running an SSIS package under the SQL Job Agent, the following error is encountered. Error Message: "Unable to generate a temporary class (result=1). error CS2001: Source file 'C:\Windows\TEMP\...' could not be found error ...SharePoint - Error Message: Object Reference not set to an instance of an object.
Action: We started getting an error from a component which copies a file to an Office 365 SharePoint site. This upload has been working fine for months and no deployments have been made to it. The error is happening both on the deployed version and ...