Web Deploy for .Net 4

From Wiki-eostar.com
Jump to: navigation, search

These instructions are for IIS 7. For instructions for IIS 6, see Web.Config and Handheld Connections For eoMobile 2009.

Role / Feature Requirements for Windows Server 2012 R2 for eoStar Web Services

From the Service Manager, click Manage > Add Roles and Features. Click Next until you reach the Server Roles page. Scroll down to Web Server (IIS) and ensure that the following are selected.

Note: Additional features may be installed, but the list below MUST be installed for eoStar Web Services to properly function.
  • Web Server
  • Web Server
  • Common HTTP Features
  • Default Document
  • Directory Browsing
  • HTTP Errors
  • Static Content
  • Health and Diagnostics
  • HTTP Logging
  • Performance
  • Static Content Compression
  • Security
  • Request Filtering
  • Application Development
  • .NET Extensibility 4.5
  • ASP.NET 4.5
  • ISAPI Extensions
  • ISAPI Filters
  • Management Tools
  • IIS Management Console
  • Management Services

Web Deploy


Web Deploy is a requirement for the new Deployment method, download from the link above (x64 or x86 depdning on your platform, DO NOT select the WebPI option), Install, then follow the procedure below.

If you're upgrading Web Deploy to version 3.6, Web Server (IIS) > Management Tools > Management Services gets installed in order to see the Deploy UI in IIS Manager.

Web Deploy Installation

Below are screenshots for the Web Deploy installation process for use with the newer installation packages for web services and web sites (the .ZIP files instead of the .MSI).

Web Deploy can be downloaded from the link found in the #Web Deploy section.

Web Deploy 1.png

Web Deploy 2.png

Web Deploy 3.png

Web Deploy 4.png

Web Deploy 5.png

Web Deploy 6.png

Web Deploy 7.png

Installing eoNetService using the Web Deployment method for IIS7 & 7.5

Open IIS Manager, expand it open and select “Default Web Site”, then right click on “Default Web Site” choose Deploy>Import Application

NOTE: Ensure you've selected "Default Web Site" before choosing Deploy, if you receive an error during installation telling you "The selected package contains applications, which cannot be installed at the server level. Select a site and install the package within the site." then "Default Web Site" was not selected prior to Deployment.

IMPORTANT: When deploying over an existing install, choose "Yes, delete all extra files and folders on the destination that are not in the application package."

Web deploy 1.jpg

Choose the .ZIP file for the Web service your trying to install (eonetservice.zip in this instance).

Web deploy 2.jpg

This screen will display the contents of the package, click Next.

Web deploy 3.jpg

This screen allows the user to change the Application path, Physical Path, and Connection string, do not change the values from here! Click Next.

Web deploy 4.jpg

Installation Progress…

Web deploy 5.jpg

Installation Summary… Click Finish.

Web deploy 6.jpg

Now that eoNetService has been installed, it’s time to configure the connection string.

Configuring and Testing the web server (eoNetService)

Click “Default Web Site” and under ASP.NET double-click “Connection Strings”.

Web deploy 7.jpg

In the Actions panel, click Add.

Web deploy 8.jpg

Within the “Add Connection String” window, fill in the following fields, then click Ok.

Web deploy 9.jpg

  • Name: The name of the connection string, to be used on the mobile devices
  • Server: The name of your SQL Server serving an eoStar database
  • Database: The name of your eoStar database
  • Credentials: Most customers will utilize SQL credentials, select the radio button, click “Set” and specify a username and password of a SQL User (Not a Windows or AD User ID)

Once the connection string is configured, it’s time to test it to ensure its working properly.

Inside IIS Manager, expand “Default Web Site”, and select “eonetservice” at the bottom of the page, select “Content View”.

Web deploy 10.jpg

When in “Content View”, find “h3.asmx” in the list, right click and choose Browse.

Web deploy 11.jpg

If everything is working properly you’ll be greeted by the H3 page.

Web deploy 12.jpg

From this screen we can see that the web service and all its underlining components are working, next thing to test is the connectivity from the web server to the SQL Server, to test this, click the Ping hyperlink.

In the “Login” field, enter the name of your connection string from the earlier example, followed by a period and a handheld number assigned to a user (done from within eoStar). In this instance we’re testing handheld number 1 with my connection string named “Test”.

In the “Password” field, enter the access password (if any) of the user who is assigned to this handheld (Records>Employee>Records More Panel).

Once these fields have been specified, click Invoke.

Web deploy 13.jpg

If all is well, you’ll receive a “Hello” back from the eoStar database.

Web deploy 14.jpg

Once we’ve ensured the IIS Server is serving pages properly, and we’ve verified with “Ping” that our IIS Server can talk to our SQL Server, administrators can utilize this same page to test and ensure your Firewall is working properly and serving pages, simply modify the URL and in place of “localhost”, enter your External IP address.

If you run into any errors, please read the message as many errors are self-explanatory, if not, please look through this list and see if your message matches any of those and follow the suggested actions.

Troubleshooting: Error 404.2/ISAPI and CGI Restriction List

This error can occur after using the Deployment method to installing any of the web service programs. The instructions that show in the error message will solve the problem. This is a visual walkthrough of those instructions:

Web deploy error 1.jpg

Web deploy error 2.jpg

Web deploy error 3.jpg

Web deploy error 4.jpg

Web deploy error 5.jpg

Web deploy error 6.jpg

Troubleshooting: Error Error 500.21 (500) - Internal Server ErrorHandler

This error occurs after re-installing IIS and the ASP.Net is not recognized as being registered.

2016-11-08 8-26-41.png

Find the file path "Microsoft.Net\Framerwork64\version" 2016-11-08 8-45-41.png

Open Command Prompt

  • Run cd "File PAth"
  • Run "aspnet_regiis -i"

2016-11-08 8-34-08.png