VoiceGuide IVR Software Main Page
Jump to content

Trace Log Shows The Following Error:

Recommended Posts

Dear Support,

 

My script raises an error and hangs up when I try to login through IVR.

I found out that in my VBScript, UserID variable remains empty because it does not get the value of $RV[userID]

I am attaching the trace log.

It has the following lines of error description:

"VGMTYPE_EVALEXPR InvokeMember Eval : Exception has been thrown by the target of an invocation."

 

Please let me know what is going wrong.

 

Thanks.

0804_1731_vgEngine.zip

Share this post


Link to post

This just tells you that the expression you were trying to evaluate was an invalid expression and could not be evaluated.

 

We'll change what is logged in the trace file to properly reflect that. In the meantime:

 

In your script, the module [isAllowedIncomingNUmber] has this expression:

 

$RV[isAllowedPhoneNumber] = true

 

and when the expression is not true (or invalid after the $RV substitution) then the Fail path is taken, or the call is ended if Fail path is not defined (as it has been in this case).

 

The $RV[isAllowedPhoneNumber] is not defined in your script, so it gets replaced with an empty string.

 

Recommend you change the expression to something like this:

 

"$RV[isAllowedPhoneNumber]" = "true"

 

then at least you will not get an 'invalid expression' error.

Share this post


Link to post

Thanks for the reply, but the error that matters has taken place before the script tries to assign a value for $RV[isAllowedPhoneNumber].

 

My script takes $RV[userID] by using, RV_UserID = $RV[userID], which should have a value at this moment and set to RV at [GenerateMainMenu] module.

But for soem reason (I changed the code in copule of modules to unify the connection string by the way), it now returns nothing.

 

If you see the trace log, RV is added for UserID with value of 93297 in many places. But the value cannot obtained in this script.

 

Please let me know why I cannot retrieve the RV already set.

 

Thanks.

 

 

Share this post


Link to post

I guess I figured out the cause of the problem: I accidently skipped to open a recordset for one query for authentication.

You can ignore this case as I think it is closed now.

 

Thanks for your help though!

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×