Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The requested service 'Clio.Command.CreatioInstallCommand.InstallerCommand' has not been registered when calling clio deploy-creatio with MSSQL zip file #317

Open
josehernaC2C opened this issue Sep 19, 2024 · 6 comments
Labels
bug Something isn't working

Comments

@josehernaC2C
Copy link

Hello,

I'm following the clio tutorial to install Creatio from CLI, but I'm getting the error below. Any ideas on what I'm missing?

Thanks,

Jose

clio version '6.1.0.37'

[ERR] - The requested service 'Clio.Command.CreatioInstallCommand.InstallerCommand' has not been registered. To avoid this exception, either register a component to provide the service, check for service registration using IsRegistered(), or use the ResolveOptional() method to resolve an optional dependency.
Install Creatio from clio error

@kirillkrylov
Copy link
Contributor

@josehernaC2C
I can’t seem to reproduce this error.
If you run the command outside the playbook, does it yield the same outcome?
Also note that you’re using a PostgreSQL file, not MSSQL

@kirillkrylov kirillkrylov added the bug Something isn't working label Sep 20, 2024
@josehernaC2C
Copy link
Author

@kirillkrylov
I ran the deploy command outside the playbook and got the same result. I already have Version 8.1.3.6734 installed on my local and I was trying to add a clean install for 8.1.3.6801 using the MSSQL zip file provided by Creatio support.

We are growing as a developer team and we are trying to figure it out the easiest way to deploy local Creatio instances to our windows\SQL server environment

clio.deploy-creatio.error.2024-09-20_12-25-08.mp4

@kirillkrylov
Copy link
Contributor

@josehernaC2C

We've added additional debugging options to clio commands. You can now run any command with --debug flag to get more details.

Your exception seem to be related to kubectl, which is installed when you install Rancher Desktop. Please make sure Rancher Desktop is installed before running the installer command

Please make sure to follow the instructions provided in this link.
https://github.com/Advance-Technologies-Foundation/clio?tab=readme-ov-file#install-rancher-desktop-and-configure-resources

@josehernaC2C
Copy link
Author

Thanks @kirillkrylov I was missing a couple of steps.

I'm almost there. Now I'm getting this error:

[Starting Database restore] - 07:03:28
Microsoft.Data.SqlClient.SqlException (0x80131904): Login failed for user 'sa'.

where do I get and change that password?

Copy link
Contributor

Make sure deploy mssql with the provided manifest template.

@josehernaC2C
Copy link
Author

Thanks @kirillkrylov. The issue was that I already had a SQL Server local instance running on port 1433 and I think the scripts were trying to open that one that had sa disable.

After that I got this error:
Microsoft.Data.SqlClient.SqlException (0x80131904): Cannot open backup device 'C:\Program Files\Microsoft SQL Server\MSSQL14.MSSQLSERVER\MSSQL\DATA\CreatioStudio8.1.3.6801.bak'. Operating system error 2(The system cannot find the file specified.).
RESTORE DATABASE is terminating abnormally.

But I think it is because the script was looking for a Creatio name and the ZIP file we received had the backup name as BPMonline813Studio.bak

I copied the back up there with the expected name and the site came up.

Thanks again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants