Announcement: New Knowledge Base

4 June 2020: We are pleased to announce the launch of a new Knowledge Base, Changelogs for Business Security Products, where you can find more details, such as bugfixes or new features, about the most recent releases of our business-related products.

Upgrade FSPMS 12.10 => 12.21 : PM console not reachable

Hello,

I  updated our PM 12.10 to 12.21.

I run the PM and The PM Server on a WS 2008 R2.

The PM Server Manager status indicates, that Administration module at Http port 8080 : "A connection with the server cannot be established".

When I changed the Http port from 8080 to 8081 I get a status "OK"

But I can't start the  policy management console  -  I used https://localhost:8081.

 

With the PM 12.10 I could use 8080 - and all worked fine for several month.

Has anyone ideas how to get the PM console running?

 

Thanks

PM-KH

 

 

 

Best Answer

  • PM-KHPM-KH Posts: 4
    Accepted Answer

    The Policy Manager Option "RestricktLocalhost" is activated. That means only the PM console on the server can be used. To use a local PM console you have to deactivate this option. 

    Therefore you have 1. to stop the PM services  "net stop fsma" 2. Regedit: HKEY_Local_MACHINE->SOFTWARE->(WOW64) -> Data Fellows -> F-Secure ->Managmant Server 5 -> RestricktLocalhost -> "0".  3. Start the Policy Manager services with "net start fsma". After ttha I could start my local PM.

Comments

  • etomcatetomcat Posts: 1,318 Superuser
    Hello,
     
    This is what F-Secure's Partner Support told me, concerning a similarly phrased problem some 2 weeks ago:
     
    This is a known issue with Policy Manager 12.21 upgrade. Kindly advise the customer to uninstall the current PMS 12.21, repair H2DB file, reinstall previous PMS 12.20 version, and then upgrade the software.
     
    The instructions are available on our community known issues page:
     
    We regret the problem. Please note that F-Secure Policy Manager 12.30 is already in development with the aim of enhancing functionality and product quality.
     
    Best Regards: Tamas Feher, Hungary.
  • PM-KHPM-KH Posts: 4

    Hello etomcat,

     

    I changed the HTTP Port from 8080 to 8081 Ports. After some efforts it will work on the Server. 

    But on a client I couldn't start the PM.

    At the moment it ist OK for me to work on the server.

    So the problem exists further on.

  • aimutchaimutch Posts: 24

    I just tried installing PM 12.30 and am encountering the same problem. I'll see if the workaround works. 

  • MJ-perCompMJ-perComp Posts: 1,098

    The recommended way is to restart the setup and select to modify the settings.

     

    BTW: 12.30 is RTM!

This discussion has been closed.