I am trying to remove java 6 32 bit and install java 7 64 bit, but after initially having the uninstaller open and execute successfully, asking me to plan a full removal after a reboot, the uninstaller did not come back, and neither does executing it again work.
I’ve tried using revouninstaller to remove the old java, which seems to be successful, but java 7’s installer still won’t execute.
When I execute the offline installer, it asks for administrator privileges, loads up the MSI, and then vanishes. After consulting the event viewer I found these entries from MsiInstaller:
Product: Java(TM) 7 Update 2 (64-bit) — Installation operation failed.
and
Windows Installer installed the product. Product Name: Java(TM) 7 Update 2 (64-bit). Product Version: 7.0.20. Product Language: 1033. Manufacturer: Oracle. Installation success or error status: 1602.
All I know is that error 1602 is supposed to mean user cancelled the installation, which leads me to believe either UAC isn’t working correctly (seems to work fine though), or there is some registry entry blocking the MSI installer (though I’ve checked manually).
This article features error number Code 1602, commonly known as Backup Exec 2012 Error Code 1602 described as Error 1602: Backup Exec has encountered a problem and needs to close. We are sorry for the inconvenience.
About Runtime Code 1602
Runtime Code 1602 happens when Backup Exec fails or crashes whilst it’s running, hence its name. It doesn’t necessarily mean that the code was corrupt in some way, but just that it did not work during its run-time. This kind of error will appear as an annoying notification on your screen unless handled and corrected. Here are symptoms, causes and ways to troubleshoot the problem.
Definitions (Beta)
Here we list some definitions for the words contained in your error, in an attempt to help you understand your problem. This is a work in progress, so sometimes we might define the word incorrectly, so feel free to skip this section!
- Backup — The act of saving one’s files, data, applications, etc
- Error code — An error code is a value returned to provide context on why an error occurred
- Exec — This tag refers to the starting of another, subsidiary program
Symptoms of Code 1602 — Backup Exec 2012 Error Code 1602
Runtime errors happen without warning. The error message can come up the screen anytime Backup Exec is run. In fact, the error message or some other dialogue box can come up again and again if not addressed early on.
There may be instances of files deletion or new files appearing. Though this symptom is largely due to virus infection, it can be attributed as a symptom for runtime error, as virus infection is one of the causes for runtime error. User may also experience a sudden drop in internet connection speed, yet again, this is not always the case.
(For illustrative purposes only)
Causes of Backup Exec 2012 Error Code 1602 — Code 1602
During software design, programmers code anticipating the occurrence of errors. However, there are no perfect designs, as errors can be expected even with the best program design. Glitches can happen during runtime if a certain error is not experienced and addressed during design and testing.
Runtime errors are generally caused by incompatible programs running at the same time. It may also occur because of memory problem, a bad graphics driver or virus infection. Whatever the case may be, the problem must be resolved immediately to avoid further problems. Here are ways to remedy the error.
Repair Methods
Runtime errors may be annoying and persistent, but it is not totally hopeless, repairs are available. Here are ways to do it.
If a repair method works for you, please click the upvote button to the left of the answer, this will let other users know which repair method is currently working the best.
Please note: Neither ErrorVault.com nor it’s writers claim responsibility for the results of the actions taken from employing any of the repair methods listed on this page — you complete these steps at your own risk.
Method 1 — Close Conflicting Programs
When you get a runtime error, keep in mind that it is happening due to programs that are conflicting with each other. The first thing you can do to resolve the problem is to stop these conflicting programs.
- Open Task Manager by clicking Ctrl-Alt-Del at the same time. This will let you see the list of programs currently running.
- Go to the Processes tab and stop the programs one by one by highlighting each program and clicking the End Process buttom.
- You will need to observe if the error message will reoccur each time you stop a process.
- Once you get to identify which program is causing the error, you may go ahead with the next troubleshooting step, reinstalling the application.
Method 2 — Update / Reinstall Conflicting Programs
Using Control Panel
- For Windows 7, click the Start Button, then click Control panel, then Uninstall a program
- For Windows 8, click the Start Button, then scroll down and click More Settings, then click Control panel > Uninstall a program.
- For Windows 10, just type Control Panel on the search box and click the result, then click Uninstall a program
- Once inside Programs and Features, click the problem program and click Update or Uninstall.
- If you chose to update, then you will just need to follow the prompt to complete the process, however if you chose to Uninstall, you will follow the prompt to uninstall and then re-download or use the application’s installation disk to reinstall the program.
Using Other Methods
- For Windows 7, you may find the list of all installed programs when you click Start and scroll your mouse over the list that appear on the tab. You may see on that list utility for uninstalling the program. You may go ahead and uninstall using utilities available in this tab.
- For Windows 10, you may click Start, then Settings, then choose Apps.
- Scroll down to see the list of Apps and features installed in your computer.
- Click the Program which is causing the runtime error, then you may choose to uninstall or click Advanced options to reset the application.
Method 3 — Update your Virus protection program or download and install the latest Windows Update
Virus infection causing runtime error on your computer must immediately be prevented, quarantined or deleted. Make sure you update your virus program and run a thorough scan of the computer or, run Windows update so you can get the latest virus definition and fix.
Method 4 — Re-install Runtime Libraries
You might be getting the error because of an update, like the MS Visual C++ package which might not be installed properly or completely. What you can do then is to uninstall the current package and install a fresh copy.
- Uninstall the package by going to Programs and Features, find and highlight the Microsoft Visual C++ Redistributable Package.
- Click Uninstall on top of the list, and when it is done, reboot your computer.
- Download the latest redistributable package from Microsoft then install it.
Method 5 — Run Disk Cleanup
You might also be experiencing runtime error because of a very low free space on your computer.
- You should consider backing up your files and freeing up space on your hard drive
- You can also clear your cache and reboot your computer
- You can also run Disk Cleanup, open your explorer window and right click your main directory (this is usually C: )
- Click Properties and then click Disk Cleanup
Method 6 — Reinstall Your Graphics Driver
If the error is related to a bad graphics driver, then you may do the following:
- Open your Device Manager, locate the graphics driver
- Right click the video card driver then click uninstall, then restart your computer
Method 7 — IE related Runtime Error
If the error you are getting is related to the Internet Explorer, you may do the following:
- Reset your browser.
- For Windows 7, you may click Start, go to Control Panel, then click Internet Options on the left side. Then you can click Advanced tab then click the Reset button.
- For Windows 8 and 10, you may click search and type Internet Options, then go to Advanced tab and click Reset.
- Disable script debugging and error notifications.
- On the same Internet Options window, you may go to Advanced tab and look for Disable script debugging
- Put a check mark on the radio button
- At the same time, uncheck the «Display a Notification about every Script Error» item and then click Apply and OK, then reboot your computer.
If these quick fixes do not work, you can always backup files and run repair reinstall on your computer. However, you can do that later when the solutions listed here did not do the job.
Other languages:
Wie beheben Fehler 1602 (Backup Exec 2012 Fehlercode 1602) — Fehler 1602: Backup Exec hat ein Problem festgestellt und muss geschlossen werden. Wir entschuldigen uns für die Unannehmlichkeiten.
Come fissare Errore 1602 (Backup Exec 2012 Codice errore 1602) — Errore 1602: Backup Exec ha riscontrato un problema e deve essere chiuso. Ci scusiamo per l’inconveniente.
Hoe maak je Fout 1602 (Backup Exec 2012 Foutcode 1602) — Fout 1602: Backup Exec heeft een probleem ondervonden en moet worden afgesloten. Excuses voor het ongemak.
Comment réparer Erreur 1602 (Backup Exec 2012 Code d’erreur 1602) — Erreur 1602 : Backup Exec a rencontré un problème et doit se fermer. Nous sommes désolés du dérangement.
어떻게 고치는 지 오류 1602 (Backup Exec 2012 오류 코드 1602) — 오류 1602: Backup Exec에 문제가 발생해 닫아야 합니다. 불편을 드려 죄송합니다.
Como corrigir o Erro 1602 (Código de erro 1602 do Backup Exec 2012) — Erro 1602: O Backup Exec encontrou um problema e precisa fechar. Lamentamos o inconveniente.
Hur man åtgärdar Fel 1602 (Backup Exec 2012 felkod 1602) — Fel 1602: Backup Exec har stött på ett problem och måste avslutas. Vi är ledsna för besväret.
Как исправить Ошибка 1602 (Backup Exec 2012 Код ошибки 1602) — Ошибка 1602: Возникла ошибка в приложении Backup Exec. Приложение будет закрыто. Приносим свои извинения за неудобства.
Jak naprawić Błąd 1602 (Backup Exec 2012 kod błędu 1602) — Błąd 1602: Backup Exec napotkał problem i musi zostać zamknięty. Przepraszamy za niedogodności.
Cómo arreglar Error 1602 (Backup Exec 2012 Código de error 1602) — Error 1602: Backup Exec ha detectado un problema y debe cerrarse. Lamentamos las molestias.
About The Author: Phil Hart has been a Microsoft Community Contributor since 2010. With a current point score over 100,000, they’ve contributed more than 3000 answers in the Microsoft Support forums and have created almost 200 new help articles in the Technet Wiki.
Follow Us: 
This repair tool can fix common computer problems such as blue screens, crashes and freezes, missing DLL files, as well as repair malware/virus damage and more by replacing damaged and missing system files.
STEP 1:
Click Here to Download and install the Windows repair tool.
STEP 2:
Click on Start Scan and let it analyze your device.
STEP 3:
Click on Repair All to fix all of the issues it detected.
DOWNLOAD NOW
Compatibility
Requirements
1 Ghz CPU, 512 MB RAM, 40 GB HDD
This download offers unlimited scans of your Windows PC for free. Full system repairs start at $19.95.
Article ID: ACX02857EN
Applies To: Windows 10, Windows 8.1, Windows 7, Windows Vista, Windows XP, Windows 2000
Speed Up Tip #75
Setup Automatic Login:
If you are not too concerned about security in Windows or your computer is in a secure location, you can always set up automatic login. With this, your computer boots right into the desktop after turning it on without asking for a password.
Click Here for another way to speed up your Windows PC
Я пытаюсь удалить 32-разрядную версию Java 6 и установить 64-разрядную версию Java 7, но после первоначального открытия и успешного запуска деинсталлятора, запрашивая у меня полное удаление после перезагрузки, деинсталлятор не вернулся и не выполняет его. снова работать.
Я попытался с помощью revouninstaller удалить старую версию Java, которая кажется успешной, но программа установки Java 7 по-прежнему не запускается.
Когда я запускаю автономный установщик, он запрашивает права администратора, загружает MSI и затем исчезает. Посоветовавшись с программой просмотра событий, я нашел следующие записи в MsiInstaller:
Продукт: Java(TM) 7, обновление 2 (64-разрядная версия) — операция установки не выполнена.
а также
Установщик Windows установил продукт. Название продукта: Java(TM) 7, обновление 2 (64-разрядная версия). Версия продукта: 7.0.20. Язык продукта: 1033. Производитель: Oracle. Успешная установка или статус ошибки: 1602.
Все, что я знаю, это то, что ошибка 1602 должна означать, что пользователь отменил установку, что заставляет меня думать, что либо UAC не работает правильно (хотя, кажется, работает нормально), либо есть какая-то запись реестра, блокирующая установщик MSI (хотя я ‘ проверено вручную).
- Status
- Not open for further replies.
-
- Aug 28, 2019
-
- 3
-
- 0
-
- 10
- 0
-
#1
-
- Dec 24, 2011
-
- 8,087
-
- 1,030
-
- 53,590
- 1,538
-
#2
-
- Aug 28, 2019
-
- 3
-
- 0
-
- 10
- 0
-
#3
what OS u got, which java version
I have Windows Ten. I do not have Java so I do not know what version. Installing any recent version should be fine.
-
- Dec 24, 2011
-
- 8,087
-
- 1,030
-
- 53,590
- 1,538
-
- Aug 28, 2019
-
- 3
-
- 0
-
- 10
- 0
-
#5
I need Java to run Java Apps. I tried your links but I got the same message. Error Code 2
- Status
- Not open for further replies.
- Advertising
- Cookies Policies
- Privacy
- Term & Conditions
- Topics
 |
Error Number: | Error 1602 |
| Error Name: | Backup Exec 2012 Error Code 1602 | |
| Error Description: | Error 1602: Backup Exec has encountered a problem and needs to close. We are sorry for the inconvenience. | |
| Developer: | Symantec | |
| Software: | Backup Exec | |
| Applies to: | Windows XP, Vista, 7, 8, 10, 11 |
Analysis of Backup Exec 2012 Error Code 1602
Backup Exec 2012 Error Code 1602 is typically an error (bug) found at runtime. Programmers like Symantec endeavor to produce software that is free from these glitches until it is publicly released. Sadly, some critical issues such as error 1602 can often be overlooked.
Backup Exec users can face an error message after execution the program such as «Backup Exec 2012 Error Code 1602». In this way, end-users alert vendors about the presence of error 1602 problems by providing information to developer. Symantec will then have the knowledge to investigate how and where to fix the issue. So, in these cases, the developer will then release a Backup Exec program update to fix the error message displayed (and other reported problems).
Why And When Is Runtime Error 1602 Triggered?
A failure during the execution of Backup Exec is generally when you will encounter Backup Exec 2012 Error Code 1602 as a runtime error. Let’s analyze some of the most common causes of error 1602 runtime errors:
Error 1602 Crash — This is a common error 1602 runtime error that results in the program completely terminating. When the given input is invalid or does not adhere to the format expected, Backup Exec (or OS) fails.
Backup Exec 2012 Error Code 1602 Memory Leak — The consequences of a Backup Exec memory leak involve a malfunctioning operating system. It may be triggered by the misconfiguration of the software by Symantec, or when one command starts a loop which can’t be ended.
Error 1602 Logic Error — A Backup Exec logic error happens when it produces the wrong output, despite the user providing the correct input. This is seen when Symantec’s source code contains a flaw in data handling.
Backup Exec 2012 Error Code 1602 issues are often the result of the file that is missing, deleted, or accidentally moved from Backup Exec’s original installed location. Downloading and replacing your Symantec file can fix the problem in most cases. After the problem file is replaced, running a registry scan can help clean up any invalid Backup Exec 2012 Error Code 1602, file extension, or other file path references which could have been affected from a previous malware infection.
Classic Backup Exec 2012 Error Code 1602 Problems
These Backup Exec 2012 Error Code 1602-related Backup Exec Troubles Include:
- «Backup Exec 2012 Error Code 1602 Error.»
- «Invalid Win32 Program: Backup Exec 2012 Error Code 1602»
- «Backup Exec 2012 Error Code 1602 needs to close.»
- «Sorry, we can’t find Backup Exec 2012 Error Code 1602.»
- «Backup Exec 2012 Error Code 1602 not found.»
- «Start-up error in application: Backup Exec 2012 Error Code 1602.»
- «Backup Exec 2012 Error Code 1602 is not running.»
- «Backup Exec 2012 Error Code 1602 quit.»
- «Fault in Software Path: Backup Exec 2012 Error Code 1602.»
These Symantec error messages can appear during program installation, while a Backup Exec 2012 Error Code 1602-related software program (eg. Backup Exec) is running, during Windows startup or shutdown, or even during the installation of the Windows operating system. Keeping track of when and where your Backup Exec 2012 Error Code 1602 error occurs is a critical piece of information in troubleshooting the problem.
Backup Exec 2012 Error Code 1602 Problem Causes
Backup Exec 2012 Error Code 1602 issues are caused by a corrupt or missing Backup Exec 2012 Error Code 1602, invalid registry keys associated with Backup Exec, or a malware infection.
Chiefly, Backup Exec 2012 Error Code 1602 complications are due to:
- Backup Exec 2012 Error Code 1602 entry invalid or corrupt.
- Virus or malware corrupting Backup Exec 2012 Error Code 1602.
- Backup Exec 2012 Error Code 1602 mistakenly deleted or maliciously by software unrelated to the Backup Exec application.
- A different application in conflict with Backup Exec 2012 Error Code 1602, or other shared references.
- Corrupt download or incomplete installation of Backup Exec software.
Product by Solvusoft
Download Now
WinThruster 2022 — Scan your PC for computer errors.
Compatible with Windows 11, 10, 8, 7, Vista, XP and 2000
Optional Offer for WinThruster by Solvusoft | EULA | Privacy Policy | Terms | Uninstall
Log of the machines on which it is failing..:
————————————————————————————————
Successfully selected content location C:WINNTsystem32CCMCacheCEN00174.4.System
execmgr
6/10/2011 12:32:27 PM 3480 (0x0D98)
GetFileVersionInfoSize failed for file C:WINNTsystem32CCMCacheCEN00174.4.SystemINST-CTXOnlinePlgun-12-1-0-3.cmd, error 1812
execmgr
6/10/2011 12:32:27 PM 3480 (0x0D98)
Executing program as a script
execmgr
6/10/2011 12:32:27 PM 3480 (0x0D98)
Successfully prepared command line «C:WINNTsystem32CCMCacheCEN00174.4.SystemINST-CTXOnlinePlgun-12-1-0-3.cmd»
execmgr
6/10/2011 12:32:27 PM 3480 (0x0D98)
Command line = «C:WINNTsystem32CCMCacheCEN00174.4.SystemINST-CTXOnlinePlgun-12-1-0-3.cmd», Working Directory = C:WINNTsystem32CCMCacheCEN00174.4.System
execmgr
6/10/2011 12:32:27 PM 3480 (0x0D98)
Created Process for the passed command line
execmgr
6/10/2011 12:32:27 PM 3480 (0x0D98)
execmgr
6/10/2011 12:32:27 PM 3480 (0x0D98)
Raised Program Started Event for Ad:CEN203C3, Package:CEN00174, Program: CitrixOnlinePluginFull
execmgr
6/10/2011 12:32:27 PM 3480 (0x0D98)
Program exit code 1602
execmgr
6/10/2011 12:32:42 PM 2636 (0x0A4C)
Looking for MIF file to get program status
execmgr
6/10/2011 12:32:42 PM 2636 (0x0A4C)
Script for Package:CEN00174, Program: CitrixOnlinePluginFull failed with exit code 1602
execmgr
6/10/2011 12:32:42 PM
2636 (0x0A4C)
execmgr
6/10/2011 12:32:42 PM 2636 (0x0A4C)
Raised Program Error Event for Ad:CEN203C3, Package:CEN00174, Program: CitrixOnlinePluginFull
execmgr
6/10/2011 12:32:42 PM 2636 (0x0A4C)
Execution is complete for program CitrixOnlinePluginFull. The exit code is 1602, the execution status is FailureNonRetry
execmgr
6/10/2011 12:32:42 PM 3480 (0x0D98)
———————————————————————————————————————————-
Please suggest..
Share your knowledge. It’s a way to achieve immortality.
Добрый день!
В связи с обновлением платформы, хочу развернуть через GPO обновление клиентов 1С до свежей версии 8.3.22, чтобы не бегать ножками по каждому юзверу а это порядка 100 компов (все компы в домене). Попытался на своем ПК установить через GPO. Сначала была ошибка связанная с SQL, в интернете найдя инфу что нужно через orca поправить msi пакет, открыл 1CEnterprise 8_xp (x86-64) и внес в поле «Property» следующие данные:
DESIGNERALLCLIENTS = 1
THINCLIENT = 1
THINCLIENTFILE = 1
SERVER = 0
WEBSERVEREXT = 0
CONFREPOSSERVER = 0
SERVERCLIENT = 0
CONVERTER77 = 0
LANGUAGES = RU
Сохранил это под именем transfer.mst
Начал разворачивать через GPO, добавил пакет 1CEnterprise 8_xp (x86-64), тип особый, добавил модификации: transfer.mst и 1049_xp.mst , нажал ок. Перезагрузил компьютер, и не установилось ни чего, залез в «Просмотр событии» у себя на клиенте, и обнаружил: Установщик Windows выполнил установку продукта. Продукт: 1C:Enterprise 8 (x86-64) (8.3.22.1672). Версия: 8.3.22.1672. Язык: 1033. Изготовитель: 1C-Soft. Установка завершена с состоянием: 1602.
Подскажите, что еще необходимо сделать, в интернете не нашел решение этой ошибки.
другие программы спокойно устанавливаются (7zip, Office, Skype, и т.д.).
Операционная система Windows 10 Pro x86
-
Вопрос задан07 нояб. 2022
-
239 просмотров