20 réponses à ce sujet

[KREUGER44]

 I want all of you who have this problem to post in this thread. It IS important. Show your feeelings and enervation.Post solutions and let this thread grow so the developers at Bioware take this issue seriously. 

I´ve heard they are working on a toolset patch and I want all of you to try to engage them to solve this problem for us with it. Atm they are not thinking of solving this (not on their list) that is something that needs to be changed!

I myself bought the game because of the promising toolset, I have tried every solution out there in all of the hundreds of threads on internet and it doesn´t work for me.. 

Those of you in a similar position or those of you who managed to get the toolset working, please contribute.

Help me threads:

http://social.biowar.../8/index/146067
http://social.biowar.../8/index/126237
http://social.biowar.../8/index/109919
http://social.biowar.../8/index/126925
http://social.biowar.../8/index/121517
http://daforums.biow...06561&forum=140
http://www.giantbomb...ot-work/270708/
http://daforums.biow...07361&forum=140
http://daforums.biow...ect to database
http://daforums.biow...ect to database
http://daforums.biow...ect to database
http://forums.penny-...=105184&page=19
http://social.biowar.../8/index/189725

Solution oriented threads:
http://social.biowar.../8/index/152871
http://social.biowar.../8/index/153732

I will edit and link some more in the future.

Modifié par KREUGER44, 14 novembre 2009 - 06:23 .

[Astorax]

While I appreciate your concern, it's a known issue.



Posting more about it won't do anything to make them fix it faster. They're working as hard as they can already on it (as they said so in the announcement thread which is visible to all forums).

[KREUGER44]

This is what they have said Astora, nothing about them working on this issue here:

"We are working on a both a new toolset installer and patch to work on the following major issues:
Discourage/prevent the installation of the toolset on a Windows XP SP2 machine, in order to prevent the SQL Server reboot chaos that happens. (SP3 on Windows XP is the minspec)

* New core resources database with plot GUIDs that are consistant with the ones released with the game so that running the toolset does not mess with your save games. This is the "Click Here if the Toolset Broke your DA:Origins Game" thread.
* The "SQL and Steam" issue, which really has nothing to do directly with Steam, it is just an issue of installing SQL Server instance to a long pathname. We are looking to find a new home for this data that will always be under the arbitrary 58 character limit imposed by SQL Server.
* Trying to work around the "Toolset Install Stuck at Execute:regsvr32.exe" part way through the install process
* Make ERF and GFF editors usable outside of the toolset (removing keyfile checks)"

Thus we need their attention to start working on a fix for this problem.
I want all of you to send them emails or post in this patch-thread so they make it a priority issue: 
http://social.biowar.../8/index/173428

Modifié par KREUGER44, 13 novembre 2009 - 08:32 .

[Skydiver8888]

i'm with you kreuger. can't get it to work no matter what i try. My data folder is empty, i try the dos command and just get errors.



it's really frustrating.



What IS odd is that i have the steam version, but i am NOT getting the typical steam "path name too long" error on installation. Just this database thing.

[KREUGER44]

Skydiver8888 wrote...

i'm with you kreuger. can't get it to work no matter what i try. My data folder is empty, i try the dos command and just get errors.

it's really frustrating.

What IS odd is that i have the steam version, but i am NOT getting the typical steam "path name too long" error on installation. Just this database thing.

If you have a different language than english in your OS you might need to change "program files" in the dos commande to what´s apropriate in my case simply "program" 

I actually managed to get the data files but i still cannot run the toolset : [

[Astorax]

There's a couple different problems currently associated with the cannot connect bug.



The primary one is involving installs from Steam (this is the one they're working on actively).



The second is a problem with the installation of the SQL 2005 database service on the machine. Most of the suggestions involved uninstalling what the toolset attempted to install, then installing SQL 2005 from the services tab manually, then reinstalling the toolset.

[Livemmo]

This thread isnt so huge..

[Ninjaphrog]

Spam Threadz!

[shreddog]

Got the same problem. Vista 64 - DA standard retail version

[LokiHades]

I agree on this. I had to reinstall my game, and this happened.

[Skydiver8888]

Astorax wrote...

There's a couple different problems currently associated with the cannot connect bug.

The primary one is involving installs from Steam (this is the one they're working on actively).

The second is a problem with the installation of the SQL 2005 database service on the machine. Most of the suggestions involved uninstalling what the toolset attempted to install, then installing SQL 2005 from the services tab manually, then reinstalling the toolset.

Can you point me to this services tab, or the threads that explain how to do what you suggest in the last paragraph?  I am really eager to get into the toolset, but not being able to open it is driving me nuts.

My toolssql/data folder is empty, and i know it shouldn't be.  The DOS command that people suggest using doesn't work for me, even when i double and triple check all the file names and paths. 

running on  windows XP SP3, steam install.  As i said, i am NOT getting the typical error about the path name being too long for sql 2005 to install, which i find strange.  As a matter of fact, the only error i get during install is easily corrected by creating a program files/common/bioware folder. 

[DM Veil]

First time I installed the toolset everything worked fine, but I did a reinstall of the game and the toolset had to be reinstalled as well and now every time I try to install it I get a fatal error when it tries to install SQL causing my toolssql/data folder to be empty (shown below). I've tried uninstalling the toolset and SQL files and redoing it but it's always the same problem.

i552.photobucket.com/albums/jj353/mrjb/Misc/sql_fatalerror.jpg

[marshalleck]

http://evansims.com/...n-windows-7-x64



worked for me

[Wugger]

I have said issue.

[Horred the Plague]

As do I. WinXP Home SP3, game install from disc. tried a lot of workarounds already with no luck. I'm wondering why MySQL isn't supported or recognized by the configuration utility, only MSSQL. I've had that running and working great for years--it's the food of choice for NWNX2 and NWNX4 applications (NWN1 and NWN2 persistent worlds). I finally went in with MS SQL Server Management Studio Express, and after tinkering around a bit got a database going and this toolset running. I would HIGHLY suggest simplifying this process for the mainstream in the very near future, for expecting the average consumer to go through such an installation ritual is unrealistic at best.

[pinzig]

running vista x 64

digital deluxe edition from d2d

downloaded file, freezes at "verifying", doesn't install, doesn't show an error message, and oh yeah, CAN'T even END PROCESS it!!! ((can't even shut down my comp/restart, task manager fails to end it, have to do hard reboot......sigh))

[KREUGER44]

For all of us it is good to know we are not alone with this issue. The more of us that joins the ´mob´ the faster may Bioware work on making this work. We need to make our voices heard.

[shreddog]

I must say this m$ SQL thingy sucks major donkey balls!

[Ogre78]

i solve this problem in that way: unistall both tool and sql. Launch a "search" on sql and delete manually all sql folder remains. Give full access (remove "only reading") to /windows/system32 and /dragonage Folders. Install tool with sql (change nothing during installation). Go in control panel/administration then "Services", scroll down until see SQL Server (Bwda ecc.), right click -->proprieties, change and select "Account Local" and "interaction with desktop, same thing in SQL Server VSS Writer. Then launch the tool. SRY for bad english, hope i catch the english name of windows stuffs....

[KREUGER44]

Now at least they are working on this officially. Look at the Patch thread.