Installation troubleshooting

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.

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.

"unable to connect to the database"

If you receive the "unable to connect to the database" error message there are a number of possibilities to explain and correct it:

• On some systems you may encounter a problem running the toolset if you copy the uninstalled files off of the DVD first before installing them. By default SQLServer doesn't necessarily have permission to read from all of the directories that the user may have put the installation files, so if you install from such a directory it may be unable to import resources into the database. To correct this either change the administrative privileges for the directory you're installing the toolset from or install it directly from DVD.
• If you already have MSSQLServer Express installed as part of a different program, the toolset may not get the correct configuration to use it. Run the toolset configuration, select "Programmer" as user type, and then click "next" through the configuration wizard until you get to the "Content Database" field. It should read: "Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=bw_da_content_euts;Data Source=MSSQLDEV"
• On Vista systems the toolset may need administrator privileges to read the database where it's installed but fail to prompt you for them. Try right-clicking the toolset's shortcut and selecting "Run as Administrator" from the dropdown menu.
• Some users report that the installer fails to create the SQL database (e.g. your Dragon Age\toolssql\data folder is empty). You can enter the following command to try restoring the database manually (Change the paths to bw_dragonage_content.bak and your Dragon Age folder as appropriate): "C:\Program Files\Microsoft SQL Server\90\Tools\Binn\"sqlcmd -S .\BWDATOOLSET -E -Q "RESTORE DATABASE bw_dragonage_content FROM DISK = 'C:\EUTS_Install\data\bw_dragonage_content.bak' WITH MOVE 'bw_da_content_euts_Data' TO 'C:\Program Files\Dragon Age\toolssql\Data\bw_dragonage_content.mdf', MOVE 'bw_da_content_euts_Log' TO 'C:\Program Files\Dragon Age\toolssql\Data\bw_dragonage_content.ldf'"
• Some users have been successful simply installing from a more direct path (ie extract rars to a new folder C:\DAInstall and then run the exe file from that location rather than from a MSFT created My Documents path).

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.

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.

• Don't hit cancel. Cancel rolls back the installation, preventing the creation of the BWDATOOLSET database. You'll need to reinstall from scratch if this happens.
• Instead, navigate to C:\Documents and Settings\NetworkService\Application Data\Microsoft\ 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.
• 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.