What does this mean please?Run-time error '76'RadarContact.fsuipc.rcv4codeI have twice had this error immediately after take-off from EGLL Heathrow (once on runway 9L and one 9R).When I click OK, Radar Contact shuts down.JohnFollow-up note:In anticipation of being asked for a log, I tried the flight for a third time with debugging active.This time, at the very same moment I received a different message:Run-time error '52'Bad file name or numberI have the log file on hand if it is needed.J

Is it happening on other scenery and situations?Tell us about your environment such as Win version, weather add-ons, and other tasks running. All aircraft or specific aircraft. FS9 or FSX.Some malware applications can cause RC access to Win files are denial processes causing interprocess communication errors. See the pinned antivirus topic at the forum head. This is a "time bomb" occurrence. Be sure RC is a trusted application so its frequent communications with FS is not deemed a malware threat.A heavy resource load such as ASE mixed with a heavy FS resource load can cause communication dropouts via FSUIPC. This gives the same effect as pressing the START button in RC without a loaded flight. If you are an AES user try that flight without it. AES causes periodic heavy interprocess communication loads which might cause FSUIPC time-outs. There has been another service pack released for it.When you started Debug it increased the RC resource demand a bit with its heavy disk writing in that situation. Normally RC is not too demanding on resources.Make sure you have at least FSUIPC 3.98 (FS9) or 4.60 (FSX) and that you have rebuilt your scenery data base with makerwys 4.41 or better. Updated revisions to those not in full release are here but should be safe are here:http://forum.simflight.com/topic/66139-updated-modules-19th-october-2010/http://forum.simflight.com/topic/66136-useful-additional-programs-24th-september-2010/For FSUIPC be sure version 3.98 or 4.60 are first installed from here:http://www.schiratti.com/dowson.html

Is it happening on other scenery and situations?

It has never happened before, but I have yet to try any other flights since. I will do so when time permits, it may be some while.

Tell us about your environment such as Win version, weather add-ons, and other tasks running. All aircraft or specific aircraft. FS9 or FSX.

Windows XP, FS9.1, Active Sky v6 (with default clouds), Flight Deck Companion. I was using a Rick Piper Vickers Viscount (which hasn't given any problems elsewhere). I use an add-on scenery for Heathrow, I can't remember for certain whether I have flown departures from there since purchasing RC but have certainly arrived without issues.

Some malware applications can cause RC access to Win files are denial processes causing interprocess communication errors. See the pinned antivirus topic at the forum head. This is a "time bomb" occurrence. Be sure RC is a trusted application so its frequent communications with FS is not deemed a malware threat.

At present I cannot see how to add a Trusted Application in Norton, all I can find is a list of applications that Norton has decided can be trusted. FS is listed by not RC. I will look into this further.

A heavy resource load such as ASE mixed with a heavy FS resource load can cause communication dropouts via FSUIPC. This gives the same effect as pressing the START button in RC without a loaded flight. If you are an AES user try that flight without it. AES causes periodic heavy interprocess communication loads which might cause FSUIPC time-outs. There has been another service pack released for it.

I have my reservations that this could be the cause as it is always just seconds after lift-off despite differing time taxying out and queuing. I do not have AES.

When you started Debug it increased the RC resource demand a bit with its heavy disk writing in that situation. Normally RC is not too demanding on resources.

Behaviour was identical whether logging or not, apart from the differing error message.

Make sure you have at least FSUIPC 3.98 (FS9) or 4.60 (FSX) and that you have rebuilt your scenery data base with makerwys 4.41 or better. Updated revisions to those not in full release are here but should be safe are here:http://forum.simflight.com/topic/66139-updated-modules-19th-october-2010/http://forum.simflight.com/topic/66136-useful-additional-programs-24th-september-2010/For FSUIPC be sure version 3.98 or 4.60 are first installed from here:http://www.schiratti.com/dowson.html

FSUIPC is v3.90; I will update.MakeRwys.exe: v4.43John

I think I may now have resolved this issue; whilst undertaking some tests I attempted to save a position just prior to take-off so that I could return to it. Error 76 popped up again.I have Peter Dowson's autosave.dll installed which saves flights at pre-determined intervals. It would seem that it doesn't start saving flights until the wheels have left the ground, so I conclude the errors I was getting were at its first attempt to save.I did two things:

1. I deleted a large number of old flight plans and saved files which were obsolete (although not short of disc space)
2. I reset the path to the flight plans in Radar Contact (although I could see no reason for it to become incorrect)

In a test situation, the issue appears resolved. I would need to undertake a full flight to be sure, of course.It would appear, then, that Run-time error 76 refers to the inability to write files to the correct place.John

In your security add-on setup make sure RC and FS are trusted applications so they can access the Flight Simulator file folder in your My Documents folder for write access.In AS 6 (65) turn off the option to convert FS9 plans as it adds two extra fields to each waypoint in the plan, a possibility of another problem.

In your security add-on setup make sure RC and FS are trusted applications so they can access the Flight Simulator file folder in your My Documents folder for write access.

I have Norton Internet Security and as I have already said I cannot see a way to added "trusted applications".This question has been asked in http://forum.avsim.net/topic/100174-error-75-radar-contact-and-kapersky-and-norton/ but not answered, it seems. Despite a close study I can see no way to do so - I think NIS decides for itself based on its own judgement.

In AS 6 (65) turn off the option to convert FS9 plans as it adds two extra fields to each waypoint in the plan, a possibility of another problem.

I bought Active Sky as a weather programme, I had no idea it would interfere with my flight plans. Thanks for that tip, I have disabled that option.Aside of that I think the solution was in the path to the flight plan directory, can you or anybody confirm that is what that Error Code meant? That was my initial question and I wonder if there is a list of codes anywhere as it would save a lot of straw-clutching in the future?John

Here's from the pinned thread on what had to be done with norton's Internet Security Suite:-------------------------thanks to "watcher" who delved into norton antivirus, and solved the run time error 75 errors when running nortonI have been busy running various tests to try to sort out what needs to be done on my system to resolve the 75 error. What I have so far found after having run various tests is that several things need to be done when running Norton Internet Security, which includes antivirus and realtime protection. First I had to write specific rules to ensure that the locahost connection was not interfered wih. Then I had to set exclusions from realtime protection. This is sort of like a trust. I found that excluding just the RC executable was not enough. It was only after I excluded both RC directories that I had any success. So far I have managed to complete one flight from EGNT to EGLL without a 75 error. Will do more testing to make sure that it is not a fluke. I suspect that the communications are being stacked in one of these directories, requiring a write into a temporary file or stack located there. Please correct me if I am wrong in this assumption. In the midst of all this the USB hub on which my MPanel is located finally died so that delayed me considerably.JD-------------------------so you are looking to "exclude" programs and folders from one of Norton's modules. In the Norton firewall or whatever RC must have access to local host better entered as 127.0.0.1 for the IP address. FYI that is known as a loopback used for communication of client/server modules run on the same PC. See if there is any reference to this in your Norton logs.

I am very grateful for all your help but with the greatest of respect I do not find those instructions for NIS at all specific and I cannot see any such options open to me in the version I have. I have used NIS for many years and worked my way through many versions and do recall the exclusion feature being present in the past but I don't think it is there now.Anyway, I can now say with certainty that is not the solution to my problem so there is no point in pursuing this further - because it is now solved. I have conducted my originally planned flight from EGLL without any problems . . . whoopee! I am convinced that error message related to the path to the flight plan files but I still do not understand why the setting suddenly failed when I had previously conducted many fault-free flights.I do think it is a great shame there seems to be no source of error code explanations, if there had been this could have saved you (and me) a lot of wasted time exploring other avenues.Kindest regards, and thanks again,John

I am very grateful for all your help but with the greatest of respect I do not find those instructions for NIS at all specific and I cannot see any such options open to me in the version I have. I have used NIS for many years and worked my way through many versions and do recall the exclusion feature being present in the past but I don't think it is there now.Anyway, I can now say with certainty that is not the solution to my problem so there is no point in pursuing this further - because it is now solved. I have conducted my originally planned flight from EGLL without any problems . . . whoopee! I am convinced that error message related to the path to the flight plan files but I still do not understand why the setting suddenly failed when I had previously conducted many fault-free flights.I do think it is a great shame there seems to be no source of error code explanations, if there had been this could have saved you (and me) a lot of wasted time exploring other avenues.Kindest regards, and thanks again,John

76 is almost always caused by antivirus programs turning off permissions allowing rc to write to it's directory after a period of time. every antivirus program has their own unique nomenclature, and different ways of tweaking it. 75 is almost always caused by running rc without starting it as admin on windows 7 and vista.jd

76 is almost always caused by antivirus programs turning off permissions allowing rc to write to it's directory after a period of time. every antivirus program has their own unique nomenclature, and different ways of tweaking it. 75 is almost always caused by running rc without starting it as admin on windows 7 and vista.jd

Thanks.I have heard back from Symantec Support and there is indeed a means of excluding programmes in Norton Internet Security although it is well buried and not well documented. It is their view that NIS will not prevent software writing files or alter permissions. They have also offered/recommended a free upgrade from NIS 2011 to 2012 and have suggested I monitor things there without adding any exceptions at this point in time.Everything in RC continues to work smoothly at the moment, just as it had done prior to this problem arising. Curious . . .John

Thanks for the update, John.