Mapping proc output to vars gets error extracting result into a variable of type (DBTYPE_UI2)

Question

Hi, we run std 2012.  I have a proc (sets nocount on) whose params r shown in the first block .   My execute ssis sql task mapping is shown in the block following that (same order as shown, the param sizes are all -1).  The variable
characteristics and initial values are shown in the 3rd block.  The execute sql task command is
exec usp_fileArrivalStatus ?,?,?,?,?,? output,? output,? output
when I run the proc in ssms followed by a select on the output fields, I get stat 0, instance id -1 and file name empty string (aka tick tick aka '')
The error is:
[Execute SQL Task] Error: Executing the query "exec usp_fileArrivalStatus ?,?,?,?,?,? output,? ou..." failed with the following error:
"An error occurred while extracting the result into a variable of type (DBTYPE_UI2)".
Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
Does anybody know what is wrong?
CREATE PROCEDURE [dbo].[usp_fileArrivalStatus] @NewFilePattern varchar(500),
@PkgName varchar (257),
@appid int,
@MsgHistCreateDate date,
@messageFriendlyName varchar(500),
@arrivalStatus int output,
@instanceId bigint output,
@fileName varchar(500) output
VariableName Direction DataType ParamName
User::TranFilePattern Input VARCHAR 0
System::PackageName Input VARCHAR 1
User::AppID Input SHORT 2
User::todaysDate Input DATE 3
User::TranFileArriveStatus OUTPUT SHORT 5
User::TranFileInstanceId OUTPUT LARGE_INTEGER 6
User::TranFileName OUTPUT VARCHAR 7
User::TranFileFriendlyName Input VARCHAR 4
User::TranFilePattern,string,tranfile05-Nov-2014
User::fileDate,string,05-Nov-2014
System::PackageName,
User::AppID,int32,12
User::todaysDate,DateTime, set by select getdate()
User::TranFileArriveStatus,int32,0
User::TranFileInstanceId,Int64,0
User::TranFileName,string
User::TranFileFriendlyName,string,Tran File

Answer 1

I may have gotten past this.  The ui showed the first execution of that proc as the aborting component but when I looked at my error code (-1073548784), and component name in the
message sent with notification email, I noticed the second component name.  It too executes that proc and still had ushort for appid in sql task mapping and long for instance id.  I changed these characteristics to match what I posted and got green
on the seq container that runs both.
I think I go thru this kind of adventure every time I try to map proc output to ssis vars.