Friday, 10 May 2013

HOW TO CHECK YOUR 2013 JAMB RESULT

As the 2013 JAMB UTME results have been released, the popular result checking site www.myjambresult.com has remained down till the time of writing of this post. Therefore it became necessary to show parents and candidates how they can check the result.

HOW TO CHECK 2013 JAMB RESULT

  1. Visit http://www.jamb.org.ng/Unifiedtme4/
  2. Type in any of your registration number, serial number and or pin
  3. click on check result out
  4. Congratulations: your result will now appear for you to print it
Please note the following:
  1.  People for computer based test should note that the Computer Based Test (CBT) is scheduled to take place from May 18 to June 1 and the candidates need to reprint their e-registration slips afresh to further  
     ascertain their CBT centres.
  2. There are many scams for score upgrade. Be carefully and think well before you pay anybody for score upgrade.
  3. With only your registration number, you can check your result
  4. visiting www.myjambresult.com returns the following eror:

Server Error in '/' Application.


The file '/index.aspx' has not been pre-compiled, and cannot be requested.


Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

Exception Details: System.Web.HttpException: The file '/index.aspx' has not been pre-compiled, and cannot be requested.

Source Error: 

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace: 


[HttpException (0x80004005): The file '/index.aspx' has not been pre-compiled, and cannot be requested.]
   System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) +3483714
   System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) +93
   System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean noAssert) +111
   System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp, Boolean noAssert) +54
   System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath) +31
   System.Web.UI.PageHandlerFactory.System.Web.IHttpHandlerFactory2.GetHandler(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath) +40
   System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig) +139
   System.Web.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +120
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +155


Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET Version:2.0.50727.832

No comments:

Post a Comment