Bugzilla Import fails
Trying to retire our Bugzilla server in favor of our shiny new RTC 1.0.1
repository.
Using RTC 1.0.1 client, when I try to use the Bugzilla Importer, I get a
dialog box that says:
Unexpected content, please check Bugzilla URL and authentication.
The declaration for the entity "HTML.Version" must end with '>'.
The Bugzilla URL and credentials are correct.
I've found Defect 29839 that seems to be a direct hit on this symptom
but I'm not sure whether its been fixed or is still open.
Can someone suggest a way to workaround this problem .. or perhaps
there's a another way I can get a 1000 or so Bugzilla reports into RTC ?
Any help appreciated
Cheers
repository.
Using RTC 1.0.1 client, when I try to use the Bugzilla Importer, I get a
dialog box that says:
Unexpected content, please check Bugzilla URL and authentication.
The declaration for the entity "HTML.Version" must end with '>'.
The Bugzilla URL and credentials are correct.
I've found Defect 29839 that seems to be a direct hit on this symptom
but I'm not sure whether its been fixed or is still open.
Can someone suggest a way to workaround this problem .. or perhaps
there's a another way I can get a 1000 or so Bugzilla reports into RTC ?
Any help appreciated
Cheers
5 answers
The Bugzilla URL and credentials are correct.
I've found Defect 29839 that seems to be a direct hit on this symptom
but I'm not sure whether its been fixed or is still open.
Defect 29839 is resolved, but defect 56559 is still open. I suspect
that the Bugzilla URL you entered is not using the format that the
importer expects. Could you post it here? Maybe we can spot the problem.
Regards,
Patrick
Jazz Work Item Team
The URL that I gave the Importer was same URL that we use in our Web
browsers:
http://godel/bugs
BTW: We use Bugzilla 2.22.2 running on Linux
Patrick Streule wrote:
browsers:
http://godel/bugs
BTW: We use Bugzilla 2.22.2 running on Linux
Patrick Streule wrote:
The Bugzilla URL and credentials are correct.
I've found Defect 29839 that seems to be a direct hit on this symptom
but I'm not sure whether its been fixed or is still open.
Defect 29839 is resolved, but defect 56559 is still open. I suspect that
the Bugzilla URL you entered is not using the format that the importer
expects. Could you post it here? Maybe we can spot the problem.
Regards,
Patrick
Jazz Work Item Team
Is there something unusual about our Bugzilla server ?
Or does the RTC Bugzilla Importer have problems ?
David Ward wrote:
Or does the RTC Bugzilla Importer have problems ?
David Ward wrote:
The URL that I gave the Importer was same URL that we use in our Web
browsers:
http://godel/bugs
BTW: We use Bugzilla 2.22.2 running on Linux
Patrick Streule wrote:
The Bugzilla URL and credentials are correct.
I've found Defect 29839 that seems to be a direct hit on this symptom
but I'm not sure whether its been fixed or is still open.
Defect 29839 is resolved, but defect 56559 is still open. I suspect
that the Bugzilla URL you entered is not using the format that the
importer expects. Could you post it here? Maybe we can spot the problem.
Regards,
Patrick
Jazz Work Item Team
Is there something unusual about our Bugzilla server ?
Or does the RTC Bugzilla Importer have problems ?
Have you checked the error log? Is there anything logged when the
import fails? Did you try the fully qualified host name, too, with the
same problem?
Otherwise, please open a work item for this issue so we can track it better.
Regards,
Patrick
Jazz Work Item Team
OK I fixed this problem by changing the authentication from Basic HTTP
to "Use Cookies". Its not clear to me why this fixes it.
The reporting of the error seems to be main difficulty here.
Thnaks
Dave
Patrick Streule wrote:
to "Use Cookies". Its not clear to me why this fixes it.
The reporting of the error seems to be main difficulty here.
Thnaks
Dave
Patrick Streule wrote:
Is there something unusual about our Bugzilla server ?
Or does the RTC Bugzilla Importer have problems ?
Have you checked the error log? Is there anything logged when the import
fails? Did you try the fully qualified host name, too, with the same
problem?
Otherwise, please open a work item for this issue so we can track it
better.
Regards,
Patrick
Jazz Work Item Team