313 réponses à ce sujet

[Amalgamet]

I found the fix for the "Can't connect to Database" issue.

1. Uninstall SQL server and the Toolset from PC.

2. Delete C:\\Program Files\\Microsoft SQL Server

3. Delete in regedit:

HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Services\\MSSQLServer

HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Microsoft SQL Server

4. Reboot

5. Install Toolset with the SQL.



And the toolset works. No other issues. sorry for my bad English, but I wanted to help.

[Radimov]

Don't work in windows 7

[Allan Smith]

New update posted at the top of the thread.

[Greg the Mad]

I already know the answer, but I still have to ask:

If SQL is such a pain in the ass, why bother to use it?

Thanks for the update by the way. And about the updating in the wiki: Thats what they invented wave for.


Greg the Mad

Modifié par Greg the Mad, 26 novembre 2009 - 06:39 .

[Nikki503]

Maybe someone can help me with a similar problem with different details? My toolset installed and worked fine until I went to export my mod. The export went fine, however it exported to my admin account's addins folder rather than my addins folder. The only way I have found around this was to give my user login admin status. I don't like running this way, as it leaves my system less protected, but the real problem came when I went to resume playing my campaign. Everything seems fine til I leave camp and lose my party!

[BryanDerksen]

Internally, we use one big SQL server that everyone working on the game connects to. The advantage of this is that we can't inadvertently step on each others' toes thanks to the checkout/checkin functionality, and that we can always see the latest versions of the game's resources when working on it. It's really really handy... when you've got dozens of people all working on the same module simultaneously. For an individual user working on his own perhaps not so much, but doing a rewrite of the toolset's resource storage system was a bit beyond the budget we had for getting the end user toolset available.



The other reason why it works well for us internally is that we've got people whose main job is to do the database administration for us. We're not able to package that up to ship with the end user toolset, alas.



Nikki> the missing party member problem sounds like the plot GUID bug biting you. See http://social.biowar...p/Plot_GUID_bug for details.

[Zophu]

Allan Smith wrote...

New update posted at the top of the thread.

yay updates

[Greg the Mad]

BryanDerksen wrote...

Internally, we use one big SQL server that everyone working on the game connects to. The advantage of this is that we can't inadvertently step on each others' toes thanks to the checkout/checkin functionality, and that we can always see the latest versions of the game's resources when working on it. It's really really handy... when you've got dozens of people all working on the same module simultaneously. For an individual user working on his own perhaps not so much, but doing a rewrite of the toolset's resource storage system was a bit beyond the budget we had for getting the end user toolset available.

The other reason why it works well for us internally is that we've got people whose main job is to do the database administration for us. We're not able to package that up to ship with the end user toolset, alas.

I understand that its handy to you, but on my opinion I would have programmed the toolset in such a way that it sees the SQL server (checkin/checkout, etc) as a feature that you can initialize if wanted, but is not required. So that either the SQL server handles the content, OR the toolset itself. 
But thats something you probably would have thought of from start, and its definitely something you put in, only for community, if you just can put a SQL server client into the installer.

And I know how handy such a server can be, I have heard the story of Mass Effect 2.
One part of the team in Edmonton and the other one in Montreal, and both are working, more or less, on the same content. If you now sent a part of the team down to Austin, you'll create the absolute server overkill. ^.^


Greg the Mad

[Cat Lance]

Thanks for this update, again, Allan! Keep reading them with bated breath!

:happy:

[FalconEX]

Delighted by the latest update -- PLEASE - Do release the repaired SQL server data files & allow us to patch the DB asap. Thank you again for the link to the wiki page will work w/the new lightmap stuff tonight.

[Dark_Ansem]

will wait for the next version then. I'd rather not break the game.

[Asher Ravenheart]

When will the patch for the problem "Unable to connect to the database"?

[Dark_Ansem]

no need to patch for that. check here

http://social.biowar...the_database.22

[Asher Ravenheart]

Dark_Ansem wrote...

no need to patch for that. check here
http://social.biowar...the_database.22

I'm Italian, my english is bad. The explanations are too technical for me, i need a simple and intuitive explanation.

Modifié par Asher Ravenheart, 29 novembre 2009 - 01:51 .

[Endurium]

Just want to add or confirm a problem:



Attempted opening of a large save game (possibly lots of items in merchants/backpack) results in a failure with "out of memory" message. Typical of saved games toward end of campaign.



I'm running Vista64 Ultimate with 6GB system memory.

[Sidrat2009]

If you have SQL Express 2008 already installed set up and running, is it possible to use that for the tool set on a manual recovery perhaps? or not?

[giskard44]

Allan Smith

Are you or Bioware a little worried about the SQL system employed might lead to more of the same sort of issues in the future if the game patch and the tool patch are released at different times ?

It strikes me that any game patch or toolkit patch would have to be released at the same time to avoid this issue reoccuring over and over again.

Also I can understand the use of SQL, there are advantages here that are worth exploring for the modding communities but we need a simple backup and restore system badly. Losing all our work each time we install the toolkit does not endear modders to biowares toolkit and requiring us to be experts in SQL is asking too much.

Especially with the toolkit being so hard to learn initially anyway.

I am not being nasty here, what I am saying is, as a person that promotes modding when ever i go. People read what i write about workarounds and tips and all the hassles involved and simple decide not to bother modding DA. I have a several folk on my site right now that would love to mod DA but they are scared too because of steep learning curve and current problems.

If you decide to release patches at different times, this issue will become the bane of DA modders existances and if you fail to address the problem of losing the database where our hard work is installed, your going to lose what few modders are trying to battle their way through the toolkit today.

Whats needed is policy of updating the game and the toolkit on the same day so to avoid this issue and some sort of backup and restore tool for the tookit database.

I think the community will handle the rest given a chance. Many of us are busy writing detailed tutorials so the steep learning curve will be leveled out in time. The rest is what we need help with, if possible.

Remember we are modders, not SQL specialists, please keep that in mind.

Thanks

PS I use phpadmin on my site for backing up and restoring SQL databases, its not too hard to use, you might want to look in to that or something similar.

Modifié par giskard44, 30 novembre 2009 - 04:43 .

[Qutayba]

Thanks for keeping us updated. The modding community seems to be growing fast. While there are glitches, there are enough things in the toolset that work to keep us busy until all the glitches are worked out. I'd rather the fixes not be released until they're well tested. Despite the frustrations, I'm glad I've jumped into the process early. I'm learning the toolset better in part because I have to solve a lot of problems with trial and error. It's an incredibly powerful toolset, and I anticipate some stellar mods. Thank you, Allan, Bryan, and Bioware, for supporting the modding community.

[Nikki503]

giskard44 wrote...

Are you or Bioware a little worried about the SQL system employed might lead to more of the same sort of issues in the future if the game patch and the tool patch are released at different times ?

<content removed>

If you decide to release patches at different times, this issue will become the bane of DA modders existances and if you fail to address the problem of losing the database where our hard work is installed, your going to lose what few modders are trying to battle their way through the toolkit today.

Whats needed is [...] some sort of backup and restore tool for the tookit database.

Windows updates are a problem also.  I have Vista and when it updated last week I started getting the toolset cannot connect to the database error.  I was told to reinstall, and even though I thought I had backed up everything, I lost all my mod work. Fortunatly I had not done moch so far, or I might have given it up.  

I think the only way we have to backup our mods now is builder to builder create.  I have not used this yet, but I beleive this creates a file that you could re-open into your toolset (B2B load) giving you a working copy of your mod upto the point that you did the create.  Anyone know how long this takes to make?  Is it a viable backup option?

[Ranlas]

The builder to builder create/load is effectively a method of exporting resources from your database into what is essentially a zip file for easy transport. The time is takes to create a Builder to Builder file depends on the amount of resources you're putting into it. I don't know whether art resources (levels, head morphs, models, etc) are included in the file, so you may need to grab those separately.



At the beta event, we were shown how to use Builder to Builder Create and Load. In my experience, it hasn't taken longer than a minute, but there are those with much more experience than I who can tell you better.

[Aesir Rising]

Is there a way to separate the data from the DBMS and leave the option to use whatever DBMS you want up to the user?



I want to dabble in the toolset, but not if I have to install an outdated package on my updated system. Would love to be able to use PostGre or MySQL as both can be installed/uninstalled without leaving a ton of detritus on my system.

[Asher Ravenheart]

Doug-Le-Guedin wrote...

When we can expect to use the new version of the Toolset ?
I wait it because no one of the ways submited for the "Unable to connect to the datase" work for me...

I am in the same situation:crying:

[Ginggis Khan]

Nikki503 wrote...

giskard44 wrote...

Are you or Bioware a little worried about the SQL system employed might lead to more of the same sort of issues in the future if the game patch and the tool patch are released at different times ?



If you decide to release patches at different times, this issue will become the bane of DA modders existances and if you fail to address the problem of losing the database where our hard work is installed, your going to lose what few modders are trying to battle their way through the toolkit today.

Whats needed is [...] some sort of backup and restore tool for the tookit database.

Windows updates are a problem also.  I have Vista and when it updated last week I started getting the toolset cannot connect to the database error.  I was told to reinstall, and even though I thought I had backed up everything, I lost all my mod work. Fortunatly I had not done moch so far, or I might have given it up.  

I think the only way we have to backup our mods now is builder to builder create.  I have not used this yet, but I beleive this creates a file that you could re-open into your toolset (B2B load) giving you a working copy of your mod upto the point that you did the create.  Anyone know how long this takes to make?  Is it a viable backup option?

I did back up the database 2 days ago by using information in DA Builder Wiki, there are both strings for backup and restore. I reinstalled my Toolset afterwards, all mods were gone of course, I ran the restore and everything was back. I think you've missed something in backup/restore process, unless there is some odd Vista update patch that breaks SQL database? I wouldn't be surprised.

[giskard44]

Nikki503



Thanks for the info, but I do not have those connection problems. I am just concerned bioware are expecting modders to have system administrator skills in order to mod DA and whats said on the wiki seems to prove that point.



I know enough about sql on my site to handle it if need be but as a person that promotes modding, I know roughly the average skill level of most would be modders and this far exceeds their abilities.