Run time error 10: native error

Read log files for errors! If this fails, come here for help

Moderator: Forum Moderator

Post Reply
wormwood
Peon
Posts: 21
Joined: Thu Aug 18, 2005 10:07 pm

Run time error 10: native error

Post by wormwood » Tue Oct 25, 2005 2:16 pm

When my server crashes this is what I get.

From the amxx logs:

Code: Select all

L 10/25/2005 - 14:29:21: [AMXX] Displaying debug trace (plugin "warcraft3FT.amxx")
L 10/25/2005 - 14:29:21: [AMXX] Run time error 10: native error (native "get_user_team")
L 10/25/2005 - 14:29:21: [AMXX]    [0] warcraft3FT.sma::client_disconnect (line 553)
From the server logs:

Code: Select all

L 10/25/2005 - 14:48:44: [WAR3FT] dev: called: GiveFnptrsToDll
L 10/25/2005 - 14:48:44: [WAR3FT] WARNING: meta-interface version mismatch; requested=WAR3FT ours=5:12
L 10/25/2005 - 14:48:44: [WAR3FT] WARNING: metamod version is newer than expected; consider finding a newer version of this module
I have amxmodx 1.6 and metamod 1.18 on a linux server. I recompiled all the plugins on Sun. Oct 23, 2005.

any suggestions?

User avatar
Geesu
<b>King of the world!</b>
Posts: 3159
Joined: Tue Jul 05, 2005 9:24 pm
Contact:

Post by Geesu » Tue Oct 25, 2005 3:43 pm

What happens when it crashes? That native error won't cause a crash...
No Support via PM

User avatar
Lazarus Long
Lead PITA SOB
Posts: 618
Joined: Tue Jul 05, 2005 9:24 pm

Re: Run time error 10: native error

Post by Lazarus Long » Tue Oct 25, 2005 5:58 pm

wormwood wrote:From the server logs:

Code: Select all

L 10/25/2005 - 14:48:44: [WAR3FT] dev: called: GiveFnptrsToDll
L 10/25/2005 - 14:48:44: [WAR3FT] WARNING: meta-interface version mismatch; requested=WAR3FT ours=5:12
L 10/25/2005 - 14:48:44: [WAR3FT] WARNING: metamod version is newer than expected; consider finding a newer version of this module
I have amxmodx 1.6 and metamod 1.18 on a linux server. I recompiled all the plugins on Sun. Oct 23, 2005.

any suggestions?
It doesn't have to do with your error (at least it never gave me any problem besides being annoying to see in the logs) but you can also recompile the module against Metamod 1.18 and these warning messages will go away.
Lazarus

wormwood
Peon
Posts: 21
Joined: Thu Aug 18, 2005 10:07 pm

Post by wormwood » Wed Oct 26, 2005 4:08 pm

Ive recompiled again just to be sure. I will inform you if I have any further problems.

Thanks

Post Reply