Signature failed to validate
Hi,
I am working with OSB 10.3 and WSE 3.0
I have problem with message level security when I sign message with WSE 3.0 and send it to the OSB
I have proxy service that gets object Message {Header and Body}
the problem occurs when Body element have member class "XmlElement Any" with [XmlAnyElementAttribute] as member class
i,e my soap.body looks like
<soap:body>
<header>
<bla>...</bla>
</header>
<body>
<here comes any element that i want to insert , every time different tag name \>
</body>
</soap:body>
if body looks like this i get WSSecurityException : Signature failed to validate
and reference soap:body element (addressing and timestamp are validated)
if I remove XmlAnyElement and insert some string or whatever everything is fine.
I am stuck on it for 2 days now. Google don't help me :(
Thank you in advance
Raise a case with support and follow up there. Seeing your message structure, it seems there MAY be an issue at client side while generating signature.
Regards,
Anuj
Similar Messages
-
WSS client fails to validate signature
I try to call a secure X.509 web service with a standalone client. My client is able to call the service, but it fails to validate a signature in the response. Stacktrace:
Exception in thread "main" javax.xml.ws.soap.SOAPFaultException: weblogic.xml.dom.marshal.MarshalException: weblogic.xml.crypto.wss.WSSecurityException: Signature failed to validate. Reference: #str_nqug2feZarDRqizh does not validate.
at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:196)
at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:122)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:119)
at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89)
at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:118)
at $Proxy29.echoComplexType(Unknown Source)
at examples.webservices.simple_client.SecureMain2.main(Unknown Source)I deployed my war in WLS 10.3.1 and 10.3.3 with the same result.
My web service class is annotated with
@Policy(uri="policy:Wssp1.2-2007-Wss1.0-X509-Basic256.xml")I managed to get the request and response message from the sysout by setting VM directive
-Dweblogic.wsee.verbose=*I don't know where to go from here. Any help would be very much appreciated! Messages and sources are pasted below.
Request
<?xml version='1.0' encoding='UTF-8'?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Header>
<wsse:Security
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
S:mustUnderstand="1">
<wsse:BinarySecurityToken
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary"
ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"
wsu:Id="bst_Wf9BN8DhNsWFJp0a">MIIEVjCCAz6gAwIBAgIIBLJ8Vn+Q6E4wDQYJKoZIhvcNAQEFBQAwbDELMAkGA1UEBhMCTkwxFjAUBgNVBAgTDU5vb3JkIEhvbGxhbmQxHDAaBgNVBAcTE0x1Y2h0aGF2ZW4gU2NoaXBob2wxDTALBgNVBAoTBEZMVVgxGDAWBgNVBAMTD0ZMVVggTkwgVEVTVCBDQTAeFw0wOTEyMDMxNTI4MDdaFw0xMDEyMDMxNTI4MDdaMIGZMQswCQYDVQQGEwJOTDEWMBQGA1UECBMNTm9vcmQgSG9sbGFuZDEcMBoGA1UEBxMTTHVjaHRoYXZlbiBTY2hpcGhvbDEhMB8GA1UEChMYRkxVWCBMTk0gQkFDS09GRklDRSBURVNUMRwwGgYDVQQDExNMTk0gQmFja29mZmljZSBUZXN0MRMwEQYKCZImiZPyLGQBGRYDbG5tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA2ZsbeLX/1L0tMUnQkv903uEpiWIcrDzyd4IeBUZYGrbhJeU4DDtA2s4eDrs8UvmRyEVDklo45+V0E0nXs7mdKd453LvuCebQIkP9mIW1IWmfY7JzV2ZsGQuc2agaz6Sv9r+hsGScNeAmJHxgsEOSdbG6bs22NOeVmnQkxtxvDKjMfXNPIzfZoPoTxrjrnZ5MP8eA8pQtxu4eC7prhVnr/YARjzHWuMFhJ4WpZATrYOEdh6xiV5eb57um32FeOt07Pe5MfM1DRQI3c82vBRKydLqoKL+BucmfiMXjZH4fZ1lxxDIyxXI9uIpyVKBMg/fPfcN+H4UhaIdfYCKgEYUEZwIDAQABo4HNMIHKMB0GA1UdDgQWBBTNjyK10oUHCfthcT8t/E85su4ZyTCBnQYDVR0jBIGVMIGSgBQf3FULkLMCn5fhk9WjpUdLWBaVAKFwpG4wbDELMAkGA1UEBhMCTkwxFjAUBgNVBAgTDU5vb3JkIEhvbGxhbmQxHDAaBgNVBAcTE0x1Y2h0aGF2ZW4gU2NoaXBob2wxDTALBgNVBAoTBEZMVVgxGDAWBgNVBAMTD0ZMVVggTkwgVEVTVCBDQYIIBLJ8Vn+Q6EkwCQYDVR0TBAIwADANBgkqhkiG9w0BAQUFAAOCAQEAG80vtoA79iC2FtDjvxzXxF2BTmseuzOseiKT/uGdiiaAUEiGR/UDRtMyUCLTZrKVbl5B/myquti5dNpTOYqfej07zYV8DZhLfjHZFA5MQh0I7pa5XJxxWyY3rhMVDreN8aG9cSK1dxIuuxhvUCmgpLxardQMP1KAdio1sOoa+eggPD9fHvTDSU2/yYNFkWhFuqL7yPr11FCdTxxGYEUCvinAnJdoIWWTgYMEsc1FCClQgGNq3YWyt17QHUoCOlIP+lwJqo8ZMm4Snu4h+39LuOYNnQzt8wgteZljXjubkpPjR0zNxzGXmsMWePdaSPdkAnKEeQYj758IpuXU6m5r2w==
</wsse:BinarySecurityToken>
<dsig:Signature xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
<dsig:SignedInfo>
<dsig:CanonicalizationMethod
Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
<dsig:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1" />
<dsig:Reference URI="#Timestamp_hTfC4UvelIQ1rn58">
<dsig:Transforms>
<dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
</dsig:Transforms>
<dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
<dsig:DigestValue>Cz65y09RWeYk3bns0Zr3oBW80H0=</dsig:DigestValue>
</dsig:Reference>
<dsig:Reference URI="#Body_pW1NfGuv6WDEeSpi">
<dsig:Transforms>
<dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
</dsig:Transforms>
<dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
<dsig:DigestValue>htwgWFOYC84hfti4iXCCHh+deQs=</dsig:DigestValue>
</dsig:Reference>
<dsig:Reference URI="#bst_Wf9BN8DhNsWFJp0a">
<dsig:Transforms>
<dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
</dsig:Transforms>
<dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
<dsig:DigestValue>iOWrjzD2sZxSPXAWm8ZCFmA6tTY=</dsig:DigestValue>
</dsig:Reference>
</dsig:SignedInfo>
<dsig:SignatureValue>HxJyWczUY0vDts7+L3fHQVOCk0u1RsRJa/uiYVLJFamKlUGsP65cAzXN07S0oxrU4L/1h98QtD+K9nwog4qpqcuA9ocACCHIk5mHKVOIe3mg5Fo6cXgVzKVecoX2pB1p7XE74rv3Pqt2Jlnm6h34zDHC4nWmqnpL9KYB2oy3b6h5JyZMUAcd7MuKZ9jE0rVthgWLPeskR/4HKjhAKn8E7p62N3EWl+zjttBpwflFplc2478k6l94MfGhAAAfyQGhwXYG8+Ntn7yx3iy3k0pbdqWv6Otr7Df0X+qtg2/dg+zkjqHYDtHDOhbOBM3xSuKB+JwKz/5S6QRcEhSUS67nVQ==
</dsig:SignatureValue>
<dsig:KeyInfo>
<wsse:SecurityTokenReference
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
xmlns:wsse11="http://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
wsse11:TokenType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"
wsu:Id="str_Lko8bqWzpHuAHfh0">
<wsse:Reference URI="#bst_Wf9BN8DhNsWFJp0a"
ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" />
</wsse:SecurityTokenReference>
</dsig:KeyInfo>
</dsig:Signature>
<wsu:Timestamp
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
wsu:Id="Timestamp_hTfC4UvelIQ1rn58">
<wsu:Created>2010-10-01T15:10:09Z</wsu:Created>
<wsu:Expires>2010-10-01T15:11:09Z</wsu:Expires>
</wsu:Timestamp>
</wsse:Security>
</S:Header>
<S:Body
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
wsu:Id="Body_pW1NfGuv6WDEeSpi">
<ns3:echoComplexType xmlns:ns2="http://example.org/complex"
xmlns:ns3="http://example.org">
<arg0>
<intValue>999</intValue>
<stringValue>Hello Struct</stringValue>
</arg0>
</ns3:echoComplexType>
</S:Body>
</S:Envelope>
Response
<?xml version='1.0' encoding='UTF-8'?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Header>
<wsse:Security
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
S:mustUnderstand="1">
<dsig:Signature xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
<dsig:SignedInfo>
<dsig:CanonicalizationMethod
Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
<dsig:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1" />
<dsig:Reference URI="#Timestamp_QqBGh7JHiRcPisbg">
<dsig:Transforms>
<dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
</dsig:Transforms>
<dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
<dsig:DigestValue>QlAcOoVC9AaVR8qXElY0xcpL7No=</dsig:DigestValue>
</dsig:Reference>
<dsig:Reference URI="#Body_ELn3kyPvh9p7QpoV">
<dsig:Transforms>
<dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
</dsig:Transforms>
<dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
<dsig:DigestValue>yQN4RviZ3zpJyZxLHrBv9d7cgds=</dsig:DigestValue>
</dsig:Reference>
<dsig:Reference URI="#str_nqug2feZarDRqizh">
<dsig:Transforms>
<dsig:Transform Algorithm="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#STR-Transform">
<wsse:TransformationParameters>
<dsig:CanonicalizationMethod
Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
</wsse:TransformationParameters>
</dsig:Transform>
</dsig:Transforms>
<dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
<dsig:DigestValue>DVw6Uu/0QGb9WOROwxUGHidxdAU=</dsig:DigestValue>
</dsig:Reference>
</dsig:SignedInfo>
<dsig:SignatureValue>qgCaw39pMkxKTxaF0zupYoXNlHLQXww4MODkEJyoJJ/a/58sijzZ0JrD8Ni83Gb5LTflHlDkr6ANt/NPiauTu7azHnyMhQGtHhCY0tXk2XwS2tlKK1UP7dnZ7NazxSxSnAviHIgTHw1Ltg1XeOXjNrMmRRoaV1Lcb0ZfXUvSBiXGpBuprNYMqG/ARF6uV+sAUN2XFQkf+CLxNi6CBs+6M46yyy/FryvbHhlBLBBnyWXJ+yCo8TYhkKpo/moDFAUDAuhPBi60P7tocj/apxrjYZbaJVvIe+lHR09JxMZ5gdDTPAKuc3FQdt9p5yfA3m7mrNltlBY1I8RZSSb0ptItlg==
</dsig:SignatureValue>
<dsig:KeyInfo>
<wsse:SecurityTokenReference
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
xmlns:wsse11="http://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
wsse11:TokenType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"
wsu:Id="str_nqug2feZarDRqizh">
<wsse:KeyIdentifier
EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary"
ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509SubjectKeyIdentifier">S07jQjWN88pUII1gXUy7Hx60qC0=</wsse:KeyIdentifier>
</wsse:SecurityTokenReference>
</dsig:KeyInfo>
</dsig:Signature>
<wsu:Timestamp
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
wsu:Id="Timestamp_QqBGh7JHiRcPisbg">
<wsu:Created>2010-10-01T15:10:09Z</wsu:Created>
<wsu:Expires>2010-10-01T15:11:09Z</wsu:Expires>
</wsu:Timestamp>
</wsse:Security>
</S:Header>
<S:Body
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
wsu:Id="Body_ELn3kyPvh9p7QpoV">
<ns2:echoComplexTypeResponse xmlns:ns2="http://example.org"
xmlns:ns3="http://example.org/complex">
<ns3:EchoStructReturnMessage>
<intValue>999</intValue>
<stringValue>Hello Struct</stringValue>
</ns3:EchoStructReturnMessage>
</ns2:echoComplexTypeResponse>
</S:Body>
</S:Envelope>
Client
package examples.webservices.simple_client;
import java.security.cert.X509Certificate;
import java.util.ArrayList;
import java.util.List;
import java.util.Map;
import javax.xml.ws.BindingProvider;
import weblogic.security.SSL.TrustManager;
import weblogic.wsee.security.bst.ClientBSTCredentialProvider;
import weblogic.wsee.security.util.CertUtils;
import weblogic.xml.crypto.wss.WSSecurityContext;
import weblogic.xml.crypto.wss.provider.CredentialProvider;
public class SecureMain2 {
public static void main(String ar[]) throws Exception {
ComplexService test = new ComplexService();
ComplexPortType port = test.getComplexPortTypePort();
BasicStruct in = new BasicStruct();
in.setIntValue(999);
in.setStringValue("Hello Struct");
// String constants to for server certificate, and client identity store
String serverCertFile = "D:\\Development\\WebLogic-keystores\\client_trust.der";
String clientKeyStore = "D:\\Development\\WebLogic-keystores\\client_store.jks";
String clientKeyStorePass = "password";
String clientKeyAlias = "alias";
String clientKeyPass = clientKeyStorePass;
// Create list of credential providers
List<CredentialProvider> credProviders = new ArrayList<CredentialProvider>();
// Create a credential provider with the client indentity and the server side certificate
final X509Certificate serverCert = (X509Certificate) CertUtils.getCertificate(serverCertFile);
serverCert.checkValidity();
CredentialProvider cp = new ClientBSTCredentialProvider(clientKeyStore, clientKeyStorePass, clientKeyAlias, clientKeyPass, "JKS",
serverCert);
credProviders.add(cp);
// Finally add the credential providers to the request context
Map<String, Object> requestContext = ((BindingProvider) port).getRequestContext();
requestContext.put(WSSecurityContext.CREDENTIAL_PROVIDER_LIST, credProviders);
// Setup the TrustManager to verify the signature on the returned message
requestContext.put(WSSecurityContext.TRUST_MANAGER, new TrustManager() {
public boolean certificateCallback(X509Certificate[] chain, int validateErr) {
// Check that the server cert matches
boolean result = chain[0].equals(serverCert);
return result;
// Invoke the service
BasicStruct result = port.echoComplexType(in);
System.out.println("\n\n\t Service returned: " + result.getStringValue());
Web service
package examples.webservices.complex;
// Import the standard JWS annotation interfaces
import javax.jws.WebMethod;
import javax.jws.WebParam;
import javax.jws.WebResult;
import javax.jws.WebService;
import javax.jws.soap.SOAPBinding;
import weblogic.jws.Policy;
// Import the BasicStruct JavaBean
import examples.webservices.complex.BasicStruct;
// Standard JWS annotation that specifies that the portType name of the Web
// Service is "ComplexPortType", its public service name is "ComplexService",
// and the targetNamespace used in the generated WSDL is "http://example.org"
@WebService(serviceName="ComplexService", name="ComplexPortType",
targetNamespace="http://example.org")
// Standard JWS annotation that specifies this is a document-literal-wrapped
// Web Service
@SOAPBinding(style=SOAPBinding.Style.DOCUMENT,
use=SOAPBinding.Use.LITERAL,
parameterStyle=SOAPBinding.ParameterStyle.WRAPPED)
@Policy(uri="policy:Wssp1.2-2007-Wss1.0-X509-Basic256.xml")
* This JWS file forms the basis of a WebLogic Web Service. The Web Services
* has two public operations:
* - echoInt(int)
* - echoComplexType(BasicStruct)
* The Web Service is defined as a "document-literal" service, which means
* that the SOAP messages have a single part referencing an XML Schema element
* that defines the entire body.
public class ComplexImpl {
// Standard JWS annotation that specifies that the method should be exposed
// as a public operation. Because the annotation does not include the
// member-value "operationName", the public name of the operation is the
// same as the method name: echoInt.
// The WebResult annotation specifies that the name of the result of the
// operation in the generated WSDL is "IntegerOutput", rather than the
// default name "return". The WebParam annotation specifies that the input
// parameter name in the WSDL file is "IntegerInput" rather than the Java
// name of the parameter, "input".
@WebMethod()
@WebResult(name="IntegerOutput",
targetNamespace="http://example.org/complex")
public int echoInt(
@WebParam(name="IntegerInput",
targetNamespace="http://example.org/complex")
int input)
System.out.println("echoInt '" + input + "' to you too!");
return input;
// Standard JWS annotation to expose method "echoStruct" as a public operation
// called "echoComplexType"
// The WebResult annotation specifies that the name of the result of the
// operation in the generated WSDL is "EchoStructReturnMessage",
// rather than the default name "return".
@WebMethod(operationName="echoComplexType")
@WebResult(name="EchoStructReturnMessage",
targetNamespace="http://example.org/complex")
public BasicStruct echoStruct(BasicStruct struct)
System.out.println("echoComplexType called");
return struct;
}Hi ,
I have used the same Web Service Code provided by you and tried to execute the Standalone client ( as pasted by you here ) against the service and after some modification I was able to get the signature validation to true .
Here is the client I have used :
package examples.webservices.simple_client;
import java.security.cert.X509Certificate;
import java.util.ArrayList;
import java.util.List;
import java.util.Map;
import javax.xml.ws.BindingProvider;
import weblogic.security.SSL.TrustManager;
import weblogic.wsee.security.bst.ClientBSTCredentialProvider;
import weblogic.wsee.security.util.CertUtils;
import weblogic.xml.crypto.wss.WSSecurityContext;
import weblogic.xml.crypto.wss.provider.CredentialProvider;
import examples.webservices.complex.BasicStruct;
import javax.xml.rpc.Stub;
public class SecureMain2 {
public static void main(String ar[]) throws Exception {
ComplexService test = new ComplexService_Impl();
ComplexPortType port = test.getComplexPortTypeSoapPort();
BasicStruct in = new BasicStruct();
in.setIntValue(999);
in.setStringValue("Hello Struct");
// String constants to for server certificate, and client identity store
String serverCertFile = "E:\\wls_docs\\web_service\\demo.cer";
String clientKeyStore = "E:\\wls_docs\\web_service\\DemoIdentity.jks";
String clientKeyStorePass = "DemoIdentityKeyStorePassPhrase";
String clientKeyAlias = "DemoIdentity";
String clientKeyPass = "DemoIdentityPassPhrase";
// Create list of credential providers
List<CredentialProvider> credProviders = new ArrayList<CredentialProvider>();
// Create a credential provider with the client indentity and the server side certificate
final X509Certificate serverCert = (X509Certificate) CertUtils.getCertificate(serverCertFile);
serverCert.checkValidity();
CredentialProvider cp = new ClientBSTCredentialProvider(clientKeyStore, clientKeyStorePass, clientKeyAlias, clientKeyPass, "JKS",
serverCert);
credProviders.add(cp);
Stub stub = (Stub)port;
stub._setProperty(WSSecurityContext.CREDENTIAL_PROVIDER_LIST, credProviders);
stub._setProperty(WSSecurityContext.TRUST_MANAGER,
new TrustManager(){
public boolean certificateCallback(X509Certificate[] chain, int validateErr){
boolean result = chain[0].equals(serverCert);
System.out.println(" Validating Signature" );
System.out.println(" Result is " +result ) ;
return result;
// Finally add the credential providers to the request context
//Map<String, Object> requestContext = ((BindingProvider) port).getRequestContext();
//requestContext.put(WSSecurityContext.CREDENTIAL_PROVIDER_LIST, credProviders);
// Setup the TrustManager to verify the signature on the returned message
//requestContext.put(WSSecurityContext.TRUST_MANAGER, new TrustManager() {
//public boolean certificateCallback(X509Certificate[] chain, int validateErr) {
// Check that the server cert matches
//boolean result = chain[0].equals(serverCert);
//return result;
// Invoke the service
BasicStruct result = port.echoComplexType(in);
System.out.println("\n\n\t Service returned: " + result.getStringValue());
Thanks,
Sandeep -
X86 via patchsvr, "Failed to validate the digital signature(s)"
Been running very well for a while, now I'm getting these errors after an smpatch update/
bash-3.00# smpatch update
com.sun.patchpro.util.Percentage@96b5c2
119146-05 has been validated.
com.sun.patchpro.util.Percentage@5db5ae
119253-05 has been validated.
com.sun.patchpro.util.Percentage@42f352
119316-03 has been validated.
com.sun.patchpro.util.Percentage@1df2964
119251-03 has been validated.
com.sun.patchpro.util.Percentage@1ab600f
119255-06 has been validated.
com.sun.patchpro.util.Percentage@2fb002
120475-02 has been validated.
com.sun.patchpro.util.Percentage@cc7439
118924-02 has been validated.
com.sun.patchpro.util.Percentage@e2892b
118727-03 has been validated.
com.sun.patchpro.util.Percentage@9b688e
120236-01 has been validated.
com.sun.patchpro.util.Percentage@ed5d9d
120544-01 has been validated.
com.sun.patchpro.util.Percentage@1682a53
com.sun.patchpro.util.Percentage@7a9224
118891-01 has been validated.
com.sun.patchpro.util.Percentage@110b640
119686-03 has been validated.
com.sun.patchpro.util.Percentage@2d59a3
119076-06 has been validated.
com.sun.patchpro.util.Percentage@158015a
120010-01 has been validated.
com.sun.patchpro.util.Percentage@c0c8b5
119716-03 has been validated.
com.sun.patchpro.util.Percentage@b914b3
119108-06 has been validated.
com.sun.patchpro.util.Percentage@13fba1
120777-03 has been validated.
com.sun.patchpro.util.Percentage@1ed27e4
118345-04 has been validated.
com.sun.patchpro.util.Percentage@d61aef
118372-04 has been validated.
com.sun.patchpro.util.Percentage@82674b
119997-01 has been validated.
com.sun.patchpro.util.Percentage@14b84c7
119995-01 has been validated.
com.sun.patchpro.util.Percentage@fa5ff3
120037-01 has been validated.
com.sun.patchpro.util.Percentage@1b17d49
120035-01 has been validated.
com.sun.patchpro.util.Percentage@19855ed
119991-01 has been validated.
com.sun.patchpro.util.Percentage@31688f
120252-02 has been validated.
com.sun.patchpro.util.Percentage@1c794cc
120738-01 has been validated.
com.sun.patchpro.util.Percentage@1f9e31e
119987-01 has been validated.
com.sun.patchpro.util.Percentage@adf5be
119375-05 has been validated.
com.sun.patchpro.util.Percentage@e0c7c3
120665-01 has been validated.
com.sun.patchpro.util.Percentage@15b123b
118873-02 has been validated.
com.sun.patchpro.util.Percentage@9fdee
120051-01 has been validated.
com.sun.patchpro.util.Percentage@1fe4169
118851-02 has been validated.
com.sun.patchpro.util.Percentage@178920a
118863-01 has been validated.
com.sun.patchpro.util.Percentage@bbfa5c
120049-01 has been validated.
com.sun.patchpro.util.Percentage@131de9b
120347-01 has been validated.
com.sun.patchpro.util.Percentage@10d95cd
120720-01 has been validated.
com.sun.patchpro.util.Percentage@e5f46e
com.sun.patchpro.util.Percentage@1128f5a
118885-01 has been validated.
com.sun.patchpro.util.Percentage@1818f80
120470-02 has been validated.
com.sun.patchpro.util.Percentage@f42160
120468-02 has been validated.
com.sun.patchpro.util.Percentage@1bb326c
120047-01 has been validated.
com.sun.patchpro.util.Percentage@eb7331
120628-01 has been validated.
com.sun.patchpro.util.Percentage@1d7b222
119585-01 has been validated.
com.sun.patchpro.util.Percentage@1efe475
com.sun.patchpro.util.Percentage@7ff5b6
118847-01 has been validated.
com.sun.patchpro.util.Percentage@dc9065
com.sun.patchpro.util.Percentage@8beff2
com.sun.patchpro.util.Percentage@1362a63
119118-05 cannot be validated.
com.sun.patchpro.util.Percentage@c67a88
119417-01 cannot be validated.
com.sun.patchpro.util.Percentage@96ad7c
120455-01 cannot be validated.
com.sun.patchpro.util.Percentage@57ae58
120283-01 has been validated.
com.sun.patchpro.util.Percentage@775121
119373-02 has been validated.
com.sun.patchpro.util.Percentage@1f8acdc
120459-01 has been validated.
com.sun.patchpro.util.Percentage@11cc367
119543-05 has been validated.
com.sun.patchpro.util.Percentage@160c4b0
119411-02 has been validated.
com.sun.patchpro.util.Percentage@114025
119413-06 has been validated.
com.sun.patchpro.util.Percentage@8a52b6
120457-01 has been validated.
com.sun.patchpro.util.Percentage@13c550f
119549-02 has been validated.
com.sun.patchpro.util.Percentage@1f488f1
120297-01 has been validated.
com.sun.patchpro.util.Percentage@14a9387
120136-01 has been validated.
com.sun.patchpro.util.Percentage@11b86c7
com.sun.patchpro.util.Percentage@2da5a6
Unexpected Failure: java.lang.Throwable: ERROR: Failed to validate the digital signature(s).
bash-3.00#
And there it dies. here's the client's version information
bash-3.00# pkginfo -l SUNWppror
PKGINST: SUNWppror
NAME: PatchPro core functionality (Root)
CATEGORY: system
ARCH: i386
VERSION: 5.0,REV=2005.01.09.21.19
BASEDIR: /
VENDOR: Sun Microsystems, Inc.
DESC: PatchPro core functionality (Root)
PSTAMP: pm8-20020050222115150
INSTDATE: Jun 20 2005 12:41
HOTLINE: Please contact your local service provider
STATUS: completely installed
FILES: 15 installed pathnames
8 shared pathnames
3 linked files
9 directories
1 executables
5 blocks used (approx)
bash-3.00# pkginfo -l SUNWpprou
PKGINST: SUNWpprou
NAME: PatchPro core functionality (Usr)
CATEGORY: system
ARCH: i386
VERSION: 5.0,REV=2005.01.09.21.19
BASEDIR: /
VENDOR: Sun Microsystems, Inc.
DESC: PatchPro core functionality (Usr)
PSTAMP: pm8-20020050222115151
INSTDATE: Jun 20 2005 12:41
HOTLINE: Please contact your local service provider
STATUS: completely installed
FILES: 25 installed pathnames
7 shared pathnames
10 directories
5 executables
bash-3.00# uname -a
SunOS dns01 5.10 Generic_118844-01 i86pc i386 i86pc
bash-3.00#
Help?
Thanks,
Doug
1630 blocks used (approx)Unfortunatly the update server is having some very strange hicups every now and then. I've been able to reproduce this once on a sparc box. What I did was basicly running 'smpatch analyze' for a second time, followed by the regular 'update' command after which things worked out for me.
Some strange things also occur when you sometimes run the 'analyze' command, and then run it again. Sometimes you'll be presented with 2 different lists of available updates. -
PatchPro download failure | Failed to validate the digital signature
Hi,
Patchpro failing to validate some patches on 2 of our servers. One is throwing an error (1, below), the other is echoing an error to screen(2).
We are patching around a dozen servers (all SPARC, versions 8, 9 and 10) and these are the only 2 with problems.
Thanks for any help you can provide.
1)
Sol 9, SunFire 440
Error: PatchPro failed: ERROR: Failed to validate the digital signature(s).
/var/tmp/patches/124215-01.jar.tmp cannot be validated.
2)
Sol 8, SunFire 890
117557-04 cannot be validated.
com.sun.patchpro.model.PatchProRuntimeException: Unexpected throwable
at com.sun.patchpro.cli.PatchServices.waitForThread(PatchServices.java:1284)
at com.sun.patchpro.cli.PatchServices.downloadAllPatches(PatchServices.java:835)
at com.sun.patchpro.cli.PatchServices.main(PatchServices.java:502)
Caused by:
java.lang.Throwable: ERROR: Failed to validate the digital signature(s).
at com.sun.patchpro.model.PatchProModel$InnerDownloadPatchThread.downloadPatchFailed(PatchProModel.java:2855)
at com.sun.patchpro.server.GroupPatchDownloader.dispatchFailedEvent(GroupPatchDownloader.java:384)
at com.sun.patchpro.server.GroupPatchDownloader.downloadPatchFailed(GroupPatchDownloader.java:335)
at com.sun.patchpro.server.ServerPatchServiceProvider.dispatchFailedEvent(ServerPatchServiceProvider.java:2577)
at com.sun.patchpro.server.ServerPatchServiceProvider.validatePatchBundle(ServerPatchServiceProvider.java:2196)
at com.sun.patchpro.server.ServerPatchServiceProvider.requestDownload(ServerPatchServiceProvider.java:1780)
at com.sun.patchpro.server.ServerPatchServiceProvider.performDownloadPatches(ServerPatchServiceProvider.java:1082)
at com.sun.patchpro.server.ServerPatchServiceProvider.downloadPatches(ServerPatchServiceProvider.java:860)
at com.sun.patchpro.server.PatchServerProxy.downloadPatches(PatchServerProxy.java:142)
at com.sun.patchpro.server.GroupPatchDownloader.downloadPatches(GroupPatchDownloader.java:124)
at com.sun.patchpro.model.PatchProModel.performPatchDownload(PatchProModel.java:1932)
at com.sun.patchpro.model.PatchProStateMachine$10.run(PatchProStateMachine.java:526)
at com.sun.patchpro.util.State.run(State.java:266)
at java.lang.Thread.run(Thread.java:536)
#Not Working - Solaris9
===========
uname -a
=========
SunOS 05alpha 5.9 Generic_118558-28 sun4u sparc SUNW,Sun-Fire-V440
smpatch get
===========
# smpatch get
Unknown subcommand was specified.
Usage:
smpatch add -i <patchid> [-i <patchid> ...] |
-x idlist=<patchlist_file> [-d <patchdir>] [-h] where:
add Subcommand used to install the patches.
-d <patchdir>
Used to specify the directory where patches are
expected to be installed from.
-h Used to display help information for the add
subcommand.
-i <patchid>
Used to specify the id of the patch to install.
One or more patches can be specified using this
option.
-x idlist=<patchlist_file>
Used to specify the path of the file that contains
a list of patches to install.
Usage:
smpatch analyze [-h] where:
analyze Subcommand used to analyze a host and list needed
patches.
-h Used to display help information for the analyze
subcommand.
Usage:
smpatch download [-i <patchid> [-i <patchid> ...] |
-x idlist=<patchlist_file>] [-d <patchdir>] [-h] where:
download Subcommand used to download patches from SunSolve.
-d <patchdir>
Used to specify the directory where the patches
from SunSolve are to be downloaded.
-h Used to display help information for the download
subcommand.
-i <patchid>
Used to specify the id of the patch to download.
One or more patches can be specified using this
option.
-x idlist=<patchlist_file>
Used to specify the path of the file that contains
a list of patches to download.
Usage:
smpatch remove -i <patchid> [-h] where:
remove Subcommand used to remove a patch.
-h Used to display help information for the remove
subcommand.
-i <patchid>
Used to specify the id of the patch to remove.
Usage:
smpatch update [-d <patchdir>] [-h] where:
update Subcommand used to download and install required
patches for the local host.
-d <patchdir>
Used to specify the directory where the patches
from SunSolve which are required by the local host
are to be downloaded and installed from.
-h Used to display help information for the update
subcommand.
smpatch analyze
==============
smpatch analyze
Assessing required patches for machine "05alpha/150.3.84.207" . Please wait...
113434-33 SunOS 5.9: /usr/snadm/lib Library and Differential Flash Patch
111711-16 32-bit Shared library patch for C++
111712-16 64-Bit Shared library patch for C++
111722-05 SunOS 5.9: Math Library (libm) patch
117560-04 SunOS 5.9: Microtasking libraries (libmtsk) patch
115835-03 SunOS 5.9: Ghostscript patch
114344-21 SunOS 5.9: kernel/drv/arp Patch
117453-01 SunOS 5.9: libwrap Patch
114131-03 SunOS 5.9: multi-terabyte disk support - libadm.so.1 patch
120441-03 SunOS 5.9: libsec patch
113319-24 SunOS 5.9: libnsl nispasswdd patch
112960-40 SunOS 5.9: patch libsldap ldap_cachemgr libldap
118465-03 SunOS 5.9: rcm_daemon Patch
123762-01 SunOS 5.9: Chicago audio driver Patch
113318-26 SunOS 5.9: patch /kernel/fs/nfs and /kernel/fs/sparcv9/nfs
114718-05 SunOS 5.9: usr/kernel/fs/pcfs Patch
115544-02 SunOS 5.9: nss_compat patch
118463-01 SunOS 5.9: du Patch
116016-03 SunOS 5.9: /usr/sbin/logadm patch
123182-01 SunOS 5.9: iwscn patch
115542-02 SunOS 5.9: nss_user patch
116014-06 SunOS 5.9: /usr/sbin/usermod patch
117433-02 SunOS 5.9: FSS FX RT Patch
117431-01 SunOS 5.9: nss_nis Patch
123770-01 SunOS 5.9: Netra-CP3010 platform libraries patch
118558-35 SunOS 5.9: Kernel Patch
116561-15 SunOS 5.9: Volume System H/W Series platmod patch
123769-01 SunOS 5.9: Netra-CP3010 platform binaries patch
115336-04 SunOS 5.9: /usr/bin/tar, /usr/sbin/static/tar Patch
123767-01 SunOS 5.9: locator patch
117426-03 SunOS 5.9: ctsmc and sc_nct driver patch
123766-02 SunOS 5.9: pcf8584/pmugpio/ebus patch
121319-01 SunOS 5.9: devfsadmd_mod.so Patch
123765-01 SunOS 5.9: Chicago platform Patch
123764-01 SunOS 5.9: Boston platform Patch
123763-02 SunOS 5.9: Sun Fire V215/V245 platform Patch
121316-02 SunOS 5.9: kernel/sys/doorfs Patch
121314-01 SunOS 5.9: tl driver patch
120445-01 SunOS 5.9: Toshiba platform token links (TSBW,Ultra-3i)
112964-16 SunOS 5.9: /usr/bin/ksh Patch
113032-04 SunOS 5.9: /usr/sbin/init Patch
114259-02 SunOS 5.9: usr/sbin/psrinfo Patch
116543-04 SunOS 5.9: vmstat Patch
112958-04 SunOS 5.9: patch pci.so
112954-15 SunOS 5.9: uata Driver Patch
122716-01 SunOS 5.9: kernel/fs/lofs patch
122713-01 SunOS 5.9: expr patch
117168-02 SunOS 5.9: mpstat Patch
116498-02 SunOS 5.9: bufmod Patch
116495-03 SunOS 5.9: specfs Patch
117160-01 SunOS 5.9: /kernel/misc/krtld patch
118586-02 SunOS 5.9: cp/ln/mv & XPG4 cp/ln/mv Patch
120025-01 SunOS 5.9: ipsecconf Patch
117155-10 SunOS 5.9: pcipsy Patch
116486-03 SunOS 5.9: tsalarm Driver Patch
121998-01 SunOS 5.9: two-key mode fix for 3DES Patch
116482-02 SunOS 5.9: modload Utils Patch
117746-04 SunOS 5.9: patch platform/sun4u/kernel/drv/sparcv9/pic16f819
121992-01 SunOS 5.9: fgrep Patch
120768-01 SunOS 5.9: grpck patch
119438-01 SunOS 5.9: usr/bin/login Patch
116510-02 SunOS 5.9: wscons Patch
114224-06 SunOS 5.9: csh Patch
116670-04 SunOS 5.9: gld Patch
114383-04 SunOS 5.9: Enchilada/Stiletto - pca9556 driver
114370-05 SunOS 5.9: libumem.so.1 patch
124498-01 SunOS 5.9: tail patch
117483-01 SunOS 5.9: ntwdt Patch
112908-27 SunOS 5.9: gl_kmech_krb5 Patch
117480-01 SunOS 5.9: pkgadd Patch
117123-07 SunOS 5.9: wanboot Patch
115030-03 SunOS 5.9: Multiterabyte UFS - patch mount
113335-04 SunOS 5.9: devinfo Patch
113493-03 SunOS 5.9: libproc.so.1 Patch
113330-03 SunOS 5.9: rpcbind Patch
115028-02 SunOS 5.9: patch /usr/lib/fs/ufs/df
117471-03 SunOS 5.9: fifofs Patch
118897-01 SunOS 5.9: stc Patch
115022-03 SunOS 5.9: quota utilities
113720-02 SunOS 5.9: rootnex Patch
113329-18 SunOS 5.9: lp Patch
123056-01 SunOS 5.9: ldterm patch
114349-04 SunOS 5.9: sbin/dhcpagent Patch
113278-15 SunOS 5.9: NFS Daemon Patch
113471-09 SunOS 5.9: truss Patch
113277-48 SunOS 5.9: sd and ssd Patch
117457-01 SunOS 5.9: elfexec Patch
113077-18 SunOS 5.9: /platform/sun4u/kernal/drv/su Patch
113072-08 SunOS 5.9: patch /usr/sbin/format
112839-08 SunOS 5.9: patch libthread.so.1
114331-02 SunOS 5.9: power Patch
112998-04 SunOS 5.9: patch /usr/sbin/syslogd
114133-03 SunOS 5.9: mail Patch
119937-02 SunOS 5.9: inetboot patch
115553-23 SunOS 5.9: USB drivers patch
117443-01 SunOS 5.9: libkvm Patch
114329-02 SunOS 5.9: /usr/bin/pax Patch
114128-03 SunOS 5.9: sd_lun patch
119929-01 SunOS 5.9: /usr/bin/xargs patch
113459-05 SunOS 5.9: udp patch
116009-05 SunOS 5.9: sgcn & sgsbbc patch
123761-04 SunOS 5.9: PCIE/Fire drivers Patch
123760-01 SunOS 5.9: platform driver Patch
116557-04 SunOS 5.9: sbd Patch
120241-04 SunOS 5.9: bge patch
116530-02 SunOS 5.9: bge.conf Patch
116488-03 SunOS 5.9: Lights Out Management (lom) patch
117131-01 SunOS 5.9: adm1031 Patch
117124-12 SunOS 5.9: platmod, drmach, dr, ngdr, & gptwocfg Patch
118539-02 SunOS 5.9: schpc Patch
118472-01 SunOS 5.9: pargs Patch
122002-01 SunOS 5.9: kstat patch
122709-01 SunOS 5.9: /usr/bin/dc patch
117067-04 SunOS 5.9: awk nawk oawk Patch
115259-03 SunOS 5.9: patch usr/lib/acct/acctcms
112959-03 SunOS 5.9: patch libfru
112913-02 SunOS 5.9: fruadm Patch
113027-06 SunOS 5.9: libfrureg.so.1 Patch
114564-09 SunOS 5.9: /usr/sbin/in.ftpd Patch
117441-01 SunOS 5.9: FSSdispadmin Patch
118191-01 gtar patch
114818-06 GNOME 2.0.0: libpng Patch
117177-02 SunOS 5.9: lib/gss module Patch
116340-05 SunOS 5.9: gzip and Freeware info files patch
113579-09 SunOS 5.9: ypserv/ypxfrd Patch
122673-01 SunOS 5.9: sockio.h header patch
116474-03 SunOS 5.9: libsmedia Patch
116669-20 SunOS 5.9: md Patch
112965-06 SunOS 5.9: patch /kernel/drv/sparcv9/eri
112838-12 SunOS 5.9: pcicfg Patch
117127-02 SunOS 5.9: header Patch
123768-02 SunOS 5.9: byteorder.h and ddi_impldefs.h patch
121321-03 SunOS 5.9: ldap Patch
116231-03 SunOS 5.9: llc2 Patch
122976-01 SunOS 5.9: /usr/lib/mdb/kvm/ipc.so Patch
117179-01 SunOS 5.9: nfs_dlboot Patch
121194-01 SunOS 5.9: usr/lib/nfs/statd Patch
116502-03 SunOS 5.9: mountd Patch
113320-06 SunOS 5.9: patch se driver
114731-09 SunOS 5.9: kernel/drv/glm Patch
114716-02 SunOS 5.9: usr/bin/rcp Patch
112915-04 SunOS 5.9: snoop Patch
116778-01 SunOS 5.9: in.ripngd patch
119447-01 SunOS 5.9: ses Patch
114356-08 SunOS 5.9: /usr/bin/ssh Patch
113273-11 SunOS 5.9: /usr/lib/ssh/sshd Patch
113575-08 SunOS 5.9: sendmail Patch
116780-02 SunOS 5.9: scmi2c Patch
112972-17 SunOS 5.9: patch /usr/lib/libssagent.so.1 /usr/lib/libssasnmp.so.1 mibiisa
122485-01 SunOS 5.9: 1394 mass storage driver patch
113716-02 SunOS 5.9: sar & sadc Patch
117473-01 SunOS 5.9: fwtmp Patch
116472-02 SunOS 5.9: rmformat Patch
120443-01 SunOS 5.9: sed core dumps on long lines
121588-01 SunOS 5.9: /usr/xpg4/bin/awk Patch
123058-01 SunOS 5.9: /usr/xpg4/bin/more Patch
123184-02 SunOS 5.9: Bug fixes for Arabic fonts
113584-17 SunOS 5.9: yesstr, nostr nl_langinfo() strings incorrect in S9
117100-04 SunOS 5.9: New Euro UTF-8 locales needed
114600-06 SunOS 5.9: vlan driver patch
112817-29 SunOS 5.9: Sun GigaSwift Ethernet 1.0 driver patch
113042-16 SunOS 5.9: qlc driver patch
113041-13 SunOS 5.9: fcip driver patch
113039-17 SunOS 5.9: Sun StorEdge Traffic Manager patch
113040-21 SunOS 5.9: fctl/fp/fcp driver patch
117595-05 SunOS 5.9: Manual Page updates for Solaris 9
112622-19 SunOS 5.9: M64 Graphics Patch
116126-05 Fixes to general release PatchPro 2.2
119480-10 SUNWppro SUNWsy1cf SUNWsdb Bug fixes and updated keystore file with new patch signing certificate.
117985-03 SunOS 5.9: XIL 1.4.2 Loadable Pipeline Libraries
114538-38 SunOS 5.9: Sun XVR-100 Graphics Accelerator Patch
112661-11 SunOS 5.9: IIIM and X Input & Output Method patch
114677-12 SunOS 5.9: International Components for Unicode Patch
116039-02 SunOS 5.9: sun4u platform links patch
112804-02 CDE 1.5: sdtname patch
113244-09 CDE 1.5: dtwm patch
114312-02 CDE1.5: GNOME/CDE Menu for Solaris 9
119976-01 CDE 1.5: dtterm patch
112771-33 Motif 1.2.7 and 2.1.1: Runtime library patch for Solaris 9
117728-01 CDE1.5: dthello patch
124215-01 CDE 1.5: dtterm patch
112785-56 X11 6.6.1: Xsun patch
112807-18 CDE 1.5: dtlogin patch
118759-01 X11 6.6.1: Font Administration Tools patch
117577-03 X11 6.6.1: TrueType fonts patch
117663-02 X11 6.6.1: xwd patch
113764-05 X11 6.6.1: keyboard patch
/etc/release
==========
# cat /etc/release
Solaris 9 9/04 s9s_u7wos_09 SPARC
Copyright 2004 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 29 June 2004
CLUSTER
=========
# cat /var/sadm/system/admin/CLUSTER
CLUSTER=SUNWCuser
pkginfo
=======
# pkginfo -l SUNWpmgr SUNWppror SUNWpprou
PKGINST: SUNWpmgr
NAME: Solaris Patch Manager Base 1.0.1 1.0.1
CATEGORY: system
ARCH: all
VERSION: 1.0.1
BASEDIR: /
VENDOR: Sun Microsystems, Inc.
DESC: Patch Manager CLI for Solaris 2.6, 2.7 and 2.8
PSTAMP: ute15320031103164007
INSTDATE: May 16 2006 14:51
HOTLINE: Please contact your local service provider
STATUS: completely installed
FILES: 4 installed pathnames
3 shared pathnames
3 directories
1 executables
9 blocks used (approx)
ERROR: information for "SUNWppror" was not found
ERROR: information for "SUNWpprou" was not found -
Smpatch PatchPro failed: ERROR: Failed to validate the digital signature
Hello,
I 'm trying to update solaris 9 (5.9 Generic_118558-03 sun4u sparc) using smpatch.
I get the following error from all - to be installed - patches!!
Downloading the required patches for machine "xxx". Please wait...
Error: PatchPro failed: ERROR: Failed to validate the digital signature(s).
/var/sadm/spool/112941-10.jar.tmp cannot be validated.
I have read that you need to install patchid 112945-44 so i have installed it with no solution.
I have cleared the /var/tmp/patches/ directory:
# rm /var/tmp/patches/*.jar.tmp
# rm /var/sadm/spool/*.jar
I would be grateful if you reply me with any help.
Thanks,I thought this solution:
To download signed patch 112945-45 and:
# mv 112945-45.jar /var/sadm/spool/
# smpatch add -i 112945-45
On machine ""xxx"...
Installing patch 112945-45 ...
Error: PatchPro failed: Received a Manipulable event.
Error: PatchPro failed: Received a Manipulable event.
Error: PatchPro failed: ALERT: Failed to install a patch. 112945-45
/var/sadm/spool/patchpro_dnld_2007.06.14@12:22:38:EEST.txt has been moved to /var/sadm/spool/patchproSequester/patchpro_dnld_2007.06.14@12:22:38:EEST.txt
Problem Summary:
Inside /var/log/messages :
Jun 14 12:44:05 polymnia root: [ID 702911 user.error] Thu Jun 14 12:44:05 EEST 2007(ERROR) => Thread[Thread-18,5,main] <=Problem installing patches: Received a Manipulable event.
Jun 14 12:44:05 polymnia root: [ID 702911 user.alert] Thu Jun 14 12:44:05 EEST 2007(ALERT) => com.sun.patchpro.manipulators.SunOSSunPatchInstaller@73a5d3 <=112945-45 validation failed.
Jun 14 12:44:05 polymnia root: [ID 702911 user.crit] Thu Jun 14 12:44:05 EEST 2007(CRITICAL) => com.sun.patchpro.manipulators.SunOSSunPatchInstaller@73a5d3 <=com.sun.patchpro.security.SignatureValidationException: ERROR: Failed to validate the digital signature(s) for:
Jun 14 12:44:05 polymnia at com.sun.patchpro.manipulators.Installer.extractPatch(Installer.java:314)
Jun 14 12:44:05 polymnia at com.sun.patchpro.manipulators.SunOSSunPatchInstaller.install(SunOSSunPatchInstaller.java:46)
Jun 14 12:44:05 polymnia at com.sun.patchpro.manipulators.Installer.run(Installer.java:134)
Jun 14 12:44:05 polymnia at java.lang.Thread.run(Thread.java:536)
Jun 14 12:44:06 polymnia root: [ID 702911 user.error] Thu Jun 14 12:44:05 EEST 2007(ERROR) => Thread[Thread-18,5,main] <=Problem installing patches: Received a Manipulable event.
Jun 14 12:44:06 polymnia root: [ID 702911 user.alert] Thu Jun 14 12:44:06 EEST 2007(ALERT) => com.sun.patchpro.util.PatchBundleInstaller@9360e7 <=Failed to install a patch. 112945-45
Jun 14 12:44:06 polymnia patchadd utility failed. Reason code :0
Jun 14 12:44:06 polymnia root: [ID 702911 user.error] Thu Jun 14 12:44:06 EEST 2007(ERROR) => Thread[Thread-18,5,main] <=Problem installing patches: ALERT: Failed to install a patch. 112945-45
Also i have just seen that messages complains for the digital cert when i am tryring to download the patch using smpach
Jun 14 12:49:20 polymnia root: [ID 702911 user.error] Thu Jun 14 12:49:20 EEST 2007(ERROR) => com.sun.patchpro.server.ServerPatchServiceProvider@92425a <=com.sun.patchpro.security.NotSignedByKnownCertificateException: 112945-45/prepatch CN=Enterprise Services Patch Management, O=Sun Microsystems Inc
Jun 14 12:49:20 polymnia at com.sun.patchpro.security.SignatureValidationUtil.validateJarFile(SignatureValidationUtil.java:232)
Jun 14 12:49:20 polymnia at com.sun.patchpro.server.ServerPatchServiceProvider.validatePatchBundle(ServerPatchServiceProvider.java:1837)
Jun 14 12:49:20 polymnia at com.sun.patchpro.server.ServerPatchServiceProvider.requestDownload(ServerPatchServiceProvider.java:1437)
Jun 14 12:49:20 polymnia at com.sun.patchpro.server.ServerPatchServiceProvider.performDownloadPatches(ServerPatchServiceProvider.java:739)
Jun 14 12:49:20 polymnia at com.sun.patchpro.server.ServerPatchServiceProvider.downloadPatches(ServerPatchServiceProvider.java:585)
Jun 14 12:49:20 polymnia at com.sun.patchpro.server.PatchServerProxy.downloadPatches(PatchServerProxy.java:130)
Jun 14 12:49:20 polymnia at com.sun.patchpro.server.GroupPatchDownloader.downloadPatches(GroupPatchDownload
Jun 14 12:49:20 polymnia root: [ID 702911 user.error] Thu Jun 14 12:49:20 EEST 2007(ERROR) => com.sun.patchpro.server.ServerPatchServiceProvider@92425a <=Failed to validate the digital signature(s). for: /var/sadm/spool/112945-45.jar.tmp: 112945-45/prepatch CN=Enterprise Services Patch Management, O=Sun Microsystems Inc
Jun 14 12:49:20 polymnia root: [ID 702911 user.error] Thu Jun 14 12:49:20 EEST 2007(ERROR) => Thread[Thread-18,5,main] <=Error: downloading patches.ERROR: Failed to validate the digital signature(s).
The following patches were not downloaded. Contact your Sun Microsystems support provider for more information.
112945-45
Message was edited by:
sapila -
119116-20 - ERROR: Failed to validate the digital signature(s).
Hi I am getting such errors when I use smpatch:
bash-3.00# smpatch download -i 119116-20
com.sun.patchpro.util.Percentage@1c4ff2c
119116-20 cannot be validated.
Unexpected Failure: java.lang.Throwable: ERROR: Failed to validate the digital signature(s).
Can you please help me fix this?
Thanks,
MayureshI'm getting the same problem ; smpatch fails to validate signed patches.
I followed the instructions at:
http://forum.sun.com/jive/thread.jspa?threadID=108470&messageID=369154
However, 112945-43 is obsoleted by 112945-44, which I installed instead. I also installed this certificate, as the instructions indicate:
http://www.sun.com/pki/certs/ca/Object_Signing_CA-cert.der
Using pkgadm addcert -t -f der ./Object_Signing_CA-cert.der. I can see that it is installed:
# pkgadm listcert
Keystore Alias: Object Signing CA
Common Name: Object Signing CA
Certificate Type: Trusted Certificate
Issuer Common Name: Sun Microsystems Inc Root CA
Validity Dates: <Jun 2 00:00:00 2005 GMT> - <Jun 1 23:59:59 2015 GMT>
MD5 Fingerprint: A9:C8:BE:5E:79:67:42:A2:31:77:17:B9:0A:80:F8:F1
SHA1 Fingerprint: C7:CA:40:96:E7:DC:D8:59:01:07:76:B1:7A:FF:C0:B4:C3:27:A5:40However, 'smpatch update' still produces:
Error: PatchPro failed: ERROR: Failed to validate the digital signature(s).
/var/sadm/spool/113434-33.jar cannot be validated.I'm guessing that the Object Signing CA on http://www.sun.com/pki/certs/ca/ is not the correct certificate that I need to verify the signed patches. Can anyone point me in the right direction?
Thanks. -
Smpatch download: Failed to validate the digital signature
Hello,
what's the trick to download the patches?
# smpatch download
127732-01 cannot be validated.
123328-01 cannot be validated.
128495-01 has been validated.
125917-02 has been validated.
122537-02 cannot be validated.
121944-03 has been validated.
118667-14 cannot be validated.
Failure: ERROR: Failed to validate the digital signature(s).
# uname -a
SunOS mantis 5.10 Generic_118833-36 sun4v sparc SUNW,Sun-Fire-T1000
# smpatch get
patchpro.backout.directory "" ""
patchpro.baseline.directory - /var/sadm/spool
patchpro.download.directory /var/sadm/spool /var/sadm/spool
patchpro.install.types - rebootafter:reconfigafter:standard
patchpro.patch.source - https://getupdates1.sun.com/
patchpro.patchset current current
patchpro.proxy.host 172.x.x.xxx ""
patchpro.proxy.passwd **** ****
patchpro.proxy.port 8080 8080
patchpro.proxy.user "" ""-- NickI can echo this behavior here....
Also, I can isolate it (right now) to two patches. Looks like other people had more affected. Tomorrow, maybe it affects more for me too, I don't know. Manually downloading the two patches signed jar files, it seems like something is corrupt in the jar file:
# jar tvf 123328-01.jar
76 Mon Jun 05 14:11:28 CDT 2006 123328-01/.diPatch
236 Mon Jun 05 14:11:30 CDT 2006 123328-01/patchinfo
424 Mon Jun 05 16:04:24 CDT 2006 123328-01/SUNWcsu/pkgmap
538 Mon Jun 05 16:04:24 CDT 2006 123328-01/SUNWcsu/pkginfo
4985 Mon Jun 05 14:11:28 CDT 2006 123328-01/SUNWcsu/install/checkinstall
93 Mon Jun 05 14:11:28 CDT 2006 123328-01/SUNWcsu/install/copyright
5768 Mon Jun 05 14:11:28 CDT 2006 123328-01/SUNWcsu/install/i.none
1555 Mon Jun 05 14:11:28 CDT 2006 123328-01/SUNWcsu/install/patch_checkinstall
824 Mon Jun 05 14:11:28 CDT 2006 123328-01/SUNWcsu/install/patch_postinstall
6916 Mon Jun 05 14:11:28 CDT 2006 123328-01/SUNWcsu/install/postinstall
7437 Mon Jun 05 14:11:28 CDT 2006 123328-01/SUNWcsu/install/preinstall
18996 Mon Jun 05 15:59:36 CDT 2006 123328-01/SUNWcsu/reloc/usr/bin/expr
464 Mon Jun 05 16:04:24 CDT 2006 123328-01/SUNWxcu4/pkgmap
533 Mon Jun 05 16:04:24 CDT 2006 123328-01/SUNWxcu4/pkginfo
4985 Mon Jun 05 14:11:28 CDT 2006 123328-01/SUNWxcu4/install/checkinstall
93 Mon Jun 05 14:11:28 CDT 2006 123328-01/SUNWxcu4/install/copyright
5768 Mon Jun 05 14:11:28 CDT 2006 123328-01/SUNWxcu4/install/i.none
1555 Mon Jun 05 14:11:28 CDT 2006 123328-01/SUNWxcu4/install/patch_checkinstall
824 Mon Jun 05 14:11:28 CDT 2006 123328-01/SUNWxcu4/install/patch_postinstall
6703 Mon Jun 05 14:11:28 CDT 2006 123328-01/SUNWxcu4/install/postinstall
7437 Mon Jun 05 14:11:28 CDT 2006 123328-01/SUNWxcu4/install/preinstall
19060 Mon Jun 05 15:59:36 CDT 2006 123328-01/SUNWxcu4/reloc/usr/xpg4/bin/expr
464 Mon Jun 05 16:04:26 CDT 2006 123328-01/SUNWxcu6/pkgmap
533 Mon Jun 05 16:04:26 CDT 2006 123328-01/SUNWxcu6/pkginfo
4985 Mon Jun 05 14:11:30 CDT 2006 123328-01/SUNWxcu6/install/checkinstall
93 Mon Jun 05 14:11:30 CDT 2006 123328-01/SUNWxcu6/install/copyright
5768 Mon Jun 05 14:11:30 CDT 2006 123328-01/SUNWxcu6/install/i.none
1555 Mon Jun 05 14:11:30 CDT 2006 123328-01/SUNWxcu6/install/patch_checkinstall
824 Mon Jun 05 14:11:30 CDT 2006 123328-01/SUNWxcu6/install/patch_postinstall
6703 Mon Jun 05 14:11:30 CDT 2006 123328-01/SUNWxcu6/install/postinstall
7437 Mon Jun 05 14:11:30 CDT 2006 123328-01/SUNWxcu6/install/preinstall
18996 Mon Jun 05 15:59:36 CDT 2006 123328-01/SUNWxcu6/reloc/usr/xpg6/bin/expr
2380 Tue Jun 20 06:52:26 CDT 2006 123328-01/README.123328-01
13272 Mon Sep 26 22:46:30 CDT 2005 123328-01/LEGAL_LICENSE.TXT
5197 Tue Jun 20 07:00:18 CDT 2006 META-INF/manifest.mf
java.util.zip.ZipException: invalid entry size (expected 5305 but got 8321 bytes)
at java.util.zip.ZipInputStream.readEnd(ZipInputStream.java:371)
at java.util.zip.ZipInputStream.read(ZipInputStream.java:148)
at java.util.zip.ZipInputStream.closeEntry(ZipInputStream.java:92)
at sun.tools.jar.Main.list(Main.java:863)
at sun.tools.jar.Main.run(Main.java:212)
at sun.tools.jar.Main.main(Main.java:1022)The two patches I currently have affected are 123328-01.jar and 122537-02.jar -
I am attempting to distribute Adobe Flash updates using SCUP 2011, SCCM 2012 R2, WSUS ver4 and Windows Server 2012. Everything installs without error. I have acquired a certificate for SCUP signing from the internal Enterprise CA. I have
verified the signing certificate has a 1024 bit key. I have imported the certificate into the server's Trusted Publishers and Trusted Root CA stores for the computer. When I attempt to publish a Flash update with Full content I receive the following
error:
2015-02-13 23:00:48.724 UTC Error Scup2011.21 Publisher.PublishPackage PublishPackage(): Operation Failed with Error: Verification of file signature failed for file:
\\SCCM\UpdateServicesPackages\a2aa8ca4-3b96-4ad2-a508-67a6acbd78a4\3f82680a-9028-4048-ba53-85a4b4acfa12_1.cab
I have redone the certificates three times with no luck. I can import metadata, but any attempt to download content results in the verification error.
TIAHi Joyce,
This is embarrassing, I used that very post as my guide when deploying my certificate templates, but failed to change the bit length to 2048. Thank you for being my second set of eyes.
I changed my certificate key bit length to 2048, deleted the old cert from all certificate stores, acquired the a new signing cert, verified the key length was 2048, exported the new cert to pfx and cer files, imported into my Trusted publishers
and Trusted Root Authorities stores, reconfigured SCUP to use the new pfx file, rebooted the server and attempted to re-publish the updates with the following results:
2015-02-16 13:35:44.006 UTC Error Scup2011.4 Publisher.PublishPackage PublishPackage(): Operation Failed with Error: Verification of file signature failed for file:
\\SCCM\UpdateServicesPackages\a2aa8ca4-3b96-4ad2-a508-67a6acbd78a4\3f82680a-9028-4048-ba53-85a4b4acfa12_1.cab.
Is there a chance this content was already created and signed with the old cert, so installing the new cert has no effect? In ConfigMgr software updates I see 4 Flash updates, all marked Metadata Only (because they were originally published as "Automatic."
No Flash updates in the ConfigMgr console are marked as downloaded. I can't find any documentation on how the process of using SCUP for downloading content for an update marked Metadata Only actually works.
Comments and suggestions welcome. -
Deployer Installation: Failed to validate Release Management Server for Team Foundation Server 2013
Attempting to install the deployer on a machine and getting the below error. Not sure what that means, out of turn error or what actually occurs at this step, validating release management server, during the configuration piece. The user,
that we set for the service was validated fine. The user is an service account in the TFS RM Server, is an admin on the local box as well.
I am able to get into the TFS RM Server through the client just fine. I can hit the TFS RM UI just fine as well.
Curious what would not allow the deployer to complete as mentioned below.
Any help is appreciated.
I, 2013/12/16, 14:46:26.521, Validated account to use as identity for Release Management Services.
I, 2013/12/16, 14:46:26.521, Validating Release Management Server for Team Foundation Server 2013...
E, 2013/12/16, 14:46:30.905, Received Exception : Microsoft.TeamFoundation.Release.CommonConfiguration.ConfigurationException: Failed to validate Release Management Server for Team Foundation Server 2013.
at Microsoft.TeamFoundation.Release.CommonConfiguration.DeployerConfigurationManager.ValidateServerUrl()
at Microsoft.TeamFoundation.Release.CommonConfiguration.DeployerConfigurationManager.ValidateAndConfigure(DeployerConfigUpdatePack updatePack, DelegateStatusUpdate statusListener)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
I, 2013/12/16, 14:46:30.905, Work completed for GetConfiguration() call : got out of turn error
E, 2013/12/16, 14:46:30.905, Failed to validate Release Management Server for Team Foundation Server 2013.Hi Kpdn,
Thanks for your post.
All your participation and support are very important to build such harmonious/ pleasant / learning environment for MSDN community.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey. -
SSL VPN Failed to validate server certificate (cannot access https)
Hi all,
I have the next problem.
I've configured in an UC520 a SSL VPN.
I can access properly and I can see the labels, but I only can access urls which are http, not https:
I can access the default ip of the uc520 (192.168.1.10) but
When I try to get access to a secure url I get the msg: Failed to validate server certificate
I'm trying to access a Cisco Digital Media Manager, whose url is https://pc.sumkio.local:8080
Does the certificate of both hardware has to be the same?
How can I add a https?
Here is the config of the router:
webvpn gateway SDM_WEBVPN_GATEWAY_1
ip address 192.168.1.254 port 443
ssl trustpoint TP-self-signed-2977472073
inservice
webvpn context SDM_WEBVPN_CONTEXT_1
secondary-color white
title-color #CCCC66
text-color black
ssl authenticate verify all
url-list "Intranet"
heading "Corporate Intranet"
url-text "DMM Sumkio" url-value "http://pc.sumkio.local:8080"
url-text "Impresora" url-value "http://192.168.10.100"
url-text "DMM" url-value "https://pc.sumkio.local:8443"
url-text "DMM 1" url-value "http://192.168.10.10:8080"
url-text "UC520" url-value "http://192.168.10.1"
policy group SDM_WEBVPN_POLICY_1
url-list "Intranet"
mask-urls
svc dns-server primary 192.168.10.250
svc dns-server secondary 8.8.8.8
default-group-policy SDM_WEBVPN_POLICY_1
aaa authentication list sdm_vpn_xauth_ml_1
gateway SDM_WEBVPN_GATEWAY_1
max-users 10
inservice
Any help would be apreciatted.
Thank youHi, thanks for your advise.
I'm trying to copy the certificate via cut and paste, but I'm getting a
% Error in saving certificate: status = FAIL
I dont know if I'm doing this right.
I open the https page from the DMM with Mozilla Firefox, and in options I export the certificate in PEM format.
I get a file which if I open with notepad is like
-----BEGIN CERTIFICATE-----
MIICOzCCAaSgAwIBAgIET7EwyzANBgkqhkiG9w0BAQUFADBhMQswCQYDVQQGEwJV
KoZIhvcNAQEFBQADgYEAdk7n+tJi0igrTD2o7RD9ty8MLTyHN4uk8km+7DbpEy0g
mxLY0UZswYvbj15kPdd8QbeGEdDR6SXOYePsfIRJzL0mqMON4oiUhsqAK5y2yC6R
nqy4wWQ2fGVEYAeLpb1jGKdZWpuag/CO90NMHcMiobfBh+4eTqm7kRPTEyma6V0=
-----END CERTIFICATE-----
If I try to authenticate the trustpoint, I get that error.
how can I export the certificate from the DMM?
I think that this file is not the right file.
and then, do I have to make some changes in
webvpn gateway SDM_WEBVPN_GATEWAY_1?
Should I choose the new trustpoint?
I understand that the old trustpoint is for the outside connection, no for the LAN connection.
Dont worry about me, answer when you can but I really need to fix this.
Thank you so much -
I have reset both my torch and playbook back to original only thing that I kept was my contact. And still problems I am a few min away from leave my loved blackberry and going android !! Or heaven help us Phone
Issues 1) playbook wont connect to desktop manager anymore
2) Play book has 2 calendar icons with two different settings on them ??? I have one that is currently working with my yahoo email and calendar account.
3) my Phone when connected to desk top software shows the calendar as read only
4) Unable to update my phone says During an update of the applications on the BlackBerry® smartphone an error message may be displayed "BlackBerry Desktop Software failed to validate your BlackBerry device update - Aborting install due to validation failure. Some packages contained unsatisfactory dependencies."
I just want my email and Calendars to work I am tried of spending nights trying to get these deices working !!!
someone please help me. !!
I know you are going to ask I have updated everything last time and it is all as update as it can get.
As for now as I wait I am going to wipe my phone again and just set everything up again !! If I have to even my contacts AHHHH Help I am starting to think crazy thoughtsDid you try to eboot the your PC or laptop where your device is connected ?
I experienced this with my windows laptop, after a failed to do an update, I restart the laptop and my Torch, then retried, and it's worked -
Blackberry Desktop Software Failed to validate your blackberry device
Blackberry 8310 was running slow. The people at the ATT store said I need to update the software. Downloaded the newest version to the desktop and when I tried to upload it to the phone received the following message
"Blackberry Desktop Software Failed to validate your blackberry device update"
"Aborting install due to validation failure. Some packages contained unsatisfied dependencies"
I am sure others have seen it. What do I need to do. Thanks MikeGlad to hear. I just did this again last night, and I think I've isolated the specific program that causes the problem, but I can't be sure.
I think it's "Documents To Go".
People might try deleting just that one program first in Options > Applications > Add-Ons if they didn't want to delete everything else too. It's worth a shot.
J -
Verification of signature failed for file - when locally publish big file
Hi, I try to locally publish a package that is made of a 486 MB file. And I get this error message :
Verification of signature failed for file : ...
It works if I try with a smaller file (30~40 MB). So the issue is not related to the certificate. It's just like if there was a 'Timeout' that occurs during the process of publishing. But I can't see what to do to fix this.
Any advices are welcome.
David COURTEL
IT Technician
Wsus Third-Party Softwares Publishing :
Wsus Package PublisherDavid, there's a natural filesize limit for publishing CABs of 384MB.
This
article from myITForum.com has a PowerShell script that can be used to set the value higher.
Also, SolarWinds has a
free tool (useful if PowerShell is not an option) to set this value. In addition, the utility can be run remotely. All it needs is a local API connection. It has built in help, but here's the syntax you'll need:
/action setmaxcabsize /targetwsusname
WSUSServerName /targeetwsususessl {YES|NO} /targetwsusport portnumber /maxcabfilesize
sizeInMB
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds. -
WARNING: Failed to validate the xml content
Hi,
We notice this error when we start the web logic admin console and also in many of Hyperion log files. There are many instances of this error and everything is pointing to different lines in this file “jps-config.xml”.
WARNING: Failed to validate the xml content. cvc-complex-type.2.4.a: Invalid content was found starting with element 'serviceInstance'. One of '{"http://xmlns.oracle.com/oracleas/schema/11/jps-config-11_1.xsd":serviceInstance}' is expected.
Location: line 378 column 91 of file:/D:/Oracle/Middleware/user_projects/domains/EPMSystem/config/fmwconfig/mbeans/../jps-config.xml.
Oct 16, 2012 4:21:56 PM oracle.security.jps.internal.common.util.StrictValidationEventHandler handleEvent
Any ideas?
Regards,
Ragav.
Edited by: ragavhere on Oct 17, 2012 2:04 PMHi,
can you please provide more details on your application?
Which version of ADF are you using and which server. Are you trying to deploy on GlassFish server?
Which IDE are you using?
Perhaps this will be useful:
https://blogs.oracle.com/shay/entry/deploying_oracle_adf_applications_to
Regards,
Dimitrios. -
Apps won't install: BlackBerry Desktop Mgr failed to validate your BlackBerry device update
Just tried out the new Desktop Manager for Mac and it seems to blow up when trying to either install or uninstall applications.
I get the following error:
BlackBerry® Desktop Manager failed to validate your BlackBerry® device update.
Validation failed because a module marked for add (net_rim_platform_resource__pt) is not available on local disk
Some users have reported success with uninstalling an app first, but no luck with me.
Anyone have any ideas on this?
Thanks,
TomHi,
I've had the same problem and I have figured it out...for me anyway. Make sure you have the latest version of Blackberry Desktop Manager and obviously the lastest software for BlackBerry Torch also. So, ths is what worked for me...
connect phone to computer and click on Applications (top right)
click "Check for Updates"
click "Show Other Versions" (if there are no updates for phone)
chose "BlackBerry 6.0 6.0.0.246 (Current Version-Reload)
then select
Once this has reloaded and your device is restarted go back to Applications and add/delete (by checking or un-checking) what you want.
*Warning: I had a fair amount of trouble with error messages or something having to be reset, but after going through all the red tape and turning my phone off and on again a couple times it worked!!
Hope this helps or at least gets you started.
~Never missed my iPhone so much~
Geaux Tigers
Maybe you are looking for
-
When I enter a new event on iCal with the time, it leaves the time off of the Monthly view and in order for me to glance at the times of the day's events I have to click on each event or go into the event and edit it again putting the time on, for it
-
I updated to Yosemite on my Mac mini/server. Then my server wouldn't work. I updated and bought the software needed when updating to Yosemite. The server seems to be working. Subsequently I've started getting a notification on the server icon that an
-
How do I sync my email on my iphone/ipad and mac so I don't have to "Read" emails in 2 places?
My iphone and ipad are synced so when I read an email on one of the devices, it is marked as read, but I just got a new iMac and it will not mark the emails I've read on my iphone/ipad as read. How do I fix this?
-
Steps for re-using the same user id of a deleted user in OIM 11g ?
Hello experts, By Default, in OIM 11.1.1.5.0 it is not allowing to re-use the same user id of a deleted user. Consider a user with user id as "ABCD1234". The user is deleted from OIM and it is not getting displayed in the user search. But in DB we co
-
Find a specific Sublayer and move to top level layer
I have a lot of illustrator files that are organized by a template size. The layers are setup so that the top level layer is always Template. However the sublayer I need to move to the top level could be called 42 Pg Border or 30 Pg Border or 24 Pg B