Recently set up a new file server (VM running Server 2012 R2). Server has separate OS and Data partitions (each on different physical disk array) and I've enabled Shadow Copies on the Data volume. Server is also running DFS/DFSR and replicating the files on the Data volume with other file servers. The VM is running on Hyper-V host, which is also Server 2012 R2.  

Each day, when a shadow copy snapshot is taken, the file server generates an ESENT Event ID 508 similar to the following:

DFSRs (1192) \\.\D:\System Volume Information\DFSR\database_5464_BC1C_64BC_2B2\dfsr.db: A request to write to the file "\\.\D:\System Volume Information\DFSR\database_5464_BC1C_64BC_2B2\fsr.log" at offset 4075520 (0x00000000003e3000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (25 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

So first thought was maybe I do have faulty hardware. But I set up a second file server (on separate physical host with identical hardware) and am seeing the same behavior on that server as well. The odds of both servers having faulty hardware are pretty low, so it must be my configuration.

I noticed the Shadow Copy storage area was set to the same volume as the snapshot being taken, so I changed that to use the OS volume instead, but that didn't fix it:

Then I tried turning off Windows write-cache buffer flushing on the Data volume, but that didn't help:

Tried allocating more (and static) memory to the server, rather than having it use Dynamic Memory, but no change there either. 

Using Hyper-V manager, tried moving the vhdx file from IDE controller to SCSI, but no change there.

Anyone else have any suggestions/insight into what the problem might be or how I can fix it?

Shaun

Recently feel our file server (Windows Storage Server 2012 R2) open file slowly. Server has separate OS and Data partitions (External Storage) . Server is also running DFS/DFSR and replicating the files on the Data volume with other file servers. The Server is running on Windows Storage Server 2016 .  

We found when users feel slow, the file server generates  ESENT Event ID 508,510,533 similar to the following:

508
DFSRs (2408) \\.\F:\System Volume Information\DFSR\database_D428_ADCA_28AD_AC44\dfsr.db: to the file "\\.\F:\System Volume Information\DFSR\database_D428_ADCA_28AD_AC44\dfsr.db" at offset 1148928000 (0x00000000447b4000) for 16384 (0x00004000) bytes succeeded but took an abnormally long time(22 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

510
DFSRs (2408) \\.\E:\System Volume Information\DFSR\database_8476_DF15_76DF_738\dfsr.db: to the file "\\.\E:\System Volume Information\DFSR\database_8476_DF15_76DF_738\dfsr.db" at offset 1027284992 (0x000000003d3b2000) for 8192 (0x00002000) bytes succeeded but took an abnormally long time(36 seconds) to be serviced by the OS. in addition 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 28804 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

533
DFSRs (6932) \\.\E:\System Volume Information\DFSR\database_8476_DF15_76DF_738\dfsr.db: to the file“\\.\E:\System Volume Information\DFSR\database_8476_DF15_76DF_738\dfsr.db”at offset 91471872 (0x000000000573c000) for 8192 (0x00002000) bytes has not completed for 36 second(s). This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

Anyone else have any suggestions/insight into what the problem might be or how I can fix it?

Hello everyone,

I do have a very strange issue with my file server. Let me first describe the infrastructure.

OS: Windows Server 2016
Roles: File and Storage Services
Type: Member of a 2016 Domain

On the file server I do have to following structure/permission:

• F:\
  • ANWDTest
    • ZZZ
      • DIMS
      • Wagenbuch

The NTFS permissions to those folders is like that:

• ANWDTest
  Inheritance disabled
  CREATOR OWNER - Full control - Subfolders and files only
  SYSTEM - Full control - This folder, subfolders and files
  Administrators - Full control - This folder, subfolders and files
  L_NTFS_J_R - Read & execute - This folder only
  
  
• ZZZ
  Inheritance enabled
  L_NTFS_J_ZZZ_R - Read & execute - This folder only
  
  
• DIMS
  Inheritance enabled
  L_NTFS_J_ZZZ_DIMS_R - Read & execute - This folder, subfolders and files
  L_NTFS_J_ZZZ_DIMS_W - Modify - This folder, subfolders and files
  
  
• Wagenbuch
  Inheritance enabled
  L_NTFS_J_ZZZ_Wagenbuch_R - Read & execute - This folder, subfolders and files
  L_NTFS_J_ZZZ_Wagenbuch_W - Modify - This folder, subfolders and files

So far I think this is nothing special, now here is my issue:

When I delete the "Wagenbuch" or the "DIMS" folder this does remove the group "L_NTFS_J_ZZZ_R" from the "ZZZ" folder AND does remove the group "L_NTFS_J_R" from the "ANWDTest" folder... and I do have absolutly no idea why this is happening.

Does anyone see an error in the setup or did face similar issues? I am totally lost here, even no idea where to start searching.. Google did also not help at all.

Thanks for the support!

UPDATE 1: To be sure that is not an issue of our file server - I did setup the same structure on an other 2016 server, and did face the same issue.

UPDATE 2: In the meantime I did the same setup on a 2012 R2 server and there is no issue at all, so this seems to be related to Server 2016.

UPDATE 3: I just did a test setup of the brand new 2019 server - I do have the exact same error as on server 2016.

Hi All,

I have a new project which is to create a DFS namespace with DFSR on our 2 company sites.

Scenario is:

-We have an existing standalone fileserver which has \\SERVER share name and we need to migrate it on our new FS but with the new technology DFS.

-We have files that has hard coded links that points to \\SERVER.

-I'm having problem since when create domain base namespace, it automaticall adds the netbiosname before the share name.ex. \\mydomain.com\Share

As mentioned on the title, How can i change the newly create DFS namespace to be the same with my existing file server share name? This is for us to avoid changing all the hard coded links on our thousand files.

Hi All,

Hoping someone somewhere has seen this before, I've googled this problem a fair bit without any joy..

One of our DFS Namespaces is reporting the below under 'DFS Management'.

"ERROR - An item with the same key has already been added."

Background/What I can say -

• Domain environment.
• The namespace is still visible within AD, in the usual place.
• This particular namespace has near 1500 links within it.
• The namespace cannot be UNC'd to, unlike our other namespaces (all near-identical setup).
• I have been able to export the contents of the config via dfsutil for reference.
• DFS Management gives the option to 'display the namespace' which only leads to the previous error message - if I am fast enough to right-click and click on 'Properties' before the error appears, it causes MMC to crash.
• The namespace appears to be functioning as expected right now (nearly 4 hours after it was first noticed by an engineer), however we simply cannot manage it via DFS Management (I've not tried adjusting any existing links via dfsutil).

Any help will be greatly appreciated, let me know if you want any more details!

Cheers!

I used a 250GB SSD and a 2TB HDD to creat a storage tiers. Now I want to add another disk into the storage pool and extend the storage tiers. When I choose the option "extend the virtual disk", it shows "Not supported type". 

So how to add disks into an existing storage tiers in Windows Server 2016？

Thank you!

We have an Scale-out File server with 2 nodes.

If node 1 is active, Node 2 has an offline disk in disk management. When a failover happens the disk on node 1 will become offline and the disk on node 2 will become online.

Our problem is that someone removed the offline disk from (inactive) node 2 by ejecting it in Disk Management on node 2.

Now we want to get this disk back on node 2. What should we do to resolve this issue

Hello,

I have a storage pool composed of 5 disks and I built a storage space of 18 tb with parity. One of the disk crashed and I managed to replace it with a new one but for some reason the volume D: does not want to come back as normal and it is now degraded and offline. With the help of diskpart I can manage to bring it online however it is in readonly mode, I can see the files however I can only read them of course, so while the system is stating "offline scan and repair needed"  it seems I cannot do it because of the current readonly mode, I have maybe an idea why the volume did not come back properly, it seems one of the five disk is showing bad sectors as I can see events 7 "The device, \Device\Harddisk4\DR4, has a bad block." (thought all the 5 disks are shown as "healthy" in the Storage Pool and the virtual Disk D: shown also as "Healthy" in Disk Management ?!?)

Chkdsk d: \scan on the drive is showing the following :

PS C:\Windows\system32> chkdsk d: /scan
The type of the file system is NTFS.
Shadow copying the specified volume is not supported.
A snapshot error occured while scanning this drive. Run an offline scan and fix.

Can someone kindly advise what should I do in order to fix that storage space?

Problem:

This error is periodically recorded in the System event log:

Event ID: 10000
Source: DistributedCOM
Event Data: Unable to start a DCOM Server: {9C38ED61-D565-4728-AEEE-C80952F0ECDE}. The error: "0" Happened while starting this command: C:\Windows\System32\vdsldr.exe -Embedding

This error appears when DFS-R is installed, when the computer is rebooted, every time the DFS-R service is started, and whenever application aware checkpoint-based backups are taken.

Simple reproduction steps:

1. On a clean computer or VM, boot from the Microsoft-provided Windows Server 2019 media. I used SW_DVD9_Win_Server_STD_CORE_2019_1809.1_64Bit_English_DC_STD_MLF_X22-02970.ISO from the Volume Licensing website.
2. Install Windows Server 2019
3. Install DFS-R using PowerShell: Install-WindowsFeature -Name FS-DFS-Replication
4. Error will now be present in Event Log: Get-EventLog -LogName System -EntryType Error -Source DCOM
5. Restarting the computer, or just restarting the DFS-R service, will cause another error to be added to the event log.

Notes:

• Problem affects Core and Desktop Experience
• Problem affects Standard and Datacenter
• As of 2019-Sep-17, installing Windows Updates doesn't make a difference
• Joining a domain, or not, makes no difference
• Properly configuring DFS Replication does not make a difference

Request:

This issue is related to another TechNet question, but there's no answer there.

I thinkit's ignorable, but I don't really know.  I would like to "fix" whatever is causing this error.  Or, at least get some authoritative comments that it is safe to ignore, and preferably have someone at Microsoft correct the problem that is leading to an ignorable error.

Any and all help would be appreciated.  Thank you.

-Tony

Anyone experienced Microsoft Sync Center Issues after move from a NAS to an EMC isilon based NAS(in the process changing Server Name & IP Address) resulting impact on Network shares UNC path name? We have certain users still having their home drive path referencing the old path ie (\server\oldshare instead of\server\newshare still being referenced). We ensured the old UNC to new UNC was properly defined and effected via gpo for Folder redirection. This policy has been enforced thoroughly on clients and tested after several updates and restarts.

Manually deleting the old references on client by IT support still results into conflicts and eventually rolls back after a while to referencing the old path. Our conclusion was this https://stealthpuppy.com/configuring-an-automatic-resolution-policy-for-offline-files-in-windows-7/doesnt work properly on Windows 10

The Client has no control over this since option has also been greyed out due to a global policy restriction making it impossible to effect this change on the client side of things. Is there any way this can be resolved via group policy via a global reg update setting? Do we have to re initiate offline caching on clients or via gpo? I also noticed that this has affected most clients migrating from windows 7 -> 10, most clients working offline or remotely via wifi/vpn outside the corporate network or havent been online for several days due to business travel.

We have also adhered to all best practices here https://4sysops.com/archives/folder-redirection-part-5-best-practices/

I am thinking of possible scenarios via global policies - Reg Update of Offline cache paths from 7 -> 10 via GPO or manually via Clients?

Trigger manual offline sync cache process a step before or during the Migration process so Files are where they supposed to be when migration is done.

We have also found a script here which can trigger this cache manually but will require system priveleges which the user doesnt have and we want to avoid having the user do this. We might probably include that in our migration process ->https://gallery.technet.microsoft.com/scriptcenter/How-to-sync-offline-files-0b2f0e96

Is the information in this article https://social.technet.microsoft.com/Forums/windows/en-US/9ce9195f-0aea-4019-84e5-13bd01e36b19/cannot-remove-offline-files-from-sync-center?forum=w7itpronetworking relevant?

Tips will be welcomed

Greetings,

I am currently working on DFS implementation project. Two DFS Server: primary in main site and secondary in DR site

i got recommendation from Microsoft to disable target folders in secondary DFS Server in order to avoid conflict in data replication. i have many target foders (above 70).

I wanted to enable or disable target folders by command and i found tool named Dfsutil.exe

i tried to run the command as below but it give me an error:

dfsutil.exe Property State Online "\\DFS01\FS01" "\\domain.local\sharing\FS01" 

Noting that DFS01 is the server name and domain.local\sharing\FS01 is namespace share path

Error is as below:

Could not complete the command successfully.
SYSTEM ERROR - The RPC server is unavailable.

Any thoughts? 

Regards,

My company uses windows server 2012 without active directory. On the server's C drive we have a folder named "Shared Space". Inside this folder there are various subfolders for different departments, e.g Marketing Folder, Management folder, Procurement folder etc. 

We want users to be able to access all folders except some folders, like "Management folder". If they try to access it then we want the system to ask a username and password. What is the simplest way to achieve this?
 

I have a client with an Acronis Cloud backup and it has been failing.

The error says the backup was cancelled by user, and I know that this is false.

I have worked with Acronis support, which seems sluggish to the point of almost unresponsive.

I have worked with them to get to a point where it appears that maybe a writer is failing, but I am not familiar enough with it to determine how to approach it, and I really am tired of waiting on Acronis and suspect they will be telling me to fix this error before they continue assisting.

Rebooting the server has no effect, changing timeouts and backup times have no effect either.

Anyway....

I copied and pasted all of the IDs from the vssadmin list writers, so I know there are no typing mistakes.  This is the one in question.

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {6ce6b02a-cad3-4f5f-bcf9-52bdd18e811c}
   State: [1] Stable
   Last error: No error

This is the error when attempting backup with diskshadow from an administrative command prompt.

ERROR: The writer "{4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}" was not included. Aborting ...
       Check the syntax of the writer name and writer ID.

Any assistance would be appreciated

I have 4 Windows 2019 virtual servers running in VMWare and on a single domain.  (2 in one site and 2 in another geographical site).  I want to build a Stretch Cluster using Storage Replica.  All servers have the same size and configuration of disks created.  Can I just add the 4 servers to cluster manager and then add the File Server role to the cluster to create a shared folder?  Or do I need to create a cluster at each site and then replicate the clusters across?  I'm a little confused at how this might work.  I'd also be willing to have 2 servers at one site and just a single server at the second site if that makes it easier.

Thanks in advance.

We are currently testing migrating from PowerPathAdmin Software to the Native Windows Multipathing (MPIO).

When attempting to add the storage device via the MPIO GUI or command line the server will reboot however the disks still won't appear in "MPIO Devices" or when running the mpclaim command no disks are being detected:

New-MSDSMSupportedHw -VendorId DGC -ProductId VRAID

PS C:\Windows\system32> mpclaim -s -d

No MPIO disks are present.

----------------------------------------------------------

PS C:\Windows\system32> mpclaim -e

"Target H/W Identifier   "   Bus Type     MPIO-ed      ALUA Support
-------------------------------------------------------------------------------
"XtremIO XtremApp        "   Fibre        NO           ALUA Not Supported
"DGC     VRAID           "   Fibre        NO           Implicit and Explicit

-------------------------------------------------------------------------------

PS C:\Windows\system32> Get-MPIOAvailableHW

VendorId ProductId        IsMultipathed   IsSPC3Supported BusType
-------- ---------        -------------   --------------- -------
XtremIO  XtremApp         False           False           FibreChannel
DGC      VRAID            False           True            FibreChannel

A separate job was raised with DELL EMC and they advised to update the drivers on our HBA cards in the Dell M630 blades and this was done and still not working. Please also note we were able to get the MPIO to work with one of our Windows 2008 SQL Server Clusters.

for example in Windows Server 2008 it looks like the following:

i have 2 domain controller with same model HP DL 380 G6 with server 2003. PDC and AD DC.My AD DC become unserviceable due to hardware issue.now i have DL380 G9 model with different hardware. now i want to use this as a AD DC with DL 380 G6 PDC.

the issue is i have very important applications on old hard drive of DL 380 G6 with server 2003.

i tried to install serevr 2003 on new AD DC but failed, minimum server 2012 should install on it.

how i can recover all settings of old hard drives in to new machine?

For the Get- and Set-DfsnServerConfiguration Powershell cmdlets (and the equivalent WMI classes), there are two properties for setting referral behavior:  EnableInsiteReferrals and EnableSiteCostedReferrals.  In both cases, the cmdlet documentation states that this is a boolean setting, but that the default value is "None".   The documentation does NOT state whether "None" is interpreted as $false or $true - I assume $false.  

What is the actual default interpretation of "None" in this context for currently supported OS versions (Server 2012/2012 R2/2016/2019)?

Thanks!

Hi Everyone,

I have a user within the organisation that has moved a file from a folder to a newly created folder.

They seem to have lost track of where they had originally transferred the file from (original folder location).

Is there a way I could find out where the original file location?

Thanks

D

Hello

We use a bunch of file server and AD RMS server in our work environment to protect documents.
File Management Tasks are launched on the server file. Small files (up to 1.5 GB) are encrypted almost instantly, but larger files are not encrypted at all, and the error message is "Unable to protect file appears in the logs: The compound file is too large for the current implementation"
Tell me where I have a bottleneck in this system that cannot handle large files.