9 réponses à ce sujet

[kskh2o]

Hello,

I installed the toolset on XP SP2, and had the whole BSOD, enless restrat etc happen.  Anyhow, I booted in safe mode, and uninstalled SQL from programs in control panels (I have windows installer ennabled in safe mode).

However,

Uninstalling SQL from bottom to top as stated in the wiki, does not actually remove SQL from system entirely.  I had to go into services and disbale the three associated services in order to stop getting an error at start.  Now I cannot find a way to remove those service entries from the services tab.

Anyway SQL is 'mostly uninstalled' but now there is no way to uninstall the toolset. Since the toolset installation never completes on this botched XP SP2 install, there never was an uninstall file created nor does the toolset appear in Programs and settings for you to remove it.

Now at this point I've upgraded to SP3, and before I go ahead and even try to install the new Toolset, I was wondering how I can remove (uninstall) the botched installation on my system (toolset 1.00) remove the broken SQL services which did not uninstall with the removal of SQL from programs and settings, and basically get back to before hacing even tried to install the toolset.

Thanks for any help

[BryanDerksen]

As far as the SQL server stuff, we're not really sure how to clean up the mess - it's not our program. You may be able to Google up some Microsoft documentation on the matter. For the toolset all of the registry keys are in HKEY_CURRENT_USER/Software/Bioware/Dragon Age/Toolset, and the same path under HKEY_LOCAL_MACHINE. You can just delete both of those "Toolset" registry folders. And of course delete the tools subdirectory under the Dragon Age game folder, if that's still there.



However, I suspect you won't actually need to do any cleanup at this point. We've had no problems when doing test installs overtop of existing installations without removing them first. If you want to be as tidy as possible without delving into the intricacies of Microsoft's Knowledge Base, perhaps you could try installing 1.00 overtop of the old installation and then immediately uninstalling it again?

[kskh2o]

Thanks Bryan



I did go through pages and pages of MSKB and there is a lot of registry keys they mention. I ran across a lot of pages talking about incompatibility of MSSQL 2005 with .net framework (which I have installed) on SP3. So at least I am ready for another round of wrestling. =)



It's good to hear that at least I can install 1.01 on top of a botched 1.00 installation. If everything goes well with this installation big mac, I probably will not have to worry about actually cleaning things up as you said.



Thanks again for such a quick reply and heads up.

[BryanDerksen]

We've had a fair number of positive reports from people who have tried installing MSSQL 2008 instead of 2005, you might want to check up on that as an alternative. Assuming 2005 does cause you additional grief with that .net thing.

Modifié par BryanDerksen, 12 décembre 2009 - 12:22 .

[kskh2o]

No luck getting SQL Server 2005 installed and running. First the SQL Service fails to start. If I go into services and start it manually, I get the classic "SQL has encountered a problem and needs to close" error reporting window, and back to the service failed to start dialogue.



If I click cancel, basically the database fails to install and the toolset will not run. (failed to conect to DB message). I've started the download of SQL 2008, and will report how that went once it id done.

[kskh2o]

Wow, I finally got the toolset to work, with SQL 2008.  It took quite some time, more restarts than I care to remember, but I loaded into the toolset finally.

The "Manual Database Installation" wiki was very helpful in getting things running.

Just in case anyone else is trying to get the toolset to work with 2008, I was able to do it on XP SP3, with .Net 3.5 SP1 installed (required for SQL 2008 anyway).  And below is the general coruse of action I took in order to make it work.

Since I never touched SQL before or any database management for that matter, the following description I have may have superflous steps to it, but at least things are working.

2005, was not installing (at least the toolset installer was not installing 2005 on my XP SP3 with .NET 3.5).  The service would fail to start.  So I ran along and got

SQL 2008 Express, .NET 3.5, Windows Installer 4.5, Windows Powershell.

If you havet already done it, you need to patch .NET to 3.5 SP1, update windows installer to 4.5 and install windows powershell in order to be able to install SQL 2008 successfully.

I Installed all of the above with the default settings, I checked every single optional component to install under SQL 2008. 

One dialog came up where I had to assign a different user to the SQL 2008 services.  I picked LOCALSYSTEM for SQL Server and LOCAL SERVICE for the otehrs (except  SQL Server Agent Service which got NETWORK SERVICE but was disabled and not running so I don't think it matters)

Installation completed successfully for once, and I was able to launch SQL Server Management studio.

From there on, it was pretty straightforward, using the Manual Install Wiki

Two things that kept me from connecting were:

When creating the new database as per the wiki, you need to select SQL 2005 compatibility mode.  I did this throught he properties dialog of the bw_dragonage_content db after having created it.

I assigned an owner (my user on the computer) through the properties>Files dialog [This might not be necessary]

In the configuretoolset utility, I had to manually enter some parameters.
Server Name:  I had to enter the Server name found in the properties dialog of SQL Management Studio, which was COMPUTERNAME\\SQLEXPRESS  (computername is YOUR computer name).

Tested the connection in the configuration utility and was able to connect.

Then as the wiki said, I had to edit the registry to modify the server name in the key as the configuration utility did not change the registry (1.01 does not seem to have fixed that).

Once all that was done I was able to run the toolset, connect and get started on learning how to use this puppy.

Hope this helps anyone else on the same boat as me.

[xcorps]

All I can say is I sure hope you get a lot of enjoyment from the TS. You earned it.

[DjDeni]

Thak You partner for this!!!.. I have a lots of problems right now..and You are my solution! Thank You and the guys @ tje Bioware!

[DjDeni]

Guess its not so easy as i thought.. can you tell me how to get this sql studio working? i fail to connect ..what do i nedd to write in the dialog under

server name:? (i guess mycomputername\\sqlexpress

authentification:? (i guess Sql server)

Login:dont know or remeber

password:i know it as i had to write it somewhere during the instalation.. but there was no Login name..



i get this message:

TITLE: Connect to Server

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



Cannot connect to Rahzel\\sqlexpress.



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

ADDITIONAL INFORMATION:



A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)



For help, click: http://go.microsoft....33&LinkId=20476



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

BUTTONS:



OK

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

[DjDeni]

FORGET IT!!!!



I GOT IT!!!!



Works like a CHARM..

I did a little mistake.. and dind know how to set SQL Server to work.. :/



Sorry to bother You guys..



It took me 8-10 hours to meki it work..but beeing hard headed as always i finnaly got it..

Already working on the new adventure.. The quest for the Chrome

hehehhh..



Thanx Guys once again for help !