Infor OS On-Prem Install: Host Router Alias is required?

Hopefully this is the right group for this as it's not UX per se.

Running through our first Infor OS install following the install guide. Once we get to Backend Service Information > Backend Grid Configuration, the doc says the Host Router Alias and Alias Port are optional and used in a multi-node farm. We're doing a single VM deployment, so I would think the field being blank would be the choice (as it's blank by default).

However, upon clicking Next, we're getting an error that the Host Router Alias is required. Providing the default domain gives an error that the Host Router Alias format is incorrect (seems like it's looking for a dot (.) in the name). Adding a dot to the end matches the requirement and formatting, but then of course doesn't validate with the self-signed certificate for the default domain ("inforosdemovm").

I guess the question is, what's required here when not using a multi-node farm?

0712131256598360.doc

Find more posts tagged with

Installation

Accepted answers

Brandon Watson

Put your "Farm Name" here. For example, inforos.domain.com. Use the full URL that you want to use to access Infor OS. Even if it is not a farm, this alias is used for communication. If you do not want to use anything special, you could just use "servername.domain.com" as the alias. These are the two options for the alias and either way you will want to ensure that a DNS entry exists, and is pointed to this server, before doing the installation.

All comments

Brandon Watson

unknown

Thanks, Brandon. That helped me realize I needed to use a domain with a dot (domain.local) instead of single word. Although now, I'm getting "The Certificate import failed. Check whether the Powershell is available in the PATH environment variable." (which of course it is, so the error isn't all that helpful)

unknown

Hi There,

We're currently trying to troubleshoot our own OS installation and this was one of the issues we had as well. Out of curiosity, what did you put for the Alias Port. I believe we used Port 29091, and signed the router alias as 'servername.domain.com' - substituting our server and domain in.

From memory, we also encountered the Certificate Import error, and we found that it was because our certificate password had forbidden characters in it (Mentioned in the install guide). Unsure if you've resolved the issue, but that might be worth trying.

Brandon Watson

Jamie - You will want to use the HTTPS port for the alias,;for that particular screen you should use 29090, which is the HTTPS port.

steve mcenany

You can't really modify an install outside of editing the database that I've found with support, but there is an installer log file that generates at c:programdatainforOSionstaller*.log -- grab the latest to review the ports, OAUTH keys, etc... Great reference tool for looking things up to connect other applications that need the OAUTH info as an example. P.S. We just defaulted to the 29090 port.

unknown

Thanks for that, it seems like Xtreme is saying that post installation changes are not supported and a reinstall is needed. We'll give that a crack, but I'll be sure to keep that in mind for future troubleshooting. Thanks!

unknown

Have done many InforOS installs starting at version 3, and part of my standard troubleshooting was to uninstall and re install, the installer is actually very good at cleaning itself up when you do an uninstall, just delete the infor directories before starting again.

I noticed someone mentioned special characters, this applies to the domain as well, I had no end of issues when I was trying to use os-dev as an internal domain name !

unknown

Just to clarify, this is just the domain? Our domain for all our servers is .companyname, that company name doesn't have any special characters, but the servernames themselves do. E.G ABC-ION, or ABC-SYTUTL etc.

Thanks for the suggestion too! I see that mentioned in the install guide, so we'll be sure to do that. I think we might need to tidy up the entries in IFS and AD FS as well?

unknown

In the end, we found the first install a bit tricky as there are several key points missing from the documentation. If you have access to Infor Campus, we found the video tutorial (although slightly different from current release) to be the most helpful. Just search for course ID 02_0051200_EEN0169_ION. The course particularly touches on what to provide on each screen of the installer.

We spent a couple weeks with support trying to debug the installer only to find simple gotchas that would be really helpful to know from the beginning. This is the message that was sent back to support once we had a successful install.

---

Hi folks,

We were finally able to complete our first OS install late last night. There are a few things that would be worth adding to the documentation to avoid hitting the the breakpoints we surfaced.

The error messages in all the breakpoints will lead the next unsuspecting installer astray.

1. The username on the host machine can not contain a space. This led to the initial error we reported stating that the database farm fetch failed. So "SystemAdmin" is fine, "System Admin" will break the process.

2. The password for the SSL certificate can not be overly complex or too long. This led to the certificate import failing after the backend configuration screen. We typically use long random generated passwords, but in this case simplified it to 16 characters with no digits or symbols. Not sure what the actual acceptable characters are for this.

3. OS can not be mounted on a mapped network drive unless the drive is configured to remap upon reboot with granted access for the grid_TechStackGrid virtual user. This will cause the installation to fail once it tries to start the grid_TechStackGrid service as the executable is not accessible. We switched to an attached storage disk instead of an SMB storage share to solve this issue.

---

Another that should be added is that each password must be BOTH Windows and SQL safe.

Copyright © 2025 Infor. All rights reserved.