Home >> Support Board

Support Board

Date/Time: Thu, 02 May 2024 08:15:53 +0000

How to Post a Message for Support

[Programming Help] - DLL issue ... Windows error code 126

View Count: 657

[2020-02-19 12:13:55] #1 [Go To First Post]
User92573 - Posts: 483
Dear Support Board Can anyone throw some light on the issue I'm experiencing. WIN10 1909 clean install on 2 PC's and both have same issue. Apart from OS, SierraChart64 is the only program. This I copied to C:\ from a backup location. Windows firewall is set to allow SC in both Private and Public Windows defender AV is set to exclude folder C:\SierraChart64 When I try to add a study DLL each study is replaced by the following: CreateStudyDLLModuleFunctionObjectErrorLoading C:\SierraChart64\Data\"filename".dll. Windows error code 126: The specified module could not be found. Likely missing dependency file. All were working previously so the only change is that I no longer have other programs such as Office and Visual Studio 2017 loaded on either PC however I didn't think the compiled DLL's had a dependency? Its not a Sierra Chart issue but any help would be appreciated. Many thanks Note I did add a separate folder "C:\SierraChart32\ACS_Source\sierrachart.h" that can be referenced in the 64 Bit DLL's .cpp (for .h files). Update: I noticed that when compiled via SC versus Visual Studio I obtain two very different DLL sizes! Sierra Chart compile 01.DLL 848kb; Visual Studio 78kb Sierra Chart compile 02.DLL 831kb; Visual Studio 74kb This is clearly relates to the issue as it seems that the Sierra Chart compiler (which works) is creating a type of static DLL that includes the libraries/headers etc thus allowing the DLL, or all of the Sierra folder contents to be moved to any drive/location without it breaking any links. Is this correct because I only ever created dynamic libraries (DLL's). If this is the case how can I compile my DLL's outside of Sierra Charts? I cant see a way using Visual Studio? The Sierra Chart compiler does remove the above issue but it doesn't fully answer why the smaller, linked DLL's now fail. Help from a techie would be gratefully received. Many thanks Date Time Of Last Edit: 2020-02-19 18:01:58

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