sql server msde: I have a customer who bought a Dell computer that has an instance of MSDE
already on it "MICROSOFTSMLBIZ." I guess this is for Outlook 2003 business
contact manager. I installed another instance of MSDE (with SQL
authentication) before I realzied that was on there and rather than giving
mine an instance name it went on as the default. I've read over various
posts in groups to see what I'm doing wrong but having no luck. I have read
section 3 "Service Pack Installation" of the htm file. Here's what I have
tried running a few times:

setup /upgradesp sqlrun SECURITYMODE=SQL UPGRADEUSER=AnAdminLogin
UPGRADEPWD=AdminPassword /L*v C:\MSDELog.log

When it's done, it just gets back to the command prompt. There are no
warnings or messages there. But every time I get a very large log file that
near the end says that it failed. When I run @@VERSION I should get:

[Microsoft][ODBC SQL Server Driver][SQL Server]Microsoft SQL Server 2000 -
8.00.2039 (Intel X86) but I don't. It's still version 8.00.0760

Can anyone tell me what might be wrong? I'd rather not uninstall version 3
and then reinstall version 4 but I will if necessary. It's not that big of a
deal. But I'd like to know how to do this correctly in case I run into it
again.

Thanks,

Keith

hi Keith,
[quoted text, click to view]

probably the "old" instance you are trying to upgrade is not a default
instance but a named instance (MICROSOFTSMLBIZ)... if this is the case,
provide the additional parameter INSTANCENAME=MICROSOFTSMLBIZ

but what is strange to me is the fact that it seems you the result of your
operation is the installation of a default instance, but the /upgradesp
SQLRUN parameter should actually report "This product is not installed.
Check if a appropriate instance of MSDE is installed." exception..
please check your C:\MSDELog.log to further info of your installation...
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
--------- remove DMO to reply

Thanks Andrea but I'm not trying to upgrade the MICROSOFTSMLBIZ instance. I
don't care about that instance at all. What I need to do is to upgrade the
one that I installed that does not have an instance name (or rather that I
didn't give an instance name when I installed it).

Can each instance be updated independent of the others? Are they totally
separate installations?

Here's the last part of the upgrade log:

=== Logging stopped: 10/18/2006 13:51:24 ===
MSI (c) (3C:9C) [13:51:24:515]: Note: 1: 1729
MSI (c) (3C:9C) [13:51:24:515]: Product: Microsoft SQL Server Desktop
Engine -- Configuration failed.

MSI (c) (3C:9C) [13:51:24:515]: Grabbed execution mutex.
MSI (c) (3C:9C) [13:51:24:515]: Cleaning up uninstalled install packages, if
any exist
MSI (c) (3C:9C) [13:51:24:515]: MainEngineThread is returning 1603
=== Verbose logging stopped: 10/18/2006 13:51:24 ===

Rather than posting the entire log, what in there would help someone see
what's wrong?

I guess the other thing I'm wondering is when you install an un-named
instance of MSDE where a named instance already exists, does the
installation give it a name? or is it still just "local" or the machine
name?

Maybe the best solution at this point is to unistall my unnamed instance and
reinstall it with a name?

Thanks,

Keith

[quoted text, click to view]
hi Keith,

[quoted text, click to view]

Thanks for your help on this. I would rather understand than kill it and
start over.

When I installed my unnamed instance I never set DISABLENETWORKPROTOCOLS=0
so according to the help file I shouldn't need that right?

Here is where there are instances of RETURN VALUE 3:

MSI (s) (FC:30) [13:50:58:859]: Doing action:
UpgDetectBlankSaLogin.2D02443E_7002_4C0B_ABC9_EAB2C064397B
Action start 13:50:58:
UpgDetectBlankSaLogin.2D02443E_7002_4C0B_ABC9_EAB2C064397B.
MSI (s) (FC:D0) [13:50:58:875]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI9E.tmp, Entrypoint: UpgDetectBlankSaLogin
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{689404D2-1C94-44B3-9203-BEC5594FDA7A}
TempFolder is
C:\DOCUME~1\Admin\LOCALS~1\Temp\{689404D2-1C94-44B3-9203-BEC5594FDA7A}\
Loading extended custom action library
C:\DOCUME~1\Admin\LOCALS~1\Temp\{689404D2-1C94-44B3-9203-BEC5594FDA7A}\sqlca
x.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{689404D2-1C94-44B3-9203-BEC5594FDA7A}
Starting custom action UpgDetectBlankSaLogin()
Entering Function MyMsiEvaluateCondition
MsiEvaluateCondition for VersionNT returned TRUE
End Function MyMsiEvaluateCondition
An error was encountered during connection to server: 3
Ending custom action UpgDetectBlankSaLogin().
Action ended 13:51:24:
UpgDetectBlankSaLogin.2D02443E_7002_4C0B_ABC9_EAB2C064397B. Return value 3.
Action ended 13:51:24: INSTALL. Return value 3.
Property(S): UpgradeCode = {421A321C-2214-4713-B3EB-253F2FBCCE49}


And here:

Property(S): AgentServiceName = SQLSERVERAGENT
Property(S): InstanceRegKey = MSSQLServer
Property(S): InstanceSubDir = MSSQL
Property(S): SqlPerfMonRegKey = SQLCTR
Property(S): SQLServiceName = MSSQLSERVER
Property(S): SqlStates = 134382085
Property(S): MSDE8Upgrade = 1
Property(S): SqlRestartService = 0
Property(S): SqlStartType = 2
Property(S): SqlServiceType = 16
Property(S): ROOTDRIVE = C:\
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): SqlFeature = SqlRun
MSI (s) (FC:30) [13:51:24:484]: MainEngineThread is returning 1603
MSI (s) (FC:80) [13:51:24:484]: Destroying RemoteAPI object.
MSI (s) (FC:84) [13:51:24:484]: Custom Action Manager thread ending.
MSI (c) (3C:9C) [13:51:24:484]: Back from server. Return value: 1603
MSI (c) (3C:9C) [13:51:24:484]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
Action ended 13:51:24: INSTALL. Return value 3.
Property(C): UpgradeCode = {421A321C-2214-4713-B3EB-253F2FBCCE49}
Property(C): ProductName = Microsoft SQL Server Desktop Engine
Property(C): VersionNT = 501


Thanks,

Keith

hi Keith,

[quoted text, click to view]

to "upgrade" a default instance, installed like
c:\MSDERelA\>setup.exe SECURITYMODE=SQL DISABLENETWORKPROTOCOLS=0 SAPWD=xxx
/L*v "C:\Msde3.txt"

you only need something like
c:\SQL2KSP4\MSDE\>setup.exe /upgradesp SQLRUN SECURITYMODE=SQL
DISABLENETWORKPROTOCOLS=0 UPGRADEUSER=sa UPGRADEPWD=xxx /L*v "C:\Msde4.txt"

[quoted text, click to view]

yes, they are totally separated as regard binaries and registry entries..
you can have up to 16 instances per machine at different service pack
level..
only the common "shared" components (ie: SQL-DMO dependencies and the like)
will be at the higher installed service pack..

[quoted text, click to view]
installation failed...
look for
RETURN VALUE 3
entries... about 10 lines before each entry some description of the problem
will be reported..

[quoted text, click to view]

if you do not provide an instance name, a default instance will be
installed... it's name will then be "." or "(Local)" for local connections
and ComputerName for remote ones..
if you install a named instance, it's name will be ".\InstanceName" or
"(Local)\InstanceName" for local connections and ComputerName\InstanceName
for remote ones..

[quoted text, click to view]
not required.. just try understand what's the matter..

--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
--------- remove DMO to reply

hi Keith,
[quoted text, click to view]

:D

[quoted text, click to view]

DISABLENETWORKPROTOCOLS=0 instructs the installer to enable network
protocols, required if you have your instance to be available in a lan... if
you do not have this requirement, becouse your MSDE instance will only be
used by local connections, you are not required to..
in order to enable those network protocols after install time, you have to
execute the Server Network Utility (svrnetcn.exe) and enable the required
protocol(s)..

[quoted text, click to view]

UpgDetectBlankSaLogin
this exception indicates you did not provide the
SAPWD=xxxx
parameter to your call to the setup.exe boostrap installer of MSDE..

--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
--------- remove DMO to reply

One more quick question. If the instance was installed with SAPWD=<some
password> (not blank), does the upgrade only need SAPWD or does it also need
UPGRADEUSER=AnAdminLogin UPGRADEPWD=AdminPassword? (which would seem to me
not to make any sense)

Keith

hi Keith,
[quoted text, click to view]

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/distsql/distsql_84xl.asp
"SAPWD is ignored when you upgrade an existing instance of MSDE 2000, so you
should ensure the sa login has a strong password before upgrading."

the original SAPWD is valid and maintained..
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
--------- remove DMO to reply

make sure you kill all unneeded process thru services and process
explorer
clear all you temp file (especially under \docs and
setting\user\local..\temp)
important part here
clear(blankout) your SA password thru whatever (Enterprise manager)
then on your setup.exe line add "BLANKSAPWD=1"

worked for me

StanGuru

[quoted text, click to view]