Re: Pulling down a forked branch

2020-06-02 Thread Michael Vorburger
Manoj, you're close, but in this particular case, the "have the correct access rights" message is due to something slightly different... Natasha, you are actually up against not 1 and not 2 but 3 separate problems here... ;-) 1. Unless I'm mistaken and the syntax has changed since I last did

Scheduler Jobs Failing

2020-06-02 Thread zayyad
Hello Devs, We have some tenants's jobs failing especially accrual jobs, on inspecting the logs I came across this error: 23:00:00.065 [Scheduler9_Worker-6] ERROR org.quartz.core.ErrorLogger - Unable to notify TriggerListener(s) while firing trigger (Trigger and Job will NOT be fired!).

Re: [Mifos-developer] Scheduler Jobs Failing

2020-06-02 Thread Bharath Gowda
Hi Zayyad, Technically I will let developers answer your query. To unblock you immediately you can try restarting your servers, I guess that will solve the problem for now. Regards, Bharath Lead Implementation Analyst | Mifos Initiative Skype: live:cbharath4| Mobile: +91.7019636073

Re: [Mifos-developer] Scheduler Jobs Failing

2020-06-02 Thread Michael Vorburger
Something with your database, note Could not get JDBC Connection; nested exception is java.sql.SQLException Best of luck figuring it out. On Tue, 2 Jun 2020, 11:49 , wrote: > Hi Bharath, > > > > I had already restarted the server and ran the jobs. > > > > I got this error on running the jobs

RE: [Mifos-developer] Scheduler Jobs Failing

2020-06-02 Thread zayyad
Hi Bharath, I had already restarted the server and ran the jobs. I got this error on running the jobs manually after server restarted. Regards; *** Zayyad A. Said | Chairman & C.E.O Cell No.: +254 716 615274 | Skype: zsaid2011 Email:

Re: Pulling down a forked branch

2020-06-02 Thread Natasha Natarajan
Thank you, Michael! It seems to have worked! Definitely, I will look into those git tools. On Tue, Jun 2, 2020 at 12:25 AM Michael Vorburger wrote: > Manoj, you're close, but in this particular case, the "have the correct > access rights" message is due to something slightly different... > >