XDSDocumentEntry exists in metadata with no corresponding attached document

Mar 11, 2008 at 1:58 PM
I'm having problems in general with setting up the system on a single laptop. There seems to have been secure connection configuration information in the app.config file. I removed that and also adjusted the port numbers to have them all be 8080 for the repository and 18080 for the registry. That seemed to work without any errors or port conflicts. On the first test I'm getting the following error. I'm using 15270 release and have tried the 15690 test documents - both throwing the same exception.

Any ideas?

<tns:RegistryResponse status="urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Failure" xmlns:tns="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0" xmlns:rim="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0"><tns:RegistryErrorList highestSeverity=""><tns:RegistryError codeContext="XDSDocumentEntry exists in metadata with no corresponding attached document" errorCode="XDSMissingDocumentAttachment" severity="urn:oasis:names:tc:ebxml-regrep:ErrorSeverityType:Error" /></tns:RegistryErrorList></tns:RegistryResponse>
Developer
Mar 11, 2008 at 10:00 PM
Hi Carruda,

Which transaction did you run to get this error?

Cheers, Wagner.


carruda wrote:
I'm having problems in general with setting up the system on a single laptop. There seems to have been secure connection configuration information in the app.config file. I removed that and also adjusted the port numbers to have them all be 8080 for the repository and 18080 for the registry. That seemed to work without any errors or port conflicts. On the first test I'm getting the following error. I'm using 15270 release and have tried the 15690 test documents - both throwing the same exception.

Any ideas?

<tns:RegistryResponse status="urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Failure" xmlns:tns="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0" xmlns:rim="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0"><tns:RegistryErrorList highestSeverity=""><tns:RegistryError codeContext="XDSDocumentEntry exists in metadata with no corresponding attached document" errorCode="XDSMissingDocumentAttachment" severity="urn:oasis:names:tc:ebxml-regrep:ErrorSeverityType:Error" /></tns:RegistryErrorList></tns:RegistryResponse>

Mar 12, 2008 at 1:15 PM
Hi carruda,

Are you running Provide and Register using the Test Harness in the latest release? There was a bug that was fixed on Feb 15, it was trying to give the same ID to both documents. If you try getting the latest out of the repository, I think your problem will go away.

Darcy


carruda wrote:
I'm having problems in general with setting up the system on a single laptop. There seems to have been secure connection configuration information in the app.config file. I removed that and also adjusted the port numbers to have them all be 8080 for the repository and 18080 for the registry. That seemed to work without any errors or port conflicts. On the first test I'm getting the following error. I'm using 15270 release and have tried the 15690 test documents - both throwing the same exception.

Any ideas?

<tns:RegistryResponse status="urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Failure" xmlns:tns="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0" xmlns:rim="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0"><tns:RegistryErrorList highestSeverity=""><tns:RegistryError codeContext="XDSDocumentEntry exists in metadata with no corresponding attached document" errorCode="XDSMissingDocumentAttachment" severity="urn:oasis:names:tc:ebxml-regrep:ErrorSeverityType:Error" /></tns:RegistryErrorList></tns:RegistryResponse>

Mar 13, 2008 at 2:55 PM
I got the latest build and finally fixed the communications issues with the services. When I try "Provide and Register Document Set" and "Register Document Set", I receive the following message. I'm using the following PatientID = "urn:uuid::ae94516f-570c-41ba-ae95-26ae76e50d45" which was provided in the documentation.

<tns:RegistryResponse status="urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Failure" xmlns:tns="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0" xmlns:rim="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0"><tns:RegistryErrorList highestSeverity=""><tns:RegistryError codeContext="Patient ID referenced in metadata is not known to the Registry actor via the Patient Identity Feed or is unknown because of patient identifier merge. The codeContext shall include the value of patient ID in question." errorCode="XDSUnknownPatientId" severity="urn:oasis:names:tc:ebxml-regrep:ErrorSeverityType:Error" /></tns:RegistryErrorList></tns:RegistryResponse>
Mar 13, 2008 at 3:41 PM
I think that part of the documentation is out of date. Try using opening the patient table in the XdsRegistryDB and using one of the entries that the registry knows about e.g. 498ef443e7ac4a6^^^&1.3.6.1.4.1.21367.2005.3.7&ISO

Darcy


carruda wrote:
I got the latest build and finally fixed the communications issues with the services. When I try "Provide and Register Document Set" and "Register Document Set", I receive the following message. I'm using the following PatientID = "urn:uuid::ae94516f-570c-41ba-ae95-26ae76e50d45" which was provided in the documentation.

<tns:RegistryResponse status="urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Failure" xmlns:tns="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0" xmlns:rim="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0"><tns:RegistryErrorList highestSeverity=""><tns:RegistryError codeContext="Patient ID referenced in metadata is not known to the Registry actor via the Patient Identity Feed or is unknown because of patient identifier merge. The codeContext shall include the value of patient ID in question." errorCode="XDSUnknownPatientId" severity="urn:oasis:names:tc:ebxml-regrep:ErrorSeverityType:Error" /></tns:RegistryErrorList></tns:RegistryResponse>

Mar 13, 2008 at 3:55 PM
I deleted my databases and recreated them with the database scripts from the 15690 source release. Then I tried "urn:uuid::ae94516f-570c-41ba-ae95-26ae76e50d45" again - same result. Then cut/pasted every patientuuid from the database table and the test still failed. Here are the patientid pk's and uuid's in the registry database:

4 498ef443e7ac4a6^^^&1.3.6.1.4.1.21367.2005.3.7&ISO
5 e21007e556864ca^^^&1.3.6.1.4.1.21367.2005.3.7&ISO
6 284c2500d0e949c^^^&1.3.6.1.4.1.21367.2005.3.7&ISO
7 abfb47b943d9426^^^&1.3.6.1.4.1.21367.2005.3.7&ISO
8 1.2.840.114350.1.13.99998.8734^^^34827G409
9 61d26732db0f474^^^&1.3.6.1.4.1.21367.2005.3.7&ISO
10 8fe78ac84449423^^^&1.3.6.1.4.1.21367.2005.3.7&ISO
Mar 13, 2008 at 4:01 PM
I believe there is another issue with patientIDs in that you need to close the program and re-open it before you can change the patient ID. Try closing the test harness and re-opening it, and then using 498ef443e7ac4a6^^^&1.3.6.1.4.1.21367.2005.3.7&ISO as your patientID.

The test harness replaces something like '$patiendID$' to the patient id that you enter. If you subsequently enter a new patient ID, it tries to replace $patientID$ with the new ID that you have entered, only $patientID$ no longer exists, because it was already replaced to your first patient ID.

If closing and re-opening doesn't work for you, then I am out of ideas on this one.

Darcy


carruda wrote:
I deleted my databases and recreated them with the database scripts from the 15690 source release. Then I tried "urn:uuid::ae94516f-570c-41ba-ae95-26ae76e50d45" again - same result. Then cut/pasted every patientuuid from the database table and the test still failed. Here are the patientid pk's and uuid's in the registry database:

4 498ef443e7ac4a6^^^&1.3.6.1.4.1.21367.2005.3.7&ISO
5 e21007e556864ca^^^&1.3.6.1.4.1.21367.2005.3.7&ISO
6 284c2500d0e949c^^^&1.3.6.1.4.1.21367.2005.3.7&ISO
7 abfb47b943d9426^^^&1.3.6.1.4.1.21367.2005.3.7&ISO
8 1.2.840.114350.1.13.99998.8734^^^34827G409
9 61d26732db0f474^^^&1.3.6.1.4.1.21367.2005.3.7&ISO
10 8fe78ac84449423^^^&1.3.6.1.4.1.21367.2005.3.7&ISO

Mar 13, 2008 at 4:13 PM
Actually, if the above doesn't work, I may recognize the error if you post the message. There was one other thing I had to change relating to the message version of the response I think, I eventually got provide and register to work though...

Good luck


e9p1 wrote:
I believe there is another issue with patientIDs in that you need to close the program and re-open it before you can change the patient ID. Try closing the test harness and re-opening it, and then using 498ef443e7ac4a6^^^&1.3.6.1.4.1.21367.2005.3.7&ISO as your patientID.

The test harness replaces something like '$patiendID$' to the patient id that you enter. If you subsequently enter a new patient ID, it tries to replace $patientID$ with the new ID that you have entered, only $patientID$ no longer exists, because it was already replaced to your first patient ID.

If closing and re-opening doesn't work for you, then I am out of ideas on this one.

Darcy


carruda wrote:
I deleted my databases and recreated them with the database scripts from the 15690 source release. Then I tried "urn:uuid::ae94516f-570c-41ba-ae95-26ae76e50d45" again - same result. Then cut/pasted every patientuuid from the database table and the test still failed. Here are the patientid pk's and uuid's in the registry database:

4 498ef443e7ac4a6^^^&1.3.6.1.4.1.21367.2005.3.7&ISO
5 e21007e556864ca^^^&1.3.6.1.4.1.21367.2005.3.7&ISO
6 284c2500d0e949c^^^&1.3.6.1.4.1.21367.2005.3.7&ISO
7 abfb47b943d9426^^^&1.3.6.1.4.1.21367.2005.3.7&ISO
8 1.2.840.114350.1.13.99998.8734^^^34827G409
9 61d26732db0f474^^^&1.3.6.1.4.1.21367.2005.3.7&ISO
10 8fe78ac84449423^^^&1.3.6.1.4.1.21367.2005.3.7&ISO


Mar 13, 2008 at 4:57 PM
That did the trick! All tests are passing perfectly. Also my source was completely convert to VS2008 and 3.5 framework. The big thing that helped me was to replace all the .map files with an "Add Service Reference" to the Registry and Repository - that made it easier to configure because the Repository couldn't connect to the Registry properly.

Thanks again for your help.

-Charlie