Esx_addonaccount error


why can i always get error with esx_addonaccount, can one help me?

me error same :sweat_smile:

realy? and no one can help us everywhere has tried discord and no one writes anything

same error here.

Connecting: lord0o
Sending heartbeat to live-internal.fivem.net:30110
Sending player (1) ELS data
Error running system event handling function for resource esx_addonaccount: citizen:/scripting/lua/scheduler.lua:41: Failed to execute thread: @esx_addonaccount/server/main.lua:71: attempt to index a nil value (local 'xPlayer')
stack traceback:
        @esx_addonaccount/server/main.lua:71: in upvalue 'handler'
        citizen:/scripting/lua/scheduler.lua:219: in function <citizen:/scripting/lua/scheduler.lua:218>
stack traceback:
        [C]: in function 'error'
        citizen:/scripting/lua/scheduler.lua:41: in field 'CreateThreadNow'
        citizen:/scripting/lua/scheduler.lua:218: in function <citizen:/scripting/lua/scheduler.lua:182>
Error running system event handling function for resource esx_datastore: citizen:/scripting/lua/scheduler.lua:41: Failed to execute thread: @esx_datastore/server/main.lua:88: attempt to index a nil value (local 'xPlayer')
stack traceback:
        @esx_datastore/server/main.lua:88: in upvalue 'handler'
        citizen:/scripting/lua/scheduler.lua:219: in function <citizen:/scripting/lua/scheduler.lua:218>
stack traceback:
        [C]: in function 'error'
        citizen:/scripting/lua/scheduler.lua:41: in field 'CreateThreadNow'
        citizen:/scripting/lua/scheduler.lua:218: in function <citizen:/scripting/lua/scheduler.lua:182>
Error running system event handling function for resource esx_status: citizen:/scripting/lua/scheduler.lua:41: Failed to execute thread: @esx_status/server/main.lua:29: attempt to index a nil value (local 'xPlayer')
stack traceback:
        @esx_status/server/main.lua:29: in upvalue 'handler'
        citizen:/scripting/lua/scheduler.lua:219: in function <citizen:/scripting/lua/scheduler.lua:218>
stack traceback:
        [C]: in function 'error'
        citizen:/scripting/lua/scheduler.lua:41: in field 'CreateThreadNow'
        citizen:/scripting/lua/scheduler.lua:218: in function <citizen:/scripting/lua/scheduler.lua:182>

This is my config.lua

endpoint_add_tcp "0.0.0.0:30120"
endpoint_add_udp "0.0.0.0:30120"

set mysql_connection_string "server=127.0.0.1;database=essentialmode;userid=root;password="
set es_enableCustomData 1
set sv_licenseKey "eri2g5yh3cj04a19f61bfitxnd36f7il"
sv_scriptHookAllowed 0
rcon_password tuvieja123
sv_hostname "ESX PUBLIC SERVER"
set temp_convar "ESX"

# disable announcing? clear out the master by uncommenting this
#sv_master1 ""

# want to only allow players authenticated with a third-party provider like Steam?
sv_authMaxVariance 1
sv_authMinTrust 1

# add system admins
add_ace group.admin command allow # allow all commands
add_ace group.admin command.quit deny # but don't allow quit
add_ace resource.essentialmode command.sets allow
add_ace resource.essentialmode command.add_ace allow
add_ace resource.essentialmode command.add_principal allow
add_principal identifier.steam:XXXXXXXXXXXXX group.admin # add the admin to the group

# hide player endpoints in external log output
sv_endpointprivacy true

#### FIVEM DEFAULT ####
    start NativeUI
	start mapmanager
    start chat
    start spawnmanager
    start sessionmanager
    restart sessionmanager
    start fivem
    start hardcap
    start ■■■■■■■
    start es_extended
    #start scoreboard
	#start Stadus_Scoreboard
    start es_ui
	start fxmigrant
	start PDX-loadscreen
	start bob74_ipl
	start CarCommand
	start spawn
	start spawnzone
	
#### MYSQL ASYNC
    start async
	start mysql-async


#### ESSENTIAL MODS
    start esplugin_mysql
    start essentialmode
    start es_admin2
	start CustomScripts
    start esx_society
	start esx_rpchat
	start chat-theme-civlifechat
	start PvP
	start esx_boilerplate
	
	
#### MAPAS
#minimapa textura colorida
    start map
#plaza
    start plazafinal
	start variosmap

#### AUTOS ADDON
    start AMGGTR
	

#### ESX REQUIRED MODS
    start esx_accessories
    start JoinTransition
	start EasyAdmin
	start pNotify
    #start banking
    #start es_rp
    start sesx
    start instance
    start cron
	start vMenu
	
	### INVENTORY HUD + TRUNK
	start esx_inventoryhud
	start esx_inventoryhud_trunk
	
	#start esx_lscustomsV2
	start esx_lscustom
    start esx_skin
    start esx_menu_default
    start esx_menu_list
    start esx_menu_dialog
    start esx_phone
    start esx_addonaccount
    start esx_addoninventory
    start esx_datastore
	start baseevents
    start esx_service
    start esx_billing
	start esx_scoreboard
	start esx_weaponshop

#### ESX JOBS
    start esx_jobs
    start esx_joblisting
    start esx_taxijob
    start esx_mechanicjob
    start esx_policejob
    start esx_property
    start esx_realestateagentjob
    start esx_bankerjob
    start esx_ambulancejob
    start esx_vehicleshop
	start esx_shops
	start esx_dmvschool
	start esx_licenseshop

#### ESX ANY OTHER MODS
    start esx_status
    start esx_basicneeds
    start esx_clotheshop
    start esx_garage
	#start esx_drp_garage
	#start esx_advancedgarage
    start esx_holdup
    start esx_drugs
    start esx_atm
	start RealisticVehicleFailure
	#start removeAIcops
	start SeatbeltIndicator
	start simeonfix
	start smoke
	start zone
	
	###NUEVOS PARA PROBAR
	start esx-checkdeathcause
	start esx_animations
    start cardealership
	start mgtablet
	start Storerobbery
	start carhud
    start skinchanger
	start TimeAndDateDisplay
	start watermark
	start frfuel
	
	##SIRENAS
	start ELS-FiveM
	
	##que es?
	#start ASSandACL
	

#### ANY NON ESX MODS
    #start nonESXmod

(sorry for the mess, but it works fine, i get into the server, but when I connect or someone else, i got that error on the console. I’ve tried to reinstall the databases but nothing solved.)

That was to be expected. That’s why i never trust these things.

1 Like

hmm ok, but is already solved

Want to share what went wrong though? i guess that’s why these forums are on the internet. My server runs though and all works but with some handle and CreateThreadNow errors but it seems that no one cares and with that i mean that people never came up with qa solution and the user that had that problem is nowhere to been seen… What was your solution now i can write you about this??

I mean, now you do the same as others… Say that it is solved but the topic is still unsolved and i see also no solution. Nothing against you or whatever but isn’t that these forums are there to get help and to help others?

I just reinstalled everything and connected to the database after that it went again without problems

Me also did a re-install and still have the same issue as before :frowning:

Error running system event handling function for resource esx_addonaccount: citizen:/scripting/lua/scheduler.lua:41: Failed to execute thread: @esx_addonaccount/server/main.lua:71: attempt to index a nil value (local ‘xPlayer’)
stack traceback:
@esx_addonaccount/server/main.lua:71: in upvalue ‘handler’
citizen:/scripting/lua/scheduler.lua:219: in function citizen:/scripting/lua/scheduler.lua:218
stack traceback:
[C]: in function ‘error’
citizen:/scripting/lua/scheduler.lua:41: in field ‘CreateThreadNow’
citizen:/scripting/lua/scheduler.lua:218: in function citizen:/scripting/lua/scheduler.lua:182

I have the same type of error. I would really appreciate any help.

Same error here

Has someone now a way how to fixed it?

1 Like

{HELP ME PLIZZZ}

Could any of you post the lines where you get the errors?

TriggerEvent(‘esx_addonaccount:getSharedAccount’, society.account, function(account)

  cb(accounts.money)

end)

On these lines

dose any one know on how to fix this

how do i fix this
image
esx_addacount


esx_datastore

it gives me this error when I want to place things in the house


esx_property

Hi!

The error comes from the table addon_account and addon_account_data. I had the same problem as you and the only solution was to delete everything and put it back manually in the DB with the MySQL files. My advice for the future is to always make a backup of your database so that you are safe if you encounter this kind of problem again