Kreslavsky IT blog » Symantec

Unable to upgrade the OfficeScan client error when upgrading the client

Gil Kreslavsky — Tue, 20 Oct 2009 15:57:55 +0000

It happened to me after server upgrade to version 10 ,
but it can be relevant to versions 7 and 8.

You can solve it by editing ofcscan.ini file to bypass server checking.

To allow upgrade go to your OfficeScan server.
Open your PCCSRV folder “ by default installed in c:Program FilesTrend MicroOfficeScanPCCSRV”
Backup your ofcscan.ini file
Locate the following line [INI_CLIENT_SETUP_SECTION]
Under LIENT_SETUP_SECTION] find the line “BypassServerChecking=0” ad change to “BypassServerChecking=1”
Save the file and try to run installation again

Your OfficeScan session has timed out. Please log in again

Gil Kreslavsky — Mon, 19 Oct 2009 11:22:00 +0000

You receive the error “Your OfficeScan session has timed out” when you try to login to your Office Scan server via web console.

It usually happens if IUSR_computername has no permissions on TEMP Folder

To fix it navigate to

%Program Files%Trend MicroOfficeScanPCCSRV

Right click on Tempadd the user IUSR_computername from your local computerand grant him full control permission.

Online Virus Scan Sites

Gil Kreslavsky — Wed, 17 Jun 2009 07:05:15 +0000

List of available Online Virus Scanners.

Windows 2008 shares unavailable

Gil Kreslavsky — Mon, 27 Apr 2009 11:43:08 +0000

If you can’t access your shared folders on windows 2008 check the thinks bellow.

The issue can happen if you have certain versions of Symantec Endpoint Protection or Antivirus installed

To resolve the issue update

To resolve this issue, upgrade the Symantec Endpoint Protection software to Symantec Endpoint Protection 11.0 MR3.

you can find more information on the issue Here http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008091611042748 or http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008091611042748)

http://www.symantec.com/business/support/index.jsp

Symantec Norton Uninstall and Removal tools Download

Gil Kreslavsky — Tue, 15 Jul 2008 12:38:50 +0000

Manual Uninstall of Symantec Products

Gil Kreslavsky — Tue, 15 Jul 2008 11:52:08 +0000

List of all manual uninstall resources at Symantec

Norton SystemWorks

How to uninstall Norton SystemWorks manually

Norton AntiVirus

Norton Internet Security / Personal Firewall

Norton Utilities

Norton CleanSweep

WinFax

Symantec Utilities

Removing LiveUpdate after Add/Remove Programs does not work

Symantec Anti Virus 10.2 for Windows Vista

Manually uninstalling Symantec AntiVirus 10.2 client

Symantec Anti Virus 10.1 and Symantec Client Security 3.1

Symantec Anti Virus 10.0 and Symantec Client Security 3.0

Symantec Anti Virus Corporate Edition 9.x

Symantec Anti Virus Corporate Edition 8.x

Symantec Anti Virus Corporate Edition 7.x

How to uninstall Norton AntiVirus Corporate Edition 7.5 and 7.6

Exchange

SnapManager jobs fail

Gil Kreslavsky — Thu, 03 Apr 2008 12:20:00 +0000

After a backup job run you receive error messages.

Backup SG [First Storage Group] Error: SnapManager detected the following Exchange writer error. Please retry SnapManager operation.

VSS_E_WRITERERROR_RETRYABLE: The writer failed due to an error that might not occur if another snapshot copy is created.

Backup SG [First Storage Group]: Failed

Backup failed.

Error Code: 0xC00413CA

SnapManager detected the following Exchange writer error. Please retry SnapManager operation.

VSS_E_WRITERERROR_RETRYABLE: The writer failed due to an error that might not occur if another snapshot copy is created.

After few hours of check I found out that the guilty one is Backup Exec Agent..

Even found article on netapp, Actualy I just removed BackupExec agent, and started to use alternative backup solution , but you can follow the article.

SnapManager for Exchange (SME) backup fails with VSS_E_PROVIDER_VETO

Symptoms

SME backup fails with VSS_E_PROVIDER_VETO

After a reboot of the Exchange Server (either clustered or non clustered), the first SME backup works fine.

The next (and the following) backup(s) fail with VSS_E_PROVIDER_VETO:

VSS Event ID: 8193:
Volume Shadow Copy Service error: Unexpected error calling routine DeviceIoControl(IOCTL_VOLUME_SET_GPT_ATTRIBUTES). hr = 0x800700aa

Navssprv Event ID 4356:
NetApp VSS hardware provider’s AbortSnapshot method is called [SnapshotSetId={c1bfe1c1-a6f7-4636-adad-8d60515123e8}]
VSS has failed the current shadow copy session because the previous errors are not continuable

SnapDrive Event ID 191:
Failed to create a consistent snapshot({c1bfe1c1-a6f7-4636-adad-8d60515123e8}) of the virtual disk(s) [J: I: E: F: G: H: ]

SME:
Error in calling VSS API: Error code = 0×80042306 Error description: VSS_E_PROVIDER_VETO (Error Code: 0×80042306)

Solution

Follow these steps to determine the root cause:

1. Take a manual snapshot using SnapDrive and mount a LUN in that snapshot. If this is possible, then this is not a SnapDrive problem. Go to the next step.

2. Ensure the SnapDrive account in a member of the local administrators group on both the filer and the host.

3. Is a preferred IP Address configured? If not, configure it. In SnapDrive 3.2 and above, this can be done in the SD GUI by right-clicking on “Disks” after expanding “SnapDrive”. Choose properties from the pop-up menu and then go to the “Preferred filer” tab. Enter the filer name and the preferred IP address in the respective columns. The PIP should be a public interface on the filer NOT the private interface used for ISCSI-BLOCK traffic.

4. Make sure that no non-Exchange/SQL data is being stored on the LOGS LUN.

5. Make sure that a stand-alone VSS Hardware Provider from SnapDrive 3.0x has not been installed. This can be checked by running “vssadmin list providers” anywhere on the SnapDrive Server. Only two providers should be listed. If doing an upgrade from SnapDrive 3.0x, then completely uninstall SnapDrive 3.0x and the Hardware Provider first. Then install SnapDrive 3.1x from scratch.

6. Is Veritas Agent used for backing up SnapDrive Server? If so, using Volume Shadowcopy Service (VSS) and Veritas Snapshot Provider (VSP) can cause volumes to become marked read-only. Check the version of the “vsp.sys” driver. If it is less than 1.4, upgrade it. To download the updated driver and to get more info on this problem read the following Veritas Article .

Check for the following file: windowssystem32driversvsp.sys. If the file version is 1.03, either remove the “Veritas Remote Backup Agent ” Or update vsp.sys to version 1.04 (Veritas Hotfix 272771). After installing Veritas Hotfix 272771 (vsp.sys and vspapi.dll), multiple SME backups will work fine.

Related links:
Veritas Backup Exec: http://seer.support.veritas.com/docs/272771.htm
NetBackup: http://seer.support.veritas.com/docs/272814.htm

Last updated: 26 MAR 2007

Related Blogs

Related Blogs on NetApp
Moshable Music

Removing Symantec Antivirus Corporate Edition SCScleanwipe

Gil Kreslavsky — Tue, 17 Oct 2006 16:48:00 +0000

Some times removing Corporate edition is not that easy.

Don’t worry that tool will do the job.

Download the zipped file scscleanwipeto your desktop

Warnings about SCSCleanWipe:

SCSCleanWipe removes ALL Symantec products, not only the AntiVirus program. If you have other Symantec programs installed, make sure you can reinstall them after running SCSCleanWipe.

The SCSCleanWipe User’s Guide says: “…SCSCleanWipe is an unsupported Symantec tool provided as a fallback resource in case a regular uninstallation cannot properly commence. The tool is provided as an “as is” state and Symantec takes no responsibilities with any unforeseen errors resulting from usage of the tool.”

How to download and use SCSCleanWipe

SaveSCSCleanWipe.zip to your desktop
Close the browser
On the desktop, double click SCSCleanWipe.zip
Double click SCS_CleanWipe.bat
Click Extract all
Click Next
Click Next
Click Finish
Close both SCSCleanWipe windows
Find the SCSCleanWipe folder, double click it
Double click SCS_CleanWipe.bat

The SCSCleanWipe manual is in the Docs folder, SCS CleanWipe Users Guide.doc.

If you want manualy remove . Go To Symantec Site