1. mike S
  2. PowerServer
  3. Monday, 25 November 2024 16:46 PM UTC

any idea what would cause this in powerserver?  We did do an update and prior to that the user ran fine.  The runtime did not change with the update, just the application was updated.

This is only for 1 user, all our others are fine.  checked the website and the runtimes are there.

The login screen (PB screen) does run - we have them login which first calls a non-PS REST api to authenticate and log to a database that they connected , so it MUST have the runtimes available since that screen ran.   

my guess is that the user somehow (or some process) deleted the runtimes off her machine?  I would have thought that PS would auto download any missing runtimes.  

 

has anyone else run across this in powerserver after an update?



There are no replies made for this question yet.
However, you are not allowed to reply to this question.