named.conf not available in etc folder – RHEL 5.4

Error scenario:  I try to setup DNS server configuration in RHEL 5.4.
I mount the ISO file of redhat and installed bind-9 series rpm file. 
After the installation when I try to start the name service it fails with 
[root@localhost ~]# service named start

Locating //etc/named.conf failed: [FAILED]

Root cause: We have not installed the caching-nameserver rpm and hence 
the name.conf file not available in /etc folder.The package caching-nameserver 
do not contain any /etc/named.conf file. 
Perhaps,/etc/named.caching-nameserver.conf is an alternative one.

Solution: We need to install the caching name server in the RHEL rpm package 
and run the command 

#rpm -ql caching-nameserver 
Then install the rpm # rpm –ivh caching-nameserver*.rpm
Your problem solves.

The file is corrupt and cannot be opened in Excel 2010.

Error: The file is corrupt and cannot be opened in Excel 2010 when you try to open an excel file from network.


Try the following steps:

1. Open Excel 2010.
2. Click on File > Options.

3. Select Trust Center > Trust center settings.

4. Select Protected view.
5. Uncheck all the options under Protected View > OK.

6. Restart Excel 2010 and try to open Excel documents.




How To Kill Defunct Or Zombie Process?

A “defunct” processes is also known as a “zombie” processes. A Zombie process is referred as dead process which is receding on your system though its completed executing. In one shot we can say its a dead processes which is still in RAM. This process will be in your process table and consuming your memory. Having more defunct process will consume your memory which intern slows your system. We have to kill the defunct process in order to free RAM and make system stable.

How to find a defunct process?

#ps -ef grep | defunct

How can I kill a defunct process?

kill -9 pid (defunct) or worst case reboot the server.



AD replication tool

Today I come across an article in Microsoft where they introduce an AD replication tool which is more helpful for analysing and creating report (Excel) for problem servers in a forest.

Please find the url for more info:

Download link:


Domain replication issues or you get an event error “Event ID: 13568

Domain replication issues or you get an event error “Event ID: 13568 The File Replication Service has detected that the replica set “DOMAIN SYSTEM VOLUME (SYSVOL SHARE)” is in JRNL_WRAP_ERROR”

Root cause: This may occur due to corrupt files available in the Sysvol folder which creates issues in replication; even if you try to restart the ntfrs service this problem occur.


Nonauthoritative restores are the most common way to reinitialize individual members of FRS replica sets that are having difficulty

To perform a nonauthoritative restore, stop the FRS service, configure the


registry key, and then restart the FRS service. To do so:

  1. Click Start, and then click Run.
  2. In the Open box, type cmd and then press ENTER.
  3. In the Command box, type net stop ntfrs.
  4. Click Start, and then click Run.
  5. In the Open box, type regedit and then press ENTER.
  6. Locate the following subkey in the registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup

  1. In the right pane, double-click BurFlags.
  2. In the Edit DWORD Value dialog box, type D2 and then click OK.
  3. Quit Registry Editor, and then switch to the Command box.
  4. In the Command box, type net start ntfrs.
  5. Quit the Command box.

When the FRS service restarts, the following actions occur:

  • The value for BurFlags registry key returns to 0.
  • Files in the reinitialized FRS folders are moved to a Pre-existing folder.
  • An event 13565 is logged to signal that a nonauthoritative restore is started.
  • The FRS database is rebuilt.
  • The member performs an initial join of the replica set from an upstream partner or from the computer that is specified in the Replica Set Parent registry key if a parent has been specified for SYSVOL replica sets.
  • The reinitialized computer runs a full replication of the affected replica sets when the relevant replication schedule begins.
  • When the process is complete, an event 13516 is logged to signal that FRS is operational. If the event is not logged, there is a problem with the FRS configuration.

More info:-

Snapshot removing command in VMware

After the backup session in VMware servers, backup application unable to remove the snapshot.

To remove the snapshot the following are the methodology can be used.

1. Vsphere Powershell CLI (Latest version):

PS C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI> Get-VM  VMNAME* | get-snapshot | Remove-Snapshot -Confirm:$false

PS C:\Program Files (x86)\VMware\Infrastructure\vSphere PowerCLI>

2. From ESX (4.X & 5.X):

For Esx4.X: #vmware-cmd path_to_vmxfile removesnapshots

For ESX 5.X: #vim-cmd vmsvc/snapshot.removeall [VMID]

 3.  Through Shell script: