- 19 Mar 2024
- 4 Minutes to read
- Print
- DarkLight
- PDF
Manual Install of the Pharos Database
- Updated on 19 Mar 2024
- 4 Minutes to read
- Print
- DarkLight
- PDF
Goal: Manually Install the Pharos Database for Uniprint 8.3 and greater.
Details:
Installation Overview
Obtain the database install files
Create a Database and Database Login in SQL Server
Manually install the Pharos Database
Install the other Principal Server components
Configure Microsoft Server to control the Pharos services
Test the configuration
Install other Pharos services (optional)
Each procedure is detailed below.
1. Obtain the database install files
A number of files are required for a manual installation of the Pharos Database:
dbinst.sql and p3static.sql – these files are located on the Pharos CD in the database\db directory.DatabaseRegistryShell.x86.reg or DatabaseRegistryShell.x64.reg depending on the architecture of your server – (attached)
Your license information file – this is the text file supplied with your Pharos license.
Copy these files to the Server.
2. Create a Database and Database Login in SQL Server
To create a database, follow these steps using SQL Server Enterprise Manager:
Expand a server group, then expand the server.
Right-click Databases, then click New Database.
On the General tab, enter a name for the new database. This will usually be “pharos”. The default settings on the Data Files tab and Transaction Log tab are correct for a Pharos installation.
Click OK to create the new database.
**********************************************************************************************************************************************************************************
To add a login for the database, follow these steps using SQL Server Query Analyzer:
Start SQL Server Query Analyzer.
Log on as the 'sa' database user and make sure that the connection is against the master database.
Enter the following query into the query window:
Where:
use master
exec sp_addlogin @loginame = '<loginame>', @passwd = '<pwd>'
go
use <dbname>
exec sp_changedbowner @loginame = '<loginame>'
go
exec sp_defaultdb @loginame = '<loginame>', @defdb = '<dbname>'
go
• <dbname> is the name of the database you just created.
• <loginame> and <pwd> are the new login name and password for the database.Execute the query.
**********************************************************************************************************************************************************************************
Before Continuing you need to check the collation SQL setting
Run the Query below
select name, collation_name, compatibility_level from sys.databases
select serverproperty('Collation')
Write down the name of the collation and when you create the Pharos database you need to make sure it has the same collation setting.
**********************************************************************************************************************************************************************************
3. Manually install the Pharos Database
Start SQL Server Query Analyzer.
Log on as the Pharos Database user, using the user name and password you created previously. (If SQL Query Analyzer is still open, select Connect from the File menu to log on with the new details.)
Ensure that the Pharos Database is selected as the current database.
Open the file dbinst.sql (File menu > Open) and execute it. This file can be found under the \database\db folder on your Pharos CD. This may take a moment to run. Make sure there are no errors (“Query batch completed” should appear in the status bar at the bottom of the window).
Open and execute the file p3static.sql in SQL Server Query Analyzer.
Update the system table in the database with your license details. To do this, execute the following query in SQL Query Analyzer: Replace <sitename> with your site name and <clientcode> with your client code. This information can be found in your license information file (the text file supplied with your Pharos license key). The first two lines of this file contain your site name (after “Licensed to =”) and client code (after “Client code =”). Once the modifications are made, execute the query.
update system set licenced_to = '<sitename>', license_quick_key = '<clientcode>'
The Pharos Database is now installed.
4. Install the other Principal Server components
The servers can be installed with the standard setup program on the Pharos CD, but the registry on each node must be modified first so that the Pharos installers are aware that the database has been installed, and can access the name of the Server where database has just been installed.
To modify the registry, perform the following steps on each node:
Copy the registry file DatabaseRegistryShell.reg onto the node.
Open this file with a text editor, e.g. Notepad.
Make sure that the “Database Name”, “Password” and “User Name” values are the same as the values you created in step 2 above.
Replace the value of “Server Name” with the name of the virtual server running SQL Server.
Make sure that the “Pharos Database” value contains the build number of your release of Pharos (you can see the build number on the title bar of the first dialog that appears when you run Setup.exe on the Pharos CD).
Close the text editor and execute the registry file by double-clicking on it.
You can now run the Pharos setup program to install the Principal Server. Choose ‘Principal Server’ on the Select Role screen, then select all components on the Select Components screen (the Pharos Database should not be available for installation). When prompted for the SQL Server Machine Name, type in the name of the server running SQL Server. The installation of the services should proceed normally, with one exception: the second time you install the Distribution Service, an error message will appear, due to the fact that the installers attempt to insert an entry for a second Distribution Service into the Pharos Database, when there can only ever be one. This error message can be safely ignored.