Hi,
I am running csweb 7.2 on my server and cs pro 7.2 on my laptop. However, when I try to deploy my app, i get a series of errors. The first being that the csweb I'm running does not support application deployment. The second one is that the pen file already exists in my temp files....
I have attached the screen shots of the errors I'm getting. How do i resolve these issues?
Thanks
Singani
Deployment Error
Re: Deployment Error
First make sure you completed the upgrade to CSpro 7.2 correctly. If you log into CSWeb from your browser do you see the "Apps" option on the left in between "Data" and "Users"? If you click on it do you get an error? If "Apps" is not there or if you get an error then please redo the CSWeb installation/upgrade.
If that is not the issue please post the sync.log file from the PC that you used to Deploy? You can find it in the directory C:\Users\<your username>\AppData\Roaming\CSPro.
If that is not the issue please post the sync.log file from the PC that you used to Deploy? You can find it in the directory C:\Users\<your username>\AppData\Roaming\CSPro.
Re: Deployment Error
Hi Josh,
When I log on to my csweb I am able to see the Apps option and if i click on it, it brings up the applications page. Then the following is what i got from the sync log.
singani
When I log on to my csweb I am able to see the Apps option and if i click on it, it brings up the applications page. Then the following is what i got from the sync log.
Code: Select all
20/03/2019 11:37:21.765 INFO: Connect to server http://xxxxxxxxxx/ssam/api/ using saved credentials
20/03/2019 11:37:21.765 INFO: Connect to server http://xxxxxxxxxxx/ssam/api/
20/03/2019 11:37:21.765 INFO: Set listener
20/03/2019 11:37:21.765 INFO: On start
20/03/2019 11:37:21.781 INFO: Call connect
20/03/2019 11:37:23.687 INFO: Refreshing oauth token
20/03/2019 11:37:24.265 INFO: Got new oauth token
20/03/2019 11:37:25.734 INFO: Server API version: 1.1
20/03/2019 11:37:25.734 INFO: Connection successful. Server id: http://xxxxxxxxxxxxx/ssam/api/
20/03/2019 11:37:25.734 INFO: Uploading package PAMO/PATH Malaria Survey
20/03/2019 11:37:25.750 INFO: Uploading app package PAMO/PATH Malaria Survey 63290 bytes
20/03/2019 11:47:47.203 ERROR: Error uploading package:
20/03/2019 11:47:47.203 INFO: Disconnecting from server
Re: Deployment Error
On the server, the api.log file located under the logs folder of csweb installation, you will find additional information of the failure. Can you send us the error info in the api.log and ui.log file?
Re: Deployment Error
Hi Savy,
This is what I got from the api log from my server...
This is what I got from the api log from my server...
Code: Select all
[2019-03-20 11:37:26] CSPro API.ERROR: Symfony\Component\HttpKernel\Exception\NotFoundHttpException: No route found for "PUT /apps/PAMO/PATH%20Malaria%20Survey" (uncaught exception) at /home/xxxxxx/public_html/xxxxxxx/ssam/vendor/symfony/http-kernel/EventListener/RouterListener.php line 176 {"exception":"[object] (Symfony\\Component\\HttpKernel\\Exception\\NotFoundHttpException(code: 0): No route found for \"PUT /apps/PAMO/PATH%20Malaria%20Survey\" at /home/xxxxxxxx/public_html/xxxxxx/ssam/vendor/symfony/http-kernel/EventListener/RouterListener.php:176, Symfony\\Component\\Routing\\Exception\\ResourceNotFoundException(code: 0): No routes found for \"/apps/PAMO/PATH%20Malaria%20Survey\". at /home/xxxxxxxxx/public_html/xxxxxxxxxx/ssam/vendor/symfony/routing/Matcher/UrlMatcher.php:98)"} []
Re: Deployment Error
Hi Josh and Savy,
I figured it out. It turns out that the forward slash (/) I was adding in the Package Application was the issue . After removing it, I was able to deploy my application without any trouble.
Thanks for all the help.
Singani
I figured it out. It turns out that the forward slash (/) I was adding in the Package Application was the issue . After removing it, I was able to deploy my application without any trouble.
Thanks for all the help.
Singani
Re: Deployment Error
Thanks for figuring that out. I was able to reproduce the problem on my server too by adding a / in the package name. We will add a check to prevent this in the next version.