Hello, 

We are using Windows Server 2008 R2 Enterprise. We have SQL Server 2008 R2 and MS Dynamics CRM 2011 installed on the machine. The total disk space is 1 TeraBytes, with 991 GB C:/ drive partion. 

Last morning when we tried to open the SQL Server, we found that we were not able to perform any operation because C:/ drive has 0% free space and is completely full. When I check the actual size of files in c:/, it was only 41 GB. We tried to perform several remedies but no luck. 

Urgent help is needed on this issue as project operations is getting affected. 

Kindly advise. 

Best, 

Fahad

Fahad Ali Shaikh

Is it possible to disable 64 bit cookies or enable 32 bit cookies within a Windows 2012 R2 NFS Server?

We are performing a migration, and the current NFS client (solaris 10) is passing back the 64bit fileid / cookie to the application.  Unfortunately the application is 32bit and it promptly fails to see the file.  Upgrading the application isn't an option at this time (as it works on the old linux NFS we are migrating from), so was looking for alternative.

Another alternative is NFS V2, but would rather see what else we could do.

Thanks in Advance

All,

I have been struggling on getting some virtual machines to disk punch and getting the right syntax to work.

The below is the powershell script which was posted on "whats up duck". However getting this to run via a scheduled task posed me a number of issues since to get a scheduled task to show on a machine required a reboot (this was done via group policy), I couldn't get it to display or run any way else. The other alternative would be to do a script which would configure a scheduled task and then remove it, this was just a pain.

Content of Write-ZeroesToFreeSpace.ps1"

<#
 .SYNOPSIS
  Writes a large file full of zeroes to a volume in order to allow a storage
  appliance to reclaim unused space.

 .DESCRIPTION
  Creates a file called ThinSAN.tmp on the specified volume that fills the
  volume up to leave only the percent free value (default is 5%) with zeroes.
  This allows a storage appliance that is thin provisioned to mark that drive
  space as unused and reclaim the space on the physical disks.

 .PARAMETER Root
  The folder to create the zeroed out file in.  This can be a drive root (c:\)
  or a mounted folder (m:\mounteddisk).  This must be the root of the mounted
  volume, it cannot be an arbitrary folder within a volume.

 .PARAMETER PercentFree
  A float representing the percentage of total volume space to leave free.  The
  default is .05 (5%)

 .EXAMPLE
  PS> Write-ZeroesToFreeSpace -Root "c:\"

  This will create a file of all zeroes called c:\ThinSAN.tmp that will fill the
  c drive up to 95% of its capacity.

 .EXAMPLE
  PS> Write-ZeroesToFreeSpace -Root "c:\MountPoints\Volume1" -PercentFree .1

  This will create a file of all zeroes called
  c:\MountPoints\Volume1\ThinSAN.tmp that will fill up the volume that is
  mounted to c:\MountPoints\Volume1 to 90% of its capacity.

 .EXAMPLE
  PS> Get-WmiObject Win32_Volume -filter "drivetype=3" | Write-ZeroesToFreeSpace

  This will get a list of all local disks (type=3) and fill each one up to 95%
  of their capacity with zeroes.

 .NOTES
  You must be running as a user that has permissions to write to the root of the
  volume you are running this script against. This requires elevated privileges
  using the default Windows permissions on the C drive.
 #>
 param(
   [Parameter(Mandatory=$true,ValueFromPipelineByPropertyName=$true)]
   [ValidateNotNullOrEmpty()]
   [Alias("Name")]
   $Root,
   [Parameter(Mandatory=$false)]
   [ValidateRange(0,1)]
   $PercentFree =.05
 )
 process{
   #Convert the $Root value to a valid WMI filter string
   $FixedRoot = ($Root.Trim("\") -replace "\\","\\") + "\\"
   $FileName = "ThinSAN.tmp"
   $FilePath = Join-Path $Root $FileName

   #Check and make sure the file doesn't already exist so we don't clobber someone's data
   if( (Test-Path $FilePath) ) {
     Write-Error -Message "The file $FilePath already exists, please delete the file and try again"
   } else {
     #Get a reference to the volume so we can calculate the desired file size later
     $Volume = gwmi win32_volume -filter "name='$FixedRoot'"
     if($Volume) {
       #I have not tested for the optimum IO size ($ArraySize), 64kb is what sdelete.exe uses
       $ArraySize = 64kb
       #Calculate the amount of space to leave on the disk
       $SpaceToLeave = $Volume.Capacity * $PercentFree
       #Calculate the file size needed to leave the desired amount of space
       $FileSize = $Volume.FreeSpace - $SpacetoLeave
       #Create an array of zeroes to write to disk
       $ZeroArray = new-object byte[]($ArraySize)

       #Open a file stream to our file
       $Stream = [io.File]::OpenWrite($FilePath)
       #Start a try/finally block so we don't leak file handles if any exceptions occur
       try {
         #Keep track of how much data we've written to the file
         $CurFileSize = 0
         while($CurFileSize -lt $FileSize) {
           #Write the entire zero array buffer out to the file stream
           $Stream.Write($ZeroArray,0, $ZeroArray.Length)
           #Increment our file size by the amount of data written to disk
           $CurFileSize += $ZeroArray.Length
         }
       } finally {
         #always close our file stream, even if an exception occurred
         if($Stream) {
           $Stream.Close()
         }
         #always delete the file if we created it, even if an exception occurred
         if( (Test-Path $FilePath) ) {
           del $FilePath
         }
       }
     } else {
       Write-Error "Unable to locate a volume mounted at $Root"
     }
   }
 }

So, PSEXEC then utilising a CMD then powershell to execute this script from a list was the best way. You need to run your CMD with your domain admin account (shift and right click CMD and run as different user) because the issues with PSEXEC is it will try to use your local rights to create the service which fails and gives you access is denied.

psexec -d -u domain\username  @C:\users\%username%\desktop\diskpunch\computers.txt cmd /c "\\dom.ain\NETLOGON\Diskpunch\diskpunch.bat"" (We're putting it in netlogon since we're using it again later)

Then put in your password

((IN YOUR COMPUTERS.TXT JUST LIST THE SERVERS AND PLEASE NOTE THE DOUBLE QUOTES ON THE END))

The batch file has the following

powershell.exe -executionpolicy Bypass -command "Get-WmiObject Win32_Volume -filter drivetype=3 | \\Dom.ain\NETLOGON\diskpunch\Write-ZeroesToFreeSpace.ps1"

This may seem simple for some of you but it really got on my nerves getting the config right so I thought I'd share incase anyone else wants to disk punch their Virtual Infrastructure.

Anyway, hope this helps someone.

We're continually running into a problem where a user will open a password-protected Excel file as read-only, but then a second user is unable to open that file with write permissions after entering the password (the second user will receive a message that the file is locked for editing by "user").

When I view the status of the file using the "Share and Storage Management" admin tool and selecting "Manage Open Files", the "Open Mode" reports "Read, Write" for the user who opened the file as read-only: 

In Excel, on that user's machine, the status will show "Read Only". The first user will then have to close the file before the second user is able to open it with write access after entering the Excel password.

I've tried opening a different password-protected file to see what the Share and Store Management admin tool reports, and noticed that when I first open the file and am prompted to enter the password, the open mode on the file server is "Read, Write". After I choose "Read Only" in Excel, the open mode on the file server changes to "Write". Then a few seconds later, the file is not reported as being open at all on the file server (even though I have it open in Read-Only mode - which sounds like what the normal behavior should be). It seems that the file is getting hung in "Read, Write" mode sometimes. This is Windows Storage Server 2008, SP2. The file share is a DFS share.

Shaun

Hello,

I'm having a problem renaming new folders in one directory only.
The folder is a sitting on a file server which is apart of the file server cluster Windows 2008 R2.

Let say I have a volume mounted on X:

I have the following folders

X:\Test
X:\Test\Desktop
X:\Test\Favourite

If I create a new folder under X:\Test\Desktop that will be called New Folder by default. After the creation the system will not let me rename it (folder or file in use by another process), however I can move it or delete it without problem.

I have checked if the file is locked already with different software, did not help, folder not locked.

I have admin rights, I'm the owner also.

I can create and rename folders on the same driver anywhere except from the Desktop folder. File server has been rebooted and failed over to other node in the cluster, but the problem still stand.  Have no antivirus installed.

Any idea what is the problem? Where should I look?

Thanks!

DA-Sky

Hello,

we want to audit every delete action on our fileserver. But when i set it up all read actions are also logged.

Is there an option to only log deleted files?

Regards,

The Problem:

These files are located at : "c:\ClusterStorage\Volume1\System Volume Information"

This Cluster Shared Volume is mounted at three nodes on that location, say Node1, 2 and 2. All running windows 2012 (not R2)

We're using NetBackup (3rd party tool) to take full VMs Backups

Things I've tried:

• Delete them using GUI o simple CLI tools. Nop-
  
• Close open handles using processExplorer. I tried it on all nodes nad when I found an open handles (sometimes I got no results on all nodes) they were owned by SYSTEM (pid 4); impossible to close.
  
• Tried taking ownership since I can't event check ACLs on these files. Tried using GUI, subinacl and cacls. Nothing worked.
  
• Since everything points to VSS, I tried stopping related services (swprv and vss) as shown in this post. Also, tried stopping Netbackup related services on all nodes.
  

This is an example of these files:

04/05/2015  10:10 p.m.       191.512.576 {3e733b9f-f181-11e4-93f3-e0db55058cb5}{3808876b-c176-4e48-b7ae-04046e6cc752}
04/05/2015  10:16 p.m.       268.238.848 {3e733bac-f181-11e4-93f3-e0db55058cb5}{3808876b-c176-4e48-b7ae-04046e6cc752}
05/05/2015  10:11 p.m.   201.249.964.032 {3e733bc3-f181-11e4-93f3-e0db55058cb5}{3808876b-c176-4e48-b7ae-04046e6cc752}
05/05/2015  10:13 p.m.       225.771.520 {70b98db5-f383-11e4-9401-2c44fd7c8153}{3808876b-c176-4e48-b7ae-04046e6cc752}
05/05/2015  10:16 p.m.       318.193.664 {70b98e8f-f383-11e4-9401-2c44fd7c8153}{3808876b-c176-4e48-b7ae-04046e6cc752}
06/05/2015  11:12 a.m.   225.812.938.752 {70b98f5f-f383-11e4-9401-2c44fd7c8153}{3808876b-c176-4e48-b7ae-04046e6cc752}
23/04/2015  10:22 p.m.       593.444.864 {7568117e-e9e9-11e4-93f3-e0db55058cb5}{3808876b-c176-4e48-b7ae-04046e6cc752}
24/04/2015  11:23 a.m.   204.293.476.352 {75681191-e9e9-11e4-93f3-e0db55058cb5}{3808876b-c176-4e48-b7ae-04046e6cc752}
24/04/2015  11:25 a.m.       222.904.320 {7568158a-e9e9-11e4-93f3-e0db55058cb5}{3808876b-c176-4e48-b7ae-04046e6cc752}
24/04/2015  11:30 a.m.       561.364.992 {7568159a-e9e9-11e4-93f3-e0db55058cb5}{3808876b-c176-4e48-b7ae-04046e6cc752}
24/04/2015  12:31 p.m.     6.228.623.360 {756815ab-e9e9-11e4-93f3-e0db55058cb5}{3808876b-c176-4e48-b7ae-04046e6cc752}
24/04/2015  02:11 p.m.     4.969.119.744 {75681606-e9e9-11e4-93f3-e0db55058cb5}{3808876b-c176-4e48-b7ae-04046e6cc752}
24/04/2015  10:05 p.m.    33.613.393.920 {756816cf-e9e9-11e4-93f3-e0db55058cb5}{3808876b-c176-4e48-b7ae-04046e6cc752}
24/04/2015  10:08 p.m.     1.422.983.168 {756819e4-e9e9-11e4-93f3-e0db55058cb5}{3808876b-c176-4e48-b7ae-04046e6cc752}
27/04/2015  10:03 p.m.   277.178.253.312 {756819f6-e9e9-11e4-93f3-e0db55058cb5}{3808876b-c176-4e48-b7ae-04046e6cc752}
27/04/2015  10:14 p.m.       411.271.168 {75683447-e9e9-11e4-93f3-e0db55058cb5}{3808876b-c176-4e48-b7ae-04046e6cc752}
27/04/2015  10:18 p.m.       267.419.648 {75683470-e9e9-11e4-93f3-e0db55058cb5}{3808876b-c176-4e48-b7ae-04046e6cc752}

[...]

 Any ideas?

 Thanks.

Rodrigo.

Hi,

I am having an issue where our DFS has stopped replicating. Currently we are replicating a number of folders (7) that contain excel files that we have to distribute to different offices across the country.

Looking into the event logs I see Event ID 4012. The event says to remove the affected member from the DFS and re-add it to resolve the issue. I backed up the folder contents on each of the members and removed the server from under the memberships tab in the DFS snap in. I then proceeded to re-add the server. After re-adding and allowing sufficient time to begin replication, I am still given the same error.

I used "dfsrdiag pollad /verbose" and the operation completed successfully. I also ran dfsrdiag pollad /member:rjc-van01 and this also completed successfully.

I am stumped on this one.

Guys.

Got a weird issue. I have two Server 2012 R2 servers running DFS. I have been using the get-dfsrbacklog command for months with out issue. After i restarted SERVER-B i am unable to retrieve the DFS backlog from either SERVER-B or SERVER-A. I receive the message below. 

I am unsure what the issue is and google is not turning up much. Can anyone advise?

Get-DfsrBacklog : Could not retrieve the backlog information. Replication group: "EUHome" Replicated folder: "EUHome"

We recently migrated from our windows 2003R2 file server environment to 2012R2.  Ever since the migration we have experienced file corruption on multiple types of files.  (.mdb, .pst, xls)  The majority of these files have been access DB and email .pst archive files. (I know .pst files not supported)   The error messages for the .mdb files are typically "Your  networks access was interrupted".  For .xls, it would just indicated that the file could not open.  

Both of these volumes are setup to dedupe.  I've read some articles that say that deduplication could be the issue and that you can exclude certain file types/extensions from deduplication.  In checking the current deduplication, there are some exclusions but not for .mdb, .pst or xls.

ExcludeFileTypeDefault  : {edb, jrs}

NoCompressionFileType   : {asf, mov, wma, wmv...}

I've read some articles that suggested that the problem is that SMB is the issue and that I should disable SMB 3.0.. Others commented that you should not turn off SMB 3.x on the server because you would loose many of the benefits that SMB 3.x provides and that it may cause other issues.  The clients are all running Windows 7 Pro, and on the server it shows the access from the clients are v2.10, which is the default for Windows 7.  There were some patches for 2012R2 to turn off Leasing, which is described as another form of Oplocks.. I did install this patch but the corruption continues. https://www.microsoft.com/en-us/download/details.aspx?id=42738

We also ran chkdsk /scan on the two drives that the user files are located. On one of the drives, it did find some errors. "Volume Bitmap is incorrect".  After a reboot, and a rerun, these errors have been cleaned.

Another strange thing we noticed is that both drives that we are having these corruption issues on are being deduped.  (get-dedupvolume |fl ) It clearly shows that both are enabled.  The weird thing is that only one of the drives listings are blue, the other is the default black.  Shouldn't windows explorer list them both in blue? 

We're at a loss on what to do next.. Any suggestions on how to start eliminating possibilities to find the solution?

For the migration, For the most part, we followed these instructions http://blogs.technet.com/b/josebda/archive/2014/11/05/migrating-file-server-from-windows-server-2003-to-windows-server-2012-r2.aspx

William McConnell

I am reviewing Microsoft's ODX documentation.  It states the following:

The Windows host also limits the number of file fragments to 64. If the offload read request consists of more than 64 fragments, Windows fails the copy offload request and falls back to the traditional copy operation.

I have two volumes (S: and T:) on an iSCSI SAN.  I have a test file 960MB.bin on my S:\ drive.  My disk editor shows that this file is comprised of 180 clusters:

I then copy the file from the S:\ volume to the T:\ volume.  During the copy operation, I monitor the traffic going to the iSCSI volumes.  I see 180 back-to-back ODX transfers comprised of the following sequence:

• Source Volume:  CDB - Populate Token
• Source Volume:  CDB - Receive ROD Token Information
• Destination Volume:  CDB - Write Using Token
• This repeats a total of 180 times until the file copy is complete

So when Microsoft's documentation states that The Windows host also limits the number of file fragments to 64, what is it referring too?  If it's referring to the file fragmentation like I show above, why did ODX engage for me?  Is there a difference between Server 2012 and 2012 R2?  Is there a registry key to adjust this setting?

Storage spaces does not seem to be the ticket and Disk Managment does not offer mirror for the EFI partition. I found a KB for Server 08 that was about 10 pages long that had a lot of diskpart and bcdedit stuff.

I hope I am just missing something simple.

Thanks,

Grey

I created a MMC console on my Windows 7 workstation with a Disk Management Snap-in for each of my servers which run Server 2003 and 2008 R2.  I have just added a Server 2012 R2 to my domain and added Disk Management Snap-in for it in my console.  When I select Server 2012 R2 in the console it reports that it is "Unable to connect to Virtual Disk Service".  I ran the following commands on the 2012 R2:

sc config vds start=auto

Result: [SC] ChangeServiceConfig SUCCESS

net start vds

Result: The requested service has already been started.

This did not resolve the problem.  Please help me figure out how to view the 2012 R2 server's Disk Management remotely using an MMC console.

Thank you in advance!

Hi all - hope someone can help

I have a problem on Windows 2008 and Windows 2012 servers

Users have there own network drive on the server and are creating .tmp files - think this is through excel

They can't delete them - even after a system reboot

I can't delete them from the administrator a/c  on the server unless I reboot the server first

Can't change the permissions

Have seen question asked before - but that was related to SEP - we are no longer running SEP - have changed to Panda

This was happening before and after the removal of SEP

Hello,

Is there a technique which provides permissions to non Domain Admins to create and manage Domain based DFS Namespaces in 2012 R2?  Namely, the use of ms-DFSR-GlobalSettings or some other attributes?

We really don't want nonDomainAdmins to have this control, but I couldn't find anything specific on this.  I know there is delegated permissions to manage after a Namespace is created.

Thanks for your help! SdeDot

I have recently upgraded a clients servers to Windows Server 2012 & since doing so have lost the ability to scan to folder.

Both servers are domain controllers and previously on a 2008 domain controller I would have had to make the following change to allow scan to folder:
 Administrative Tools
 Server Manager
 Features
 Group Policy Manager
 Forest: ...
 Default Domain Policy
Computer configuration
 Policies
 Windows Settings
 Security Settings
 Local Policies
 Security Options
 Microsoft Network Server: Digitally Sign Communications (Always)
 - Define This Policy
 - Disabled

However I have applied this to the Windows 2012 server but am still unable to scan, possibly due to added layers of security in server 2012. The error on the scanner is Authentication with the destination has failed check settings.
I have also tried the following at the server:
Policies -> Security Policies
Change Network Security: LAN Manager authentication level to: Send LM & NTLM - Use NTLMv2 session security if negotiated.
Network security: Minimum session security for NTLM SSP based (including secure RPC) clients and uncheck the require 128 bit.
Network security: Minimum session security for NTLM SSP based (including secure RPC) servers and uncheck the require 128 bit
I have created a user account on the server for the ricoh and set this in the settiings of the Ricoh and verified everything is correct.

Are there any other things I have missed?

Hi all how are you today, Here is my Issue i'm attempting to setup DFS on our network and its not working quite how I expected it to. I have a Domain Controller at a branch office running Server 2012 that connects to our Domain Controller here at our main office running Server 2008, now the DC at our branch office also functions as the file server considering it has more than enough storage space on it. At the main office we have 1 DC and a file server running Server 2008 and I setup DFS on our file server and configured a namespace and replication group for the folder I want to replicate between the two servers  and then I get errors

4004

4102

5002

in that order on the branch office DC. Now if I set up a new share on our main office DC with the same name and same permissions as the folder i'm trying to replicate between the main office storage server and branch office DC and then throw a few text documents and files in there it works flawlessly, I even put a 50gb folder into it to see if it would continue working and it did. So I dont know what is wrong but what I find particularly interesting in the 5002 error is the "Error: 5 (Access is denied.)" line of text under additional information. Now I seen people all over technet with that same error and it has never been solved, well this time we have to solve it guys so any and all help would be appreciated.

Viper Technologies Computer Repair Putting The Venomus Bite Back In Your Computer We Are Located In Antigonish ,NS Canada Check Us Out HTTP://WWW.VIPERTECHNOLOGIES.TK

On a Windows 2003 server, I have a dedicated hidden share where I store all Users' Home Directory folders.

Normally I can remote browse to the share via UNC.

However some folder remain hidden unless I either browse directly from the file server itself. This will work when using the UNC path as well.

I did see that the icon does look different. The ones I cannot see remotely are in yellow but with a sheet of paper at the top.

Hi There,

Massive shot in the dark here but I am struggling with a pretty major issue atm.  We have a production file server that is hosted on the following:

Dell MD 3220i -> iSCSI -> Server 2008 R2 Hyper-v Cluster -> Passthrough Disk -> Server 2012 R2 File Server VM

Essentially 3 times now, roughly a month or so apart.  The file server stops accepting connections.  During this time, the server is perfectly accessible through rdp or with a simple ping.  I can browse the files on the server directly but no-one appears to be able to access the shares over SMB.  A reboot of the server fixes the issue.  

As per a KB article I removed nod antivirus from the server to rule out a conflicting filter mode driver after the second fault.  Sadly yesterday it happened again.

The only relevant errors in the servers log files are:

SMB Server Event ID 551
SMB Session Authentication Failure

Client Name: \\192.168.105.79
Client Address: 192.168.105.79:50774
User Name: HHS\H6-08$
Session ID: 0xFFFFFFFFFFFFFFFF
Status: Insufficient server resources exist to complete the request. (0xC0000205)

Guidance:

You should expect this error when attempting to connect to shares using incorrect credentials.

This error does not always indicate a problem with authorization, but mainly authentication. It is more common with non-Windows clients.

This error can occur when using incorrect usernames and passwords with NTLM, mismatched LmCompatibility settings between client and server, duplicate Kerberos service principal names, incorrect Kerberos ticket-granting service tickets, or Guest accounts without Guest access enabled

and

SMB Server event ID 1020
File system operation has taken longer than expected.

Client Name: \\192.168.105.97
Client Address: 192.168.105.97:49571
User Name: HHS\12J.Champion
Session ID: 0x2C07B40004A5
Share Name: \\*\Subjects
File Name:
Command: 5
Duration (in milliseconds): 176784
Warning Threshold (in milliseconds): 120000

Guidance:

The underlying file system has taken too long to respond to an operation. This typically indicates a problem with the storage and not SMB.

I have checked the underlying disk/iscsi/network hyper-v cluster for any other errors or issues, but as far as I can tell everything is fine. 

Is it possible that something else is left over from the NOD antivirus installation?  

Looking for suggestions on how to troubleshoot this further.

Thanks