Our Sponsors

How to Verify Your Policy Settings

With Windows XP, users no longer need to run a command line tool to check policies on their computer. Now any user can obtain a graphical report directly from the Help and Support Center.

To check policies in effect on your computer

  1. Click Start, click Help and Support Center.
  2. Under Pick a Task, select Use Tools to view your computer information and diagnose problems. 
  3. Click Advanced System Information, then click View Group Policy settings applied. 

When system information is collected, results appear on the screen. This report can be printed, saved as an html file, and sent to a support administrator. In this example, the first few items in the report are shown in the figure below.

You can also use “gpresult” in CLI to verify the GPO applied settings.

Event 4014 – Equallogic VSS Error

Event Type Error
Event Source EqualLogic
Event Category VSS
Event ID 4014
Description iSCSI login error 0xEFFF000A to target 0-8a0906-96854b302-b41000096f14a49a, incorrect CHAP credentials.

1.Verify the CHAP authentication username and password are correct on both Dell iSCSI SAN PS series and Windows iSCSI initiator.

2. Uncheck Authenticate using CHAP user name on Dell Dell iSCSI SAN PS series and only select Limit access by IP Address and specify the range of IP address to which it can authenticate.

CA BrightStor Backup Server Error 12507

The volume shadow service provider vetoed an operation. The provider logged the error in the event log.

Error 12507

The volume shadow service provider is unable to find an object that has been selected. This could be a volume, a Writer or a Component.

Module:

VSS Error Messages

Reason:

The selected volume, Writer, or Component is not available to the Volume Shadow Service Provider.

Action:

Check the Activity Log and the Windows Event Log for additional information.

Check the Windows server, at the exact backup time, the Windows system logged “Event ID 10, iSCSIPrt,  Login request failed. The Login response packet is given in the dump data.”  The Windows server iSCSI volume tempararily lost the connection to iSCSI target, so CA Brightstor ”Agent for Open File” couldn’t take the snapshot for this volume, therefore CA logged Error 12507 within backup log. 

Check Volume Shadow Copy Error – provider veto for troubleshooting VSS error.

Volume Shadow Copy Error – provider veto

Possible solutions to fix the problem.

1. VSS Providers
Check to see if there are any non-standard providers that are causing the problem when performing the VSS snapshot. To do this, go to the command-line and execute the following command “vssadmin list providers”.

If there are any non-standard providers listed, consider uninstalling them. Note that the Microsoft default providers are generally very reliable, so uninstalling 3rd party providers may solve the problem.

If the “vssadmin list providers” command hangs, it is likely that a newly installed VSS provider is malfunctioning. We have seen this with certain imaging products. In this case, uninstall these products to resolve the issue.

2. Multiple Backups
Ensure that the backup is not running at the same time as another backup as the custom provider may only allow one snap-shot at a time.

3.Corrupted data on the drive to be backed up.
Run CHKDSK on each drive with the /f switch to fix any errors on the disk.

4. VSS believes the system is in setup process
Check the status of the system by following these steps:

a. Go to the Registry Editor and locate HKEY_LOCAL_MACHINE\SYSTEM\Setup
b. Ensure that the following registry values are set to 0:
SystemSetupInProgress
UpgradeInProgress

5.VSS dlls are corrupted
Re-install the VSS dlls by following these steps:

a. Using command prompt, CD to the WINDOWS\system32 directory
b. Stop the Volume Shadow Copy service by executing the command “net stop vss”
c. Register the following DLLs and services by executing these commands:

regsvr32 ole32.dll
regsvr32 vss_ps.dll
Vssvc /Register
regsvr32 /i swprv.dll
regsvr32 /i eventcls.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll
regsvr32 msxml.dll
regsvr32 msxml3.dll
regsvr32 msxml4.dll


6.COM+ needs to be re-installed
Re-install COM+ by following these steps:
a. Backup and then delete HKLM\Software\Microsoft\COM3
b. Boot to Recovery console and rename clbcatq.dll to ~clbcatq.dll. Be sure
to use the tilde.
c. Boot to normal mode and in Control Panel, open the Add or Remove
Programs tool, and then open the Add/Remove Windows Components tool. Do not
make any changes, just click “Next”. This reinstalls COM+.

Using WMIC install and uninstall software remotely

Using WMIC install and uninstall software remotely

1. Login CMD with domain admin account.

 Runas /user:DomainAdminAccount@DOMAIN cmd

input password when it prompted.

2. Open a WMIC shell with appropriate permissions by running “WMIC” command.

3. Install MSI software remotely

 > /node:COMPUTERNAME product call install true,”" , “c:\Active Directory Janitor 2.0.msi”

4.  Query installed software first and then uninstall selected software

>/node:COMPUTERNAME product get name,version,vendor

>/node:COMPUTERNAME product where name=”Active Directory Janitor 2.0″ call uninstall

5. Install and uninstall software remotel on multiple computers at one time

>/node:@”c:\computers.txt” product where name=”Active Directory Janitor 2.0.msi” call uninstall

> /node:@”c:\computers.txt” product call install true,”" , “c:\Active Directory Janitor 2.0.msi”