Login Page - Create Account

Support Board


Date/Time: Wed, 17 Jan 2018 09:24:06 +0000



error msg

Support Request:
[2017-12-05 15:06:19]
User98657 - Posts: 96
I'm getting this new error message. When i get the error message I'm unable to do anything in the program. It is still running, I just cant do anything until I click the "OK" button. It seems I have to click it roughly 49 times to completely clear the message. This just started in the past couple of days.

I have updated since it began so not likely related to the version.

screencast.com/t/PvsOBYp8spoa

i can't post a screen shot of the error because once it occurs i cant access the menu bar until i clear the message. i've attached the screenshot location of the picture of the error if you'd care to look.

The message log says : Caught an unhandled exception in c_Chart:WindowProc. Message: 15, wParam: 0, IParam: 0|2017-12-05 08:49:02

This message is being repeated continually about every half-second or so (I'm seeing two messages per second). It seems to get to a point of overflow then throws the error message on the screen forcing me to click out of it roughly 49 times to clear it.
[2017-12-05 15:12:47]
User98657 - Posts: 96
Update:

I exited SC and restarted. No new occurrence in the first few minutes of operation. i will try to monitor for a cause.
[2017-12-05 18:23:26]
Sierra Chart Engineering - Posts: 56211
This is a Windows 10 issue. Unfortunately, Microsoft is producing very unreliable software. It really is very sad the problems Microsoft is having and their incompetence.

We ourselves are affected by very serious problems with Visual C++/Visual Studio.

To the point, where we eventually have to migrate away from those programs.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
Date Time Of Last Edit: 2017-12-05 18:23:58
[2017-12-05 18:27:15]
User98657 - Posts: 96
So for now is the solution to simply exit and restart SC?
[2017-12-05 18:47:39]
Sierra Chart Engineering - Posts: 56211
Any time you encounter a message like this:

The message log says : Caught an unhandled exception in c_Chart:WindowProc. Message: 15, wParam: 0, IParam: 0|2017-12-05 08:49:02

A restart of Sierra Chart is necessary.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
[2017-12-07 17:50:37]
User98657 - Posts: 96
This error is appearing several times a day now.

Have you, as my software provider, contacted Microsoft and tried to find a solution to this for your end users?

Why should each of us having this issue have to try to sort it out with Microsoft. You, as engineers, are certainly in a much better position to deal with them on this (as unpleasant as you may find that to be).
[2017-12-07 18:38:35]
Sierra Chart Engineering - Posts: 56211
We will see if we can reproduce the problem on Windows 10.

If we cannot, then we really do not know what we could do about this. Even if we were to test your Chartbook, we are not going to encounter the problem because we have run through that type of test with another user before. And we could not reproduce it. But we can try again in your case.

Whatever is causing the problem, Microsoft most likely is already aware of it and we would expect it eventually gets resolved.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
Date Time Of Last Edit: 2017-12-07 18:39:07
[2017-12-07 19:37:09]
Sierra Chart Engineering - Posts: 56211
This is from one of our programmers:
I am running Windows 10, and I have never encountered this error.

Provide us your Chartbook file that you are using when you encounter this. Here are instructions:

https://www.sierrachart.com/index.php?page=PostingInformation.php#AttachFile

Also the most reliable solution is to go back to Windows 7. And stay with that as long as possible. You should be fine for two years. Windows 10 is simply unstable.


We certainly have a large number of users using Windows 10. A rough estimate is maybe we have heard about this from about eight users. So most users are not experiencing this issue.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
Date Time Of Last Edit: 2017-12-07 19:44:02
[2017-12-07 19:51:27]
User98657 - Posts: 96
i would gladly downgrade to Win7, but i can't. MS has forced builders to move to Win10 and will not/has not provided the drivers i would need to run the machine.

i called the builder to see if i could simply strip Win 10 off the machine and load a fresh version of Win7. They said i would not be able to get the drivers for the chipsets on the machine and it would therefore not run. Believe me, if i could i'd go all the way back to XP. If my old machine were not failing i'd have stuck with it. now kind of wishing i had just found a way to rebuild that one.

i called MS and set up a tech support call with them. They called back, but unfortunately their server is down and i need to call back in a few hours. Go figure!!
Private File
Attachment Deleted.
[2017-12-07 19:55:05]
Sierra Chart Engineering - Posts: 56211
OK we are going to test this Chartbook on Windows 10 and see what we find out.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
[2017-12-07 20:05:22]
User98657 - Posts: 96
Ok, Thanks. But just a point of note: i don't recall the issue being limited to a specific chart book. I could me mistaken, but i do switch between two and can't say for sure that it only happens in this one. I do know for sure that it does happen in this CB, just not sure it's only related to THIS chartbook.
[2017-12-07 20:18:58]
Sierra Chart Engineering - Posts: 56211
Also make sure this option is disabled:
https://www.sierrachart.com/index.php?page=doc/GeneralSettings.html#DestroyChartWindowsWhenHidden
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
Private File
[2017-12-07 20:27:17]
User98657 - Posts: 96
It is disabled (never has been enabled)
[2017-12-07 20:40:27]
Sierra Chart Engineering - Posts: 56211
We see you are also using this: TradeControl.dll

Restart Sierra Chart in safe mode:
https://www.sierrachart.com/index.php?page=doc/LoginInstructions.php#UsingSafeMode

See if that resolves the problem.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
[2017-12-07 21:10:52]
User98657 - Posts: 96
Charts are running in Safe Mode now. i will let you know what happens.
[2017-12-08 16:43:33]
User98657 - Posts: 96
Just encountered an error message for "improper argument" while running in safe mode.

At 10:37 it began.
"Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam:0, lParam:0,|2017-12-08 10:37:42"
[2017-12-08 16:51:39]
User98657 - Posts: 96
After getting the error and send you the previous message I "saved all", exited SC and said yes to "save all?" during the exit.

I'm opening in safe mode. after startup i opened the chartbook i closed during the exit. it did not open the same way i closed it. a different chart opened (part of the chartbook, but not the chart i had open when i saved all). Also, two Fib levels that i have deleted twice so far today reappeared on the chart and a new Fib i inserted twice so far today was gone again.

fortunately my spreadsheet work did save.

But obviously there's something going on here if the chart is not saving. This is not the first time i've noticed this over the past few days, but it is the first time i've been able to accurately document it.

It would seem, from a layman's perspective, the error i'm encountering is affecting how the charts / chartbook is being saved - or not being saved as it were.

** To be clear, after deleting those previous Fibs and placing the new Fib, i had hit "save all" several times to ensure (or try to ensure) my spreadsheet work was being saved. While the spreadsheet work was saved, for whatever reason, the charts are not.
Date Time Of Last Edit: 2017-12-08 17:10:42
[2017-12-08 17:50:25]
Sierra Chart Engineering - Posts: 56211

It would seem, from a layman's perspective, the error i'm encountering is affecting how the charts / chartbook is being saved - or not being saved as it were.
Yes, this potentially can make sense. Once an unhandled exception occurs, it can affect the overall stability and functioning of Sierra Chart.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
[2017-12-08 18:40:35]
User98657 - Posts: 96
So that tells us that this problem is "systemic" (for lack of a better term) - meaning the issue is present regardless of getting the error message. If i'm telling SC to "save all" and it is not saving the charts, and there's no apparent error message, then obviously something is wrong from the start and the program is not operating correctly. And i don't say that to be accusatory, I'm trying to get some understanding of what's going on so i can try to find a solution.

So i just had a conversation with MS. From their perspective they really can't help me at this point.

They put it this way. They cannot state whether or not SC is compatible with Windows 10. They have no idea if you (SC) performed necessary upgrades to previous versions to ensure Win10 compatibility. And they also stated that Win10 is vastly different than 7 and there may very well be programs that did run on 7 that will need upgrading to run properly on 10.

With respect to our specific issue: They said the error message is being created by SC. They have no insight to SC (obviously) and therefore can't tell me what is causing the error. If, they said, the developers of the program can tell us why their program is generating the error they may be able to help me correct it if it is in fact a Win10 issue. So if you guys can tell me what exactly this "unhandled exception" refers to, or is caused by, i may be able to go back to them for help.
[2017-12-08 18:43:44]
User98657 - Posts: 96
Would it help to log onto my machine while the error is in play?
[2017-12-08 22:00:55]
Sierra Chart Engineering - Posts: 56211
We are going to do some additional testing of your chart book on Windows 10.


So that tells us that this problem is "systemic" (for lack of a better term) - meaning the issue is present regardless of getting the error message. If i'm telling SC to "save all" and it is not saving the charts, and there's no apparent error message, then obviously something is wrong from the start and the program is not operating correctly.

If you are having a problem with saving a Chartbook even before you encounter the unhandled exception, then it would be best to that we look at this issue using uusing remote assistance. We can do this over the weekend.

Just make sure your current telephone number is here:
https://www.sierrachart.com/UserControlPanel.php?page=ManageAccountInfo
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
Date Time Of Last Edit: 2017-12-08 22:02:17
[2017-12-08 22:01:55]
Sierra Chart Engineering - Posts: 56211
Corrections were made to the prior post. Refresh this page.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
[2017-12-08 22:20:25]
User98657 - Posts: 96
yes. That's the best number to use as it's the land-line at the house, next to the PC. my mobile is a better number to reach me, but not as reliable where the machine is located.

But i would need to know what time you'd be calling, at least a window of time.
[2017-12-08 22:31:46]
User98657 - Posts: 96
Also, Does this help us get closer to finding a solution?

I copied and pasted part of the message log. This time it seems to indicate a possible leading cause.
Scroll down to 16:25:35 and again at 16:39:25. you can see it tried to open a MDI detachable window at precisely the same time as the error chain started.
This is the first time i recall seeing something that appaered to be so directly associated with the error string.

HTTP connection to ds01.ddfplus.com:80 (64) | Socket gracefully closed by remote side. | 2017-12-08 16:23:16
HTTP connection to ds01.ddfplus.com:80 (64) | Received socket Close event. | 2017-12-08 16:23:16
HTTP connection to ds01.ddfplus.com:80 (64) | Initiating close of socket by core. | 2017-12-08 16:23:16
HTTP connection to ds01.ddfplus.com:80 (64) | Graceful close received or receive error. Shutdown complete. Closing socket now. | 2017-12-08 16:23:16
HTTP connection to ds01.ddfplus.com:80 (64) | Closed. | 2017-12-08 16:23:16
RTYH8 [CBV] 1 Day #1 | Reloading chart. | 2017-12-08 16:24:50
RTYH8 [CBV] 15 Min #2 | Reloading chart. | 2017-12-08 16:24:50
Not loading TradeControl.dll. ACS Safe Mode enabled. | 2017-12-08 16:24:50
RTYH8 [CB] Flex Renko 2-1-1 #3 | Reloading chart. | 2017-12-08 16:24:50
RTYH8 [CBV] 1 Day #4 | Reloading chart. | 2017-12-08 16:24:50
c_Chart::CreateDetachableWindow: Error creating the MDI child window. | 2017-12-08 16:24:50 *
c_Chart::CreateDetachableWindow: Error creating the MDI child window. | 2017-12-08 16:24:50 *
RTYH8 [CB] Flex Renko 2-1-1 #7 | Reloading chart. | 2017-12-08 16:24:50
c_Chart::CreateDetachableWindow: Error creating the floating window. | 2017-12-08 16:24:50 *
Not loading TradeControl.dll. ACS Safe Mode enabled. | 2017-12-08 16:24:50
c_Chart::CreateDetachableWindow: Error creating the floating window. | 2017-12-08 16:24:50 *
Requesting market depth updates for: RTYH8 if supported. | 2017-12-08 16:24:53
Not loading TradeControl.dll. ACS Safe Mode enabled. | 2017-12-08 16:24:54
+ Loading market depth data. | 2017-12-08 16:24:54
Loaded depth data records for RTYH8 2017-12-08 from 2017-12-08 08:30:02 to 2017-12-08 15:14:59. | 2017-12-08 16:24:54
c_Chart::CreateDetachableWindow: Error creating the MDI child window. | 2017-12-08 16:24:54 *
c_Chart::CreateDetachableWindow: Error creating the MDI child window. | 2017-12-08 16:24:54 *
Not loading TradeControl.dll. ACS Safe Mode enabled. | 2017-12-08 16:24:54
c_Chart::CreateDetachableWindow: Error creating the MDI child window. | 2017-12-08 16:24:54 *
c_Chart::CreateDetachableWindow: Error creating the MDI child window. | 2017-12-08 16:24:54 *
Not loading TradeControl.dll. ACS Safe Mode enabled. | 2017-12-08 16:25:35
c_Chart::CreateDetachableWindow: Error creating the MDI child window. | 2017-12-08 16:25:35 *
c_Chart::CreateDetachableWindow: Error creating the MDI child window. | 2017-12-08 16:25:35 *
Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-08 16:25:35 *
c_Chart::CreateDetachableWindow: Error creating the MDI child window. | 2017-12-08 16:25:39 *
c_Chart::CreateDetachableWindow: Error creating the MDI child window. | 2017-12-08 16:25:39 *
Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-08 16:25:39 *
Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-08 16:25:39 *
Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-08 16:25:48 *
Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-08 16:25:51 *
Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-08 16:25:51 *
Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-08 16:25:51 *
Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-08 16:25:51 *
Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-08 16:25:51 *
Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-08 16:25:51 *
Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-08 16:25:51 *
Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-08 16:25:51 *
Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-08 16:25:51 *
Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-08 16:25:51 *
Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-08 16:25:51 *
Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-08 16:25:51 *
Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-08 16:25:51 *
Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-08 16:25:51 *
Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-08 16:25:51 *
Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-08 16:25:51 *
Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-08 16:25:51 *
Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-08 16:25:51 *
Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-08 16:25:53 *
Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-08 16:25:53 *
Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-08 16:25:55 *
Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-08 16:27:19 *
Date Time Of Last Edit: 2017-12-08 22:34:25
[2017-12-08 22:40:48]
User98657 - Posts: 96
Here's another clue:

Usually, once the unhandled exception begins, it continues until it overflows then starts throwing the dialog box. This time it did not. BUT.... the moment i clicked on a detached window it immediately started throwing more errors and the dialog box appeared. when i cleared the dialog box and click OFF of the detached window and on to the message log window, the errors stopped.
[2017-12-08 22:43:08]
User98657 - Posts: 96
Can you please send an email and let me know what time to expect your call. i will not be sitting at my desk over the weekend except to work on this with you.
[2017-12-09 12:04:53]
Sierra Chart Engineering - Posts: 56211
It would be in the late afternoon Saturday.

In general we are not enthusiastic about this. We do not believe we can help. We will have a quick look at this. We have to make it clear what our position is.

It is unfortunate the problems that Microsoft is creating. If you want we can put your account on hold, until such time that Microsoft gets the problem resolved.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
Date Time Of Last Edit: 2017-12-09 20:50:55
[2017-12-09 20:51:27]
Sierra Chart Engineering - Posts: 56211
We just left you a voicemail and also sent you an email now.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
[2017-12-10 22:55:39]
Sierra Chart Engineering - Posts: 56211
For the record, the dialog box you are referring to is something like "encountered an improper argument".

This is a dialog box is from the Windows operating system, MFC or from the Visual C++ standard library. It is not from Sierra Chart.

Microsoft needs to update that to show the actual context of the error like the function it relates to.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
Date Time Of Last Edit: 2017-12-10 22:56:01
[2017-12-11 00:14:41]
Sierra Chart Engineering - Posts: 56211
We have released version 1665. Update to the "Prerelease" following the instructions here:
https://www.sierrachart.com/index.php?page=doc/SoftwareDownload.php#FastUpdate

If you see any messages in the Message Log which include the text "exception", then just provide those lines here and that will help us narrow down the problem.


This version will give us a much better idea of where the problem is actually occurring. Potentially we will then be able to solve it from our side.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
[2017-12-11 04:10:54]
User98657 - Posts: 96
Installed prerelease, V1665. I will let you know what happens.

Thanks for the help.
[2017-12-11 06:09:27]
Sierra Chart Engineering - Posts: 56211
OK let us know as soon as you can. We are very interested to see where the exception is occurring. Once we see that, we will then be able to narrow it down further.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
Date Time Of Last Edit: 2017-12-11 06:09:56
[2017-12-11 09:20:05]
sunnyod - Posts: 66
I have the same issue as you User98657. Got some other MS related issues too. See this thread. Not sure if they are related to this problem, but I didn't want to create a separate thread for this. I find that this dialog box error comes up when I try to save a chartbook, open a chart book or do something that requires a dialog to be navigated to. Thank you for following through with this, hopefully both my issues are related! Will be following this thread closely
[2017-12-11 14:24:05]
User98657 - Posts: 96
Well, it didn't take long.

Got the error very quickly this morning.

occurred when i expanded a chart to full screen.

Let me know what you need me to do (send, log in to my machine....)
[2017-12-11 14:53:47]
User98657 - Posts: 96
Caught the error again. at 8:52 central.
[2017-12-11 15:11:41]
User98657 - Posts: 96
Caught it again at 9:11 central.
[2017-12-11 17:37:22]
Sierra Chart Engineering - Posts: 56211
We just need you to provide the last 20 lines or so of the Message Log. You can copy them and then paste them here.

Or use the "Send for Analysis" button on the Message Log. If you use Send for Analysis, let us know when that is done.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
Date Time Of Last Edit: 2017-12-11 17:38:16
[2017-12-11 18:55:26]
User98657 - Posts: 96
It has occurred several times since my last message. I copied and saved the first few to notepad.

Here are the error messages from the first one i saved, let me know if you need the second one.


RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:29 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:29 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:30 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:30 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:30 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:31 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:32 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:32 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:33 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:33 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:34 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:34 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:35 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:35 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:36 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:36 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:37 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:37 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:38 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:38 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:39 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:39 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:40 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:40 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:41 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:41 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:42 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:42 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:43 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:43 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:44 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:44 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:45 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:45 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:46 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:46 *
ESH8 [CBV] Renko 2t #1 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:47 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:47 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:48 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:49 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:50 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:50 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:51 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:51 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:52 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:52 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:53 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:54 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:54 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:55 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:56 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:57 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:58 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:59 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:52:59 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:53:00 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:53:00 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:53:01 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:53:01 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:53:02 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:53:02 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:53:03 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:53:04 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:53:05 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:53:06 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:53:06 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:53:07 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:53:08 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:53:08 *
RTYH8 [CBV] 1 Day #15 | Caught an unhandled exception in c_Chart::WindowProc. Message: 15, wParam: 0, lParam: 0 | 2017-12-11 08:53:09 *
[2017-12-11 19:06:43]
Sierra Chart Engineering - Posts: 56211
This is all we need. What we can tell is the error is actually occurring someplace different than we thought.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
Date Time Of Last Edit: 2017-12-11 19:10:17
[2017-12-11 19:59:23]
Sierra Chart Engineering - Posts: 56211
We are going to be releasing version 1667 in about 10 minutes. This is a prerelease. Update to that version and provide us the Message Log lines with the exception messages.

At this point, we are not hopeful we can do anything about this. If the problem is where we think it is, that clearly is an issue on the side of Microsoft and we would not know what to do to work around it.

But we will see.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
Date Time Of Last Edit: 2017-12-11 19:59:46
[2017-12-11 20:17:00]
User98657 - Posts: 96
But can we get closer to telling MS where their problem lies?
[2017-12-11 20:26:42]
Sierra Chart Engineering - Posts: 56211
Yes. This new version is out.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
[2017-12-11 20:32:19]
User98657 - Posts: 96
ok, updated.
[2017-12-11 23:25:17]
User98657 - Posts: 96
Sorry, I had to bug out of the office right after updating this latest prerelease.

This new version will not start up. It looks like it's starting fine, but then hangs. It won't connect to the data service, even if i manually try to connect, then when i try to exit via File>Exit it just hangs. I have to use task manager to shut it down.
[2017-12-11 23:27:10]
User98657 - Posts: 96
Update: i figured out the hang on exit. The "Save All" dialog box was buried under the open windows. i just had to find it.

But it will not connect, and doesn't appear to be opening all the chartbooks correctly.
[2017-12-11 23:31:01]
User98657 - Posts: 96
Although it appears to open correctly in safe mode, it actually does not.

Even thought it say's it's connected, it will not load any new data.
[2017-12-11 23:52:14]
Sierra Chart Engineering - Posts: 56211
We apologize for this. In an effort to try to see what we could do to work around the issue, we ended up introducing a new issue which did not show up in testing.

We have removed version 1667 because it does have a significant issue with detached charts.

We have now released 1668. When you start Sierra Chart, do not open any existing Chartbooks and update to the latest prerelease which is now 1668.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
Date Time Of Last Edit: 2017-12-11 23:52:25
[2017-12-12 00:01:20]
Sierra Chart Engineering - Posts: 56211
Also we are testing your Chartbook on a Windows 10 system now and there are no exceptions occurring at all.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
[2017-12-12 01:01:42]
User98657 - Posts: 96
Well, that would make sense as not all of the Win10 users are experiencing this issue.

I really don't want to have to strip this machine down and start reloading Windows and everything else unless i absolutely have to.
[2017-12-12 03:07:25]
Sierra Chart Engineering - Posts: 56211
See if you have any problems with 1668. It is possible we may have determined what the problem was and have it resolved. Still the behavior on the part of the operating system is improper, but at least we may have worked around it.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
Date Time Of Last Edit: 2017-12-13 16:09:35
[2017-12-12 14:09:57]
User98657 - Posts: 96
I will let you know, thanks.

There were no errors when i came in this morning, but that's not unusual.
[2017-12-12 14:32:13]
User98657 - Posts: 96
NQH8 [CB] Flex Renko 2-1-1 #18 | Performing a full recalculation because it has been tagged. Chartbook: Daily.cht | 2017-12-12 08:29:10
ESH8 [CBV] Renko 2t #1 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:30:49
ESH8 [CBV] Renko 2t #1 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:30:50
ESH8 [CBV] Renko 2t #1 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:30:50
ESH8 [CBV] Renko 2t #1 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:30:50
ESH8 [CBV] Renko 2t #1 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:30:51
ESH8 [CBV] Renko 2t #1 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:30:51
ESH8 [CBV] Renko 2t #1 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:30:52
ESH8 [CBV] Renko 2t #1 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:30:52
ESH8 [CBV] Renko 2t #1 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:30:53
ESH8 [CBV] Renko 2t #1 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:30:53
ESH8 [CBV] Renko 2t #1 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:30:54
ESH8 [CBV] Renko 2t #1 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:30:54
ESH8 [CBV] Renko 2t #1 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:30:55
ESH8 [CBV] Renko 2t #1 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:30:55
ESH8 [CBV] Renko 2t #1 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:30:56
ESH8 [CBV] Renko 2t #1 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:30:56
ESH8 [CBV] Renko 2t #1 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:30:57
ESH8 [CBV] Renko 2t #1 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:30:57
ESH8 [CBV] Renko 2t #1 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:30:58
ESH8 [CBV] Renko 2t #1 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:30:58
ESH8 [CBV] Renko 2t #1 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:30:59
ESH8 [CBV] Renko 2t #1 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:30:59
ESH8 [CBV] Renko 2t #1 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:00
ESH8 [CBV] Renko 2t #1 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:00
ESH8 [CBV] Renko 2t #1 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:01
ESH8 [CBV] Renko 2t #1 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:01
ESH8 [CBV] Renko 2t #1 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:02
ESH8 [CBV] Renko 2t #1 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:02
ESH8 [CBV] Renko 2t #1 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:03
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:03
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:03
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:04
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:05
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:06
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:06
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:07
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:07
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:08
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:08
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:09
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:09
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:10
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:10
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:11
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:12
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:12
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:13
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:14
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:14
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:15
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:15
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:16
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:16
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:17
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:18
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:19
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:19
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:20
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:20
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:21
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:22
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:23
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:23
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:24
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:25
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:26
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:26
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:27
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:27
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:28
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:29
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:30
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:31
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:31
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:32
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:33
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:33
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:33
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:34
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:35
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:36
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:36
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:37
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:37
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:38
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:38
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:39
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:39
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:40
RTYH8 [CBV] 1 Day #15 | Exception in c_Chart::ChartDraw. Section 4. | 2017-12-12 08:31:40
[2017-12-12 14:39:33]
User98657 - Posts: 96
I am shutting down, choosing "no" on save all, restarting.
[2017-12-12 17:14:52]
Sierra Chart Engineering - Posts: 56211
It should be obvious that repetitive postings are not helping us. One post is sufficient. We are going to delete duplicates.

You should understand that we are extremely busy.

We have narrowed the problem further. Update to prerelease version 1669.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
Date Time Of Last Edit: 2017-12-12 17:16:32
[2017-12-12 17:24:09]
User98657 - Posts: 96
Please do delete anything that doesn't help. It wasn't intended to be anything other than information to perhaps give you more to go on.

I'll only send one going forward.

I know you're busy, that goes without saying. Again, I didn't intend for the additional posts to be an annoyance.

I do appreciate the time you're spending on this.

1669 is installed.
Date Time Of Last Edit: 2017-12-12 17:26:38
[2017-12-13 14:09:45]
User98657 - Posts: 96
No new errors since uploading 1669!
[2017-12-13 14:58:01]
sunnyod - Posts: 66
Same here - update to 1669 has fixed that issue and possibly also the chart windows failing to detach issue i've been seeing. Still early to confirm seconds issue is fixed though
[2017-12-13 16:10:06]
Sierra Chart Engineering - Posts: 56211
That is interesting because nothing changed in 1669 which would have resolved it. We would of thought that 1668 might have solved it.

Did either of you perform a Windows update? Maybe that resolved the problem.

Here is one such problem:
https://support.microsoft.com/en-us/help/4054150/issues-when-windows-10-fall-creators-update-calls-createwindowex-for-s

Microsoft was supposed to have released an update December 12 to resolve it.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
Date Time Of Last Edit: 2017-12-13 16:12:46
[2017-12-13 16:21:26]
User98657 - Posts: 96
No windows update here. i have them turned off for the time being so i can more closely monitor and control the updates.

I did install an update on 12/11, but I continued to have the issue after that update. And... That update was simply reinstalling the 12/3 update I tried to uninstall. I was able to uninstall parts of it, but not all of it. And the roll back did not help the situation so on the 11th i just reinstalled that 12/3 release.

I did just now allow the machine to look for updates and i see the update you're referring to. i will let it install and let you know if anything happens.

In any event, i'm not sure why the errors stopped, but I'm obviously happy they stopped.

Thanks again for continuing to grind on this. i know it was a PITA.
[2017-12-13 18:42:32]
sunnyod - Posts: 66
Yes I installed that 1709 update yesterday.... That could be it for me
[2017-12-13 19:05:04]
Sierra Chart Engineering - Posts: 56211
Will check what we did to see if we inadvertently made some change which can resolve the issue but if not, then this actually does indicate a quite a serious issue in Windows 10 where apparently a memory corruption is occurring and in this particular build of Sierra Chart, it is not causing any problem.

So it is possible that with another release of Sierra Chart you would have the problem.

So this is quite a serious problem that Microsoft does need to resolve.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
[2017-12-13 19:27:06]
User98657 - Posts: 96
I guess we will see.

In any case, thanks for the effort.

Still holding after the new MS update on V 1669.

And I did an inordinate amount of chart drawing yesterday, new charts, in and out of chart books, deleting and redrawing charts, changing periodicities, changing draw types....

i wasn't trying to get it to break, just experimenting with different things and it held solid.
[2017-12-14 08:47:58]
sunnyod - Posts: 66
I am seeing strange slow downs in Sierra sometimes. But it's hard to say what causes them as I've not been taking note of the log. Maybe this is the memory issue. Will note any new occurrences if they happen

Actually come to think of it, it happens when I have my other trading apps open. Specifically FXCM's Trading Station and MT4. If Sierra is open at same time all three become really slow. Shouldn't be an issue on my PC - it's 16 core 32GB ram
Date Time Of Last Edit: 2017-12-14 08:55:40
[2017-12-14 15:25:48]
Sierra Chart Engineering - Posts: 56211
In response to post to #64 this is not in the right thread.

It is unrelated.

However, refer to help topic 30:

Http://www.sierrachart.com/index.php?page=doc/helpdetails30.html

Will note any new occurrences if they happen
We will not pay any attention to this. This will not mean anything to us. We can only refer you to help topic 30.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. If possible please keep your questions brief and to the point. Please be aware of support policy:
https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation

If your question/request has been answered and you do not have anything further, then it is easiest for us if you do not reply again to say thank you.
Date Time Of Last Edit: 2017-12-14 15:26:08

To post a message in this thread, you need to login with your Sierra Chart account:

Login


Login Page - Create Account