Okay, here's my problem(s):1) I have tried to configure ASX to run on the same system as FSX, but whenever I try to apply the weather, I get an error message that says "UnHandled Exception- Value cannot be null". After this, the program does NOT freeze up or anything, but neither does any weather load into FSX. 2) I have followed the instructions on setting up ASX on a client system, with FSX on a server system, and after numerous attempts, and LOTS of rechecking of the .xml .ini and .cfg files, reading over the documentation over and over, I cannot get the two to communicate. I have also done the following in an effort to figure this out: 1-complete FSX reinstall, complete with SP1 and SP2 (FSX runs great!) 2-installed the SDK updates, as directed in ASX networking notes 3- uninstalled and reinstalled ASX several timesI CAN access the required folders and files specified in the ASX networking doc form the client system.I have run the 'AI Traffic' test, and I get a black, dos window with no messages whatsoever on the client, and nothing on the server. THe box closes after about 30 secs.*As I read in another user's post, I cannot figure out how to get SimConnect added to the Window's Firewall exception list...I can get close, but in the end, I cannot find SimConnect listed as a program to allow, unlike on my server system. Lastly, within FSX, what do I need to have the weather settings on: 1-weather themes? 2-Real-world (static)? 3-Real-world (updated)? 4) User-defined?Lots of questions, I know, but trust me, I tried to figure this out on my own. So, thanks for any help with this, and I appreciate it.

Hi,Let's see what we can do!1. Are you running B1160? You should not be getting that error when installed on your main machine running B1160.2. If the AI Traffic utility is not working, then something is still not right on your network. All messages show up on the client machine. Not sure about the firewall. I think you should allow ASX access not SimConnect, but I could be wrong about that.3. When things are working correctly, User Defined is automatically chosen.Please let us know how you are doing on this stuff.Thanks,Jimhttp://www.hifisim.com/banners/hifi-community-sigbanner.jpghttp://www.hifisim.com/

Jim, thank you so much for the reply. 1. Yes, I am running B1160 (It is the only build I have downloaded).2. I have ASX access allowed on my Windows firewall. 3. Thanks for letting me know about the 'User Defined' bit...much appreciated!:)4. Alas, still no ASX effects in FSX, the AI program still not successful, and I still get this "Unhandled exception has occurred in your application etc...."So, I am out of ideas...I have full share access to all the folders and files from the CLIENT machine...I can read and write to them from the CLIENT. Jim, I am at a loss friend...

Hi,Is ASX allowed on both machines firewalls?Jimhttp://www.hifisim.com/banners/hifi-community-sigbanner.jpghttp://www.hifisim.com/

I thought it was, but it was not on the SERVER..oops! Okay, so after allowing ASX on the SERVER firewall, still no luck. Same problems. AI Traffic test no luck, and no ASX effects in FSX...Any other ideas? Thanks again for the help thus far...

Hi,Revisit the files that you need to set up and make sure your settings match to what is in the manual. If the AI program will not connect that means something is not set up right.Jimhttp://www.hifisim.com/banners/hifi-community-sigbanner.jpghttp://www.hifisim.com/

Okay Jim, I shall do that. I have done that before, several times. Maybe I am not understanding exactly how they are suppost to look like. However, why would I get this exact same "Uhandled exception error" even when running ASX on the same system as FSX? Any ideas on that one?

Hi,Is that a pop-up window or an error on the ASX main page?Jimhttp://www.hifisim.com/banners/hifi-community-sigbanner.jpghttp://www.hifisim.com/

It is a pop-up window...sorry I didn't tell you that early...

Hi,That is a .NET error window, so that tells me something is wrong with your .NET2.0 installation. I know, with Vista you don't have a .NET option! What a few users have had to do is reinstall Vista.Thanks,Jimhttp://www.hifisim.com/banners/hifi-community-sigbanner.jpghttp://www.hifisim.com/

Can we be more sure about this? I get this error on two different PC's (SERVER and CLIENT). Also, I just re-installed Vista on the CLIENT PC like three days ago (thanks to a hard drive failure)....I want to be ultra sure that is not due to something else first....

Hi,Generate the entire error and e-mail it to Damian at damianc(at)hifisim.comThat way you will know for sure. Don't do anything with your Vista yet.Thanks,Jimhttp://www.hifisim.com/banners/hifi-community-sigbanner.jpghttp://www.hifisim.com/

Okay, I'll try that...thx.

Have the exact same problem when applying weather after installing SP3 (worked fine pre-SP3). I'm running FSX SP2 on Vista 64. Tried uninstalling ASX w/ SP3 and installing pre-SP3 version but the pop-up error remains. If you have any suggestions, please let me know. The error reads:See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.************** Exception Text **************System.ArgumentNullException: Value cannot be null.Parameter name: Argument 'Array' is Nothing. at Microsoft.VisualBasic.Information.UBound(Array Array, Int32 Rank) at ASX.WeatherConfig_Control.ApplyToSingleStation() at ASX.WeatherConfig_Control.btn_ApplyWeather_Click(Object sender, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.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.1434 (REDBITS.050727-1400) CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll----------------------------------------XEngine Assembly Version: 1.0.0.325 Win32 Version: 1.0.0.325 CodeBase: file:///C:/Program%20Files%20(x86)/HiFi/XEngine/XEngine.exe----------------------------------------Microsoft.VisualBasic Assembly Version: 8.0.0.0 Win32 Version: 8.0.50727.1434 (REDBITS.050727-1400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll----------------------------------------System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll----------------------------------------System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll----------------------------------------System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll----------------------------------------System.Runtime.Remoting Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll----------------------------------------System.Configuration Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll----------------------------------------System.Xml Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll----------------------------------------XEngine_Module_Interface Assembly Version: 1.0.0.221 Win32 Version: 1.0.0.221 CodeBase: file:///C:/Program%20Files%20(x86)/HiFi/XEngine/XEngine_Module_Interface.DLL----------------------------------------XEngine_UI Assembly Version: 0.0.0.235 Win32 Version: 0.0.0.235 CodeBase: file:///C:/Program%20Files%20(x86)/HiFi/XEngine/XEngine_UI.DLL----------------------------------------Utility Assembly Version: 1.0.0.2 Win32 Version: 1.0.0.2 CodeBase: file:///C:/Program%20Files%20(x86)/HiFi/XEngine/Utility.DLL----------------------------------------WorldData Assembly Version: 1.0.0.3 Win32 Version: 1.0.0.3 CodeBase: file:///C:/Program%20Files%20(x86)/HiFi/XEngine/WorldData.DLL----------------------------------------FSInterface Assembly Version: 1.0.0.6 Win32 Version: 1.0.0.6 CodeBase: file:///C:/Program%20Files%20(x86)/HiFi/XEngine/FSInterface.DLL----------------------------------------AvMath Assembly Version: 1.0.0.1 Win32 Version: 1.0.0.1 CodeBase: file:///C:/Program%20Files%20(x86)/HiFi/XEngine/AvMath.DLL----------------------------------------Microsoft.FlightSimulator.SimConnect Assembly Version: 10.0.61242.0 Win32 Version: 10.0.61355.0 (fsx-sp1.20070510-2038) CodeBase: file:///C:/Windows/assembly/GAC_32/Microsoft.FlightSimulator.SimConnect/10.0.61242.0__31bf3856ad364e35/Microsoft.FlightSimulator.SimConnect.dll----------------------------------------ASX Assembly Version: 0.1.0.1056 Win32 Version: 0.1.0.1056 CodeBase: file:///C:/Program%20Files%20(x86)/HiFi/XEngine/Modules/ASX.DLL----------------------------------------HiFiSimControls Assembly Version: 1.1.0.1 Win32 Version: 1.1.0.1 CodeBase: file:///C:/Program%20Files%20(x86)/HiFi/XEngine/HiFiSimControls.DLL----------------------------------------User_FlightPlan Assembly Version: 1.0.0.1 Win32 Version: 1.0.0.1 CodeBase: file:///C:/Program%20Files%20(x86)/HiFi/XEngine/User_FlightPlan.DLL----------------------------------------msvcm80 Assembly Version: 8.0.50727.1434 Win32 Version: 8.00.50727.1434 CodeBase: file:///C:/Windows/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.1434_none_d08b6002442c891f/msvcm80.dll----------------------------------------************** JIT Debugging **************To enable just-in-time (JIT) debugging, the .config file for thisapplication or computer (machine.config) must have thejitDebugging value set in the system.windows.forms section.The application must also be compiled with debuggingenabled.For example:When JIT debugging is enabled, any unhandled exceptionwill be sent to the JIT debugger registered on the computerrather than be handled by this dialog box.

Hi,Please start a new thread. It is too hard to follow multiple users in the same thread.Thanks!Jimhttp://www.hifisim.com/banners/hifi-community-sigbanner.jpghttp://www.hifisim.com/