Home >> Support Board

Support Board

Date/Time: Sun, 28 Apr 2024 04:17:07 +0000

How to Post a Message for Support

error msg

View Count: 3713

[2017-12-05 15:06:19] #1 [Go To First Post]
User98657 - Posts: 304
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] #2 [Go To First Post]
User98657 - Posts: 304
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] #3 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
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. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2017-12-05 18:23:58

[2017-12-05 18:27:15] #4 [Go To First Post]
User98657 - Posts: 304
So for now is the solution to simply exit and restart SC?

[2017-12-05 18:47:39] #5 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
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. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing

[2017-12-07 17:50:37] #6 [Go To First Post]
User98657 - Posts: 304
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] #7 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
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. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2017-12-07 18:39:07

[2017-12-07 19:37:09] #8 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
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. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2017-12-07 19:44:02

[2017-12-07 19:51:27] #9 [Go To First Post]
User98657 - Posts: 304
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] #10 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
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. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing

[2017-12-07 20:05:22] #11 [Go To First Post]
User98657 - Posts: 304
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] #12 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
Also make sure this option is disabled: General Settings Window: Destroy Chart Windows when Hidden (Global Settings >> General Settings >> GUI >> Application GUI) Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing


Private File

[2017-12-07 20:27:17] #13 [Go To First Post]
User98657 - Posts: 304
It is disabled (never has been enabled)

[2017-12-07 20:40:27] #14 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
We see you are also using this: TradeControl.dll Restart Sierra Chart in safe mode: Sierra Chart - Software Login Instructions: Using Safe Mode See if that resolves the problem. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing

[2017-12-07 21:10:52] #15 [Go To First Post]
User98657 - Posts: 304
Charts are running in Safe Mode now. i will let you know what happens.

[2017-12-08 16:43:33] #16 [Go To First Post]
User98657 - Posts: 304
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] #17 [Go To First Post]
User98657 - Posts: 304
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] #18 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
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. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing

[2017-12-08 18:40:35] #19 [Go To First Post]
User98657 - Posts: 304
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] #20 [Go To First Post]
User98657 - Posts: 304
Would it help to log onto my machine while the error is in play?

[2017-12-08 22:00:55] #22 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
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. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2017-12-08 22:02:17

[2017-12-08 22:01:55] #23 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
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. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing

[2017-12-08 22:20:25] #24 [Go To First Post]
User98657 - Posts: 304
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] #25 [Go To First Post]
User98657 - Posts: 304
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

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