22 réponses à ce sujet

[RyanFialcowitz]

The ToolSet itself installs fine, but when it tries to install SQL Server 2005 Express I get hit with this error:

An error occurred while attempting to create the directory C:\\\\ProgramData\\\\Microsoft\\\\Windows\\\\Start Menu

I've tried downloading different versions of the program from Microsoft but I always get some variation of that message. I'm running Windows 7 Ultimate 64 bit and I've tried both 32 bit and 64 bit installers.

- Ryan Paul Fialcowitz

Modifié par RyanFialcowitz, 29 janvier 2011 - 11:16 .

[Elvhen Veluthil]

I don't know if you have tried the latest version, service pack 4, if not, give it a try. You need administrative rights to install it properly (failing to create folders is sometimes result of this):



http://www.microsoft...16-017bdf47abdc

[RyanFialcowitz]

Elvhen Veluthil wrote...

I don't know if you have tried the latest version, service pack 4, if not, give it a try. You need administrative rights to install it properly (failing to create folders is sometimes result of this):

http://www.microsoft...16-017bdf47abdc

I get the same error. I should note that, as far as I can tell, all the folders mentoned have Full Control under Security/Permissions. I specifically took Ownership of every file on the computer for this very reason. . . Any other ideas?

EDIT
Why, exactly is SQL Server 2005 Express required to run the program? Is there another program or method I could use to modify the game's files?

- Ryan Paul Fialcowitz

Modifié par RyanFialcowitz, 29 janvier 2011 - 09:38 .

[Elvhen Veluthil]

I think SQL server is needed because the toolset needs a database to do its things. Have a look at this problem described in the wiki, maybe it gives you any idea about your problem:



http://social.biowar..._long_path_name

[Elvhen Veluthil]

Also the wiki has instructions how to manually install the SQL server:



http://social.biowar...se_installation

[RyanFialcowitz]

Elvhen Veluthil wrote...

I think SQL server is needed because the toolset needs a database to do its things. Have a look at this problem described in the wiki, maybe it gives you any idea about your problem:

http://social.biowar..._long_path_name

I may not be a computer expert but it makes NO SENSE why I should need to do ANYTHING with a server in order to edit a file on my hard drive. For reference- Star Wars: Knights Of The Old Republic, a BioWare game, needs no server and even uses the same file formats. Further all of Bethesda Software's more recent games don't require anything beyond their respective editors. It wouldn't be so bad if the required software works- but obviously it does not. This isn't a rant against the above poster- but seriously the requirement of SQL Servers makes no sense. Unless you'd like to try to sell me on the idea that it's IMPOSSIBLE to hex edit a UTI file in the game folder, there SHOULD be no need for this database nonsense.

Secondly, the issue that is subject of the link you posted has already been fixed.

Elvhen Veluthil wrote...

Also the wiki has instructions how to manually install the SQL server:

http://social.biowar...se_installation

RyanFialcowitz wrote...

I've tried downloading different versions of the program from Microsoft but I always get some variation of that message. I'm running Windows 7 Ultimate 64 bit and I've tried both 32 bit and 64 bit installers.

- Ryan Paul Fialcowitz

Modifié par RyanFialcowitz, 29 janvier 2011 - 11:19 .

[Elvhen Veluthil]

Well then, sorry for not being of any help to you. One way or another, you'll need a database to work with the toolset (not the game), so go in more details about your problem and hopefully someone of the experienced fellows will show up and give you a hand. Cheers.

[DarthParametric]

The toolset we have is what Bioware used to make the game. It was designed to run off a database backend to facilitate multiple remote users sharing and updating a single repository. In that sense, it is an efficient and logical approach. Such a system has the same potential use for mod groups - even more so seeing as they are often spread to the four corners of the earth, as opposed to just down the corridor. Granted, it doesn't have much application for a single user, but that's not what it was designed for and they weren't going to expend resources changing it. Be thankful we got a toolset at all. It works just fine for the vast majority of end users. Railing against it because you can get it to work isn't going to change anything, and it's not going to encourage people to try and help you resolve your issue.

[RyanFialcowitz]

Elvhen Veluthil wrote...

Well then, sorry for not being of any help to you. One way or another, you'll need a database to work with the toolset (not the game), so go in more details about your problem and hopefully someone of the experienced fellows will show up and give you a hand. Cheers.

It's all good, the fault is with Microsoft- not you. Your help is appreciated.

DarthParametric wrote...

The toolset we have is what Bioware used to make the game. It was designed to run off a database backend to facilitate multiple remote users sharing and updating a single repository. In that sense, it is an efficient and logical approach. Such a system has the same potential use for mod groups - even more so seeing as they are often spread to the four corners of the earth, as opposed to just down the corridor. Granted, it doesn't have much application for a single user, but that's not what it was designed for and they weren't going to expend resources changing it. Be thankful we got a toolset at all. It works just fine for the vast majority of end users. Railing against it because you can get it to work isn't going to change anything, and it's not going to encourage people to try and help you resolve your issue.

I fully understand your point, mine is that SQL Server should not have been a requirement for simply running the Toolset. Obviously the program is buggy and therefore not reliable. Either way it's Microsoft's fault, either from an operating system prospective or a software prospective. But Bioware could have released a more user friendly program. As I stated earlier it's an absurd requirement to modify local files. In any case, and I mean no offense by this, I seriously doubt anyone will solve this issue. I shall attempt to install SQL Server in Windows XP and see if that goes smoother, but I wouldn't be suprised if it is still problematic.

Thank you for your input and help, both of you.

- Ryan Paul Fialcowitz

[DarthParametric]

In the majority of cases there are no files as such - it's all stored in a database. Physical files are primarily used for final compiled game-only content. Hence you need to install a database for the toolset to use.

[RyanFialcowitz]

DarthParametric wrote...

In the majority of cases there are no files as such - it's all stored in a database. Physical files are primarily used for final compiled game-only content. Hence you need to install a database for the toolset to use.

Right, I understand the Toolset won't work without SQL Server. My point is that they could just as easily have made an editor that directly edited the files.

- Ryan Paul Fialcowitz

[DarthParametric]

Maybe, if they set out to make a specific end-user toolset. They didn't do that - they gave us the toolset they used to make the game. And technically, they did provide a standalone editor - the GFF editor.

[RyanFialcowitz]

DarthParametric wrote...

Maybe, if they set out to make a specific end-user toolset. They didn't do that - they gave us the toolset they used to make the game. And technically, they did provide a standalone editor - the GFF editor.

Dude, I get your argument. They released the Toolset to the public, maybe it worked out of the box for you- but for others and myself the dependecy on SQL Server caused nothing but problems and could easily have been avoided.

Seriously, at this point it's probably better to silence our guns. The point of this topic is how to install SQL Server on Windows 7 Ultimate 64 bit. Not even versions SPECIFICALLY designed for Windows 7 64 bit will install, which is a fatal flaw when software will not work with out it. Hopefully it will install under Windows XP- but I am not hopeful.

- Ryan Paul Fialcowitz

[DarthParametric]

Works perfectly fine under Win7 x64 for me. Sucks for you I guess that it doesn't work for you, but it's not an inherent issue with the software.

[RyanFialcowitz]

DarthParametric wrote...

Works perfectly fine under Win7 x64 for me. Sucks for you I guess that it doesn't work for you, but it's not an inherent issue with the software.

Specious reasoning, just because it works for you doesn't mean that is no inherent issue with the software.

The Toolset and SQL Server 2005 Express installed fine in Windows XP- but I would bet my fortune that I will run into more problems.

I think it's time to let this thread die the death it so richly deserves, don't you?

- Ryan Paul Fialcowitz

[DarthParametric]

No more specious than the fact that it not working for you means there is an issue. If that were the case, there would be a lot more people reporting problems (and far fewer mods). Does it work for everyone? No, but what software does?

[RyanFialcowitz]

[quote]DarthParametric wrote...

No more specious than the fact that it not working for you means there is an issue. [\\quote]

There is a mountain of evidence. All one must do is Google- but then most searches of that ilk will produce similiar results. There is either a problem with Windows 7 Ultimate 64 bit or the ENTIRE line of SQL Server software. If there were no issue there would be no thread. There are numerous other threads on this site claiming numerous problems with SQL Server. Bear in mind, my only issue with the Toolset is the pointless dependence on a secondary piece of software.

[quote]If that were the case, there would be a lot more people reporting problems (and far fewer mods). Does it work for everyone? No, but what software does?[/quote]

It should work for most people- if it doesn't it shouldn't be released. The issue is not with the Toolset.

- Ryan Paul Fialcowitz

[jlg1984]

I can't get the toolset to work, every time I try to start it, It says that the toolset needs to be configured, so I tried to configure, when I am done with that I try to open the toolset again and get the same message. My OS is Windows XP Profession SP3. I even tried Unistalling and then reintalling again, but still nothing. Anyone Have any Ideas as to what I may be doing wrong or how to fix this problem.

[Elvhen Veluthil]

jlg1984 wrote...

I can't get the toolset to work, every time I try to start it, It says that the toolset needs to be configured, so I tried to configure, when I am done with that I try to open the toolset again and get the same message. My OS is Windows XP Profession SP3. I even tried Unistalling and then reintalling again, but still nothing. Anyone Have any Ideas as to what I may be doing wrong or how to fix this problem.

Have a look at the wiki page about manual database installation and configuration:

http://social.biowar...se_installation

[jlg1984]

The SQL is installed not, But the toolset still doesn't work

[Rasputin]

I have the same problem Im going to read up on that last link provided... but, sadly its one more barrier to entry combined with the fact that DA2 toolset will probably be realeased soon and everyone will be modding for that anyway... so uh.. *shrugs*

[Beerfish]

When I've had problems in this regard I have always uninstalled everything, the toolset 1st then all of the 2005 sql stuff (or as much as it will let me). I then start over again and install again. Now this blows away any work you have already done so this is not the ideal solution if you have done work on stuff and then have more problems.

Also, there could be a problem with game version vs tooslet version perhaps? Not sure if that can be a problem or not.

[Oliver Sudden]

I can't get it up and running, either. Tried manual installs and everything, but still can't get the SQL server started during the install (mostly 1053 errors). Once I get told to check permissions on the server client I get hopelessly lost because I can't find what to fix (or how).

Not that I'm any sort of expert with SQL, mind you. I know just enough to pronounce it correctly.