Jump to content

Toolset won't work. H E L P!


Habren82

Recommended Posts

Registration is not necessary to download the toolset and other ressources: http://social.bioware.com/wiki/datoolset/index.php/Community:Toolset_source_files

(Use the CDN link)

 

SQL Server 2016 was released last June and supports the Express version as well.

The question which SQL version to install depends a bit on how willing you are to be experimental. I know people got it working with SQL 2008 on Win 10 but for later versions I know no reports.

The version should better support SQL 2005 compatibility. Therefore the latest version I would expect to get it to work without too much hassle would be SQL 2012 (https://msdn.microsoft.com/en-gb/library/bb510680.aspx)

 

Good luck with the fresh installation on your virginal notebook! Best preconditions...

Link to comment
Share on other sites

Hi LadyHonor and YaraC,

 

I finally got everything to work. Thank you so much for your help and advise. VERY much appreciated. You guys rock!!! http://www.freesmileyfaces.com/files/day-by-day/communicate-smiley-faces/59.gif

Link to comment
Share on other sites

  • 1 month later...

I can't install SQL Servor 2008. It's so damn frustrating. I get to "Feature Selection" and keep getting an error message that says "The INSTANCESHAREDWOWDIR command line value was not specified."

 

Every guide I see online says not to change the install directory and to proceed with the installation, but it WON'T LET ME. It won't let me go until I fix the goddamn validation errors. And if I don't change the install directory, I get two OTHER error messages.

Link to comment
Share on other sites

I am afraid noone here will be able to give you a really smart advice, laydyvoldything. It is a obviously a Microft bug. It seems your only choice is to try out different (succesful) approaches mentioned in the Microsoft forums and check if it works for you. You can find different installation procedures with switches e.g. here or here.

Edited by YaraC
Link to comment
Share on other sites

Okay, it turned out I had a version of SQL that never got properly uninstalled- even though I THOUGHT I had.

 

So I'm using SQL 2014, and in trying to create a new database ("bw_dragonage_content") and make it compatible back to 2014, I got an error message saying that I couldn't do that.

 

So.... now what?

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...