RE: SBS 2003 SP1 Upgrade - MSDE 2000 Service Pack 4 did not instal
- From: dataArtist <dataArtist@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 9 May 2006 07:18:01 -0700
Hello Jenny,
Thank you for your response to my post. I have emailed the files you
requested to the address you indicated. (Note: my sending email address is
robp@xxxxxxxxxxxxxxxxxxx for the files)
I noticed an error in my osql command I used previously with the corrected
command SBSMONITORING and SHAREPOINT instances do show SP4 as the commend
result (I have emailed result output as text files).
Also I have noticed today in the event logs the following errors which may
be related:
Event ID: 1000
Windows SharePoint Services 2.0
#50070: Unable to connect to the database STS_Config on
FPHSERVER\SharePoint. Check the database connection information and make sure
that the database server is running.
Event ID: 1005
dsrestor
The DSRestore Filter failed to connect to local SAM server. Error returned
is <id:997>.
Please advise if you need futher information.
Thanks again for your great help!
--
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-8cf8982
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 notinstall
thread-index: AcZyzAZt4FFg8qnvQmCNUgZJ4+0zNw==the
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
upgrade I received two messages as follows:see
"MSDE 2000 Service Pack 4 did not install. For additional instructions,
the SQL Server 2000 Service Pack Web site atthrough
http://go.microsoft.com/fwlink/?LinkId=46241."
I was able to complete the installation of all components and click
to the Finish button of each update wizard.from
The first message was displayed at the end of SBS 2003 SP1 installation
CD 2, the second message came with the end of the ISA 2004 installationfrom
CD3.I
As far as I have been able to test all components seem to be working fine
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\ServicePackNumber
= 1Holmes)
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
- References:
- RE: SBS 2003 SP1 Upgrade - MSDE 2000 Service Pack 4 did not install
- From: "Jenny wu [MSFT]"
- RE: SBS 2003 SP1 Upgrade - MSDE 2000 Service Pack 4 did not install
- Prev by Date: Re: ISA Authentication: No internet access on some computers
- Next by Date: Re: sbs2003 and rights/policies
- Previous by thread: RE: SBS 2003 SP1 Upgrade - MSDE 2000 Service Pack 4 did not install
- Next by thread: RE: SBS 2003 SP1 Upgrade - MSDE 2000 Service Pack 4 did not instal
- Index(es):