• 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 (7)

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

  1. Issue
2
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
UNC resolution in PB2022 R3 64 bit with mapped dri...
FileDelete function does not delete file on PB201...
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
Load more comments
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Saturday, 27 July 2024 19:47 PM UTC
@Armeen:

Sorry but "we will prioritize to resolve it." It's now half a year ago. If anyone needs to use .net 8 they cannot.

Is there an estimated time to solve this problem?

regards.
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Saturday, 27 July 2024 20:08 PM UTC
Hi Miguel;

The plan is to support .Net 8 in the next PB 2022 R3 MR. AFAIK, the current target for that MR is the end of July. What I do not know is if that's the release date or the Engineering to QA date. Of course, QA will have the last word before release. So that might hinder the actual release date if they discover any irregularities. Either way, we should have a PB with .Net 8 support soon this summer (IMHO). Again, based on what I've heard this far. HTH

Regards ... Chris
  1. Helpful
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Saturday, 27 July 2024 21:31 PM UTC
Thanks for the info Chris!
  1. Helpful
There are no comments made yet.
Responses (7)
Yiannis Papadomichelakis
Yiannis Papadomichelakis Accepted Answer Pending Moderation
  1. Wednesday, 15 November 2023 18:40 PM UTC
  2. PowerBuilder
  3. # 1

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.
Aubrey Lin @Appeon
Aubrey Lin @Appeon Accepted Answer Pending Moderation
  1. Thursday, 16 November 2023 02:12 AM UTC
  2. PowerBuilder
  3. # 2

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.
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. # 3


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.
wang gaofeng
wang gaofeng Accepted Answer Pending Moderation
  1. Wednesday, 31 January 2024 06:34 AM UTC
  2. PowerBuilder
  3. # 4

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

Comment
There are no comments made yet.
Rodolfo Reyes
Rodolfo Reyes Accepted Answer Pending Moderation
  1. Thursday, 25 July 2024 20:32 PM UTC
  2. PowerBuilder
  3. # 5

Gracias por este tema.

 

Desde hace dos días nos pasó justo lo que aquí comentan. Ya habíamos desinstalo Power Builder 2022 R2 varias veces y hecho muchas cosas para que nos dejará entrar sin éxito.

Como no podemos disintalar los componentes de .NET 8 porque los estamos utilizando, hicimos lo de editar el JSON.

 

 

Comment
There are no comments made yet.
Jeff Stubbs
Jeff Stubbs Accepted Answer Pending Moderation
  1. Thursday, 21 November 2024 16:56 PM UTC
  2. PowerBuilder
  3. # 6

Same problem here: "Invalid parameter on the client side" before logging into PB 2022R2 after using it regularly without issue.

I think this is the .NET 8 update that was pushed out to our PCs.

 

Unfortunately, the fix (https://www.appeon.com/developers/get-help/knowledgebase/4538) modifying the pbdevproxy.runtimeconfig.json (tried commenting, then removing "rollForward": "LatestMajor", then replacing with "LatestMinor") resulted in new error message while starting PB (before the login screen)

I verified this file exists in 

C:\Program Files (x86)\Appeon\PowerBuilderUtilities 22.0
C:\Program Files (x86)\Appeon\PowerBuilder 22.0\IDE

and the first location is on the system PATH.

I did read https://www.appeon.com/developers/get-help/knowledgebase/4574, install procman, and tried copying pbsys.dll from C:\Program Files (x86)\Appeon\PowerBuilder 22.0\IDE to C:\Program Files (x86)\Appeon\PowerBuilder 22.0, as there were references to that directory in procman, but still got the same error.

 

This PC is locked down so that I am unable to uninstall these updates, or update to PB 2022R3.   (The PowerBuilderInstaller_bootstrapper.exe "Failed to update the installer")

 

Any other ideas?
Thanks,
Jeff

 

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.