RE: SBS 2003 SP1 Upgrade - MSDE 2000 Service Pack 4 did not instal

Hi Robert,

Thanks for your update.

After reviewed the sbsisa2k4setup.log file, we found the following error:

SBSISA2K4SETUP: *** LaunchMSDESP4 returned ERROR 0x80070002
SBSISA2K4SETUP: *** Running MSDE SP4 setup unattended returned ERROR
0x80070002

That error is E_NOTFOUND and would only happen if the it could not open the
following regkey:

HKEY_LOCAL_MACHINE\Software\Microsoft\SmallBusinessServer\ServicePacks

After opening that, it would need to read a key named "WMSDE2000SP4Path" as
a REG_SZ and have it contain the path to the MSDE SP4 files. As you have
already upgrade SQL to SP4, we can specify the WMSDE2000SP4Path to point to
the fully expanded path of "%ProgramFiles%\ Microsoft SQL Server
SP4\WMSDE". For example, C:\Program Files\Microsoft SQL Server SP4\WMSDE.
You can also create a same REG_SZ value "MSDE2000SP4Path" and point it to
C:\Program Files\Microsoft SQL Server SP4\MSDE.

In other word, there should be two reg keys under the following node:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\ServicePacks

MSDE2000SP4Path
WMSDE2000SP4Path

Then please run command to apply WMSDE SP4 to the MSFW instance.

Q: Also I am wondering about the command line you said to try, it points to
the WMSDE setup files. Is this correct? I thought the WMSDE could only be
used for the SHAREPOINT instance?

A: Yes, it is correct. The files under the folder: C:\Program Files\
Microsoft SQL Server SP4\WMSDE are WMSDE SP4 installation files and they
can be applied to any WMSDE instances.

Q: I will have to schedule some down time for the server to try this update
so It might be a couple of days before I can let you know how it went.

Ok, I will wait for you. Please feel free to let me know if you need
further assistance to the issue.

Have a nice day!

Sincerely,

Jenny Wu
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
The customer mail content:
===================
Hi Jenny,

Thank you for quick response!

I have looked through the sbsisa2k4setuplog.txt file and the only
reference I can see regarding the database upgrade are as follows:

IsISA2k4Installed returned TRUE
SBSISA2K4SETUP: Entering LaunchMsdeSp4
SBSISA2K4SETUP: *** Opening MSDE SP4 Path regkey returned ERROR 0x80070002
SBSISA2K4SETUP: *** LaunchMSDESP4 returned ERROR 0x80070002
SBSISA2K4SETUP: *** Running MSDE SP4 setup unattended returned ERROR
0x80070002
SBSISA2K4SETUP: MSDE SP4 failed. Setting property to signal user of failure.
SBSISA2K4SETUP: WriteBool( GUID_PROPERTY_MSDE_INSTALL_FAILED, TRUE )
returned OK
SBSISA2K4SETUP: CSbsIsa2k4SetupCommit::CommitEx returned OK
SBSISA2K4SETUP: CommitEx returned OK
SBSISA2K4SETUP: Marking committer succeeded.
SBSISA2K4SETUP: Reading MSDE Failed property returned OK
SBSISA2K4SETUP: Warning the user that MSDE SP4 installation failed.
SBSISA2K4SETUP: Waiting for the user to dismiss the status dialog
SBSISA2K4SETUP: Commit returned OK
SBSISA2K4SETUP: Commit returned OK
SBSISA2K4SETUP: Prompting user for a reboot
SBSISA2K4POSTSETUP: Setup wrapper signaled completion
SBSISA2K4SETUP: Setting the event to signal post setup
SBSISA2K4SETUP: InstallISA2k4 returned OK
SBSISA2K4SETUP: Installing ISA2k4 returned OK
SBSISA2K4SETUP: Exiting


Judging from this it seems that it could not find the MSDE SP4 path it
wanted in the Registry.

I have the following directories on my computer:

C:\Program Files\ Microsoft SQL Server SP4\MSDE (about 76 mb of setup
files)
C:\Program Files\ Microsoft SQL Server SP4\WMSDE (about 76 mb of setup
files)

The MSFW instance is located in the following:

C:\Program Files\Microsoft SQL Server\MSSQL$MSFW


These seem to be standard locations so I'm not sure why it couldn't find
them in the registry.

Also I am wondering about the command line you said to try, it points to
the WMSDE setup files. Is this correct? I thought the WMSDE could only be
used for the SHAREPOINT instance?

I will have to schedule some down time for the server to try this update so
It might be a couple of days before I can let you know how it went.


Thanks again for your great help!

===================

--------------------
X-Tomcat-ID: 185767765
References: <2C2CCCEF-4C81-48E4-A86A-A0CA545FB700@xxxxxxxxxxxxx>
<7GohTxxcGHA.4776@xxxxxxxxxxxxxxxxxxxxx>
<3F70DFF5-216E-4C38-B147-B559A9E10016@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
From: v-yanniw@xxxxxxxxxxxxxxxxxxxx ("Jenny wu [MSFT]")
Organization: Microsoft
Date: Wed, 10 May 2006 10:57:43 GMT
Subject: RE: SBS 2003 SP1 Upgrade - MSDE 2000 Service Pack 4 did not instal
X-Tomcat-NG: microsoft.public.windows.server.sbs
Message-ID: <fe7gVCCdGHA.188@xxxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.windows.server.sbs
Lines: 409
Path: TK2MSFTNGXA01.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:267070
NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122

Hi Rob,

Thanks for your information. I appreciate your time.

To the ISA 2004 issue, please first export all configuration information
to
a .xml file to avoid any unexpected thing, you can restore back.

Please go to the sbsisa2k4setuplog.txt file
(%sbsprogramdir%\Support\sbsisa2k4setuplog.txt) and find the information
such as:

"SBSISA2K4SETUP: Command Line: "C:\Program Files\Microsoft SQL Server
SP4\WMSDE\setup.exe" /upgradesp sqlrun BLANKSAPWD=1 INSTANCENAME=MSFW
DISABLENETWORKPROTOCOLS=1 /L*v "C:\Program Files\Microsoft
Integration\Windows Small Business Server 2003\Logs\ISA_MSDE.log""

Then please open command prompt to run command line to manually update the
MSFW instance to SP4:

C:\Program Files\Microsoft SQL Server
SP4\WMSDE\setup.exe" /upgradesp sqlrun BLANKSAPWD=1 INSTANCENAME=MSFW
DISABLENETWORKPROTOCOLS=1 /L*v "C:\Program Files\Microsoft
Integration\Windows Small Business Server 2003\Logs\ISA_MSDE.log"

What is the result?

If the process failed, you can directly insert the ISA 2004 installation
CD
and click install ISA 2004 to repair the ISA server. Can you update it
successfully?

If the issue persists, I would like to suggest that you remove the ISA
server from Add/Remove programs and then re-install the ISA 2004. Then
import the ISA configuration information to restore back all
configurations.

=============================
Regarding to 1000 Windows SharePoint Services 2.0 error event issue, let
us
perform the following suggestions to trouble shoot the issue:

Suggestion 1:
==============
This issue occurs when the SharePoint Timer Service tries to contact the
configuration database when the computer starts or shuts down. By default,
the configuration database in Windows SharePoint Services is named
STS_config.

The error message that is mentioned in the "Symptoms" section does not
affect the functionality of Windows SharePoint Services or of Windows
Small
Business Server 2003. If you can connect to the Windows SharePoint
Services
Web site successfully, you can safely ignore this error message.

To work around this issue, add the DependOnService registry entry to the
following registry subkey on the server, and then set the DependOnService
Registry entry to MSSQL$SHAREPOINT:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SPTimer

To do this, follow these steps:

Warning: If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system.
Microsoft
cannot guarantee that you can solve problems that result from using
Registry Editor incorrectly. Use Registry Editor at your own risk.

1. Click "Start", and then click "Run".
2. In the "Open" box, type "regedit" (without the quotation marks), and
then click "OK".
3. Locate, and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SPTimer

4. On the "Edit" menu, point to "New", and then click "String Value".
5. Type "DependOnService" (without the quotation marks), and then press
ENTER
6. On the "Edit" menu, click "Modify".
7. In the "Value data" box, type "MSSQL$SHAREPOINT" (without the quotation
marks), and then click "OK".
8. Quit Registry Editor.

For more information, see:
840685 An event ID 1000 error message is logged to the application event
log
http://support.microsoft.com/?id=840685

Try to test, does it work?

Suggestion 2:
==============
Ensure that the SharePoint Configuration Database, the Admin apppool, and
the SharePoint Timer Service are all running under the same context.

a. Browse SharePoint Central Admin
b. Under Server Configuration, Click Configure Virtual Server for Central
Administration
c. Select Use an Existing Application Pool
d. Select the application pool that the admin vserver is running under
e. Click OK
f. Run IISReset
g. Restart the SharePoint Timer Service (use the Services MMC or use Net
Stop/Start on sptimer)

Suggestion 3:
==============
Please try to disable the loopback check to see if the issue is resolved.
You can refer to the following steps:

1. Click Start, click Run, type regedit, and then click OK.
2. In the Registry editor, locate and then click the following registry
key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa.
3. Right-click Lsa, point to New, and create a DWORD Value.
4. Type DisableLoopbackCheck, and then press Enter.
5. Right-click DisableLoopbackCheck, and then click Modify.
6. In the Value data box, type 1, and then click OK.
7. Quit the Registry editor, and then restart your computer.

More information:
831105 "Unable to Connect to Database" Error Message When You Connect to a
http://support.microsoft.com/?id=831105

320204 SharePoint Portal Server Does Not Start After You Install MDAC 2.7
http://support.microsoft.com/?id=320204

=============================

For the Event error "EventCode=1005 Source=dsrestor". This is a known bug
with SBS 2k3 which has already been filed. Since it will not cause any
problem, there is no hotfix released for it and can be safely ignored.

Additionally, The 1005 error indicates that dsrestore was unable to
connect
to the sam and verify the passwords are in synch when the server boots.
The
dsrestore process is to synch the domain admin password with the dsrm
password. The dsrestor process will run every 30 mins to verify that the
passwords are in synch. If the process fails it does not run again until
the server is rebooted. As a workaround you can manually reset the DSRM
password to match the domain admin password by using ntdsutil.
For more information about resetting the password, see:

322672 How To Reset the Directory Services Restore Mode Administrator
Account
http://support.microsoft.com/?id=322672

Hope above information helps! I am glad to help.

Have a nice day!

Sincerely,

Jenny Wu
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check
the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In
doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
Thread-Topic: SBS 2003 SP1 Upgrade - MSDE 2000 Service Pack 4 did not
instal
thread-index: AcZzpI64oMD3/djZRrurq3NXyK8IdA==
X-WBNR-Posting-Host: 67.69.18.2
From: =?Utf-8?B?ZGF0YUFydGlzdA==?= <dataArtist@xxxxxxxxxxxxxxxxxxxxxxxxx>
References: <2C2CCCEF-4C81-48E4-A86A-A0CA545FB700@xxxxxxxxxxxxx>
<7GohTxxcGHA.4776@xxxxxxxxxxxxxxxxxxxxx>
Subject: RE: SBS 2003 SP1 Upgrade - MSDE 2000 Service Pack 4 did not
instal
Date: Tue, 9 May 2006 13:10:03 -0700
Lines: 200
Message-ID: <3F70DFF5-216E-4C38-B147-B559A9E10016@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Newsgroups: microsoft.public.windows.server.sbs
Path: TK2MSFTNGXA01.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:266873
NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
X-Tomcat-NG: microsoft.public.windows.server.sbs

Hello Again Jenny,

I forgot to ask, what is the preferred method for re-installing ISA2004
in
this situation? Do I just run from the CD again or use the Add/Remove
programs entry? Do I have to uninstall ISA2004 first? What happens to my
configurations that had been imported from ISA2000 during the SBS Premium
Service Pack 1 upgrade?

As far as I can tell ISA2004 is solid just MSFW was not upgraded to SP4
level. Frankly I am not planning to use the MSFW database for logging
anyways
(uses too much memory).

I see the MSFW instance in the Add/Remove programs but there is no way to
uninstall it (no Change/Remove button) as with the SHAREPOINT and
SBSMONITORING instances.

--
Rob Pereira
dataArtist
I need data data data!...I can't make bricks without clay! (Sherlock
Holmes)


""Jenny wu [MSFT]"" wrote:

Hi Rob,

Thanks for using the SBS newsgroup.

From your description, I understand the issue to be: the MSDE 2000 SP4
did
not apply to all instances properly. If I am off base, please don't
hesitate to let me know.

Before we go any further, please kindly help me collect some
information
to
isolate the issue:

1. Please go to registry keys to check instances service pack level.
You
can go the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL server

Then expand one instance such as: SHAREPOINT, what is the value of the
Patchlevel?
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
server\SHAREPOINT\Setup

You can check all instances to service pack level. Also please export
the
registry keys of the Microsoft SQL server and mail to me for analyze.

2. Please take a screen shot of the MSSQL\MSFW and MSSQL\SHAREPOINT
instances version numbers in SQL Enterprise Manager and mail to me.

3. Please take a screen shot of the output when you use OSQL to check
instances versions for analyze.

If the instance MSFW's version number is not SP4, that indicates the
ISA
2004 can not be installed successfully. I suggest that you re-install
the
ISA 2004 to see what happens.

Since the instance - MSSQL\BKUPEXEC is not SBS component. The SBS 2003
SP1
can not update the instance automatically. You can manually update the
BKUPEXEC to SP4.

If the ISA 2004 still can not be installed properly, please also help
me
collect the following log files for analyze:

a. C:\Program Files\Microsoft Integration\Windows Small Business Server
2003\Logs

b. To save a text copy of Application /System log:

a). Open Event Viewer: Start -> All Programs -> Administrative Tools ->
Event Viewer.
b). Right-click on Application/System log and select "Save Log File
As?".

Please compress all files and mail me at v-yanniw@xxxxxxxxxxxxxx

More information:
Windows Small Business Server 2003 with SP1 Release Notes

http://download.microsoft.com/download/d/5/b/d5be2c2c-b1cb-47f8-9235-8cf898
2
0139e/Readme_prem.htm

I appreciate you time! I am happy to be of assistance to you and look
forward to your reply!

Have a nice day!

Sincerely,

Jenny Wu
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the
corresponding
newsgroups so that they can be resolved in an efficient and timely
manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check
the
"Notify me of replies" box to receive e-mail notifications when there
are
any updates in your thread. When responding to posts via your
newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In
doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly.
Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.

--------------------
Thread-Topic: SBS 2003 SP1 Upgrade - MSDE 2000 Service Pack 4 did not
install
thread-index: AcZyzAZt4FFg8qnvQmCNUgZJ4+0zNw==
X-WBNR-Posting-Host: 67.69.18.2
From: =?Utf-8?B?ZGF0YUFydGlzdA==?=
<dataArtist@xxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: SBS 2003 SP1 Upgrade - MSDE 2000 Service Pack 4 did not
install
Date: Mon, 8 May 2006 11:20:03 -0700
Lines: 49
Message-ID: <2C2CCCEF-4C81-48E4-A86A-A0CA545FB700@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
Newsgroups: microsoft.public.windows.server.sbs
Path: TK2MSFTNGXA01.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:266534
NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
X-Tomcat-NG: microsoft.public.windows.server.sbs

Hello,

This past weekend I completed an upgrade of an SBS 2003 Premium
Edition
server to SBS 2003 SP1. Everything seems to have gone o.k. except
during
the
upgrade I received two messages as follows:

"MSDE 2000 Service Pack 4 did not install. For additional
instructions,
see
the SQL Server 2000 Service Pack Web site at
http://go.microsoft.com/fwlink/?LinkId=46241.";

I was able to complete the installation of all components and click
through
to the Finish button of each update wizard.

The first message was displayed at the end of SBS 2003 SP1
installation
from
CD 2, the second message came with the end of the ISA 2004
installation
from
CD3.

As far as I have been able to test all components seem to be working
fine
I
can access companyweb and remote web workplace.

When I check the version numbers in SQL Enterprise Manager I see the
following:

MSSQL\MSFW = 8.00.818(SP3)
MSSQL\SBSMONITORING = 8.00.2039(SP4)
MSSQL\SHAREPOINT = 8.00.2039(SP4)
I also have an instance for Veritas Backup Exec:
MSSQL\BKUPEXEC = 8.00.760(SP3)

When I check the versions using OSQL all of them show SP3.


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\ServicePackNumbe
r

= 1

Computer Properties also shows SBS 2003 SP1.

I now have an SQL SERVER 2000 SP4 directory under Program Files.

My question is do I only need to re-apply the MSDE SP4 to the
instances
shown above?

I can send a zip of my log files if you advise an email address.

Thank you,

--
Rob Pereira
dataArtist
I need data data data!...I can't make bricks without clay! (Sherlock
Holmes)







.