11 réponses à ce sujet

[gordonbrown82]

man oh man. the fix on the wiki doesn't work for the unable to connect to database error with the patched version. it probably has something to do with that the new DAODB director has been created to fix another problem. i have managed to restore the two database files to a directory called c:\\program files\\DAODB\\data but i still can't get the toolset to start working i still get the unable to connect to database error.

[Ranlas]

What operating system are you running? Vista/Windows 7 users seem to be reporting that often this error is solved for them by installing SQL Server Express 2008 and running it in SQL Server 2005 mode.

[gordonbrown82]

it's vista. but version 1.00 worked after i restored the database so i think it's more about the toolset not finding the files it needs because it's pointing to the wrong directory rather than that.

[Hammer Fang]

gordan, did you manually run windows update after installing sql 2005?

[gordonbrown82]

nope i don't know why i should have though?

[gordonbrown82]

the problem i had before was that i couldn't restore the database but now i have the two files but it seems that the toolset can't connect to them anyway.

[DJ Doc]

I tested toolset installation on vista x64 with MSSQL 2005 Express x64 and MSSQl 2008 Express x64 worked without any problems.



Just follow the manul db install in the wiki first install activepython then MSSQL x86 when on 32bit vista x64 when on 64bit vista and then the toolset.



Next step is installing SQL Server Management Studio open it ub create a new database "bw_dragonage_content" and install the db backup from the dragon age tools directory.



Next run ConfigureToolset.exe from DA:O tools directory and configure the connection for your server and all is up and running.



!!!Rant ahead!!!



Now I only wish bioware had used cleaner SQL code and not so much T-SQL crap and one could use the Toolset with a wider range of DB Servers. I for my part have no interrest to shove money down M$ throught just to run that slag SQL Server in a VM on my dedicated linux servers to get a working vcs setup just to enable a small group to write game mods for free.



Honestly builder-to-builder is a joke and whoever came up with running a sql server as vcs for game development should get knocked on his head, hard.



One could even build something better, faster and a lot more portable with Subversion...

[gordonbrown82]

"Next run ConfigureToolset.exe from DA:O tools directory and configure the connection for your server and all is up and running."



this is the problematic step. i already have the files i need.

[gordonbrown82]

any help would be appriciated on this i went through three days of mucking around with the exact same problem with version 1.00 and now i have it again but even harder to fix.

[Hammer Fang]

If you haven't had windows update sql 2005 then do so, there is an update and that fixed it for me. the other thing is, the wiki doesn't mention, last time I checked that ....

the toolset now just *IGNORES* the reg 32 error on install.

so, you need to boot in

**** SAFE MODE **** and then follow the direction from the wiki to register engine.dll

good luck.

Modifié par Hammer Fang, 18 décembre 2009 - 11:09 .

[DJ Doc]

gordonbrown82 wrote...

any help would be appriciated on this i went through three days of mucking around with the exact same problem with version 1.00 and now i have it again but even harder to fix.

So you just don't know what you have to put into ConfigureToolset.exe?

Let's see I just made a couple of screenshots (I'm on a German Vista x64)  that should give you an idea

First of my settings to connect from MSSMS to my SQL Server 2008 DB
The important part here is the Servername field


Next let's look how we named aur DA:O Database here's mine


Let's see what we have to do with ConfigureToolset


we press the continue ("weiter") button

make sure that Use the default Database is unchecked then press the "..." button


Now it's getting interresting let's select the Native SQl Server Provider it's a little bit faster


Connection here the screw up usually happens
As you can see the servername her matches the one from MSSMS
"Select the database matches" aur DA:O Database from MSSMS screenshot #2
Now wie click Test Connection and it should all work
time to contine


finally wh should have something like this
My database entry is Provider=SQLNCLI10.1;Integrated Security=SSPI;Persist Security Info=False;User ID="";Initial Catalog=bw_dragonage_content;Data Source=BLUEFIRE\\\\SQLEXPRESS;Initial File Name="";Server SPN=""


Hope that helps

If someone wants to put the screens and instructions in the toolset wiki feel free to go ahead

Modifié par DJ Doc, 18 décembre 2009 - 11:31 .

[gordonbrown82]

thanks i'll check out that i'm burned out on computer fiddling for now.