Jump to content

Search the Community

Showing results for tags '2.8.10'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Using and Managing Revive Adserver
    • Documentation
    • Using Revive Adserver
    • Managing Revive Adserver
    • Bugs
  • Advanced Topics
    • Performance, Scalability, and Reliability
    • For Developers
  • Revive Adserver Community
    • Revive Adserver Project News and Announcements
    • Feature Requests
    • Plugins
    • Requests for Consulting
    • Off Topic

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL

Found 1 result

  1. Hello one more time. Finally, I've solved the task of upgrading of my adserver. But there were some strange behaviour: after running the upgrade wizard on step 2 of "Performing the Upgrade" section this article http://www.revive-adserver.com/support/upgrading/ I saw this message: But this is very strange, because I got 2.8.10 and I should see some upgrade steps like in article. My actions were: 1) Backups. 2) Unpack revive-adserver-3.0.2.tar.gz and rename it to "ox_new" (2.8.10 is in "ox" directory). 3) Make new db and user for it. 4) Fill new db with backup of old one (2.8.10). My tables got prefixes "ox_". 5) Copy config file from 2.8.10 to 3.0.2 Changed db information in it (user, pass, db name). In other attempt I've also changed the [webpath] section (admin, delivery, deliverySSL) because after running the upgrade I was redirected to old "ox" folder. 6) Run url with .../ox_new in the end and see the message I've write above. Without any mistakes or stranges. Is this behaviour weird or normal? In the admin panel of upgraded adserver I see all my zones and banners, but there are no new stat for about 3 hours after the upgrade? How I could detect if my new server is broken?
×
×
  • Create New...