Upgrade Windows Client Error

[sdnian 6]

Hello,

 

I'd like to upgrade a computer via 'Upgrade Windows Client' function, but I got failed. The error message is 'Upgrade processing error. error code: (7,3)'. What does the error code mean? How to fix it? Thank you.

 

[Marcos 5,071]

What product and version is installed on the client you're attempting to upgrade?

[sdnian 6]

What product and version is installed on the client you're attempting to upgrade?

 

 

ESET File Security 4.5.12011 upgrade to 4.5.12015

[karlisi 26]

I'd like to upgrade a computer via 'Upgrade Windows Client' function, but I got failed. The error message is 'Upgrade processing error. error code: (7,3)'.

 

ESET File Security 4.5.12011 upgrade to 4.5.12015

 

The same for me. Ended with manual upgrade. Previous version upgrades using ERAS were successfull.

Edited November 21, 2013 by karlisi

[Peter Randziak 1,130]

Hello,

 

which version of the ERA do you use?

Does the issue persist with the most current one ERA 5.1.34 ?

[sdnian 6]

Hello,

 

which version of the ERA do you use?

Does the issue persist with the most current one ERA 5.1.34 ?

 

Yes. The ERA is 5.1.34.

[Marcos 5,071]

We are going to reproduce the issue in our environment. We'll keep you updated.

[cpetry 4]

I'm also getting this error.

 

RAS Ver: 5.1.34.0

Server has ver 4.5.12011.0

Tried updating client to ver 4.5.12015.0

 

Error:

Warning Upgrade processing error, error code: (7,3)

 

I always get this error.  I can't upgrade any file server client.

 

I can upgrade my workstations to the latest version!

[paul 0]

I am seeing the exact same problem with two 4.5.12011.3 file security clients and a 4.5.10012.7 mail security client. I am trying to upgrade file security to 4.5.12015.1 and mail security to 4.5.10019.2

Edited November 29, 2013 by paul

[KiwiJJ 0]

_{I also have the same issue when trying to upgrade any of my servers. Works fine it you install manually.}

 

_{Trying to upgrade from ESET File Security for Windows Servers version 4.5.12011 to version 4.5.12015}

 

_{ERA version 5.1.34.0}

[kesteves 0]

I also have the same issue.

 

Trying to upgrade from ESET File Security for Windows Server version 4.5.12005 to version 4.5.12015.1

 

ERA version 5.1.34.0

[urist 0]

I'm seeing the same error when upgrading from 4.5.12011 to 4.5.12015 under control of ERA 5.1.34.0 on all my Windows Server 2003, 2008 and 2008R2 VMs. Running the upgrade by hand has been successful on 2008 and 2008R2, but on my sole remaining 2003 server it broke things and forced me to restart in safe mode and use the ESET Uninstaller.

 

Upgrading my workstations from EES 4.0.2126 to 5.0.2214 and from 5.0.2214 to 5.0.2225 has generally been working normally. I've seen one (7,3), one (7,-112), two broken clients that needed safe mode & the ESET Uninstaller and two clients that ERAS mistakenly thought were new after the upgrade, but the failure rate is not unusual and I doubt it's related to this problem.

 

I haven't filed a support request on this since it looks like ESET is already aware of the problem, but if it'd be useful, I should be able to do so.

[aaron.johnstone 0]

Any update on this? I'm getting the same error.

ERA version 5.1.34.

Trying to upgrade an ESET File Security client from 4.3.12017.0 to 4.5.12015.1

[mmichieletti 0]

 

Hi,

any update on this? I'm getting the same error.

ERA version 5.1.38.

Trying to upgrade an ESET File Security client from 4.5.12011.0 to 4.5.12015.1

[Marcos 5,071]

Unfortunately, it is not possible to use the upgrade client feature for v4.5 due to changes in the signature. However, you can push a new install package on clients to upgrade them to a newer version.

[karlisi 26]

I don't understand this. It's the same major version 4.5, only minor version upgrade and You say, not possible. There was major version upgrade from 4.0 to 5.0 for workstations product and it went without problems.As for push install, my servers are on remote sites, there is no VPN or EoIP connections, so remote installation not possible (can't establish IPC connection).

[Marcos 5,071]

All previous versions were signed using an old certificate, only the latest version 4.5.12015 was signed using the new one which creates a problem with the upgrade feature in ERA. The problem doesn't occur with manual or push installation.

[Megachip 5]

Same for

4.2.67 -> 5.0.2237

4.2.71 -> 5.0.2237

ERAS 5.2.26

These Version updates works on other Systems. Is there any Matrix which updates are possible?