• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • PB 17.0 shows Error: Initialization File is not Writeable...on Startup

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

Resolved PB 17.0 shows Error: Initialization File is not Writeable...on Startup

  1. Issue
0
Votes
Undo
  1. Richard Shakour
    Richard Shakour
  2. PowerBuilder
  3. Thursday, 3 January 2019 13:56 PM UTC

I just had to move PB to a new Computer after the hard drive crashed and am not getting an error message when starting PB which then shuts down PB.

I have already looked at the past article that states that this is caused by the pb.ini in the User settings (\appdata\local\Appeon\PowerBuilder 17.0\pb.ini) being set to Read Only but that is not the case.  The pb.ini file is NOT checked for Read Only but the error above keeps coming up.  I have checked all the .ini files and none are set to Read Only.

This is Windows 10 Professional.

This is basically a show-stopper so if anyone has any ideas please share.

  1. PowerBuilder
Any way to hook into the PB Filter window?
Two Factor Authentication
Responses (2)
Richard Shakour
Richard Shakour Accepted Answer Pending Moderation
  1. Thursday, 3 January 2019 14:47 PM UTC
  2. PowerBuilder
  3. # 1

This was 2017 Build 1666.

I did try running the IDE in Admin but it still gave the error.

I researched more from older cases on Google and they suggested changing the Initpath to a folder of my own creation.

[HKEY_CURRENT_USER\Software\Sybase\PowerBuilder\17.0]
"InitPath"="C:\\Users\\msnet\\AppData\\Local\\Appeon\\PowerBuilder 17.0"

So, I moved the files from the above folder to a new folder off the C:\ drive that I created and then changed the above registry to that folder and it then worked.

[HKEY_CURRENT_USER\Software\Sybase\PowerBuilder\17.0]
"InitPath"="C:\\\\Appeon\\PowerBuilder 17.0"

It must be some type of permissions issue on the folder in the default registry entry.

 

Thank you!

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 3 January 2019 15:06 PM UTC
Yes, that is why the PB IDE did not work properly as the proper install would have made those registry entries for you.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 3 January 2019 14:22 PM UTC
  2. PowerBuilder
  3. # 2

Hi Richard;

  Did you perform a new install of PB2017Rx on the secondary PC vs a copy?

Also - have you tried running the IDE in "Admin: mode?

Regards ... Chris

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.