This article describes how you upgrade to the latest ScriptServer Components.

Vefore starting, ensure that you have valid license files at hand. The new components require the new license file format which means that instead of having the w3ss.lic and optionaly tp.lic you will only have one file named license.bin.

1. Backup your database and your files
2. Stop your IIS from the command prompt with the following command:
   net stop iisadmin
3. Stop the ScriptServer service which allows domain log ons with the following command:
   net stop w3ntlogon
4. Uninstall the existing ScriptServer components from the Control Panel - Add/Remove Programs
5. Install the new ScriptServer components from the ScriptServer installation CD
6. Update your ScriptServer tools (usally resides in c:\scriptserver\tools) with the latest tools
7. Use MS SQL Query Analyzer and for each existing ScriptServer site on this server, connect to their respective SQL Server and database and execute the statement in the attached file.
8. Again for each database, execute the following SQL statement:
   EXEC [dbo].[Tools_GrantScriptServerPublicAccountPermissions] @PublicAccountName = ' APPNAMEPublic'
   Replace APPNAMEPublic with the respective public login for each database.
9. Place the new license files (called license.bin) in each respective site's home directory. Make sure that file permissions are set to allow the Everyone account READ permissions.
10. Start the web service and the lgon service again:
    net start w3ntlogon
    net start iisadmin
    net start w3svc
    And possibly
    net start smtpsvc
    net start msftpsvc
11. Everything should be up and running now, so check your websites to make sure.

To prepare for easier updates in the future you should also perform the following steps.For each ScriptServer website, ensure that it has its own copy of the /systemImages folder. In some older installations all sites will share the systemImages folder.

1. Copy the c:\scriptserver\files\systemimages into each site's home directory IF it isn't already there.
2. Remap the SystemImages IIS Virtual directory for each ScriptServer site to point to each respective SystemImage folder instead of the shared folder.

Troubleshooting

If you are running older versions of TradePoint you will need to manually register the TPext.dll component. Do this by following these steps:

1. Downloading and extract the attached TPExt file
2. Copy TPext.dll to c:\scriptserver\bin (or wherever you have installed your ScriptServer)
3. Open the command prompt, navigate to the folder above and execute regsvr32 tpext.dll