Skip to content
  • There are no suggestions because the search field is empty.

AppEnhancer - ErrorCode: 401, Message: Unable to find the render server to render the page.

Full error: Unable to display the current page. Details: {"errorCode":401,"message":"Unable to find the render server to render the page. Contact your administrator.","innerException":null,"data":null}.

Applies to Versions:
All

Summary:
There are a number of reasons this error can appear. Here are some possible resolutions.


First step. Enable Verbose Logs to see if they give hints to anything.

Resolution 1:

First, check to make sure that the AX Render Server Service is up and running in windows services. If it is running:

1. Go into AX Administrator.
2. Server Management,
3. Then click on the Validate button.

Let me know if any errors show up in the validate pop up. If no errors show up

1. please check the render cache folder configured in AX Admin
2. Make sure the folder exists, that it is a shared UNC path.
3. And that everyone has full control to this folder.


*************************************************************************************************************

Resolution 2:

Next you can try this:

Go into AX Administrator > Monitoring.  Check these 2 spots:

    1. Registered components
    2. Running components

Under each of these sections, double-check to make sure ONLY the correct render server is listed and not some errant render server.  If you do see an incorrect render server, remove it from under the “registered components” section.  Then do an iisreset and re-test the issue. 


*************************************************************************************************************
Resolution 3:

Another instance of this error that our PS team actually ran into. Is the render cache database configured in this tab using the AX database? Or is it using a completely separate database just for rendering? 

  1. Go to the AX Administrator website
  2. Rendering Server. Under the cache tab, there is a field where you can specify a database.
  3. Is the database configured in this box the same exact AX database under Environment > Datasources?

Then do this:

  1. Query the cm_config table. 
  2. Truncate the cm_config table.  While you’re in there, I’d recommend you also clear out all old render jobs that may have been left behind.  You can do this by truncating cm_rscache and cm_rsjobqueue tables.
  3. Afterwards, go through the regular steps of removing the xscm.config file from the server, launching component registration wizard, and adding a NEW datasource (not existing since cm_config is empty). 
  4. After plugging in all the necessary info into component registration wizard, you should be able to log into the AX Admin site, re-add the datasource, and add all the configs back in. 
  5. Then do component registration again for the rest of the components you just added the configs for, then an iisreset, then you should be able to test again.


*************************************************************************************************************
Resolution 4:

  1. Rebooting

  2. Unregistering and Re-registering all components

  3. IISReset.

  4. Uninstalling and Reinstalling Render Server and patches

  5. Made sure we are on patch 29

  6. Check and redid render configuration in admin and reregistered.

If the issue still occurs, please test this:

Go into AX Administrator, add a local path to your storage management and point it to a folder in your local drive (for example, c:\render). If the folder doesn’t exist, please create it. Then change the render server settings to point to that render folder for the cache.

Do a component registration for render server and AX web again, then another iisreset and re-test the issue. 

*************************************************************************************************************