139 réponses à ce sujet

[Allan Smith]

***Update: Locking thread***
I am locking this thread so that subsequent viewers will see this post and realize that this is not an issue anymore.  There are no Steam specific issues with installing the toolset as of version 1.01.    If you are having difficulties installing the toolset, check out Installation troubleshooting on the wiki for more assistance.



***Update***
The following wiki page contains the latest and greatest information on working around this issue

http://social.biowar...tion_with_Steam

Going directly there will save you running through all of the rest of the posts here to piece together a solution.  A big thanks to everyone who pitched in to help us through this issue.
***End Update***

We are currently investigating an issue installations of the toolset for Steam users.  If you have issues with the toolset installer with Steam, follow this thread.  We will keep you posted as things develop.  So far it looks to be a problem with the default path length on Steam being too long for SQL Server 2005 to handle.   When we have a work around, a solution will be posted  here.

If anyone has been sucessful with a Toolset /Steam install, please pipe up too. 

Modifié par Allan Smith, 01 février 2010 - 09:32 .

[Neon0x]

Ok, sweet, thanks. Hope you guys can figure out something soon, and I'm a modder, not a player.

[Wannabeuk]

Is there any way to get access to the install files themselves, as a simple code change in Sysdbupg.sql would solve this issue apparently.

[Syn.aptic]

Is it possible to install the SQL server seperately? I already have it installed though - possibly not SP3.

[Wannabeuk]

Right, im trying something currently, i have searched for an edited the file after the .exe extracts itself, im testing if this works now (althought i dont think i found the right file tbh)

[indio]

Wannabeuk wrote...

Right, im trying something currently, i have searched for an edited the file after the .exe extracts itself, im testing if this works now (althought i dont think i found the right file tbh)

Exciting news. Go my son!

[Hazado22]

FIXED! Do what is says there
http://support.microsoft.com/kb/935371
the file sysdbupg.sql is located at C:\\\\Program Files (x86)\\\\Steam\\\\steamapps\\\\common\\\\dragon age origins\\\\tools\\\\toolssql\\\\MSSQL.1\\\\MSSQL\\\\Install

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

I hit cancel the first time and let it complete the toolset install then tried to reinstall may be why I have these files above.

Yes i have the steam version and the toolset is working for me after i did the above fix

Modifié par Hazado22, 06 novembre 2009 - 07:35 .

[Wannabeuk]

Yep, it did work just as posted above.

For the lazy:

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

Find:
SELECT @certificate_name = QUOTENAME(@certificate_name, '''')
Replace With:
SELECT @certificate_name = '''' + REPLACE(@certificate_name, '''', '''''') + ''''
Re-install toolkit

Modifié par Wannabeuk, 06 novembre 2009 - 07:38 .

[BryanDerksen]

Awesome, you guys are ahead of us. We just finished reproducing the error.



We're going to try reproducing your fix now.

[carllar]

I had a pre-existing instance of SQL 2008 Express so I simply pointed the installer to that and it seems to have worked in that the toolset is able to start up. Beyond that I can't say if it is functioning correctly or not.



There was a second issue at the end of the installation process where it gives an error message saying that it can't open the uninstall.exe file. I noticed that it seemed to be trying to use a default C:\\Program Files\\Bioware\\Dragon Age\\ directory rather than the Steam directory that it detected at the beginning of the install. I simply ignored the error and the install completed.

[UnlightedOne]

Hazado22 wrote...

FIXED! Do what is says there
http://support.microsoft.com/kb/935371
the file sysdbupg.sql is located at C:\\\\\\\\Program Files (x86)\\\\\\\\Steam\\\\\\\\steamapps\\\\\\\\common\\\\\\\\dragon age origins\\\\\\\\tools\\\\\\\\toolssql\\\\\\\\MSSQL.1\\\\\\\\MSSQL\\\\\\\\Install

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

I hit cancel the first time and let it complete the toolset install then tried to reinstall may be why I have these files above.

Yes i have the steam version and the toolset is working for me after i did the above fix

Perfect fix. Well done sir and many thanks.

[indio]

1. Install toolset

2. When error arrives and asks to Retry, complete the fix now

3. Hit Retry and finish the install

[Neon0x]

Hazado22 wrote...

FIXED! Do what is says there
http://support.microsoft.com/kb/935371
the file sysdbupg.sql is located at C:\\\\\\\\Program Files (x86)\\\\\\\\Steam\\\\\\\\steamapps\\\\\\\\common\\\\\\\\dragon age origins\\\\\\\\tools\\\\\\\\toolssql\\\\\\\\MSSQL.1\\\\\\\\MSSQL\\\\\\\\Install

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

I hit cancel the first time and let it complete the toolset install then tried to reinstall may be why I have these files above.

Yes i have the steam version and the toolset is working for me after i did the above fix

Thank you SOOOO much. Toolset seems ot be working now.

[Ticladesign]

I cannot find the "install" directory at all... there's just Data. Log, and Template data in that directory.

[Wannabeuk]

Ensure you have already attempted the install as explained above

[Ticladesign]

Silly me. Thanks!

[boba1974]

This fixes it for the Impulse version as well.

[Syn.aptic]

When I tried to reinstall the toolset I only had a MSSQL.2 folder. I ran the installer again and it popped up a different error - I forgot to copy but it basically said something about not parsing sysdbupg.sql. I deleted the file (MSSQL.2\\MSSQL\\Install) and replaced with a blank file with same name. Installer carried on and I can now use the toolset.

[pasmith]

I too am having the problem where the uninstall file wants to be created in the wrong directory.

Instead of C:\\Program Files (x86)\\Steam\\steamapps\\common

It tries to write to C:\\Program Files (x86)\\common

Modifié par pasmith, 06 novembre 2009 - 08:29 .

[leotime0]

it would be much better to have the toolset in the tools tab in steam

[BryanDerksen]

Our test machines are being a bit uncooperative, perhaps because they've had the toolset installed and uninstalled so many times. We're still working on a clean reproduction of the fix.



In the meantime, I've thrown together a wiki page covering this issue using various posts reporting successes. See http://social.biowar...tion_with_Steam and feel free to add more details or other bits of information there as they arise.

[The junk]

 Thanks for the post. It's working for me.

Just a quick reminder: For previous cancelled installations, be sure to follow the MS support post. Specifically, use add/remove to uninstall 'SQL Server 2005' and delete the 'MSSQL.1' folder from '[wherever]\\Steam\\steamapps\\common\\dragon age origins\\tools\\toolssql'. I did not do those things ( ), at first, and so the fix above was unsuccessful.

[Ag0Ag0]

 I tried the above steps several times and keep getting a new error after I hit retry.

"
SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft]
[SQL Native Client][SQL Server]CREATE DATABASE failed. Some file names listed could not be
created. Check related errors..Refer to the server error logs and Setup logs for detailed error information.
"

The sql directory it created is MSSQL.2 rather than the MSSQL.1 in the instructions above, probably because I already had sql 2005 installed. I don't know anything about setting up a database though, other software I have installed it and uses it automatically. The MS knowledgebase article says if this fails to unistall sql and try again, but I cannot do this as I have other software that is using it, and only one instance of it shows up in the add/remove software.

[BryanDerksen]

Yeah, that was the error that we were getting here when we tried reproducing the original issue. So we're tracking both of these now.

[Syn.aptic]

@Ag0Ag0:

I encountered this problem and detailed it in my post above. That was my mystery error, and replacing sysdbupg.sql with a blank file with the same name fixed my problem.