Dragon Age Toolset Wiki - User contributions [en]

Installation into a directory with a long path name

2009-11-07T18:32:38Z

A Monk32:

MSSQL Express 2005's installer has a limitation that prevents it from installing to a directory path that's longer than 58 characters. Microsoft's Knowledge Base has details here: http://support.microsoft.com/kb/935371

Unfortunately, the default installation path used by Steam goes over this limit. When you hit this error you'll get the error message

"SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft] [SQL Native Client] [SQL Server]Incorrect syntax near '='. "

A workaround has been developed that allows installation to work correctly, however.

Open the file \Steam\steamapps\common\dragon age origins\tools\toolssql\MSSQL.1\MSSQL\Install\Sysdbupg.sql

Find the line [it's near the bottom] that reads:
<pre>
SELECT @certificate_name = QUOTENAME(@certificate_name, '''')
</pre>

Replace it with the following line:
<pre>
SELECT @certificate_name = '''' + REPLACE(@certificate_name, '''', '''''') + ''''
</pre>

Re-install toolset.

If you can't find these files, you can try doing it while the installation process is ongoing. When the error message above pops up, edit the Sysdbupg.sql file and then click "retry" after you save the modified version.

If you still run into problems, Delete temp_MS_AgentSigningCertificate_database.MDF and LDF from C:\Program Files (x86)\Steam\steamapps\common\dragon age origins\tools\toolssql\MSSQL.1\MSSQL\Data

You may also run into the following error message:

"SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]CREATE DATABASE failed."

This one can be worked around by replacing the Sysdbupg.sql file with a blank file of the same name.

'''Note:''' BioWare is working on this problem to produce a better workaround than having to edit things on the fly while installing. We may be able to produce a new installer that handles this situation. Hopefully this won't take very long, we thank you for your patience.

[[Category:Toolset installation]]

Installation into a directory with a long path name

2009-11-07T18:32:10Z

A Monk32:

MSSQL Express 2005's installer has a limitation that prevents it from installing to a directory path that's longer than 58 characters. Microsoft's Knowledge Base has details here: http://support.microsoft.com/kb/935371

Unfortunately, the default installation path used by Steam goes over this limit. When you hit this error you'll get the error message

"SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft] [SQL Native Client] [SQL Server]Incorrect syntax near '='. "

A workaround has been developed that allows installation to work correctly, however.

Open the file \Steam\steamapps\common\dragon age origins\tools\toolssql\MSSQL.1\MSSQL\Install\Sysdbupg.sql

Find the line[it's near the bottom]that reads:
<pre>
SELECT @certificate_name = QUOTENAME(@certificate_name, '''')
</pre>

Replace it with the following line:
<pre>
SELECT @certificate_name = '''' + REPLACE(@certificate_name, '''', '''''') + ''''
</pre>

Re-install toolset.

If you can't find these files, you can try doing it while the installation process is ongoing. When the error message above pops up, edit the Sysdbupg.sql file and then click "retry" after you save the modified version.

If you still run into problems, Delete temp_MS_AgentSigningCertificate_database.MDF and LDF from C:\Program Files (x86)\Steam\steamapps\common\dragon age origins\tools\toolssql\MSSQL.1\MSSQL\Data

You may also run into the following error message:

"SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]CREATE DATABASE failed."

This one can be worked around by replacing the Sysdbupg.sql file with a blank file of the same name.

'''Note:''' BioWare is working on this problem to produce a better workaround than having to edit things on the fly while installing. We may be able to produce a new installer that handles this situation. Hopefully this won't take very long, we thank you for your patience.

[[Category:Toolset installation]]