Welcome Inspire Pilots!
Join our free DJI Inspire community today!
Sign up

[fixed] Camera Exporter (Windows) crashes when clicking on export

Joined
May 12, 2019
Messages
5
Reaction score
0
On a Windows 10 system I installed DjiCameraExporter.1.0.0.11. When starting the application, the SSD shows up with the clips. When clicking Export, the application crashes.

The application previously worked fine on the same computer, but not on the new operating system installation.

Output from the event viewer:

Code:
Application: DjiCameraExporter.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException
   at System.Windows.Forms.FolderBrowserDialog.RunDialog(IntPtr)
   at System.Windows.Forms.CommonDialog.ShowDialog(System.Windows.Forms.IWin32Window)
   at System.Windows.Forms.CommonDialog.ShowDialog()
   at DjiCameraExporter.MainWindow.OnExportButtonClick(System.Object, System.Windows.RoutedEventArgs)
   at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs)
   at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)
   at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs)
   at System.Windows.UIElement.RaiseEvent(System.Windows.RoutedEventArgs)
   at System.Windows.Controls.Primitives.ButtonBase.OnClick()
   at System.Windows.Controls.Button.OnClick()
   at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(System.Windows.Input.MouseButtonEventArgs)
   at System.Windows.UIElement.OnMouseLeftButtonUpThunk(System.Object, System.Windows.Input.MouseButtonEventArgs)
   at System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(System.Delegate, System.Object)
   at System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object)
   at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs)
   at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)
   at System.Windows.UIElement.ReRaiseEventAs(System.Windows.DependencyObject, System.Windows.RoutedEventArgs, System.Windows.RoutedEvent)
   at System.Windows.UIElement.OnMouseUpThunk(System.Object, System.Windows.Input.MouseButtonEventArgs)
   at System.Windows.Input.MouseButtonEventArgs.InvokeEventHandler(System.Delegate, System.Object)
   at System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object)
   at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs)
   at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean)
   at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs)
   at System.Windows.UIElement.RaiseTrustedEvent(System.Windows.RoutedEventArgs)
   at System.Windows.UIElement.RaiseEvent(System.Windows.RoutedEventArgs, Boolean)
   at System.Windows.Input.InputManager.ProcessStagingArea()
   at System.Windows.Input.InputManager.ProcessInput(System.Windows.Input.InputEventArgs)
   at System.Windows.Input.InputProviderSite.ReportInput(System.Windows.Input.InputReport)
   at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr, System.Windows.Input.InputMode, Int32, System.Windows.Input.RawMouseActions, Int32, Int32, Int32)
   at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr, MS.Internal.Interop.WindowMessage, IntPtr, IntPtr, Boolean ByRef)
   at System.Windows.Interop.HwndSource.InputFilterMessage(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 DjiCameraExporter.App.Main()

Faulting application name: DjiCameraExporter.exe, version: 1.0.0.0, time stamp: 0x56e26794
Faulting module name: KERNELBASE.dll, version: 10.0.17763.475, time stamp: 0x9877ee8b
Exception code: 0xe0434352
Fault offset: 0x0011c762
Faulting process id: 0x1460
Faulting application start time: 0x01d51538c46dc28a
Faulting application path: C:\Users\<HIDDEN>\AppData\Local\Apps\2.0\NZ8JPRHE.2MQ\VG8VO914.B2G\djic..tion_e7d59a5fef768c67_0001.0000_6ad1349a72538f79\DjiCameraExporter.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 8e3de37b-22f0-4274-8796-a107e5471a41
Faulting package full name:
Faulting package-relative application ID:


Fault bucket 2249203885360613634, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: DjiCameraExporter.exe
P2: 1.0.0.0
P3: 56e26794
P4: System.Windows.Forms
P5: 4.7.3324.0
P6: 5c09ba04
P7: 21a8
P8: 4a
P9: System.InvalidOperationException
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER80FB.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER81D7.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER81E7.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER81E5.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER8206.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_DjiCameraExporte_fe31c692234d43cdbdfeb8fc4cdfa785153e4_2560e88a_357285ae

Analysis symbol:
Rechecking for solution: 0
Report Id: 8e3de37b-22f0-4274-8796-a107e5471a41
Report Status: 268435456
Hashed bucket: 86583416836c12c9ff36c70456590902
Cab Guid: 0
And the wer file contents: [too big to post, see here: Version=1 EventType=CLR20r3 EventTime=132035097670972393 ReportType=2 Consen - Pastebin.com]

This problem disallows me to do any work. It's critical that this problem can be resolved. Any help is highly appreciated.

Side question
: Is there any official DJI support in this forum?
 
Joined
May 12, 2019
Messages
5
Reaction score
0
The reason is, that I remapped the Desktop folder on my PC to a network drive. This caused the FolderBrowserDialog to fail, since network drive were not enabled and Desktop was set as the root folder. Two solutions to fix:

Fix:
  1. The obvious workaround: Remap the desktop folder to some local folder.
  2. Create a dword registry entry at Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\EnableLinkedConnections with value 1.

Details for fix 2.:
Note: To configure the EnableLinkedConnections registry value you need to follow these steps:


  1. Click Start, type regedit in the Start programs and files box, and then press ENTER.
  2. Locate and then right-click the registry subkey HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System.
  3. Point to New, and then click DWORD Value.
  4. Type EnableLinkedConnections, and then press ENTER.
  5. Right-click EnableLinkedConnections, and then click Modify.
  6. In the Value data box, type 1, and then click OK.
  7. Exit Registry Editor, and then restart the computer.

 
Joined
Jun 28, 2016
Messages
757
Reaction score
271
Age
56
Glad you found a fix. My favorite fixes happen in the registry.

Off topic...

If you ever get tired of Cortana (which I've hated from day one), there's a great DWORD hack to get rid of that beotch, too. I'll post it if you're interested.

D
 
  • Like
Reactions: spark
Joined
May 12, 2019
Messages
5
Reaction score
0
If you ever get tired of Cortana (which I've hated from day one), there's a great DWORD hack to get rid of that beotch, too. I'll post it if you're interested.
Thanks. Haven't yet had to meet Cortana as I've always disabled it when installing Windows.
 

New Threads

Members online

Forum statistics

Threads
19,249
Messages
189,204
Members
28,510
Latest member
HueyAddis