Error publishing to web api to remote server

Resolved Error publishing to web api to remote server

Issue

Votes

Undo

Simone Olianti
SnapObjects
Monday, 1 July 2019 09:32 AM UTC

Hi there, following the "Create Web API" tutorial i've been able to create my first SnapDevelop web api using an ODBC SA data source adatped to my db. Everything working fine when i run the app on localhost from snapdevelop ide and i'm able to access it from my Powerbuilder dw using RESTClient (wow! :D )

Anyway when i try to deploy and publish the app to my remote web server, despite i've followed the deploy tutorial, i still get an error "unable to connect to the remote computer". On the server firewall is down, IIS looks ok, only thing is that it's running on a WIndows 10 Pro machine so i really don't know if maybe i missed something during the configuration.
Any ideas? is there a way to deploy the app and copy it manually to the web server?

tia,

Simone

Accepted Answer

Logan Liu @Appeon Accepted Answer Pending Moderation

Tuesday, 2 July 2019 02:00 AM UTC
SnapObjects
# Permalink

Hi Simone,

If your remote web server is not a Windows Server, please use File Sysem instead of Web Deploy for deployment:

"Windows Server 2012 or 2016 is recommended. If your operating system is Windows 10, for example, you can use File System, rather than Web Deploy, to publish your project to your local host."

https://www.appeon.com/support/documents/appeon_online_help/snapdevelop2019/publish/index.html

Regards,

Logan

Comment

Simone Olianti
Tuesday, 2 July 2019 07:39 AM UTC

Thank you Logan, been able to make it work using file system

Helpful 0

There are no comments made yet.

Responses (2)

Marco Meoni Accepted Answer Pending Moderation

Monday, 1 July 2019 11:34 AM UTC
SnapObjects
# 1

Hi Simone,
I havent tried it yet, but if Windows sw requirements are same as .NET Web Service deployment to a remote server, you need to undergo following checks (copy&paste from .NET WS and assmebly targets):

You can deploy directly to a mapped server only if the server is in the same domain or workgroup as the development computer. In addition, you must add the development computer user's Windows login ID as a member of the Administrators group

HTH

Comment

There are no comments made yet.

Page :
1

There are no replies made for this question yet.
However, you are not allowed to reply to this question.

Please login to post a reply

You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here. Register Here »

Forgot Password?

We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.