Registration for an event fails in .Save

I know it's a data problem with the particular member but I haven't a clue as to the culprit. I'm able to register for this event for everyone but this particular member. I did a step thru this morning and was able to determine that it's stopping at the cregistration.save operation.

Here is part of the code

Dim regIndividual As New CRegistration(user, eventCode, row("ST_ID"), False, False)
.
. lots of logic in here
.
Try
regIndividual.Validate()
Catch ex As Exception
.
. no error here
.
End Try
Try
regIndividual.Save()
Catch ex As Exception
.
. errors here
.
End Try

I know it's a SQL error because (one time) I found a SQL error in the regIndividual description. Here is part of the error:

StackTrace = " at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExcep...

I also got the following in the catch block:

" at Asi.iBO.Events.CRegistration.PrepOrderForSave()
at Asi.iBO.Events.CRegistration.Save(DataServer server)
at Asi.iBO.Events.CRegistration.Save()
at EventBilling.eventRegistration() in C:\dotNet\HAAWEBdotNET\Custom\EventRegistration\EventBilling.aspx.vb:line 615"

I know that if this happens once, it will happen again. Also this user is going to want to register for other classes and he will not be able to.

If anyone has a clue as to which field in iMIS I might be looking for, I'd greatly appreciate the help.

Thanks,

Mary

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Mary, if you can post the

Mary, if you can post the exact error message and the full stack trace (or e-mail them to me at emeans@advsol.com) I can help you determine the problem (and start the ball rolling on a fix if it turns out to be a bug).

Can't duplicate today

I went back in to get the full error message and stack trace. I set verisign to test mode and entered a test CC number. You guessed it, it registered him.

Yesterday, I was able to duplicate the problem the user had using a Discover card and regular verisign connection. It made the charge to his CC but errored out in the .save call.

I'm sure I'll see it again. I've added the full stack trace to the error message that is emailed to me so we'll be a step ahead.

Thanks for your quick response. Wish we could have pursued it further.

Mary

No problem Mary, just let me

No problem Mary, just let me know if you hit it again and we'll try tracking it down again. :)