Error at central server running 1.5 when processing remoteformentry

[Wachira, Eric]

Some javascript/style in this post has been disabled (why?)

Hi,

We are testing 1.5 with remoteformentry 2.7 and are getting errors after processing the forms at central. At remote, a patient is created and encounter form filled. For an existing patient a encounter form is also filled out. At remote, the zip file to export to central is generated ok and upon import at central we get the "Import successful message". However, no encounter appears in the patient dahsboard for the existing patient and the new patient is also not found from the Find Patient window.

The forms end up in the error queue and when you try to resolve the errors using the Resolve Error Queue link the system throws an error. We have the Tribe-1.4 module installed at both central and remote server.

Attached is the tomcat log.

Kindly adivce.

-Eric



++ DISCLAIMER ++
This email, any attachment and response string are confidential and may be legally privileged. Any opinions expressed in this mail do not necessarily reflect the opinions of Research Care Training Program (RCTP) or it's afilliate projects.If you are not the addressee, or have received this e-mail in error, please notify the sender immediately, delete it from your system and do not copy, disclose or otherwise act upon any part of this e-mail or its attachments.Internet communications are not secure and therefore RCTP does not accept legal responsibility for the contents of this message as it has been transmitted over a public network.Any opinion or other information in this e-mail or its attachments that does not relate to the business of the RCTP family is personal to the sender and is not given or endorsed by RCTP.
________________________________________

---

[hidden email] from OpenMRS Implementers' mailing list
EERROR - RemoteFormEntryPendingProcessor.processRemoteFormEntryPendingQueue(180) |2009-10-29 13:36:06,406| Error while parsing remoteformentry pending queue (null)
org.openmrs.api.APIException: The Tribe object is no longer supported.  Install the Tribe module
        at org.openmrs.Tribe.<init>(Tribe.java:54)
        at org.openmrs.module.remoteformentry.RemoteFormEntryUtil.setPatientProperties(RemoteFormEntryUtil.java:541)
        at org.openmrs.module.remoteformentry.impl.RemoteFormEntryServiceImpl.updatePatientInDatabase(RemoteFormEntryServiceImpl.java:381)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
        at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
        at $Proxy115.updatePatientInDatabase(Unknown Source)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
        at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
        at org.springframework.aop.framework.adapter.MethodBeforeAdviceInterceptor.invoke(MethodBeforeAdviceInterceptor.java:50)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
        at $Proxy116.updatePatientInDatabase(Unknown Source)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
        at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
        at $Proxy116.updatePatientInDatabase(Unknown Source)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:198)
        at $Proxy115.updatePatientInDatabase(Unknown Source)
        at org.openmrs.module.remoteformentry.RemoteFormEntryPendingProcessor.processRemoteFormEntryPendingQueue(RemoteFormEntryPendingProcessor.java:165)
        at org.openmrs.module.remoteformentry.RemoteFormEntryPendingProcessor.processNextRemoteFormEntryPendingQueue(RemoteFormEntryPendingProcessor.java:204)
        at org.openmrs.module.remoteformentry.RemoteFormEntryPendingProcessor.processRemoteFormEntryPendingQueue(RemoteFormEntryPendingProcessor.java:274)
        at org.openmrs.module.remoteformentry.ProcessPendingQueueItemsTask.execute(ProcessPendingQueueItemsTask.java:43)
        at org.openmrs.scheduler.tasks.TaskThreadedInitializationWrapper.execute(TaskThreadedInitializationWrapper.java:72)
        at org.openmrs.scheduler.timer.TimerSchedulerTask.run(TimerSchedulerTask.java:44)
        at java.util.TimerThread.mainLoop(Unknown Source)
        at java.util.TimerThread.run(Unknown Source)
ERROR - RemoteFormEntryPendingProcessor.processRemoteFormEntryPendingQueue(180) |2009-10-29 13:36:06,468| Error while parsing remoteformentry pending queue (null)
java.lang.NullPointerException
        at org.openmrs.module.remoteformentry.RemoteFormEntryUtil.getPatientIdentifiers(RemoteFormEntryUtil.java:357)
        at org.openmrs.module.remoteformentry.RemoteFormEntryPendingProcessor.processRemoteFormEntryPendingQueue(RemoteFormEntryPendingProcessor.java:104)
        at org.openmrs.module.remoteformentry.RemoteFormEntryPendingProcessor.processNextRemoteFormEntryPendingQueue(RemoteFormEntryPendingProcessor.java:204)
        at org.openmrs.module.remoteformentry.RemoteFormEntryPendingProcessor.processRemoteFormEntryPendingQueue(RemoteFormEntryPendingProcessor.java:274)
        at org.openmrs.module.remoteformentry.ProcessPendingQueueItemsTask.execute(ProcessPendingQueueItemsTask.java:43)
        at org.openmrs.scheduler.tasks.TaskThreadedInitializationWrapper.execute(TaskThreadedInitializationWrapper.java:72)
        at org.openmrs.scheduler.timer.TimerSchedulerTask.run(TimerSchedulerTask.java:44)
        at java.util.TimerThread.mainLoop(Unknown Source)
        at java.util.TimerThread.run(Unknown Source)
INFO - LoggingAdvice.invoke(102) |2009-10-29 13:37:33,203| In method AdministrationService.addGlobalPropertyListener. Arguments: GlobalPropertyListener=org.openmrs.order.DrugOrderSupport@66da81,
INFO - LoggingAdvice.invoke(127) |2009-10-29 13:37:33,218| Exiting method addGlobalPropertyListener
DEBUG - Extension.initialize(71) |2009-10-29 13:38:02,390| Initializing extension for point: org.openmrs.admin.list
DEBUG - Extension.initialize(71) |2009-10-29 13:38:02,390| Initializing extension for point: org.openmrs.admin.list
INFO - LoggingAdvice.invoke(102) |2009-10-29 13:38:06,718| In method PersonService.deletePersonAttributeType. Arguments: Integer=8,
INFO - LoggingAdvice.invoke(102) |2009-10-29 13:38:06,718| In method PersonService.deletePersonAttributeType. Arguments: PersonAttributeType=Tribe,
INFO - LoggingAdvice.invoke(127) |2009-10-29 13:38:06,718| Exiting method deletePersonAttributeType
INFO - LoggingAdvice.invoke(127) |2009-10-29 13:38:06,718| Exiting method deletePersonAttributeTypeERROR - RemoteFormEntryPendingProcessor.processRemoteFormEntryPendingQueue(180) |2009-10-29 13:54:30,140| Error while parsing remoteformentry pending queue (null)
java.lang.NullPointerException
        at org.openmrs.module.remoteformentry.RemoteFormEntryUtil.getPatientIdentifiers(RemoteFormEntryUtil.java:357)
        at org.openmrs.module.remoteformentry.RemoteFormEntryPendingProcessor.processRemoteFormEntryPendingQueue(RemoteFormEntryPendingProcessor.java:104)
        at org.openmrs.module.remoteformentry.RemoteFormEntryPendingProcessor.processNextRemoteFormEntryPendingQueue(RemoteFormEntryPendingProcessor.java:204)
        at org.openmrs.module.remoteformentry.RemoteFormEntryPendingProcessor.processRemoteFormEntryPendingQueue(RemoteFormEntryPendingProcessor.java:274)
        at org.openmrs.module.remoteformentry.ProcessPendingQueueItemsTask.execute(ProcessPendingQueueItemsTask.java:43)
        at org.openmrs.scheduler.tasks.TaskThreadedInitializationWrapper.execute(TaskThreadedInitializationWrapper.java:72)
        at org.openmrs.scheduler.timer.TimerSchedulerTask.run(TimerSchedulerTask.java:44)
        at java.util.TimerThread.mainLoop(Unknown Source)
        at java.util.TimerThread.run(Unknown Source)
ERROR - RemoteFormEntryPendingProcessor.processRemoteFormEntryPendingQueue(180) |2009-10-29 13:54:30,187| Error while parsing remoteformentry pending queue (null)
java.lang.NullPointerException
        at org.openmrs.module.remoteformentry.RemoteFormEntryUtil.getPatientIdentifiers(RemoteFormEntryUtil.java:357)
        at org.openmrs.module.remoteformentry.RemoteFormEntryPendingProcessor.processRemoteFormEntryPendingQueue(RemoteFormEntryPendingProcessor.java:104)
        at org.openmrs.module.remoteformentry.RemoteFormEntryPendingProcessor.processNextRemoteFormEntryPendingQueue(RemoteFormEntryPendingProcessor.java:204)
        at org.openmrs.module.remoteformentry.RemoteFormEntryPendingProcessor.processRemoteFormEntryPendingQueue(RemoteFormEntryPendingProcessor.java:274)
        at org.openmrs.module.remoteformentry.ProcessPendingQueueItemsTask.execute(ProcessPendingQueueItemsTask.java:43)
        at org.openmrs.scheduler.tasks.TaskThreadedInitializationWrapper.execute(TaskThreadedInitializationWrapper.java:72)
        at org.openmrs.scheduler.timer.TimerSchedulerTask.run(TimerSchedulerTask.java:44)
        at java.util.TimerThread.mainLoop(Unknown Source)
        at java.util.TimerThread.run(Unknown Source)
DEBUG - Extension.initialize(71) |2009-10-29 13:54:32,140| Initializing extension for point: org.openmrs.admin.list
DEBUG - Extension.initialize(71) |2009-10-29 13:54:32,140| Initializing extension for point: org.openmrs.admin.list
INFO - TribeListController.formBackingObject(126) |2009-10-29 13:54:34,593| formBackingObject
INFO - TribeListController.initBinder(52) |2009-10-29 13:54:34,609| initBinder
ERROR - RemoteFormEntryPendingProcessor.processRemoteFormEntryPendingQueue(180) |2009-10-29 13:54:35,265| Error while parsing remoteformentry pending queue (null)
org.openmrs.api.APIException: The voided bit was set to true, so a void reason is required at save time for object: Kisii of class: class org.openmrs.PersonAttribute
        at org.openmrs.api.handler.VoidSaveHandler.handle(VoidSaveHandler.java:77)
        at org.openmrs.api.handler.VoidSaveHandler.handle(VoidSaveHandler.java:46)
        at org.openmrs.aop.RequiredDataAdvice.recursivelyHandle(RequiredDataAdvice.java:215)
        at org.openmrs.aop.RequiredDataAdvice.recursivelyHandle(RequiredDataAdvice.java:232)
        at org.openmrs.aop.RequiredDataAdvice.recursivelyHandle(RequiredDataAdvice.java:178)
        at org.openmrs.aop.RequiredDataAdvice.before(RequiredDataAdvice.java:128)
        at org.springframework.aop.framework.adapter.MethodBeforeAdviceInterceptor.invoke(MethodBeforeAdviceInterceptor.java:49)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
        at org.springframework.aop.framework.adapter.MethodBeforeAdviceInterceptor.invoke(MethodBeforeAdviceInterceptor.java:50)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
        at $Proxy67.savePatient(Unknown Source)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
        at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
        at $Proxy67.savePatient(Unknown Source)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:198)
        at $Proxy133.savePatient(Unknown Source)
        at org.openmrs.module.remoteformentry.impl.RemoteFormEntryServiceImpl.updatePatientInDatabase(RemoteFormEntryServiceImpl.java:384)
        at sun.reflect.GeneratedMethodAccessor475.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
        at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
        at $Proxy115.updatePatientInDatabase(Unknown Source)
        at sun.reflect.GeneratedMethodAccessor475.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
        at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
        at org.springframework.aop.framework.adapter.MethodBeforeAdviceInterceptor.invoke(MethodBeforeAdviceInterceptor.java:50)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
        at $Proxy116.updatePatientInDatabase(Unknown Source)
        at sun.reflect.GeneratedMethodAccessor475.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
        at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
        at $Proxy116.updatePatientInDatabase(Unknown Source)
        at sun.reflect.GeneratedMethodAccessor475.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:198)
        at $Proxy115.updatePatientInDatabase(Unknown Source)
        at org.openmrs.module.remoteformentry.RemoteFormEntryPendingProcessor.processRemoteFormEntryPendingQueue(RemoteFormEntryPendingProcessor.java:165)
        at org.openmrs.module.remoteformentry.RemoteFormEntryPendingProcessor.processNextRemoteFormEntryPendingQueue(RemoteFormEntryPendingProcessor.java:204)
        at org.openmrs.module.remoteformentry.RemoteFormEntryPendingProcessor.processRemoteFormEntryPendingQueue(RemoteFormEntryPendingProcessor.java:274)
        at org.openmrs.module.remoteformentry.ProcessPendingQueueItemsTask.execute(ProcessPendingQueueItemsTask.java:43)
        at org.openmrs.scheduler.tasks.TaskThreadedInitializationWrapper.execute(TaskThreadedInitializationWrapper.java:72)
        at org.openmrs.scheduler.timer.TimerSchedulerTask.run(TimerSchedulerTask.java:44)
        at java.util.TimerThread.mainLoop(Unknown Source)
        at java.util.TimerThread.run(Unknown Source)

[Ben Wolfe]

Some javascript/style in this post has been disabled (why?)

Ah yes, thats a bug that needs fixed in the module.  Can you create a ticket for that?

Wachira, Eric wrote:

Hi,

We are testing 1.5 with remoteformentry 2.7 and are getting errors after processing the forms at central. At remote, a patient is created and encounter form filled. For an existing patient a encounter form is also filled out. At remote, the zip file to export to central is generated ok and upon import at central we get the "Import successful message". However, no encounter appears in the patient dahsboard for the existing patient and the new patient is also not found from the Find Patient window.

The forms end up in the error queue and when you try to resolve the errors using the Resolve Error Queue link the system throws an error. We have the Tribe-1.4 module installed at both central and remote server.

Attached is the tomcat log.

Kindly adivce.

-Eric



++ DISCLAIMER ++
This email, any attachment and response string are confidential and may be legally privileged. Any opinions expressed in this mail do not necessarily reflect the opinions of Research Care Training Program (RCTP) or it's afilliate projects.If you are not the addressee, or have received this e-mail in error, please notify the sender immediately, delete it from your system and do not copy, disclose or otherwise act upon any part of this e-mail or its attachments.Internet communications are not secure and therefore RCTP does not accept legal responsibility for the contents of this message as it has been transmitted over a public network.Any opinion or other information in this e-mail or its attachments that does not relate to the business of the RCTP family is personal to the sender and is not given or endorsed by RCTP.
________________________________________

---

[hidden email] from OpenMRS Implementers' mailing list

---

[hidden email] from OpenMRS Implementers' mailing list

[Wachira, Eric]

Some javascript/style in this post has been disabled (why?)

Thanks Ben. The ticket is no. 1913

-Eric


Ben Wolfe wrote:

Ah yes, thats a bug that needs fixed in the module.  Can you create a ticket for that?

Wachira, Eric wrote:

Hi,

We are testing 1.5 with remoteformentry 2.7 and are getting errors after processing the forms at central. At remote, a patient is created and encounter form filled. For an existing patient a encounter form is also filled out. At remote, the zip file to export to central is generated ok and upon import at central we get the "Import successful message". However, no encounter appears in the patient dahsboard for the existing patient and the new patient is also not found from the Find Patient window.

The forms end up in the error queue and when you try to resolve the errors using the Resolve Error Queue link the system throws an error. We have the Tribe-1.4 module installed at both central and remote server.

Attached is the tomcat log.

Kindly adivce.

-Eric



++ DISCLAIMER ++
This email, any attachment and response string are confidential and may be legally privileged. Any opinions expressed in this mail do not necessarily reflect the opinions of Research Care Training Program (RCTP) or it's afilliate projects.If you are not the addressee, or have received this e-mail in error, please notify the sender immediately, delete it from your system and do not copy, disclose or otherwise act upon any part of this e-mail or its attachments.Internet communications are not secure and therefore RCTP does not accept legal responsibility for the contents of this message as it has been transmitted over a public network.Any opinion or other information in this e-mail or its attachments that does not relate to the business of the RCTP family is personal to the sender and is not given or endorsed by RCTP.
________________________________________

---

[hidden email] from OpenMRS Implementers' mailing list

---

[hidden email] from OpenMRS Implementers' mailing list

++ DISCLAIMER ++
This email, any attachment and response string are confidential and may be legally privileged. Any opinions expressed in this mail do not necessarily reflect the opinions of Research Care Training Program (RCTP) or it's afilliate projects.If you are not the addressee, or have received this e-mail in error, please notify the sender immediately, delete it from your system and do not copy, disclose or otherwise act upon any part of this e-mail or its attachments.Internet communications are not secure and therefore RCTP does not accept legal responsibility for the contents of this message as it has been transmitted over a public network.Any opinion or other information in this e-mail or its attachments that does not relate to the business of the RCTP family is personal to the sender and is not given or endorsed by RCTP.
________________________________________

---

[hidden email] from OpenMRS Implementers' mailing list

[Ben Wolfe]

Some javascript/style in this post has been disabled (why?)

Fixed in version 2.8 of remoteformentry.  While I was in there I added in a new feature: this version now also supports transporting relationships from remote to central.

http://modules.openmrs.org/modules/view.jsp?module=remoteformentry

Ben

Wachira, Eric wrote:

Thanks Ben. The ticket is no. 1913

-Eric


Ben Wolfe wrote:

Ah yes, thats a bug that needs fixed in the module.  Can you create a ticket for that?

Wachira, Eric wrote:

Hi,

We are testing 1.5 with remoteformentry 2.7 and are getting errors after processing the forms at central. At remote, a patient is created and encounter form filled. For an existing patient a encounter form is also filled out. At remote, the zip file to export to central is generated ok and upon import at central we get the "Import successful message". However, no encounter appears in the patient dahsboard for the existing patient and the new patient is also not found from the Find Patient window.

The forms end up in the error queue and when you try to resolve the errors using the Resolve Error Queue link the system throws an error. We have the Tribe-1.4 module installed at both central and remote server.

Attached is the tomcat log.

Kindly adivce.

-Eric



++ DISCLAIMER ++
This email, any attachment and response string are confidential and may be legally privileged. Any opinions expressed in this mail do not necessarily reflect the opinions of Research Care Training Program (RCTP) or it's afilliate projects.If you are not the addressee, or have received this e-mail in error, please notify the sender immediately, delete it from your system and do not copy, disclose or otherwise act upon any part of this e-mail or its attachments.Internet communications are not secure and therefore RCTP does not accept legal responsibility for the contents of this message as it has been transmitted over a public network.Any opinion or other information in this e-mail or its attachments that does not relate to the business of the RCTP family is personal to the sender and is not given or endorsed by RCTP.
________________________________________

---

[hidden email] from OpenMRS Implementers' mailing list

---

[hidden email] from OpenMRS Implementers' mailing list

++ DISCLAIMER ++
This email, any attachment and response string are confidential and may be legally privileged. Any opinions expressed in this mail do not necessarily reflect the opinions of Research Care Training Program (RCTP) or it's afilliate projects.If you are not the addressee, or have received this e-mail in error, please notify the sender immediately, delete it from your system and do not copy, disclose or otherwise act upon any part of this e-mail or its attachments.Internet communications are not secure and therefore RCTP does not accept legal responsibility for the contents of this message as it has been transmitted over a public network.Any opinion or other information in this e-mail or its attachments that does not relate to the business of the RCTP family is personal to the sender and is not given or endorsed by RCTP.
________________________________________

---

[hidden email] from OpenMRS Implementers' mailing list

---

[hidden email] from OpenMRS Implementers' mailing list

[Wachira, Eric]

Some javascript/style in this post has been disabled (why?)

Asante sana Ben.

-Eric

Ben Wolfe wrote:

Fixed in version 2.8 of remoteformentry.  While I was in there I added in a new feature: this version now also supports transporting relationships from remote to central.

http://modules.openmrs.org/modules/view.jsp?module=remoteformentry

Ben

Wachira, Eric wrote:

Thanks Ben. The ticket is no. 1913

-Eric


Ben Wolfe wrote:

Ah yes, thats a bug that needs fixed in the module.  Can you create a ticket for that?

Wachira, Eric wrote:

Hi,

We are testing 1.5 with remoteformentry 2.7 and are getting errors after processing the forms at central. At remote, a patient is created and encounter form filled. For an existing patient a encounter form is also filled out. At remote, the zip file to export to central is generated ok and upon import at central we get the "Import successful message". However, no encounter appears in the patient dahsboard for the existing patient and the new patient is also not found from the Find Patient window.

The forms end up in the error queue and when you try to resolve the errors using the Resolve Error Queue link the system throws an error. We have the Tribe-1.4 module installed at both central and remote server.

Attached is the tomcat log.

Kindly adivce.

-Eric

++ DISCLAIMER ++
This email, any attachment and response string are confidential and may be legally privileged. Any opinions expressed in this mail do not necessarily reflect the opinions of Research Care Training Program (RCTP) or it's afilliate projects.If you are not the addressee, or have received this e-mail in error, please notify the sender immediately, delete it from your system and do not copy, disclose or otherwise act upon any part of this e-mail or its attachments.Internet communications are not secure and therefore RCTP does not accept legal responsibility for the contents of this message as it has been transmitted over a public network.Any opinion or other information in this e-mail or its attachments that does not relate to the business of the RCTP family is personal to the sender and is not given or endorsed by RCTP.
________________________________________

---

[hidden email] from OpenMRS Implementers' mailing list