startup.txt Ignored during startup

[ReAP3R_za]

Here's one for the other RSP's out there.

 

We recently expanded our server offering and added a remote server version of TCAdmin v 2. The problem now remains that when we start up a new BF3 server on the remote box, it completely ignores the startup files. Each server auto defaults to 64 slots, it does not read the admin password at all.

 

I've managed to narrow this down to TCAdmin purely because I am able to startup a server manually, pointing it at the instance folder with the startup files and works perfectly.

 

TCAdmin on the master server works 100% when setting up new BF servers with none of the issues we are experiencing on the remote server.

 

Has anyone experienced this? Would anyone be able to offer advice?

[MarcT]

I have not experienced this before, hopefully someone out there will have a good insight on this.

 

Good luck with the issue!

[lpgservers]

Removed my previous comment. I still wouldn't help you after ripping others work whether you removed it or not.

Edited March 16, 2013 by lpgservers
Updated info

[HIS-MOTHER]

He actually removed the splash page after we had some emails with him..

 

 

 

Post your TCA command line....

[Bubka3]

He actually removed the splash page after we had some emails with him..

Huh?

[HIS-MOTHER]

Huh?

 

http://clientforums.tcadmin.com/showthread.php?t=10872

[ReAP3R_za]

Thank you for being willing to assist Lane. I've managed to solve the problem in the end through recoding a BF3 config file for TCAdmin.

[HIS-MOTHER]

Thank you for being willing to assist Lane. I've managed to solve the problem in the end through recoding a BF3 config file for TCAdmin.

 

Anytime, although I'm not Lane.

[ReAP3R_za]

Anytime, although I'm not Lane.

 

Apologies. Either way, I do appreciate the willingness to assist.