3

Closed

Program stops working

description

After connection I select a role and click Export. CRM 2015 Office 365. Windows 8.1

I receive RoleSheetExplorer has stopped working message.

Degub gives me "System.NullReferenceException", Object reference not set to an instance of an object.

Event View Log
Error 2/2/2016 9:25:26 AM Application Error 1000 (100)
Faulting application name: RoleSheetExporter.exe, version: 3.2.0.0, time stamp: 0x568be8e0
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0dda8283
Faulting process id: 0x2fb8
Faulting application start time: 0x01d15dcde459855f
Faulting application path: C:\Users\khester\Downloads\RoleSheetExporter 3.2.0.0\RoleSheetExporter.exe
Faulting module path: unknown
Report Id: 2ee4b54d-c9c1-11e5-8264-342387fe7422
Faulting package full name:
Faulting package-relative application ID:

Application: RoleSheetExporter.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
at RoleSheetExporter.MainWindow.<orgParameteredCallBack>b__6(Microsoft.Xrm.Sdk.Metadata.EntityMetadata)
at System.Linq.Enumerable+WhereArrayIterator`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].MoveNext()
at RoleSheetExporter.MainWindow.orgParameteredCallBack(Microsoft.Xrm.Sdk.OrganizationResponse, System.Object)
at AsyncServices.AsyncService.newOrgWorker_RunWorkerCompleted(System.Object, System.ComponentModel.RunWorkerCompletedEventArgs)
at System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(System.ComponentModel.RunWorkerCompletedEventArgs)
at System.ComponentModel.BackgroundWorker.AsyncOperationCompleted(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
at System.Windows.Application.RunDispatcher(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window)
at System.Windows.Application.Run(System.Windows.Window)
at RoleSheetExporter.App.Main()
Closed Apr 6, 2016 at 7:54 AM by Johninfant

comments

Johninfant wrote Apr 4, 2016 at 10:58 AM

Hi

Can you please attach a screenshot of the app, when the error occurs? Want to see how far the app runs before getting into exception. Need to see the console area.

Regards,
John

Johninfant wrote Apr 6, 2016 at 7:54 AM

Hi this issue is fixed in v3.4 I just uploaded. Please verify.

Thanks for reporting. :)

wrote Apr 6, 2016 at 7:54 AM