Re: VSS Errors using NTBackup
- From: "David Copeland [MSFT]" <davidcop@xxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 1 Nov 2007 11:31:31 -0500
Can you try the following and see if that helps.. based on
"Limit on 'Max worker threads' reached."
osql -E -S %computername%\msfw
sp_configure 'max worker threads',nnnn
go
reconfigure
go
exit
Where nnnn is a larger value.. for example, 512.
Then restart the MSFW instance. Keep in mind that you will want to do this locally due to the fact that while the instance is stopped ISA should go into lockdown mode due to the fact it can't log.
--
Hope that helps,
David Copeland
Microsoft Small Business Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
Newsgroups:
SBS v4.x : microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs
"StephanHeine" <StephanHeine@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:00339D53-9785-4E7C-8DD1-E0DBA305C0D9@xxxxxxxxxxxxxxxx
Hi Terrence,
Quick update:
It seems that this problem could be related to too many SQL connections when
trying to do the StateBackup.
BTW this server is also running ISA2004 SP2 logging to MSDE.
From the MSSQL$MSFW Errorlog:
2007-10-29 15:04:32.78 spid179 startsubprocess: Limit on 'Max worker
threads' reached.
2007-10-29 15:04:32.81 backup BACKUP failed to complete the command
BACKUP DATABASE [ISALOG_20071026_FWS_001] TO
VIRTUAL_DEVICE='{D0198987-7F25-4ED7-B908-BF1E9BB6E600}119' WITH
SNAPSHOT,BUFFERCOUNT=1,BLOCKSIZE=1024
2007-10-29 15:04:33.01 spid89 startsubprocess: Limit on 'Max worker
threads' reached.
2007-10-29 15:04:33.01 spid89 Thread creation failed. Running
BACKUP/RESTORE cleanup.
2007-10-29 15:04:33.07 spid89 BackupSoftFile::WriteMediaFileMark:
failure on backup device '{D0198987-7F25-4ED7-B908-BF1E9BB6E600}4'. Operating
system error 995(error not found).
2007-10-29 15:04:33.09 spid51 BackupMedium::ReportIoError: write failure
on backup device '{D0198987-7F25-4ED7-B908-BF1E9BB6E600}1'. Operating system
error 995(error not found).
2007-10-29 15:04:33.09 spid51 Internal I/O request 0x386D5BD8: Op: Write,
pBuffer: 0x159C0400, Size: 1024, Position: 0, UMS: Internal: 0x0,
InternalHigh: 0x0, Offset: 0x0, OffsetHigh: 0x0, m_buf: 0x00000000, m_len: 0,
m_actualBytes: 0, m_errcode: 995, BackupFile:
{D0198987-7F25-4ED7-B908-BF1E9BB6E600}1
[These lines are snippets from a 90MB errorlog file]
Now there is an error entry for every log DB in ISA.
I have also read that MSDE has a worker thread limit of 8.
Short work around at this moment:
net stop "Microsoft Firewall"
net stop "MSSQL$MSFW"
Do StateBackup
net start "MSSQL$MSFW"
net start "Microsoft Firewall"
In this fashion the StateBackup gets executed sucsessfully. :-)
It seems that too many DB's running has this effect.
Any suggestions further ?
Thanks
Stephan
"Terence Liu [MSFT]" wrote:
Hello Stephan,
Thank you for your update.
Please feel free to take your time.
If there's anything else I can do for you, please do not hesitate to let me
know.
Thank you and have a nice day.
Best regards,
Terence Liu(MSFT)
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: VSS Errors using NTBackup
| thread-index: AcgALlfNTpy0EvbVSRW7kYN0kIZbBA==
| X-WBNR-Posting-Host: 207.46.19.197
| From: =?Utf-8?B?U3RlcGhhbkhlaW5l?=
<StephanHeine@xxxxxxxxxxxxxxxxxxxxxxxxx>
| References: <5632A781-AE5C-4FCA-B1CA-757B2A95A17A@xxxxxxxxxxxxx>
<dl61Nur6HHA.4100@xxxxxxxxxxxxxxxxxxxxxx>
| Subject: RE: VSS Errors using NTBackup
| Date: Wed, 26 Sep 2007 04:14:02 -0700
| Lines: 288
| Message-ID: <F64C392F-4E47-41F5-83FB-BC31E8155F45@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.2929
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:65686
| NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Hi Terence,
|
| Thank you for your prompt post. I unfortunatley was out of the country
| until recently and will give you a response on this issue soon.
|
| Many Thanks
| Stephan
|
| "Terence Liu [MSFT]" wrote:
|
| > Hello Stephan,
| >
| > Thanks for posting here.
| >
| > According to your description, I understand that you received server
| > performance report about event errors VSS 6013 and 8193on the SBS 2003.
If
| > I have misunderstood the problem, please don't hesitate to let me know.
| >
| > First, I would like to thank you for your pre-troubleshooting process
and
| > information to isolate this issue.
| >
| > I. Please install the following VSS hotfix:
| >
| > A Volume Shadow Copy Service (VSS) update package is available for
Windows
| > Server 2003
| > http://support.microsoft.com/default.aspx?scid=kb;en-us;833167
| >
| > If you had installed SBS 2003 sp1, please install the following VSS
hotfix:
| >
| > A new Volume Shadow Copy Service update is now available that fixes
various
| > Volume Shadow Copy Service problems in Windows Server 2003
| > http://support.microsoft.com/default.aspx?scid=kb;en-us;913648
| >
| > II. Please perform the following steps to re-register VSS binaries and
| > services, first stop the Volume Shadow Copy Service:
| >
| > Open a command prompt and change directories to \windows\system32 (this
is
| > important when you begin registering the dlls):
| >
| > net stop vss
| >
| > Then register the following dlls and services (be sure you're still in
the
| > windows\system32 directory at your command prompt):
| >
| > regsvr32 ole32.dll
| > regsvr32 vss_ps.dll
| > Vssvc /Register
| > regsvr32 /i swprv.dll
| > regsvr32 /i eventcls.dll
| > regsvr32 es.dll
| > regsvr32 stdprov.dll
| > regsvr32 vssui.dll
| > regsvr32 msxml.dll
| > regsvr32 msxml3.dll
| > regsvr32 msxml4.dll
| >
| > III. On a SQL Server
| > --------------
| > Be sure the system account is a member of the SQL Administrators group.
| >
| > IMPORTANT NOTE: In cases where the above steps do not resolve, you may
wish
| > to reinstall COM+, and then re-register the services and binaries again.
| >
| > On a post SP1 System
| > ----------------------------------
| > Reinstall COM+
| >
| > 1. Backup and then delete HKLM\Software\Microsoft\COM3
| > 2. Boot to Recovery console and rename clbcatq.dll to ~clbcatq.dll. Be
| > sure to use the tilde.
| > 3. Boot to normal mode and in Control Panel, open the Add or Remove
| > Programs tool, and then open the Add/Remove Windows Components tool. Do
not
| > make any changes, just
| > click "Next". This reinstalls COM+.
| >
| > NOTE: You must have your Windows Server 2003 SP1 files available during
| > this step.
| >
| > IV. Disable shared memory protocol
| > a. Click Start, point to Programs, point to Microsoft SQL Server, and
then
| > click Client Network Utility.
| >
| > b. In the SQL Server Client Network Utility dialog box, click the
General
| > tab.
| >
| > c. Click to clear the Enable shared memory protocol check box, and then
| > click OK.
| >
| > If we cannot resolve the issue after we perform the above steps, please
| > kindly help me collect some information for further investigation:
| >
| > 1. Please send me the backup log files:
| >
| > a. The Backupxx.log files in the folder ''C:\Documents and Settings\SBS
| > Backup User\Local Settings\Application Data\Microsoft\Windows
| > NT\NTBackup\data''.
| >
| > Note: Before reproduce the problem, please open NTBACKUP, click
| > "Tools"->"Options" and then check "Detailed" on the "Backup Log" tab.
Then
| > reproduce this issue and send the backup log to me (Tools->Report).
| >
| > b. The Sbsbackuplog0x.log files which can be located under the folder
| > ''%sbsprogramdir%\Support\Backup Logs''.
| >
| > 2. Gather MPS network report:
| >
| > a. Download MPSrepot_network from
| >
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd9
| > 15706/MPSRPT_NETWORK.EXE
| >
| > b. Run MPSRPT_NETWORK.exe on the server box.
| >
| > c. The tool will automatically collect the information. This procedure
will
| > take 10~15 minutes.
| >
| > d. Open Windows Explorer, navigate to the folder:
| > %SystemRoot%\MPSReports\Network\Reports\Cab\
| >
| > e. Send the .cab file directly to me at v-terliu@xxxxxxxxxxxxx
| >
| > I appreciate your time and cooperation. If anything is unclear, please
feel
| > free to let me know.
| >
| > I am looking forward to hearing from you.
| >
| > Have a nice day!
| >
| > Best regards,
| >
| > Terence Liu(MSFT)
| >
| > 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: VSS Errors using NTBackup
| > | thread-index: AcfqSsaXxIZKrB3hRDi/9fnErgwacA==
| > | X-WBNR-Posting-Host: 207.46.193.207
| > | From: =?Utf-8?B?U3RlcGhhbkhlaW5l?=
| > <StephanHeine@xxxxxxxxxxxxxxxxxxxxxxxxx>
| > | Subject: VSS Errors using NTBackup
| > | Date: Wed, 29 Aug 2007 07:42:08 -0700
| > | Lines: 99
| > | Message-ID: <5632A781-AE5C-4FCA-B1CA-757B2A95A17A@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:59448
| > | NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
| > | X-Tomcat-NG: microsoft.public.windows.server.sbs
| > |
| > | Hi,
| > |
| > | After going through the forums, I still cannot come up with a
solution.
| > |
| > | The VSS Writer that fails is the MSDEWriter:
| > |
| > | Warning: VSS Writer (BackupComplete): "MSDEWriter", State: 8
| > | (VSS_WS_FAILED_AT_PREPARE_SNAPSHOT)
| > |
| > | From the Event Logs:
| > |
| > | The
| > |
| > | Event Type: Error
| > | Event Source: VSS
| > | Event Category: None
| > | Event ID: 8193
| > | Date: 2007/08/28
.
- Follow-Ups:
- Re: VSS Errors using NTBackup
- From: StephanHeine
- Re: VSS Errors using NTBackup
- References:
- RE: VSS Errors using NTBackup
- From: StephanHeine
- RE: VSS Errors using NTBackup
- Prev by Date: Re: One Users My Documents no longer redirected.
- Next by Date: Re: FTP Through 2003 SBS
- Previous by thread: RE: VSS Errors using NTBackup
- Next by thread: Re: VSS Errors using NTBackup
- Index(es):
Relevant Pages
|
Loading
