Windows Server 2008 R2 - VSS Errors
-
Friday, April 27, 2012 4:22 PM
We just stated noticing that we are getting these 2 errors in the
Application log on one of our 2008 R2 servers. We have found suggestions
that apply to Server 2003 but we have not found anything for Server
2008 R2. We have tried rebooting the server and
still have the same issue. When we run "vssadmin list writers" it hangs
and does not complete. When we try to create a new shadow copy we get a
message saying "Another Shadow copy creation is in progress. Wait a few
minutes and try again." If we wait a few
minutes and try again we get the same message. We found a suggestion
saying to re-register some DLL files but we would not like to do that.
We have also looked at this ->
http://support.microsoft.com/kb/956136. but that does not apply to R2.
All updates
are installed on the server. Also, the hard drive has around 280 GB of
free space.Has anyone seen this issue on Server 2008 R2? Does anyone have a fix for it?
Log Name: Application
Source: VSS
Date: 4/3/2012 9:08:27 AM
Event ID: 12305
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Server
Description:
Volume Shadow Copy Service error: Volume/disk not connected or not
found. Error context:
CreateFileW(\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy26,0x00000000,0x00000003,...).Log Name: Application
Source: VSS
Date: 4/3/2012 9:07:32 AM
Event ID: 7001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: Server
Description:
VssAdmin: Unable to create a shadow copy: Another shadow-copy creation
is in progress, so the current shadow copy cannot be created. There are
a number of common scenarios causing this problem: * If
Shadow Copies of Shared Folders is set up, ensure that no two volumes
have schedules that lie within five minutes of each
other.
* If automatic backup of any form is scheduled, ensure that the backup
schedule does not overlap with the schedule used for Shadow
Copies of Shared Folders. Generally, retrying
the operation after a few minutes or changing the schedule of an
automatic task should fix this problem.
Command-line: 'vssadmin create shadow /For=E:'.
All Replies
-
Saturday, April 28, 2012 4:16 AM
Hi;
Instead of using vssadmin list writers command, you can use diskshadow. This tools is an interactive command. Execute diskshadow /l C:\output.txt, and then type list writers in diskshadow> prompt. Then open the output.txt and see if it contains reports about your writers...
Do you have any other products on the server that uses Volume Shadow Copy Service (like any other backup products)? Do you use VSS For Share Folder feature (If you are not sure, go to the Shadow Copies tab of the Properties screen on one of your NTFS-formated volumes. Look at the Next Run Time section. Do you see Disabled in this section for all of your volumes)? If you do not find the problematic application or service, I suggest you to start the server in Clean Boot, as the following steps, and try to do the backup operating again:
1. Click "Start", go to "Run", and type "msconfig" in the open box to start the System Configuration Utility.
2. Click the "Services" tab, check the "Hide All Microsoft Services" box and click Disable All (if it is not gray).
3. Click the "Startup" tab, click "Disable All" and click "OK".
4. Restart your computer. When the "System Configuration Utility" window appears, please check the box and click "OK".Also, please run chkdsk /f C: on that server, restart it and give a try...
Please execute vssadmin list providers and paste the result in your reply.
Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
- Edited by R.AlikhaniMicrosoft Community Contributor Saturday, April 28, 2012 4:23 AM
-
Monday, April 30, 2012 2:09 PM
Hello,
I will try those suggestions and let you know what happens.
Thank you
-
Wednesday, May 02, 2012 8:33 AMModeratorany updates ?
Jeff Ren TechNet Community Support beneficial to other community members reading the thread.
-
Wednesday, May 02, 2012 3:36 PM
Hello,
When I ran diskshadow /l C:\output.txt, and then type list writers in diskshadow> prompt. it would just hang at list writers and not put anything in the output.txt file.
We are using R1soft and I do see Disabled under the Next Run Time for all the volumes.
We were able to run chkdsk last night and today we are able to run the list writers command and I have the information in the output.txt file. There is to much information in the output.txt file to paste in here. I was also able to run the vssadmin list providers command and the results are below.
C:\Users\ip-helpdesk>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5} -
Wednesday, May 02, 2012 5:26 PM
There is to much information in the output.txt file to paste in here.
Instead of executing diskshadow command, execute vssadmin list writers command and past the output here.
Also do the following actions BEFORE performing a backup operation:
1. Go to "Task Scheduler" console.
2. On the left pane, right-click "Task Scheduler Library" and select Disable All Running Tasks options.
Please report back the result.
Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
- Edited by R.AlikhaniMicrosoft Community Contributor Wednesday, May 02, 2012 5:28 PM
- Edited by R.AlikhaniMicrosoft Community Contributor Wednesday, May 02, 2012 5:28 PM
-
Monday, June 04, 2012 3:46 PM
Hello,
Rich has left our company and I will be picking up this issue for him.
I disabled all running tasks and then ran the vssadmin list writers command. Vssadmin hangs at waiting for responses and never completes the request.
Thanks,
Brandon
-
Monday, June 04, 2012 4:53 PM
Please before running vssadmin list writers, reboot the server and make a try again and then report back the result.
Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
-
Wednesday, June 06, 2012 2:19 PM
Here is the output of vss list writers from directly after a reboot:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\ip-helpdesk>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Writer name: 'Task Scheduler Writer'
Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
State: [1] Stable
Last error: No error
Writer name: 'VSS Metadata Store Writer'
Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
State: [1] Stable
Last error: No error
Writer name: 'Performance Counters Writer'
Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
State: [1] Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {659049c1-a46e-418b-bdaf-a6779c3c8e81}
State: [1] Stable
Last error: No error
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {f62617af-91f4-4e54-8abf-1374d925974f}
State: [1] Stable
Last error: No error
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {7cfd1c94-c58a-43c6-9313-a72c4a1491d6}
State: [1] Stable
Last error: No error
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {24d95617-96f0-4ef5-b370-35c162b9c7fd}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {07007b62-f739-4734-9bf8-31f28c24c5f8}
State: [1] Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {6ad0f2a5-80a8-457e-a791-20e1d3985144}
State: [1] Stable
Last error: No error
Writer name: 'ISA Writer'
Writer Id: {25f33a79-3162-4496-8a7d-caf8e7328205}
Writer Instance Id: {beb7e92c-7856-4258-b4bc-a741551c7a63}
State: [1] Stable
Last error: No error
Writer name: 'NPS VSS Writer'
Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
Writer Instance Id: {0cf86378-8667-4e33-94c5-7b909e19e72e}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {b21072a1-aab6-42c2-b6bf-9bedb2467aad}
State: [1] Stable
Last error: No error
Writer name: 'DFS Replication service writer'
Writer Id: {2707761b-2324-473d-88eb-eb007a359533}
Writer Instance Id: {78482337-b80c-4f66-9deb-e46da800b393}
State: [1] Stable
Last error: No error
Writer name: 'Dhcp Jet Writer'
Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
Writer Instance Id: {c80ab396-15a1-46f3-a4b9-451d3ca8295f}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {d09471e1-2cd4-4220-bc28-dbe54cb70830}
State: [1] Stable
Last error: No error
Writer name: 'ADAM (ISASTGCTRL) Writer'
Writer Id: {dd846aaa-a1b6-42a8-aaf8-03dcb6114bfd}
Writer Instance Id: {04babd42-5d3d-4949-9eda-9e02527fd4a8}
State: [1] Stable
Last error: No error
Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
Writer Instance Id: {2e07a00b-063a-4dd3-9538-43b922cbd9d1}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {dd059980-8607-4236-89e5-13ac5a0fe273}
State: [1] Stable
Last error: No error
-
Wednesday, June 06, 2012 5:36 PM
Now your writers are in an stable status. Can you please provide us the result of the backup operation? Do you see the error messages that your college has been reported in his first thread?
Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
-
Wednesday, June 06, 2012 6:01 PMYes, it will work for a time after reboot, but then will eventually fail once again. The server has actually been rebooted a number of times since the problem began. I just tried kicking off a manual backup to see if that is triggering the failure, but that does not appear to be the case, it is still in a good state.
-
Wednesday, June 06, 2012 6:04 PM
Can you please provide us any events related to your backup operation that has been registered in Event Viewer utility?
Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
-
Wednesday, June 06, 2012 6:19 PM
It doesn't write anything to the Windows logs, it just uses its own log file.
The errors in the log from last nights attempt are as follows:
[2012-May-27 21:03:38],[ INFO],[199.xxx.xxx.xxx:59655],Executing backup request...
[2012-May-27 21:03:38],[ERROR],[199.xxx.xxx.xxx:59655],An exception occurred during the request. Another replication is already in progress.
some more stuff, and then:
2012-Jun-05 20:07:35],[ERROR],[199.xxx.xxx.xxx:32492],An error occured during the asynchronous execution of VSS operation 'VssWrapper::DoSnapshotSet'. 0x800706ba
[2012-Jun-05 20:07:35],[ERROR],[199.xxx.xxx.xxx:32492],Event listener unable to obtain event log records; The interface is unknown
More events around session keys and what not, and then:
[2012-Jun-05 22:47:18],[ INFO],[NO-CONNECTION],[ChangeTracker],Initial changes found for device '\\?\Volume{6e980326-1c99-406c-b26a-cb4b03567}' with volume id '4'
[2012-Jun-05 22:47:33],[ERROR],[NO-CONNECTION],Unable to open device '' to fetch content id.: The filename, directory name, or volume label syntax is incorrect
- Edited by Brandon74 Wednesday, June 06, 2012 6:20 PM grammar issue
-
Wednesday, June 06, 2012 6:38 PM
It doesn't write anything to the Windows logs, it just uses its own log file.
The errors in the log from last nights attempt is as follows:
[2012-May-27 21:03:38],[ INFO],[199.xxx.xxx.xxx:59655],Executing backup request...
[2012-May-27 21:03:38],[ERROR],[199.xxx.xxx.xxx:59655],An exception occurred during the request. Another replication is already in progress.
some more stuff, and then:
2012-Jun-05 20:07:35],[ERROR],[199.xxx.xxx.xxx:32492],An error occured during the asynchronous execution of VSS operation 'VssWrapper::DoSnapshotSet'. 0x800706ba
[2012-Jun-05 20:07:35],[ERROR],[199.xxx.xxx.xxx:32492],Event listener unable to obtain event log records; The interface is unknown
More events around session keys and what not, and then:
[2012-Jun-05 22:47:18],[ INFO],[NO-CONNECTION],[ChangeTracker],Initial changes found for device '\\?\Volume{6e980326-1c99-406c-b26a-cb4b03567}' with volume id '4'
[2012-Jun-05 22:47:33],[ERROR],[NO-CONNECTION],Unable to open device '' to fetch content id.: The filename, directory name, or volume label syntax is incorrect
Do you use the native Windows Server backup software for backing up the server or you have a third-party backup tool?
Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
-
Wednesday, June 06, 2012 6:43 PMIt is a 3rd party tool called R1soft CDP Agent.
-
Wednesday, June 06, 2012 6:59 PM
As this tool is a third-party tool, and the logs that you have provided is based on that tool, I suggest to make a similar backup operation with Windows Server Backup utility in Windows Server 2008 R2 to better analyze your issue...
Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
-
Wednesday, June 06, 2012 7:03 PMOnce VSS failes again, I'll set up a backup task using Windows Backup and then send the errors reported.
-
Wednesday, June 06, 2012 7:04 PMThe issue can also be reproduced by running a shadow copy task, would that also work to help troubleshoot the issue?
-
Wednesday, June 06, 2012 7:07 PM
The issue can also be reproduced by running a shadow copy task, would that also work to help troubleshoot the issue?
What do you mean about "Running A Shadow Copy Task"?
Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
-
Wednesday, June 06, 2012 7:10 PM
manually creating a shadow copy.
vssadmin create shadow /For=X:
-
Wednesday, June 06, 2012 7:15 PM
Ok. Can you please provide me the exact error message after executing the mentioned command?
Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
-
Wednesday, June 06, 2012 7:21 PM
Will do. I just ran it now as a baseline test and it was successfully created. Once VSS is again in a failed state, I'll rerun the test and post the results as well as the windows event logs (which are also posted in Rich's original description).
Thank You
-
Thursday, June 07, 2012 3:01 PM
Here is the output:
(C) Copyright 2001-2005 Microsoft Corp.
Error: Another shadow-copy creation is in progress, so the current shadow copy c
annot be created. There are a number
of common scenarios causing this problem:
* If Shadow Copies of Shared Folders is set up, ensure that no two volum
es have schedules that lie within five minutes
of each other.
* If automatic backup of any form is scheduled, ensure that the backup s
chedule does not overlap with the schedule
used for Shadow Copies of Shared Folders.
Generally, retrying the operation after a few minutes or changing the schedule o
f an automatic task should fix this problem.
-
Thursday, June 07, 2012 4:18 PM
Just a quick update:
The backup task that I mentioned running in a previous post completed successfully on a data partition (E:\) but then failed against the system partition (C:\). When I checked the backup software logs, the logging stopped with the last log being a task to track changes on the system partition. I checked the windows log from that time period and found this:
A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the backup process is retried,
the error is likely to reoccur.
. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.
Operation:
BackupComplete Event
Context:
Execution Context: Writer
Writer Class Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Name: SqlServerWriter
Writer Instance Name: SQL Server 2008 R2:SQLWriter
Writer Instance ID: {7cfd1c94-c58a-43c6-9313-a72c4a1491d6}
Command Line: "C:\Program Files\Microsoft SQL Server\90\Shared\sqlwriter.exe"
Process ID: 4584If I restart the SQL VSS writer service, vssadmin list writers runs again.
I found a log for one of the databases was huge so I shrunk that. I checked the permissions for System on each of our SQL instances to make sure it was a sysadmin. I'll look at the error some more...
-
Thursday, June 07, 2012 5:02 PM
Try to stop SQL Server VSS Writer service from Services.msc console and test again. Based on my experience, this writer has some incompatibility with Windows Server Backup. Please report back the result...
Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
- Edited by R.AlikhaniMicrosoft Community Contributor Thursday, June 07, 2012 5:02 PM
-
Thursday, June 07, 2012 9:00 PMI'm confident that the backup will complete if I stop that service, and will try that as a workaround tonight, but I'd like to first try and identify the problem so that I can use the VSS Writer for SQL. I'll let you know if that allows the back up task to complete.
-
Friday, June 08, 2012 4:08 AMAs your previous post I found that you are using TMG 2010 on your Windows Server 2008 R2 server. Right? If so, please tell us which version of SQL Server has been installed on the server?
Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
-
Friday, June 08, 2012 2:27 PM
The backup completed last night for both partitions.
The version is SQL 2008 R2.
-
Friday, June 08, 2012 2:49 PM
So when you disable SQL Server Writer everything works well? Do you have installed Service Pack 1 of the SQL Server 2008 R2? If not, please install it, because it also installs the latest SQL Server Writer that may resolved your problem...
Please do it and report back the result...
Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
- Edited by R.AlikhaniMicrosoft Community Contributor Friday, June 08, 2012 2:50 PM Typo
-
Friday, June 08, 2012 3:23 PM
I should have written that they are version 2008 R2 SP1 10.51.2500.0, so we are already on SP1. Sorry about leaving that part out.
-
Friday, June 08, 2012 3:26 PM
Please tell us the version of the following files:
Sqlwriter_keyfile.dll
Sqlwvss_xp.dll
Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
-
Friday, June 08, 2012 3:32 PM10.50.2500.0 for both.
-
Friday, June 08, 2012 3:41 PM
Based on the following article, you have not installed any Update Packages to your SQL Server 2008 R2 SP1. The latest Update Package is 6 and Microsoft strongly recommends to install the latest Update Package.
http://support.microsoft.com/kb/2567616
By installing the latest Update Package (they are cumulative), the SQL Server VSS Writer is also updates to its latest version from Microsoft...
Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
- Edited by R.AlikhaniMicrosoft Community Contributor Friday, June 08, 2012 3:41 PM Typo
- Edited by R.AlikhaniMicrosoft Community Contributor Friday, June 08, 2012 3:42 PM
-
Friday, June 08, 2012 3:45 PMYes, that does contain a newer version of the SQL writer. I'll give it a try tonight and report back Monday.
-
Wednesday, June 20, 2012 3:03 AM
Any updates?
Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
-
Wednesday, June 20, 2012 2:22 PMSorry I haven't gotten to this yet, it has fallen in priority since I can get good backups of the server as a whole even if the SQL writer is not working. I should have an update soon.
-
Saturday, June 30, 2012 1:42 PM
The CU7 update did not fix the problem. CU7 was applied to the shared components and 3 of the 5 SQL instances running on the machine. The MSFW and ISARS instances for TMG did not get updated since those run as 2008 instances.
Stopping the SQL Server VSS Writer allows shadow copies to be created without a problem. With it running causes a timeout on the VSS generation whether using backup software of the vssadmin create shadow command.
Any other suggestions?
Rob
-
Saturday, June 30, 2012 5:04 PM
You can simply force Windows Server Backup to ignore the "SQL Server VSS Writer" functionality during the backing up process. To do this configuration, on a system with Windows Server 2008 R2, follow the steps below:
1. Run vssadmin list writers and record the "Writer ID" value of the "SqlServerWriter" writer. Look at the following figure:
2. Under the regkey "HKLM\Software\Microsoft\Windows NT\CurrentVersion\SPP", create a new MULTI_SZ key with the name DisabledWriters.
Note: SPP key does not exist by default. So you sould create it first and then the mentioned above step.
3. Enter the writer id {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a} with braces as the value.
4. Shut down wbengine service if it’s running. Use the command “net stop wbengine”. Restart the wbengine. Use the command “net start wbengine”.
As long as the key is in place, Windows Server Backup will not include the "SQL Server Vss Writer" in the system state.
Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
- Edited by R.AlikhaniMicrosoft Community Contributor Saturday, June 30, 2012 5:09 PM
- Edited by R.AlikhaniMicrosoft Community Contributor Saturday, June 30, 2012 5:09 PM
-
Friday, July 06, 2012 4:32 PM
The backup is not using Windows backup. So I don't think this registry key will help. In addition, this will disable the use of the writer for backups. We are doing that by stopping the service. The downfall is that any data in RAM for the SQL database will not be flushed since the writer is what causes the backup to be in a good state. So disabling it may work around the issue but doesn't resolve it.
Anyone else have suggestions on why this writer would be having these problems? I have several other servers with a similar configuration that do not have a problem. Just looking for suggestions on a fix.
Rob
.png)
