Invalid Ref Call Attempt

[deviljin112]

Hello,

After the update, for some strange reason any admin command i use (i.e /car or /tpwaypoint etc) does not work and in console i get

Invalid ref call attempt: 13

The number changes based on the command used...

Any ideas?

[Bazookan]

I have this exact same issue aswell. After the 3.0.1 update! I’ve tried stopping esx_status, esx_property and esx_basicneeds. I even did a clean new server and downloaded everything from scratch...Nothing works. So it got to do with the new mysql-async update.

[deviljin112]

So i found 2 fixes... (either is bad)

1. If you restart esx_status the errors stop -> breaks esx_status (in my case it didnt work anyway after update)
2. Turn off all scripts that have their client coding in .js (not in html folder or nui) -> for some reason esx_status works but acts strange and sometimes breaks

Thats all i concluded so far...

[ghost]

Might be fixed by 3.0.2, if this was caused by 3.0.1. There were some unsafe changes in the MySQL.lua

If it still persists it might be something else.

[deviljin112]

Sooooo also found out recently update 3.0.1 breaks multi query, so that means stuff like gcphone stops working because it requires two queries running simultaneously, async exceeds my programming knowledge and skills so I'm literally waiting and hoping the author knows how to solve all these issues or has tips on how to do it

Edit: I've managed to turn off all client.js scripts that kept breaking esx_status with new FiveM server update :) so my esx_status is running fine now, however gcphone is now not working due to async... So yeah...

Edit2: all my invalid ref attempt disappeared after turning off the client.js scripts... I hope that helps others with similar issues

Edit3: also updating to newest server artifact fixed the admin commands not working... I feel like the async and new server update broke something each and now it's a matter of figuring out which is which

[ghost]

Did you use 3.0.2? Which should fix the issue with the phone.

It originally did not allow multiple statements per query.

[deviljin112]

Oh no i havent i actually totally missed you've updated it 2hrs ago hahaha I will check it out tomorrow currently unable to access my computer I will update you when I check it out thanks

[GrapsZ]

3.0.2 doesn't fix the issue with the phone dude :/

[ghost]

Which connection string are you using?

Make sure to use the mysql-async 2.x compatible one.

[CruelAlpha]

This issue does nto seem to be fixed yet

[ghost]

Invalid ref calls are not because of this resource. See https://github.com/brouznouf/fivem-mysql-async/issues/41#issuecomment-425654258

3.0.0 should have broken already the stuff that is reported. No proper reply on whether multiple statements work.

Closed this issue for the sake of cleaning up.

[deviljin112]

Just for the sake of the argument and for those looking for a fix...

Async DOES NOT cause invalid ref attempt... That was caused by newest fivem server update that caused issues with client.js scripts... The only thing that async has broken (that is now apparently fixed - I haven't tested that myself) is multistatement dB entries which were required by scripts such as gcphone... Therefore, async caused errors with gcphone and multistatement... And fivem server artifact caused admin commands breaking and invalid statement so don't expect the author to fix what this script has not broken and allow him to continue his great work on async...

Thank you

[ghost]

yes. And the title is about the ref calls. so it was closed, as I am not fond to have an open issue about another open issue, that might not be open at all.

https://github.com/citizenfx/fivem/commit/b250df1cf1859e21d8a2078b23ade14e098a6ebd