When you encounter an error, the most effective first step is not to search for a solution immediately — it is to observe and identify. The error's timing, location, and pattern are the most reliable signals for narrowing down which category it belongs to. Ask yourself:
-
When did it occur? During the build, on app launch, during a specific data operation, or after the app had been running normally?
-
Where did it appear? In the PowerBuilder IDE output window, in the Cloud App Launcher dialog, or inside the running application itself?
-
Who is affected? Only one user on one machine, or all users attempting the same operation?
-
Is it consistent or intermittent? Does it happen every time, or only under certain conditions such as concurrent use or after a period of inactivity?
Use these observations to match the error to a category (1 to 3). Once you have identified the likely type, gather the following before searching for a solution or seeking help:
-
The exact error message and error code — copy or screenshot the full text
-
The PowerServer version, PowerBuilder version, OS, web server type, and database type
-
The specific sequence of actions that reproduces the error
-
Relevant log files — PowerServer Web APIs logs for server and database errors; the Cloud App Launcher log for install and session errors
With the category identified and these details in hand, look up the specific issue in the PowerServer Help troubleshooting section, or post in the Appeon community forums for targeted assistance.
