Translations by Victor Yu

In this case, check if the service ``postgresql-9.0 - PostgreSQL Server 9.0`` is running in the Services Manager (:menuselection:`Control Panel --> System and Security --> Administrative Tools --> Services`).

*PostgreSQL 9.0 in the Services list*

You can edit the service configuration to start PostgreSQL as a service on system boot. This is usually the default.

*Configure PostgreSQL 9.0 service*

*Restarting the service*

To initialize the server with configurations of your choice, you have to invoke it at the Windows Command prompt with the options you wish to override.

``-d <db_name>`` : Name of the database created for OpenERP Server.

``-r <db_user>`` : Name of the PostgreSQL user (role).

``--db_host=<postgresql_server_address>`` : Address of the server where PostgreSQL is. If you have installed PostgreSQL on the same computer as OpenERP Server, you can enter ``localhost``, else, the IP address or the name of the distant server.

Before the execution of this command you have to decide the purpose of the database created in OpenERP.

Sample command: ::

Here you have to enter the username and password specified in the PostgreSQL connection configuration during server installation.

When you execute the initialization command, if you specify a logfile, the server runtime output is written to that file, and you will not see any server output in the prompt window. You have only to wait until the prompt comes back.

You can initialize the database with OpenERP Server to:

Take a look at the system with modules installed and demo data loaded

If you execute the sample command above, you will get a database with only base modules installed and loaded with demo data. To initialize OpenERP Server with additional modules and its demo data, you need to add this option to the above command: ::

This command will initialize the OpenERP Server with the module :mod:`sale` and its dependencies, and fill its PostgreSQL database with their related demo data. As can be seen, you must specify the target database for the module installation.

To install more than one module, specify a comma-separated module list at the command-line.

Execute the command with an option excluding the demo data: ::

This will load base modules (and other modules if -i option is used), but will not load its demo data.

Sample command usage: ::

Execute the command with an option that updates the data structures: ::

The service and some runtime information is accessible through the Computer Management console in Administrative Tools.

*Recovery tab to set service failure response*

The Computer Management logging service offers additional information about the execution of the OpenERP Server, for example, the startup or shutdown information of the service.

*Server information in Windows Logs list*

*OpenERP Server log file*

*The services in Windows Task Manager*

For more information, please take a look at :ref:`Additional Installation Information and Troubleshooting <troubleshooting-and-windows-complementary-install-information>`, where you can find some troubleshooting examples.

OpenERP Server (Windows)

Of course you should always test these updates on a staging environment (copy of your production environment) before actually applying them on the real production systems.

Stop the OpenERP server and the Web Server (if present).

Update the source files to the latest release, or simply install the new releases over the previous ones. If need be, you can uninstall the previous version, but be sure to avoid uninstalling PostgreSQL, as this could delete your current databases!

Locate the separate server executable ``openerp-server.exe`` (this is not the executable used by the Windows Service!). It should be in the location where you installed OpenERP Server, for example in ``C:\Programs\OpenERP 6.0\Server``.

From a Command-Line Prompt, start the server executable manually (directly call the executable you located above), with the following parameters, to trigger an update of all module data and views in the database, based on the new source files (include your usual startup parameters, if any, and replace ``DB_NAME`` with the name of the OpenERP database you wish to update)::

Let the server complete its startup (watch the log file for the final message that says ``OpenERP server is running, waiting for connections`` or wait until you can connect to that database with a GTK client), then stop the server using the :kbd:`Ctrl+C` key combination and repeat previous step for each database on this OpenERP installation (any database not updated will use the latest business logic but might have errors or missing improvements in the views until you update it using this procedure).

Stop the server again with :kbd:`Ctrl+C` and restart it normally as a service.

You can now proceed with the update of the GTK clients, which can be done separately by simply reinstalling the latest version over the previous one.

As an alternative to restarting the server in update mode for each database, as described above, you may try to start the server normally after installing the new version, and then connect to each database as the *Administrator* user, open the list of modules and manually trigger an update of the *base* module.

Because all modules depend on *base* they will be updated too. However this requires the *Administrator* password of each database and may not work for some updates, specifically when the update prevents you from logging into the system.

OpenERP's release policy states that one or two major releases are published from the development version every year. Transitioning to the next major release implies a lot more changes than jumping to another minor release. As the underlying OpenERP data structures usually evolve quite a bit from one major release to the next, a full migration of the existing data is needed. Each major release will be published with specific recommendations and procedures for upgrading an existing OpenERP system to the next major version.

Major Release

For major releases, it is usually not possible to skip one release, for example upgrading directly from OpenERP 4.2 to OpenERP 6.0. If you need to do such an upgrade, you will simply have to do each intermediary upgrade one after the other.

Upgrade; OpenERP (Windows)

OpenERP Web (Windows)