12 réponses à ce sujet

[Magic]

Until today, I successfully used Toolset v1.00 without problems. I decided to install v1.01 but now I cannot use either version anymore. I get the "Unable to connect to the database" error:
http://social.biowar...to_the_database

During installation, I encounter the Windows File Protection error for "msxml6r.dll":
http://support.microsoft.com/kb/958897

Yes, I have a localized Windows XP SP3. I did not have much custom content, so I decided to start with a fresh database. I did the following:
1. First, I installed v1.01 over v1.00, selecting to install MS SQL Express 2005 SP3 (again) and to restore to the default database. The installation was successful, I could use Toolset v1.01 but I noticed that the old database was still intact and the Single Player resources missing. I decided to start over completely.
2. I deinstalled the Toolset, selecting to both deinstall database and MS SQL Express.
3. When I install the toolset again, now every time the file protection error for "msxml6r.dll" appears. This is for both toolset versions.
4. When I start the toolset, the unable to connect to database error occurs.

Please note that both versions installed without error the first time, before I uninstalled SQL Express 2005 (Never change a running system, I guess.)

I tried/checked the following:
- As http://support.microsoft.com/kb/958897 states, I checked that the log file says, installation of MSXML 6.0 Parser was successful.
- I did the full manual installation of the toolset. The same errors appear at the same times.
- I used ConfigureToolset.exe to check the settings according to the help page.
- I used regedit to check for the correct setting in the environment key.
- I rebooted between installation/deinstalltion.
- I tried the complete uninstall of the SQL Server including registration keys.
- I used the Windows Installer CleanUp Utility to get rid of MSXML 6.0 Parser but it seems the deinstallation was not a problem anyway.

To get it work properly again, I assume I need to reach a clean state before installation again. Any help please?

[Magic]

Never mind! I found the solution. I'll try to reproduce it ^^ and update the wiki.

[Allan Smith]

Sweet, I started to reply with some troubleshooting ideas, then got distracted, when I came back to the thread, you already had the fix. I'll be interested in finding out what the issue was.



Typically you should not have to clean off the toolset before re-installing, it usually works, however, when it goes bad, it really goes bad.

[Magic]

Thanks for your assistance. Yes, I continued the troubleshooting by going through each step of the Installation troubleshooting guide again. I am lucky that it is already so detailed, so I could find the problem. It was a mix of a database and localization problem it seems.

The files bw_dragonage_content.mdf and bw_dragonage_content_log.ldf were missing, so the database restoration was not successful. When I used SQL Server Management Studio Express to restore the files again, unpredictable behavior occurs unfortunately. The files can be placed in the following folders:
1. C:\\Programme\\DAODB\\MSSQL.1\\MSSQL\\Data
2. C:\\Programme\\DAODB\\Data
3. C:\\Program Files\\DAODB\\Data

A split is also possible for the two files (occured for me), and additionally the resulting target location does not reliably match the destination specified in the SQL Server Management Studio Express tool! My files are now in destination 1 (toolset working properly, database restored, Single Player contents available) despite the fact that I entered destination 3. I tripple-checked now because I assumed the files might not be generated at all. At some point I'm pretty sure the files were simply not at the place where they were supposed to be. Anyway, I'm glad this could be solved. I'll try to write at least some information that might be useful into the wiki.

[Magic]

I'm unsure what to write due to the unpredictability. Is it correct that the files bw_dragonage_content.mdf and bw_dragonage_content_log.ldf should be found as registered in reg key HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Microsoft SQL Server > BWDATOOLSET > Setup > SQLPath?

I also just noticed that my .ldf file is named bw_dragonage_content_log.ldf now although I wrote bw_dragonage_content.ldf as destination name.

Modifié par Magic, 18 décembre 2009 - 12:46 .

[slimouz]

Hi, i've been tring to install the toolset v1.01 since two day's and i can't start it, windows error constatelly appear :
"Unable to connet to the database."

"Run the toolset configuration and verify your settings or search on the toolset wiki http..."

I'm on windows XP (not craked)
I've tried to run the toolset configuration program and changed dirrections as they said on some other bioware forums.
I've tried to configure it also manually via the cmd console, but it tells me the configue ended abnormally.
I've tried to unistal and reinstal meny times the toolset, and the SQL servers.
I havn't used or installed the toolset v1.00 before.
And my data in C:\\program files\\DAODB\\Data is empty (i've checked out hidden files)

Every time in install the toolset, when i come to the SQL installation part an error message showes up telling me that the file called "C:\\\\WINDOWS\\\\system32\\\\msxmlr6.dll" is secured and that i should do a windows update.
(i did it and unistalled and reistalled the wohl thing, it didn't changed any thing)

I'm completelly lost, i have no idea what to do to make this toolset worke, so please help me .

Modifié par slimouz, 03 janvier 2010 - 04:02 .

[Toccoa1977]

same problem here and no clue :-(

[Toccoa1977]

same problem here and no clue :-(

[jobenn]

I am have the same problem, but with windows 7 pro. Going to try some of the solutions you have posted here and see what happens.

[ZarpDK]

I have the same problem.. i am running Windows 7 Ultimate 64 bit - And get the message: "Unable to connect to the database"

[Gorath Alpha]

The Toolset Forum is *STILL* where this belongs.

[CHT87]

Same issue here.

Is there really no solution for this?!

[Kronaras]

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.