Log in

View Full Version : Getting errors when i try to launch server


Astal
06-19-2014, 10:22 PM
Its saying something about error loading items common/memory_mapped_file line 130, no logs appeared for the errors, this happens when I launch world

Scorpious2k
06-19-2014, 10:28 PM
Did you run shared_memory.exe and let it finish before starting world?

Astal
06-19-2014, 10:30 PM
Did you run shared_memory.exe and let it finish before starting world?

it crashes i believe, no log file though, yeah it disappears after it gets to loading base data.

Getting the same error when running shared_memory, says line 61 in memory_mapped_file.cpp

Scorpious2k
06-19-2014, 10:38 PM
Then you need to run it from a batch file so it doesn't close.

create a file that has these 3 lines in it:

@echo off
shared_memory.exe
pause

save it as test.bat in your eqemu folder where shared_memory.exe, world.exe, etc are

double click it to run it

let's see what the error says

Astal
06-19-2014, 10:41 PM
Then you need to run it from a batch file so it doesn't close.

create a file that has these 3 lines in it:

@echo off
shared_memory.exe
pause

save it as test.bat in your eqemu folder where shared_memory.exe, world.exe, etc are

double click it to run it

let's see what the error says

no error, just stops loading at base data then it says hit any key to continue, the only other error i caught when first running shared memeory is


Eqemu exception (shared memory) in ..\common\memory_mapped_file.cpp at line 61 could not open a file for this shared memory segment

Scorpious2k
06-19-2014, 10:44 PM
You have a directory called Shared in that directory, right?

Astal
06-19-2014, 10:45 PM
You have a directory called Shared in that directory, right?

yes it has the following files

base_data
items
faction
loot_drop
loot_table
skill_caps and spells

Scorpious2k
06-19-2014, 10:51 PM
Delete all those files. Let's see what happens when you run test.bat again

Astal
06-19-2014, 10:54 PM
Delete all those files. Let's see what happens when you run test.bat again

same thing happens

Scorpious2k
06-19-2014, 10:55 PM
Are the files back?

Astal
06-19-2014, 10:59 PM
Are the files back?

yeah they come back after i run shared memory

Scorpious2k
06-19-2014, 11:09 PM
are any of them zero length?

Astal
06-20-2014, 11:32 AM
are any of them zero length?

no none of them are

imma try switching database once i get my meds today and see if it works, if it does its an error with my db and ill have a lot of work to do :(

Scorpious2k
06-20-2014, 12:13 PM
The only thing that has me baffled is how is it creating the files without *telling* you that it is creating them (in shared_memory.exe)

Trubles
06-20-2014, 12:16 PM
You might have a NULL in your database where there shouldn't be one.

What were you doing before you blew it up.

Astal
06-20-2014, 03:34 PM
You might have a NULL in your database where there shouldn't be one.

What were you doing before you blew it up.

this is my database from 2012. I quit working on it because i was sick, and figured id start it up again. So i havent really done anything to it since then, it did work with the older server from back then. It says its creating the files but it stops at base data then shared_memory shuts down with no error ect...

I get an error when shared memory runs but it blinks out before you can see it and restarts on its own. I posted it earlier in the thread it was about not being able to open a shared memory file. It errored on the Items table.

For some reason it restarts after that and runs through until base data.

My friend whos running the exact same database as me on x64 says he cant get it working on 32 bit either, so im wondering if its not my database after all

Uleat
06-20-2014, 04:08 PM
Since this is a 2012 db..has you sourced in all of the updates since?

Astal
06-20-2014, 06:57 PM
Since this is a 2012 db..has you sourced in all of the updates since?

yes, my friend did it, and hes running the exact database on x64 binaries, is there anything specific that may make it run on x64 and not x86, like a specific file he may not have sourced or?

or could it be a memory issue with the server like would i have to edit anything in the source to make it work with extra items and spells?

Astal
06-21-2014, 03:08 AM
Resourced my database, no files are appearing in the shared folder and im getting this error from world

nevermind, still getting the same error as before, cannot open shared memory file for this file segment

Astal
06-21-2014, 04:47 AM
Ok after i removed all the extra junk from the folder im just getting this error when I launch world after shared memory.

http://s14.postimg.org/o1z45j4pd/eq_errors2.jpg

lerxst2112
06-21-2014, 05:36 AM
If there aren't any files in the shared directory it does no good to try and run world, it will fail as you've seen.

Make sure you have a logs directory in your server directory, delete all files from the shared directory, then run shared_memory from a command prompt so you can see everything it outputs. Then, look in the logs directory to see if it wrote anything there.

Post the contents of the shared folder and any text it printed or wrote to a log file.

Astal
06-21-2014, 07:08 AM
If there aren't any files in the shared directory it does no good to try and run world, it will fail as you've seen.

Make sure you have a logs directory in your server directory, delete all files from the shared directory, then run shared_memory from a command prompt so you can see everything it outputs. Then, look in the logs directory to see if it wrote anything there.

Post the contents of the shared folder and any text it printed or wrote to a log file.

i cant get em to print in log files but i got the screen shot.

http://s16.postimg.org/8xggmcdol/eq_errors.jpg


HOWEVER if I run my whole server I get this error on world im guessing however thats cause the items arent loaded right, i get the same error using the PEQ database as mine so that shouldnt be it

http://s24.postimg.org/4fugy9pn9/eq_errors2.jpg

Astal
06-21-2014, 07:30 AM
The line in the source that error is pointing at is does that mean the name of the memory file in shared is wrong?

if(file == INVALID_HANDLE_VALUE) {
EQ_EXCEPT("Shared Memory", "Could not open a file for this shared memory segment.");
}

Trubles
06-21-2014, 10:47 AM
did you copy eqtime.cfg into your server folder from the source?

joligario
06-21-2014, 01:11 PM
did you copy eqtime.cfg into your server folder from the source?

That won't error out the shared memory.

Scorpious2k
06-21-2014, 01:55 PM
That won't error out the shared memory.

But it is the error he is getting in the screenshot.

Astal
06-21-2014, 05:47 PM
But it is the error he is getting in the screenshot.

i fixed the time thing still getting the shared memory error which is the problem, this exact database works on x64

Uleat
06-21-2014, 08:28 PM
Re-run cmake and post a screenie of the output there, si vous plais.

(You don't need to make changes..I'm just curious what is being found.)

Astal
06-22-2014, 01:18 AM
Re-run cmake and post a screenie of the output there, si vous plais.

(You don't need to make changes..I'm just curious what is being found.)

http://s27.postimg.org/8lbcdsacz/cmake1.jpg

http://s27.postimg.org/gpjgiiws3/cmake2.jpg

Astal
06-22-2014, 03:00 AM
Also if anyone could do me this favor, compile the 32bit server with vc++ 2013 and send me the exes maybe this is a problem with VC++ 2010

joligario
06-22-2014, 10:24 AM
Also if anyone could do me this favor, compile the 32bit server with vc++ 2013 and send me the exes maybe this is a problem with VC++ 2010

Done: https://github.com/EQEmu/Server/wiki/EQEmu-Binaries

Astal
06-22-2014, 11:08 AM
those are built with 2013? they are not valid win 32 applications, u sure u did 32bit

yeah u might wanna recheck em, im on xp and its saying not a valid win 32 application

thanks for tryin tho

unless maybe you just uploaded the wrong ones i dunno

joligario
06-22-2014, 12:52 PM
Yes, I'm sure. Now that you mention XP, I'm thinking they aren't backwards compatible on an XP machine. I'll build one on an XP machine for you to try if you want. Clarified the build on GIT.

EDIT: Hmm, or maybe not. I forgot I dumped my XP virtual machine...

lerxst2112
06-22-2014, 07:26 PM
http://msdn.microsoft.com/en-us/library/jj851139.aspx

joligario
06-22-2014, 08:10 PM
Ah, I wonder if Express doesn't allow it. I'll toy around with it.

Astal
06-22-2014, 08:51 PM
yeah i dont think u can use 2013 on xp i tried, oh well no biggy ill just wait to work on my server till next month when i get more ram, also if anyone has ddr 2 2gb or bigger sticks for sale lemme know haha i hate to spend 50-60 bucks on 2gb

lerxst2112
06-22-2014, 09:03 PM
Although those instructions refer to 2012 even though they are marked as for 2013, I do have the 120xp and 110xp toolsets available in my 2013 express installation. That may be because I also have 2012 installed, but worth a shot.

I don't believe your issues are related to 32-bit or XP, since the shared memory error relates to not being able to create the file. I suspect your working directory or the permissions of the shared directory are the issue. I tried to eliminate the working directory as a problem by asking you to run it from the command prompt but you didn't, so I gave up.

Astal
06-22-2014, 09:20 PM
Although those instructions refer to 2012 even though they are marked as for 2013, I do have the 120xp and 110xp toolsets available in my 2013 express installation. That may be because I also have 2012 installed, but worth a shot.

I don't believe your issues are related to 32-bit or XP, since the shared memory error relates to not being able to create the file. I suspect your working directory or the permissions of the shared directory are the issue. I tried to eliminate the working directory as a problem by asking you to run it from the command prompt but you didn't, so I gave up.

I ran it from a command prompt, how does that eliminate the working directory as the problem? The file is still held in that folder in windows? Im confused, ive ran shared mem from a command prompt, same error as I posted in the image

lerxst2112
06-22-2014, 11:47 PM
The screenshot you posted showed it being run from explorer. Running it from a command prompt after you cd to the directory ensures the working directory is correct, where running it from a batch file wouldn't. It also ensures that any output from the program would remain in the window for you to copy/paste.

I would delete the shared and logs directories, empty the trash if you use the recycle bin, then reboot. After that, from a command prompt navigate to the server directory, create both the shared and logs directories using mkdir, then run shared_memory again. There should be output both in the command prompt window as well as a log file in the logs directory.

Astal
06-23-2014, 03:47 AM
The screenshot you posted showed it being run from explorer. Running it from a command prompt after you cd to the directory ensures the working directory is correct, where running it from a batch file wouldn't. It also ensures that any output from the program would remain in the window for you to copy/paste.

I would delete the shared and logs directories, empty the trash if you use the recycle bin, then reboot. After that, from a command prompt navigate to the server directory, create both the shared and logs directories using mkdir, then run shared_memory again. There should be output both in the command prompt window as well as a log file in the logs directory.

k i did run it using cd on command prompt but ill do that

Astal
06-23-2014, 05:13 AM
The screenshot you posted showed it being run from explorer. Running it from a command prompt after you cd to the directory ensures the working directory is correct, where running it from a batch file wouldn't. It also ensures that any output from the program would remain in the window for you to copy/paste.

I would delete the shared and logs directories, empty the trash if you use the recycle bin, then reboot. After that, from a command prompt navigate to the server directory, create both the shared and logs directories using mkdir, then run shared_memory again. There should be output both in the command prompt window as well as a log file in the logs directory.

k i did it, same error as before, nothing in logs

Scorpious2k
06-23-2014, 05:14 PM
Start over. Use the guide to set up a vanilla system with the PEQ database. Run it.

If it works, then we change ONE thing at a time until it breaks.

The last thing changed is what is wrong.

This will be much better than everyone guessing at what is changed and what is going on.

lerxst2112
06-23-2014, 07:18 PM
Any there are no files at all in the shared directory?

The problem is that MemoryMappedFile doesn't give nearly enough information to troubleshoot this without either changing the code or running it in the debugger. At a minimum you'd need to know the requested size that's passed in and what GetLastError() returns when it fails.

Astal
06-24-2014, 03:47 AM
Any there are no files at all in the shared directory?

The problem is that MemoryMappedFile doesn't give nearly enough information to troubleshoot this without either changing the code or running it in the debugger. At a minimum you'd need to know the requested size that's passed in and what GetLastError() returns when it fails.

is there any way to find that out?

Yes there are files in the directory up to base data

Uleat
06-24-2014, 05:34 PM
What is the highest Item ID in-use in your database?

lerxst2112
06-24-2014, 07:27 PM
is there any way to find that out?

Yes there are files in the directory up to base data

This feels like pulling teeth...

Clean everything out of the logs and shared directories.
Run shared_memory
Post all of the filenames and sizes of all the files in the logs and shared directories.

As far as finding out exactly what is failing, the list of files will help since whatever is missing is probably the problem. The information about the size and type of error can be determined by running the code in the debugger with the proper working directory, using something like procmon, or changing the code to log that information.

You can also try generating each file by itself by passing the appropriate command line parameters to shared memory. They are base_data, items, factions, loot, skill_caps, and spells.