RE: Event errors after power outage crash
- From: v-mzhuan@xxxxxxxxxxxxxxxxxxxx (Manfred Zhuang [MSFT])
- Date: Wed, 29 Aug 2007 09:53:01 GMT
Hello Brad,
Thank you for your reply and I am sorry for the delay.
After reviewing your replies, I understand that after re-register VSS
files, original errors disappeared. Now on startup, WSS3 error 3355 is
received and when perform a scheduled backup, VSS error 6013 is received.
However, manual backup works properly.
Based on current situation, I think the two errors can be caused by a SQL
server issue.
I suggest you post the issue in SQL newsgroup to see we can get more
information.
In the mean time, I suggest you try following steps to see if it helps:
Suggestion 1: Install the latest VSS component
=============
I would like to confirm what service pack has been installed on the SBS
server. I suggest you install following update to see if it helps:
Microsoft Windows Small Business Server 2003 Service Pack 1 (SP1)
http://www.microsoft.com/downloads/details.aspx?FamilyID=b6f8a4c0-b707-4161-
adeb-44f1b756119f&DisplayLang=en
Windows Server 2003 Service Pack 2 (32-bit x86)
http://www.microsoft.com/downloads/details.aspx?FamilyID=95ac1610-c232-4644-
b828-c55eec605d55&DisplayLang=en
Windows Server 2003 may not start when the Volume Shadow Copy Service is
enabled
http://support.microsoft.com/kb/931312/en-us
NOTE: Although KB931312 does not match the issue you are encountering, it
can update the VSS component to the latest version.
Additional information:
Best practices and known issues when you install Windows Server 2003
Service Pack 2 on a Windows Small Business Server 2003-based computer
http://support.microsoft.com/kb/939421
Suggestion 2: Remove and reinstall WSS 3
==========================
I suggest you remove and reinstall Windows SharePoint Services 3 and check
if it helps.
I hope the above information is helpful to you. However, if the issue
persists, please help me gather following information:
Backup Logs.
a. The Backupxx.log files in the folder 'C:\Documents and Settings\SBS
Backup User\Local Settings\Application Data\Microsoft\Windows
NT\NTBackup\data'.
Or 'C:\Documents and Settings\CurrentUserName\Local Settings\Application
Data\Microsoft\Windows NT\NTBackup\data'
b. The Sbsbackuplog0x.log files which can be located under the folder
'%sbsprogramdir%\Support\Backup Logs'.
Please try the above steps at your earliest convenience. If you have any
concern, please feel free to let me know.
Best regards,
Manfred Zhuang(MSFT)
Microsoft 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: Event errors after power outage crash
| thread-index: Acfmray6MZ4j3U0GSRW8r6ORqXt12g==
| X-WBNR-Posting-Host: 207.46.19.197
| From: =?Utf-8?B?QnJhZCBDaHJpc3RpZQ==?=
<BradChristie@xxxxxxxxxxxxxxxxxxxxxxxxx>
| References: <7BFA1E88-5937-4405-BA01-4A032F380C9C@xxxxxxxxxxxxx>
<bzkopdj5HHA.2340@xxxxxxxxxxxxxxxxxxxxxx>
| Subject: RE: Event errors after power outage crash
| Date: Fri, 24 Aug 2007 17:20:00 -0700
| Lines: 62
| Message-ID: <A861F486-B6AE-4236-8B73-CC0F3531FF70@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.2826
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:58717
| NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Hi Manfred
|
| The results are in - I opted for suggestion 3 and after a server restart
it
| came in a winner.
|
| On start up I have three warnings (19011, 3 and 5603) and one error. Any
| idea what that is about?
|
| Event Type: Error
| Event Source: Windows SharePoint Services 3
| Event Category: Database
| Event ID: 3355
| Date: 24/08/2007
| Time: 11:31:31 pm
| User: N/A
| Computer: SERVER2
| Description:
| Cannot connect to SQL Server. np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query
| not found. Additional error information from SQL Server is included below.
| Timeout expired. The timeout period elapsed prior to completion of the
| operation or the server is not responding.
|
| I do get four of this errors when running a backup
|
| Event Type: Error
| Event Source: VSS
| Event Category: None
| Event ID: 6013
| Date: 25/08/2007
| Time: 12:03:23 am
| User: N/A
| Computer: SERVER2
| Description:
| Sqllib error: OLEDB Error encountered calling IDBInitialize::Initialize.
hr
| = 0x80040e4d. SQLSTATE: 42000, Native Error: 18456
| Error state: 1, Severity: 14
| Source: Microsoft OLE DB Provider for SQL Server
| Error message: Login failed for user 'NT AUTHORITY\SYSTEM'.
| Data:
| 0000: 2d 20 43 6f 64 65 3a 20 - Code:
| 0008: 53 51 4c 43 4f 4e 4e 43 SQLCONNC
| 0010: 30 30 30 30 30 34 39 31 00000491
| 0018: 2d 20 43 61 6c 6c 3a 20 - Call:
| 0020: 53 51 4c 43 4f 4e 4e 43 SQLCONNC
| 0028: 30 30 30 30 30 33 39 37 00000397
| 0030: 2d 20 50 49 44 3a 20 20 - PID:
| 0038: 30 30 30 30 34 33 37 36 00004376
| 0040: 2d 20 54 49 44 3a 20 20 - TID:
| 0048: 30 30 30 30 34 34 30 34 00004404
| 0050: 2d 20 43 4d 44 3a 20 20 - CMD:
| 0058: 43 3a 5c 57 49 4e 44 4f C:\WINDO
| 0060: 57 53 5c 53 79 73 74 65 WS\Syste
| 0068: 6d 33 32 5c 76 73 73 76 m32\vssv
| 0070: 63 2e 65 78 65 20 20 20 c.exe
| 0078: 2d 20 55 73 65 72 3a 20 - User:
| 0080: 4e 54 20 41 55 54 48 4f NT AUTHO
| 0088: 52 49 54 59 5c 53 59 53 RITY\SYS
| 0090: 54 45 4d 20 20 20 20 20 TEM
| 0098: 2d 20 53 69 64 3a 20 20 - Sid:
| 00a0: 53 2d 31 2d 35 2d 31 38 S-1-5-18
|
| Thanks for your help.
|
.
- References:
- Event errors after power outage crash
- From: Brad Christie
- RE: Event errors after power outage crash
- From: Manfred Zhuang [MSFT]
- Event errors after power outage crash
- Prev by Date: RE: low disk space
- Next by Date: Re: Help with configuring Connection Filtering - RBL - zen.spamhaus.org
- Previous by thread: RE: Event errors after power outage crash
- Next by thread: Offline files affecting access from vpn connection
- Index(es):
Relevant Pages
|
Loading
