American Airlines Virtual

If you used your old .ini file then the FREP likely went to your old VA. That is the file that tells the program what site to send the file to.

Isaac - I confirmed your FSACARS FREP did indeed go to our AAVirtual VA web-site. You are good to go.

Matteo Lorenzi wrote:Hi
when i click 'send log' this error message appear:'error sending log:database error'.
In Fsacars folder i had a look to the sendingreport html file that report me that:

[phpBB Debug] PHP Notice: in file /home1/aavirtua/public_html/modules/FSACARS/receive_pirep.php on line 362: strpos() [function.strpos]: Empty delimiter
OK

don't know what it means!?
..so i put my frep manually on the website..

Matteo,

I believe you received the error because you left the "Callsign" field blank. See the FSACARS for AAVirtual thread, Use FSACARS for your flight section, item #8:
8. On the Flight Plan tab, most fields are self explanatory. For your FREP to be automatically submitted, the following fields are required:
- Departure Airport (4 letter ICAO airport code)
- Arrival Airport (4 letter ICAO airport code)
- Aircraft Type (Any text will be accepted, but if you use the 3 letter IATA code like the codes used in the timetable, the code will get translated into a verbose aircraft description in your FREP)
- Pilot Number (use only the numbers, do not use AA, AAV, or AAL)
- Callsign (Must match your FREP i.e. "AAL1234" or "CHART")
- If you are flying online, select VATSIM in the "Online" box

Note that the callsign is a required field.

Jim, one thing you can do is look for a .dat file in your FSACars directory in Program Files. If there, it is the remainders of a previous flight not satisfactorily sent. I had a similar issue where FSACars was giving me a "...database error..." every time I attempted to file a completed flight (it was also sending two flights instead of one sometimes).

Look in the Technical forum and you will find the info about older .dat files being left that interfere, and how to eliminate.

Jim,

If you are having problems
The first step is to look at this file in your FSACARS directory: sendlogreport.html
It will tell you what the problem is (bad username/password, too many bad logins, etc.).
If the error message doesn't get you there, let me know what it says and I'll keep helping you.

Mike

You must enter a callsign.

Did I miss something on the aircraft codes? My FREPs don't ever show the correct aircraft. This last one for example, I flew a 757-200 and used the aircraft code B752. When I submitted my FREP it showed B752 instead of the full aircraft type. This used to work but maybe I missed something while I was off in the sandbox.

I would expect that from Jeff Jett, but you Sergio? Really?

Yes, it appears something is broken. I'll look at it over Thanksgiving break.

Michael Blakely wrote:Yes, it appears something is broken. I'll look at it over Thanksgiving break.

Good thing Sergio has confessed to the misdeed. At least I can't be blamed for breaking it this time!

I took a look at my AAV.ini file in FSACars and my passwd is not under my pilot number (which is in the [FSACARS] group) but in the [LOG] group where the URL for AAV is positioned. Also make sure you are using "passwd=xxxxxx" and not using "password=xxxxxx". Both are present in the .INI file.

Joshua,

Theodore's comment is correct. If you are still having trouble, please send my your aav.ini file via email.

Josh,

I think this happens when the FREP getting submitted has no flight number. This happens when you forget to fill in the flight number field in the FSACARS form. This is what's causing the database error. To flush this flight from FSACARS, delete the AAL####.dat file, where #### is your AAV pilot number.

So tried a flight tonight and got FSACARS running.. went to send the file and received this: Any thoughts?

Robert Shepherd wrote: ↑04-30-2021 07:36 PM So tried a flight tonight and got FSACARS running.. went to send the file and received this: Any thoughts?

I got the same error msg. tonight and my FSACARS has been working fine up to this point. Must be something on the receiving end (maybe in the middle of a backup).