Unable to connect to database
#101
Posté 24 novembre 2009 - 10:38
It might help others from experiencing this nightmare and I'll try to explain this in english for those not highly technical:
The problem for me was this:
Running Vista 32bit, SQL Express 2005 already installed (MS Accounting) here's the problem:
The connection string is incorrect: Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=bw_dragonage_content;Data Source=.\\BWDATOOLSET"
The installation does not create a data source: .\\BWDATOOLSET nor does loading the backup create it.
In my install I have SQLExpress as the only datasource/Engine and installing the toolset loads the database into that 'Engine'.
So to fix the problem change this: "BWDATOOLSET"
to "SQLExpress" (without the quotes)
If the name of your engine is different, use whatever name appears in your management console.
Best of luck to those having this freaking problem.
#102
Posté 25 novembre 2009 - 01:09
http://social.biowar...troubleshooting
and
http://social.biowar...se_installation
i just changed .\\\\BWDATOOLSET to username\\SQLEXPRESS in the toolset config. I am using windows 7 x64 just so you know, and the command line thing was useless.
Modifié par sand beagle, 25 novembre 2009 - 01:10 .
#103
Posté 25 novembre 2009 - 01:11
#104
Posté 25 novembre 2009 - 01:27
MoxinRift wrote...
Haven't read all of this, so may be superfluous - but I got on the right path after reading Smergo's post. His command didn't work for me though, so I did the following:
1. Make sure you have all rights to the whole Dragon Age program folder (I really hate Vista sometimes ..)
2. Uninstall the toolset.
3. Run the installer as administrator.
4. Set the toolset to run as administrator.
5. Run the damn thing.
This finally worked for me. Thanks a lot to Smergo.
I also have vista and My computer makes me enter my admin password everytime I run the toolset. My toolset seems to work fine, but when I run the game, the mods do not show up. I'm thinking it's the admin thing that's the problem. Anyone know how to fix this?
#105
Posté 25 novembre 2009 - 02:34
#106
Posté 25 novembre 2009 - 09:33
Excedrin wrote...
...
The connection string is incorrect: Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=bw_dragonage_content;Data Source=.\\\\BWDATOOLSET"
The installation does not create a data source: .\\\\BWDATOOLSET nor does loading the backup create it.
In my install I have SQLExpress as the only datasource/Engine and installing the toolset loads the database into that 'Engine'.
So to fix the problem change this: "BWDATOOLSET"
to "SQLExpress" (without the quotes)
Nah - this doesn't work either. I open the configure toolset utility and specify your modified string and still getting an 'unable to connect' error. It's almost as if Bioware didn't want us to use this thing! A good thing I didn't have to pay for it.
G.
#107
Posté 27 novembre 2009 - 02:59
#108
Posté 28 novembre 2009 - 11:52
#109
Posté 29 novembre 2009 - 10:38
#110
Posté 03 décembre 2009 - 01:26
#111
Posté 04 décembre 2009 - 10:13
EDIT: I'm using a steam dragon age and I just managed to fix my problem and get the tool set working.
I followed the instructions at http://social.biowar...se_installation
and if you have steam also follow http://social.biowar...tion_with_Steam
Modifié par SteamPunks, 04 décembre 2009 - 11:00 .
#112
Posté 11 décembre 2009 - 08:57
#113
Guest_Doug-Le-Guedin_*
Posté 16 décembre 2009 - 01:15
Guest_Doug-Le-Guedin_*
#114
Posté 24 décembre 2009 - 12:47
#115
Posté 27 décembre 2009 - 01:08
#116
Posté 30 décembre 2009 - 10:41
My problem is that under "Original File Name", instead of the path to the .bak file, wich I chose exactly as pointed out here: http://social.biowar...base_backup.png (example: c:\\program files\\dragon age\\tools\\dbbak\\bw_dragonage_content.bak), I only see the .bak file. I can start the restoration at this point, and it even says it was succesfull, but at the target-location no files are created. No wonder, seeing that SQL doesn't seem to keep track from where it should get the .bak... It really starts getting on my nerves.
Modifié par Varhjhin, 30 décembre 2009 - 10:57 .
#117
Posté 05 janvier 2010 - 09:53
#118
Posté 07 janvier 2010 - 01:33
#119
Posté 07 janvier 2010 - 02:05
#120
Posté 10 janvier 2010 - 05:44
Seraph798 wrote...
I tried doing what Smergo recommended, but I couldn't find toolssql in the tools folder. Does anyone know where to find the folder? I have Vista if that matters.
This. there is no such thing as toolssql in my folder, using vista too.
And for the poster above me, trust me, Bioware won't fix this, we have to do a lot of programming crap in order to get something like this working, it's the exact same thing as with downloadable content, it just...Doesn't work properly unless you fix it yourself... :<
#121
Posté 11 janvier 2010 - 01:41
The problem I had happened to appear:
When I did run the ToolSet, it couldn't connect to the database, so my friend tried to restore the database as described on several sources, including this thread, with using the following command line (be sure to only have single backslashes in the whole paths, this forum seems to add more):
He did get a connection refused response in the output then and the command failed overall. My friend did the following then to address the issue: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\\DAODB\\bw_dragonage_content.mdf', MOVE 'bw_dragonage_content_log' TO 'C:\\Program Files\\DAODB\\bw_dragonage_content.ldf'"
1) In the 'SQL Server Configuration Manager' (via start menu), left click 'SQL Server 2005 Services', there should be a 'SQL Server (BWDATOOLSET)' running to the right.
2) Right click 'SQL Server (BWDATOOLSET)' and select 'Properties'
3) Instead of using the option 'Build-In Account', he selected a specific account via 'This Account:'. The account he did specify now was named exactly after my XP user account and we even used the same password. Now we both do not know if the exact phrasing there is necessary or even recommended, but it helped me anyway in the end.
4) He did run the command line now again (the one stated above) and it did go through and created 'bw_dragonage_content.mdf' and 'bw_dragonage_content.ldf' in the directory 'C:\\Program Files\\DAODB'
5) Running the Toolset now worked without any further configuration.
I hope this helps some people at least and I am sorry with not being able to respond any questions further, as I could not explain a single bit sadly.
Modifié par Ceneen, 11 janvier 2010 - 01:48 .
#122
Posté 11 janvier 2010 - 07:23
And I still don't understand where and how I would have to put that command line (and why). I am a complete idiot what comes to Windows system since I'm usually a Mac user. Tried to look the Wiki, but my mind just went blank.
Edit: And it also seems that the installation didn't went as it should have, I have ni folder in the start menu, from which I would be able to uninstall the toolset, so now I don't even know how to do that.
Modifié par Ubasti, 11 janvier 2010 - 07:39 .
#123
Posté 11 janvier 2010 - 07:48
Ceneen wrote...
I got it working now - thanks to a friend who did the trouble-shooting and did get some grey hairs due to this. I will post here the procedures and please try not to ask back, as I couldn't explain any of it, my friend could only answer, but he got no access here.
The problem I had happened to appear:
When I did run the ToolSet, it couldn't connect to the database, so my friend tried to restore the database as described on several sources, including this thread, with using the following command line (be sure to only have single backslashes in the whole paths, this forum seems to add more):He did get a connection refused response in the output then and the command failed overall. My friend did the following then to address the issue: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\\\\DAODB\\\\bw_dragonage_content.mdf', MOVE 'bw_dragonage_content_log' TO 'C:\\\\Program Files\\\\DAODB\\\\bw_dragonage_content.ldf'"
1) In the 'SQL Server Configuration Manager' (via start menu), left click 'SQL Server 2005 Services', there should be a 'SQL Server (BWDATOOLSET)' running to the right.
2) Right click 'SQL Server (BWDATOOLSET)' and select 'Properties'
3) Instead of using the option 'Build-In Account', he selected a specific account via 'This Account:'. The account he did specify now was named exactly after my XP user account and we even used the same password. Now we both do not know if the exact phrasing there is necessary or even recommended, but it helped me anyway in the end.
4) He did run the command line now again (the one stated above) and it did go through and created 'bw_dragonage_content.mdf' and 'bw_dragonage_content.ldf' in the directory 'C:\\\\Program Files\\\\DAODB'
5) Running the Toolset now worked without any further configuration.
I hope this helps some people at least and I am sorry with not being able to respond any questions further, as I could not explain a single bit sadly.
I checked the folder DAOB, and it already had those files. *bashes her head to the table few times in frustration*
#124
Posté 12 janvier 2010 - 12:32
Ubasti wrote...
I checked the folder DAOB, and it already had those files. *bashes her head to the table few times in frustration*
As far as I understood it, there were two problems on my PC:
1) Due to a faulty installation (even though the install went through flawlessly, aka no errors), the ToolSet couldn't connect to the database. I guess that is what those two files mdf and ldf are about?!?
2) The restoration process didn't work initially due to account restrictions and only did procede as soon as my friend changed the account who is allowed to access.
From what we read here and in the wiki, there are many different problems that could arise and would show in almost the same way (unable to connect). It took the better half of a day for us (or rather more for him) to get this going and hopefully it helps one or two others.
#125
Posté 12 janvier 2010 - 07:56
Well, have to say that at least I've learned tons about Windows system while going through this.
Oh, one thing, I tried to do the backup restore thing, but I got this message in the log:
+=================================================================+
+=================================================================+
Backup Batch File initated on ti 12.01.2010 at 9:51:38,31
using the following config.ini settings:
-------------------------------------------
Backup/Restore Config file
[SQL Server Name]
.\\\\BWDATOOLSET
[Database Name]
bw_dragonage_content
[Path to Directory to Save new Backup files to]
c:\\\\Backups\\\\
[Name of New Backup File]
DABackup001.bak
[Path to Directory Containing Existing Backup Files]
c:\\\\Backups\\\\
[Name of Existing Backup File to Restore]
DABackup001.bak
-------------------------------------------
Following command line being executed:
sqlcmd -S .\\\\BWDATOOLSET -E -Q "BACKUP DATABASE bw_dragonage_content TO DISK = 'c:\\\\Backups\\\\DABackup001.bak'"
Msg 927, Level 14, State 2, Server PELIXP\\\\BWDATOOLSET, Line 1
Database 'bw_dragonage_content' cannot be opened. It is in the middle of a restore.
Msg 3013, Level 16, State 1, Server PELIXP\\\\BWDATOOLSET, Line 1
BACKUP DATABASE is terminating abnormally.
Backup file will be found at: c:\\\\Backups\\\\DABackup001.bak
Batch File completed at 9:51:45,57
+=================================================================+
+=================================================================+
+=================================================================+
+=================================================================+
Restore Batch File initated on ti 12.01.2010 at 9:52:02,34
using the following config.ini settings:
-------------------------------------------
Backup/Restore Config file
[SQL Server Name]
.\\\\BWDATOOLSET
[Database Name]
bw_dragonage_content
[Path to Directory to Save new Backup files to]
c:\\\\Backups\\\\
[Name of New Backup File]
DABackup001.bak
[Path to Directory Containing Existing Backup Files]
c:\\\\Backups\\\\
[Name of Existing Backup File to Restore]
DABackup001.bak
-------------------------------------------
The backup file c:\\\\Backups\\\\DABackup001.bak does not exist. Restore process aborted
Batch File completed at 9:52:08,37
+=================================================================+
+=================================================================+
So it didn't work either. And I just wonder what is that "middle of restore" that it claims the bw_dragonage_content is in?
Modifié par Ubasti, 12 janvier 2010 - 08:01 .





Retour en haut






