Also have the same problem since fivem update yesterday. Every time that error shows in the console it stops apartments from working to. Hope this is fixed soon because its causing pretty big problems on populated servers.
how about 20 characters ??
Now, as s many people report same issue I’m sure it’s fivem related (the change they did within the update).
I hope we will at least get the information what was changed and could cause that chain of events so we can try to fix it ourselves.
It’s been 24h since the update, many servers have same issue and I they are just waiting for the update to fix that. There is still no response from staff.
Provide a repro, and maybe you’ll get a ‘staff response’ that has any meaning.
We can’t install every single resource you guys use, so it’s impossible to actually reproduce this issue internally whatsoever.
Since nothing was changed that should cause an issue like this, it’s likely something to do with an obscure resource.
Also, if anyone comes along with ‘just install these 150 ESX resources and it’ll happen’, they’ll promptly be shown the door as we aren’t going to install 150 resources by hand that all have additional setup requirements just to be able to reproduce some obscure issue, so it’s up to you to provide information that can be used to fix the issue. If this happens to be an automated script to set up this ESX suite, or a server dump, or whatever, it doesn’t matter, as long as it can reproducibly show the issue within 15-30 minutes.
As a quick fix, you can remove some JS-based client resources you may happen to be using, such as some ‘custom radio’ resource that seems to be popular in servers that install 500 resources.
Issues added to repos of the resources as well:
All of the JS based resources seems working fine (I have a few)
FIX - Update:
since this morning i’m getting this on esx whenever i try to use a / command how do i fix it? (no using any js script)
Same… getting this error only when trying to use a / command
Fixed reverting latest windows artifact update to an older
I was using the lastest build from septembre 20, 2018 and I’m getting this error…
switched back to the build of september 10, 2018 and I’m still getting the error…
Wich build are you using ?
6 september… be sure not to have radio script running
After a few test, the problem is coming from mysql-async and not any script or fivem build.
Do you still have the new mysql-async version install with all the esx script updated to work with it ?
yeah work like a charm for me… the error for me was the updated server version
I still seem to be getting this issue, what was your solution?
1 Like
i have the same problem after cfxserver update
So, whenever I input a command in chat, I get
Invalid ref call attempt: 3
Reverting to earlier builds won’t solve the problem in long term. Was the problem identified?
I fixed it myself, it has to be one of your esx scripts that are outdated/not compatible.
Just update all your scripts, or disable them to see which one it is.
Have you found a fix at all I’m still looking for a fix for this issue ?
Nothing, except silly rollback to stone age of FiveM artifacts.