September 20, 2012 at 9:52 am
I'm getting the error below, just to preface...I do have all my package variables in the package level/scope, could there be another reason as to why this is occurring or other things i should try first?
dtexec /f "D:\SSISPackages\TEST_REPORT.dtsx" /set "\package.variables[User::ReportID].Properties.Value";"95E56F3A-DBEF-4FA1-B3E9-92A4BCB15E42"
Microsoft (R) SQL Server Execute Package Utility
Version 10.50.2500.0 for 64-bit
Copyright (C) Microsoft Corporation 2010. All rights reserved.
NULL
Started: 10:54:02 AM
Warning: 2012-09-20 10:54:02.72
Code: 0x80012017
Source: TEST_REPORT
Description: The package path referenced an object that cannot be found:
"\package.variables[User::ReportID].Properties.Value". This occurs when an
attempt is made to resolve a package path to an object that cannot be found.
End Warning
DTExec: Could not set \package.variables[User::ReportID].Properties.Value
value to 6A48D31E-3356-41C2-8BA7-A4C73869D5F1.
Started: 10:54:02 AM
Finished: 10:54:02 AM
Elapsed: 0.468 seconds
NULL
September 20, 2012 at 11:04 am
Variables in SSIS are case-sensitive, i.e. \Package.Variables[User::ReportID].Properties.Value is not the same as \package.variables[User::ReportId].Properties.Value, so first verify you're referencing the correct name.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
September 20, 2012 at 11:27 am
I solved the issue, it seems that running this line will always throw an error...
exec master..xp_cmdshell 'dtexec /f "D:\SSISPackages\TEST_REPORT.dtsx" /set "\package.variables[User::ReportID].Properties.Value";"95E56F3A-DBEF-4FA1-B3E9-92A4BCB15E42"'
But running it in this scrict form below always works...(weird?!?!)
set @ssispath = 'D:\SSISPackages\TEST_REPORT.dtsx'
set @ReportID = '95E56F3A-DBEF-4FA1-B3E9-92A4BCB15E42'
select @cmd = 'dtexec /F "' + @ssispath + '"'
select @cmd = @cmd + ' /SET \Package.Variables[User::ReportID].Properties[Value];"' + @ReportID + '"'
exec master..xp_cmdshell @cmd
Thanks again to everyone for their help...I hope this helps everyone with this similar issue...I know I surely learned from this issue as well as from everyone's help 🙂
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply