Tyrone Hopes

Instructions for setting up Content Manager using MSDE

Installing MSDE

Before you start, make sure you know the name of your computer EG 'ws06' and that your login has full admin rights for the computer.

Download MSDE - this is downloaded from MSDN website. Use 'save' as the option - this saves the install files to a specified directory - for example c:\msde.
Open a command window (start > run > 'cmd'). Navigate to where the download is: cd c:\msde for example.
Enter at the command prompt 'dir' to check that you are where the setup.exe is. Then enter:
setup.exe /qb+ INSTANCENAME=CM SAPWD=sa DISABLENETWORKPROTOCOLS=0
(this sets the instancename to CM , the password to sa and it is also configured to accept network connections).
Restart your computer after MSDE has been installed. This should (a) start SQL Server and (b) allow you to use osql from the root directory in the command window.
Check MSDE is okay by going to control panel > administrative tools > services and look for MSSQL$CM - it should say 'started'. If not start it with the link. If not in the services list, the install did not work.
The install of MSDE also gives you the osql tool. osql is a method of maintaining databases in MSDE via the command prompt. Get to osql by opening a command window (see above) then type:
osql -E -S servername\CM (servername is your server name )
you will now be at the osql prompt '1>'. Enter the following command: Use master go (it should now be at the '1>' prompt again) Hit enter every time you type in 'GO' (this specifies tosql to execute the command just entered). Enter:
```
CREATE DATABASE content_dc
ON 
( NAME = content_dc_dat,
   FILENAME = 'c:\CM\data\content_dc_dat.mdf',
   SIZE = 10MB,
   MAXSIZE = 50MB,
   FILEGROWTH = 5MB )
LOG ON
( NAME = content_dc_log,
   FILENAME = 'c:\CM\data\content_dc_log.ldf',
   SIZE = 5MB,
   MAXSIZE = 25MB,
   FILEGROWTH = 5MB )
GO
```
Note: it is okay to copy the above then right click in the command window and use paste.
Once the database has been created successfully you get a 2 line message explaining that space has been allocated. After this it is time to populate the database with the database tables. This is done by running another command in osql. Firstly, exit the current osql by entering 'exit' and pressing return. Transfer the script '2007_-5_10_db_script.sql' from the scripts directory (or from the zip file further down on this page) to a directory like c:\tmp
Then enter
osql -E -S servername\CM -d content_dc -i c:\tmp\2007_05_10_db_script.sql
About a whole screen of '1>' or '2>' will appear. This indicates the script is running.
You will be at the DOS prompt of the command window again. Copy the two other scripts to the c:\tmp directory, namely templates.sql and nodes.sql Enter:
osql -E -S servername\CM -d content_dc -i c:\tmp\templates.sql
then enter:
osql -E -S servername\CM -d content_dc -i c:\tmp\nodes.sql

The database is now fully installed.

Installing Content Manager Application

Note that there are a number of prerequisites. Microsoft Windows .NET framework 1.1 needs to be installed (can be obtained from Microsoft's www.msdn.com website. It also requires the Microsoft Installer. However with Windows XP no action is required as it's part of XP. If you're about to install, and you have a zipped package, unzip to a temporary location, then install from there. Also, ensure you are installing with the setup and MSI files on the local machine - not across a network.

Install the new Content Manager program (attached) by clicking on Setup.exe. Follow the prompts. It will create the program in c:\Program Files\GT4 Design\Content Manager
A new shortcut should appear on your desktop which starts the application. You may want to remove any other old shortcuts that went to earlier version of this program.
Configuration: there should be the following layout of directories and files>:
c:\CM which includes:
c:\CM\data and
C:\CM\icons
the icons folder should be populated with 88 objects.
In the c:\data directory should be the two SQL files ending in mdf and ldf, and a further subdirectory - \dc.
This should hold website.xml and a further subdirectory called \images.
The application configuration file should now be set up - I have sent one via email.

The Content Manager application can now run, and should allow the import of Sage products into the Content Manager database.

Troubleshooting

Installation Problems

If there was a problem with the install, uninstall the partially installed program first. This will ensure that the registry is cleared, and a re-install attempt is not going to attempt a 'repair' which does not always work.

You may get the error message "The advertised application will not be installed because it might be unsafe. Contact your administrator to change to installation user interface option of the package to basic". The installer requires the administrator login to work properly; this error message is specifically about machine privileges. If you are working on a network, you must be using a login with local administrator privileges for the computer it is to be installed on. If you are a non Administrator user but with administrator rights this may cause this message to appear. To fix, log off and re install as 'the' administrator.

Content Manager Problems

If you get a 'null exception' immediately upon starting, it is because the application can't find a file it is expecting at a certain location. This is because either it is missing, or because it is being told to look in the wrong location. Usually the problem will be fixed by modifying the CM2.exe.config record parameters, and starting the application again.