Pak sum/name mismatch

Hi.

Next problem. Server is running now, but when i try to connect it gives the error "pak sum/name mismatch".
Ive searched the net to find a solution, but all i found was that i might have to many paks or mods in my main. To me this sounds weird, cause it only gives me this error when i try to connect to my own server.
My main on the client side is clean, the uo therefor has a lot of custom paks in it, but never gave this error before and still doesnt when i wanna play on other servers.

My question is : is this a server side problem? and what to do a bout it?

Server is Windows based and running with awe 2.12

This error was an error because of too much custom pk3-files - has been patched with patch 1.3.

So it must be something on Server or Client side - I remember you have deletetd some pk3´s, you wrote you deleted paka.pk3...

Perhaps you should make and post some screenshots of your Call of Duty-, your main-, your uo- and your MOD-folder (Server & Client) and we will take a look at it.

I made sum screenshots, but are not able to put them here.

ill send them to your email adress, ok?

http://imageshack.us

I put the screenshots on this site : http://home.wanadoo.nl/moses

O ok, let´s try it, but first a tip for the future:
Save screenshots as .jpg, .jpeg or .gif - this will take less webpsace and the pics will be loaded faster...

---

The server looks good, but why do you have several folders for AWE?

You should have only one folder for AWE -> awe_cod or awe_uo (for CoD or UO) - on server and on client side...

And what is you starting parameter?

If the foldername is not unique on server and on client side, the client will try to download the server files...

And you really should clean up the main-folder of your client - it is full with maps and several MODs - I think this is were the error comes from.

The other folder with awe in it was created when i unziped the downloaded zipfile. I removed the folder. Now the awe modfiles are only in the serverfolder with my cfg file.

What do you mean with the starting parameter? is it this :
"C:\Program Files\Call of Duty\CoDUOMP.exe" +set fs_game "Myserver Awe 2.12" +set dedicated 2 +exec MiklosbattlefieldUO.cfg

The problem, i think , must be on the serverside, cause, beside the dedicated server, i can use two other computers as clients and they both give the sam error. Client1 has the large uo folder with all the pk3files and client2 has got a clean install of both cod and coduo.

To be sure to have all the required and only the required files in my call of duty folder on the server side, i deleted and reinstalled both cod and coduo on the server as well.

There is no interferance off zonealarm on the trusted side, cause i removed that (and reinstalled it later again, ofcourse ), started the server and it gave the same mismatch.

I see your server have the Awe Mod and the Merciless Mod installed...

Maybe they aren't compatibly !?!

I would delete the Merciless Mod and try again.

I think you're refering to the merciless blood mod.
It was already in there when i unpacked the awe 2.12 zipfile. but anyway i tried to run the server without it and it gave the same error.

Running the server on the other comp wasnt a solution either, still same error.

What did help was removing the complete awe mod and startup with a simple cfg file. So the problem must be in that mod.

Ok guys,

Found the problem

Somehow cod has dificulties when downloading pk3-files (or folders in wich the are, wich was the problem in my case) that have spaces in the name.

I was running the server from the folder Myserver Awe 2.12. It had 2 spaces in the name. Chaged the name to MyserverAwe_2.12 and it works ! !

thnx for all the help.

Hi, sorry, haven´t been here for some days.

Ok, you found it, I haven´t thought for it - don´t use spaces in names for folders or pk3-files, CoD and UO (and CoD2) can´t handle it. Have forgotten it in my last post, sorry.