Toolset Patch Information
#301
Posté 21 décembre 2009 - 11:13
#302
Posté 21 décembre 2009 - 11:58
#303
Posté 22 décembre 2009 - 01:59
If you build new levels in the level editor, or head morphs or other ART resources, they are independant and can just be re-added to another module, provided you dont delete the files. All other resources are part of the database and will be lost if you dont back them up. You can find backup/restore instructions for migrating to the new toolset on the wiki,
#304
Guest_Yenaquai_*
Posté 22 décembre 2009 - 05:27
Guest_Yenaquai_*
Had about ten installs/reinstallations with different approaches but still can't get it to work. It's getting a little bit frustrating... just now SQL seems to be completely broken and uninstallable... *sigh*
#305
Guest_Yenaquai_*
Posté 22 décembre 2009 - 05:29
Guest_Yenaquai_*
Modifié par Yenaquai, 22 décembre 2009 - 05:30 .
#306
Posté 22 décembre 2009 - 05:52
Yenaquai wrote...
Is there any chance this whole "unable to connect to database"-error can be fixed within a new patch? Just wondering... if it is technically possible to fix the problem.
Had about ten installs/reinstallations with different approaches but still can't get it to work. It's getting a little bit frustrating... just now SQL seems to be completely broken and uninstallable... *sigh*
Essentially no. There is no single cause for "Unable to connect to database". Effectively what this error message means is that the toolset couldn't get the database to work. The reasons that it won't connect are bountiful: the database doesn't exist, the database didn't start, the database doesn't have permissions, the database is somehow incomplete, etc. Since the toolset doesn't get any more information than the database telling it to go take a hike, we get this nebulous error.
It's unlikely that BioWare is going to be able to solve all of the issues with a product they didn't write that's running in system configurations it wasn't written for.
If anyone is having issues with the connection error after trying the solutions on the wiki, then I suggest they start a new thread for it. Include specific details about your system including operating system, langauge, and hardware and then perhaps the community or BioWare will be able to help more specifically. We're all in this together.
#307
Guest_Yenaquai_*
Posté 22 décembre 2009 - 06:43
Guest_Yenaquai_*
Ranlas wrote...
Yenaquai wrote...
Is there any chance this whole "unable to connect to database"-error can be fixed within a new patch? Just wondering... if it is technically possible to fix the problem.
Had about ten installs/reinstallations with different approaches but still can't get it to work. It's getting a little bit frustrating... just now SQL seems to be completely broken and uninstallable... *sigh*
Essentially no. There is no single cause for "Unable to connect to database". Effectively what this error message means is that the toolset couldn't get the database to work. The reasons that it won't connect are bountiful: the database doesn't exist, the database didn't start, the database doesn't have permissions, the database is somehow incomplete, etc. Since the toolset doesn't get any more information than the database telling it to go take a hike, we get this nebulous error.
It's unlikely that BioWare is going to be able to solve all of the issues with a product they didn't write that's running in system configurations it wasn't written for.
If anyone is having issues with the connection error after trying the solutions on the wiki, then I suggest they start a new thread for it. Include specific details about your system including operating system, langauge, and hardware and then perhaps the community or BioWare will be able to help more specifically. We're all in this together.
Thanks for clarification.
I still have to try the cmd- manual restoration of the database, as well as SQL 2008... if that won't work I would welcome the help, so I'll post in the forums.
#308
Posté 23 décembre 2009 - 02:34
my PC fought a Revenant and the Aura of Weakness spell stayed long after the fight. it's still not gone. i have tried dispel cleanse area and camping sio i resolved to find it in the toolset and remove it that way. I was hoping somebody might know where that's located?
Modifié par MrMaps, 23 décembre 2009 - 05:49 .
#309
Posté 04 janvier 2010 - 08:53
#310
Posté 11 janvier 2010 - 11:15
SQL Express 2008 can have issues in Windows XP, more so than Vista, and for database editing and management , I have only found SSMSE 2005 to work. If you can clarify what operating system you are using, I would be happy to offer some assistance getting it going for you. For most database connection difficulties, the "Forum" will not be proactive enough of a solution. You will need to counter each connectivity or database error, right then and there, so it is possible you may even need more of an instant communication and response, than is possible here, not that the good forums folk cannot help, oh no, I am sure they can. We all try in our special given talent ways.Yenaquai wrote...
Ranlas wrote...
Yenaquai wrote...
Is there any chance this whole "unable to connect to database"-error can be fixed within a new patch? Just wondering... if it is technically possible to fix the problem.
Had about ten installs/reinstallations with different approaches but still can't get it to work. It's getting a little bit frustrating... just now SQL seems to be completely broken and uninstallable... *sigh*
Essentially no. There is no single cause for "Unable to connect to database". Effectively what this error message means is that the toolset couldn't get the database to work. The reasons that it won't connect are bountiful: the database doesn't exist, the database didn't start, the database doesn't have permissions, the database is somehow incomplete, etc. Since the toolset doesn't get any more information than the database telling it to go take a hike, we get this nebulous error.
It's unlikely that BioWare is going to be able to solve all of the issues with a product they didn't write that's running in system configurations it wasn't written for.
If anyone is having issues with the connection error after trying the solutions on the wiki, then I suggest they start a new thread for it. Include specific details about your system including operating system, langauge, and hardware and then perhaps the community or BioWare will be able to help more specifically. We're all in this together.
Thanks for clarification.![]()
I still have to try the cmd- manual restoration of the database, as well as SQL 2008... if that won't work I would welcome the help, so I'll post in the forums.
#311
Posté 15 janvier 2010 - 09:52
Since we can't post on your new announcement (for obvious reasons), I'll stick my thanks here for the update on the next patch. I'm sure that the part of the community that works with the toolset and sees how complex it is will generally be more understanding of changes in Bioware's timetable than the broader player base is about delays. Speaking for myself, just seeing a sign that you're still checking things out and planning to improve the toolset, is all I really need to be content for now. I want it to be done right (and realize that other impending Bioware games are probably diverting a lot of Dragon Age staff for the time being) and can wait.
#312
Posté 15 janvier 2010 - 10:13
I am un-stickying this thread now. Will let it work its way down through the pile.
#313
Posté 29 avril 2010 - 11:01
#314
Posté 29 juillet 2010 - 08:37






Retour en haut




