v1.01 - Unable To Connect To Database!
#1
Posté 11 décembre 2009 - 06:43
#2
Posté 11 décembre 2009 - 08:55
Same problem here.
I quit.
#3
Posté 11 décembre 2009 - 01:01
Same problem!!
And they said they'd fixed the long Steam filepath issue... so the solution I used to make the old Toolset working now doesn't apply!
Goddammit....
#4
Posté 11 décembre 2009 - 01:30
What do you know, it installed PERFECTLY. No problems at all.
However, when launching the Toolset I'm still "unable to connect to database". Apparently the MS SQL Server is not presently configured to work with the DA Toolset.
Question is, how do I make it work?
*** UPDATE ***
Tried reinstalling the Toolset WITHOUT reinstalling the default MS SQL (i.e., so that the Toolset will use my new MS SQL installation which I did from the Microsoft installer).
It finishes rather well, with a CMD command line window opening at the end and executing some sort of a command.
Unfortunately, still "unable to connect to database".
And in the Windows Services, SQL is only listed as (EXPRESS), not (BDTOOLSET).
Apparently I can't marry the Microsoft-installed SQL and the Toolset database.
Modifié par Malcroix, 11 décembre 2009 - 01:40 .
#5
Posté 11 décembre 2009 - 02:13
I performed a manual database recovery and manually redirected the Toolset to see the new database. Here's the guide I used:
http://social.biowar...se_installation
This solution worked for me. Toolset launched!
#6
Posté 11 décembre 2009 - 02:15
Malcroix wrote...
PROBLEM SOLVED.
I performed a manual database recovery and manually redirected the Toolset to see the new database. Here's the guide I used:
http://social.biowar...se_installation
This solution worked for me. Toolset launched!
It worked for me too !
#7
Guest_Leopard73_*
Posté 11 décembre 2009 - 02:22
Guest_Leopard73_*
lol
And that is even with a brand new mod made with this Toolset. so when you fix your DB problem you got another one waiting for you in a dark alley around the corner MUWHAHAHAHAHAHAHA
#8
Posté 11 décembre 2009 - 02:26
I was having an issue with the original toolset with the regsvr.exe locking up. The new toolset installs completely without any snags (even SQL installs without a problem). But now when I launch the toolset it never opens. I get my little hourglass telling me my computer's doing something, but nothing happens. This problem also happened to me with the first toolset after following the instructions at the wiki to fix the regsvr.exe error.
My fiancee got the toolset to work and I'm aware the toolset doesn't open immediately, but I waited for a while and still nothing. I uninstalled and reinstalled and still it's not working. I know this probably isn't the perfect place to post my problem, but I'm getting desperate (please forgive me). /facepalm
I do appreciate what the work everyone is putting it to get the toolset to work properly, so I will continue to be patient. Thank you!
Modifié par LOST_PriNcEsS_, 11 décembre 2009 - 04:44 .
#9
Posté 11 décembre 2009 - 05:13
I hope v1.02 will have even more bugs, that could be fun...
#10
Posté 11 décembre 2009 - 05:26
If you are running on Vista, can you try right-clicking and running the Toolset as an administrator?
#11
Posté 11 décembre 2009 - 05:41
I went to DOS and wrote
sqlcmd -S .\\\\BWDATOOLSET -E -Q "RESTORE DATABASE bw_dragonage_content FROM DISK = 'C:\\\\Program Files\\\\\\\\Dragon Age\\\\tools\\\\dbbak\\\\bw_dragonage_content.bak' WITH MOVE 'bw_dragonage_content' TO 'C:\\\\Program Files\\\\Dragon Age\\\\tools\\\\toolssql\\\\Data\\\\bw_dragonage_content.mdf', MOVE 'bw_dragonage_content_Log' TO 'C:\\\\Program Files\\\\Dragon Age\\\\tools\\\\toolssql\\\\Data\\\\bw_dragonage_content.ldf'"
to recreate the database.
Now it works fine
#12
Posté 11 décembre 2009 - 05:42
Durmir wrote...
I've tried to follow the guide, but it doesn't work (though i'm not sure i've understood the last step...). I tried also all that was suggested on the toolset wiki. Still I have the same error : unable to connect to database...
I hope v1.02 will have even more bugs, that could be fun...
The last step is very important - since you've installed MSQL separately, you'll have to manually point the Toolset to the MSQL server. This is done via 2 steps:
1. Configure Toolset utility: in the second window, make sure you're NOT using the "default database", but rather click on the ellipsis (...) and enter the NAME OF YOUR ACTIVE MSQL SERVER, in my case SQLEXPRESS;
2. System registry: open it (run "regedit"), find your Toolset data, and manually enter the line generated by your Configure Toolset utility AFTER you have entered the correct name of your active MSQL server.
It's actually explained pretty thoroughly in that guide.
#13
Posté 11 décembre 2009 - 06:00
#14
Posté 11 décembre 2009 - 06:02
http://social.biowar...to_the_database
Will continue updating it with tips and helps.
#15
Posté 11 décembre 2009 - 09:42
TimelordDC wrote...
It is possible that the Engine.dll never got registered in your case. Have you tried running in safe mode and registering the dll?
If you are running on Vista, can you try right-clicking and running the Toolset as an administrator?
.DLL will not register for me using the run command in normal Windows or in safe mode. At least, I don't think it has; I don't get an error message or a confirmation message. Things just run in the background and nothing happens, like the toolset. Right-clicking and running the toolset as an administrator (since I have Vista) also doesn't work. Does this problem have anything to do with my Vista being 64 bit?
#16
Posté 12 décembre 2009 - 07:19
#17
Posté 03 janvier 2010 - 04:19
I get to: Is the Toolset correctly pointing to database? and I go through the configure toolset instructions. Everything is exactly as the wiki page says it should be. I hit "Test Connection" and it's not "Ok" and the page doesn't tell me what to do from there.
After testing the connection I get the error: "Test connection failed because of an error in initializing provider. Cannot open database 'bw_dragonage_content' requested by the login. The login failed"
I'm a bit stuck on what to do next.
#18
Posté 03 janvier 2010 - 09:17
#19
Posté 10 janvier 2010 - 04:00
After i checked all of these, i just clicked test connection, it said it was ok, and now it is working for me.
#20
Posté 12 janvier 2010 - 09:08
"test connection failed because error in initializing provider.
[DBNETLIB][Connect()).]SQL Server does not exist or access denied"
#21
Posté 14 janvier 2010 - 01:16
#22
Posté 15 janvier 2010 - 09:43
#23
Posté 16 janvier 2010 - 10:27
#24
Posté 22 janvier 2010 - 12:25
#25
Posté 29 janvier 2010 - 09:14





Retour en haut






