I see the error below whilst trying to download data. Please assist
Data Viewer Error:Exception handling
-
- Posts: 7
- Joined: April 29th, 2014, 9:32 am
- Location: Harare Zimbabwe
Data Viewer Error:Exception handling
RussMarange
-
- Posts: 1804
- Joined: December 5th, 2011, 11:27 pm
- Location: Washington, DC
Re: Data Viewer Error:Exception handling
Unfortunately the screenshot isn't so helpful because a lot of the details are cut off. Can you copy the exception text and paste it here?
Also, since this is seemingly a CSPro bug, you might consider trying to sync using logic and see if the problem still occurs.
1) Create an application (entry/batch) and attach your dictionary as an external dictionary.
2) syncconnect(Dropbox);
3) syncdata(GET, DICT_NAME);
Also, since this is seemingly a CSPro bug, you might consider trying to sync using logic and see if the problem still occurs.
1) Create an application (entry/batch) and attach your dictionary as an external dictionary.
2) syncconnect(Dropbox);
3) syncdata(GET, DICT_NAME);
-
- Posts: 7
- Joined: April 29th, 2014, 9:32 am
- Location: Harare Zimbabwe
Re: Data Viewer Error:Exception handling
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Runtime.InteropServices.SEHException (0x80004005): External component has thrown an exception.
at SyncClient.syncData(SyncClient* , SyncDirection , ISyncableDataRepository* , CStringT<wchar_t\,StrTraitMFC_DLL<wchar_t\,ATL::ChTraitsCRT<wchar_t> > >* )
at CSPro.Sync.SyncClient.syncData(SyncDirection direction, DataRepository repository, String universe, IProgress`1 progressPercent, IProgress`1 progressMessage, ValueType cancellationToken, OnSyncError onError)
at DataViewer.Synchronizer.<>c__DisplayClass4_0.<SyncDataAsync>b__0()
at System.Threading.Tasks.Task`1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at DataViewer.Synchronizer.<DownloadAsync>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at DataViewer.DownloadDialog.<buttonDownload_Click>d__16.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__6_0(Object state)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9139.0 built by: NET481REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
DataViewer
Assembly Version: 7.7.3.0
Win32 Version: 7.7.3.0
CodeBase: file:///C:/Program%20Files%20(x86)/CSPro%207.7/DataViewer.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9075.0 built by: NET481REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9139.0 built by: NET481REL1LAST_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9032.0 built by: NET481REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
zDataCLR
Assembly Version: 7.7.3.0
Win32 Version:
CodeBase: file:///C:/Program%20Files%20(x86)/CSPro%207.7/zDataCLR.DLL
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9032.0 built by: NET481REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9139.0 built by: NET481REL1LAST_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9032.0 built by: NET481REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
zDictCLR
Assembly Version: 7.7.3.0
Win32 Version:
CodeBase: file:///C:/Program%20Files%20(x86)/CSPro%207.7/zDictCLR.DLL
----------------------------------------
zUtilCLR
Assembly Version: 7.7.3.0
Win32 Version:
CodeBase: file:///C:/Program%20Files%20(x86)/CSPro%207.7/zUtilCLR.DLL
----------------------------------------
zBridgeCLR
Assembly Version: 7.7.3.0
Win32 Version:
CodeBase: file:///C:/Program%20Files%20(x86)/CSPro%207.7/zBridgeCLR.DLL
----------------------------------------
Microsoft.Web.WebView2.WinForms
Assembly Version: 1.0.1020.30
Win32 Version: 1.0.1020.30
CodeBase: file:///C:/Program%20Files%20(x86)/CSPro%207.7/Microsoft.Web.WebView2.WinForms.DLL
----------------------------------------
Microsoft.Web.WebView2.Core
Assembly Version: 1.0.1020.30
Win32 Version: 1.0.1020.30
CodeBase: file:///C:/Program%20Files%20(x86)/CSPro%207.7/Microsoft.Web.WebView2.Core.DLL
----------------------------------------
zSyncCLR
Assembly Version: 7.7.3.0
Win32 Version:
CodeBase: file:///C:/Program%20Files%20(x86)/CSPro%207.7/zSyncCLR.DLL
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Runtime.InteropServices.SEHException (0x80004005): External component has thrown an exception.
at SyncClient.syncData(SyncClient* , SyncDirection , ISyncableDataRepository* , CStringT<wchar_t\,StrTraitMFC_DLL<wchar_t\,ATL::ChTraitsCRT<wchar_t> > >* )
at CSPro.Sync.SyncClient.syncData(SyncDirection direction, DataRepository repository, String universe, IProgress`1 progressPercent, IProgress`1 progressMessage, ValueType cancellationToken, OnSyncError onError)
at DataViewer.Synchronizer.<>c__DisplayClass4_0.<SyncDataAsync>b__0()
at System.Threading.Tasks.Task`1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at DataViewer.Synchronizer.<DownloadAsync>d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at DataViewer.DownloadDialog.<buttonDownload_Click>d__16.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__6_0(Object state)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9139.0 built by: NET481REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
DataViewer
Assembly Version: 7.7.3.0
Win32 Version: 7.7.3.0
CodeBase: file:///C:/Program%20Files%20(x86)/CSPro%207.7/DataViewer.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9075.0 built by: NET481REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9139.0 built by: NET481REL1LAST_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9032.0 built by: NET481REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
zDataCLR
Assembly Version: 7.7.3.0
Win32 Version:
CodeBase: file:///C:/Program%20Files%20(x86)/CSPro%207.7/zDataCLR.DLL
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9032.0 built by: NET481REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9139.0 built by: NET481REL1LAST_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9032.0 built by: NET481REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
zDictCLR
Assembly Version: 7.7.3.0
Win32 Version:
CodeBase: file:///C:/Program%20Files%20(x86)/CSPro%207.7/zDictCLR.DLL
----------------------------------------
zUtilCLR
Assembly Version: 7.7.3.0
Win32 Version:
CodeBase: file:///C:/Program%20Files%20(x86)/CSPro%207.7/zUtilCLR.DLL
----------------------------------------
zBridgeCLR
Assembly Version: 7.7.3.0
Win32 Version:
CodeBase: file:///C:/Program%20Files%20(x86)/CSPro%207.7/zBridgeCLR.DLL
----------------------------------------
Microsoft.Web.WebView2.WinForms
Assembly Version: 1.0.1020.30
Win32 Version: 1.0.1020.30
CodeBase: file:///C:/Program%20Files%20(x86)/CSPro%207.7/Microsoft.Web.WebView2.WinForms.DLL
----------------------------------------
Microsoft.Web.WebView2.Core
Assembly Version: 1.0.1020.30
Win32 Version: 1.0.1020.30
CodeBase: file:///C:/Program%20Files%20(x86)/CSPro%207.7/Microsoft.Web.WebView2.Core.DLL
----------------------------------------
zSyncCLR
Assembly Version: 7.7.3.0
Win32 Version:
CodeBase: file:///C:/Program%20Files%20(x86)/CSPro%207.7/zSyncCLR.DLL
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
RussMarange
-
- Posts: 7
- Joined: April 29th, 2014, 9:32 am
- Location: Harare Zimbabwe
Re: Data Viewer Error:Exception handling
An error message " The parameter is incorect" pops up towards finishing downloading.Gregory Martin wrote: ↑March 17th, 2023, 4:14 pm Unfortunately the screenshot isn't so helpful because a lot of the details are cut off. Can you copy the exception text and paste it here?
Also, since this is seemingly a CSPro bug, you might consider trying to sync using logic and see if the problem still occurs.
1) Create an application (entry/batch) and attach your dictionary as an external dictionary.
2) syncconnect(Dropbox);
3) syncdata(GET, DICT_NAME);
Moreover i decided to set my application in download mode and i downloaded via csentry. I did successifully but the data file cant be opened on the Laptop.
Kindly assist, am now stranded
RussMarange
-
- Posts: 7
- Joined: April 29th, 2014, 9:32 am
- Location: Harare Zimbabwe
Re: Data Viewer Error:Exception handling
Here is what i did:
First Solution
1. I downloaded my data from dropbox to the android phone. then i removed some cases that looked to have bad structure..
2. I then created another dropbox account and send the data from that android with many cases to new server.
3. I then downloaded it to the desktop without a problem.
Second solution.
I went through my production dropbox account and removed some files that were there before the time of interest.
2.I then downloaded using data viewer and it worked perfectly.
3. So the cause was bad case.
However i spend a day.
First Solution
1. I downloaded my data from dropbox to the android phone. then i removed some cases that looked to have bad structure..
2. I then created another dropbox account and send the data from that android with many cases to new server.
3. I then downloaded it to the desktop without a problem.
Second solution.
I went through my production dropbox account and removed some files that were there before the time of interest.
2.I then downloaded using data viewer and it worked perfectly.
3. So the cause was bad case.
However i spend a day.
RussMarange
-
- Posts: 1804
- Joined: December 5th, 2011, 11:27 pm
- Location: Washington, DC
Re: Data Viewer Error:Exception handling
So your solution solved the problem, or it is still pending?
We are actually reworking some of the sync code for CSPro 8.0 to support syncing binary data, so we'll try to keep an eye out for what might have caused this problem.
We are actually reworking some of the sync code for CSPro 8.0 to support syncing binary data, so we'll try to keep an eye out for what might have caused this problem.