2025-02-27 18:56:07 +07:00
|
|
|
---
|
|
|
|
show-content: true
|
|
|
|
---
|
2024-03-04 18:02:08 +07:00
|
|
|
|
2025-02-27 18:56:07 +07:00
|
|
|
# On-premise
|
2016-12-19 20:23:14 +07:00
|
|
|
|
2025-02-27 18:56:07 +07:00
|
|
|
## Register a database
|
2016-12-26 23:08:43 +07:00
|
|
|
|
2024-02-23 03:34:26 +07:00
|
|
|
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.
|
2016-12-26 23:08:43 +07:00
|
|
|
|
2025-02-27 18:56:07 +07:00
|
|
|
:::{tip}
|
|
|
|
The expiration date is also displayed at the bottom of the Settings page.
|
|
|
|
:::
|
2016-12-26 23:08:43 +07:00
|
|
|
|
2025-02-27 18:56:07 +07:00
|
|
|
(on-premise-duplicate)=
|
2016-12-26 23:08:43 +07:00
|
|
|
|
2025-02-27 18:56:07 +07:00
|
|
|
## Duplicate a database
|
2016-12-26 23:08:43 +07:00
|
|
|
|
2024-02-23 03:34:26 +07:00
|
|
|
Duplicate a database by accessing the database manager on your server
|
|
|
|
(`<odoo-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,
|
2025-02-27 18:56:07 +07:00
|
|
|
which executes all {file}`neutralize.sql` scripts for every installed module.
|
2016-12-26 23:08:43 +07:00
|
|
|
|
2025-02-27 18:56:07 +07:00
|
|
|
## Common error messages and solutions
|
2019-02-04 22:55:49 +07:00
|
|
|
|
2025-02-27 18:56:07 +07:00
|
|
|
### Registration error
|
2019-02-04 22:55:49 +07:00
|
|
|
|
2024-02-23 03:34:26 +07:00
|
|
|
In case of a registration error, the following message should be displayed.
|
2019-02-04 22:55:49 +07:00
|
|
|
|
2025-02-27 18:56:07 +07:00
|
|
|
```{image} on_premise/error-message-sub-code.png
|
|
|
|
:alt: Database registration error message
|
|
|
|
```
|
2019-02-04 22:55:49 +07:00
|
|
|
|
2024-02-23 03:34:26 +07:00
|
|
|
To resolve the issue:
|
2016-12-26 23:08:43 +07:00
|
|
|
|
2024-02-23 03:34:26 +07:00
|
|
|
- Check the **validity of your Odoo Enterprise subscription** by verifying if your subscription
|
2025-02-27 18:56:07 +07:00
|
|
|
details have the tag {guilabel}`In Progress` on your [Odoo Account](https://accounts.odoo.com/my/subscription) or contact your Account Manager.
|
2016-12-26 23:08:43 +07:00
|
|
|
|
2024-02-23 03:34:26 +07:00
|
|
|
- Ensure that **no other database is linked** to the subscription code, as only one database can be
|
|
|
|
linked per subscription.
|
2016-12-26 23:08:43 +07:00
|
|
|
|
2025-02-27 18:56:07 +07:00
|
|
|
:::{tip}
|
|
|
|
If a test or a development database is needed, you can {ref}`duplicate a database
|
2025-02-28 03:47:22 +07:00
|
|
|
<on-premise-duplicate>`.
|
2025-02-27 18:56:07 +07:00
|
|
|
:::
|
2016-12-26 23:08:43 +07:00
|
|
|
|
2024-02-23 03:34:26 +07:00
|
|
|
- Verify that **no databases share the same UUID** (Universally Unique Identifier) by opening your
|
2025-02-27 18:56:07 +07:00
|
|
|
[Odoo Contract](https://accounts.odoo.com/my/subscription). If two or more databases share the
|
2024-02-23 03:34:26 +07:00
|
|
|
same UUID, their name will be displayed.
|
2016-12-26 23:08:43 +07:00
|
|
|
|
2025-02-27 18:56:07 +07:00
|
|
|
```{image} on_premise/unlink-db-name-collision.png
|
|
|
|
:alt: Database UUID error message
|
|
|
|
```
|
2016-12-26 23:08:43 +07:00
|
|
|
|
2025-02-27 18:56:07 +07:00
|
|
|
If that is the case, manually change the database(s) UUID or [send a support ticket](https://www.odoo.com/help).
|
2016-12-26 23:08:43 +07:00
|
|
|
|
2024-02-23 03:34:26 +07:00
|
|
|
- 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:
|
2016-12-26 23:08:43 +07:00
|
|
|
|
2024-11-18 21:35:25 +07:00
|
|
|
- Odoo 18.0 and above: `services.odoo.com` on port `80`
|
|
|
|
- Odoo 17.0 and below: `services.openerp.com` on port `80`
|
2016-12-26 23:08:43 +07:00
|
|
|
|
2024-02-23 03:34:26 +07:00
|
|
|
These ports must be kept open even after registering a database, as the update notification runs
|
|
|
|
once a week.
|
2016-12-26 23:08:43 +07:00
|
|
|
|
2025-02-27 18:56:07 +07:00
|
|
|
### Too many users error
|
2016-12-26 23:08:43 +07:00
|
|
|
|
2024-02-23 03:34:26 +07:00
|
|
|
If you have more users in a local database than provisioned in your Odoo Enterprise subscription,
|
|
|
|
the following message should be displayed.
|
2016-12-26 23:08:43 +07:00
|
|
|
|
2025-02-27 18:56:07 +07:00
|
|
|
```{image} on_premise/add-more-users.png
|
|
|
|
:alt: Too many users on a database error message
|
|
|
|
```
|
2016-12-26 23:08:43 +07:00
|
|
|
|
2024-02-23 03:34:26 +07:00
|
|
|
When the message appears, you have 30 days to act before the database expires. The countdown is
|
|
|
|
updated every day.
|
2016-12-26 23:08:43 +07:00
|
|
|
|
2024-02-23 03:34:26 +07:00
|
|
|
To resolve the issue, either:
|
2016-12-26 23:08:43 +07:00
|
|
|
|
2025-02-27 18:56:07 +07:00
|
|
|
- **Add more users** to your subscription by clicking the {guilabel}`Upgrade your subscription` link
|
2024-02-23 03:34:26 +07:00
|
|
|
displayed in the message to validate the upsell quotation and pay for the extra users.
|
2025-02-28 03:47:22 +07:00
|
|
|
- {ref}`Deactivate users <users-deactivate>` and **reject** the upsell quotation.
|
2016-12-26 23:08:43 +07:00
|
|
|
|
2024-02-23 03:34:26 +07:00
|
|
|
Once your database has the correct number of users, the expiration message disappears automatically
|
|
|
|
after a few days, when the next verification occurs.
|
2016-12-19 20:23:14 +07:00
|
|
|
|
2025-02-27 18:56:07 +07:00
|
|
|
### Database expired error
|
2016-12-19 20:23:14 +07:00
|
|
|
|
2024-02-23 03:34:26 +07:00
|
|
|
If your database expires before you renew your subscription, the following message should be
|
|
|
|
displayed.
|
2016-12-19 20:23:14 +07:00
|
|
|
|
2025-02-27 18:56:07 +07:00
|
|
|
```{image} on_premise/database-expired.png
|
|
|
|
:alt: Database expired error message
|
|
|
|
```
|
2016-12-19 20:23:14 +07:00
|
|
|
|
2024-02-23 03:34:26 +07:00
|
|
|
This message appears if you fail to act before the end of the 30-day countdown.
|
2016-12-19 20:23:14 +07:00
|
|
|
|
2024-02-23 03:34:26 +07:00
|
|
|
To resolve the issue, either:
|
2016-12-19 20:23:14 +07:00
|
|
|
|
2025-02-27 18:56:07 +07:00
|
|
|
- Click the {guilabel}`Renew your subscription` link displayed in the message and complete the
|
2024-02-23 03:34:26 +07:00
|
|
|
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.
|
2025-02-27 18:56:07 +07:00
|
|
|
- [Send a support ticket](https://www.odoo.com/help).
|
|
|
|
|
|
|
|
```{toctree}
|
|
|
|
on_premise/packages
|
|
|
|
on_premise/source
|
|
|
|
on_premise/update
|
|
|
|
on_premise/deploy
|
|
|
|
on_premise/email_gateway
|
|
|
|
on_premise/geo_ip
|
|
|
|
on_premise/community_to_enterprise
|
|
|
|
```
|
2024-03-04 18:02:08 +07:00
|
|
|
|