Ok, so I'm getting the "unable to connect to the database" error that a lot of people are getting, the thing is I'm also using the Steam version of DA:O, so I'm getting a lot of mixed messages as to what I'm supposed to be doing.
1: "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[/code]""
I have no worldly clue what program they are talking about, I'd assume it was the "Configure Toolset" program in the /tools directory, but all that does is ask me by game build and database directory, nothing about being a programmer.
2:Some users report that the installer fails to create the SQL database (e.g. your Dragon Age\\toolssql\\data[/code] folder is empty). You can enter the following command to try restoring the database manually (Change the paths tobw_dragonage_content.bak[/code] 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:\\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'"
[/code]
Again, failing to tell me the exact program I'm supposed to be typing this gibberish in I assumed it was the command prompt. So I changed all that to "C:\\Program Files\\Microsoft SQL Server\\90\\Tools\\Binn\\sqlcmd -S .\\BWDATOOLSET -E -Q "RESTORE DATABASE bw_dragonage_content FROM DISK = 'C:\\Program Files (x86)\\Steam\\steamapps\\common\\dragon age origins\\tools\\dbbak\\bw_dragonage_content.bak' WITH MOVE 'bw_dragonage_content' TO 'C:\\Program Files (x86)\\Steam\\steamapps\\common\\dragon age origins\\tools\\toolssql\\Data\\bw_dragonage_content.mdf', MOVE 'bw_dragonage_content_Log' TO 'C:\\Program Files (x86)\\Steam\\steamapps\\common\\dragon age origins\\tools\\toolssql\\Data\\bw_dragonage_content.ldf'" which is, as far as I can tell, exactly the same line as the one provided, with the paths changed. The only thing this did was let cmd tell me that 'C:\\Program' is not recognized as a yadda yadda it doesn't work.
Then I tried First use the ConfigureToolset to set the correct string.If you don't use the default settings you can copy the string from from the ConfigureToolset tool otherwise use one of the following command line queries to get the connection string.Win32: reg query "HKLM\\SOFTWARE\\BioWare\\Dragon Age\\Toolset\\Environment" /v DefaultDatabaseConnection[/code]Win64: reg query "HKLM\\SOFTWARE\\Wow6432Node\\BioWare\\Dragon Age\\Toolset\\Environment" /v DefaultDatabaseConnection[/code]Now run the following command line (substituting your connection string for the final value)reg add "HKCU\\Software\\BioWare\\Dragon Age\\Toolset\\Environment" /v DefaultDatabaseConnection /t REG_SZ /d "Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=bw_dragonage_content;Data Source=.\\BWDATOOLSET"
Again, I have no clue what program I'm supposed to be trying to enter this in.
[/code]Can someone please translate this into idiot for me?
Need help decyphering "unable to connect to the database" wiki
Débuté par
Vhakk
, nov. 10 2009 10:45
#1
Posté 10 novembre 2009 - 10:45
#2
Posté 19 novembre 2009 - 10:39
Bump.
#3
Posté 19 novembre 2009 - 10:56
I couldn't get it to talk to my current SQL installation, so I just removed my old installation (wasn't using it) and had the toolset install the version it wanted to, complete with the default database name etc. Then I ran the configuration program for the toolset to reset it to the default settings, and it worked fine.
#4
Posté 19 novembre 2009 - 06:10
I get the "unable to connect to the database" error aswell. I'm using a DVD copy of the game, on a 64bit Win7 OS. The data folder that the toolset wiki mentions is indeed empty, and just like the author of this thread I'm utterly clueless as to where I'm supposed to run that command. Aside from enjoying a few games now and then, my experience with computers is somewhat limited. Any help on this would be greatly appreciated.
#5
Posté 11 décembre 2009 - 03:38
I had this problem when I was messing with msconfig. I accidentally disabled the SQL database in there, which was pretty obvious but it took me a while to think about it. Just a thought for people who might have done the same thing.
#6
Posté 21 décembre 2009 - 10:53
#7
Posté 18 mars 2010 - 04:47
Ok this is just bs. The toolset should never used that MYSQL peice crap it's over 5 years out date.
Modifié par dragonsouce, 18 mars 2010 - 05:39 .
#8
Posté 18 mars 2010 - 03:34
I installed then I did this so I could reinstalled it all the crap.
Run a regcleaner like total uninstall or and CCleaner and then "window install clean up" that free from MS so going to have to run ccleaner again as MS does not know what there doing.
Next part Important as the peice crap SQLEXPR redid your primissions on your Adminstration rights (your not realy a Adminstator any more
then I Open “RegEdit” and browse to the key HKEY_LOCAL_MACHINE\\\\\\\\\\\\\\\\SOFTWARE\\\\\\\\\\\\\\\\Microsoft\\\\\\\\\\\\\\\\Windows\\\\\\\\\\\\\\\\CurrentVersion\\\\\\\\\\\\\\\\Installer\\\\\\\\\\\\\\\\UserData\\\\\\\\\\\\\\\\S-1-5-18\\\\\\\\\\\\\\\\Components
1. Right Click on Components select permissions
2. Click Advanced
3. Select the “Owner” Tab
4. Select Administrators (Group) as owner and Click Apply.
5. Then Select Checkbox that says “Replace owner on sub containers and objects” and Click apply.
6. Browse back to the Permissions tab, select the Check box that says “Replace all child objects with inheritable permissions from this object” and Click apply
this let's reinstall.
ps
yes MS will tell you to do different to do it other ways but there retarded. This works.
Now Uninstall the mess and follow these dirctions and do a manual install.
http://social.biowar..._Manual_Install
Now it will work.
PS sorry for the delay just noticed the last two lines of my instructions wear cut off well it's complete now and will work.
PPS I Still needed to use ConfigureToolset.exe tool. No idea why as I basically used it to change to use a pass word then not use one but it work now.
Run a regcleaner like total uninstall or and CCleaner and then "window install clean up" that free from MS so going to have to run ccleaner again as MS does not know what there doing.
Next part Important as the peice crap SQLEXPR redid your primissions on your Adminstration rights (your not realy a Adminstator any more
then I Open “RegEdit” and browse to the key HKEY_LOCAL_MACHINE\\\\\\\\\\\\\\\\SOFTWARE\\\\\\\\\\\\\\\\Microsoft\\\\\\\\\\\\\\\\Windows\\\\\\\\\\\\\\\\CurrentVersion\\\\\\\\\\\\\\\\Installer\\\\\\\\\\\\\\\\UserData\\\\\\\\\\\\\\\\S-1-5-18\\\\\\\\\\\\\\\\Components
1. Right Click on Components select permissions
2. Click Advanced
3. Select the “Owner” Tab
4. Select Administrators (Group) as owner and Click Apply.
5. Then Select Checkbox that says “Replace owner on sub containers and objects” and Click apply.
6. Browse back to the Permissions tab, select the Check box that says “Replace all child objects with inheritable permissions from this object” and Click apply
this let's reinstall.
ps
yes MS will tell you to do different to do it other ways but there retarded. This works.
Now Uninstall the mess and follow these dirctions and do a manual install.
http://social.biowar..._Manual_Install
Now it will work.
PS sorry for the delay just noticed the last two lines of my instructions wear cut off well it's complete now and will work.
PPS I Still needed to use ConfigureToolset.exe tool. No idea why as I basically used it to change to use a pass word then not use one but it work now.
Modifié par dragonsouce, 29 mars 2010 - 01:48 .
#9
Posté 18 mars 2010 - 09:04
dragonsouce wrote...
Ok this is just bs. The toolset should never used that MYSQL peice crap it's over 5 years out date.
don't bad mouth MySQL if they had used that instead of MSSQL they wouldn't had these issues.
MySQL is very simple to install and get running.
#10
Posté 29 mars 2010 - 02:03
CID-78 with do respect it's still 5 year out date not windows 7 64 friendly (even if you use 64 bit Install)and there were about a hundred free-wear open source engines that work better. But I am not going to debate it with you Microsoft data bases are crap as that is my opinion and every one here who had this head ache. You Like great You use it happily .Me I use it unhappily and wonder why they did not use SQLite.
#11
Posté 05 juillet 2010 - 01:10
Here's what worked for me:
Uninstall SQL server and the Toolset from PC.
Delete C:\\Program Files\\Microsoft SQL Server
In Regedit, delete the following:
HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Services\\MSSQLServer
HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Microsoft SQL Server
Reboot
Install Toolset with the SQL.
Uninstall SQL server and the Toolset from PC.
Delete C:\\Program Files\\Microsoft SQL Server
In Regedit, delete the following:
HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Services\\MSSQLServer
HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Microsoft SQL Server
Reboot
Install Toolset with the SQL.





Retour en haut






