22 réponses à ce sujet

[Eidolonn]

Curious.  Is the toolset compatible and/or supported with SQL 2008 Express?

[BryanDerksen]

We've never tested it.

[Eidolonn]

Okay, thanks. I will try it when I get home from work and post the results unless someone beats me to it.

[RanosB]

I'm currently having trouble getting it to work with 2008 express, I'm getting database connection problems.

Modifié par RanosB, 06 novembre 2009 - 07:28 .

[Eidolonn]

RanosB wrote...

I'm currently having trouble getting it to work with 2008 express, I'm getting database connection problems.

Did the database get created? If so, did you try putting it in Type 90 (i.e. SQL 2005) mode?

[RanosB]

No it seems I have some issues on my computer. First 2008 wont uninstall, in safe mode I get setup errors, in normal I get restart required every time I try it(even after restarts). Also I get Critical errors when trying to uninstall MSXML6 Like is suggested to get 2005 to work. So I'm thinking I've got some serious issues here.

[Eidolonn]

Someone referenced in another thread that they had it working with SQL 2K8.

[RanosB]

Well I done messed up my installation of windows lol. Time to start backing up and doing the grand ole reformat. I'll be back later with my update.

[ToddWalter]

I'm trapped in this cyclic hell as well. SQL 2008 will not instantiate properly (claims it cannot create tempdb on a drive with loads of space, when its not looking for files on a non-mounted E:\\) It also will not uninstall which makes going back to SQL2005 problematic. Appears to be left-over cruft from VS2005 Express that causes the 2k8 installer to think it is an upgrade as opposed to a new instance. How easy is it going to be to re-download the extra content once I wipe my drive & re-install?

[ToddWalter]

Solved my own problem, at least. Hopefully this info will aid others.



Used the method for smiting SQL 2008 in the manner it deserves from the following link:



http://mark.michaeli...lNightmare.aspx



After that, when SQL 2005 fails to install during a re-install of the toolset I changed the service logon account from "Network Service" (which failed to work even after being dropped into the "Administrators" group) to "Local System" and pressed "retry". Completes successfully.

[RanosB]

Well I'm back with a fresh install of windows and sql 2008 installed completely this time. Even got the management studio to install. So I'm thinking that once I get DAO installed and the toolset going, it will work.

[marco0009]

I cannot get the toolset to startup (using 2k8). Using the Configuration Utility, the Test Connection button says the test connection succeeded. Starting the toolset yields the following error: "Unable to connect to database... Run the toolset configuration program and verify your settings or search the toolset wiki..."

I get the following log entries after it exits:

Fri Nov 06 21:15:13 2009, INFO, "C:\\tag\\main\\dev\\tools\\sdk\\src\\PluginAPI.cpp", 106, "Initializing toolset."
Fri Nov 06 21:15:15 2009, ERROR, "d:\\DASecuROMBuild\\main\\dev\\tools\\sdk\\include\\toolsoledb.h", 226, "Invalid object name 't_GlobalParameters'."
Fri Nov 06 21:15:15 2009, ERROR, ".\\ConnectionData.cpp", 214, "CConnectionData::ConnectIO caught an exception: Bad HRESULT: 80040e37"

Modifié par marco0009, 07 novembre 2009 - 03:33 .

[marco0009]

Looking around tells me this is the result of it not being able to find the tables in my database. Are there database files somewhere that I can use to import the content db onto my server?

[marco0009]

Found the database bak file and using the Management Studio restored the bw_dragonage_content database, all seems to be working fine now.

[toddhd]

Marco - Thank you!!! I was banging my head against the wall with that darn error. I too was sure my login credentials were good, and getting the same error. I had assumed that the editor would realize that the db was empty and create the neccessary entries. Once I found the *.bak file and restored it, the editor started right up! I'm on SQL 2008 as well, so it seems to work just fine. Well, let's just say it at least passes the smoke test of launching...

[RanosB]

How did you restore the backup?

[marco0009]

Connect to your server in the SQL Management Studio. Right click the Databases folder and choose Restore Database. In the to Database field enter bw_dragonage_content. For the source choose From device and click the ... button. Leave backup media as file, click Add and navigate to Program Files\\Dragon Age\\tools\\dbbak and select bw_dragonage_content.bak. Click OK on both the open screens, make sure the check box under the restore column is selected and click OK

If all goes well your database should be functional

Modifié par marco0009, 07 novembre 2009 - 05:39 .

[RanosB]

oh I figured it out lol

[RanosB]

marco0009 wrote...

Connect to your server in the SQL Management Studio. Right click the Databases folder and choose Restore Database. In the to Database field enter bw_dragonage_content. For the source choose From device and click the ... button. Leave backup media as file, click Add and navigate to Program Files\\\\Dragon Age\\\\tools\\\\dbbak and select bw_dragonage_content.bak. Click OK on both the open screens, make sure the check box under the restore column is selected and click OK

If all goes well your database should be functional

Ahh I used the restore.bin at \\Database Utilities\\backup_restore

[LionFranco]

Argh! I finally dealt with the MSXML6 thing, and now i'm having the database issue, and not sure how to resolve it. This is what it is telling me now, and while i think it is related to what you guys are talking about, i cannot seem to fix it.



TITLE: Microsoft SQL Server 2005 Setup

------------------------------



SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]CREATE DATABASE failed. Some file names listed could not be created. Check related errors.. Refer to the server error logs and Setup logs for detailed error information.



Anyone have an idea how to fix this? I really want to get the toolset working so i can get familiar with it. And the whole finding the protect folder and unchecking "Use simple file sharing (Recommended)" thing from the wiki doesnt work, as that command doesnt exist (WinXPSP3).



Any help would be greatly appreciated.

[Bronyaux]

Thanks for this thread. I have Steam and an existing SQLEXPRESS and I was having a bugger of a time getting the toolset to run (Error: Unable to connect to database). The main problem seems to be that the database wasn't restored properly on install. Thanks to this thread I found the restore batch file and tried to run it.

Just running the batch will NOT work if you don't install to the default location (e.g. Steam), because it expects the default paths to be present. I just took the sqlcmd and modified it, then ran it in a command window. If anyone is like me, here you go:

>sqlcmd -S .\\SQLEXPRESS -E -Q "RESTORE DATABASE bw_dragonage_content FROM DISK = 'c:\\Backups\\DABackup001.bak' WITH REPLACE, MOVE 'bw_dragonage_content' TO 'E:\\Steam\\steamapps\\common\\dragon age origins\\tools\\toolssql\\Data\\bw_dragonage_content.mdf', MOVE 'bw_dragonage_content_log' TO 'E:\\Steam\\steamapps\\common\\dragon age origins\\tools\\toolssql\\Data\\bw_dragonage_content.ldf' "

Note that you need to change the file paths to match what you've got running. The c:\\Backups\\DABackup001.bak was just a copy+rename from the file in tools\\dbbak\\bw_dragonage_content.bak. And your steam might not reside in E:

After I ran that and connected the database in the toolset config app, everything seems to work. Well, at least so far.

Hope this is a useful resource.

[cjb110]

I got it installed ok on SQL Express 2008 SP1 64bit and Win7...though having SQL services disabled while installing doesn't help!



Getting Management Studio installed was the hardest! I really don't know how they can keep making wizards so dumb.



When I restored the toolset db I had the log ldf on C:\\*SQL Default* and moved the data mdf to another drive.



Once I had it looking up in SSMS, I ran the config prog to change the connection string and it loaded, loaded the tavern ok...not done more than that though at the moment.

[cjb110]

LionFranco wrote...
SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]CREATE DATABASE failed. Some file names listed could not be created. Check related errors.. Refer to the server error logs and Setup logs for detailed error information.

Anyone have an idea how to fix this? I really want to get the toolset working so i can get familiar with it. And the whole finding the protect folder and unchecking "Use simple file sharing (Recommended)" thing from the wiki doesnt work, as that command doesnt exist (WinXPSP3).

Any help would be greatly appreciated.

Sounds like the path could be too long...where are you installing it to?
SQL seems to have some crappy <60 char path limit.