RE: SP3 Invalid instance name
From: ntwkprof (ntwkprof@yahoo.com)
Date: 01/28/03
- Next message: Richard Waymire [MS]: "Re: Upgrading Sql Server 8.0.0.194 RTM"
- Previous message: Mike: "SQL Patch not working on Professional"
- In reply to: linda deng[MSFT]: "RE: SP3 Invalid instance name"
- Next in thread: linda deng[MSFT]: "RE: SP3 Invalid instance name"
- Reply: linda deng[MSFT]: "RE: SP3 Invalid instance name"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "ntwkprof" <ntwkprof@yahoo.com> Date: Tue, 28 Jan 2003 09:24:38 -0800
Sorry Linda...this dosen't work either.
>-----Original Message-----
>Hi James,
>
>The self-extracting file: SQL2KdeskSP3.exe (about 70MB)
from the Microsoft
>SQL Server Downloads Web site has included all of the
files that are
>required to install a new instance of Desktop Engine
(.msi files), to
>upgrade all existing instances of Desktop Engine (.msp
files), as well as
>to consume merge modules (.msm files) into applications.
It means that all
>the 16 MSI files and 16 MSP files have contained in this
SQL2KDeskSP3.exe
>file.
>
>The setup parameters are different from those parameters
used when applying
>MSDE SP2. For example, the parameter '/p' is replaced
with a new parameter
>'/upgradesp'. For more information on these parameters,
please refer to the
>section: '3.7 Install Desktop Engine SP3' in the readme
(sp3readme.htm)
>under the self-extracting folder.
>
>I have applied SP3 for a MSDE named instance (VSdotNet)
installed with
>VS.NET successfully on my test machine. Here is what I
have done:
>
>1). Extract this SQL2KDeskSP3.exe to the local folder,
say C:\sql2kmsdesp3.
>2). Check all the 16 MSI files and 16 MSP files under the
sub-folder
>.\Setup.
>3). Open a command prompt and change current directory to
C:\sql2kmsdesp3.
>4). Run the following command: (Assume that you use
Windows authentication
>to run the setup program to apply SP3)
>
>setup.exe /upgradesp SQLRUN INSTANCENAME=VSdotNet /l*v
C:\temp\MSDE_SP3.txt
>
>NOTE:
>a. If the MSDE instance in your situation is not a named
instance, but a
>default one, please remove INSTANCENAME= parameter from
the command above.
>b. '/l*v' is helpful when troubleshooting an
installation. It tells the
>setup program to generate the verbose installation log
file.
>
>c. Before running this command, please make sure that
your sa password is
>not a blank, because the setup program cannot proceed if
a blank password
>is detected, regardless of whether the MSDE instance is
using Windows or
>Mixed Mode authentication. There are two possible methods
you can choose:
>c-1. Before installation, please use sp_password to
specify a non-blank
>password for sa.
>or
>c-2. Add another setup parameter: BLANKSAPWD=1 into the
command to override
>the default behavior of the installer. For example,
>
>setup.exe /upgradesp SQLRUN INSTANCENAME=VSdotNet
BLANKSAPWD=1 /l*v
>C:\temp\MSDE_SP3.txt
>
>The use of blank passwords is strongly discouraged.
>
>d. You also can use the SQL Server authentication to
apply SP3 for the MSDE
>instance, if your MSDE instance supports this
authentication mode. For
>example,
>
>setup.exe /upgradesp SQLRUN INSTANCENAME=VSdotNet
SECURITYMODE=SQL
>UPGRADEUSER=sa UPGRADEPWD= sa_password /l*v
C:\temp\MSDE_SP3.txt
>
>5). The installation of the MSDE SP3 runs for a long
time. Please be
>patient with it.
>
>On my test machine, the setup program lasts about 30
minutes to finish
>applying SP3 for MSDE. Especially the last step: the
status bar reaches the
>end and the time remaining is 0 seconds, it seems that
the setup program
>hangs. Please take it easy, the setup program actually is
running some
>script files at the back-end. From the Task Manager, we
can see that the
>process: sqlservr.exe is active.
>Please apply SP3 on your MSDE instance after reviewing
the information
>above and the SP3 readme. If you still have the problem,
please view the
>installation log file: MSDE_SP3.txt generated during the
process.
>
>Please let me know if you have any further questions or
concerns.
>
>Sincerely,
>
>Linda Deng
>Microsoft Corporation
>
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>.
>
- Next message: Richard Waymire [MS]: "Re: Upgrading Sql Server 8.0.0.194 RTM"
- Previous message: Mike: "SQL Patch not working on Professional"
- In reply to: linda deng[MSFT]: "RE: SP3 Invalid instance name"
- Next in thread: linda deng[MSFT]: "RE: SP3 Invalid instance name"
- Reply: linda deng[MSFT]: "RE: SP3 Invalid instance name"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
