Reporting Module - Perpetually queued reports

[Myles Barros]

I am interested in making contributions to the Reporting module and as such have been experimenting with it to understand its capabilities. I've been running into difficulties, however, in rendering the reports. While the content of the reports is successfully rendered when pre-viewing the content but the reports themselves are not run; they are perpetually queued without end.

I'm currently running an instance of OpenMRS that was installed using the 1.9.7 Standalone package. I have the following modules installed:

Serialization Xstream 0.2.7, Logic Module 0.5.2, Reporting 0.8.2, Patient Image 0.5.1, Rest Web Services 2.4.8f3fb, Calculation 1.1, HTML Widgets 1.6.6.

[Lara Kellett]

Hi Myles,

Have a look in your log and see if there are messages similar to this coming up

WARN - AbstractReportsTask.authenticate(61) |2012-12-31 14:05:41,112| Not authenticating to avoid locking account. Please ensure you scheduler username and password are configured correctly in your global properties

If there are you need to go into the global properties (can be accessed from the setting page under scheduler) you should see a scheduler password and username global properties, these need to be set to a correct user (with the system developer role) for the report tasks to run. By default these values are set to the default password of test for the admin user, however you would have been forced to change this default password when running through the initial install of OpenMRS. If you fix the global property and restart your server the reports should run.

Hope that helps,

Lara Kellett
Médecins Sans Frontières/Doctors Without Borders
lara.k...@newyork.msf.org
 +1.631.480.4969
Skype: lara.kellett

--
OpenMRS Developers: http://go.openmrs.org/dev
Post: d...@openmrs.org | Unsubscribe: dev+uns...@openmrs.org
Manage your OpenMRS subscriptions at https://id.openmrs.org/

To unsubscribe from this group and stop receiving emails from it, send an email to dev+uns...@openmrs.org.

[Myles Barros]

Sorry for the late response - you were exactly right, it was a problem with the scheduler username and password.

Thanks very much for your help.