David Beavon (Software) asked a question.

June 13, 2020 at 6:46 PM
Configs overwritten by service pack (11.7.6)

Has anyone tried the service pack v.11.7.6 yet? On a development machine I unchecked the default behavior to create a backup copy of the entire Progress installation directory (aka DLC or whatever it is called).

 

...I didn't expect this, but it seems to have overwritten at least one config file, eg instances.windows in C:\Progress\OpenEdge\servers\pasoe\conf

 

Is that expected? I suppose I will need to take more precautions as we roll this out beyond development. I didn't anticipate that a service pack (especially a 6th one for 11.7) would mess with my configs!

 

Also the KB and release notes don't seem to say there are followup work items to repair/restore my overwritten configs

https://knowledgebase.progress.com/articles/Article/P21979

 

So far the only file I noticed a problem with is instances.windows (in C:\Progress\OpenEdge\servers\pasoe\conf) ... As a result my PASOE isn't registering in admin server. I also noticed my PASOE instance isn't starting; but that may be a separate issue. I guess I will know shortly...

 

 

Hopefully we won't find much more damage from this service pack, beyond a few configs. I just wanted to share this information in case there are others that are planning to install this soon. I guess it never hurts to take a backup copy of your original files, and keep them for a few weeks after the service pack is installed.

 

The interesting thing is that this didn't happen to me on a PDSOE workstation, but it did on a server that was running only the PASOE license.... I guess I got a false sense of security after installing on my personal workstation!

  • 5 answers
  • 300 views

  • David Beavon (Software)

    My PASOE installation is back up and running. The only file in the %DLC% that ended up needing to be rebuilt was instances.windows. There were other problems in the PASOE instance itself (oepas1) but that is another story.

    Selected as Best

  • David Beavon (Software)

    My PASOE installation is back up and running. The only file in the %DLC% that ended up needing to be rebuilt was instances.windows. There were other problems in the PASOE instance itself (oepas1) but that is another story.

    Selected as Best

  • Dileep Dasa (Progress Software)

    instances.windows file should not be overwritten. I had 11.7.5 installed and applied 11.7.6 service pack on it. I don't see the instances.windows file overwritten. Can you describe the steps you followed to apply service pack?

  • David Beavon (Software)

    What licenses are you upgrading? Try doing that same upgrade on windows with only (1) ProdAs for OE (2) Nameserver and (3) OE SQL Client Access.

     

    I had just downloaded the service pack, and unzipped, and ran the Setup.exe after stopping appserver and admin server. Unfortunately I also unchecked the option to create a backup copy of the DLC directory.

     

    While you are on 11.7.5 you may want to ensure that you have created a PASOE instance that is visible in instances.windows before you start applying the service pack. This isn't a huge deal, and I learned my lesson. Going forward I will keep a backup copy of the DLC directory when applying service packs. Better to be safe than sorry!

  • Dileep Dasa (Progress Software)

    I have done exactly the same thing you described. Installed only the three components you mentioned and created an instance with 11.7.5. Then installed SP6 over it. I still see the instance created in 11.7.5 after installing SP6 when I did "pasman instances" and I could also see the corresponding entry in instances.windows file located at $DLC/servers/pasoe/conf.

     11.7.5

     

    11.7.6

  • David Beavon (Software)

    Thanks for testing. We have some other machines to upgrade shortly as well. I will let you know if this happens on any others. Hopefully there are other customers who are starting to roll this out as well. We don't need to be the first into production.

     

     

    FYI, Our PASOE instance is actually called "oepas1" which is the default instance name. (Perhaps that makes a difference when the service pack is cleaning out the instances.windows file?)

     

    This is a fairly minor problem and our PASOE server seems to be running smoothly again. If this is the only problem with SP6 (along with the changes in the PASOE spring security framework) then I would consider it a fairly smooth upgrade.