Aller au contenu

Photo

Server Error: "Local vault characters not allowed"


  • Veuillez vous connecter pour répondre
19 réponses à ce sujet

#1
Promethean 47

Promethean 47
  • Members
  • 157 messages
http://nwn2forums.bi...10807&forum=116

My server continues to intermittently have this same issue.  Players try to create a new character on the a/d interface, or select an old one, and are given this error, crashed back to main title menu.

To be clear, I have the settings so that local vault characters are not allowed.  I also am not enforcing legal characters.  

Given these settings, I have no clue how this could be causing an issue.

#2
Promethean 47

Promethean 47
  • Members
  • 157 messages
Any ideas?

#3
SkywingvL

SkywingvL
  • Members
  • 351 messages
Is character export similarly broken?

If so, my guess is that your %TEMP%\\\\NWN2\\\\TEMP.0 directory has been deleted it. Recreating it manually should allow you to recover (the server creates this directory each startup).

If that's the case, it will be up to you to discover what's whacking the directory.  Tools like Process Monitor from Sysinternals would be my recommendation on tracking that down -- good luck.

Modifié par SkywingvL, 11 octobre 2010 - 05:10 .


#4
casadechrisso

casadechrisso
  • Members
  • 726 messages
I was shown around on your server a few weeks ago and actually encountered this same problem - almost gave up trying due to it. :)



My wild guess would be Windows safety settings... maybe the directory is protected with Admin rights, or you have to run the server in admin mode, something along these lines.

#5
Olblach

Olblach
  • Members
  • 175 messages
First place to look would be nwn.ini in your server's "My Documents\\Neverwinter Nights 2" folder.

#6
Promethean 47

Promethean 47
  • Members
  • 157 messages
I've looked through the nwn.ini and nwn2player.ini as well as the nwnx4.ini.



There is nothing that should be causing this problem. The server is set to not allow use of local characters. (allowlocalcharacters=0).



We use the following:

- custom built from scratch classes

- custom built from scratch races and subraces

- custom magic system

- i.e. a lot a lot of custom stuff



My thought is somehow the server is erroring because there is some local file teh player client is trying to load that is clashing with our custom stuff. I.e. a character created using our custom classes etc, if stored locally, would presumably crash that player client whenever it was used to load a character for a different pw. But we have no reports of such crashing by players trying to do other pw's. Thus, I don't think this is really an issue with local content stored by the player.



Could it be something stored to the server that is conflicting with the server's own 'servervault'?


#7
Promethean 47

Promethean 47
  • Members
  • 157 messages
How do I find this %temp% folder you speak of skywing?

#8
Promethean 47

Promethean 47
  • Members
  • 157 messages
okay. figured that out. I did run %temp% and it showed. the %TEMP%\\\\\\\\NWN2\\\\\\\\TEMP.0 folder indeed already existed and was empty.



What does this mean?

#9
barfoobaz

barfoobaz
  • Members
  • 4 messages
I've heard of this happening before, something to do with Fastboot feature added to NWNX4 not too long ago. Are you using that?



- Bar

#10
SkywingvL

SkywingvL
  • Members
  • 351 messages
xp_fastboot shouldn't cause the "deleted temp.0 folder breaking character export / character creation" problem. (xp_fastboot won't work correctly should your %temp% is not on the same volume as your NWN2 home directory [something you would have to go out of your way to do, not a default configuration], this is called out in the documentation and the result would just be that the server would refuse to start up the module until the issue was corrected.)

Modifié par SkywingvL, 15 octobre 2010 - 04:48 .


#11
SkywingvL

SkywingvL
  • Members
  • 351 messages

Promethean 47 wrote...

okay. figured that out. I did run %temp% and it showed. the %TEMP%\\\\\\\\\\\\\\\\NWN2\\\\\\\\\\\\\\\\TEMP.0 folder indeed already existed and was empty.

What does this mean?

It's normal for this directory to be empty.  Was this when the problem was reproducing or during normal server operation?

There may be other issues that could lead to this problem, however, deleting the temp.0 directory will certainly result in it as the server will fail to dump the character to disk there during one of the steps in handling a character creation request.

#12
Promethean 47

Promethean 47
  • Members
  • 157 messages
skywing - the only way i know how to export characters in the client is to use DMFI's save character option. I think I may just have to find you online sometime and go over this.



I had my players clear their local vaults and they stopped having problems. That said, inevitably more players will come in with this same problem. So i'd like to solve it....sigh. The joys of nwn2.

#13
Olblach

Olblach
  • Members
  • 175 messages
nwn.ini contains the paths for the different vaults. Are they ok?

#14
Promethean 47

Promethean 47
  • Members
  • 157 messages
What does this setting really do?



Added the option "Supress Base Servervault" to prevent listing characters in the root of a Server Vault:



nwplayer.ini

[Server Options]

Suppress Base Servervault=0



Set this to 1 if you don't want your clients seeing character files from the root of the Server Vault.





#15
Promethean 47

Promethean 47
  • Members
  • 157 messages
My server's nwn2player.ini (***** indicate blacking out passwords/emails etc)



[Game Options]

Pause On Lose Focus=1

Difficulty Level=3

[Server Options]

Validate Character Ownership=0

Pause Loading During Cutscenes=0

ClientSyncRequired=1

DisableClientOverride=1

DisableClientCustomUI=0

InfoURL=http://dl.dropbox.com/u/1803465/client/info.htm

NewsURL=http://dl.dropbox.com/u/1803465/client/news.htm

RulesURL=http://dl.dropbox.com/u/1803465/client/rules.htm

AdminEmail=**********

ClientCacheStrategy=2

ClientCachePassphrase=*****************

EnableClientModuleCleanup=1

EnableClientCampaignCleanup=1

Disable log in heal=0

HideChallengeRatingInExamine=1

HideEffectListInExamine=0

2DA Cache Size=10

ShowSearchSpam=0

Scripts Print To Log=1

Scripts Print To Screen=0

Game Port=5121

Max Players=40

Server Name=Legacy: Beta (Stage 3)

Reload Module When Empty=0

GameSpy Enabled=1

Game Type=0

PVP Setting=2

PauseAndPlay=0

Disable AutoSave=0

Auto Save Interval=0

AllowLocalChars=0

Game Region=0

Game Type=3

ServerDownTimer=180

CD Banned Behavior=0

One Party Only=0

Enforce Legal Characters=0

ItemLevelRestrictions=0

Suppress Base Servervault=1

Disallow Shouting=1

ShowDMJoinedMessage=0

BackupSavedChars=0

[Banned Ips]

0=

[Banned Players]

0=

[Banned CD Keys]

0=








My server's nwnx file:



# NWNX4 configuration file

# These are the default values for NWNX4.



# Path to NWN2 installation (where nwn2server.exe is located)

# no default. You really have to specify it, currently.

nwn2 = C:\\Program Files\\Atari\\Neverwinter Nights 2



# You can override the tempory path NWN2 uses

# This is where NWN2 will put its logfiles (among other files)

# no default

# nwn2temp = C:\\NWNX4\\logs



# Command line parameters to start the server with

# default: no parameters

parameters = -moduledir "Legacy1" -adminpassword **** -difficulty 3 -dmpassword **** -gametype 3



# Should NWNX restart the server if the server process has gone away ?

# 0 = do not restart the server

# 1 = restart the server

# default: 1

processWatchdog = 1



# Should NWNX restart the server if it locks up ?

# This can happen if the server is still running, but does not react to gamespy queries any more.

# 0 = do not query the server

# 1 = query the server

# default: 1

gamespyWatchdog = 0



# If you activate the gamespy watchdog, you need to specify the port your NWN2 server is running on

# default: 5151

gamespyPort = 5121



# How often should the gamespy watchdog query the server ?

# Note: The server will be restarted if it does not react to a certain number of

# queries in a row. See setting gamespyTolerance below.

# default: every 30 seconds

gamespyInterval = 30



# How often may the server not react to gamespy queries ?

# Note: The server will be restarted if it does not react this many queries in a row

# Example: gamespyInterval = 30 and gamespyTolerance = 4 means that the server will

# be restarted if it does not react within 2 minutes

# default: 4 queries

gamespyTolerance = 4



# How long should NWNX wait before the gamespy watchdog kick in ?

# Note: Give the server enough time to load the module, otherwise the watchdog will start to complain

# Value = seconds to wait

# default: 30 seconds

gamespyDelay = 30



# If the server crashes, how long should NWNX wait before it restarts the server ?

# Value = seconds to wait

# default: 5 seconds

restartDelay = 5



# Should NWNX disable the general protection fault error dialog ?

# Note: The watchdogs may fail to restart the server properly if this dialog stays open

# 0 = do not disable the GPFault dialog

# 1 = disable the GPFault dialog

# default: 1

noGPFaultErrorBox = 1



# If you want NWNX to execute a CMD or BAT file before restarting the server after

# a crash, specify it's name here. If you leave this setting empty, no program

# will be run. NWNX will wait for the program to finish before it continues.

# no default

# restartCmd = nwnx_restart.cmd



# How long should NWNX wait for the server to shutdown gracefully

# before it ends the server process forcefully ?

# Value = seconds to wait

# default: 10 seconds

gracefulShutdownTimeout = 30



# You can enter a server message that will be sent to all players

# as NWNX tries to shutdown the server.

# Value = message

# default: none

gracefulShutdownMessage = Server is restarting, please log out.



# How long should the shutdown server message be displayed ?

# Value = seconds to wait before actual shutdown

# default: 5 seconds

gracefulShutdownMessageWait = 15







#16
c i p h e r

c i p h e r
  • Members
  • 261 messages
I've had players experience this kind of problem. The client would crash whenever attempting to load the character selection menu. I've chalked it up to corrupt or incompatible bic files, and purging those files solves the problem.

I'm not entirely sure what can cause corruption, but a 2DA change that affects character builds or attributes would create an incompatibility. If a character is no longer compatible with the options a world supports, it's at least understandable why the client would choke on it.

#17
Shockwolf

Shockwolf
  • Members
  • 26 messages
Do you use Ccleaner or any other type of cache cleaning app whilst your NWN2 server is up?

#18
Promethean 47

Promethean 47
  • Members
  • 157 messages
Ok, so this problem persists.

My server vault paths are correct. 

The server does not use or run ccleaner.

My idea for a band-aid to alleviate this problem is to setup automatic timed server resets (the nwnserver, not the actual machine server i.e. windows reboot). Can someone point me to a link showing how best to set it up so the server restarts once every 6 hours or so?  I haven't found an nwnx command paramaters or documentation or any nwnx plugins that do this.

Do I need to do an inmodule script that will control/send a shutdown/reset command?

I'm looking to get my ducks in a row for imminent server launch, and I'd appreciate some advice from the pros on how to best set up my nwnx and server for ideal operation.

#19
painofdungeoneternal

painofdungeoneternal
  • Members
  • 1 799 messages
google xp_system, it does server reboots from nwscript. ( nwnx plugin )

#20
Promethean 47

Promethean 47
  • Members
  • 157 messages
Solution Found:



This may not work for everyone, but we have solved this problem (I believe). Our server machine was indeed running Norton. I went into Norton's settings and did the following:



(1) Turn off active-cache monitoring

(2) Add folder exemptions to mydocs>nwn2, all dropbox/hosting folders, and C:/programfiles...atari>nwn2. (basically add an exception for any folder nwn2 or your server uses to run/host nwn2).



This problem has not posted up since despite 4-5 updates and countless resets.