See the later sections of this thread for FSACARS problem solving. viewtopic.php?t=15538
FSACARS problem solving The first step is to look at this file in your FSACARS directory: sendlogreport.html
NOTE: Your FSACARS directory could be:
1. Your install directory
2. C:\Program Files (x86)\FSacars
3. C:\Users\your_user_name\AppData\Local\VirtualStore\Program Files (x86)\FSacars
Check all 3.
The sendlogreport.html file 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.
If you are experiencing "Database Corruption" or "Tampered Log" errors, go to your FSACARS directory(ies) and delete these files:
Any file with an airport code in the file name (i.e. KLAX)
fsacars.mdb
fsacarslog.*
AALxxxx.dat (where xxx is your pilot number)
[edit]added 12/28/2020
windows 10 causes FSACARS to sometimes put files in your FSACARS directory, and sometimes it puts them in this other directory:
C:\Users\your_user_name\AppData\Local\VirtualStore\Program Files (x86)\FSacars
So, if your .ini file changes or corrupt file deletion attempts are not working, go look in this new directory and look for the files there.
First question, when is this happening? Installation? Launch? Sending the report? Maybe use this thread and let me know what section and step # this occurs.
I see in the pic you provided it shows your pilot number as AVxxxx. Check your AAL.INI config file. Your pilot number in that fill should only be the numeric digits of your pilot number. It should not have AAVxxx.
Theodore Martin wrote: ↑02-05-2023 01:22 AM
I see in the pic you provided it shows your pilot number as AVxxxx. Check your AAL.INI config file. Your pilot number in that fill should only be the numeric digits of your pilot number. It should not have AAVxxx.
That's a thread from last year that Anthony added on to instead of starting a new thread.
Theodore Martin wrote: ↑02-05-2023 01:22 AM
I see in the pic you provided it shows your pilot number as AVxxxx. Check your AAL.INI config file. Your pilot number in that fill should only be the numeric digits of your pilot number. It should not have AAVxxx.
That's a thread from last year that Anthony added on to instead of starting a new thread.
Good catch Mike. I was rushing and I guess these older eyes missed that detail. That's why we have you.