Problem with my test server (Windows 10/64 bits)

[bury]

Hello.

My server is hosted on a debian server but as it just have one ip available, I cant make a test server there so I make all my tests on my CPU, that is a windows 10 64 bits. It works even better than the debian one since the hardware of my pc is better than the one of the hosting server.

It has always worked 100% but I was about to start the server today and suddenly got this error:

"Unhandled exception, generating minidump..."

That warning I think is not the problem because it has always been there when server worked fine.

The weird thing is that I've not changed anything. It's a week since I dont use the test server... And when I was testing scripts etc everything worked properly, I just tested some things about the map, and console hasn't even loaded the map now, lol

I've tried restarting my PC, even restarting/uninstalling services of apache and mysql. The website on my localhost works properly and as you can see it loads the db too (Tried to set it on with the mysql stopped and it gave db error, so thats not the problem...).

Any idea? I can't make tests without it
Ty!!!

 

[Nekiro]

You have solution in your console, copy the query „SET Global...” and execute in your phpmyadmin sql tab.

 

[bury]

You have solution in your console, copy the query „SET Global...” and execute in your phpmyadmin sql tab.

As I say thats not the problem. I did that and...:

" Unhandled exception, generating minidump... "

(And it crashes everytime I try it and also the window of cmd/console dissapears)

EDIT:

The folder where is located the console executable (with config.lua etc) is full of .mdmp files lol one is created each time I try to open the console.

 

[WibbenZ]

As I say thats not the problem. I did that and...:

" Unhandled exception, generating minidump... "

(And it crashes everytime I try it and also the window of cmd/console dissapears)

EDIT:

The folder where is located the console executable (with config.lua etc) is full of .mdmp files lol one is created each time I try to open the console.

Then something is crashing the server and the server is giving you a crash dump to help you find the issue.
What does those files contain?

 

[bury]

Then something is crashing the server and the server is giving you a crash dump to help you find the issue.
What does those files contain?

How could I open them? its called for example: "theforgottenserver_26-10-2017_01-03-29.mdmp"

Tried with notepad ++ and it doesnt open.

 

[WibbenZ]

How could I open them? its called for example: "theforgottenserver_26-10-2017_01-03-29.mdmp"

Tried with notepad ++ and it doesnt open.

It should open but question is if it's in plain text or if you need to "decompile" the dump, upload one of them otherwise.

 

[bury]

It should open but question is if it's in plain text or if you need to "decompile" the dump, upload one of them otherwise.

This is one. I added .txt at the end so that I could upload in otland otherwise I wasnt allowed to do it. Just remove .txt and u'll have the .mdmp file.

Thanks wibben.

 

[WibbenZ]

This is one. I added .txt at the end so that I could upload in otland otherwise I wasnt allowed to do it. Just remove .txt and u'll have the .mdmp file.

Thanks wibben.

Okay so it's not in plain text humm ...
What I can find on google is that it isn't a good way to find issues for some reason? And alot of ppl seem to say it's not even worth using.

Do you have access to a computer running Linux? In that case you can use gdb ot get a clean crash log.
When I run into these issues on Windows I normally use a clean datapack and one by one remove / replace each folder (ex actions, talkactions etc etc) to see when the server starts.
From there you can remove like 10 lines from ex actions.xml and see when it starts, eventually you will find the script that caused the problem and can continue from there.

 

[bury]

Okay so it's not in plain text humm ...
What I can find on google is that it isn't a good way to find issues for some reason? And alot of ppl seem to say it's not even worth using.

Do you have access to a computer running Linux? In that case you can use gdb ot get a clean crash log.
When I run into these issues on Windows I normally use a clean datapack and one by one remove / replace each folder (ex actions, talkactions etc etc) to see when the server starts.
From there you can remove like 10 lines from ex actions.xml and see when it starts, eventually you will find the script that caused the problem and can continue from there.

Hey Wibben! Sorry for the late answer. I didnt need the test server (becuase had the real one on my hosting running without problem) and I left the problem stay. Now I return on it and I'm doing what you said. I copied my fully working server to my PC through FTP and tried renaming actions folder to old_actions and using the working folder. I did that with all folders and server still doesn't start. If I restart my server on my Linux hosting it starts without problem.

I knew this was going to happen because when I make some change in my test server I write it down, and after I see everything works properly I add that change (could be a script, could be a line in a script) to my hosting server. So yes, my server stopped working without reason lol. I'm trying to find out what is happening but atm I've no clue. Tried even to change config.lua Maybe a db problem?

EDIT: OK, tested the also fully working db of my hosting on the test server and it keeps generating minidumps.... So, if the datapack is not the problem, if the db is not the problem... what could be? binaries???

EDIT2: OK, tried downloading all libraries etc ([8.60] The Forgotten Server 0.4) the 64x, obiously, and it doesnt work. It keeps doing minidumps. This is really crazy.

 

[Okke]

WINDOWS

 

[bury]

WINDOWS

I can't do a test server in my hosting because I only have 1 ip. If Windows is the problem what have changed on it? I've been working on this test server more than 7 months but suddenly it started doing mini dumps on the start. I haven't done any update etc

 

[Okke]

Why don't you just install VirtualBox and set up a linux testing environment just to run the server? Windows is to mimimi about most everything. If your hosting can run it but your windows can't, the fault is definitely your code or the system it runs on.

 

[bury]

Why don't you just install VirtualBox and set up a linux testing environment just to run the server? Windows is to mimimi about most everything. If your hosting can run it but your windows can't, the fault is definitely your code or the system it runs on.

I dont know because here I manage everything very quickly, if a script works I just add it to my real server.

The thing is, why it worked for that long time and now it doesn't? If I download 0.4 from zero and install everything it won't work because of this minidump issue....

 

[bury]

b u m p

 

[Linxsis]

Okay so it's not in plain text humm ...
What I can find on google is that it isn't a good way to find issues for some reason? And alot of ppl seem to say it's not even worth using.

To open a mdmp file you use Visual Studios which i did and here is the information.

Dump Summary
------------
Dump File:    theforgottenserver.mdmp : C:\Users\User\Downloads\theforgottenserver.mdmp
Last Write Time:    12/21/2017 11:38:40 PM
Process Name:    theforgottenserver.exe : F:\Users\pedrito\Desktop\tibia 2017\theforgottenserver.exe
Process Architecture:    x64
Exception Code:    0xE06D7363
Exception Information:
Heap Information:    Not Present

System Information
------------------
OS Version:    10.0.14393
CLR Version(s):

Modules
-------
Module Name    Module Path    Module Version
-----------    -----------    --------------
theforgottenserver.exe    F:\Users\pedrito\Desktop\tibia 2017\theforgottenserver.exe    0.0.0.0
ntdll.dll    C:\Windows\System32\ntdll.dll    6.2.14393.103
kernel32.dll    C:\Windows\System32\kernel32.dll    6.2.14393.0
KERNELBASE.dll    C:\Windows\System32\KERNELBASE.dll    6.2.14393.187
ws2_32.dll    C:\Windows\System32\ws2_32.dll    6.2.14393.0
libxml2.dll    F:\Users\pedrito\Desktop\tibia 2017\libxml2.dll    0.0.0.0
lua5.1.dll    F:\Users\pedrito\Desktop\tibia 2017\lua5.1.dll    5.1.4.0
sqlite.dll    F:\Users\pedrito\Desktop\tibia 2017\sqlite.dll    0.0.0.0
sechost.dll    C:\Windows\System32\sechost.dll    6.2.14393.0
rpcrt4.dll    C:\Windows\System32\rpcrt4.dll    6.2.14393.82
user32.dll    C:\Windows\System32\user32.dll    6.2.14393.5
win32u.dll    C:\Windows\System32\win32u.dll    6.2.14393.51
gdi32.dll    C:\Windows\System32\gdi32.dll    6.2.14393.0
gdi32full.dll    C:\Windows\System32\gdi32full.dll    6.2.14393.0
libmysql.dll    F:\Users\pedrito\Desktop\tibia 2017\libmysql.dll    0.0.0.0
libeay32.dll    F:\Users\pedrito\Desktop\tibia 2017\libeay32.dll    0.0.0.0
dbghelp.dll    C:\Windows\System32\dbghelp.dll    6.2.14321.1024
ucrtbase.dll    C:\Windows\System32\ucrtbase.dll    6.2.14393.0
msvcp100.dll    C:\Windows\System32\msvcp100.dll    10.0.40219.325
mswsock.dll    C:\Windows\System32\mswsock.dll    6.2.14393.0
msvcr100.dll    C:\Windows\System32\msvcr100.dll    10.0.40219.325
wsock32.dll    C:\Windows\System32\wsock32.dll    6.2.14393.0
msvcrt.dll    C:\Windows\System32\msvcrt.dll    7.0.14393.0
zlib1.dll    F:\Users\pedrito\Desktop\tibia 2017\zlib1.dll    1.2.5.0
advapi32.dll    C:\Windows\System32\advapi32.dll    6.2.14393.0
dbgcore.dll    C:\Windows\System32\dbgcore.dll    6.2.14321.1024
imm32.dll    C:\Windows\System32\imm32.dll    6.2.14393.0
NapiNSP.dll    C:\Windows\System32\NapiNSP.dll    6.2.14393.0
pnrpnsp.dll    C:\Windows\System32\pnrpnsp.dll    6.2.14393.0
nlaapi.dll    C:\Windows\System32\nlaapi.dll    6.2.14393.0
dnsapi.dll    C:\Windows\System32\dnsapi.dll    6.2.14393.0
nsi.dll    C:\Windows\System32\nsi.dll    6.2.14393.0
IPHLPAPI.DLL    C:\Windows\System32\IPHLPAPI.DLL    6.2.14393.0
winrnr.dll    C:\Windows\System32\winrnr.dll    6.2.14393.0
rasadhlp.dll    C:\Windows\System32\rasadhlp.dll    6.2.14393.0

https://support.microsoft.com/en-us/search?query=0xE06D7363