Going to close it. I'm not able to reproduce the problem. If you have any updates please re-open it.

Hi Gary,
I'm looking at the issue again. I wasn't able to reproduce the original problem when using FogBugz 8.7.60 with a database access.

Looking at the logs and comparing it with the code I see a strange thing - there's "Retrieving projects..." in the log but actually no projects were imported (there should be message in the log). That's really strange and that would be a cause for the error you got. If no projects were selected the import should end up exactly with the error you got.

So I wonder how is it possible no projects were selected? What browser did you use? Can you try importing again with FogBugz importer and see if it happens again when you use Firefox or Chrome?

Cheers,
Pawel

Sorry so late on reply.

I've been using 4.1.4 all along. Someone recommended importing using the Fogbugz on demand import. This is working for all our tables except our three largest resulting in the same error as posted before.

Gary

I have installed the newest FogBugz 8.7.60 for tests and I don't get any errors importing using JIM 4.1.4. Gary can you try out JIM 4.1.4?

Unfortunately when the exception happens JIM doesn't have the idea which issue is broken so we can't report it.

I guess in your case the easiest option would be to search the database (you're looking for <?xml). You can also try running the same search query importer use (FogBugz API is documented here http://fogbugz.stackexchange.com/fogbugz-xml-api), after you log in you want to issue search command, here's snippet from our code that we use to build the query:

final UriBuilder uri = UriBuilder.fromUri(apiUri)
				.queryParam("cmd", "search")
				.queryParam("q", String.format("project:=%s", projectId))
				.queryParam("cols", "ixBug,tags,fOpen,sTitle,sArea,sComputer,"
						+ "ixPersonAssignedTo,ixPersonOpenedBy,sStatus,ixPriority,sPriority,sFixFor,sVersion,sCustomerEmail,"
						+ "dtOpened,dtClosed,dtResolved,hrsOrigEst,hrsElapsed,hrsCurrEst,sCategory,events");

We have thousands of issues. How can we know which one is offending? I don't see it in the exception output.

@Gary, that's a problem with FogBugz XML output - when you have an issue that includes XML inside of the description (or comments) it will be incorrectly presented in the remote API. They do not escape or encode content served by the remote endpoint so you end up with XML content inside another XML content which breaks the parser.

The only thing you can do is to modify offending issue and change XML so it will not break the parser.

Using your recommendation it imported projects but when attempting to import issues it get's the following exception:

2012-04-19 16:08:47,997 JiraTaskExectionThread-20 ERROR admin 962x6050x1 10lrk8 192.168.1.21 /secure/admin/views/ImporterLogsPage!import.jspa [imports.importer.impl.DefaultJiraDataImporter$1Thread[http-8080-8,5,main]] Unexpected failure occurred. Importer will stop immediately. Data maybe in an unstable state
java.lang.RuntimeException: com.atlassian.jira.plugins.importer.imports.fogbugz.hosted.FogBugzRemoteException: org.jdom.input.JDOMParseException: Error on line 1: The processing instruction target matching "[xX][mM][lL]" is not allowed.
at com.atlassian.jira.plugins.importer.imports.fogbugz.hosted.FogBugzHostedDataBean.getIssuesIterator(FogBugzHostedDataBean.java:167)
at com.atlassian.jira.plugins.importer.imports.importer.impl.DefaultJiraDataImporter.importIssues(DefaultJiraDataImporter.java:683)
at com.atlassian.jira.plugins.importer.imports.importer.impl.DefaultJiraDataImporter.doImport(DefaultJiraDataImporter.java:300)
at com.atlassian.jira.plugins.importer.imports.importer.impl.ImporterCallable.call(ImporterCallable.java:25)
at com.atlassian.jira.plugins.importer.imports.importer.impl.ImporterCallable.call(ImporterCallable.java:14)
at com.atlassian.jira.task.TaskManagerImpl$TaskCallableDecorator.call(TaskManagerImpl.java:359)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at com.atlassian.multitenant.impl.DefaultMultiTenantManager.runForTenant(DefaultMultiTenantManager.java:61)
at com.atlassian.multitenant.juc.MultiTenantExecutors$WrappedRunnable.run(MultiTenantExecutors.java:160)
at com.atlassian.jira.task.ForkedThreadExecutor$ForkedRunnableDecorator.run(ForkedThreadExecutor.java:249)
at java.lang.Thread.run(Unknown Source)
Caused by: com.atlassian.jira.plugins.importer.imports.fogbugz.hosted.FogBugzRemoteException: org.jdom.input.JDOMParseException: Error on line 1: The processing instruction target matching "[xX][mM][lL]" is not allowed.
at com.atlassian.jira.plugins.importer.imports.fogbugz.hosted.FogBugzClient.getWithToken(FogBugzClient.java:225)
at com.atlassian.jira.plugins.importer.imports.fogbugz.hosted.FogBugzClient.getCases(FogBugzClient.java:275)
at com.atlassian.jira.plugins.importer.imports.fogbugz.hosted.FogBugzHostedDataBean.getIssuesIterator(FogBugzHostedDataBean.java:117)
... 14 more
Caused by: org.jdom.input.JDOMParseException: Error on line 1: The processing instruction target matching "[xX][mM][lL]" is not allowed.
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:468)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:770)
at com.atlassian.jira.plugins.importer.imports.fogbugz.hosted.FogBugzClient.getWithToken(FogBugzClient.java:218)
... 16 more
Caused by: org.xml.sax.SAXParseException: The processing instruction target matching "[xX][mM][lL]" is not allowed.
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)
at org.apache.xerces.impl.XMLScanner.scanPIData(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanPIData(Unknown Source)
at org.apache.xerces.impl.XMLScanner.scanPI(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)

Before we release 4.2 which should have the fix for this issue, as Pawel suggested try out our OnDemand importer which actually works without any issues with self-hosted FogBugz instances too (provided that the access to their remote API is unrestricted from JIRA).

Please try FogBugz OnDemand importer. It should work with your instance. The only thing you'll miss we'll be links.