nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Error and XML file . . .help needed

unknown

I'm hoping someone who knows XML can help: can someone decifer the error:

"An error occurred:

javax.xml.bind.UnmarshalException

- with linked exception:

[org.xml.sax.SAXParseException; LineNumber: 353; columnNumber:34; cvc-complex-type.2.4.a: Invalid content was found starting with element 'allProjects'. One of '{context, applicableIssueType, customeFieldConfiguration, config}' is expected.] "

It appears to say 2 different things to me

1) a '{context, applicacableIssueType, customeFIeldConfiguration, config}' is expected - i.e., it's missing OR 2) possibly the date format is incorrect . . . .

here's the section from the XML file the error refers to - line 353 column 34-37 is bold

<customField>
<type>com.atlassian.jira.plugin.system.customfieldtypes:datepicker</type>
<name>Date Found</name>
<description>Date that the problem or observation was found</description>
<searchTemplate>com.atlassian.jira.plugin.system.customfieldtypes:daterange</searchTemplate>
<customFieldConfigScheme>
<name>Default Configuration Scheme for Date Found</name>
<description>Default configuration scheme generated by JIRA</description>
<allProjects>true</allProjects>

<applicableIssueType><issueType>Bug</issueType>
<customFieldConfiguration>Default Configuration for Date Found</customFieldConfiguration>
</applicableIssueType>

THERE WERE MULTIPLE <applicableIssueType> </applicableIssueType> blocks all saying the same thing but with different IssueTypes

<config>
<name>Default Configuration for Date Found</name>
<description>Default configuration generated by Jira</description>
<defaultValue>
<singularValue>18/Jul/19</singularValue>
</defaultValue>
</config>
</customFieldConfigScheme>
</customField>

Accepted answers

unknown

@[deleted]you need to ensure that the Project Configurator versions match on both the export and import servers. I found that the export (3.0.4) and the import (3.0) was causing this issue, so upgraded the import server to 3.0.4 and it worked

All comments

Thomas Deiler_db00h3

Dear @[deleted],

I have read your post twice to figure out what you plan to do with this XML - I failed. Can you please tell us what you wanna do with this XML and where/when this exception is thrown?

So long

Thomas

unknown

Hi Thomas,

What happened is they were trying to do an import into JIRA whe they got the error mentioned above which referenced the XML file.

That's all I know, unfortunately. I asked specifically how and when the error was generated but was only told the information I just relayed to you.

Jim

Thomas Deiler_db00h3

Dear @[deleted],

I cannot recommend to fix the DB dump manually - even if it is readable as XML, until you exactly know what you do.

Is the Jira version, where you try to import, the same with which the dump was created?

So long

Thomas

unknown

Hi THomas.

Yes, they were the same versions.

You can forget about my question for now. An import was occuring, an error was enountered that referenced the XML file. To me, it seems clear what they were trying to do - an import.

I'm unable at this time to provide any other details - let's drop it for now.

Thank you for your help.

Jim

unknown

Thank You.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server

java

error