diff --git a/content/administration/hosting.rst b/content/administration/hosting.rst index 5e308e126..447466e87 100644 --- a/content/administration/hosting.rst +++ b/content/administration/hosting.rst @@ -20,7 +20,7 @@ To Odoo Online - Odoo Online is *not* compatible with **non-standard apps**. - The database's current version must be :doc:`supported `. -#. Create a :ref:`duplicate ` of the database. +#. Create a :ref:`duplicate of the database `. #. In this duplicate, uninstall all **non-standard apps**. #. Use the database manager to grab a *dump with filestore*. #. `Submit a support ticket `_ including the following: diff --git a/content/administration/on_premise.rst b/content/administration/on_premise.rst index 15a5e43e1..ed41335da 100644 --- a/content/administration/on_premise.rst +++ b/content/administration/on_premise.rst @@ -7,159 +7,110 @@ On-premise 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 Expiration Date in the About menu (Odoo 9) or in the Settings Dashboard -(Odoo 10). +To register your database, enter your subscription code in the banner in the app dashboard. If the +registration is successful, the banner will turn green and display the database expiration date. -Registration Error Message --------------------------- +.. tip:: + The expiration date is also displayed at the bottom of the Settings page. -If you are unable to register your database, you will likely encounter this -message: - -.. image:: on_premise/error_message_sub_code.png - :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:: on_premise/unlink_single_db.png - - A confirmation message will appear; make sure this is the correct database as - it will be deactivated shortly: - - .. image:: on_premise/unlink_confirm_enterprise_edition.png - -* 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:: on_premise/unlink_db_name_collision.png - - 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. - -* Check your network and firewall settings - - * The Update notification must be able to reach Odoo's subscription - validation servers. In other words, make sure that the Odoo server is able - to open outgoing connections towards: - - * services.odoo.com on port 443 (or 80) - * services.openerp.com on port 443 (or 80) for older deployments - - * Once you activated your database, you must keep these ports open, as the - Update notification runs once a week. - -Error message due to too many users ------------------------------------ - -If you have more users in your local database than provisionned in your -Odoo Enterprise subscription, you may encounter this message: - -.. image:: on_premise/add_more_users.png - :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. -- **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:: on_premise/database_expired.png - :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, the database is expired. - -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: - -.. _duplicate_premise: +.. _on-premise/duplicate: Duplicate a database ==================== -You can duplicate your database by accessing the database manager on your -server (/web/database/manager). In this page, you can easily -duplicate your database (among other things). +Duplicate a database by accessing the database manager on your server +(`/web/database/manager`). Typically, you want to duplicate your production database +into a neutralized testing database. It can be done by checking the neutralize box when prompted, +which executes all :file:`neutralize.sql` scripts for every installed module. -.. image:: on_premise/db_manager.gif +Common error messages and solutions +=================================== -When you duplicate a local database, it is **strongly** advised to change -the duplicated database's uuid (Unniversally Unique Identifier), since this -uuid is how your database identifies itself with our servers. Having two -databases with the same uuid could result in invoicing problems or registration -problems down the line. +Registration error +------------------ -.. note:: - From July 2016 onward, Odoo 9 now automatically change the uuid of a duplicated database; a - manual operation is no longer required. +In case of a registration error, the following message should be displayed. -The database uuid is currently accessible from the menu :menuselection:`Settings --> Technical --> -System Parameters`, we advise you to use a `uuid generator `_ or to -use the unix command ``uuidgen`` to generate a new uuid. You can then simply replace it like any -other record by clicking on it and using the edit button. +.. image:: on_premise/error-message-sub-code.png + :alt: Database registration error message -.. image:: on_premise/db_uuid.png +To resolve the issue: + +- Check the **validity of your Odoo Enterprise subscription** by verifying if your subscription + details have the tag :guilabel:`In Progress` on your `Odoo Account + `_ or contact your Account Manager. + +- Ensure that **no other database is linked** to the subscription code, as only one database can be + linked per subscription. + + .. tip:: + If a test or a development database is needed, you can :ref:`duplicate a database + `. + +- Verify that **no databases share the same UUID** (Universally Unique Identifier) by opening your + `Odoo Contract `_. If two or more databases share the + same UUID, their name will be displayed. + + .. image:: on_premise/unlink-db-name-collision.png + :alt: Database UUID error message + + If that is the case, manually change the database(s) UUID or `send a support ticket + `_. + +- As the update notification must be able to reach Odoo's subscription validation servers, ensure + your **network and firewall settings** allow the Odoo server to open outgoing connections + towards: + + - `services.odoo.com` on port `443` (or `80`) + - for older deployments, `services.openerp.com` on port `443` (or `80`) + + These ports must be kept open even after registering a database, as the update notification runs + once a week. + +Too many users error +-------------------- + +If you have more users in a local database than provisioned in your Odoo Enterprise subscription, +the following message should be displayed. + +.. image:: on_premise/add-more-users.png + :alt: Too many users on a database error message + +When the message appears, you have 30 days to act before the database expires. The countdown is +updated every day. + +To resolve the issue, either: + +- **Add more users** to your subscription by clicking the :guilabel:`Upgrade your subscription` link + displayed in the message to validate the upsell quotation and pay for the extra users. +- :ref:`Deactivate users ` and **reject** the upsell quotation. + +.. important:: + If you are on a monthly subscription plan, the database will automatically update to reflect the + added user(s). If you are on a yearly or multi-year plan, an expiration banner will appear in the + database. You can create the upsell quotation by clicking the banner to update the subscription + or `send a support ticket `_ to resolve the issue. + +Once your database has the correct number of users, the expiration message disappears automatically +after a few days, when the next verification occurs. + +Database expired error +---------------------- + +If your database expires before you renew your subscription, the following message should be +displayed. + +.. image:: on_premise/database-expired.png + :alt: Database expired error message + +This message appears if you fail to act before the end of the 30-day countdown. + +To resolve the issue, either: + +- Click the :guilabel:`Renew your subscription` link displayed in the message and complete the + process. If you pay by wire transfer, your subscription will be renewed when the payment arrives + which can take a few days. Credit card payments are processed immediately. +- `Send a support ticket `_. .. toctree:: diff --git a/content/administration/on_premise/add-more-users.png b/content/administration/on_premise/add-more-users.png new file mode 100644 index 000000000..a6c607cd7 Binary files /dev/null and b/content/administration/on_premise/add-more-users.png differ diff --git a/content/administration/on_premise/add_more_users.png b/content/administration/on_premise/add_more_users.png deleted file mode 100644 index 4088de604..000000000 Binary files a/content/administration/on_premise/add_more_users.png and /dev/null differ diff --git a/content/administration/on_premise/database_expired.png b/content/administration/on_premise/database-expired.png similarity index 100% rename from content/administration/on_premise/database_expired.png rename to content/administration/on_premise/database-expired.png diff --git a/content/administration/on_premise/db_manager.gif b/content/administration/on_premise/db_manager.gif deleted file mode 100644 index 17e795f55..000000000 Binary files a/content/administration/on_premise/db_manager.gif and /dev/null differ diff --git a/content/administration/on_premise/db_uuid.png b/content/administration/on_premise/db_uuid.png deleted file mode 100644 index 589e063b2..000000000 Binary files a/content/administration/on_premise/db_uuid.png and /dev/null differ diff --git a/content/administration/on_premise/error_message_sub_code.png b/content/administration/on_premise/error-message-sub-code.png similarity index 100% rename from content/administration/on_premise/error_message_sub_code.png rename to content/administration/on_premise/error-message-sub-code.png diff --git a/content/administration/on_premise/unlink_db_name_collision.png b/content/administration/on_premise/unlink-db-name-collision.png similarity index 100% rename from content/administration/on_premise/unlink_db_name_collision.png rename to content/administration/on_premise/unlink-db-name-collision.png diff --git a/content/administration/on_premise/unlink_confirm_enterprise_edition.png b/content/administration/on_premise/unlink_confirm_enterprise_edition.png deleted file mode 100644 index 967fd3f1f..000000000 Binary files a/content/administration/on_premise/unlink_confirm_enterprise_edition.png and /dev/null differ diff --git a/content/administration/on_premise/unlink_single_db.png b/content/administration/on_premise/unlink_single_db.png deleted file mode 100644 index 6188a9437..000000000 Binary files a/content/administration/on_premise/unlink_single_db.png and /dev/null differ