 | Charles on Robocopy ERROR 5 (0x00000005)… |
 | Taya on Enabling Anonymous LDAP A… |
 | jmmelkon on Robocopy ERROR 5 (0x00000005)… |
 | krtonozka on Robocopy ERROR 5 (0x00000005)… |
 | lihu on How to find the NetBIOS Name o… |
Ignited RSS
How to verify if the WMI is working fine on the Server?
ANS: Open Command prompt in Administrator mode and run the below command:
winmgmt /verifyrepository
If the WMI is working fine, then you get message as WMI is consistent, or else you get the error code.
Below is the link for the Error code reference for WMI
Depended on the scope of error you need to troubleshoot further.
Alert: This source server failed to generate the changes
Description: This directory service failed to retrieve the changes requested for the following directory partition. As a result, it was unable to send change requests to the directory service at the following network address.
Event ID: 1479
Active Directory Domain Services could not update the following object in the local Active Directory Domain Services database with changes received from the following source directory service. Active Directory Domain Services does not have enough database version store to apply the changes.
User Action
Restart this directory service. If this does not solve the problem, increase the size of the database version store. If you are populating the objects with a large number of values, or the size of the values is especially large, decrease the size of future changes.
Additional Data
Error value:
8573 The database is out of version store.
Resolution:
{MS has provided the resolution in this Link}
Note: Take Backup of Registry before changing
Registry Location:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters
You need to add the Registry value “EDB max ver pages” with 32 Bit DWord Decimal value as you need with reference below:
9600 = 152 MB
12800 = 202 MB
16000 = 252 MB
19200 = 302 MB
Reboot the Server once the changes have been done.
Check the Event viewer after restart; you need to get event 1394 in ADS Logs
The WordPress.com stats helper monkeys prepared a 2013 annual report for this blog.
Here’s an excerpt:
The concert hall at the Sydney Opera House holds 2,700 people. This blog was viewed about 21,000 times in 2013. If it were a concert at Sydney Opera House, it would take about 8 sold-out performances for that many people to see it.
Robust File and Folder Copy.
By default Robocopy will only copy a file if the source and destination have different time stamps or different file sizes.
Syntax
ROBOCOPY Source_folder Destination_folder [files_to_copy] [options]
Key
file(s)_to_copy : A list of files or a wildcard.
(defaults to copying *.*)
Source options
/S : Copy Subfolders.
/E : Copy Subfolders, including Empty Subfolders.
/COPY:copyflag[s] : What to COPY (default is /COPY:DAT)
(copyflags : D=Data, A=Attributes, T=Timestamps
S=Security=NTFS ACLs, O=Owner info, U=aUditing info).
/SEC : Copy files with SECurity (equivalent to /COPY:DATS).
/DCOPY:T : Copy Directory Timestamps. ##
/COPYALL : Copy ALL file info (equivalent to /COPY:DATSOU).
/NOCOPY : Copy NO file info (useful with /PURGE).
/A : Copy only files with the Archive attribute set.
/M : like /A, but remove Archive attribute from source files.
/LEV:n : Only copy the top n LEVels of the source tree.
/MAXAGE:n : MAXimum file AGE – exclude files older than n days/date.
/MINAGE:n : MINimum file AGE – exclude files newer than n days/date.
(If n < 1900 then n = no of days, else n = YYYYMMDD date).
/FFT : Assume FAT File Times (2-second date/time granularity).
/256 : Turn off very long path (> 256 characters) support.
Copy options
/L : List only – don’t copy, timestamp or delete any files.
/MOV : MOVe files (delete from source after copying).
/MOVE : Move files and dirs (delete from source after copying).
/Z : Copy files in restartable mode (survive network glitch).
/B : Copy files in Backup mode.
/ZB : Use restartable mode; if access denied use Backup mode.
/IPG:n : Inter-Packet Gap (ms), to free bandwidth on slow lines.
/R:n : Number of Retries on failed copies – default is 1 million.
/W:n : Wait time between retries – default is 30 seconds.
/REG : Save /R:n and /W:n in the Registry as default settings.
/TBD : Wait for sharenames To Be Defined (retry error 67).
Destination options
/A+:[RASHCNET] : Set file Attribute(s) on destination files + add.
/A-:[RASHCNET] : UnSet file Attribute(s) on destination files – remove.
/FAT: Create destination files using 8.3 FAT file names only.
/CREATE: CREATE directory tree structure + zero-length files only.
/DST: Compensate for one-hour DST time differences ##
/PURGE: Delete dest files/folders that no longer exist in source.
/MIR: MIRror a directory tree – equivalent to /PURGE plus all subfolders (/E)
Logging options
/L: List only – don’t copy, timestamp or delete any files.
/NP: No Progress – don’t display % copied.
/LOG:file : Output status to LOG file (overwrite existing log).
/UNILOG:file : Output status to Unicode Log file (overwrite) ##
/LOG+:file : Output status to LOG file (append to existing log).
/UNILOG+:file : Output status to Unicode Log file (append) ##
/TS : Include Source file Time Stamps in the output.
/FP : Include Full Pathname of files in the output.
/NS : No Size – don’t log file sizes.
/NC : No Class – don’t log file classes.
/NFL : No File List – don’t log file names.
/NDL : No Directory List – don’t log directory names.
/TEE : Output to console window, as well as the log file.
/NJH : No Job Header.
/NJS : No Job Summary.
Repeated Copy Options
/MON:n : MONitor source; run again when more than n changes seen.
/MOT:m : MOnitor source; run again in m minutes Time, if changed.
/RH:hhmm-hhmm : Run Hours – times when new copies may be started.
/PF : Check run hours on a Per File (not per pass) basis.
Job Options
/JOB:jobname : Take parameters from the named JOB file.
/SAVE:jobname : SAVE parameters to the named job file
/QUIT : QUIT after processing command line (to view parameters).
/NOSD : NO Source Directory is specified.
/NODD : NO Destination Directory is specified.
/IF : Include the following Files.
Advanced options you’ll probably never use
/EFSRAW : Copy any encrypted files using EFS RAW mode. ##
/MT[:n] : Multithreaded copying, n = no. of threads to use (1-128) ###
default = 8 threads, not compatible with /IPG and /EFSRAW
The use of /LOG is recommended for better performance.
/SECFIX : FIX file SECurity on all files, even skipped files.
/TIMFIX : FIX file TIMes on all files, even skipped files.
/XO : eXclude Older – if destination file exists and is the same date or newer than the source – don’t bother to overwrite it.
/XC | /XN : eXclude Changed | Newer files
/XL : eXclude “Lonely” files and dirs (present in source but not destination)
This will prevent any new files being added to the destination.
/XX : eXclude “eXtra” files and dirs (present in destination but not source)
This will prevent any deletions from the destination. (this is the default)
/XF file [file]… : eXclude Files matching given names/paths/wildcards.
/XD dirs [dirs]… : eXclude Directories matching given names/paths.
XF and XD can be used in combination e.g.
ROBOCOPY c:\source d:\dest /XF *.doc *.xls /XD c:\unwanted /S
/IA:[RASHCNETO] : Include files with any of the given Attributes
/XA:[RASHCNETO] : eXclude files with any of the given Attributes
/IS : Include Same, overwrite files even if they are already the same.
/IT : Include Tweaked files.
/XJ : eXclude Junction points. (normally included by default).
/MAX:n : MAXimum file size – exclude files bigger than n bytes.
/MIN:n : MINimum file size – exclude files smaller than n bytes.
/MAXLAD:n : MAXimum Last Access Date – exclude files unused since n.
/MINLAD:n : MINimum Last Access Date – exclude files used since n.
(If n < 1900 then n = n days, else n = YYYYMMDD date).
/BYTES : Print sizes as bytes.
/X : Report all eXtra files, not just those selected & copied.
/V : Produce Verbose output log, showing skipped files.
/ETA : Show Estimated Time of Arrival of copied files.
## = New Option in Vista (XP027) all other options are valid for the XP version of Robocopy (XP010)
### = New Option in Windows 7 and Windows 2008 R2
Robocopy EXIT CODES
File Attributes [RASHCNETO]
R – Read only
A – Archive
S – System
H – Hidden
C – Compressed
N – Not content indexed
E – Encrypted
T – Temporary
O – Offline
If either the source or desination are a “quoted long foldername” do not include a trailing backslash as this will be treated as an escape character, i.e. “C:\some path\” will fail but “C:\some path\\” or “C:\some path\.” or “C:\some path” will work.
By copying only the files that have changed, robocopy can be used to backup very large volumes.
ROBOCOPY will accept UNC pathnames including UNC pathnames over 256 characters long.
/REG Writes to the registry at HKCU\Software\Microsoft\ResKit\Robocopy
/XX (exclude extra) If used in conjunction with /Purge or /Mir, this switch will take precedence and prevent any files being deleted from the destination.
To limit the network bandwidth used by robocopy, specify the Inter-Packet Gap parameter /IPG:n
This will send packets of 64 KB each followed by a delay of n Milliseconds.
Open Files
Robocopy will fail to copy files that are locked by other users or applications, so limiting the number of retries with /R:0 will speed up copying by skipping any in-use files. The Windows Volume Shadow Copy service is the only Windows subsystem that can copy open files. Robocopy does not use the Volume Shadow Copy service, but it can backup a volume shadow that has already been created with VSHADOW or DISKSHADOW.
Permissions
All versions of Robocopy will copy security information (ACLs) for directories, version XP010 will not copy file security changes unless the file itself has also changed, this greatly improves performance.
/B (backup mode) will allow Robocopy to override file and folder permission settings (ACLs).
ERROR 5 (0x00000005) Changing File Attributes … Access is denied
This error usually means that File/Folder permissions or Share permissions on either the source or the destination are preventing the copy, either change the permissions or run the command in backup mode with /B.
To run ROBOCOPY under a non-administrator account will require backup files privilege, to copy security information auditing privilege is also required, plus of course you need at least read access to the files and folders.
Availability
Robocopy is a standard command in Windows 7 and above. The Windows Server 2003 Resource Kit Tools include Robocopy XP010, which can be run on NT 4/ Windows 2000. Robocopy does not run on Windows 95, or NT 3.5. (RoboCopy is a Unicode application).
Robocopy ‘Jobs’ and the ‘MOnitor source’ option provide an alternative to setting up a Scheduled Task to run a batchfile with a RoboCopy command.
Examples:
Copy files from one server to another including subfolders (/S)
If this command is run repeatedly it will skip any files already in the destination, however it is not a true mirror as any files deleted from the source will remain in the destination.
ROBOCOPY \\Server1\reports \\Server2\backup *.doc /S
List files over 32 MBytes in size:
ROBOCOPY C:\work /MAX:33554432 /L
Move files over 14 days old: (note the MOVE option will fail if any files are open and locked.)
ROBOCOPY C:\work C:\destination /move /minage:14
Backup a Server:
The script below copies data from FileServ1 to FileServ2, the destination holds a full mirror along with file security info. When run regularly to synchronize the source and destination, robocopy will only copy those files that have changed (change in time stamp or size.)
@ECHO OFF
SETLOCAL
SET _source=\\FileServ1\e$\users
SET _dest=\\FileServ2\e$\BackupUsers
SET _what=/COPYALL /B /SEC /MIR
:: /COPYALL :: COPY ALL file info
:: /B :: copy files in Backup mode.
:: /SEC :: copy files with SECurity
:: /MIR :: MIRror a directory tree
SET _options=/R:0 /W:0 /LOG:MyLogfile.txt /NFL /NDL
:: /R:n :: number of Retries
:: /W:n :: Wait time between retries
:: /LOG :: Output log file
:: /NFL :: No file logging
:: /NDL :: No dir logging
ROBOCOPY %_source% %_dest% %_what% %_options%
Run two robocopy jobs at the same time with START /Min
Start /Min “Job one” Robocopy \\FileServA\C$\Database1 \\FileServeBackupA\c$\Backups
Start /Min “Job two” Robocopy \\FileServB\C$\Database2 \\FileServeBackupB\c$\Backups
Related Posts:
This Alert occurs in 2008 R2 Servers
——————————————————————————
Alert: Active Directory cannot update object due to insufficient memory
Last modified by: System
Last modified time: 7/18/2013 1:02:10 PM
Alert description: Active Directory Domain Services could not update the following object in the local Active Directory Domain Services database with changes received from the following source directory service. Active Directory Domain Services does not have enough database version store to apply the changes.
User Action
Restart this directory service. If this does not solve the problem, increase the size of the database version store. If you are populating the objects with a large number of values, or the size of the values is especially large, decrease the size of future changes.
——————————————————————————-
Additional Data
Reboot will clear the version table but it does nothing to identify or resolve the core issue.
The version store has reached its maximum size because of unresponsive transaction. Updates to database are rejected until the long-running transaction is omitted or rolled back. TechNet suggested looking for event IDs-1022, 1069,623 and none of these event ids could be found in event viewer.
Resolution:
Below is the solution but it is your own risk to change registry setting.
Backup the Registry before Proceeding
“Please reboot the server”
Check in the Event Viewer for Event ID 1394 “All Problems preventing updates to the Active Directory Domain Services database have been cleared. New Updates to the Active Directory Domain Services database are succeeding. The Net Logon service has restarted”
You can find this event in “Directory Services” Log of the Domain Controller.
Issue:
This kind of issue is basically related to Task Scheduler, Normally you observe that the Tasks are not running as scheduled, when you try to check the properties of task, you get this error.
When you click “Ok”, you get the Properties of the task, but nothing works even though you make the changes.
Note: Backup all the information related to Logon Credentials used to run the specified tasks.
Resolution:
You need to clear the folder “S-1-5-18”
You can find the folder in the below location:
“C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA”
Once you have deleted the folder, you can go back to Tasks and open the task properties, this time you won’t get the error.
Make sure to re-enter the logon credentials used to run the tasks.
Summary: Group Policy application seems straightforward enough: Group Policy Objects (GPOs) are linked to organizational units (OUs); users and computers are in OUs. All the GPOs from a user’s OU hierarchy filter down to the user.
Things get more complicated, though, when you remember that GPOs can be linked to a domain and to sites—meaning you’ll have to open a whole new console to see what’s going on. You also have to consider local security policies, which exist solely on the client computer and are applied before any domain-based policies arrive. Throw in options such as Block Policy Inheritance, No Override, and loopback processing, and it’s no wonder why there’s such a robust market for third-party GPO tools. However, with some patience and a methodology, you can do quite a bit of quality troubleshooting on your own.
Start from the Scratch
Too many administrators try to start at the top, working their way down the hierarchy of GPOs and figuring out which ones apply. That method is time-consuming, error-prone, and just plain boring. It’s a lot easier to start at the bottom—the client—and work your way up the tree. Windows XP’s Gpresult tool, for example, is a great troubleshooting tool. Run from the command line, it will tell you which groups the current user is a member of (which can affect GPO application), and give you a list of every GPO that is currently affecting the user. You’ll also see the last time that GPOs were applied to the computer. What Gpresult is displaying is called resultant set of policy (RSOP). It sorts through all the blocked inheritance, no overrides, and conflicting policies to sort out exactly which policies are being applied.
By default, Gpresult doesn’t show you which individual policies are applied or what they are set to; because GPOs successively overwrite one another as they are applied, you can still be left with a troubleshooting task to figure out which of the GPOs listed is responsible for the settings you’re seeing. Fortunately, Gpresult has a “superverbose” mode, enabled by running
Gpresult /z
This mode not only displays which GPOs have been applied, but lists every single policy that’s enabled in each GPO, allowing you to see which GPO modified which setting, and which GPO finally won out in the end. Figure 36.1 shows a portion of Gpresult’s superverbose output. In this example, the GPO being applied is Local Group Policy, and you can see exactly which registry keys each setting is modifying.
Superverbose mode also breaks down the user and computer policies, allowing you to see every setting that is affecting the current users or their machines.
The FSMO role owners are stored in Active Directory in different locations depending on the role. The DN of the server holding the role is actually stored as the FSMO Role Owner attribute of various objects. For the Ignitedsoul.com domain, here are the containers that hold that attribute in the following order: PDC Role Owner, Infrastructure Master, RID Master, Schema Master, and Domain Naming Master:
LDAP://dc=Ignitedsoul,dc=com
LDAP://cn=Infrastructure,dc=Ignitedsoul,dc=com
LDAP://cn=RID Manager$,cn=System,dc=Ignitedsoul,dc=com
LDAP://cn=Schema,cn=Configuration,dc=Ignitedsoul,dc=com
LDAP://cn=Partitions,cn=Configuration,dc=Ignitedsoul,dc=com
The information in the attribute is stored as a DN, representing the NTDS Settings object of the domain controller that is the role owner. So, example contents for this attribute are:
CN=NTDS Settings, CN=MYSERVER1, CN=Servers, CN=My Site, CN=Sites,
CN=Configuration, DC=Ignitedsoul, DC=com
Issue:
– The Remote connection gets established but gets disconnected moments before you get the Desktop.
Symptoms:
– You are able to Ping the Server
– The Server seems to be fine when checked in Console.
– All the RDP Services seems to be fine.
– When trying to take Remote connection, the connection gets established, but closes automatically with an error.
– It asks to check the Network connections or the Remote desktop Services.
Resolution:
– The Main Culprit here is : rdpcorekmts.dll file in C:\Windows\System32 location
– All you need to do it replace this .dll file with same file in any working server.
– You need to rename the file to : rdpcorekmts.old
– You cannot rename the file directly as the Administrator too has only read permission on this file.
– First you need to take ownership of this file.
– Then you need to edit the security permissions and give full control for the Administrator or your account.
– Only then you can rename the file.
– Now copy the rdpcorekmts.dll file from any working server and paste in the System32 folder of the server with issue.
– This replacement resolves the issue, and you can take RDP of the Server normally.
Ravindra Kulkarni
IgNiTeD SoUL 