“No Record Found” During Post Utme Registration And How To Correct It » NAIJAPARY
Connect with us


“No Record Found” During Post Utme Registration And How To Correct It



Share this post with your Friends on 👇

I did change of course but I am getting the error of during .

This is the complain of so many candidates ; especially when the post utme registration has begun and closing date is already at hand for some schools.

The good news right now is that Jamb has given an official statement as regards the issue… See what Jamb said about it below:

According To Jamb: All candidates who earlier did JAMB change of course and institution and have been unable to register for their school’s Post-UTME screening exercise due to responses like “No Record Found” on the school’s portal have been asked to be patient as the issue will be resolved soon.

ALSO READ:   AKSU Notice To Candidates Yet To Accept Admission On JAMB CAPS - 2018/2019

The reason for the issue is the fact that JAMB has not sent your details to the new schools you changed to.

However, JAMB has disclosed that soon enough, details of the affected candidates will be sent to their various schools and afterwards such candidates will now be able to register for the Postp-UTRME screening of their various schools.

JAMB will soon send their details to their various schools which will enable them register during online registration on their various school portal.

According to JAMB, all Institutions have been directed to ensure that all candidates are considered for their various PUTME”

ALSO READ:   ANSU Admission List Out - 2018/2019

Candidates should not panic as they would certainly sit for the PUTME in the Institutions they have made changes to.

Share this post with your Friends on 👇
Click to comment

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.


Subscribe To Naijapary via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 4,108 other subscribers

error: Content is protected !!