You may have encountered an error code indicating psae error while logging in. As it turns out, there are several steps you can take to fix this problem, which we’ll discuss shortly.
Login failed without reason code when launching App Engine from PSAE control line
E: PT8.54 bin server winx86 psae.exe -CT ORACLE -CD xxxxx -CO 0202113 -CP xxxxx -R X -AI SFMAINT
I recently worked on one of my old unnecessary desktops that I use for various tweaks and new things in PeopleSoft, and when I tried to create an app builder with PeopleTools 8.I 55 I had a country My mistake: I haven’t come before.
I called the app constructor directly using the executable, i.e. “Your safety is poorly defined parameters. Contact your security administrator.
At first I thought it might have something to do with Windows being able to access it as I noticed that this PeopleTools Home is read-only in some way. Changing directory settings didn’t help either. After browsing for a few minutes, I finally opened the configuration manager (pscfg.exe) and apparently found that all the paths in the Profile tab were correct and I entered the ID again. / Password on the “Start” tab.
By storing these settings in Configuration I Manager, I was able to call Application Designer directly without any problem.
If customers get the same error message when launching the psae.exe engine (application), check this location with Gray Heller.
You may not have understood this, but there are two ways to run one type of application core program in PeopleSoft: one using PSAE and the other using PSAESRV.
Come on Let’s see what is the difference between PSAE and PSAESRV and what are the best use cases for each right now.
PSAE Vs. PSAESRV
The PeopleSoft Application Engine template uses psae of.exe (PSAE) to run. psae.exe is probably in PS_HOME bin client winx86 for location, for some reason D: psft pt ps_home8.57.06 bin client winx86
PSAESRV are process scheduler server processes, which in turn are started when the procedure scheduler domain starts. By default psrcs.cfg runs 3 PSAESRVs. Below is the PSAESRV of the main section of the psrcs.cfg file, which lists the default maximum instances on behalf of PSAESRV. The number of PSAESRV instances specified here must match block concurrency in the server definition application during kernel programs.
[PSAESRV] ; ================================================== = ========================== ; Application Engine Tuxedo Server Settings ; ================================================== = ========================== ; –––––––––––––––––––––––––––– – – – – – – – – – – ; The maximum instance must reflect the specific maximum concurrency defined for the pro type.cessa ; given by the generic process type of the application engine as defined by ; on the server definition page in Process Scheduler Manager Maximum number of copies = 3
If you start the process scheduler domain yourself, anyone can check the status of PSAESRV.
PSAESRV remain in the Process Scheduler Settings menu by default. To enable or disable PSAESRV, you must use option 4 in the user process scheduler administration menu in PSADMIN.
When it comes to performance, in most cases you will hardly notice a difference when using PSAE and PSAESRV. You will most likely notice a difference in overall performance when running hundreds of AEs in a short period of time. For example, a problem is a common situation in PeopleSoft CRM, but not in any other PeopleSoft application.
It is commonly said that if you start an engine process that experts say takes more than 10 seconds, the PSAE turns out to be PSAESRV.
In most cases, it is best to disable PSAESRV in the main process scheduler configuration. Come onAlso consider some situations to help you decide if you need to turn PSAESRV on and off.
Fortect is the world's most popular and effective PC repair tool. It is trusted by millions of people to keep their systems running fast, smooth, and error-free. With its simple user interface and powerful scanning engine, Fortect quickly finds and fixes a broad range of Windows problems - from system instability and security issues to memory management and performance bottlenecks.
1. Download Fortect and install it on your computer
2. Launch the program and click "Scan"
3. Click "Repair" to fix any issues that are found
1. If you start an application with PSAESRV disabled, it may take a few seconds longer for the AE software to start (the time can vary from a few milliseconds to a few seconds depending on computer devices and configuration). Therefore, if you have situations where hundreds or software applications start automatically in a short period of time, consider setting up PSAESRV.
2. In situations where the route planner is stopped, the psae procedure that is running (depending on which Application Engine processes are running) will probably continue to run until termination, just like these types of people outside of the process planner. If you are using PSAESRV, the process will fail in both directions due to the process termination scheduler.
3. At runtime, PSAE creates a database connection and therefore dismounts the database at the end of the process, which also frees up process and underlying data session resources . It also helps prevent possible memory leak problems that can take up valuable system space. PSAESRVs, on the other hand, accumulate memory over time and free exercise programs, memory restart or process scheduler domain, possibly depending on the PSAESRV retry counter setting in psrcs.cfg.
4. The scheduler process will start or stop if PSAESRV is equipped, because it needs to start / stop this set of PSAESRVs. The more maximum possibilities are specified in PSAESRV, the longer it takes for the idea of starting / stopping the process scheduler domain.
It is also recommended to publish an article by David Kurtz on the same topic.
