- Joined
- Sep 20, 2012
- Messages
- 420
- Reaction score
- 47
This is only in relation to: TeamNG UNTIL i have made an open version (problems with Windows atm!)
While i made the tool i failed to give instructions on how to use the damn thing. I should do that. First off with the tool you have 3 Server side buttons and the client button - the client is a basic redirection to download a full client that works with the files.
So the buttons: Database, Tools, Server - When hitting the Database button you download the backup database, a FULL Setup for MSSQL 2017 and MSSQL Management Studio 17 - Database is dependant on what you put in Server Location text box (default C:\) but the other two download to where-ever you launch the application from - you need to install the MSSQL 2017 and management studio - (guide available in my previous post) Here.
After you completely setup both of the SQL 2017 & Management software this is where it gets interesting. You need to do a couple of things to ensure the services run (that i DIDN'T include!). So it works with EVERY system i didn't use ODBC connectors. This is because its faster and easier to plug them into a SQL Driver. Next download the server (make sure everything is correct) i.e. IP Address, Computer Name and Database. Once thats done you'll have nothing to worry about with the server side but its the database side you have issues with.
So open the SQL Management Software (you should have it launched already if you've restored the backups). In Security on the Object Explorer -> You have a drop down menu of 5 (Logins, Server Roles, Credentials, Audits, Server Audit Specifications) you want to expand Logins - See if NT AUTHORITY\SYSTEM is there. If not ADD it, if so you need to go to properties on it. Then go to User Mapping -> Ensure it has Access TO EVERY database that you restored, (Account, AccountLog, OperatorTool, StatisticsData, w00_Character, w00_GameLog). Also grant every role membership - (this is to make the services run). Once that's done you can run the services and hopefully if done correctly you should have the Server running with no issues. (found a few issues with this myself but it works)
Fiesta Server Installation V2 has been released in page 3 just for the sake of it i'm giving an update
You must be registered to see links
Also i am intending on converting over to C++/C# for version 3 if i ever make Version 3 with added support of what files you want from Odin to TeamNG files.
While i made the tool i failed to give instructions on how to use the damn thing. I should do that. First off with the tool you have 3 Server side buttons and the client button - the client is a basic redirection to download a full client that works with the files.
So the buttons: Database, Tools, Server - When hitting the Database button you download the backup database, a FULL Setup for MSSQL 2017 and MSSQL Management Studio 17 - Database is dependant on what you put in Server Location text box (default C:\) but the other two download to where-ever you launch the application from - you need to install the MSSQL 2017 and management studio - (guide available in my previous post) Here.
After you completely setup both of the SQL 2017 & Management software this is where it gets interesting. You need to do a couple of things to ensure the services run (that i DIDN'T include!). So it works with EVERY system i didn't use ODBC connectors. This is because its faster and easier to plug them into a SQL Driver. Next download the server (make sure everything is correct) i.e. IP Address, Computer Name and Database. Once thats done you'll have nothing to worry about with the server side but its the database side you have issues with.
So open the SQL Management Software (you should have it launched already if you've restored the backups). In Security on the Object Explorer -> You have a drop down menu of 5 (Logins, Server Roles, Credentials, Audits, Server Audit Specifications) you want to expand Logins - See if NT AUTHORITY\SYSTEM is there. If not ADD it, if so you need to go to properties on it. Then go to User Mapping -> Ensure it has Access TO EVERY database that you restored, (Account, AccountLog, OperatorTool, StatisticsData, w00_Character, w00_GameLog). Also grant every role membership - (this is to make the services run). Once that's done you can run the services and hopefully if done correctly you should have the Server running with no issues. (found a few issues with this myself but it works)