When I run RC4 in my own account, which is an Administrator account, it seems to work ok for a while but then goes away with error 75 sometime during a flight. Had this problem before and as advised reinstalled outside the Program Files directory. When I choose Run As Administrator the application comes up and I can load a plan but as soon as I click on the Start RC button I receive the message "IPC Request Contains Bad Data".

See the thread regarding Kapersky Anti-virus causing Error 75s pinned at this forum top. It can apply to other protection services. Be sure in all of your protection schemes RC is a trusted application. IPC errors can occur if RC and FS are blocked from each other. Be sure FS is running and a flight loaded before pressing the START in RC,In some operating systems it was found that the path setting in RC did not stick between sessions and had to be set each time RC was loaded. The flight plan loading path you noticed when opening in the explorer type window is independent of the .wx/.flt setting path in the RC path setup.

When I run RC4 in my own account, which is an Administrator account, it seems to work ok for a while but then goes away with error 75 sometime during a flight. Had this problem before and as advised reinstalled outside the Program Files directory. When I choose Run As Administrator the application comes up and I can load a plan but as soon as I click on the Start RC button I receive the message "IPC Request Contains Bad Data".

This solution is taken from the RC FAQ...http://www.jdtllc.com/FAQ.htm#25

I had already reinstalled the latest FSUIPC before posting. FSUIPC is working fine with SerialFP2. It is only RC4 that is having a problem. I have tried running RC4 in a closed environment with no Antivurius or Firewall running and a complete disconnect from the net and get the samme results. I have invested several weeks in trying to cope with this app, whose functionality I find quite good, but whose reliability is not. I think it is time to give up and look for something else.

I had already reinstalled the latest FSUIPC before posting. FSUIPC is working fine with SerialFP2. It is only RC4 that is having a problem. I have tried running RC4 in a closed environment with no Antivurius or Firewall running and a complete disconnect from the net and get the samme results. I have invested several weeks in trying to cope with this app, whose functionality I find quite good, but whose reliability is not. I think it is time to give up and look for something else.

If this was a problem with RC4 then we would be bombarded with messages but we haven't so it's almost certainly something on your system. I'm sorry I can't be more specific but without sitting in front of your machine it's difficult to diagnose the problem. It would be a pity if you stopped using RC4 because of this. Perhaps JD can offer different advice or failing that try Pete Dowson.You didn't say if you had followed the advice in the FAQ to delete certain files. Did you do that?

When I run RC4 in my own account, which is an Administrator account, it seems to work ok for a while but then goes away with error 75 sometime during a flight. Had this problem before and as advised reinstalled outside the Program Files directory. When I choose Run As Administrator the application comes up and I can load a plan but as soon as I click on the Start RC button I receive the message "IPC Request Contains Bad Data".

if you are running windows 7 or vista, you have to run as administrator. in windows 7 or vista, even if your account is a member of the administrator group, you still are not running as administrator.run time error 75 is almost always one of two things. permissions or lack of admin rights, or anti virus programs.what version of fsuipc? are you running widefs?what version of rc?specific version numbers, the latest doesn't help me figure it out.what version of fs?what service packs if any?if fs running when you click start rc button?

Before I did my original post I deleted the FSUIPC4 dll and its config file and reinstalled version 4.60.I am running RC 4.3.3845I am running FSX with SP2 installedMy system is XP with SP3 installedFSX is running when I click on RC start button.

Before I did my original post I deleted the FSUIPC4 dll and its config file and reinstalled version 4.60.I am running RC 4.3.3845I am running FSX with SP2 installedMy system is XP with SP3 installedFSX is running when I click on RC start button.

fsx is running when you click the start rc, but is fsx ready to fly? not the fly now window, or choose a flight menu, or flightplanner window?jd

My procedure is to bring up FSX, load a flight plan, click on fly now, then wait for the scenery load to complete. When the aircraft is located at the gate I start SerialFP2. When that is initalized I then start the Radar Contact app. Next I load the flight plan into RC. When that completes I set the arrival gate, then click on the Start RC button. Always the same procedure whether I run RC from my own account or the Administrator account.

My procedure is to bring up FSX, load a flight plan, click on fly now, then wait for the scenery load to complete. When the aircraft is located at the gate I start SerialFP2. When that is initalized I then start the Radar Contact app. Next I load the flight plan into RC. When that completes I set the arrival gate, then click on the Start RC button. Always the same procedure whether I run RC from my own account or the Administrator account.

you have to run rc, by right mouse clicking the .exe or shortcut, and clicking run as administrator. you don't need to try it one way or the other. it can only be run that way on vista or 7what is serial fp2? if you don't start that, does rc run?to troubleshoot this, we're probably going to have to take one add-on away at a time, to see which one is problematic, and then see if we can fix it, when we find it. we know rc works with fsx.is this a widefs/network configuration? i forget if i asked that or not.also, can you make a log and send it to me? instructions pinned to the top of the forumjd

you have to run rc, by right mouse clicking the .exe or shortcut, and clicking run as administrator. you don't need to try it one way or the other. it can only be run that way on vista or 7what is serial fp2? if you don't start that, does rc run?to troubleshoot this, we're probably going to have to take one add-on away at a time, to see which one is problematic, and then see if we can fix it, when we find it. we know rc works with fsx.is this a widefs/network configuration? i forget if i asked that or not.also, can you make a log and send it to me? instructions pinned to the top of the forumjd

I am running by right mouse clicking the shortcut and clicking on run as administrator. As I stated earlier my system is XP with Service Pack 3 applied. The log that I just sent you is without SerialFP running, only FSX and RC are running when the error occurs. SerialFP is only a driver for VRInsight's MPanel communicating through FSUIPC4 and simply provides a means to better control com, autopilot, and other controls. As I said, the error occurs whether or not SerialFP is running. It is not a widefs/network configuration.

I am running by right mouse clicking the shortcut and clicking on run as administrator. As I stated earlier my system is XP with Service Pack 3 applied.

This is confusing. I also have XP SP3 installed and have never had to right-click any shortcut and choose "run as Administrator". If your account is that of an administrator then there's no need to do this. Just double-click to launch it and you should be fine.

The log that I just sent you is without SerialFP running, only FSX and RC are running when the error occurs. SerialFP is only a driver for VRInsight's MPanel communicating through FSUIPC4 and simply provides a means to better control com, autopilot, and other controls. As I said, the error occurs whether or not SerialFP is running. It is not a widefs/network configuration.

Hopefully the log will pinpoint where the problem lies.

This is confusing. I also have XP SP3 installed and have never had to right-click any shortcut and choose "run as Administrator". If your account is that of an administrator then there's no need to do this. Just double-click to launch it and you should be fine.

I think the confusion arises because of poor Microsoft terminology. There are at least two levels of "Administrator" (two that matter). There's the one you think you are, and there's an "elevated" one. Installers and Setup programs automatically get "elevated" status, but other programs can also run with that privilege level by using the right-click "run as administrator" option.I don't know about XP SP3, but certainly Vista and Windows 7 protect all folders in "Program Files" against normal user changes -- you can read but not write or delete. Same applies to "normal" programs. Elevated privileges get around that.The problem becomes worse for programs written to assume they can write to their own folders, like FS9. If you install FS9 in Program Files (as it does by default), then Windows (at least Vista and 7) sees it is unaware and actually places it in folders which it can write to, but hidden from the user. The folders the user sees are only aliasses -- for reading, not writing or deleting. To see the real folders you have to run Explorer "as administrator".FSX is different. It never writes to its own folders. That's why everything is in one of three other places - My Documents, AppData or ProgramData, depending on whether it's for all or only one user.FSUIPC's installer, being an installer, has elevated privileges. That's why I moved the Registration there (so it can write to the Registry). But it also changes the status of the FS Modules folder to "everyone has read/write access". This is counter to Microsoft dictates but seems to be the only sanitory way out for FSUIPC and other add-in module users.Oh, something important: one other nasty thing happen. If you have FS installed into Program Files and so protected, applications which may been to write to its folders cannot unless run "as administrator". Consequently a lot of application vendors, RC's included, are advising folks to run their applications "as administrator". That then has further connotations, because Windows actively prevents programs at different privilege levls sharing data via memory -- exactly how FSUIPC interfacing works. Therefore, if you have to run your application "as administrator", you also have to run FS "as administrator" if the application uses FSUIPC.Fun, eh?The easiest and best way out is to do the sensible thing. NEVER EVER install anything like FS into "Program Files". Then all this is irrelevant. You and I never have, but most users aren't so savvy! ;-)Best RegardsPete

Great reply Pete. Sounds like Watcher has installed FSX in Program Files. That path becomes so torturous I have never gone with the Microsoft 'suggested' location.So what's the easiest way to overcome this problem?

1. Copy the FSX install to another temporary location.
2. Uninstall FSX.
3. Reinstall FSX (to C:\FSX).
4. Delete the new install and move the original back to the new location?

I suspect a few Registry edits will be required but a search and replace should be okay.

So what's the easiest way to overcome this problem?

1. Copy the FSX install to another temporary location.
2. Uninstall FSX.
3. Reinstall FSX (to C:\FSX).
4. Delete the new install and move the original back to the new location?

I suspect a few Registry edits will be required but a search and replace should be okay.

I would advise against un-installing FSX. Too often it seems to make a pig's ear of the SimConnect setup which then often means a complete Windows re-install, especially on Vista or Win7 for which I've found no way to do SimConnect repairs. SimConnect is a "side-by-side library assembly" and seems to involve so much convolution inside Windows and the registry that it is impossible to untangle, and FSX's uninstaller does a half-baked job. So much so that on the re-install it tries to install SimConnect again and compounds the mess.Best way, in my opinion, is to rename the existing install path (just the "Flight Simulator X" part at then"), using an elevated Explorer (i.e. one "run as administrator"), then install FSX again but explicitly selecting a decent path elsewhere -- on a completely different drive is good, but choose some sensible path like "C:\FSX" or "D:\FSX", etc.This should fix the registry pointers for FSX itself, but not, of course, for any add-ons which use the Registry to locate themselves (FSUIPC is not one which needs a registry change). So it would usually then be a good idea to reinstall add-ons afterwards. They might appear to work, but you might find the next update says you need to install the original first.There is also a registry fixer program which works for FS9 and FSX -- I put a link to it in an Announcement on my Support Forum. It simply corrects the pointers to the folders.Then you could probably delete the original Flight Simulator X folders entirely (again using an elevated Explorer), though I always found it beneficial to have a spare installation in order to recover files from that some fool add-on has messed up! ;-)RegardsPete