Post reply

SQL 2000 SP3

  • January 30, 2003 at 4:53 am

    #447578

    I had major headaches trying to egt sp3 installed. In the end I had to change the registry to egt the thing past authentication:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo\DSQuery

    value to "DBNETLIB".

    It seems MDAC 2.6 and under can't authenticate to even start the install. This came from MS, but took ages to find.

  • February 3, 2003 at 11:14 am

    #447854

    I've had an authentication/validation issue on 3 different machines at the beginning of the install, regardless of whether I use sa or a domain sysadmin/local admin account. Is this what you were referring to as the MDAC issue? Did you have to change the registry key back after completing the install? Finally, do you have a link for the MS article that gave you the answer?

    Thanks mucho.

  • February 3, 2003 at 1:09 pm

    #447878

    Haven't seen a KB article on it, yet, but it is in the Microsoft public newsgroups.

    HTML access is here:

    http://www.microsoft.com/sql/community/newsgroups/default.asp

    K. Brian Kelley

    http://www.truthsolutions.com/

    Author: Start to Finish Guide to SQL Server Performance Monitoring

    http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1

    K. Brian Kelley
    @kbriankelley

  • February 3, 2003 at 2:17 pm

    #447891

    Microsoft Knowledge Base Article - 328306

    talks about it about 3/4 of the way down

  • February 3, 2003 at 2:49 pm

    #447905

    Some of the issues are being answered by "Install MDAC 2.7 first manually" which isn't just the registry setting.

    K. Brian Kelley

    http://www.truthsolutions.com/

    Author: Start to Finish Guide to SQL Server Performance Monitoring

    http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1

    K. Brian Kelley
    @kbriankelley

  • February 4, 2003 at 9:33 am

    #447998

    After SP3 installation two machine upgrade from SQL 65 to SQL 2000 is failing during export and import using name pipes with following message. Both machines running on domain account (members of Local Admins).

    Export.exe on the remote machine was hung...

    Export Exit Code: 259 - export.exe -CodePage 850 -DeviceType Pipe -AllTables yes -MasterPath C:\MSSQL\DATA\MASTER.DAT -DatabaseName Bars -DevicePath \\.\pipe\~cnvpipe0

    Import Exit Code: -1 - ~cnvpipe0

    Msg 4854, Level 21, State 1, Server DB01, Procedure , Line 1

    [Microsoft][ODBC SQL Server Driver][SQL Server]****

    Time:01-30-2003 14:14:51.433

    Error return from function CreateFile

    in file CnvPipe.cpp

    Line=143

    rc=5

    Msg=Access is denied.

    Has anyone faces similar problem?

    Thanks,

    sreeni

  • February 4, 2003 at 10:14 am

    #448006

    I have just installed SQL 2000 Enterprise edition onto a brand new Windows 2000 machine. Being good I applied SP3 to SQL and now when I try to look at the master database in Enterprise Manager Taskpad view I get

    An error occurred in the script on this page

    Line: 307

    char: 2

    Error: Unspecified error

    Code: 0

    URL: res://C:\Program%20Files\Microsoft%20SQL%20Server\80\Tools\Bin\Resources\1033\sqlmmc.rll/tabs.html

    Do you want to continue running the script on this page

    Yes No

    I can look at all the other system databases via taskpad view.

    Would my best option be to uninstall SQL Server 2000 Enterprise Edition and start from fresh? Or has anyone any idea why I get this problem?

  • February 4, 2003 at 10:17 am

    #448009

    I can remember having that with 1 customer but seem to remember also that i just switched the view off of TaskPad - it all functioned OK despite this. Something to do with IE do you think?

  • February 4, 2003 at 1:17 pm

    #448029

    I have applied SP3 to numerous SQL Server 2000 boxes in our environment and have not had any major problems. But, I did run into a issue with a JDBC driver from BEA. After application of SP3 the Java component of the application quit working. We applying an updated JDBC driver from BEA today.

    Regards, Jason

  • February 4, 2003 at 2:48 pm

    #448039

    We've installed about 6 without any major incident. However, on one install we are seeing a memory error for sqlmanager on startup.

    One Question:

    When rolling back SP3 is it necessary to restore all the databases or just attach them???

  • February 5, 2003 at 7:07 am

    #448084

    Quote from firthr:

    "It seems MDAC 2.6 and under can't authenticate to even start the install."

    I ran into this (i.e., SP3 would not authenticate via Windows authentication or via the sa password) on one machine during an "upgrade" from SP2 to SP3 with MDAC 2.6. I installed MDAC 2.7 Refresh, and SP3 ran fine.

    THANKS for your post, firthr!

    So far, all fresh installs of SQL 2000 and SP3 have gone fine.

  • February 6, 2003 at 5:58 am

    #448200

    We are on a big kick to get all of ours that we can to SP3. We have installed 5 test servers and 2 prod servers with SP3 from SP2 and SP1. So far all is OK.

  • February 6, 2003 at 2:53 pm

    #448296

    Rollout of sp3 went smoothly accross 2 production servers, 1 development and 8 MSDE systems. However one fell over (a 24/7 production system.) This was due as far as I could tell on a Java app that aggressively polls the SQl server. Still not 100% on why it fell over, and this is not the point of this post. The server reports itself as sp3 and after an initial problem has stayed up without a problem for a week. I only had a 1 hour window in which to install the sp3 on two machines at the time. Now Sp3 will not log into the server to reinstall, which was a more attractive option to rebuilding the entire server. The reg key for the client connection is fine (DBNETLIB), but the MDAC Utility: Component Checker has revealed the problem, a functional(it is running) but inconsistant MDAC. this tool can be found here:

    http://www.microsoft.com/downloads/details.aspx?FamilyID=8f0a8df6-4a21-4b43-bf53-14332ef092c9&DisplayLang=en

  • February 10, 2003 at 3:55 am

    #448493

    quote:

    I can remember having that with 1 customer but seem to remember also that i just switched the view off of TaskPad - it all functioned OK despite this. Something to do with IE do you think?

    I have occasionally had this problem ever since installing SQL2K, and it has persisted through all service packs to data. I just switch from Task Pad view to any other view and back again and the problem goes away!

    Tony Bater


    Tony

  • February 10, 2003 at 7:09 am

    #448517

    Grouping a few of these together:

    • If you run into the authentication issue, try installing MDAC 2.7 SP1 from http://www.microsoft.com/data and then re-attempt the service pack. MDAC installations with service packs seem to be fraught with issues.
    • When rolling back, here's the procedure: uninstall SQL Server, reinstall SQL Server, bring it back up the previous service pack, hot fix, restore system databases. I believe the user databases can be reattached... I don't remember SP 3 doing anything to change them. To be safe, make sure you have full backups before applying SP 3.
    • The Taskpad view is a big annoyance, and the typical advice has already been stated here: switch to a view other than Taskpad and switch back.
    • natasreeni, are you failing on the upgrade from SQL 6.5 to 2000 or in the applying of SP 3 after you've upgraded?

    K. Brian Kelley

    http://www.truthsolutions.com/

    Author: Start to Finish Guide to SQL Server Performance Monitoring

    http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1

    Edited by - bkelley on 02/10/2003 07:10:32 AM

    K. Brian Kelley
    @kbriankelley

Viewing 15 posts - 16 through 30 (of 54 total)

You must be logged in to reply to this topic. Login to reply