American Airlines Virtual

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).

Our web host upgraded some software tonight. That cause some applications to break. I'm in the middle of fixing them now.

OK, I just did a test and was able to submit an FSACARS log. You should be able to run your FSACARS and hit "submit log" to send in the log from your prior flight.

NOTE: FSACARS stores two sets of data, one when you run normally, and a different data set when you "run as administrator". So make sure you run it the same way you did for the flight you recorded.

Thanks! Got it sent!

Thanks for the quick response Mike.

So, flew my last flight in my bid last Friday (15th), and received the same database error that I got in my earlier post here on Friday April 30th. Is there something up with FSACARS again? I also changed my password (I thought it about time since I've had the same one for here, since, well, longer than I can remember, lol.. ). But I also changed it in the AAL.ini as well, so that should be good, UNLESS there are some special characters that are not recognized in FSACARS.

Just tried resending my log offline (not at airport) and it gave me that 'Database Error' again. FYI.

Thanks!
Robert

Robert Shepherd wrote: ↑10-21-2021 08:48 AM So, flew my last flight in my bid last Friday (15th), and received the same database error that I got in my earlier post here on Friday April 30th. Is there something up with FSACARS again? I also changed my password (I thought it about time since I've had the same one for here, since, well, longer than I can remember, lol.. ). But I also changed it in the AAL.ini as well, so that should be good, UNLESS there are some special characters that are not recognized in FSACARS.

Just tried resending my log offline (not at airport) and it gave me that 'Database Error' again. FYI.

Thanks!
Robert

Robert,

I have an idea what is going on, and I need a couple pieces of information.
1. Are you running FSACARS with user privileges (left click), or are you running with administrator privileges (right click, run as administrator)?
2. Are there two AAL.ini files on your computer in these two locations?
- FSACARS directory
- C:\Users\your_user_name\AppData\Local\VirtualStore\Program Files (x86)\FSacars directory

Thank you for the reply Mike..!

I run FSACARS solely from a saved directory/folder that I copy back onto my PC whenever I "redo" it. It has always worked before... I did verify the only AAL.ini file I have is in that directory (there is not one in a C:\Users\your_user_name\AppData\Local\VirtualStore\Program Files (x86)\FSacars directory).

I will add though that I may not have run FSACARS 'As Administrator' when I started it for this flight - and that I DO have my P3D shortcut set to 'Run as Administrator' to prevent any add-on issues. I did just try to run it 'As Admin' in "Send Only" mode to see if it would send the log, but I still got the Database Error. Could it be that possibly not running FSACARS in Admin mode during my flight is hosing me up now? If so should I just send over the log file to be entered in my FREP's? ... I have since set my FSACARS shortcut to 'Run as Admin' so hopefully this won't happen again.

As I mentioned earlier, the only other thing that changed since I ran FSACARS this time, was that I changed my AAV password to a complex password that includes a hashmark (#). I know some older software may not recognize this character. Or would I have just received a "Bad Password" error if this was the case?

Also in the sendlogreport.html file I see this:

"Bad Request
Your browser sent a request that this server could not understand.

Additionally, a 400 Bad Requesterror was encountered while trying to use an ErrorDocument to handle the request."

Thanks!

Well, that was it apparently. I changed my password just now, eliminating the #'s that were in there and my log sent! Guess I should've just tried that from the get-go . So FSACARS doesn't like the # symbol at least. It may be that other special characters will work ok though. (I've seen that selectivity as well in some programs).