Jump to content
The simFlight Network Forums
Sign in to follow this  
diceflo

some problems that keep happening

Recommended Posts

I have recently been getting these messages,sometimes in flight, sometimes, landing and just sometimes. Can you tell me what I should do?

************** Exception Text **************

System.Data.SyntaxErrorException: Syntax error: Missing operand after 'Air' operator.

at System.Data.ExpressionParser.Parse()

at System.Data.DataExpression..ctor(DataTable table, String expression, Type type)

at System.Data.Select..ctor(DataTable table, String filterExpression, String sort, DataViewRowState recordStates)

at System.Data.DataTable.Select(String filterExpression)

at Traffic_Board.TrafficBoard.SearchForDuplicateCandidates(String atcAirline, String departureICAO, String arrivalICAO, String aircraftReg, String aircraftTitle) in C:\Documents and Settings\Administrator\My Documents\FSX Traffic Board\SuperTrafficBoard Client V2.2 RC1a\Traffic Board\TrafficBoard.cs:line 2625

at Traffic_Board.TrafficBoard.FSNewFlightCreated(UInt32 fsObjectID, AI_FIXED_DATA_GROUP aiData) in C:\Documents and Settings\Administrator\My Documents\FSX Traffic Board\SuperTrafficBoard Client V2.2 RC1a\Traffic Board\TrafficBoard.cs:line 2710

at Traffic_Board.TrafficBoard.FSAircraftList(UInt32 entry, UInt32 totalEntries, UInt32 fsObjectID, AI_FIXED_DATA_GROUP aiData) in C:\Documents and Settings\Administrator\My Documents\FSX Traffic Board\SuperTrafficBoard Client V2.2 RC1a\Traffic Board\TrafficBoard.cs:line 2155

at SimConnect_Wrapper.SimConnectWrapper10SP2.SimConnect_OnRecvSimobjectDataBytype(SimConnect sender, SIMCONNECT_RECV_SIMOBJECT_DATA_BYTYPE data) in C:\Documents and Settings\Administrator\My Documents\FSX Traffic Board\SuperTrafficBoard Client V2.2 RC1a\SimConnect Wrapper 10 SP2\SimConnectWrapper10SP2.cs:line 1179

at Microsoft.FlightSimulator.SimConnect.SimConnect.raise_OnRecvSimobjectDataBytype(SimConnect value0, SIMCONNECT_RECV_SIMOBJECT_DATA_BYTYPE value1)

at Microsoft.FlightSimulator.SimConnect.SimConnect.OnReceiveMessage(SIMCONNECT_RECV pData, UInt32 cbData)

at Microsoft.FlightSimulator.SimConnect.CSignalProcDelegateMarshaler.CallSignalProc(SIMCONNECT_RECV* pData, UInt32 cbData, Void* pContext)

at SimConnect_CallDispatch(Void* , IntPtr , Void* )

at Microsoft.FlightSimulator.SimConnect.SimConnect.ReceiveDispatch(SignalProcDelegate pfcnSignal)

at Microsoft.FlightSimulator.SimConnect.SimConnect.ReceiveMessage()

at SimConnect_Wrapper.SimConnectWrapper10SP2.DefWndProc(Message& m) in C:\Documents and Settings\Administrator\My Documents\FSX Traffic Board\SuperTrafficBoard Client V2.2 RC1a\SimConnect Wrapper 10 SP2\SimConnectWrapper10SP2.cs:line 60

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.ScrollableControl.WndProc(Message& m)

at System.Windows.Forms.ContainerControl.WndProc(Message& m)

at System.Windows.Forms.Form.WndProc(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************

mscorlib

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)

CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

----------------------------------------

TrafficBoardFrontEnd

Assembly Version: 2.1.1.0

Win32 Version: 2.1.1.0

CodeBase: file:///C:/Program%20Files%20(x86)/FlyingWSimulation/SuperTrafficBoard/TrafficBoardFrontEnd.exe

----------------------------------------

System.Windows.Forms

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

----------------------------------------

System

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

System.Drawing

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

----------------------------------------

TrafficBoard

Assembly Version: 2.2.1.3

Win32 Version: 2.2.1.3

CodeBase: file:///C:/Program%20Files%20(x86)/FlyingWSimulation/SuperTrafficBoard/TrafficBoard.DLL

----------------------------------------

SimConnect Wrapper 10 SP2

Assembly Version: 2.1.0.1

Win32 Version: 2.1.0.1

CodeBase: file:///C:/Program%20Files%20(x86)/FlyingWSimulation/SuperTrafficBoard/SimConnect%20Wrapper%2010%20SP2.DLL

----------------------------------------

System.Data

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)

CodeBase: file:///C:/Windows/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll

----------------------------------------

System.Xml

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll

----------------------------------------

System.Configuration

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

----------------------------------------

Microsoft.FlightSimulator.SimConnect

Assembly Version: 10.0.61259.0

Win32 Version: 10.0.61637.0 (FSX-Xpack.20070926-1421)

CodeBase: file:///C:/Windows/assembly/GAC_32/Microsoft.FlightSimulator.SimConnect/10.0.61259.0__31bf3856ad364e35/Microsoft.FlightSimulator.SimConnect.dll

----------------------------------------

msvcm80

Assembly Version: 8.0.50727.4927

Win32 Version: 8.00.50727.4927

CodeBase: file:///C:/Windows/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4927_none_d08a205e442db5b5/msvcm80.dll

----------------------------------------

System.Deployment

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Deployment/2.0.0.0__b03f5f7f11d50a3a/System.Deployment.dll

----------------------------------------

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

For example:

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

and:

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************

System.Runtime.InteropServices.COMException (0xC000014B): Exception from HRESULT: 0xC000014B

at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)

at Microsoft.FlightSimulator.SimConnect.SimConnect.ReceiveDispatch(SignalProcDelegate pfcnSignal)

at Microsoft.FlightSimulator.SimConnect.SimConnect.ReceiveMessage()

at SimConnect_Wrapper.SimConnectWrapper10SP2.DefWndProc(Message& m) in C:\Documents and Settings\Administrator\My Documents\FSX Traffic Board\SuperTrafficBoard Client V2.2 RC1a\SimConnect Wrapper 10 SP2\SimConnectWrapper10SP2.cs:line 60

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.ScrollableControl.WndProc(Message& m)

at System.Windows.Forms.ContainerControl.WndProc(Message& m)

at System.Windows.Forms.Form.WndProc(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************

mscorlib

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)

CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

----------------------------------------

TrafficBoardFrontEnd

Assembly Version: 2.1.1.0

Win32 Version: 2.1.1.0

CodeBase: file:///C:/Program%20Files%20(x86)/FlyingWSimulation/SuperTrafficBoard/TrafficBoardFrontEnd.exe

----------------------------------------

System.Windows.Forms

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

----------------------------------------

System

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

System.Drawing

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

----------------------------------------

TrafficBoard

Assembly Version: 2.2.1.3

Win32 Version: 2.2.1.3

CodeBase: file:///C:/Program%20Files%20(x86)/FlyingWSimulation/SuperTrafficBoard/TrafficBoard.DLL

----------------------------------------

SimConnect Wrapper 10 SP2

Assembly Version: 2.1.0.1

Win32 Version: 2.1.0.1

CodeBase: file:///C:/Program%20Files%20(x86)/FlyingWSimulation/SuperTrafficBoard/SimConnect%20Wrapper%2010%20SP2.DLL

----------------------------------------

System.Data

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)

CodeBase: file:///C:/Windows/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll

----------------------------------------

System.Xml

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll

----------------------------------------

System.Configuration

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

----------------------------------------

Microsoft.FlightSimulator.SimConnect

Assembly Version: 10.0.61259.0

Win32 Version: 10.0.61637.0 (FSX-Xpack.20070926-1421)

CodeBase: file:///C:/Windows/assembly/GAC_32/Microsoft.FlightSimulator.SimConnect/10.0.61259.0__31bf3856ad364e35/Microsoft.FlightSimulator.SimConnect.dll

----------------------------------------

msvcm80

Assembly Version: 8.0.50727.4927

Win32 Version: 8.00.50727.4927

CodeBase: file:///C:/Windows/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4927_none_d08a205e442db5b5/msvcm80.dll

----------------------------------------

System.Deployment

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Deployment/2.0.0.0__b03f5f7f11d50a3a/System.Deployment.dll

----------------------------------------

FSRadio

Assembly Version: 1.0.0.0

Win32 Version: 1.0.0.0

CodeBase: file:///C:/Program%20Files%20(x86)/FlyingWSimulation/SuperTrafficBoard/FSRadio.DLL

----------------------------------------

Accessibility

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll

----------------------------------------

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

For example:

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

Share this post


Link to post
Share on other sites

This is a familar problem. Some AI packages have a single quote in the callsign, WOAI and TrafficX if I remember correctly. Should be fixed in the more recent patch levels. What version of STB are you on?

Simon

Share this post


Link to post
Share on other sites

Hi, I am using The latest STB (2.2)and I use World Of Ai and Traffic X. I wonder if it has something to do with add on airports. Do I also have to add in payware airports into STB or does it do it automatically. Thanks you for your help.

Share this post


Link to post
Share on other sites

I'm pretty sure it's a callsign, STB does not worry about airports definitions. I think the call sign was "Hex'Air".

First thing, please check your version on the Statistics Tab in the settings notebook. Then we know for sure you have the latest, please report back. After that, we'll need a trace.

Simon

Share this post


Link to post
Share on other sites

HI, I don't see anything new but like you said , it's good to be up to date. One thing that I noticed, is that a lot of my planes don't make it to their destination, sometimes they crash on arrival, sometimes in mid-air. Maybe there is too much traffic, I usually fly from big airport to big airport. Is this a known problem and also is there a way to start from where the plane crashed. If I am flying from Boston to Los Angeles and the plane crashes around Denver. I get sent back to Boston, it would be nice if I could just start from where I crashed (Denver) Just a suggestion, I really appreciate all the help.

Share this post


Link to post
Share on other sites

1) I'll need a trace for the original problem you reported: System.Data.SyntaxErrorException: Syntax error: Missing operand after 'Air' operator.

Details are in the user guide.

2) When you say crash, what do you mean? AI or user aircraft? AI crash into the ground? FSX crashes?

Share this post


Link to post
Share on other sites

When I use shadow ai and I am following a plane in locked spot view using airound. I want to follow it from airport to airport and sometimes they crash as in disappear and then I am sent back to the departing airport no matter where the ai plane disappears. Also what do you mean that you need a trace from the first problem. Do I need to send something to you?

Share this post


Link to post
Share on other sites

The follow/shadow ai has a job to do. We need to keep the AI alive so FSX thinks it is always inside the reality bubble. If your AI is just disappearing, FSX has deleted it for some reason. Traces will help me understand what is happening, and whether there is anything I can do about it.

This is also true for the problem with Hex'Air.

Please see page 80 of the user guide for instructions on running the trace. Then reproduce each problem you are seeing and send me a trace each time. In the case of Follow AI, send the details of the aircraft you are following that crashes (tail number, flight number, origin airport, destination airport, etc), as much as possible so I can find it in the trace.

Simon

Share this post


Link to post
Share on other sites

Ok, I'll look into that. By the way, what is the problem with hex air, I recompiled traffic x to not have that plane just in case it was a big problem.

Share this post


Link to post
Share on other sites

I think I have solved the problem of disapearing planes. I am using the flying w plane as my user plane and then following another flight in STB. When I accidentaly clicked the "S" key, I noticed that my user plane flying w was moving (flying). I put on the parking brakes and so far I have made a few complete flights. In FSX, the planes don't start out parked like in FS2004.

Now, the problem that keeps popping up is the HRESULT: 0xC000014B code. It sometimes shuts down the whole game. Is that code even from STB or some other addon? I hope it's not a FSX thing because I don't want to reinstall and go through all that.

Thanks,

CJ

Share this post


Link to post
Share on other sites

That's from the operating system, saying the pipe used to communicate between FSX and STB is broken. Does a reboot fix that? Also, you can disable the pipe and use TCP/IP instead. A little slower, but you probably won't notice. To do so, locate your STB install folder and create the file "IGNORE_SP2.cfg" in their. Contents do not matter, the file just has to exist.

Simon

Share this post


Link to post
Share on other sites

Well I tried putting that file in but I think I did something wrong. I feel stupid, but how do I make a file? What I did was just type IGNORE_SP2.cfg in word pad and put it in the installation folder. I'm pretty sure that I what I was supposed to do but now I am not sure because I keep getting the error again. Do I have to do something in the STB settings? Also when I select a plane to follow and I click on the flight details it never shows the next flight for that plane. Is it because I am using trafficX and World Of Ai?. Don't get me wrong, I love the program but even with the manual I still keep finding questions that come up.

Thank you

Share this post


Link to post
Share on other sites

Open Notepad and you will have a new document. Do not type anything in the new document, leave it blank. Under the File tab on the top left click "Save As" then just save it as IGNORE_SP2.cfg and save it some place where you can find it.

After you do that open Windows Explorer, go find you file you just saved and then move it to the place Simon told you to put it.

Rod

Share this post


Link to post
Share on other sites

What Rod said!

I'm glad you are asking questions rather than just putting up with things, and I do try to build on experiences in new versions.

About the next schedule, that only comes in to play when an aircraft has arrived and parked and FSX tells me what the next schedule is. In V3, you will get the previous and next schedule available at all times as we can second guess FSX by directly reading traffic BGLs.

Simon

Share this post


Link to post
Share on other sites

Now I get this message, I thought all would be fixed with 2.3 but it is not, what can I do because I am not able to use stb but so far I use only Airound.

post-36873-128689718229_thumb.png

Share this post


Link to post
Share on other sites

Sorry, the code 14B is outside of my control. It's coming from the .net framework and SimConnect. STB V2.3 has no changes in this area. I suggested the workaround of IGNORE_SP2, did that make a difference?

Share this post


Link to post
Share on other sites

No it didn't work for me or maybe I did it wrong. I am using the the latest version. Do I need to put that in again or does it know from before. Does the code mean that something else is interfering with stb. I have rex, gex, and utx and I would hope they all play together but it seems like they don't. With all those error messages, it's confusing to know what the problem is, but you say that it is a code 14b. is there another code that I should look for in the error message. I just want to be able to read through all the technical stuff and find out what the culprit is. I will check google for code 14b.

Share this post


Link to post
Share on other sites

The interesting thing is that your stack trace indicates that the error occurred when STB was being closed. Further, it was performing a return to base function. Please describe exactly the scenario in which this error occurs.

Unzip the attached file and put the IGNORE_SP2.cfg file in your STB Installation folder. After doing so, start STB, click Settings and then the Statistics tab. Tell me what it says there.

IGNORE_SP2.zip

Share this post


Link to post
Share on other sites

Well, I was flying from berlin to hamburg using rex weather and I got the message and then a shutdown. It tells me an error occured with a progream and the message mentions stb but says nothing about rex so i assume my main problem is something with stb. Here a screenshot after the ignoresp2 file was placed in the stb folder. I don't have ut2 but this problem happened before the new stb version 2.3. Here is the stats page and this is the error message I got 5 minutes after starting with the new file, what did I do wrong this time?

post-36873-128689718408_thumb.png

post-36873-128689718489_thumb.png

Share this post


Link to post
Share on other sites

So you are successful at using SimConnect SP1. Here's what microsoft has to say about your errors.

0xC000013C STATUS_REMOTE_DISCONNECT

{Virtual Circuit Closed} The network transport on a remote computer has closed a network connection. There may or may not be I/O requests outstanding.

0xC000014B STATUS_PIPE_BROKEN

The pipe operation has failed because the other end of the pipe has been closed.

In your case, the remote computer is the same computer as the TCP communications simply "loopback". The common theme here is that the other end of the connection is the problem, in other words the SimConnect server built into FSX. I can't do anything to fix FSX, all I can do is to try to find a way to work around the issue you are seeing. Maybe you would see it in REX too, but as far as I know STB is constantly driving SimConnect while REX only does it once in a while.

When the error is experienced, what do you do to recover. Keep your flight running, can you restart STB and connect back in straight away? Granted it may fail again a little later, but does it work again for a while?

My thinking is this may be a transient error on the server if we are lucky, and maybe retrying the call will work OK. If it is, that's a huge change for me to perform so we must be sure.

Regards

Simon

Share this post


Link to post
Share on other sites

When the error comes up, it just crashes fsx and the stb icon in the desktop tray dissapears. The first error message that comes up mentions the hres something or other. If I click continue another message comes up so then I have to hit quit and then restart fsx from the beginning, restart rex and restart stb like I had just turned on the computer. What does it mean about the remote computer because I am only using one computer. Have you heard of this problem before?

Share this post


Link to post
Share on other sites

Please describe how FSX crashes, that is very important to this scenario. I have seen this error before, sometimes when FSX quits normally at the request of the user and always when FSX itself crashes. For me, FSX does not crash very often unless I am pushing the edge with an overclock.

When FSX crashes, all SimConnect clients get an exception like the one you are seeing. It's not STB that is crashing FSX, but the other way around. I could put a nice pretty message around it and not crash STB, but it would not change the underlying cause in FSX.

Simon

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.