Failed Core Validation

How to diagnose why XMLSignature.validate is returning "failed core validation"?
JWSDP 2.0 demos GenDetached and Validate work fine. Modified both to function properly with "file:" input rather than "http:", thus inserted calls to SetBaseURI for the JDK bug work around. Modified versions work fine also [with file: input].
Then moved both pieces of code into my application. Unlike GenDetached.java, which simply generates an internal KeyPair, I create a keystore using keytool -genkeypair. Modified the GenDetached code to read the keystore, extract the cert and thus the public key, and separately the private key. Signed with the private key. Transformed a JAXB object and inserted it into an XML file my application creates. Output looks good. But the code imported from Validate.java indicates "failed core validation", though the one and only reference validation status is "true", i.e., successful.
If I run Validate.java on the XML generated by my app, not GenDetached.java, it too indicates "failed core validation". So something must be wrong with the signing process.
How does one go about diagnosing "failed core validation"? The whole process appears to be simple pass/fail, with no explanation or diagnostic available. Thanks.

More information...
Have modified my app to not only transform a JAXB object and an OutputStream object but also a DOM object, see code as follows:
// output the resulting document to a JAXBResult
TransformerFactory tf = TransformerFactory.newInstance();
Transformer trans = tf.newTransformer();
JAXBContext jcs = JAXBContext.newInstance("com.cryptek.jtdi.dim.dmt.jaxb");
JAXBResult jaxbResult = new JAXBResult(jcs);
trans.transform(new DOMSource(doc), jaxbResult);
JAXBElement<SignatureType> jaxbElement = (JAXBElement<SignatureType>)jaxbResult.getResult();
// output the resulting document to stdout
trans.transform(new DOMSource(doc), new StreamResult(new FileOutputStream("signature.xml")));
// output the resulting document to a DOMResult
DOMResult domResult = new DOMResult();
trans.transform(new DOMSource(doc), domResult);
debugLogger.info("dom " + domResult.toString());
DumpNode(domResult.getNode(), 0);
Very curiously, DumpNode is revealing a <SignatureValue> identical to that produced by the JAXB object, i.e., a value which Validate.java rejects for "failed core validation" but approves reference validation.
Here is the log data for the JAXB transform object and the DOM transform object. Note <SignatureValue> in both cases is the same:
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - dom javax.xml.transform.dom.DOMResult@14ce5eb
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [#document: null] name #document type 9 value null
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [Signature: null] name Signature type 1 value null
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [SignedInfo: null] name SignedInfo type 1 value null
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [CanonicalizationMethod: null] name CanonicalizationMethod type 1 value null
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [SignatureMethod: null] name SignatureMethod type 1 value null
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [Reference: null] name Reference type 1 value null
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [DigestMethod: null] name DigestMethod type 1 value null
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [DigestValue: null] name DigestValue type 1 value null
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [#text: HNq7BMuL4wdr6g6YJOuS8DlTcDA=] name #text type 3 value HNq7BMuL4wdr6g6YJOuS8DlTcDA=
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [SignatureValue: null] name SignatureValue type 1 value null
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [#text: gdnCqYJAy7z2xFV35trujkinUluBfp5rbif14yfDPrmrYIZCWlekeA==] name #text type 3 value gdnCqYJAy7z2xFV35trujkinUluBfp5rbif14yfDPrmrYIZCWlekeA==
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [KeyInfo: null] name KeyInfo type 1 value null
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [KeyValue: null] name KeyValue type 1 value null
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [DSAKeyValue: null] name DSAKeyValue type 1 value null
2007-07-27 10:00:09,468 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [P: null] name P type 1 value null
2007-07-27 10:00:09,484 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [#text: /KaCzo4Syrom78z3EQ5SbbB4sF7ey80etKII864WF64B81uRpH5t9jQTxeEu0ImbzRMqzVDZkVG9
xD7nN1kuFw==] name #text type 3 value /KaCzo4Syrom78z3EQ5SbbB4sF7ey80etKII864WF64B81uRpH5t9jQTxeEu0ImbzRMqzVDZkVG9
xD7nN1kuFw==
2007-07-27 10:00:09,484 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [Q: null] name Q type 1 value null
2007-07-27 10:00:09,484 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [#text: li7dzDacuo67Jg7mtqEm2TRuOMU=] name #text type 3 value li7dzDacuo67Jg7mtqEm2TRuOMU=
2007-07-27 10:00:09,500 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [G: null] name G type 1 value null
2007-07-27 10:00:09,500 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [#text: Z4Rxsnqc9E7pGknFFH2xqaryRPBaQ01khpMdLRQnG541Awtx/XPaF5Bpsy4pNWMOHCBiNU0Nogps
QW5QvnlMpA==] name #text type 3 value Z4Rxsnqc9E7pGknFFH2xqaryRPBaQ01khpMdLRQnG541Awtx/XPaF5Bpsy4pNWMOHCBiNU0Nogps
QW5QvnlMpA==
2007-07-27 10:00:09,500 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [Y: null] name Y type 1 value null
2007-07-27 10:00:09,500 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - node [#text: MFc9VKzBT0ilHvURWYyFmwhPyCMdzVSqqkLe/SH+Y40vbZmUbyUboJHA/da0ad1CTjQjvCORXDb1
wml6N+/DOQ==] name #text type 3 value MFc9VKzBT0ilHvURWYyFmwhPyCMdzVSqqkLe/SH+Y40vbZmUbyUboJHA/da0ad1CTjQjvCORXDb1
wml6N+/DOQ==
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - schemaVersion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v1.0
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - schemaPublicationStatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . Published
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - processingUrgencyIndicator . . . . . . . . . . . . . . . . . . . . . . . . . . false
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.schemaVersion . . . . . . . . . . . . . . . . . . . . . . . . . . . . v1.0
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.schemaPublicationStatus . . . . . . . . . . . . . . . . . . . . . . . Published
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.SignedInfoType.CanonicalizationMethodType.Algorithm . . . . http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.SignedInfoType.SignatureMethodType.HMACOutputLength[0] . . .
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.SignedInfoType.SignatureMethodType.Algorithm . . . . . . . . http://www.w3.org/2000/09/xmldsig#dsa-sha1
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.SignedInfoType.ReferenceType[0].DigestMethodType.Other[0] .
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.SignedInfoType.ReferenceType[0].DigestMethodType.Algorithm . http://www.w3.org/2000/09/xmldsig#sha1
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.SignedInfoType.ReferenceType[0].DigestValue . . . . . . . . HNq7BMuL4wdr6g6YJOuS8DlTcDA=
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.SignedInfoType.ReferenceType[0].id . . . . . . . . . . . . . null
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.SignedInfoType.ReferenceType[0].URI . . . . . . . . . . . . file:/C:/JTDITransport_svn/foo.txt
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.SignedInfoType.ReferenceType[0].Type . . . . . . . . . . . . null
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.SignatureValueType.id . . . . . . . . . . . . . . . . . . . null
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.SignatureValueType.value . . . . . . . . . . . . . . . . . . gdnCqYJAy7z2xFV35trujkinUluBfp5rbif14yfDPrmrYIZCWlekeA==
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.KeyInfoType.KeyValueType.DSAKeyValueType.P . . . . . . . . . /KaCzo4Syrom78z3EQ5SbbB4sF7ey80etKII864WF64B81uRpH5t9jQTxeEu0ImbzRMqzVDZkVG9
xD7nN1kuFw==
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.KeyInfoType.KeyValueType.DSAKeyValueType.Q . . . . . . . . . li7dzDacuo67Jg7mtqEm2TRuOMU=
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.KeyInfoType.KeyValueType.DSAKeyValueType.G . . . . . . . . . Z4Rxsnqc9E7pGknFFH2xqaryRPBaQ01khpMdLRQnG541Awtx/XPaF5Bpsy4pNWMOHCBiNU0Nogps
QW5QvnlMpA==
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.KeyInfoType.KeyValueType.DSAKeyValueType.Y . . . . . . . . . MFc9VKzBT0ilHvURWYyFmwhPyCMdzVSqqkLe/SH+Y40vbZmUbyUboJHA/da0ad1CTjQjvCORXDb1
wml6N+/DOQ==
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.KeyInfoType.KeyValueType.DSAKeyValueType.J . . . . . . . . . null
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.KeyInfoType.KeyValueType.DSAKeyValueType.Seed . . . . . . . null
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.KeyInfoType.KeyValueType.DSAKeyValueType.PgenCounter . . . . null
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.KeyInfoType.KeyValueType.java.lang.String . .
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.KeyInfoType.java.lang.String . .
2007-07-27 10:00:10,187 [main] INFO com.cryptek.jtdi.dim.dmt.JTDITransportImpl - JtdiData.Signature.id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . null
And here is the OutputStream result. Note <SignatureValue> is NOT the same as the above, and that Validate.java approves these results:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<Signature xmlns="http://www.w3.org/2000/09/xmldsig#">
<SignedInfo>
<CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments"/>
<SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#dsa-sha1"/>
<Reference URI="file:/C:/JTDITransport_svn/foo.txt">
<DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
<DigestValue>HNq7BMuL4wdr6g6YJOuS8DlTcDA=</DigestValue>
</Reference>
</SignedInfo>
<SignatureValue>E/402n/h/7G4z5tU4hq1UoNc5qM5e7KShpKl/E2Rtx20jrPN1rKVdg==</SignatureValue>
<KeyInfo>
<KeyValue>
<DSAKeyValue>
<P>/KaCzo4Syrom78z3EQ5SbbB4sF7ey80etKII864WF64B81uRpH5t9jQTxeEu0ImbzRMqzVDZkVG9xD7nN1kuFw==</P>
<Q>li7dzDacuo67Jg7mtqEm2TRuOMU=</Q>
<G>Z4Rxsnqc9E7pGknFFH2xqaryRPBaQ01khpMdLRQnG541Awtx/XPaF5Bpsy4pNWMOHCBiNU0NogpsQW5QvnlMpA==</G>
<Y>MFc9VKzBT0ilHvURWYyFmwhPyCMdzVSqqkLe/SH+Y40vbZmUbyUboJHA/da0ad1CTjQjvCORXDb1wml6N+/DOQ==</Y>
</DSAKeyValue>
</KeyValue>
</KeyInfo>
</Signature>

Similar Messages

Inconsistent Form Behavior on Failed Struts Validation

So I'm working on a strange bug regarding an Edit User form for an application, where some fields revert to their default and some fields do not.
We have a form for editing users in our system, with most of the usual information inputted in text boxes (login, first name, last name, password, password confirmation). We also have three possible levels of 'admin' - none, admin, and superadmin. These are chosen via radio buttons. There are also a couple of checkboxes (like 'user is active'). Overall, it's a fairly simple form.
When the form is submitted, we do struts validation. We've set up the validation via comment annotation in our Java code, like so:
     * @struts.validator type="minlength"
     *                   arg1value="${var:minlength}"
     * @struts.validator-var name="minlength" value="8"
     * @struts.validator type="maxlength"
     *                   arg2value="${var:maxlength}"
     * @struts.validator-var name="maxlength" value="50"
    public void setPassword1(String string) {
        password1 = string;
    }All of the fields in our form are set from user properties, so they're initialized by the values in the user object. For example, if we had user John Smith, an admin, with login 'jsmith,' we'd have the first name and last name fields initialized to John and Smith, and the radio buttons for Admin set to 'admin.' For reference, here's the EditUser.jsp code for the radio buttons, based off of the selectedAdminRole property:
<div class="InputElement">
        <label for="selectedAdminRole"><bean:message key="userForm.adminType"/></label>
          <html:radio styleId="selectedAdminRole" property="selectedAdminRole" value="None"
                      disabled="${userForm.loggedInUser.admin and userForm.userId == userForm.loggedInUser.id}">None</html:radio>
          <html:radio property="selectedAdminRole" value="Admin"
                      disabled="${userForm.loggedInUser.admin and userForm.userId == userForm.loggedInUser.id}">Admin</html:radio>
          <c:if test="${userForm.loggedInUser.superAdmin}">
              <html:radio property="selectedAdminRole" value="SuperAdmin">Super</html:radio>
          </c:if>
     </div>As you can see above, the struts validator requires passwords to be at least 8 characters long. So if the user tries to change their password to something with less than that, they'll fail validation and they'll end up back on the form with the validation errors in red at the top of the page. However, the form data that they've edited will be preserved. So if John had tried to change his first name to 'Fred,' he'd still see 'Fred' in the First Name text field, even though it wouldn't actually get saved to the user object until he submitted the form with no errors. This works with radio buttons too - if John had tried to set his admin status down to 'none' from 'admin,' the radio button 'none' would still be checked. Basically, it preserves all your progress on the form until you navigate away.
Unfortunately, it does NOT do this when you create a new user. Creating a new user uses the same form, and since there's no user object to get the fields from, they all get initialized to blank - except for one of the checkboxes ('user is active') and the radio buttons for admin (starts with 'none' checked). Now, if the user fills out the form and hits submit, but fails the struts validation, it preserves all the form data in the text fields, but reverts the checkboxes and the radio buttons to their default state.
This leads to the following problem: say I'm trying to create a new admin, Jane Smith. I fill out the whole form, check the 'admin' button, and then enter a four-letter password. I submit, and the form fails struts validation and throws me back to the page with an error message informing me that passwords need to be at least 8 characters. I look over the form again - the login field is still 'janesmith,' the first name field is still 'Jane,' the last name field is still 'Smith,' everything looks fine except I screwed up the password. I enter an 8 letter password and resubmit. Jane then logs in and complains that she's not an admin, because I didn't notice that the 'admin' button had reset itself to the default of 'none' when I failed validation.
My question is, why does it reset the radio buttons and checkboxes - but not the text fields - on failed validation when a new user is being created, but resets nothing at all when an existing user is being edited? I'd like it to reset none of the information when a new user is being created, but I cannot figure out the reason for this inconsistent behavior.
If anyone can help me figure out how to get this working so that nothing gets reset - or at least explain to me the reason for this inconsistent behavior - I would be very grateful. I will also try to provide any additional information I can if this isn't enough.

So what you are saying is that radio and checkboxes don't retain their state when validation fails?
Checkboxes are always troublesome because of their design. If not selected, they don't submit any value - so you have to specifically unset them.
My first instinct would be to look at the formbean which you are populating from, and see what (if anything) modifies its values.
- for originally loading the new user page is it an action or JSP? Does it apply any default values to the form?
- check the "input" page you redirect to when validation fails. Is it an action or a JSP?
- is the same form being uses on the newUser jsp and whatever action you are submitting it to?
- is there a form reset() method?
My theory is that the "input" page you are redirecting to when validation fails is an action, and it sets some values on the form prior to loading.
But thats just a guess at this point. Its hard to debug this without a working example. Its been a while since I worked with struts, and never with annotations providing the validation.
Suggestion for debugging: dump the contents of the form bean at strategic points in the process to see that the values are what you think they should be.
- running the save action
- just after validation
- on the jsp page.
Hope this helps some,
evnafets

Mitigation control: Sending failed No valid SAP sender address

GRC 5.3 SP10 RAR
In mitigation control: I have created a new control ID. When I am trying to assign it to a user getting error
"Sending failed No valid SAP sender address"
Please advise to resolve the issue. I need to mitigate user.

Hello Pal,
Please go to RAR configuration -> Risk Analysis -> Additional Options. Here check if you have the parameter Enable Monitor Notification set to YES. If you do then set this one to NO. Also, kindly check and make sure that you have a valid email address maintained for each of the mitigation control monitor in Mitigation tab.
If you wish to have the parameter set to yes only then you need to do the JAVA mail settings in Visual Admin. Check configuration of the JAVA mail client, which can be done using Visual Administrator, to send the Email Notification.
(Configuration > Java Mail Client > Properties > Smtp).
Regards, Varun
Edited by: Thakur Varun on May 21, 2010 3:47 PM

ICal Import Failed Multiple validation errors occurred.

I am trying to move my old iCal calendars that used to sync fine to the new ones to sync to mobile me
I exported each calendar but when I try to import each I get
iCal Import Failed Multiple validation errors occurred.
It occurs whether or not I choose to keep or remove unsafe alarms.
I have deleted iCal caches etc.

i'm having this problem as well. (in addition to duplicate calendars of the ones i was able to manually import.) any help would be greatly appreciated.
/rant on
this isn't really the way i had hoped to spend my saturday night, i'm really disappointed that ical didn't sync intuitively to mobileme--isn't that why i pay for a subscription?
/rant off.

ORA-04098 trigger"BANKTRAN_BEF_DEL" is invalid and and failed re-validation

Hey Experts,
I created follwoing trigger successfully...
create or replace trigger BANKTRAN_BEF_DEL
before delete on BANKTRAN
declare
weekend_error EXCEPTION;
not_authentocated_user EXCEPTION;
begin
if TO_CHAR(SysDate,'DY') = 'SAT' or TO_CHAR(SysDate,'DY') = 'SUN' THEN
RAISE weekend_error;
end if;
if SUBSTR(User,1,3) <> 'ATN' THEN
RAISE not_authentocated_user ;
end if;
EXCEPTION
WHEN weekend_error THEN
RAISE_APPLICATION_ERROR (-20001,
'Deletions not allowed on weekends');
WHEN not_authentocated_user THEN
RAISE_APPLICATION_ERROR (-20002,
'Deletions only allowed by authentocated users');
end;
but when deleting the records using query delete from BANKTRAN
getting the below error
ORA-04098 trigger"BANKTRAN_BEF_DEL" is invalid and and failed re-validation
Edited by: SShubhangi on Jan 7, 2013 4:21 PM

Alright.
Now Try the DML that causes the Trigger to fire.
And post the details.
PS:- Please use {noformat}{noformat} before and after the SQL statements/results or code samples.
It makes post more readable and you get better help.

Trouble with notifications - failed schema validation

I am trying to send an Email notification from a workflow and am getting the following error:
System.Web.Services: System.Web.Services.Protocols.SoapException: The request failed schema validation: The element 'Message' in namespace 'http://schemas.microsoft.com/exchange/services/2006/types' has invalid child element 'Header' in namespace 'http://schemas.xmlsoap.org/soap/envelope/'.
List of possible elements expected: 'Sensitivity, Body, Attachments, DateTimeReceived, Size, Categories, Importance, InReplyTo, IsSubmitted, IsDraft, IsFromMe, IsResend, IsUnmodified, InternetMessageHeaders, DateTimeSent, DateTimeCreated, ResponseObjects,
ReminderDueBy, ReminderIsSet, ReminderMinutesBeforeStart, DisplayCc, DisplayTo, HasAttachments, ExtendedProperty, Culture, Sender, ToRecipients, CcRecipients, BccRecipients, IsReadReceiptRequested, IsDeliveryReceiptRequested, ConversationIndex, ConversationTopic,
From, InternetMessageId, IsRead, IsResponseRequested, References, ReplyTo' in namespace 'http://schemas.microsoft.com/exchange/services/2006/types'.
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at Microsoft.ResourceManagement.WebServices.Mail.Exchange.ExchangeServiceBinding.CreateItem(CreateItemType CreateItem1)
   at Microsoft.ResourceManagement.Mail.ExchangeProxy.ExecuteCreateItem(CreateItemType request)
   at Microsoft.ResourceManagement.Mail.ExchangeServer.SendNotification(NotificationMessage message)
   at Microsoft.ResourceManagement.Mail.NotificationMessage.Send(Int32 timeoutInMilliseconds)
   at Microsoft.ResourceManagement.Workflow.Hosting.SendMailWorkItemProcessor.SendMailMessage(MessageContent messageContent, Int32 timeoutInMilliseconds)
   at Microsoft.ResourceManagement.Workflow.Hosting.SendMailWorkItemProcessor.ProcessWorkItem(WorkItem workItem
It appears that the Exchange web service doesn't like the schema FIM is presenting. Anyone seen this? Is there a trace setting that will dump out the call to the Exchange
server?
I have tested that I can hit
https://fqdn_server/ews/exchange.asmx
from the FIM Service account and the certificate is correct.

After getting product support involved, it turns out that we were pointing the FIM Service at an Exchange 2013 server but the mailbox had been created on and was physically stored on an Exchange 2010 server. By pointing FIM at the 2010 server or by trying
to send notifications to mailboxes on the 2013 server, we could make it work. Moving the mailbox from the 2010 server to the 2013 server did not solve the problem. It had something to do with mailboxes that were originally created on a 2010 server but
were accessed over EWS from a 2013 server.
It also was not a FIM issue. We used an EWS diagnostic tool (EWSEditor) to test outside of FIM and saw the same results.
The final result to get the specific user working for notifications was to create a new mailbox for them on the Exchange 2013 server.

E-Mail Validation fails (email validation)

Hi,
according to the RFC, emails addresses in the following
format are allowed: [email protected]
but SPRY fails on validating this email address. Is there a
fix for that? And if not, which file would I have to update in
order to allow this email format?
Thanks!
Nils

Hi Nils,
You need to modify
http://labs.adobe.com/technologies/spry/widgets/textfieldvalidation/SpryValidationTextFiel d.js
Open that file and do a search for 'email', you should see a
regular expression after it that looks something like this:
var rx = /^[\w\.-]+@[\w\.-]+\.\w+$/i;
You'll probably want to add the + to it like this:
var rx = /^[\w\.-\+]+@[\w\.-]+\.\w+$/i;
I'll file a bug on our side to make sure we allow all chars
specified in the RFC.
--== Kin ==--

Failed Cluster Validation Wizard - Active Directory

Hi All,
I have a problem creating a cluster that has just got me stumped.
I've created two other clusters at two other sites with exact same hardware and configuration. All worked fine at those location.
For this third location, the cluster build is not going so well.
I have 2 x Dell server for a 2 node cluster, and a Dell SAN. There are iSCSI HBAs and switches for iSCSI and a flat network for the LAN and Management on another switch. The heartbeat is connected via a directly connected cable.
The nodes are running 2012 R2 Core, with latest patches (April 2015).
Firewall is disabled by Group Policy, both on servers and Domain Controller.
The Domain Controller at this site is on the local LAN.
On each future cluster node, the LAN cards can ping the Domain Controller by name and address (using -S to verify the source address). On the DC it can also ping each LAN interface, again both by name and IP. Heartbeat NICs can similarly ping each other.
Using a Management Server on a remote subnet (Domain Account, local admin of all concerned servers, except the DC, and having read/write on the target OU), the Cluster Validation Wizard fails, on one node only.
I'm getting an error message on "System Configuration\Validate Active Directory Configuration" of:
Connectivity to a writable domain controller from node DEN1NTHV02.mycorp.net could not be determined because of this error: Could not get domain controller name from machine DEN1NTHV02.
Node(s) DEN1NTHV01.mycorp.net can reach a writable domain controller.
Node(s) DEN1NTHV02.mycorp.net cannot reach a writable domain controller. Please check connectivity of these nodes to the domain controllers.
The computer accounts are in the same OU, and both are enabled and have no (seeming) other problems.
So, (1) does anyone have any idea, or (2) where can I find the verbose output text of the failed test?

Re-check your IP configuration. Ensure the only NICs with a gateway defined is the primary NIC that will be used for client access.
"a flat network for the LAN and Management on another switch. The heartbeat is connected via a directly connected cable."
Just FYI. Though a cross-over cable between the two nodes works for a two-node cluster, it is not recommended if there is even a chance of the cluster going beyond two nodes.
Secondly, from your above statement, it sounds like you have the other, non-iSCSI networks plugged into a single switch. That becomes a single point of failure.
. : | : . : | : . tim

Failed Item Validation = Process Before Headers isn't run? (APEX 2.2.0)

Hi, all,
I have an item validation that fails. When the page reloads, I see the following in the debug output:
Do not run process "P41_BEFORE_HEADER", process point=BEFORE_HEADER, condition type=, when button pressed=If that process doesn't run, a flag I used to decide whether or not to display certain Page 0 regions never gets set properly, resulting in a mess.
Is there a way around this? The only thing that I can think of is to run the same code in a failed validation that gets run in my process. Is there a more elegant way?
Thanks!

I ended up finding Page rendering process doesn't run after validation error which basically says to make a PL/SQL region with an empty template and put any display-related PL/SQL there. I set the PL/SQL region's display point to "After Header", which is before any of my other regions.
I have a bunch of P0 regions that get conditionally displayed based on session state items set in the "Before Headers" process. All of the items are cleared by an application After Footer process. I don't want to rely on the session state, however, as the user might navigate using the browser buttons on a failed submit, and that might produce odd results. Unfortunately, I've realized that the application-wide processes don't get run either.
It seems that my option is just to create a PL/SQL function
FUNCTION SHOW_REGIONS
THIS_REGION BOOLEAN := FALSE
, THAT_REGION BOOLEAN := FALSE
, THE_OTHER_REGION BOOLEAN := FALSE
and call that function from my empty PL/SQL region, passing in true values for the regions that I want to show. Either this function would set application-level items, or other functions to get the individual flags could be called from each of the Page 0 region conditional display code. I think I will do the latter, unless there is some better way.
Thanks!
Message was edited by:
Don_84
CREATE OR REPLACE PACKAGE BODY
    TEST_PAGE_0_CONDITIONS
AS
    my_flag_one BOOLEAN := FALSE;
    my_flag_two BOOLEAN := FALSE;
    PROCEDURE SET_DISPLAY_FLAGS
            FLAG_ONE BOOLEAN := FALSE,
          , FLAG_TWO BOOLEAN := FALSE
    IS
    BEGIN
        my_flag_one := FLAG_ONE;
        my_flag_two := FLAG_TWO;
    END;
    FUNCTION GET_ONE
        RETURN BOOLEAN
    IS
    BEGIN
        RETURN my_flag_one;
    END;
    FUNCTION GET_TWO
        RETURN BOOLEAN
    IS
    BEGIN
        RETURN my_flag_two;
    END;
END;

Clean Install Solaris 10 05/09 - Update Manager Fails with Valid Acct

I have a clean install of Solaris 10 05/09, and Update Manager fails to register using a valid accout which I can login with at the Sun website. Why is this happening? How can this be fixed?

Here's the output from the script....
User: root
Logname: root
Tue Oct 6 15:35:18 EDT 2009
unknown
smpatch settings:
patchpro.backout.directory - ""
patchpro.baseline.directory - /var/sadm/spool
patchpro.download.directory - /var/sadm/spool
patchpro.install.types - rebootafter:reconfigafter:standard
patchpro.patch.source - https://getupdates1.sun.com/
patchpro.patchset - current2
patchpro.proxy.host - ""
patchpro.proxy.passwd **** ****
patchpro.proxy.port - 8080
patchpro.proxy.user - ""
smpatch analyze:
Failure: Cannot connect to retrieve current2.zip: This system is currently unreg istered and is unable to retrieve patches from the Sun Update Connection. Please register your system using the Update Manager, /usr/bin/updatemanager or provid e valid Sun Online Account(SOA) credentials.
Entitlement:
cat: cannot open /var/sadm/spool/cache/entitlement/*entitlement_client
Sun UC patch revision:
120336-04
121082-06
121119-16
121454-02
123004-03
123006-07
123631-03
123896-05
123896-15
124187-07
137138-09
Solaris release:
Solaris 10 5/09 s10x_u7wos_08 X86
Copyright 2009 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 30 March 2009
Solaris Kernel: Generic_141415-10
Machine Type: i86pc
Platform: i86pc
Java versions:
System default:
java version "1.5.0_21"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_21-b01)
Java HotSpot(TM) Client VM (build 1.5.0_21-b01, mixed mode, sharing)
Java 5:
java version "1.5.0_21"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_21-b01)
Java HotSpot(TM) Client VM (build 1.5.0_21-b01, mixed mode, sharing)
Java 6:
Unable to locate JRE meeting specification "1.6*"
Java used by smpatch and updatemanager:
/usr/sbin/pprosvc:JAVACMD="/usr/jdk/latest/bin/java -version:1.5*"
/bin/updatemanager:JAVA_EXEC="/usr/jdk/latest/bin/java -version:1.5*"
Cacao Java version:
java-home=/usr/jdk/jdk1.5.0_21
Cacao Base Directories:
cacao.install.rt.base.dir=/
cacao.install.etc.base.dir=/
Software Cluster:
CLUSTER=SUNWCall
All ccr properties:
18:
Property not defined: 18
cns.assetid:
cns.br.SunUCenabled:
true
cns.ccr.keyGenPath:
/usr/lib/cc-ccr/bin/ccrKeyGen
cns.clientid:
cns.httpproxy.auth:
cns.httpproxy.ipaddr:
cns.httpproxy.port:
cns.regtoken:
cns.security.password:
cns.security.privatekey:
cns.security.publickey:
cns.swup.UMautolaunch:
false
cns.swup.autoAnalysis.enabled:
true
cns.swup.checkinInterval:
2
cns.swup.lastCheckin:
0
cns.swup.patchbaseline:
current
cns.swup.regRequired:
true
cns.transport.serverurl:
patchsvr not installed.
Sun UC package status:
SUNWbreg not installed
SUNWdc not installed
Cacao instances:
online 15:19:45 svc:/application/management/common-agent-container-1:def ault
Services in maintenance/disabled state:
svc:/application/print/server:default (LP print server)
State: disabled since Tue Oct 06 15:15:37 2009
Reason: Disabled by an administrator.
See: http://sun.com/msg/SMF-8000-05
See: man -M /usr/share/man -s 1M lpsched
Impact: 2 dependent services are not running:
svc:/application/print/rfc1179:default
svc:/application/print/ipp-listener:default
Please attach /tmp/unknown-061009-suc-out.Z in your reply to the Sun Update Conn ection Technical Support Team.
#

Crystal Reports 12 merge module fails ICE validation during installation

Hi there,
I am using the CR 2008 merge module that I downloaded from this site, and am using MSI Factory 2.0 to install my product. The ICE validation fails during the build with the following errors.
C:\v9.wxs(6680) : warning LGHT1056 : The Directory table contains a row with primary key(s) 'INSTALLDIR' which cannot be merged from the merge module 'C:\Program Files\Common Files\Merge Modules\CRRuntime_12_0.msm'. This is likely due to collision of rows with the same primary key(s) (but other different values in other columns) between the database and the merge module.
C:\v9.wxs(6680) : warning LGHT1056 : The Directory table contains a row with primary key(s) 'ProgramMenuFolder' which cannot be merged from the merge module 'C:\Program Files\Common Files\Merge Modules\CRRuntime_12_0.msm'. This is likely due to collision of rows with the same primary key(s) (but other different values in other columns) between the database and the merge module.
C:\v9.wxs(6680) : warning LGHT1056 : The Directory table contains a row with primary key(s) 'CommonAppDataFolder' which cannot be merged from the merge module 'C:\Program Files\Common Files\Merge Modules\CRRuntime_12_0.msm'. This is likely due to collision of rows with the same primary key(s) (but other different values in other columns) between the database and the merge module.
C:v9.wxs(6680) : warning LGHT1056 : The Directory table contains a row with primary key(s) 'ProgramFilesFolder' which cannot be merged from the merge module 'C:\Program Files\Common Files\Merge Modules\CRRuntime_12_0.msm'. This is likely due to collision of rows with the same primary key(s) (but other different values in other columns) between the database and the merge module.
light.exe : error LGHT0204 : ICE79: Feature 'CMS' referenced in column 'InstallExecuteSequence'.'Condition' of row 'CMSsetupConfiguration.9CED35E4_C9E6_11D3_9833_00A0C9DA4FE9' is invalid.
Any ideas what this means?
Thanks,
Rod

Hi Falk, thanks for your interest.
Yes, I can build the setup, but I need to have zero ICE validation warnings in order to pass the Vista Certification process. It seems to me that the default merge module for CR2008 has been put together in a way that fails best practice - eg. ICE validation.
The merge module is simply added to a feature within the installer product, and if I turn on the switch to "Ignore ICE warnings", then the build works OK and I can install the product no problems. However if I turn off the "Ignore ICE warnings", then the build fails and stops dead.
The snippet I posted here was from the log file.
Hope this helps,
Best regards,
Rod

Problem when attribute fails schema validation

I have got a problem during schema validation... let's say i have the following record:
<employee ssn="123456789D" recordNum="10">
<lastName>Bloggs</lastName>
<firstName>Joe</firstName>
<address>123 America Ave</address>
</employee>
apparently the attribute ssn will fail the schema, since ssn has to be all digit and length 9. Currently my schema vaildation process will keep on going to the next record if the current one fails, and write the current bad record to a error log file. the problem i have found is that if the ssn attribute validation fails, then there is no way for me to obtain the value of recordNum attribute (all elements can still be obtained).
just wondering if anyone had similar problem...
thanks

My understanding of schmemas was that once an error is found the whole document is considered invalid. Kind of like if the XML file format is bad.
If you don't mind me asking are you using DocumentBuilder to parse and is it giving you a SAXParseException?

Pop up error messages for failed custom validation

I am using jdev-10.1.3.4
My application is in ADF BC
I am writing custom validation through managed bean, I want pop-up error message for this failed validation.
My problem scenario is:
I had some list box as "status"-when this status changes to failed then the other field namely "closed date" should become madantory and also date in closed date field can't be in future.I am able to have all this validation through managed bean and also able to use af:messages through which i am able to print error message on the top of the form, but i am not able to give pop up error message for this failed validation.
I had gone thru jdev guide but there is nothing like what i am asking.
it would be of great help if someone can give me some example also.
thanks in advance.

ADF has global setting where you can configure the way messages are shown to user:
You can make this setting in adf-faces-config.xml
The <client-validation> element controls how client-side converters and validators are run.
Three values are supported:
"INLINE": validation is shown inline in a page (the default)
"ALERT": validation is shown in an Javascript alert
"DISABLED": validation is only handled on the server
IN your case, set it to 'ALERT'.

Clientdeploy fails whilst validating user

I cannot join client computers to the domain on the Server Essentials 2012 system. When ever I try, the clientdeploy wizard fails with a message that it can't find the server, just after it has collected the domain account name and password. I'm assuming
this is some configuration issue with IIS on the server, but I haven't got any handle on what it might be.
In the ClientDeploy Log, this is what I see:
[2064] 131227.171658.4208: ClientSetup: Validating User
[2064] 131227.171658.4208: ClientSetup: Call MachineIdentityManager.GetMachineStatus
[2064] 131227.171658.6611: ClientSetup: MachineIdentityManager.GetMachineStatus had errors: ErrorCatalog:NetworkError ErrorCode:-1
BaseException: Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityException: MachineIdentityManager.GetMachineStatus ---> System.ServiceModel.ProtocolException: The remote server returned an unexpected response: (405) Method Not Allowed. ---> System.Net.WebException: The remote server returned an error: (405) Method Not Allowed.
at System.Net.HttpWebRequest.GetResponse()
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
--- End of inner exception stack trace ---
Server stack trace:
at System.ServiceModel.Channels.HttpChannelUtilities.ValidateRequestReplyResponse(HttpWebRequest request, HttpWebResponse response, HttpChannelFactory`1 factory, WebException responseException, ChannelBinding channelBinding)
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.WindowsServerSolutions.Devices.Identity.ICertService.GetMachineStatus(MachineStatus& status, Boolean& isAdmin, Int32& maxClientNum, Int32& currentClientNum, String userName, String password, String machineName)
at Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityManager.GetMachineStatus(String serverName, String userName, String password, String machineName, Boolean& isAdmin)
--- End of inner exception stack trace ---
at Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityManager.GetMachineStatus(String serverName, String userName, String password, String machineName, Boolean& isAdmin)
at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ValidateUserTask.Run(WizData data)
[2064] 131227.171658.6611: ClientSetup: Exiting ValidateUserTask.Run
[2064] 131227.171658.6611: ClientSetup: Task with Id=ClientDeploy.ValidateUser has TaskStatus=Failed
[2064] 131227.171658.6611: ClientSetup: Task with Id=ClientDeploy.ValidateUser has RebootStatus=NoReboot
[2064] 131227.171658.6611: ClientSetup: Exting ConnectorWizardForm.RunTasks
[164] 131227.171658.6711: ClientSetup: JoinNetwork Tasks returned TaskStatus=Failed
[164] 131228.000408.7404: ClientSetup: Back from the Client Deployment Wizard
[164] 131228.000408.7805: ClientSetup: Saving Wizard Data
[164] 131228.000408.7805: ClientSetup: End of ClientDeploy: ErrorCode=1603
Searching the web, I can only find this error in items about people programming web services in ASP.
Can anyone help to figure out what's wrong?

Can you check the IIS log file for "WSS Certificate Web Service"
Web Application. Log files should ben the folder C:\Inetpub\Logs\LogFiles\W3SVC2.
Check for error 405.
If you are getting error 405 check for Web Handler for *.svc
You can do this by running the PowerShell command Get-WebHandler | Where-Object {$_.Path -like "*.svc"}
This should result in the following Web Handlers
Name                          Path
Verb                          Modules
svc-Integrated-4.0     *.svc                         *
ManagedPipelineHandler
svc-ISAPI-4.0_32bit   *.svc                         *
ManagedPipelineHandler
svc-ISAPI-4.0_64bit   *.svc                         *
ManagedPipelineHandler
If the command does not return any result, you need to add the Web Handler for *.svc
This post is "AS IS" and confers no rights. Mohammed Sabir [MSFT]

Bug 2.1: Export to Excel fails: no valid colums available...

Hello,
I read some threads about the error
No valid columns available for export,
we do not currently support clob or blob columnsand none of the workarounds work for me
[Create View|http://forums.oracle.com/forums/thread.jspa?messageID=3829495]: I only have a read only user without any permissions
[Scroll Count Cancel|http://forums.oracle.com/forums/thread.jspa?messageID=3829495]
[(Re)Activate Completion Insight|http://forums.oracle.com/forums/thread.jspa?messageID=3821718]
[No dblink|http://forums.oracle.com/forums/thread.jspa?messageID=3896095]
My query has only NUMBER and VARCHAR2 as results and 1200 rows.
Log says WARNING     34     10656
oracle.dbtools.raptor.dialogs.actions.TableExportAction     oracle.dbtools.parser.plsql.TabCol.getTableNodes(TabCol.java:293)The export works in 1.2, does not work in 1.5.5 (with message "WARNING     29     17954     oracle.dbtools.raptor.dialogs.actions.TableExportAction     oracle.dbtools.parser.TabCol.getTableNodes(TabCol.java:275)"
Add: I played around with the query: the export fails when the query is like
SELECT col1
      ,(SELECT something
        FROM   whatever
       ) AS col2
FROM   some_table;while the following works
SELECT col1
      ,col2
FROM   some_table;Regards
Marcus
Edited by: Marwim on 22.12.2009 15:35

Filed
Bug 9246364 - otn: export to xls is not working for a query
-Raghu

Failed Core Validation

Similar Messages

Maybe you are looking for