You need to be logged in to view a user's profile.
  1. Esau Redwan
  2. PowerServer
  3. Thursday, 12 September 2024 18:42 PM UTC

Running local kestrel server for powerserver is giving error that it cannot reach the powerserver license server. This use to work fine for us.

I am attempting to run the local kestrel server to start recording in Jmeter for load testing the application. Is there a way to record without the local kestrel server?

We are investigating on our end as well incase there was a network change but I wanted to be pro-active and ask you guys as well incase I am missing something.

How can I login to PowerBuilder with my license and even deploy and run from Azure with no issues but a local kestrel server is blocked?

Attachments (1)
Francisco Martinez @Appeon Accepted Answer Pending Moderation
  1. Thursday, 12 September 2024 18:52 PM UTC
  2. PowerServer
  3. # 1

Hi Esau,

You need to first first let the Web APIs connect to the internet without JMeter, and then when the Web APIs are ready (you see the console output), you can begin recording.

 

Regards,
Francisco

Comment
  1. Esau Redwan
  2. Friday, 13 September 2024 22:30 PM UTC
Okay good idea i will try that
  1. Helpful
  1. Esau Redwan
  2. Tuesday, 17 September 2024 21:23 PM UTC
Hello, I tried running Jmeter with a local IIS instance but getting java socket errors when its trying to record the data.



I went back to try Kestrel again and same problem as before but this time I checked the windows error event viewer and see this. Do you guys know why this might be happening?

Faulting application name: ServerAPIs.exe, version: 1.0.0.0, time stamp: 0x66479ae7

Faulting module name: KERNELBASE.dll, version: 10.0.19041.4522, time stamp: 0xf7a99bd4

Exception code: 0xe0434352

Fault offset: 0x000000000002ba99

Faulting process id: 0x3828

Faulting application start time: 0x01db094527ec9f45

Faulting application path: C:\PowerServer_lance_ps\ServerAPIs\bin\Release\net6.0\ServerAPIs.exe

Faulting module path: C:\windows\System32\KERNELBASE.dll

Report Id: 4cdd7e25-0833-4391-a2cf-ee04eb9c71c2

Faulting package full name:

Faulting package-relative application ID:
  1. Helpful
  1. Francisco Martinez @Appeon
  2. Tuesday, 17 September 2024 21:53 PM UTC
Try changing the Web API's log level to something more detailed and see if you can catch something: https://docs.appeon.com/ps2022r3/Logging_with_the_settings_in_Logging.json.html



Regards,

Francisco
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


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