I can’t get past the very first socket initiator failure. I’m programming with Microsoft Studio’s Visual C++ in the Windows environment to produce a Windows program that is equivalent to the example program supplied by quickfixengine’s tradeclient program for initiating a buy side session. I tried the example versions of tradeclient and executor in two MS Windows command windows and saw that they communicated properly with heartbeat transmissions and responses to the tradeclient order selections on my local computer. I’m trying to do the same with my Windows client program, but I can’t get past the FIX::SocketInitiator initiator( theApp, storeFactory, settings ); command that is followed by the initiator.start(); command. In debug mode, after one single step past the SocketInitiator command I get the following four exception messages in my Visual C++ compiler’s output window:

First-chance exception in FixBuy.exe (KERNEL32.DLL): 0xE06D7363: Microsoft C++ Exception.

First-chance exception in FixBuy.exe (KERNEL32.DLL): 0xE06D7363: Microsoft C++ Exception.

First-chance exception in FixBuy.exe (KERNEL32.DLL): 0xE06D7363: Microsoft C++ Exception.

First-chance exception in FixBuy.exe (KERNEL32.DLL): 0xE06D7363: Microsoft C++ Exception.

 

Upon return from this routine I get the message:

First-chance exception in FixBuy.exe: 0xC0000005: Access Violation.

 

I single stepped into the FIX::SocketIiniator () function only to end up in an assembly code section deep within the bowels of the Microsoft and/or QuickFix library code. Any time one gets in that deep looking for an obscure exception, the problem is probably one that can be solved right away only by an expert quickfix developer who knows from personal experience that the cause is a certain library file or external dependency that is missing. If any one of you out there has a clue please let me know. Thank you…