LSO Client Install Error

 2 Replies
 0 Subscribed to this topic
 11 Subscribed to this forum
Sort:
Author
Messages
Brian
Basic Member
Posts: 13
Basic Member

    I am not sure where to look for this one....

    I go to the LSO site using the FQDN and port + /LSO and I get to the "Install Lawson Smart Office"  page but when I click the link the address it is trying to bring up is the name of the LCM service host with the same port number and indicating that the LSO server with tthe client port.

    For exmple, assume my server is NT12345  Port is 19005 and my LCM Service is LSO_HOST

    I enter in  http://NT12345:19005/LSO and I get to the install page

    But the link on the page is set to http://lso_host:19005/LSO...tps://LSO_HOST:19006

    Which takes me to a page not found page.

    If I enter the server name (replacing LSO_HOST) for the install link, I get a step further,
    http://NT12345:19005/LSO/...ttps://NT12345:19006

    Now I get the message that the application is trying to load but it fails and in the resulting  "Cannot Start Application" Details listing I see that LSO_HOST again listed as a reason that the application cannot load. 

    Can anyone give me an idea of where I messed this up?  And how to correct this.  I noticed when installing SmartOffice the LSO_HOST was used as the default value in the "Default System Profile"  Do I need to enter that value somewhere else...or uninstall SmartOffice and reinstall with the Server Name instead of the defaulting LSO_HOST name?

    Roger French
    Veteran Member
    Posts: 549
    Veteran Member
      Have you tried:

      https://servername:19006/LSO

      You will then need to install the certificates from the browser to actually be able to log in access the LSO client.

      Brian
      Basic Member
      Posts: 13
      Basic Member
        The issue here was that when I went to sign installation point, I did not replace the LSO_HOST value in the web path with the actual FQDN of the system.  I ran through teh sign portion again and the issue was resolved.