OutSystems 11 RabbitMQ Service installer errors (On Prem)

OutSystems 11 RabbitMQ Service installer errors (On Prem)

  

Screenshot attached -

I'm going through the OS 11 upgrade process on my on premises test server.

Step 6 is to Install and Configure RabbitMQ.

I'm attempting to create the service on localhost, default port and virtual host. I have entered a username and password for this installer to create. I am attempting to do this without TLS.


Right off the bat I receive the following error:


The term 'Get-ItemPropertyValue' is not recognized as the name of a cmdlet, fun
ction, script file, or operable program. Check the spelling of the name, or if
a path was included, verify that the path is correct and try again.
At C:\Program Files\OutSystems\Platform Server\scripts\RabbitMQ\RabbitMQ_Instal
lation.ps1:76 char:47
+ $platformFolderRegedit = Get-ItemPropertyValue <<<<  HKLM:\Software\OutSystem
s\Installer\Server\ -Name '(Default)'
    + CategoryInfo          : ObjectNotFound: (Get-ItemPropertyValue:String) [
   ], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException


It then appears to be working properly until further errors occur within the RabbitMQ_Instal
lation.ps file such as:


+     throw [System.Exception]::new <<<< ("RabbitMQ broker failed to start")
    + CategoryInfo          : InvalidOperation: (new:String) [], RuntimeExcept
   ion
    + FullyQualifiedErrorId : MethodNotFound

+         throw [System.Exception]::new <<<< ("Failed to create the virtual hos
t. The command returned the following output:`n$output")
    + CategoryInfo          : InvalidOperation: (new:String) [], RuntimeExcept
   ion
    + FullyQualifiedErrorId : MethodNotFound

+         throw [System.Exception]::new <<<< ("Failed to create '$admin_usernam
e' as admin user.")
    + CategoryInfo          : InvalidOperation: (new:String) [], RuntimeExcept
   ion
    + FullyQualifiedErrorId : MethodNotFound


Ultimately the Cache Invalidation Service Installation window claim's 'Done!'

However, upon attemptin to test the connection I receive the error:

Connection to the cache invalidation service failed: None of the specified endpoints were reachable.

(Which is obvious since it wasn't created via the error strings.)


Right clicking and running the Configuration Tool as Admin does not seem to fix any of the errors.

Has anyone encountered this error yet? What is the resolution?


I will be contacting OS Support about this as well, and if no one has posted the solution to this error before I hear back from them and get it resolved I will post the resolution steps within this thread.


Thanks everyone!
Braxton

Solution

Hi Braxton,

May I ask you what is the Operating System version that you are using in your on premise test server? I'm asking this because if it isn't a Windows Server 2016 the PowerShell version will not support some of the operation that are in the script.

You can check the Systems Requirements for OutSystems 11 version here.

Solution

Tiago,

That would be it!

I'm running 2008 on this instance... Not sure how to proceed at this point, however...

Upgrading our OS on our production environment could mean substantial downtime which is extremely undesirable.

I'm considering a manual install of RabbitMQ to get around this issue...

Does anyone know if there are other potentially platform-killing issues I may encounter with OutSystems 11 by not migrating to Windows Server 2016 from 2008?

Regarding the upgrade process, there is no need to have downtime during the upgrade of your factory. You can perform a balanced upgrade that involves upgrading front ends independently one by one in order to guarantee no down time. 

You can check how to do it here. In case you need help on this, I suggest that you contact OutSystems support. 

Braxton wrote:

I'm considering a manual install of RabbitMQ to get around this issue...

Does anyone know if there are other potentially platform-killing issues I may encounter with OutSystems 11 by not migrating to Windows Server 2016 from 2008?

I would say that the major issue is that you will run the platform on a non supported configuration.