FSACARS ISSUE

[Wayne Pierce]

John, This error message will always show up as a result of some entry on the AAV.ini file not set up correctly. I have had this myself and had to redo the .ini file and found I made a mistake. Either a password, user name and No. was incorrectly entered or your data file location. I will have to say this, please recheck your entries to the AAV.ini file ,for you, against the instructions on setting up FACARS.
Here is a post about setting up the FSACARS.
http://aavirtual.com/forum/viewtopic.php?f=32&t=15538

If you still have problems your .ini file needs to be looked at. Don't post it here as your password will be shown on the web.
WLP

[Norberto Rivera]

It may also have to do with the flight number you are entering. This was a recent fix. Make sure that if your bid says AAXXXX you use that prefix instead of AALXXXX.

[Michael Blakely]

It may also have to do with the flight number you are entering. This was a recent fix. Make sure that if your bid says AAXXXX you use that prefix instead of AALXXXX.

Bert,

That's not quite right. The change I made compares your FSACARS callsign with your bid, and if the AA/AAL don't match, it automatically fixes the callsign in the FREP to match the bid. This way you can put AA or AAL in FSACARS.

[Michael Blakely]

John,

If you can't figure out the problem, email your aav.ini file to me at michaelblakely at aavirtual.com

[Norberto Rivera]

It may also have to do with the flight number you are entering. This was a recent fix. Make sure that if your bid says AAXXXX you use that prefix instead of AALXXXX.

Bert,

That's not quite right. The change I made compares your FSACARS callsign with your bid, and if the AA/AAL don't match, it automatically fixes the callsign in the FREP to match the bid. This way you can put AA or AAL in FSACARS.

I stand corrected.

[Barry Theodore]

I believe you can also look in the following file: "sendlogreport.html" which is in the FSacars root directory along with "AAL.ini" file. The log report should indicate "OKOKOK" if report was sent correctly, if there is an error that will be reported in this file.

Hope this helps.

[Michael Blakely]

I believe John was receiving an error because he 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.