14 réponses à ce sujet

[Vertrix]

Old story...i got the ''unable to connect to database'' thing....i followed the guide (http://social.biowar...se_installation) but it still doesnt work...i think it's the last passage the problem.....what can i do?

[DarthGizka]

What did you do, exactly? Are you running a default installation of the toolset database or did you alter it in some way? Did it run before? Which version of Windows are you using?

 

ConfigureToolset.exe offers a convenient way of checking that your database is alive and kicking, as long as you remember to cancel out instead of committing any (unintended) changes. Every installation of SQL Server comes with sqlcmd.exe which allows more detailed checking, among other things. The most convenient tool is MS SQL Server Management Studio, but that is only available in special installations.

 

Have a look at the thread The Database error strikes again, and in particular my post about using sqlcmd to figure out what's going on.

[Vertrix]

I am using windows 7 x64. I installed the sql express studio, created the database and restored it, then, in the tollset config i setup the name of database (Inmy case, it's PC), and copied that key in HKEY_CURRENT_USER/software/bioware/dragonage/toolset/environment/database connection (this directory is not present in HKEY_LOCAL_MACHINE), but the problem still remains. It is silly, because some times ago i managed to solve the problem...

[DarthGizka]

Cool, that makes matters much clearer already. The server instance created by a default install of the toolset is BWDATOOLSET, and the default database name is bw_dragonage_content. In your case the server instance will likely have another name, like SQLEXPRESS, and you said the database name is PC. The SQL studio thingy should allow you to connect to your database and to poke around in it. Have you done that? If it works and you normally start studio as a mere mortal, try the same again but running studio as admin. Just to be sure that connecting as admin doesn't bork things, since the toolset is broken and insists on running as admin (by way of an embedded manifest).

 

If you run ConfigureToolset.exe in order to modify the configuration (instead of just checking that the database works), do not accept the defaults. They tend to be hypothetical. Select the server instance to connect to. This should populate the list box with the names of available databases for that server instance. If your toolset database is not among those listed, try running ConfigureToolset.exe as administrator. The database of a default toolset install (which uses SQL Server 2005) requires connections to be made with admin privileges.

 

The server instance must already be running when you try to start the toolset. You can check that easily by running services.msc from a command shell.

[Vertrix]

Yes, i chose the ''PC'' named database in the configure toolset, and i copied the path to the registry....but still doesnt work.

What do i have to look for in the services.msc?

[DarthGizka]

services.msc is convenient for checking whether the server instance is running, and to start it if not. I usually get caught with my pants down if something or other required a system restart, because I have set the server set to start type 'manual'.

 

Here it is not necessary. The fact that you were able to select your database in ConfigureToolset.exe tells us that the server responded and gave the program a list of available databases. It tells us also that the database was accessible at whatever privilege level ConfigureToolset.exe was run at.

 

Just to make sure, the text for DefaultDatabaseConnection under HKLM/Software/Wow6432Node/BioWare/Dragon Age/Toolset/Environment should look like this:

 

Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=bw_dragonage_content;Data Source=.\BWDATOOLSET

 

It is the same as the contents of the Database field in the Databases screen of ConfigureToolset.exe, after server and database were selected. In your case that would be PC instead of bw_dragonage_content and something like SQLEXPRESS instead of BWDATOOLSET. You can copy the text from the field to the registry, and you can paste the text from the registry into that field for testing (click "..." and then "Test Connection").

[Vertrix]

Yes, i know, and i did that, but it still doesnt work

[DarthGizka]

IOW: testing the string from the registry via ConfigureToolset.exe worked but the toolset didn't?

[Vertrix]

Nope, it doesnt work: it says ''error in the initialization of the provider''

[DarthGizka]

Are you talking about ConfigureToolset.exe? I've never seen the toolset itself give a sensible error message.

 

This means that the connection string specifies a server that is not running or not accessible. You can use services.msc to check that the SQL Server service is running. Its name there should be something like "SQL Server (SQLEXPRESS)", with the name of your toolset database server in parentheses.

 

If you start the SQL Server Browser service then you can use the server dropdown list in ConfigureToolset.exe ("Data Link Properties" screen) to pick the server instance without having to guess the name. After selecting the server you can pick a database on that server from the dropdown list in the middle of the dialogue box. Then you can use "Test Connection". If you can see the server but not your database then there is a permission problem; this happens in default installs with the ancient 2005 edition of SQL sewer. In that case you have to run ConfigureToolset.exe as administrator.

[Vertrix]

I can't seem to select the option to start SQL Server Browser service, the other one is already running

[DarthGizka]

Is it deactivated? If so, set the start type to 'manual', then the option to start it should appear. Which version of SQL Server are you using, by the way?

[Vertrix]

Yep, i enabled the browser, and that did the charm....thank you a lot!

[DarthGizka]

Glad you got it to work! The server browser service is not necessary for running the toolset itself, by the way. It is only necessary for the server list in ConfigureToolset.exe.

[Vertrix]

Yeah, and in facts, enabling it, allowed another database (the right one) to appear in the list, allowing me to succesfully enable it...