Support Board
Date/Time: Fri, 31 Oct 2025 12:11:50 +0000
Windows error code 193:
View Count: 1357
| [2018-11-19 06:03:11] |
| User316362 - Posts: 211 |
|
I've been using this dll for weeks (my dll). I tried recompiling, using different Sierra versions etc. But it just started today, Sunday evening. I see that others have been having this problem also in the past with other DLLs. Any clues? CreateStudyDLLModuleFunctionObject Error loading C:\SierraChart\Data\HamptonTrader.dll. Windows error code 193: %1 is not a valid Win32 application. | 2018-11-19 00:50:10 Date Time Of Last Edit: 2018-11-19 06:05:26
|
| [2018-11-19 06:07:12] |
| |
|
Make sure you are running the 32-bit version of Sierra Chart because it looks like that DLL requires it. Refer to: How to Use an Advanced Custom Study or a Study Collection: Custom Study Not Listed or Not Displaying on 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 |
| [2018-11-19 14:30:15] |
| User316362 - Posts: 211 |
|
I'm sure it's compiled at 32bit and I'm sure I'm running the 32 bit sierra version. I reverified This started without me changing anything. This is a deployed DLL. One thing I did notice is that WIndows 10 pushed an update on 11-17. I'll try some things on my end to see if I can pinpoint it. Date Time Of Last Edit: 2018-11-19 14:40:32
|
| [2018-11-19 14:51:53] |
| User316362 - Posts: 211 |
|
Update.... The DLL is 471 KB in size. I uploaded it and forced an update. The DLL shows up in the Data directory as a 0 bytes size file when deployed could it be the Sierra update/deployment mechanism? Date Time Of Last Edit: 2018-11-19 15:00:29
|
| [2018-11-19 15:27:37] |
| User316362 - Posts: 211 |
|
OK, I deleted everything and removed the file from the update list. I then updated the file again and added the file name back into the DLL name for updating. I forced an update and all is well now. How a zero file size got in the mix I haven't a clue. Resolved. |
To post a message in this thread, you need to log in with your Sierra Chart account: