Richard Cook
-
Posts
6 -
Joined
-
Last visited
Posts posted by Richard Cook
-
-
@Matteo Beccati I have artifcats going back to 2.0.11.
Name From Version To Version Status Date 2007-11-14 09:31:58 2.0.11-pr1 2.3.32-beta upgrade complete 2007-11-14 09:31:58 -
Hi @andrewatfornax,
That log was from my 4.0.1 to 4.0.2 upgrade.
The log after that, is from 4.0.2 to 4.1, which does not show the acknowledgement that it found 4.0.2.
From the install.log file for 4.1 (failed attempt):
Attempting to detect an existing Revive Adserver installation...
schema file found: -----------/etc/changes/schema_tables_core_621.xml
-
Sorry, I meant upgrading to 4.1, not 4.3 as I wrote in my previous posts.
Rich
-
I noticed in the log that it does not acknowledge that it found a previous installation of Revive Ad server. Could this be part of the issue?
From the install.log file for 4.3 (failed attempt):
Attempting to detect an existing Revive Adserver installation...
schema file found: -----------/etc/changes/schema_tables_core_621.xml
From the install.log file for 4.0.2 (successful)
Attempting to detect an existing Revive Adserver installation...
Revive Adserver 4.0.1 detected
This version can be upgraded
Database settings and permissions are OK
-
I'm having the exact same issue.
I updated to 4.0.2 2 months ago, with no errors.
Trying to update to 4.3 I get the same exact error messages regarding DB integrity.
=========================================================================
Attempting to detect an existing Openads (aka. phpAdsNew) installation...
PAN not detected
Attempting to detect an existing Openads (aka. Max Media Manager 0.1) installation...
MMM v0.1 not detected
Attempting to detect an existing Openads (aka. Max Media Manager 0.3) installation...
MMM v0.3 not detected
Attempting to detect an existing Revive Adserver installation...
schema file found: -----------/etc/changes/schema_tables_core_621.xml
schema definition from cache TRUE
successfully parsed the schema
schema name: openads
schema version: 621
schema status: final
running integrity check
comparing database ---------- with schema ----------/etc/changes/schema_tables_core_621.xml
column definition does not match: account_preference_assoc.account_id
[... similar info, see previous posts ...]
Issue upgrading from 4.0.2 to 4.1.0
in Managing Revive Adserver
Posted
I upgraded using 4.1.1. I got no errors during the upgrade process.
When I go to the product upgrade screen to view the version number I see.
You are currently using Revive Adserver v4.0.2 (warning: database is stamped as v4.1.1)
Rich