Aller au contenu

Photo

Don't Install the toolset if you are running Windows XP Service Pack 2 or lower


75 réponses à ce sujet

#1
Allan Smith

Allan Smith
  • BioWare Employees
  • 83 messages
There is a bug in MS SQL Server 2005 (which is installed as part of the toolset) than may send your computer into an endless reboot cycle.

If you are running XP please make sure you are on SP3 before you install the toolset.  This is not an issue with Vista or Windows 7 installs. 

If you are already into this loop, help can be found in the following thread.
http://social.biowar.../index/110833/2

Modifié par Allan Smith, 10 décembre 2009 - 11:05 .


#2
Varenus Luckmann

Varenus Luckmann
  • Members
  • 2 891 messages
...I know it's a bit of a tirade and throw around frequently, but: Was the toolset tested at all? :P

#3
Eidolonn

Eidolonn
  • Members
  • 252 messages

Varenus Luckmann wrote...

...I know it's a bit of a tirade and throw around frequently, but: Was the toolset tested at all? :P


I know it was unclear, since they spelled it out in plain English, but the problem was with SQL 2005, not the toolset.

Modifié par Eidolonn, 07 novembre 2009 - 02:40 .


#4
kurokaz3

kurokaz3
  • Members
  • 9 messages
The DA:O system requirements state that the game requires SP3. It runs reasonably well on SP2, but since SP2 is below their minimum target requirements, they really can't be blamed for not testing it thoroughly. It should be pretty generally understood that running below minimum requirements might not always work properly.



The bug is rather more severe than one would expect, but it's actually a bug in a Microsoft product, not a Bioware one. Bioware can only be held accountable in that they didn't test it on SP2, and honestly, why would they?

#5
avenger_teambg

avenger_teambg
  • Members
  • 82 messages
The installer could check and at least print a warning, instead of a random forum message?

I just installed it before i had a chance to read this, luckily i got sp3.


#6
AnTeevY

AnTeevY
  • Members
  • 109 messages
Well why would they print out a warning when they haven't tested it and therefore did not know of that bug? I think none of us beta testers got SP2.

Modifié par AnTeevY, 07 novembre 2009 - 10:33 .


#7
Nudo Judo

Nudo Judo
  • Members
  • 18 messages
Huh, sucks for us XP x64 users. I wonder if MySQL 5.1 could work with this.

EDIT: I decided to give it a go and MSSQL isn't giving me any booting issues.  And the toolset runs fine.  But I'm just one person, so my report is probably worthless and I wish I could delete this post.

Modifié par Nudo Judo, 07 novembre 2009 - 01:58 .


#8
Allan Smith

Allan Smith
  • BioWare Employees
  • 83 messages

avenger_teambg wrote...

The installer could check and at least print a warning, instead of a random forum message?
I just installed it before i had a chance to read this, luckily i got sp3.


Agreed.  We are hoping to have the next version of the installer check the service pack  and refuse to install if you don't have SP3.  We certainly would not have let this go out like this if we had been aware of this particular bug.
The game requires SP3, but it will install regardless.  We did not explicitly test XP SP 2 for the toolset as it was not supported.  It was only after we released it and people started installing the toolset with SP2 that we ever saw the issue.

#9
BlackLotus123

BlackLotus123
  • Members
  • 2 messages
Grrr!!! The Install hangs up when it reaches Execute:regsur32.exe line!!!!

#10
katt2001

katt2001
  • Members
  • 8 messages
i already have ms sql 2008 installed on my machine. will the installer check that and not install 2005 as well?




#11
InternHertz

InternHertz
  • Members
  • 1 messages
I didn't read the system requirements prior to installing it, and my Windows SubSystem got corrupted, causing the pc to go BSOD at every reboot...



Thankfully I was able to recover from the problem, went here to see if it was a bug or me being unlucky.



Now that I know I shouldn't install this on XP SP2, I feel a bit silly. Anyhow, I'll install it on Win 7 and hope it doesn't corrupt the system anymore.

#12
phordicus

phordicus
  • Members
  • 640 messages
i'm very curious why someone would run an obsolete version. the obvious answer is pirated OS. just wondering what the technical reasons are.

#13
DSWDalish

DSWDalish
  • Members
  • 137 messages
Ok im updating my xp to service pack 3 should i be fine? Oh Thank you read other posts.

Modifié par DSWDalish, 07 novembre 2009 - 11:59 .


#14
XavierGrimwand

XavierGrimwand
  • Members
  • 32 messages
I'm running XP-64 SP2, and the game plays just fine. I also keep Windows up to date with Microsoft updates, but haven't installed SP3 as it's just a cumulative update. If I install the toolset will I have issues, or will it work on a fully patched XP-64 SP2 install?


#15
Shade692004

Shade692004
  • Members
  • 1 messages
How do I update my windows from sp2 to sp3? I ran windows update but I don't see anything regarding sp3.

#16
sirkaracho

sirkaracho
  • Members
  • 52 messages
here is where i got my sp3:



http://www.chip.de/d...3_29821545.html



its a german page, but that shouldnt be a problem, the two buttons you have to click are pretty obvious, cant remember if there where instructions to follow while installing in german



microsoft.com should have an english version anyway, should be no big deal to find it :)

#17
DarkZaleth

DarkZaleth
  • Members
  • 4 messages
Well I have to say this is not good since I can not have Service Pack 3 with xp due to athlon Processors not playing nice with it. I have waited years for this game to come out so this is a big disappointment for me. I would hope you get it fixed to work with sp2 I know Iam not the only person with this issue.

#18
kalniel

kalniel
  • Members
  • 45 messages

DarkZaleth wrote...

Well I have to say this is not good since I can not have Service Pack 3 with xp due to athlon Processors not playing nice with it. I have waited years for this game to come out so this is a big disappointment for me. I would hope you get it fixed to work with sp2 I know Iam not the only person with this issue.

My Athlon processor works great with SP3.

#19
Lethe Vas'Dur

Lethe Vas'Dur
  • Members
  • 30 messages
SP3 installs a couple things no self respecting admin would ever put on a machine which is why there is an option to not install SP3 and just get the updates.



But the only thing I can see bioware needing from SP3 is the hot fixes, XML6, and the dot not pieces. Which are all updates that you get from windows update. I can see them saying you need SP3 so that they now you have those by default.



But none of that should matter if you have a fully updated SP2 unless they found a way to make NAP work across an internet connection,,,

#20
KeiraMetari

KeiraMetari
  • Members
  • 2 messages

Nudo Judo wrote...

Huh, sucks for us XP x64 users. I wonder if MySQL 5.1 could work with this.

EDIT: I decided to give it a go and MSSQL isn't giving me any booting issues.  And the toolset runs fine.  But I'm just one person, so my report is probably worthless and I wish I could delete this post.

 
 XP64 works well with toolset and SP2. XP64 is actually server 2003 internally, with some XP features/package/looks dropped on top of it. So SP2 for XP64 is not the same as SP2 for XP32. You should have no problems, in fact it would not suprise me in the slightest if both DAO and the TS work best on XP64 ( especially the toolset, provided you have 8GB RAM).

 No need to delete the post, XP64 should work fine for everyone - or at least it will not be effected by this issue.

Modifié par KeiraMetari, 08 novembre 2009 - 10:43 .


#21
Morlan78

Morlan78
  • Members
  • 2 messages
I also got the reboot error, i thought i had SP 3 installed but didnt.

After i installed service pack 3 i ran the toolset installer again, only to get errors for the msxml 6.0 Sp2 part, and the sql server parts when installing the  sql server. After searching on google i found out that the xp sp3 was causing this error(a known issue), and had to remove the msxml 6.0 Sp2 by using an utlity tool. So then i ran the toolset installer yet again, and everything seemed to have been installed correctly, but when i try to start the toolset i still get the error message saying: "Unable to connect to the database. I have run the toolset configuration utility...etc".

So when i try to run the configuration tools, i get an error when testing the connection to the db: "Cannot open database bw_dragonage_content". when trying to choose a database the dragonage database isnt an option. I only get these: master, model, msdb, and tempdb. So it seems the db for dragonage content  db isnt there.

Any advice on how to solve this?

*EDIT*
I got it to work. Had to restore the db from the .bak file as described in the troubleshooting wiki. I got an error first due to the security settings on the dragon age folder, after i changed the security settings to "grant all", i successfully got the db restored.

Modifié par Morlan78, 08 novembre 2009 - 11:38 .


#22
Ainiana

Ainiana
  • Members
  • 45 messages
i am only on SP2 (but fully updated, IT pro friends said not to get SP3 ages ago so i have never got it).

The toolset installed and loads up fine, although i have not used it really yet other than to see differences between NWN2 toolset (and that was long before i saw this message)

#23
Scrangos

Scrangos
  • Members
  • 13 messages
Ops I installed it before seeing this. I was thrown in the loop of doom. I disabled the services from auto starting in safe mode and manually uninstalled mysql (the later being a pain in the ass) to try and install again.... I luckily found this just as I was gonna try again. I'm gonna poke around for a fix without SP3.

#24
alkemi

alkemi
  • Members
  • 7 messages
Wish I would have noticed this thread earlier :P I did, however, manage to get it out of the endless loop by hitting F8 and going to 'last known good config', haven't done anything else with it yet. Seems like an awful lot of trouble though.

#25
DarwinBC

DarwinBC
  • Members
  • 4 messages
This sucks, I have an asus mobo that doesn't play nice with sp3 so I guess I'm out of luck with the tool set.