The type of the value (Int32) being assigned to variable "User::dteNewMaxDate" differs from the current variable type (DateTime). Variables may not change type during execution. Variable types are strict, except for variables of type Object

Question

The type of the value (Int32) being assigned to variable "User::dteNewMaxDate" differs from the current variable type (DateTime). Variables may not change type during execution. Variable types are strict, except for variables of type Object

kartikaya.singh

SSC Veteran

Points: 203
More actions
March 20, 2018 at 3:33 am

#403187

Hi All, I am getting the below error when dba is trying to deploy the SSIS package in the Production environment.
The type of the value (Int32) being assigned to variables "User::dteNewMaxDate" differes from current variable type(DateTime).
The datatype of the variable is datetime.
The package was deployed successfully in the TEST environment without any error but failed in Production.
Any idea why this is happening and how this can be resolved.

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Phil Parkin SSC Guru Points: 247180 More actions · Answer 1

kartikaya.singh - Tuesday, March 20, 2018 3:33 AM
ï»¿Hi All, I am getting the below error when dba is trying to deploy the SSIS package in the Production environment.
ï»¿The type of the value (Int32) being assigned to variables "User::dteNewMaxDate" differes from current variable type(DateTime).
The datatype of the variable is datetime.
The package was deployed successfully in the TEST environment without any error but failed in Production.
Any idea why this is happening and how this can be resolved.

Please confirm that this is a deployment error, rather than a runtime error.

kartikaya.singh SSC Veteran Points: 203 More actions · Answer 2

Hi Phil,

Yes this is happening at the time of deployment.

Phil Parkin SSC Guru Points: 247180 More actions · Answer 3

kartikaya.singh - Tuesday, March 20, 2018 7:16 AM
Hi Phil,
Yes this is happening at the time of deployment.

Wow, that is unusual. Can you also confirm that the SQL Server version in your TEST environment is the same as is in Production?

Martin Schoombee SSCoach Points: 19135 More actions · Answer 4

Could it be that this variable had a different type before? You may have environment(s) configured on your Production instance that are assigning a non datetime value to this variable.