Any idea why the below given error occurs ?

ExceptionGUID: b278179b-f7cc-46fd-bd16-4e12eeb99416
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
InnerException: Conversion from type 'DBNull' to type 'Integer' is not valid.
Message: DotNetNuke.Services.Exceptions.ModuleLoadException: Conversion from type 'DBNull' to type 'Integer' is not valid. ---> System.InvalidCastException: Conversion from type 'DBNull' to type 'Integer' is not valid. at Microsoft.VisualBasic.CompilerServices.Conversions.ToInteger(Object Value) at MyWebsite.Modules.LTShare.SqlDataProvider.AddLTBooking(Int32 bookingID, Int32 tripID, String name, String contactNo, String address, Int32 seatsPurchased, Double amountTransacted, String receiptNo, DateTime bookingDate, String destination, String paymentMode, String counterID) in c:\inetpub\wwwroot\ MyWebsite\App_Code\LTShare\SqlDataProvider.vb:line 111 at MyWebsite.Modules.LTShare.LTBookingController.Add(LTBookingInfo objLTBooking) in c:\inetpub\wwwroot\MyWebsite\App_Code\LTShare\LTBookingController.vb:line 98 at DesktopModules_LTBookingGUI_counter.cmdUpdate_Click(Object sender, EventArgs e) in c:\inetpub\wwwroot\MyWebsite\DesktopModules\LTBookingGUI\counter.ascx.vb:line 50 --- End of inner exception stack trace ---
Actually, this happens on the statment, controllerObject.Add(InfoObject) (this is the line depicted above on line 50)which inserts a rows into a table. The insert is working fine, but ends with the general exception "A critical error has occured".

Please help me on this. Thanking you in advance

regards

Praveen

I agree with Vladan, the code would be most helpful. What it boils down to is you are trying to convert a DBNull to an integer. Since this is happening post-update, I think your Info class may be getting a DBNull value from the database.

If you are using reflection ala DNN, then you could be failing on "bad" data. This again is happening when the DAL is trying to populate your Info class. Unfortunately DNN uses the FillObject from the CBO class. In this case you are going to have to make the offending fields required fields.

Using SQL Profiler, you can capture the stored procedure that is returning your data. Once you repeat the error find the get stored procedure and highlight it in SQL Profiler copy the line at the bottom and run it in Query Analyzer. The resulting rows returned will help you identify the offending record(s).

Thanks Vladan Strigo and HisKid for you very valuable replies......

The procedure in the controller file, was returning the integer value before. I changed the database structure, and thus there was nothing being returned from the function.

Now its working fine.....thanks again...

regards

Praveen