• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • My Powerbuilder IDE 2022 R3 does not start anymore without displaying any error message

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

Resolved My Powerbuilder IDE 2022 R3 does not start anymore without displaying any error message

  1. New
  2. Issue
0
Votes
Undo
  1. Pierre DETE
    Pierre DETE
  2. PowerBuilder
  3. Friday, 15 November 2024 15:25 PM UTC

Hello, for two days my Powerbuilder IDE 2022 R3 does not start anymore without displaying any error message.

There is a crash log in the Windows Application Event Viewer:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />
  <EventID>1000</EventID>
  <Version>0</Version>
  <Level>2</Level>
  <Task>100</Task>
  <Opcode>0</Opcode>
  <Keywords>0x8000000000000000</Keywords>
  <TimeCreated SystemTime="2024-11-15T15:12:45.2588689Z" />
  <EventRecordID>63108</EventRecordID>
  <Correlation />
  <Execution ProcessID="9428" ThreadID="37960" />
  <Channel>Application</Channel>
  <Computer>PARL6RVSSQ3.Finastra.global</Computer>
  <Security UserID="S-1-5-21-2827996254-1695550418-2679538566-24251" />
  </System>
- <EventData>
  <Data Name="AppName">PB220.exe</Data>
  <Data Name="AppVersion">22.2.0.3289</Data>
  <Data Name="AppTimeStamp">658d10f4</Data>
  <Data Name="ModuleName">PB220.exe</Data>
  <Data Name="ModuleVersion">22.2.0.3289</Data>
  <Data Name="ModuleTimeStamp">658d10f4</Data>
  <Data Name="ExceptionCode">c0000409</Data>
  <Data Name="FaultingOffset">000249d5</Data>
  <Data Name="ProcessId">0x8dd4</Data>
  <Data Name="ProcessCreationTime">0x1db3770d2814922</Data>
  <Data Name="AppPath">C:\Program Files (x86)\Appeon\PowerBuilder 22.0\PB220.exe</Data>
  <Data Name="ModulePath">C:\Program Files (x86)\Appeon\PowerBuilder 22.0\PB220.exe</Data>
  <Data Name="IntegratorReportId">35cb1a52-7b9c-4c2c-8154-5d6a51384fa3</Data>
  <Data Name="PackageFullName" />
  <Data Name="PackageRelativeAppId" />
  </EventData>
  </Event>

 

Yesterday I reinstalled it completely and it was able to start. But same problem today :(

This is the first time I have this problem.

PB2019 still works

What should I do?

Thanks in advance.

 

 

 

 

TCP IP Socket connection - Enable TLS
Who is viewing this page
Chris Pollach @Appeon
Responses (2)
Mark Goldsmith
Mark Goldsmith Accepted Answer Pending Moderation
  1. Friday, 15 November 2024 18:48 PM UTC
  2. PowerBuilder
  3. # 1

Hi Pierre,

Chris's suggestion will work for testing if the IDE will open okay, but if for some reason you can't, or don't want to, change the name of the workspace folder, you could:

1) Rename the pb.ini file (powerbuilder will create another pb.ini file), again, just to see if you can start up the IDE. With a fresh pb.ini file it can't open the last used workspace. Or,

2) Remove the line "LastWorkspace=D:\MyAppFolder\MyApp.pbw" from the pb.ini file and that also will prevent it from opening any workspace.

The pb.ini file is typically located in a folder path something similar to "C:\Users\Pierre\AppData\Local\Appeon\PowerBuilder XX.0".

HTH...regards,

Mark

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 15 November 2024 15:39 PM UTC
  2. PowerBuilder
  3. # 2

Hi Pierre;

  If you name the current WorkSpace folder (ie:  "MyApp" => "MyApp_XX".

Then restart the IDE, does it open OK?

Regards .. Chris

Comment
Pierre DETE
  1. Pierre DETE
  2. Friday, 15 November 2024 16:42 PM UTC
Hi Chris,

What do you mean by current workspace folder ?

Regards
  1. Helpful
Pierre DETE
  1. Pierre DETE
  2. Friday, 15 November 2024 16:58 PM UTC
The IDE doesn't start at all
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Friday, 15 November 2024 17:09 PM UTC
Hi Pierre ... that would be he folder where the current (last accessed) App workspace is located. The IDE will always want to return there as a default at start-up. It might also want to reopen the last Object Painter(s) that were in progress when the IDE was last active. This auto-return to the last workspace / painter could be the cause of the crashing if anything in that WS folder has been corrupted. HTH
  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.