Error reading variable

I keep receiving errors while using variables to pass values to different part of my package. For example ...

Error: 2006-05-04 10:31:59.84
Code: 0xC00470EA
Source: EdwPostProcess
Description: Reading the variable "User::GvPathRoot" failed with error code 0xC0010009.
End Error

The way my variables are constructed is :

First the global variables (Gv*) are set by the parent package; Then local variables (Lv*) are set using the EvaluateAsExpression property and giving it an expression that takes the Gv* variable and concatenate a string to it.

At execution time, while the expressions are resolved, I get the above error while it was resolved correctly in a previous task.

I tried different method including duplicating my variables but without success. I'm running out of ideas

Gilles

Sorry I don't have an answer. But just wanted to report a very similar problem I am having. I am also at my wits' end since the problem cannot be reproduced at will.

I am also passing variable from parent package to a child package. There is a loop in the parent package and in each iteration, the value of this variable changes. There are 9 iterations of the loop and so 9 different values of this variable. Most of the times all the loops are successful (particularly if the volume of data is less). If the volume of data processed by the child package is more then I sometimetimes get this error in the 5th or later iteration. I have changed the order of the values of the variable but looks like it does not matter - it fails at different values.

Ketan

|||

My variable was used in a script task and in expressions on other tasks. By re-arranging my tasks flow so the script task wouldn't be executed at the same time as another task with the same variable seem to have corrected the problem.

A variable used by a script task is lock in memory even when it is used for read only. So depending on how fast each task completes, it is possible that sometime we encounter the variable locked situation sometime not.

I found a way to eliminate the script task from my flow and everything is fine now.

Gilles

|||Another good technique to minimise locking is to reduce the scope of variables. You may end up with what seem like duplicates, by scoping variables to loops and containers or tasks, but this is more reliable than sharing variables when strictly speaking you never use the value outside of the lower scoped executable.

Error reading variable

I keep receiving errors while using variables to pass values to different part of my package. For example ...

Error: 2006-05-04 10:31:59.84
Code: 0xC00470EA
Source: EdwPostProcess
Description: Reading the variable "User::GvPathRoot" failed with error code 0xC0010009.
End Error

The way my variables are constructed is :

First the global variables (Gv*) are set by the parent package; Then local variables (Lv*) are set using the EvaluateAsExpression property and giving it an expression that takes the Gv* variable and concatenate a string to it.

At execution time, while the expressions are resolved, I get the above error while it was resolved correctly in a previous task.

I tried different method including duplicating my variables but without success. I'm running out of ideas

Gilles

Sorry I don't have an answer. But just wanted to report a very similar problem I am having. I am also at my wits' end since the problem cannot be reproduced at will.

I am also passing variable from parent package to a child package. There is a loop in the parent package and in each iteration, the value of this variable changes. There are 9 iterations of the loop and so 9 different values of this variable. Most of the times all the loops are successful (particularly if the volume of data is less). If the volume of data processed by the child package is more then I sometimetimes get this error in the 5th or later iteration. I have changed the order of the values of the variable but looks like it does not matter - it fails at different values.

Ketan

|||

My variable was used in a script task and in expressions on other tasks. By re-arranging my tasks flow so the script task wouldn't be executed at the same time as another task with the same variable seem to have corrected the problem.

A variable used by a script task is lock in memory even when it is used for read only. So depending on how fast each task completes, it is possible that sometime we encounter the variable locked situation sometime not.

I found a way to eliminate the script task from my flow and everything is fine now.

Gilles

|||Another good technique to minimise locking is to reduce the scope of variables. You may end up with what seem like duplicates, by scoping variables to loops and containers or tasks, but this is more reliable than sharing variables when strictly speaking you never use the value outside of the lower scoped executable.

error on insert...

I'm getting an error on the insert... I recently when to switch over from the @.param.Oledb type and am now using the ? for the values... Well I switched my updates and now am working on the inserts, but I am getting the error from this statement. I tried taking off the VALUES portion, but that didn't work either...

queryString = "INSERT INTO [griff30_24_stats] ([W_Rec], [Opponent], [L_Rec], [points], [done]) VALUES(?, ?, ?, ?,)"

Dim cmd as new OleDbCommand(queryString,dbConnection)

cmd.Parameters.Add("W_Rec",OleDbType.VarChar).Value = "Y"

'''It looks like you have 5 columns but only 4 question marks. Add afinal question mark (?) after that last comma and that should help.
|||

Thats a copy paste error. I have 5 "?'s" in the code, but I was going wild with the backspace. I still don't see why it's giving me the error is there a different style??

|||Can you show us a little more of the code as well as the exact error message?|||

Man, it was a little syntax error, I was missing a '(apostrophe in a statement). The little things I look over.

Error message help

I have a report parameter called @.OffenseCode and it is just a string
and also allows null values.
For some reason, I am getting the below error message, which I don't
know how to decipher. Any ideas?
"The value expression for the query parameter '@.OffenseCode'
contains an error: [BC30456] 'OffenseCode' is not a member of
'Microsoft.ReportingServices.ReportProcessing.ReportObjectModel.Parameters'."
Thank you!!!To access a Parameter value from an expression you will need to use the
following snytax.
=Parameters!@.OffenseCode.Value
if your parameter name is @.OffenseCode it may simply be OffenseCode in
which case you would need to use
=Parameters!OffenseCode.Value
You can check by going to the Report Menu, Report Parameters, this will
list all your parameters for the report and their names

error message for blank reports

When requesting reports, if a user supplies values in the parameters
for which there is no data on the database, how can I stop him/her on
this screen with an error popup display box or a message on the report
like 'no records available for the specified criteria' instead of
generating a blank report with only headers and footers.I am not sure about the other data regions such as list or matrix, but I know
that if you are using a table you can go into the table properties and put
the message that you would like to display under the "No Rows" property.
"bevarg" wrote:
> When requesting reports, if a user supplies values in the parameters
> for which there is no data on the database, how can I stop him/her on
> this screen with an error popup display box or a message on the report
> like 'no records available for the specified criteria' instead of
> generating a blank report with only headers and footers.
>|||Check the NoRows property of the table. You can enter a message there.