Sql Server 2000 SP3a - Dahotfix error
-
Hi,
I'm, trying to install 'sql2ksp3.exe' for SqlServer and thereafter 'sql2kasp3.exe' fro Analysis Services but...
I get an error 'Dahotfix has encountered a problem and....'. It happens soon after the upgrade sql scripts have run (sql2ksp3.exe)
I can't wait for too long. If there isn't any solutions I will continue with SP2 level. I don't know whether my SqlServer master db is healthy now or not - Select @@version returns ....SP2.
The reason I decided to upgrade sp2 to sp3 was actually problems with Olap Cube 'Browse data' - unspecified error....It seems that many weird problems have started to happen after WinXP sp2??
Regards, Ville
-
Not sure if you've looked at these but will post anyway. I haven't done the XPSP2 thing yet, but you may need to do the enabling of the apps prior to trying to execute the SQL Sp's?
http://support.microsoft.com/kb/841249
http://support.microsoft.com/kb/841256
http://www.windowsitpro.com/Articles/Index.cfm?ArticleID=43777&DisplayTab=Article
http://support.microsoft.com/kb/841549
Some of these reference each other and I'm sure many mor ewill surface from the links contained within.
Good luck!
Steve.
-
Thanks,
I read these articles and some other linked to these but unless I missed some crucial part, I still can't update SqlServer/Analysis S with sp3...
I allowed 'Sqlservr.exe' and Analysis services 'Msmdsrv.exe'+port 2725 through the windows firewall and my Sygate fw as well. I also tried the update while winfwall was 'Off'. I tried to connect with integrated security while upgrading but ==> 'dahotfix has encountered a problem...'
Referring to my other thread (Analysis Services) since these must be related:
...and I was able to connect/browse cube data once but only once. First I thought it succeeded after the failed sp3 upgrade because some of the files might already have changed but then after disconnect and retry ==> no luck
Ville
-
Ok, pulling at straws now, but you could try the suggestion in http://support.microsoft.com/Default.aspx?kbid=837188
from a msft transcript re: SP3 -->
Let's move to setup do's and don'ts (slide 11). As I said, always look through the Sp3readme first. That's going to have all the updated information from our side and everybody else's for information that we couldn't get to you either through this venue or through any other. Stop services before upgrading. That's going to be the best course of action if you want to avoid any kind of deadlock situations. Always refer to your logs at the end of setup if you do have questions. The ones of note for setup are Sqlsp.log, Dasetup.log, and .log. There are also .out files in the case of script failures. When setup asks you to backup your databases, please always do heed those warnings.
(the url for this transcript is http://support.microsoft.com/?scid=http://support.microsoft.com%2Fservicedesks%2Fwebcasts%2Fen%2Fwc121002%2Fwct121002.asp 
Steve.
-
Yep, you pulled the right straws, thank you.
Strangest thing (if possible with upgrades nowadays) though...the article
http://support.microsoft.com/Default.aspx?kbid=837188 suggests the logfile (dahotfix.log) is either locked, read-only or hidden attribute set. None of these seemed to apply in my case. Deleting the file did help as instructed though.
The setup (SqlServer sp3) run OK and thereafter also the Analysis Services setupsp3. ==>
1. Analysis Manager connection succeeds now every time and is fast and the cube works OK
2. 'Select @@Version' in Q Analyser still returns
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
Is my sql Server really upgared after all?
Thanks again, Ville
-
Glad you got it going.
The Service Pack 2 refers to the Win NT5.1 (ie Win XP), the version is correct for SQL SP3.
Cheers,
Steve.
Steve.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply