Resolving The Problem

To move an existing ReportNet instance from an existing server to a new one, assuming the content store database is in a central location:

1. Backup the existing server.
2. Install ReportNet in the new server.
3. Configure the new server using Cognos Configuration. Point the content store to the existing database.

To backup your configuration files:

1. Open Cognos Configuration.
2. In the File menu, click Export As.
3. Click Yes to Continue and export and decrypted content.
4. Give the file a name and save it to your hard drive

To backup your project files:

1. Go to your Project storage folder.
2. Select the project(s).
3. Right click and select Copy.
4. Make a backup folder somewhere on your hard drive.
5. Navigate to your backup folder, right click and select Paste.

To backup your Content Store:

1. Open Cognos Connection.
2. Log in as someone with Administrator rights.
3. In the Tools menu, click Deployment.
4. Select the Export tab.
5. Click the New export button.
6. Give the export a name and click Next.
7. Enable Select the entire Content Store as well a Include user account information and click Next.
8. Scroll to the bottom of the Specify a deployment archive and click the Set the encryption password.
9. Supply a password for the export zip file and click OK.
10. Click Next.
11. Click Export Now on the Review the summary page.
12. The default location of this export zip file is <cognos_installation_dir>\crn\deployment

Back up customizations:

If necessary, back up any files that you customized in ReportNet.

For example, the system.xml in the crn\templates\ps\portal directory.

To Install ReportNet on the new Server:

Follow the steps oultined in the Installation and Configuration Guide. There ia also a multimedia KNowedge Base article at:

1012615 - Installing Cognos ReportNet 1.1

To Configure Cognos Configuration in the New Server:

1. Copy the crnstartup.xml from the old server to the new server.
2. Open Cognos Configuration, change Environments to reflect the new server.
3. Check the Data Access, Content Manager. It must be configured to the central content store.