Server Problem

[Umtiti]

Hi,
I have a problem. Two days ago I started having problems when creating a virtual server, it says: invalid file path error code: 2054. Update the server to the latest version and the problem was fixed for 1 day, now I have the same problem again. How can I solve it?

Before updating the server, I was using the same version for 1 year and I never had this problem and now it just appears.

Just update the version for this problem, since I read in the TS forums that it was because of a very old version problem

 

[InVaDeR359]

Hi,
I have a problem. Two days ago I started having problems when creating a virtual server, it says: invalid file path error code: 2054. Update the server to the latest version and the problem was fixed for 1 day, now I have the same problem again. How can I solve it?

Before updating the server, I was using the same version for 1 year and I never had this problem and now it just appears.

Just update the version for this problem, since I read in the TS forums that it was because of a very old version problem

Does this mean that you fixed your problem ?

 

[Umtiti]

No, I explained badly in the last thing I said.

I still can not solve the problem, update the server to another version and I get the same error

 

[InVaDeR359]

Can you tell me in which way are you creating a virtual server, also are you using a *cracked* license or running it without license and how many slots did you set for the virtual server ?

 

[Umtiti]

I have a Cracked license. The servers I am trying to create from Yatqa and from WHMCS, a server of 10 and 30 slots.

I have more than 100 servers created and I have never had this problem and I have been with the servers for more than 4 years

 

[InVaDeR359]

Something is wrong with your WHMCS configuration then, or some file permissions are missing.
Maybe this can help you.

 

[Umtiti]

Now the servers are down and when I start it, it shows me the following error:

 

[redspark]

./ts3server_minimal_runscript.sh disable_db_logging=0 or edit start script COMMANDLINE_PARAMETERS="disable_db_logging=0 ${2}" maybe it works.