• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Unable to start IDE - Invalid parameter from the client side

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (5)

Resolved Unable to start IDE - Invalid parameter from the client side

  1. Issue
1
Votes
Undo
  1. Yiannis Papadomichelakis
    Yiannis Papadomichelakis
  2. PowerBuilder
  3. Wednesday, 15 November 2023 15:23 PM UTC

After using PB2022 R2 for about 6 hours this day, the IDE crashed (no surprises here).
Now each time I am trying to start it, I get the following message, so I am unable to use IDE!

I tried restarting the computer (Windows 11 Enterprise 22H2), reinstalling the IDE (using PB Installer) without any luck.

Obviously, the IDE left something - somewhere and now it's corrupted, prohibiting me to use it.

Please guide me in resolving this issue.

  1. IDE
  2. License
  3. Log In
  4. PowerBuilder
Azure Key Vault secret
C:\pb190t\build\unicode\DrawEx.dll
Accepted Answer
CRISTIAN MEDINA
CRISTIAN MEDINA Accepted Answer Pending Moderation
  1. Wednesday, 15 November 2023 17:37 PM UTC
  2. PowerBuilder
  3. # Permalink

The same happen to me, it was because with the last visual studio update it installed .net 8 , after uninstall .net8 I can login again

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Wednesday, 15 November 2023 17:51 PM UTC
Thanks for sharing this temporary workaround. Our product engineering is looking at this potential incompatibility issue and we will prioritize to resolve it.
  1. Helpful 6
jorge gonzalez
  1. jorge gonzalez
  2. Wednesday, 15 November 2023 20:32 PM UTC
Thank you! That worked. I installed these mega Visual Studio updates to my work and personal machines and started getting this error on both. Thanks
  1. Helpful
There are no comments made yet.
Responses (5)
wang gaofeng
wang gaofeng Accepted Answer Pending Moderation
  1. Wednesday, 31 January 2024 06:34 AM UTC
  2. PowerBuilder
  3. # 1

As a software development tool, login authorization error occurs; This is a very embarrassing thing

Comment
There are no comments made yet.
Ramón San Félix Ramón
Ramón San Félix Ramón Accepted Answer Pending Moderation
  1. Friday, 24 November 2023 10:19 AM UTC
  2. PowerBuilder
  3. # 2


The same thing just happened to me today. I commented out the json file as Aubrey Lin indicates and was able to log in.

Comment
There are no comments made yet.
Aubrey Lin @Appeon
Aubrey Lin @Appeon Accepted Answer Pending Moderation
  1. Thursday, 16 November 2023 02:12 AM UTC
  2. PowerBuilder
  3. # 3

Hi Yiannis,

Thanks for reporting this problem. Please find the workaround below for this problem:
1. Please find the pbdevproxy.runtimeconfig.json file in C:\Program Files (x86)\Appeon\PowerBuilder 22.0\IDE.
2. Comment out the following line in the JSON file.
    //"rollForward": "LatestMajor",
3. Restart PB IDE.

In this way, you should be able to use the latest Visual Studio 2022 with .NET 8 and PB at the same time.

Comment
Load more comments
Peter Piechutzki
  1. Peter Piechutzki
  2. Monday, 11 December 2023 09:42 AM UTC
Since it's a PB Problem and not a .net8 Problem imho this Solution should please be moved to accepted Answer.
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Tuesday, 12 December 2023 02:30 AM UTC
This issue only affects PB 2022 R2 (it does NOT affect PB 2022 or older), and it is already fixed in PB 2022 R3.
  1. Helpful
Mark Su
  1. Mark Su
  2. Thursday, 21 December 2023 01:17 AM UTC
Or change the value of "rollForward" to "LatestMinor".

https://learn.microsoft.com/en-us/dotnet/core/versions/selection
  1. Helpful
There are no comments made yet.
Yiannis Papadomichelakis
Yiannis Papadomichelakis Accepted Answer Pending Moderation
  1. Wednesday, 15 November 2023 18:40 PM UTC
  2. PowerBuilder
  3. # 4

You are right!

VS was upgraded during the day, I suppose .net 8 runtime was installed. I removed it and now PB works again!

Thank you!

 

Comment
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.