Unable to write to directory

[GameConnectors]

After much trouble getting SOF 1 to run, I have managed to set it up how I want it in the panel.

 

 

 

However, when creating the server I get an error (emailed) saying that it can't write the config file to the specified directory.

 

 

 

I have checked all the permissions on that directory and they are fine.

 

 

 

Needless to say that the game server does not create properly.

 

 

 

Any help would be appreciated

[ECF]

What version of TCAdmin are you running?

 

 

 

In previous versions this problem would arise when you specified a path in the game config to write the server.cfg file, and the path did not exist.

 

 

 

However, the later version of TCAdmin automatically create any file and folders for you and write the file to it.

 

 

 

 

 

Example:

 

 

 

server.cfg file is located in the /main folder

 

When you create the game config, and create a new file path to the config, make sure you have /main/server.cfg

 

 

 

Also, make sure the folder /main exists in the install files.

 

 

[GameConnectors]

Yes the directory exists in the games directory structure already.

 

 

 

The TCAdmin version is:

 

 

 

Monitor Version:

 

1.0.2266.38149

 

 

 

Web Version:

 

1.0.2264.23750

 

 

 

Web .NET Version:

 

1.1.4322.2300

 

 

[ECF]

Looks like you are missing quite a few updates there.

 

 

 

 

 

At any rate, I can only think of 2 things off the top of my head.

 

 

 

1. The file link in the game config is incorrect.

 

 

 

2. There is some odd characters in the config that may be causing a problem.

 

 

 

 

 

If you would like, you can put in a ticket and we can take a look for you.

 

 

[GameConnectors]

No problem. I figured it out. Thanks

 

 

 

However, now I got the game installed I don't any results returned from the server. I have set the game compatibility to both SoldierOfFortune and Quake2, but no joy... Any ideas?

[LFA]

Set interact with desktop in the game server's service settings or run manually with the same command line to see it if starts up correctly.