initial crash after update to build 1901
Posted: Thu May 29, 2014 3:59 pm
Hi,
We're seeing some very odd and (currently) unexplainable behavior from our reporting engine. When we install a new store, or upgrade an old one, the very first time the user generates a receipt, we see a handful of errors. There's a 404 on a webresource.axd error, as well as an error:
The funny thing is, after that first glitch, everything seems to be functioning correctly.
Research suggests this only happens on the HTML5 reporting engine, the Flash version does not suffer the same issues..
Our code is designed to allow a user to switch back and forth between the reporting engines, as some of them have better luck printing from one or the other. But all the main logic to query the database and fill a datatable is done before we call the view, consequently, before any report rendering is initiated.
We're seeing some very odd and (currently) unexplainable behavior from our reporting engine. When we install a new store, or upgrade an old one, the very first time the user generates a receipt, we see a handful of errors. There's a 404 on a webresource.axd error, as well as an error:
Code: Select all
GetReportSnapshot OrderEntry Object reference not set to an instance of an object. RTP
at RTP.Helpers.Stimulsoft.DataTableLoad(DataTable t, List`1 colList, ObjectResult oReceiptData) in c:\work\Webstore\ws_trunk\tmpFlex_RenameMe\RTP\RTP\Helpers\Stimulsoft.cs:line 632
at RTP.Helpers.Stimulsoft.ReceiptPrepare(StimReportVO rptVO) in c:\work\Webstore\ws_trunk\tmpFlex_RenameMe\RTP\RTP\Helpers\Stimulsoft.cs:line 134
at RTP.Controllers.OrderEntryController.GetReportSnapshot() in c:\work\Webstore\ws_trunk\tmpFlex_RenameMe\RTP\RTP\Controllers\OrderEntryController.cs:line 1157
at lambda_method(Closure , ControllerBase , Object[] )
at System.Web.Mvc.ActionMethodDispatcher.Execute(ControllerBase controller, Object[] parameters)
at System.Web.Mvc.ReflectedActionDescriptor.Execute(ControllerContext controllerContext, IDictionary`2 parameters)
at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethod(ControllerContext controllerContext, ActionDescriptor actionDescriptor, IDictionary`2 parameters)
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass42.<BeginInvokeSynchronousActionMethod>b__41()
at System.Web.Mvc.Async.AsyncResultWrapper.<>c__DisplayClass8`1.<BeginSynchronous>b__7(IAsyncResult _)
at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult`1.End()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethod(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass37.<>c__DisplayClass39.<BeginInvokeActionMethodWithFilters>b__33()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass4f.<InvokeActionMethodFilterAsynchronously>b__49()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass4f.<InvokeActionMethodFilterAsynchronously>b__49()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass37.<BeginInvokeActionMethodWithFilters>b__36(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult`1.End()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethodWithFilters(IAsyncResult asyncResult)
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass25.<>c__DisplayClass2a.<BeginInvokeAction>b__20()
at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass25.<BeginInvokeAction>b__22(IAsyncResult asyncResult)
Research suggests this only happens on the HTML5 reporting engine, the Flash version does not suffer the same issues..
Our code is designed to allow a user to switch back and forth between the reporting engines, as some of them have better luck printing from one or the other. But all the main logic to query the database and fill a datatable is done before we call the view, consequently, before any report rendering is initiated.