Dell PowerVault TL4000 Dell PowerVault ML6000 Encryption Key Manager User's - Page 99

Edit the Encryption Key Manager metadata file., </keyAlias1&gt

Get Dell PowerVault TL4000 PDF manuals and user guides View all Dell PowerVault TL4000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 99 highlights

[Fatal Error] EKMData.xml:290:16: The end-tag for element type "KeyUsageEvent" must end with a '>' delimiter. org.xml.sax.SAXParseException: The end-tag for element type "KeyUsageEvent" must end with a '>' delimiter. at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at javax.xml.parsers.DocumentBuilder.parse(Unknown Source) at com.ibm.keymanager.tools.EKMDataParser.a(EKMDataParser.java:136) at com.ibm.keymanager.tools.EKMDataParser.a(EKMDataParser.java:26) at com.ibm.keymanager.tools.EKMDataParser.main(EKMDataParser.java:93) If this error occurs, it is due to a missing XML ending tag for an element. The Encryption Key Manager metadata file can be recovered to allow the EKMDataParser to parse the file again. 1. Make a backup copy of the Encryption Key Manager metadata file. 2. Edit the Encryption Key Manager metadata file. 3. In XML, there is should be an initial tag and a corresponding ending tag for each piece of data or event. v Some examples of an initial tag: - - - v Some examples of an ending tag: - - - 4. Scan the file and look for unmatched tags. The error message from the EKMDataParser lists which tag is missing its ending tag. This should make the search somewhat easier. 5. When an unmatched tag is found, temporarily delete the event or add the necessary tags to complete the event. v For example, the following excerpt from a Encryption Key Manager metadata file shows a first KeyUsageEvent that has no ending tag: 001310000109 5005076312418B07 key00000000000000000F 6B657900000000000000000F Thu Aug 30 09:50:53 MDT 2007 001310000100 5005076312418ABB key000000000000000000 6B6579000000000000000000 Thu Sep 06 16:49:39 MDT 2007 Adding a between the lines Thu Aug 30 09:50:53 MDT 2007 and would complete the first . Repairing the file corruption will allow the EKMDataParser to successfully parse the data. Chapter 8. Using Metadata 8-3

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
[Fatal Error] EKMData.xml:290:16: The end-tag for element type "KeyUsageEvent" must
end with a '>' delimiter.
org.xml.sax.SAXParseException: The end-tag for element type "KeyUsageEvent" must
end with a '>' delimiter.
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
at com.ibm.keymanager.tools.EKMDataParser.a(EKMDataParser.java:136)
at com.ibm.keymanager.tools.EKMDataParser.a(EKMDataParser.java:26)
at com.ibm.keymanager.tools.EKMDataParser.main(EKMDataParser.java:93)
If this error occurs, it is due to a missing XML ending tag for an element. The
Encryption Key Manager metadata file can be recovered to allow the
EKMDataParser to parse the file again.
1.
Make a backup copy of the Encryption Key Manager metadata file.
2.
Edit the Encryption Key Manager metadata file.
3.
In XML, there is should be an initial tag and a corresponding ending tag for
each piece of data or event.
v
Some examples of an initial tag:
–
<KeyUsageEvent>
–
<driveSSN>
–
<keyAlias1>
v
Some examples of an ending tag:
–
</KeyUsageEvent>
–
</driveSSN>
–
</keyAlias1>
4.
Scan the file and look for unmatched tags. The error message from the
EKMDataParser lists which tag is missing its ending tag. This should make the
search somewhat easier.
5.
When an unmatched tag is found, temporarily delete the event or add the
necessary tags to complete the event.
v
For example, the following excerpt from a Encryption Key Manager metadata
file shows a first KeyUsageEvent that has no ending tag:
<KeyUsageEvent>
<driveSSN>001310000109</driveSSN>
<volSer>
</volSer>
<driveWWN>5005076312418B07</driveWWN>
<keyAlias1>key00000000000000000F</keyAlias1>
<dki>6B657900000000000000000F</dki>
<dateTime>Thu Aug 30 09:50:53 MDT 2007</dateTime>
<KeyUsageEvent>
<driveSSN>001310000100</driveSSN>
<volSer>
</volSer>
<driveWWN>5005076312418ABB</driveWWN>
<keyAlias1>key000000000000000000</keyAlias1>
<dki>6B6579000000000000000000</dki>
<dateTime>Thu Sep 06 16:49:39 MDT 2007</dateTime>
</KeyUsageEvent>
Adding a </KeyUsageEvent> between the lines <dateTime>Thu Aug 30
09:50:53 MDT 2007</dateTime> and <KeyUsageEvent> would complete the
first <KeyUsageEvent>.
Repairing the file corruption will allow the EKMDataParser to successfully parse
the data.
Chapter 8. Using Metadata
8-3