NaviEdit Version 7 Installation guide

NaviEdit Version 7 Installation guide

NaviEdit Installation Guide Page 2 Contents 1Revision History 3 2Dictionary 4 3Installation procedure 4 3.1Install Microsoft SQL Server 7.0 4 3.1.1Install SQL Server 7.0 Prerequisites (for NT 4.0) 4 3.1.2Install SQL Server 7.0 Components 4 3.2Install Microsoft SQL Server 2000 5 3.2.1Local installation on Windows NT4/2000/XP workstation edition 5 3.2.2Local installation on Windows NT4/2000 server edition 5 3.2.3Client installation. 5 3.3Install WIBU-Key (Drivers for the dongle protection) 6 3.3.1Run the WIBU-Key Installation 6 3.4Local installation 6 3.4.1Preparing for the installation. 6 3.4.2Run the NaviEdit Setup program 6 3.5Client/Server installation 7 3.5.1Restrictions in client/server configuration 7 3.5.2Server configuration 7 3.5.3Client configuration 7 4Setting up ODBC data connection 8 4.1Create a ODBC DSN 8 4.2Select the SQL Server to connect to (local if same computer) and Next 9 4.3Select NT authentication 9 4.4Select database. 10 4.5Test connection 10 5Troubleshooting 11 5.1JobPlanner fails to start 11 5.1.1SQL Server service is stopped 11 5.1.2Database missing 12

1 REVISION HISTORY NaviEdit Installation Guide Page 3 Initials Date Comments Kup 18.02.2000 Document created Kup 03.03.2000 Beta release of NE7.0 Kup 14.03.2000 Beta2 release of NE7.0. Added client-server installation section Kup 5.04.2000 Rel. 7.03 Srm 9.05.2000 Added more detailed description of server/client setup Srm 2.10.2000 Changed server/client part to use new BULK interface.. Kup 09.10.2000 7.2.0 release: Update to newest database version (7.0.0.3) Kup 02.11.2000 Trouble Shooting section defined Kup 14.12.200 Installation of NE on SQL Server 2000: Use client installation Srm 20.12.2000 Installation types changed Jbl 03.01.2001 SQL Server 2000 section updated JBL 23.03.2001 SQL Server 2000 Demo installation type added, updated section 3.4.2 JBL 19.12.2001 Updated to reflect new JobPlanner features JBL 08.10.2002 Release of 7.3.1. JBL 06.11.2003 7.3.7 Released HKP 13.11.2007 Extended client-server section with win xp precautions HKP 20.11.2007 Added several SQL servers section HKP 16.01.2008 New logo HKP 23.01.2008 Added SQL Server 2005 troubleshooting HKP 05.03.2008 Client/server no blank password

2 DICTIONARY OBDC=Open DataBase Connectivity DSN=Data Source Name SQL=Structured Query Language NaviEdit Installation Guide Page 4 3 INSTALLATION PROCEDURE 3.1 Install Microsoft SQL Server 7.0 If you have purchased SQL Server 2000, please proceed to section 3.2. 3.1.1 Install SQL Server 7.0 Prerequisites (for NT 4.0) The SQL Server 7.0 requires: SP 3.0->5 Internet Explorer 4.01 (found on SQL Server CD under prerequisites) 3.1.2 Install SQL Server 7.0 Components Select Database Server Desktop Edition in the first step. Select Local install in the second step, if the prerequisites have not been fulfilled you will be told after this. The install wizard starts. Step: click next. Step: Accept and click next. Step: Enter the serial number and click next. Step: Select typical and click next. Step: Select Use the same account for all services. Auto start SQL Server Service, select Use the Local system account. Click next. Step: Click next.

NaviEdit Installation Guide Page 5 3.2 Install Microsoft SQL Server 2000 3.2.1 Local installation on Windows NT4/2000/XP workstation edition Start Setup.exe and choose: Install SQL Server 2000 Components Personal Edition Database Server - Personal Edition (installation starts) Local Computer Create a new instance of SQL Server Server and Client Tools Check Default as Instance name Choose typical installation Use the same account for each service. Autostart SQL Server Service. Use local system account Windows authentication mode 3.2.2 Local installation on Windows NT4/2000 server edition Start Setup.exe and choose: Install SQL Server 2000 Components Standard Edition Database Server - Standard Edition (installation starts) Choose typical installation Autostart SQL Server Service Use local system account Windows authentication mode 3.2.3 Client installation. Start Setup.exe and choose: Install SQL Server 2000 Components Personal Edition Database Server - Personal Edition (installation starts) Local Computer Create a new instance of SQL Server Client Tools Only See section 3.5 for further instructions.

NaviEdit Installation Guide Page 6 3.3 Install WIBU-Key (Drivers for the dongle protection) 3.3.1 Run the WIBU-Key Installation Should not be necessary, since it should be auto started during installation. But if this fails, follow this procedure to install the drivers manually: 1. Start windows explorer. 2. Browse to the folder: <CDDRIVE>:\WIBU-KEY Installation on the installation CD. 3. Run Setup32.exe, to install the drivers. 4. Proceed with the NaviEdit installation. 3.4 Local installation Make sure that you are logged in as Administrator 3.4.1 Preparing for the installation. If you have the following scenario, then do not run the uninstall procedure from the control panel: NaviEdit 7.2.7 or earlier installed The database was created during installation Cause: During the uninstall procedure the database files, initially created during installation, are deleted, which could result in loss of data. This problem has been solved in versions 7.2.8 or later (CD-release). 3.4.2 Run the NaviEdit Setup program 1. Click next. 2. Accept the default path by clicking next. 3. You have 5 choices: Client (Using remote database): Only updates (installs) all the NaviEdit programs. Local (Creating demo SQL Server 2000 database): Installs the NaviEdit programs and creates a database with demo data. Local (Creating demo SQL Server 7.0 database): Installs the NaviEdit programs and creates a database with demo data. Local (Creating empty SQL Server 2000 database): Installs the NaviEdit programs and creates an empty database. Local (Creating empty SQL Server 7.0 database): Installs the NaviEdit programs and creates an empty. Upgrade existing: Only updates (installs) all the NaviEdit programs. 4. Make sure you choose an installation that matches the type of SQL Server installed. 5. When you click next the installation starts. After the installation the PC should Re-start. You might have to close the JobPlanner, which start during the installation.

NaviEdit Installation Guide Page 7 3.5 Client/Server installation Installing NaviEdit client on separate machines using a shared instance of SQL Server. In this section server or server pc refers to the computer where the SQL Server is installed, and the database-files are located. The term client or client pc refers to the computer connecting to the server pc, where the SQL Server is installed. The client needs to connect to a SQL Server. In this client/server setup the client connects to the SQL Server installed on the server pc. However the client itself might also have a SQL Server installed. In the case of both a remote and local SQL Server, it is defined by the ODBC connection whether the local or the remote SQL Server is used. The NaviEdit dongle must be attached to the client pc. 3.5.1 Restrictions in client/server configuration Some of the database management features are limited for use from a remote client. The following restrictions apply to any client connected to a remote NaviEdit database: The Create/Delete/Detach/Attach functions only works on the locally installed SQL Server (if any) Switch database ( Set Current function): can only switch from a remote database to a local database. (See section 4 for instructions) This imply that a new database must be created on the server by means of the JobPlanner on the server pc. 3.5.2 Common configuration To enable windows authentication the client side windows user should also be setup on the server with the same user name as on the client. The password must be identical on the client and the server. The user should have adequate access rights. Preferably the user should be Computer Administrator on both client and server. A non-empty password is required. 3.5.3 Server configuration 1. Install MS SQL Server on the server computer. 2. Install NaviEdit on the server computer (any setup type). 3. Create or attach new NaviEdit database on the server. Use the JobPlanner features from the File Database menu or refer to the Howto section in the online help for the JobPlanner. Note, when attaching database files to the SQL Server, the database files must be on a local file system on the server, i.e. it is not possible to attach a file like \\someserver\some-path\navieditdb.mdf. Ensure TCP/IP is enabled as network protocol.

NaviEdit Installation Guide Page 8 For the MSDE 2000 SQL Server included on the EIVA installation CD, this can be checked/setup by calling svrnetcn.exe from a command line. This would give you the following screen shoot: Any changes in the enabled protocols require a restart of the MS SQL Server. 3.5.3.1 A special note for servers running Windows XP Two security settings in Windows XP must be changed. 1. The firewall should be change to allow traffic on the ports used by the ODBC connection. The default ports are 1433 and 1434. The Windows XP firewall can be changed from Control Panel, Windows Firewall. By adding the ports 1433 and 1434 on the Exceptions tab these ports are open for connection. 2. Windows XP has as default setting a security policy enabled that translates all network connections to the Guest account. This setting will disable the windows authentication used by the ODBC connection. To correct this, go to Start, run, and enter gpedit.msc. Navigate to the Network access: Sharing and security model for local accounts and change the default value from Guest only local users authenticate as Guest to Classic local users authenticate as themselves :

NaviEdit Installation Guide Page 9 3.5.4 Client configuration 1. Make sure the client has a dongle installed (including software Wibukey). (See 3.2). 2. Create an ODBC DSN named LocalSQLServer pointing to the remote NaviEdit database. (See section 4 for instructions). 3. Install NaviEdit7.x on the client(s) using client installation. NaviEdit defaults to an ODBC DSN named LocalSQLServer, this name might be slightly misleading for a client/server setup. This ODBC DSN LocalSQLServer can either be changed, so it points to the remote SQL Server, or a new ODBC DSN could be made. 3.5.5 Several SQL Servers In a setup where several SQL Servers are used, bat-files could be made to control which server to access. The first of the following two bat-files will create a DSN named LocalSQLServer and point it to a database named NaviEditDB on the local host, and start NaviEdit using this connection. The second bat-file will create a DSN named RemoteSQLServer and point it to a database named RemoteDataBaseName on the server RemoteServerName, and start NaviEdit using this connection. NaviEditLocal.bat: C:\EIVA\NaviEdit\bin\JobPlanner.exe -d -r LocalSQLServer NaviEditDB (local) START C:\EIVA\NaviEdit\bin\JobPlanner.exe exit

NaviEdit Installation Guide Page 10 NaviEditServer.bat: C:\EIVA\NaviEdit\bin\JobPlanner.exe -d -r RemoteSQLServer RemoteDataBaseName RemoteServerName START C:\EIVA\NaviEdit\bin\JobPlanner.exe exit 4 SETTING UP ODBC DATA CONNECTION Follow this procedure to set-up a connection to a NaviEdit database from a SQL Server instance. The illustrations in this guide are from a Windows NT 4 environment. 4.1 Create a ODBC DSN In Start menu: Select Control Panel, Data Sources (ODBC). In newer versions of windows, the ODBC settings are found under Control Panel-Administrative Tools Next open it and see System DSN that a LocalSQLServer is defined. If not add a new and Configure.

NaviEdit Installation Guide Page 11 4.2 Select the SQL Server to connect to (local if same computer) and Next 4.3 Select NT authentication

4.4 Select database. NaviEditDB is used in this example. NaviEdit Installation Guide Page 12 4.5 Test connection And a result like below should appear:

5 TROUBLESHOOTING NaviEdit Installation Guide Page 13 5.1 JobPlanner fails to start 5.1.1 SQL Server service is stopped If you receive the following message at start up the SQL Server service might not be running. Solution: Start the SQL Server service: 1. Locate the service manager in the system tray: 2. Right-click and choose MSSQLServer Start. 3. Alternatively open the service manager and start the SQL Server from here. Make sure the Auto-start service when OS start checkbox is checked.

5.1.2 Database missing NaviEdit Installation Guide Page 14 If one of the following messages appears during start up, first make sure the SQL Server service is running. The messages can appear from the following reasons: The SQL Server was not started during the NaviEdit install procedure causing the initial database creation to fail. The windows user login is different from the login used to install NaviEdit The database was detached or deleted from another program than JobPlanner. Solution: Dismiss all messages until the following dialog appears:

NaviEdit Installation Guide Page 15 If the database for NaviEdit is in the list. Select it and press the button Set current. Then press Close. Possibly restart JobPlanner. If no database is present, either create an empty one ( New... ) or attach an existing database ( Attach ). When creating or attaching a new database, check the Use as default box. Then press Close. Possibly restart JobPlanner. If you wish to connect to a remote database please follow the instructions in Section 4. 5.1.3 Attaching a SQL Server 2005 database to a SQL Server 2000 It is not possible to attach a SQL Server 2005 database to a SQL Server 2000. If you try you will get an error message like this one: 5.1.4 SQL Server 2005 Express and very slow NaviEdit If NaviEdit is very slow. It could be caused by a default configuration in the Microsoft SQL Server 2005. A symptom of the problem could be that the updating of min KP and max KP in JobPlanner is very slow, even though the sqlserver-process in the TaskManager only is using a few percentages of the CPU power. To change the default value of the SQL Server 2005, start the SQL Server Configuration Manager (shown below on a Windows Vista computer)

NaviEdit Installation Guide Page 16 Enable the TCP/IP protocol and disable all other protocols for both the SQL Server 2005 Network Configuration and the SQL Native Client Configuration.

NaviEdit Installation Guide Page 17