I am revisiting an old thread that I can seem to nail down. It's one of the last nagging issues I would like to know how to resolve on the fly.Take for example I do a nice flight. Land. Close FSX. I get a closing error due to FSInn being installed. No way around that issue that I am aware of. Restart FSX and non of my 3rd party apps running remotely via simconnect will connect. The only solution is to reboot computer. Reboot, start FSX and everything is golden.What I want to be able to do is get the simmconnected apps to fire back up even through FSX shuts down incorrectly (again, due to FSInn). I thought I had it licked by shutting down Saitek services, TrackIR services and FSInn but to no avail.Any thoughts as to what services I can shut down to get simconnect working again wihtout a reboot?Benjamin.

BenjaminI could be wrong but your problem is with FSINN and not necessarily simconnect. You may need to post on that forum on how to fix the close down error. Its fairly obvious that restarting after closing FSX down that it will not restart unless you carry out a re-boot means that FSINN is still resident in memory and blocking your re-start. It seems to be a recurring problem! http://forums.vatsim.net/viewtopic.php?t=33548 RegardsPeterH

BenjaminI could be wrong but your problem is with FSINN and not necessarily simconnect. You may need to post on that forum on how to fix the close down error. Its fairly obvious that restarting after closing FSX down that it will not restart unless you carry out a re-boot means that FSINN is still resident in memory and blocking your re-start. It seems to be a recurring problem! http://forums.vatsim.net/viewtopic.php?t=33548 RegardsPeterH

Right, I mean, I didn't think it was simconnect per se but rather something else that was still open causing a block of the port or something when the FSX didn't shut down correctly. You would think there would be a service running that I could shut down from the task manager to simmconnect to pass back through.Since FSInn uses FSUIPC instead of simmconnect, what is causing the simconnect to not function if FSX is shut down incorrectly? I will keep on working on it and will in the meantime try to get FSInn to keep FSX from bombing on closeout. Thanks

Since FSInn uses FSUIPC instead of simmconnect

Does it? I didn't think it did. I thought it used FSCopilot? And in any case FSUIPC uses SimConnect.

what is causing the simconnect to not function if FSX is shut down incorrectly?

I get this too. FSX often crashes on termination in AI Player -- I think this is related to UT2 continuing to feed it with AI updates after I've requested termination. But the SimConnection problems only occur for Networked connections, not local ones -- at least with programs using Sp1 or SP2 SimConnect versions, such as ASX. Those use Pipes instead of TCP/IP ports.Therefore, I suspect the crashing of FSX at the end is ieaving the SimConnect TCP/IP port(s) in such a state that on reload they don't get assigned correctly. I've no idea how to fix that. I re-boot the system.RegardsPete

Pete - thanks for the response. You certainly know a lot more than I when it comes to FSUIPC / SimConnect etc. etc. :)I was just guessing...and assuming. I will try to nail down the FSX shutdown error and see what happen from there - starting with FSInn settings per the VATSIM.net link.Keep it coming!Benjamin.

Geniuses! The fix in the Vatsim Forum (turn off the FSCopilot / Setting / Tuner) and shutting down the FSInn prior to closing FSX did the trick. I no longer error on exiting. I can repeat on command either way. When FSX shuts down correctly, I can zip over to my laptop - presto, what once wasn't working with simconnect now does. Thanks for the help on this issue. I am knocking them out now! Gauge issue on 5040x1050 - check. Crash when loading flight plan .pln files (ended up being DisablePreload=1 + FSInn) and SimConnect issue - check!Benjamin