Installation guide

If running this command on a server that will be replaced, and that does not have .NET installed,
you will get a block_named_pipes.exe: not finding the dynamic link library
mscoree.dll error. Ignore this error and continue with the upgrade, since the replacement
server will be running Windows 2008, which installs .NET automatically.
5. At the prompt
Ready to upgrade database to version 6.5.3. Do you want to proceed [y, n]?
Type y to continue.
6. If prompted for the fully qualified host name of the login server, type the fully qualified host
name of the Application Server.
7. When prompted for a report source, if the Connectivity Manager query you ran previously
returned a single value, use that value as the report source. If the query returned multiple values
for the requesting_service field, consult a Connectivity Manager integrator, as mappings may
also need to be changed.
If this Connectivity Manager receives data from multiple report sources, then a few
requesting_service values may exist that match each report source.
8. Respond appropriately to other prompts that appear.
The database is upgraded.
In the IMPAX database, confirm that the values of the requesting_service field match those in the
Connectivity Manager. Open a SQL Server Management Studio query window and type
use mvf;
select distinct requesting_service from dosr_study;
Checking the status of SQL Server upgrades
(Topic number: 9914)
6.
After upgrading the database, check the log file to ensure that the upgrade was successful.
Important!
We recommend checking the migration log file after each leg of an upgrade before moving
on to the next leg.
To check the status of SQL Server upgrades
1. Open the log file C:\mvf-mig6\data\logs\migrate_database_to_IMPAX6.5.3.log.
2. If the following warning appears in the log file, you can safely ignore it:
Warning: The table 'CHANGE_CONTEXT_DETAIL' has been created but its maximum
row size (8095) exceeds the maximum number of bytes per row (8060). INSERT
or UPDATE of a row in this table will fail if the resulting row length exceeds
8060 bytes.
AS300 Upgrade Guide—IMPAX 5.2 or 5.3 to IMPAX 6.5.3 29
Agfa Company Confidential—Subject to Non-Disclosure Obligation