EPM 14.2 RU2 installation failure due to Error 2738: could not access VBScript run time for custom action

I need a solution

Hi,

We are running EPM 14.2 RU1 MP1 on Server 2008 R2 SP1 but when we recently tried to instlla the RU2, its observed that instllation is failed due to Error 2738: could not access VBScript run time for custom action

We tried to re register the VB Script but unsucessful, so need solution to get it done

0

Related:

Does Windows Update SHA2 problem affect SEP 12.1.x?

I need a solution

I’m looking for clarification on exactly WHICH versions of SEP are causing issues with the August 2019 Windows updates which are only SHA2 signed.

The article at https://support.symantec.com/us/en/article.tech255857.html only mentions Symantec Endpoint Protection 14.2 RU1 MP1 as an affected product. Are other SEP versions also affected, or is it JUST this SPECIFIC version? Is this version mentioned only because it is the latest version?

We have several clients still running v12.1.6 RU9 and RU10 on Server 2008 R2 platforms and Windows 7 workstations – are these computers also affected? If so, will any patches be offered for those versions?

Thanks in advance for any insight!
Warren

0

Related:

Re: Policy Managerの対応OSバージョンについて

下記のPolicy Manager 6.8のRelease NoteのP4には

https://support.emc.com/docu84761_ESRS-Policy-Manager-6.8-Release-Notes.pdf?language=en_US

Processor — One or more processors, each 2.1 GHz or better.

Free Memory—Minimum 2 GB RAM, preferred 3 GB RAM. (If the Gateway Client and Policy Manager

are on the same server, the minimum RAM is 3 GB.)

Minimum 4 GB recommend for 64-bit operating systems.

Network Interface Cards (NIC)—One 10/100 Ethernet adapters (NIC cards) are recommended (1 GB

preferred). You may choose to use a third NIC card for data backups.

Free Disk Space — Minimum 2 GB available (preferably on a storage device of 80 GB or larger)

Microsoft.NET Framework —

• Version 2.0 SP1 (minimum)

• Microsoft.NET Framework 3.5 is required if you are using the Customer Environment Check Tool

(CECT) to validate that the Policy Manager server is setup correctly to install the PM software.

• Microsoft.NET Framework 3.5 SP1 in Windows 2012

Note: Microsoft.NET Framework 4.0 is not compatible at this time.

Operating System — US English only supported, as follows:

• RedHat 6.x 64bit

• CentOS 6.x 64bit

• SuSE 11 64bit

• Windows 8 64bit

• Windows 2008 R2

• Windows 2012 R2

Web Browser:

• Microsoft Internet Explorer 10+

• Google Chrome

• Mozilla Firefox

と記載がありましたので、Cent OSも 6.x でOKと判断できるかと思います。

Related:

  • No Related Posts

How to use symantec to scan files in net app

I need a solution

We have a asp.net website that runs on windows 2008 R2 server. We want to scan the files for viruses when the users upload them. If the symatec finds the virus in the file, our website can get information.  Now we use Symantic EndPoint protect 12.1, i try to find the SDK for the Net integeration, but i can’t find it on my computer. I am not sure where the problem is, where it should be, Is there any solutions to use symantec to scan files in net app.

0

Related:

7021446: Performance Benefits Using the Latest Microsoft .NET Framework with Reflection

Microsoft .NET Framework is a required and integral part of the Reflection software. Reflection Desktop 16, Reflection 2014, and Reflection 2011 require a minimum .NET Framework version 4.0, but can benefit from the performance increases in .NET Framework version 4.5 or higher.

If you run Reflection on one of the following platforms,

Windows 7

Windows Server 2008 SP2

Windows Server 2008 R2 SP1

you can experience significant performance improvements if you run the latest version of the Microsoft .NET Framework (version 4.5 or higher).

Gains of up to 25% faster execution are possible based on our testing, but individual results may vary depending on the hardware and software environments in use. Even more significant gains in performance are possible with running Windows 8 Pro and .NET Framework 4.5.1. (Windows 8.1 includes .NET Framework 4.5.1.)

.NET Upgrade Information

In late 2013, the Microsoft Windows Update application (Control Panel) started to show .NET version 4.5.1 as an “Important “ update, so many users may have already installed it. If you have not yet updated your .NET version, you can use the Windows Update service to get the latest release, or go to the Microsoft .NET Framework 4.5.1 download site:

In late 2017, Microsoft released .NET version 4.71 and this can be used as a replacement for earlier versions of .NET to provide better security and faster performance with Reflection Desktop 16. This update is available from the Microsoft download site:

https://www.microsoft.com/en-us/download/details.aspx?id=56116

Note: You must have administrator privileges to install the stand-alone .NET Framework version 4.5 or later and its updates on a Windows system, and a restart of the system may be necessary after applying this upgrade.

Related:

7021446: Performance Benefits Using the Latest Microsoft .NET Framework with Reflection Desktop 16, Reflection 2014, or 2011

Microsoft .NET Framework is a required and integral part of the Reflection software. Reflection Desktop 16, Reflection 2014, and Reflection 2011 require a minimum .NET Framework version 4.0, but can benefit from the performance increases in .NET Framework version 4.5 or higher.

If you run Reflection on one of the following platforms,

Windows 7

Windows Server 2008 SP2

Windows Server 2008 R2 SP1

you can experience significant performance improvements if you run the latest version of the Microsoft .NET Framework (version 4.5 or higher).

Gains of up to 25% faster execution are possible based on our testing, but individual results may vary depending on the hardware and software environments in use. Even more significant gains in performance are possible with running Windows 8 Pro and .NET Framework 4.5.1. (Windows 8.1 includes .NET Framework 4.5.1.)

.NET Upgrade Information

In late 2013, the Microsoft Windows Update application (Control Panel) started to show .NET version 4.5.1 as an “Important “ update, so many users may have already installed it. If you have not yet updated your .NET version, you can use the Windows Update service to get the latest release, or go to the Microsoft .NET Framework 4.5.1 download site:

In late 2017, Microsoft released .NET version 4.71 and this can be used as a replacement for earlier versions of .NET to provide better security and faster performance with Reflection Desktop 16. This update is available from the Microsoft download site:

https://www.microsoft.com/en-us/download/details.aspx?id=56116

Note: You must have administrator privileges to install the stand-alone .NET Framework version 4.5 or later and its updates on a Windows system, and a restart of the system may be necessary after applying this upgrade.

Related:

7021446: Performance Benefits Using the Latest Microsoft .NET Framework with Reflection 2014 or 2011

Microsoft .NET Framework is a required and integral part of Reflection 2014 and Reflection 2011 software. Reflection 2014 and Reflection 2011 require a minimum .NET Framework version 4.0, but can benefit from the performance increases in .NET Framework version 4.5 or higher.

If you run Reflection 2014 or 2011 on one of the following platforms,

Windows 7

Windows Server 2008 SP2

Windows Server 2008 R2 SP1

you can experience significant performance improvements if you run the latest version of the Microsoft .NET Framework (version 4.5 or higher).

Gains of up to 25% faster execution are possible based on our testing, but individual results may vary depending on the hardware and software environments in use. Even more significant gains in performance are possible with running Windows 8 Pro and .NET Framework 4.5.1. (Windows 8.1 includes .NET Framework 4.5.1.)

.NET Upgrade Information

In late 2013, the Microsoft Windows Update application (Control Panel) started to show .NET version 4.5.1 as an “Important “ update, so many users may have already installed it. If you have not yet updated your .NET version, you can use the Windows Update service to get the latest release, or go to the Microsoft .NET Framework 4.5.1 download site:

Note: You must have administrator privileges to install the stand-alone .NET Framework version 4.5 and its updates on a Windows system, and a restart of the system may be necessary after applying this upgrade.

Related:

7022020: Reflection for Secure IT Windows Server 7.1 Service Pack 2 (SP2) Release Notes

Before you apply the service pack, note the following:

  • This document references a Reflection service pack. Service packs are available to licensed Attachmate customers with current maintenance plans for these products. For information about logins and accessing the Download Library, see Technical Note 0200.
  • Reflection for Secure IT Windows Server version 7.1 SP2 is a full product installation and does not require 7.1 to be installed.
  • For a list of features originally included in Reflection for Secure IT Windows Server 7.1, see Technical Note 2415.
  • For information about the Reflection PKI Services Manager 1.1 release, see Technical Note 2486.
  • Reflection for Secure IT version 8.0 is available beginning in November 2012. For a list of new features in 8.0, see Technical Note 2642.

This note is organized into the following sections:

Obtaining Service Packs or Updates

Maintained customers are eligible to download the latest product releases, service packs, and updates from the Attachmate Download Library web site: https://download.attachmate.com/Upgrades/. For more information about logging into and using the Download Library, see Technical Note 0200.

Installing the Service Pack

Reflection for Secure IT Windows Server version 7.1 SP2 is a full product installation and does not require 7.1 to be installed.

If you are upgrading an existing copy of Reflection for Secure IT version 7.1 or 7.1 SP1, note the following:

  • If the server is running when you apply the upgrade, the installer stops the service and any existing client connections will be disconnected.
  • We recommend that you back up your server configuration file before upgrading. This may be useful if you want to revert to an earlier version at some point in the future.
  • After applying the service pack, you need to restart Windows to complete the installation.

New Features and Fixes in Reflection for Secure IT 7.1 SP2

The following new features and resolved issues are included in Reflection for Secure IT Windows Server version 7.1 Service Pack 2.

New Features in 7.1 SP2

  • The debug log file now contains the server’s time zone setting and timestamp at the beginning of the file.
  • Failed authentication attempts are written to the Windows Event Viewer’s application log once maximum password attempts or maximum keyboard-interactive attempts have been reached.

Additional Features in 7.1 SP2

  • The client cipher list is logged to the server debug log.
  • Provide support for the user@host syntax in the User Access Control.

Resolved Issues in 7.1 SP2

  • This service packs addresses vulnerabilities described in Microsoft Security Bulletin MS09-035 and Microsoft Security Advisory 973882: Vulnerabilities in Microsoft Active Template Library (ATL) Could Allow Remote Code Execution.
  • Windows IDs were always sent in uppercase causing public key authentication to fail. This issue has been resolved.
  • Transferring an identical file to the server from a UNIX client now updates the file timestamp.
  • Password authentication now works when using an interactive user who is a member in a three level deep nested group.
  • File transfers now work if the virtual sftp directory contains dashes.
  • File transfers now work if the file is located in a directory ending with the Japanese character “hyo”.
  • Secure Shell connections now allow Japanese characters to be entered.

Supported Platforms in 7.1 SP2

For information about platform support in Reflection for Secure IT, see Technical Note 1944.

New Features and Fixes in Reflection for Secure IT 7.1 SP1

The following new features and resolved issues are included in the Reflection for Secure IT Windows Server version 7.1 Service Pack 1.

New Features in 7.1 SP1

  • Configure Reflection for Secure IT to run in a Microsoft cluster environment.
  • Apply custom SFTP directory settings to scp transfers from OpenSSH hosts.

From the Permissions pane, enable the new setting, “Use SFTP accessible directory settings for SCP1.”

  • Prevent non-interactive users from being able to connect to the server.

Non-interactive users are those who do not have the right to “Allow log on locally” (or “Log on locally”) as configured in the local computer Security Policy. From the Permissions pane, clear the new setting, “Allow non-interactive users to log on.”

Resolved Issues in 7.1 SP1

  • Public key authentication correctly supports double nesting of Active Directory global groups.

Note: Modifications to group membership made using Active Directory may take up to 20 minutes or more to be apparent to Reflection for Secure IT, depending on your Active Directory configuration.

  • Server console starts up correctly when running non-English versions of Windows.
  • When creating a group sub-configuration, you can now clear the “Allow SCP1” setting and save the change.

Supported Platforms in 7.1 SP1

For information about platform support in Reflection for Secure IT, see Technical Note 1944.

Reflection PKI Services Manager 1.0 SP1

Attachmate Reflection PKI Services Manager 1.0 provides X.509 certificate validation services for Reflection for Secure IT 7.1. The PKI Services Manager service pack is available as a separate, optional download.

Note: For information about the Reflection PKI Services Manager 1.1 release, see Technical Note 2486

Installing the Reflection PKI Services Manager Service Pack

Reflection PKI Services Manager version 1.0 SP1 is a full product installation and does not require 1.0 to be installed.

Note the following:

  • If the service is running when you apply the upgrade, the installer stops the service.
  • The service does not start automatically after the installation is complete. To start, either restart Windows, or run the following command from a DOS command window:
winpki start
  • If you are upgrading an existing copy of PKI Services Manager, the upgrade does not change the existing contents of your PKI Services Manager configuration directory (typically C:Documents and SettingsAll UsersApplication DataAttachmateReflectionPKIconfig or C:ProgramDataAttachmateReflectionPKIconfig).

Resolved Issue in PKI Services Manager 1.0 SP1

  • Unrecognized OIDs no longer cause an ASN error.

Related:

Security certificate error (12045) after upgrading to SEP14

I need a solution

Hi,

Recently we have upgraded our SEPM to version 14.0.1 (Windows Server 2008R2 x64). For test purposes we started from upgrading 2 endpoint clients to version 14 .0 RU1 (Windows 7 x64). Since the upgrade, clients are unable to connect to SEPM via HTTPS protocol. Client is constantly getting error: Security certificate error (12045). HTTP connection works fine.

At the moment we have the following settings in the Menagament Server Lists:

All endpoint clients which stayed on version 12.x connect via HTTPS to SEPM without any issues.

I tried to update sylink files but it did not solve the problem.

New case in Symantec Support was created one week ago and it is still not solved by the technican. I am on the phone almost every day and they can not figure it out.

Any ideas would be much appreciated.

Regards,

Marcin

0

Related:

SEP 14 clients virus definition not updating

I need a solution

I have just completed the exercise to migrate sepm to Windows Server 2008 R2 and upgraded from version 12 to 14. After upgrading the sepm and deployed the client package 14.0.3752.1000, most of the clients virus definition not updated since then and some of the clients virus definition shows “Not available”. I have no idea what has gone wrong. Please advise some fixes that I can resolve this problem, thank you.

0

Related: