RE: SQL Critical Update on SBS
- From: v-yanniw@xxxxxxxxxxxxxxxxxxxx ("Jenny wu [MSFT]")
- Date: Wed, 03 Aug 2005 09:05:10 GMT
Hi Blurz,
Thanks for posting here.
For your description, I understand that you encountered some problem when
install a MS SQL Server 2000 Desktop Engine critical update. If I am off
base, please don't hesitate to let me know.
Could you tell me what is the critical update? Is it KB829358?
Analyzing and suggestion:
===========
If so, the problem may be caused by either the problem in the update
package or the update is not fully applied. Let us perform the following
steps:
1. Check the file version of MSDE components. To do that:
1) Open Windows Explorer, and then navigate to \Program
Files\Microsoft SQL Server\MSSQL$SHAREPOINT\Binn\
2) Right-click 'sqlservr.exe' and choose 'Properties'.
3) In the properties window, click 'Version' tab. If the file version
is 2000.80.884.0, the database engine should be updated (The original
version is 2000.80.880.0).
If the file was not updated, you may download the package from the
following link and then manually install the update:
Critical Update for SQL Server 2000 Desktop Engine (Windows) on Windows
Server 2003 (KB829358)
http://www.microsoft.com/downloads/details.aspx?FamilyID=814c230b-5c53-453f-
810a-b9505acf1392&displaylang=en
2. If the file has been already updated, the problem may be caused by the
corrupted registry keys. Please try the following steps:
1) Click 'Start'->'Run'. Type 'regedit' and press Enter.
2) Navigate to the following registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Mi?crosoft\Microsoft SQL
Server\SHAREPOINT\Setup
3) Delete ProductCode OR change the content of Product code from
{65657C59-23A8-4974-B8E0-BA04E?BD04E4F} to anything else.
4) Close the registry editor.
If the problem persists, please collect following information for further
research:
1. Do you have SQL server installed on your SBS server? If so, have you
upgraded your Companyweb instance to Full SQL?
2. Do you have any anti-virus software installed on the SBS server?
3. You may check the event log information as following:
1) Select Administrative Tools and click Event Viewer.
2) In Event Viewer windows, click Application and System, select log
files regarding to it.
4. Please post the "Windows update.log" file in C:\Windows to newsgroup.
5. Please post the C:\WMSDEHotfix.log to newsgroup.
For the log files may be large you can add all the log files to a zip file
and mail to v-yanniw@xxxxxxxxxxxxxx
More info:
Critical update for SQL Server 2000 Desktop Engine (Windows) on Windows
Server 2003 is available for download on the Windows Update site
http://support.microsoft.com/default.aspx?scid=kb;en-us;829358
===========
For your second question: you must use the same server name and domain
name. Otherwise, SharePoint disaster recovery may fail. SharePoint stores
accounts by security identifier (SID) in the UserInfo table of the content
database. The error you restore sharepoint may caused by this. I suggest
you refer to the following KB articles to restore again.
827701 How to perform a disaster recovery operation of SharePoint Services
http://support.microsoft.com/?id=827701
829112 How to back up and restore http://companyweb data in Windows Small
Business Server 2003
http://support.microsoft.com/?id=829112
If you have any other concern or question about restore WSS I suggest you
post this question into the microsoft.public.sharepoint.windowsservices
newsgroup. You can visit the following link:
http://www.microsoft.com/technet/community/newsgroups/dgbrowser/en-us/defaul
t.mspx?dg=microsoft.public.sharepoint.windowsservices
The reason why we recommend posting appropriately is you will get the most
qualified pool of respondents, and other partners who the newsgroups
regularly can either share their knowledge or learn from your interaction
with us. Also, this is to make sure that the responders can better track
the problem Thank you for your understanding.
I appreciate your time and look forward to hearing from you.
Have a nice day!
Best Regards,
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: SQL Critical Update on SBS
>thread-index: AcWXGVHK7xHfQ2azSdelC1q7B1CgAQ==
>X-WBNR-Posting-Host: 203.92.66.194
>From: "=?Utf-8?B?Ymx1cno=?=" <blurz@xxxxxxxxxxxxxxxxxxxxxxxxx>
>Subject: SQL Critical Update on SBS
>Date: Mon, 1 Aug 2005 21:19:05 -0700
>Lines: 21
>Message-ID: <914679A1-921D-450F-A8E0-572265E0453B@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.0
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:140647
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>Hi all,
>1)
>Im running on W2k3 SBS and currently, Im having a problem with e
>installation of e MS SQL Server 2000 Desktop Engine critical update. It
seems
>that it is not installed even though i have already used windows update to
>apply this critical update and restarted e server. After installing,
Windows
>Update will still prompt me to install e same update as though it has
never
>been installed.
>
>2)
>I had made a backup of e Sharepoint services before reformatting e server.
>However, I tried to do a restore after the reformat but e companyweb
doesn't
>revert back to e original settings before the reformat. Is it because i
had
>change e domain name (eg. from companyweb.xxx.local to
compnayweb.yyy.local)?
>If so, is there any way to restore back e old companyweb settings under a
new
>domain name?
>
>Help would b greatly appreciated!
>
>Rgds
>blurz
>
.
- References:
- SQL Critical Update on SBS
- From: blurz
- SQL Critical Update on SBS
- Prev by Date: RE: Critical error in application log SBS 2003 Premium ED
- Next by Date: RE: Error installing KB832880
- Previous by thread: SQL Critical Update on SBS
- Next by thread: wanna ask about the exchange 2003
- Index(es):
Relevant Pages
|
