Hi,

It's impossible to determine the reason without reviewing the logs. You need to try running the same command using a local copy of the app hosted in cloud, get the error message and review the application logs. Also sine this is a PostgreSQL command review the command itself and check if all tables and columns in the query are double-quoted and the register is correct.

Best regards,

Oscar

Hello Federico,

Thank you for your question.

Please, refer to the following:

clio push-pkg <package name here> --uri https://mysite.creatio.com --Login UserLogin --Password UserPassword

Please, replace <package name here> with your package name, https://mysite.creatio.com with the URL to the target app, UserLogin with the login to the target app, UserPassword with the target app password.

The information about Clio can be found on the github of its developers: https://github.com/Advance-Technologies-Foundation

We recommend testing it on your development instance/sandbox etc first before doing it on your production website.

Best regards,

Anastasiia

Hello Federico,

All the information about Clio can be found on the github of its developers: https://github.com/Advance-Technologies-Foundation

Please, refer to the article below which you might find useful:

https://github.com/Advance-Technologies-Foundation/clio/wiki/Build-work…

Kind regards,

Anastasiia

Hello Anupama,

I tried replicating the same error message on my side, tried several configurations (including deleting Terrasoft.WebApp reference in IIS, different URLs with the / at the end and port numbers, localhost and actual domain name). I wasn't able to receive the same error:

Are you using the latest clio binary files (they can be found here)? Also can you login to the application from the browser directly? And have I understood you right that you are trying to login to the .NET Core app (localhost:5020)?

Oscar Dylan,

Thanks Oscar for your response. 

Yes I am using Dotnet core package and as it is not hosted on IIS and on Kestrel, I am wondering if that is the reason why I am getting 404. To check how the clio command works, I tried hosting dotnet framework package on IIS and the clio command responded successfully.

Is there any settings that I am missing for the clio to respond for Dotnet Core package.

Thanks

Anupama

Anupama,

I've also successfully logged into the .NET Core app (but it's hosted on Linux) using clio:

There shouldn't be any specific setting. Can you try re-deploying your local app using .Net Core and hosted on Linux? Also don't you receive any errors in the application logs at the moment of the connect? Logs of the .Net Core app are located in the Logs folder of the root application directory:

Oscar Dylan,

It seems to be the Url format which is different for Creatio Dotnet Core and Dotnet Framework package. 

I tried by removing the forward slash from the Url and it did worked and I am able to generate the package. 

Thanks for the suggestion shared earlier in of your messages. 

Now we are experiencing another issue. We are running the SonarQube in our project file to do a code quality analysis. So the package includes an Object Code along with the source Code and which is hindering the successful installation of the package. 

Is there any way to ignore that file as I didn't find any ignore command in the github .