Java Runtime Error 1330
Contents |
1330" when installing a Java Runtime Environment 6 update Article Number:000024931 First Published:August 15, 2015 Last Modified:August 15, 2015 Type:Support Environment BlackBerry Enterprise Server
Error 1330 Invalid Digital Signature
for Microsoft Exchange 5.0 SP2 to SP4 BlackBerry Enterprise Server for IBM Domino 5.0 error 1330 winverifytrust SP2 to SP4 Java Runtime Environment 1.6.0 Updates Back to top ↑ Overview When installing BlackBerry
Error 266 Was Returned By Winverifytrust
Enterprise Server, Java Runtime Environment (JRE) is a prerequisite and the BlackBerry Setup begins to install JRE. During the JRE Installation, an error similar to the following invalid digital signature error with a cab file is displayed:Error 1330. A file that is required cannot be installed because the cabinet file C:\Users\Username\AppData\LocalLow\Sun\Java\jre1.6.0_18\Data1.cab has an invalid digital signature. This may indicate that the cabinet file is corrupt. This was seen with Java Runtime Environment 1.6.0 Update 18 but similar errors could appear with later versions. Back to top ↑ Cause The error 24592 was returned by winverifytrust VeriSign Trust Network Root Certificate is missing from the local Certificate Store. Back to top ↑ Resolution Complete one of the following:Resolution 1 Obtain an updated copy of the VeriSign Trust Network Root Certificate and import the certificate into the local Certificate Store of the server. Open MMC then add the Certificate Snap-In. Expand the Trusted Root Certification Authority. Right-click the sub-folder Certificate, choose All Tasks > Import. Browse to the location that the VeriSign Trust Network CA file is located. Resolution 2 Install the Microsoft Root Certificate Program located here to resolve this issue. Back to top ↑ Workaround Back to top ↑ Additional Information VeriSign root certificates can be downloaded from the Symantec Website at the following link:http://www.symantec.com/page.jsp?id=rootsThere are 13 root certificates listed under the link above. It is recommended to install all but for the purpose of this issue we only need Class 3 certificates from G1, G2 and G3 as these are the ones used for code signing. Back to top ↑ Foll
& Install by Heath Stewart Application Lifecycle Management Application Insights Release Management Team Foundation Server Testing Visual Studio Team Services All Languages Visual
Error 1330 Invalid Digital Signature Data1 Cab
C++ Visual F# JavaScript TypeScript Python .NET .NET .NET with Beth Massi a file that is required cannot be installed because the cabinet file has an invalid signature ASP.NET by Scott Hanselman OData Team WPF Platform Development Apps for Windows Bing Edge Microsoft Azure Office 365
Error 1330 Invalid Digital Signature Error 266
Development Web Data Development SQL Server SQL Server Data Tools DocumentDB Setup & Install by Heath Stewart About Windows Installer, the .NET Framework, and Visual Studio. Another Possible Workaround http://support.blackberry.com/kb/articleDetail?ArticleNumber=000024931 for Error 1330 ★★★★★★★★★★★★★★★ December 11, 2008 by Heath Stewart (MSFT) // 12 Comments Share 0 0 When installing Visual Studio 2008, you might run into an error dialog that reads, Error 1330.A file that is required cannot be installed because the cabinet file D:\cab1.cab has an invalid digital signature. This may indicate that the cabinet file is corrupt. The https://blogs.msdn.microsoft.com/heaths/2008/12/11/another-possible-workaround-for-error-1330/ path and name of the cabinet may be different, but might often be D:\cab1.cab, where D: refers to your DVD drive. How to workaround this issue Some time ago I blogged that you should try copying the installation locally as in some cases this is related to brief network disconnects or disc read lag, or even a bad burn of an ISO image. You should still try that and other methods in some of the comments on that post first since those are for more likely problems. If you do not have Internet access, or have a restrictive firewall or proxy, setup may be failing to verify the signature because it cannot access the online certificate revocation list (CRL). This is most likely if you encounter the error on cab1.cab for VS2008 or MSDN. You’ll need a copy of setreg.exe which is available in the .NET Framework SDK, which is now part of the Windows SDK. By default, a revocation list is checked so Internet access is required. At any user privilege level, you can run the follo
accidentally Active Directory Blog Certification PVS Web Interface Receiver Secure Gateway Presentations PowerShell XenApp XenApp 5 for Windows Server 2003 XenApp 5 for Windows Server 2008 XenApp 6 for http://carlwebster.com/java-runtime-installation-failure-updated-for-jre-update-26/ Windows Server 2008 R2 XenApp 6.5 for Windows Server 2008 R2 XenDesktop XenServer https://windowshell.wordpress.com/2010/09/10/java-runtime-installation-failure-error-1330/ Java Runtime Installation failure - Updated for JRE Update 26 June 30, 2011 XenApp Java Runtime Installation Failure (Error 1330) Update: June 30, 2011. Oracle has changed some of the screens for JRE Update 26. This article has been updated at the bottom of the original article. When trying to error 1330 install the Java Runtime Environment (JRE) 6 Update 24 at a client site recently, I kept getting the error below (Figure 1): Figure 1 This is recorded in the Application Event Log as: Product: Java(TM) 6 Update 24 -- Error 1330.A file that is required cannot be installed because the cabinet file M:\Documents and Settings\_cwebster\Application Data\Sun\Java\jre1.6.0_24\Data1.cab has an invalid digital signature. invalid digital signature This may indicate that the cabinet file is corrupt. Error 24581 was returned by WinVerifyTrust. My first thought was that the certificate revocation check might be causing the problem, but, as you will see below, the servers are configured not to check for certificate revocation (Figure 2). Figure 2 I found a discussion of this error at http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6887806 . The problem is that Data1.cab is digitally signed and the servers I am trying to update are secured servers that do not have Internet access. Because these servers have no Internet access, they cannot verify the digital signature of Data1.cab with VeriSign. Following the instructions in the Work Around section, I went to https://knowledge.symantec.com/support/ssl-certificates-support/index?page=content&id=SO26896&pmv=print&actp=PRINT&viewlocale=en_US and created the two .cer certificate files. I then followed the link “If you enrolled for your certificate between May 17, 2009 and October 10th, 2010 Click here for your Intermediate CA.” This gave me a total of three .cer certificate files. I right-clicked each file and selected Install Certificate. Even after all this, JRE 6 Update 24 refused to install. In a past life, I was a software de
(Error1330) For security reasons, our network is completely disconnected from the Internet. And I mean completely… we are not allowed to connect, ever. In this situation, you quickly realize almost every vendor assumes you have Internet access (really? people still assume) and management of your network becomes harder by an order of magnitude. As an example, earlier this week, I was trying to create an install package for the latest JRE, version 6 update 21. I ended up getting an error 1330, invalid digital signature in data1.cab during the installation process. After some research, I came across the following forum posts: http://forums.sun.com/thread.jspa?threadID=5403715 and http://forums.sun.com/thread.jspa?threadID=5380073 EDIT: Sorry, I know these links are broken, but Oracle changed the forum structure when Sun got gobbled by them and I haven't had the time, or patience, to find where they went. Personally, I consider this an HFE failure (the fact that the links broke when the site was migrated). Shame on you Oracle. Based on our connectivity (or lack of it), I realized this was due to the fact that JRE has a CAB file that uses a VeriSign code signing certificate that is NOT part of the Microsoft Root CA list. To make matters worse, the CAB wants to run a CRL check that goes back to VeriSign. After fiddling around trying different security options to bypass the CRL check, I finally gave up and went another way. It turns out, that this issue only affects the JRE installer that is available for general consumer download. The JDK, on the other hand, has a copy of the JRE as part of the package that doesn't have this issue. The bad part, is that the JDK makes you install, well, JDK stuff in addition to the JRE (which is an option). Of course, I took this on as a challenge to split out the JRE as a standalone installer. Most installers work the same way. You download a single file and the file extracts all of the actual installation files into a temporary directory. Since we