diff --git a/db_management/db_premise.rst b/db_management/db_premise.rst index eaa4dcbe8..24841bbfc 100644 --- a/db_management/db_premise.rst +++ b/db_management/db_premise.rst @@ -6,9 +6,171 @@ On-premise Database management ============================== +Register a database +=================== + +To register your database, you just need to enter your Subscription Code in the +banner in the App Switcher. Make sure you do not add extra spaces before or after +your subscription code. If the registration is successful, it will turn green and +will provide you with the Expiration Date of your freshly-registered database. You +can check this Epiration Date in the About menu (Odoo 9) or in the Settings Dashboard +(Odoo 10). + +Registration Error Message +-------------------------- + +If you are unable to register your database, you will likely encounter this +message: + +.. image:: media/error_message_sub_code.png + :align: center + :alt: Something went wrong while registering your database, + you can try again or contact Odoo Help + +Solutions +''''''''' + +* Do you have a valid Enterprise subscription? + + * Check if your subscription details get the tag "In Progress" on + your `Odoo Account + `__ or with your Account Manager + +* Have you already linked a database with your subscription reference? + + * You can link only one database per subscription. + (Need a test or a development database? `Find a partner + `__) + + * You can unlink the old database yourself on your `Odoo Contract + `__ with the button "Unlink database" + + .. image:: media/unlink_single_db.png + :align: center + + + A confirmation message will appear; make sure this is the correct database as + it will be deactivated shortly: + + .. image:: media/unlink_confirm_enterprise_edition.png + :align: center + + +* Do you have the updated version of Odoo 9? + + * From July 2016 onward, Odoo 9 now automatically change the uuid of a + duplicated database; a manual operation is no longer required. + + * If it's not the case, you may have multiple databases sharing the same + UUID. Please check on your `Odoo Contract + `__, a short message will appear + specifying which database is problematic: + + .. image:: media/unlink_db_name_collision.png + :align: center + + + In this case, you need to change the UUID on your test databases to solve this + issue. You will find more information about this in :ref:`this section `. + + For your information, we identify database with UUID. Therefore, each database + should have a distinct UUID to ensure that registration and invoicing proceed + effortlessly for your and for us. + + +Too much users error message +---------------------------- + +If you have more users in your local database than provisionned in your +Odoo Enterprise subscription, you may encounter this message: + +.. image:: media/add_more_users.png + :align: center + :alt: This database will expire in X days, you + have more users than your subscription allows + + +When the message appears you have 30 days before the expiration. +The countdown is updated everyday. + +Solutions +''''''''' + +* **Add more users** on your subscription: follow the link and Validate + the upsell quotation and pay for the extra users. + +or + +* **Deactivate users** as explained in this `Documentation + `__ + and **Reject** the upsell quotation. + +Once your database has the correct number of users, the expiration message +will disappear automatically after a few days, when the next verification occurs. +We understand that it can be a bit frightening to see the countdown, +so you can :ref:`force an Update Notification ` to make the message disappear +right away. + +Database expired error message +------------------------------ + +If your database reaches its expiration date before your renew your subscription, +you will encounter this message: + +.. image:: media/database_expired.png + :align: center + :alt: This database has expired. + + +This **blocking** message appears after a non-blocking message that lasts 30 days. +If you fail to take action before the end of the countdown,database is expires. + +Solutions +''''''''' + +* Renew your subscription: follow the link and renew your subscription - note that + if you wish to pay by Wire Transfer, your subscription will effectively be renewed + only when the payment arrives, which can take a few days. Credit card payments are + processed immediately. +* Contact our `Support `__ + +None of those solutions worked for you? Please contact our +`Support `__ + + +.. _force_ping: + +Force an Update Notification +============================ + +Update Notifications happen once every 7 days and keep your database up-to-date with +your Odoo Enterprise subscription. If you modify your subscription (i.e. add more users, +renew it for a year, etc.), your local database will only be made aware of the change +once every 7 days - this can cause discrepancies between the state of your subscription +and some notifications in your App Switcher. When doing such an operation on your +subscription, you can force an Update using the following procedure: + +1. Connect to the database with the **Administrator** account +2. Switch to the Developer mode by using the **About** option in the + top-right menu (in V9) / in **Settings** (in V10): click on + **Activate the developer mode** +3. Navigate to the "Settings" menu, then "Technical" > "Automation" > + "Scheduled Actions" +4. Find "Update Notification" in the list, click on it, and finally click on the + button "**RUN MANUALLY**" +5. Refresh the page, the "Expiration" notification should be gone + + +.. warning:: You may have kept the same UUID on different databases and we receive + information from those databases too. So please read :ref:`this documentation + ` to know how to change the UUID. + After the change you can force a ping to speed up the verification, + your production database will then be correctly identified. + .. _duplicate_premise: -Duplicating a database +Duplicate a database ====================== You can duplicate your database by accessing the database manager on your @@ -36,128 +198,3 @@ other record by clicking on it and using the edit button. .. image:: media/db_uuid.png :align: center - - - -Register your database -====================== - - -To register your database, you just need to enter your Subscription Code in the -banner in the Appswitcher. - -If you have this error message : **"Something went wrong while registering your -database, you can try again or contact Odoo Help"** - -.. image:: media/error_message_sub_code.png - :align: center - -***Good to check*** - - -* Do you have a valid Enterprise subscription? - * You can check if your subscription details get the tag "in progress" on - your `Odoo Account - ` or with your Account Manager -* Have you already linked a database with your subscription reference? - * You can link only one database per subscription. - ( Need a test or a development database? `Find a partner - `) - * You can unlink the old database yourself on your `Odoo Contract - ` with the button "Unlink database" - -..image:: media/unlink_single_db.png - :align: center - -Don't forget to confirm it - -..image:: media/unlink_confirm_enterprise_edition.png - :align: center - -* Do you have the updated version of Odoo 9? - * From July 2016 onward, Odoo 9 now automatically change the uuid of a - duplicated database; a manual operation is no longer required. - * If it's not the case, you may have multiple databases sharing the same - UUID. Please check on your `Odoo Contract - `. - -..image:: media/unlink_db_name_collision.png - :align: center - -In this case, you need to change the UUID on your test databases to solve this -issue. So please, read the documentation to know `How to duplicate a database -(on-premise) `. - -For your information, we identify database with UUID. - - -Expiration message due to extra users -===================================== - -If you have this error message : **"This database will expire in X days, you -have more users than your subscription allows"** - -..image:: media/add_more_users.jpg - :align: center - -When the message appears you have 30 days before the expiration. -The countdown is updated everyday. - -***Solutions*** - -* Add more users : accept the upsell quotation and pay for the extra users. - -or -* **Deactivate** users as explained in this `Documentation -` -and **Reject** the upsell quotation. - -*Now your database has the correct number of users, the "expiration message" -will disappear automatically after a few days, when the next verification will -be done. We understand that it can be a bit frightening to see the countdown, -so you can force a ping to accelerate the verification* - -***How to force a Ping*** - -1. Connect to the database with the **Administrator** account -2. Switch to the Developer mode by using the **About** option in the -top-right menu (in V9) / in **Settings** (in V10): click on -**Activate the developer mode** -3. Navigate to the "Settings" menu, then "Technical" > "Automation" > -"Scheduled Actions" -4. Find "Update Notification" in the list, click on it, and finally click on the -button "**RUN MANUALLY**" -5. When you refresh the "Expiration" notification should be gone. - - -* Please check if you have correctly duplicated your database. - -*You may have kept the same UUID on different databases and we receive -information from those databases too. So please read the documentation to know -`How to duplicate a database (on-premise) -` and change the UUID. -After the change you can force a ping to accelerate the verification. -Then your production database will be correctly identify.* - -Database expired -================ - -If you have this error message : **"This database has expired, you have more -users than your subscription allows"** - -..image:: media/database_expired.jpg - :align: center - -You had 30 days to take action and now your database is expired. - -***Solutions*** - -* Add more users : follow the link "Add more users" and pay for the extra users. -* Contact our `Support ` - - -None of those solutions worked for you? Please contact our -`Support ` diff --git a/db_management/media/add_more_users.JPG b/db_management/media/add_more_users.JPG deleted file mode 100644 index 6d65a0e97..000000000 Binary files a/db_management/media/add_more_users.JPG and /dev/null differ diff --git a/db_management/media/add_more_users.png b/db_management/media/add_more_users.png new file mode 100644 index 000000000..ddce1cc33 Binary files /dev/null and b/db_management/media/add_more_users.png differ diff --git a/db_management/media/database_expired.JPG b/db_management/media/database_expired.JPG deleted file mode 100644 index 4e46a86ac..000000000 Binary files a/db_management/media/database_expired.JPG and /dev/null differ diff --git a/db_management/media/database_expired.png b/db_management/media/database_expired.png new file mode 100644 index 000000000..b42cfa685 Binary files /dev/null and b/db_management/media/database_expired.png differ diff --git a/db_management/media/error_message_sub_code.JPG b/db_management/media/error_message_sub_code.JPG deleted file mode 100644 index b2fd82e49..000000000 Binary files a/db_management/media/error_message_sub_code.JPG and /dev/null differ diff --git a/db_management/media/error_message_sub_code.png b/db_management/media/error_message_sub_code.png new file mode 100644 index 000000000..8cfec38ad Binary files /dev/null and b/db_management/media/error_message_sub_code.png differ diff --git a/db_management/media/unlink_db_name_collision.png b/db_management/media/unlink_db_name_collision.png index 61362afe6..3e4aa1735 100644 Binary files a/db_management/media/unlink_db_name_collision.png and b/db_management/media/unlink_db_name_collision.png differ diff --git a/db_management/media/unlink_single_db.png b/db_management/media/unlink_single_db.png index 4e1debf01..23210b359 100644 Binary files a/db_management/media/unlink_single_db.png and b/db_management/media/unlink_single_db.png differ