![[Guide] Custom certification errors , Privileged ip table / simple guide for newbies](https://www.elitepvpers.com/forum/iconimages/sro-pserver-guides-releases/guide-custom-certification-errors-privileged-ip-table-simple-guide-newbies_ltr.gif){kind=small}
[Guide] Custom certification errors , Privileged ip table / simple guide for newbies
1- Database initial size :
- In most of the tutorials , the default initial size of the db was "3 mb" , but when I was making a new database , my default value was "2 mb" , dun know even it's importance , but i thought it's better to make it just like the tutorials say (till I know why we should change it to 3mb)
* before : * after :
- Also you should go to (options tab) whilst restoring any database backup file (.bak) and select the option to "overwrite the existing database"
2- Hamashi ip \ static ip [Certification problems - CustomCertificationServer.bat closing suddenly \ showing error] :
- Most of the tutorials just skip this part and only mention that you should write down your ip , so most of people including me put their ipv4 which is usually 192.168.1.2 ~ 192.168.1.8 , and then they get the error during the certification process
So basically to solve this problem , you should either have a static ip (which is not an easy choice) or you use the free hamashi network
Then go to download hamashi through the normal way , install it normally , then you'll be able to get "YOUR REAL IP" that you are going to use in :
Code:
1- \CustomCertificationServer\bin\ini\srNodeType.ini 2- \server.cfg 3- \GameServer.exe [patch your ip through sr_patcher] 4- \AgentServer.exe [patch your ip through sr_patcher] 5- \MachineManager.exe [patch your ip through sr_patcher] 6- \smc\ServiceManager.cfg 7- \smc\smc_updater.cfg 8- \media.pk2 [patch it manually] 9- dbo._privilegedip
3- Privileged ip table :
In some DBs , you'll find that the privilegedip table is totally different from the tutorials , as it takes that look
and i didn't find any information about how to deal with that format of table , so i've worked out a solution through copying that table from any other clean account_db (attached below) , and here's the steps :
- Make a new database , and name it for ex : testdb
- Restore any normal account database (attached below)
- Head to your original db (usually SRO_VT_ACCOUNT) and delete the dbo._PrivilegedIp table
- Restart your mssql server
- Execute the following query - Change the XXXX to ur new db name (in our example it was "testdb") :
Code:SELECT * INTO SRO_VT_ACCOUNT.dbo._PrivilegedIP from XXXX.dbo._PrivilegedIP
- Restart the mssql server once more , then restart the management studio , and voila
So here we go now , and just to remember , those tips are meant mainly to help newbies , so please no need for such brilliant replies like "useless" or "it's too easy"
press the Thanks button if i helped you out
