Installation troubleshooting

From Dragon Age Toolset Wiki
Jump to: navigation, search

NOTE: version 1.00 had a problem with installing to directories with paths longer than 58 characters, which is the default for Steam installations. 1.01 overcomes this problem, and fixes several other important bugs, but if for some reason you wish to install 1.00 see Installation with Steam for details and a workaround.

Refer to Known issues for the current list of issues that are being worked on, and their status.

See Installing the toolset for general information and guidance about installing the Dragon Age toolset. If something goes wrong during that process this page may have useful information and advice.

If you experience a crash, logs can be found in My Documents\BioWare\Dragon Age\Toolset\logs. The log filenames will include the date on which the log file was created. Sending in a log will help greatly with bug fixing.

General errors

If the Dragon Age toolset downloads to near-completion, but you then get the error "[browser] cannot download, etc. Connection with the server was reset", this may be due to a downloading management issue. One solution is to first download an internet download manager (IDM) freeware program (e.g. Then, once the IDM is installed and in control of your downloads, retry downloading the DA toolset through your default browser.

If you get the "Dragon Age: Origins game install not found" error when you run the toolset installer:

  • You must have the game installed before you can install the toolset. Please install the game first.
  • If you have installed the game, but not yet run the configure program, you will get this message: "Please launch the Dragon Age: Origins Configure Utility". This happens automatically the first time you attempt to run the game. After you have successfully configured and launched the game at least once, you should no longer get this error.

If the toolset cannot find DLLs you may need to run the configuration tool after installation to tell the toolset where to find the Dragon Age build. This can happen if you uninstall the toolset and then reinstall it again in a different location.

If you install the toolset in a non-default location, the toolset may not be made aware of where the Resource Builder has been put. This can be easily fixed by changing the "Resource Build Path" variable found in Options->Environment.

On Vista and Windows 7 systems you may get a message reading "Windows has blocked some of the features of this program." It will indicate that the offending program is "Microsoft Register Server", located at C:\windows\system32\regsvr32.exe. The installer makes use of this program to register the game engine's DLL for use by the toolset. You can choose to block or allow this, the installer will work either way. It is somewhat safer to leave it blocked.

On Windows 7 64 bit you may experience this error durring the installation of the toolset. Error opening File or Writing:

C:\Program Files\Common Files\BioWare\Uninstall Dragon Age Toolset.exe

Click Abort to stop the installation, Retry to try again, or Ignore to skip the file.

The work around for this is to either create the folder "BioWare" in the directory of C:\Program Files\Common Files\ prior to the installation or at the point where the error is experienced. This is due to the installation program not creating the folder "BioWare" in the C:\Program Files (x86)\Common Files. Once this "BioWare" folder is created the installation will complete by clicking on "retry".

MSSQL Express 2005's installer has a limitation that prevents it from installing to a directory path that's longer than 58 characters.[1] Version 1.01 of the toolset installer has addressed this issue by installing the database to a predefined location independant of the location of the game executable.

Empty Palette Window

If after succesful launching of toolset, your window palette is empty, probably the problem is the default language not set to "English" in your DataBase properties:

  • to change it launch Microsoft SQLServer Management Studio Express 2005 (this is covered in Manual database installation)
  • in the Database tree, choose "Security" (translate it in your language)
  • then choose something like, "accounts" or "logins", then you should see a list of users, including your windows user
  • right click on your username and choose "properties"
  • at bottom right of the window that pop up locate "Default Language" and change it in "English"
  • click "ok" button

Now the empty palette window should show the resources. Thanks to Vreltek for this solution!

"Unable to connect to the database"

If you receive the "unable to connect to the database" error message there are many reasons why this happens, and various ways to correct it.

A new troubleshooting page for this error has been created. Rather than random suggestions of things to try, it has a troubleshooting flowchart to help you diagnose and fix your problem. Please visit Unable to connect to the database for the latest help with this problem.

Installer hangs at the stage of "Execute:regsvr32.exe /s "C:\Dragon Age\tools\Engine.dll"

In some instances Regsvr32.exe is failing for some unknown reason and refusing to terminate. Version 1.01 of the toolset installer has addressed this problem by no longer waiting for a return value from regsvr32, so the installer should no longer hang at this stage.

See Bug: Installer hangs at the stage of Execute:regsvr32.exe /s "C:\Dragon Age\tools\Engine.dll" for details should you encounter something like this again, or need to register engine.dll manually.

Other database issues and solutions

If you have never installed MSSQLServer Express, check for updates available for it through Windows Update after installing the toolset.

If the SQL install fails with a crash it is possible that it is conflicting with MSXML6. If you have MSXML6 installed, uninstall it and try reinstalling the toolset. See Microsoft's support page on this issue. If you have trouble uninstalling MSXML6, try the Microsoft Windows Installer Cleanup Utility.

During the SQL Server Express installation when the installation script attempts to start the database, a message box with the "The SQL Server service failed to start..." error message and options to Retry or Cancel may pop up.

  • Do not click Cancel. Clicking Cancel rolls back the installation, preventing the creation of the BWDATOOLSET database. You will need to reinstall from scratch if this happens.
  • Instead, navigate to and right click on the Protect folder and open the Properties window. On the Security tab add NETWORK SERVICE to the list of Groups and User names and grant it Full Permissions. The path to the Protect folder will be:
    • Windows XP: C:\Documents and Settings\NetworkService\Application Data\Microsoft\Protect
    • Windows 7: C:\Users\<username>\AppData\Roaming\Microsoft\Protect
  • If you don't have a Security tab then close the Properties window and select Tools | Folder Options from Explorer's menu bar. In the Folder Options window click on the View tab, scroll to the last option and uncheck Use simple file sharing (Recommended) option. Now you should be able to do complete the previous step.
  • Finally return to the "The SQL Server service failed to start..." error message and click on the Retry option.

The version of MSSQL Server 2005 included with the toolset may have trouble installing on 64-bit operating systems. This can be indicated by SQL Server Error 70047 in the installer's logs. To resolve this problem, install Microsoft .NET Framework Version 2.0 for 64-bit architectures before installing the toolset.

You may also encounter issues running migration scripts on 64 bit OSes. An alternate migration script can be found here:

You may get issues with access permissions. This can be avoided by giving your username admin rights to the database. To do this:

  1. Run "SQL Server Surface Area Configuration" (should be on your start menu under Microsoft SQL Server 2005)
  2. Select the "Add new administrator" option.
  3. Add yourself as administrator.

If you get a syntax error during installation, it could be caused by the path being too long. Rather than moving your whole install, try this:

See Manual database installation for instructions on how to manually set up the database for use with your toolset.

Windows XP SP 2 and endless reboot cycles after install

The MSSQL Server Express installer bundled with the toolset has a potential issue when installed on Windows XP Service Pack 2 that can cause an endless cycle of reboots. The toolset installer will warn you not to proceed if it detects SP2 on your system. Dragon Age: Origins has Service Pack 3 as part of its minimum installation requirements, so you should try upgrading to Service Pack 3 and reinstall.

If you're stuck in an endless reboot cycle:

  • Press ctrl+alt+del and open the task manager as soon as possible. Failing that, try booting in safe mode by holding down F8 during the boot process.
  • Then go to the start menu and in execute type in "msconfig"
  • In MSConfig go to services and deactivate all the SQL services.
  • Now you can go to control and uninstall the SQL server from the last piece upward.

Alternately, instead of booting into safe mode after holding down F8 during boot, you can choose the option "Last known good configuration (your most recent settings that worked)". This may restore your system to a functional state and allow SQL Server to function correctly.

Once you've uninstalled SQL Server this should prevent further reboot cycles. You can now install Windows XP Service Pack 3.

Externals links for troubleshooting

Canard PC forum French only :Forum résumant la marche a faire en cas de problèmes.

Language: English  • русский