Search Engine: Elastic

Article ID: 122301, created on Jul 9, 2014, last review on Nov 6, 2014

  • Applies to:
  • Business Automation 5.4


During the migration of Parallels Business Automation - Enterprise (PBA-E) to Windows 2008, the second fails with an error that states the script cannot create the pba database because it already exists.

The following error can be found in %PBA_DIR%\tools\tools.log:

[Thu Apr  3 17:03:54 2014] [Call stack]:
[Thu Apr  3 17:03:54 2014]     'helper::msystem' at c:/ProgramFiles/Parallels/PBA/tools/native/ line 534
[Thu Apr  3 17:03:54 2014]     'native::mssql::create_db' at line 336
[Thu Apr  3 17:03:54 2014]     'db::create_db' at c:\Program Files\Parallels\PBA\tools\ line 92
[Thu Apr  3 17:03:54 2014]     'main::configure' at c:\ProgramFiles\Parallels\PBA\tools\ line 79
[Thu Apr  3 17:03:54 2014] PWD: c:/Program Files/Parallels/PBA/tools

In addition, the following error is seen::

[Thu Apr  3 17:04:35 2014] Connect 'dbi:ODBC:pba', bm4
[Thu Apr  3 17:04:35 2014] Couldn't connect to database via configured parameters: DBI connect('pba','bm4',...) failed: [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'bm4'. (SQL-28000) at line 82

It is not clear why is trying to create the pba database as it already exists. The script is supposed to connect to the existing database and reconfigure the destination installation using new IP addresses only.

Cause requires the "SQL Native Client" driver to be installed on the system. The connection to the MSSQL server occurs via DSN, which is configured in:

Administrative Tools > Data Sources (ODBC) > System DSN

If the configuration of DSN is not correct, the connection fails, the script switches to the "new installation" mode, and therefore tries to perform a new installation of PBA-E using DB_HOST IP address from %PBA_DIR%\etc\ssm.conf.d\global.conf.

The issue with an incorrect DSN has two possible causes:

  1. Incorrect MSSQL Server management tools version installed. MSSQL Server 2005 management tools must be installed.

  2. DSN parameters are incorrect (e.g. MSSQL server IP, username, password or database name).


  1. Install MSSQL Server 2005 management tools.
  2. Go Adminitsrative Tools > Data Sources (ODBC) > System DSN, select pba, click Configure and correct the IP address, username, password and database. Perform the same for pba_verify.

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 210d017ddc3a076d22f0f865b1cf0730 92711db0799e8aefe8e51f12dace0496 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF