Welcome Guest! To enable all features, please Login or Register.



Last Go to last post Unread Go to first unread post
#1 Posted : Friday, March 31, 2017 4:18:18 PM(UTC)


Groups: Manager, Tech Support, Administrators
Posts: 218

Was thanked: 12 time(s) in 12 post(s)

The Document Viewer demo application is setup to run under IIS Express when installed for the first time. Once your evaluation has completed and you are ready to deploy your application to your server, you will need to deploy to IIS. By default IIS is not setup correctly for the Document Viewer to function correctly on it. To get started you will need to properly enable certain IIS settings in order to get it working.

Out of the box, this project is configured for use with IIS Express. Just make sure that the IIS Express bit-ness value matches that of the current configuration. This can be accessed from your Visual Studio by going to Tools/Options/Projects Solutions/Web Projects and checking/unchecking the value of "Use the 64 bit version of IIS Express for web sites and projects" accordingly. The value must be unchecked for the Any CPU and x86 configuration and checked for the x64 configuration.

If you intend to develop with IIS, make sure the following settings are correct:

  • IIS 6.0 or later is installed.
  • In the "Windows Features" dialog, the following boxes are checked:
  • NET Framework 4.6 Advanced Series
  • ASP.NET 4.6
  • Internet Information Services
  • Web Management Tools
  • IIS 6 Management Compatibility
  • IIS Metabase and IIS 6 configuration compatibility
  • IIS Management Console
  • World Wide Web Services
  • Application Development Features
  • .NET Extensibility 4.6
  • ASP
  • ASP.NET 4.6
  • ISAPI Extensions
  • ISAPI Filters
  • Common HTTP Features
  • Default Document
  • Directory Browsing
  • HTTP Errors
  • Static Content
  • Health and Diagnostics
  • Custom Logging
  • HTTP Logging
  • Request Monitor
  • Tracing
  • Performance Features
  • Static Content Compression
  • Security
  • Request Filtering

After ensuring these settings are correct and creating the virtual directory in IIS, Application Pool settings must be updated as follows:

Make sure the new Application Pool has Enable 32-Bit Applications set to True if you are developing for x86. Also make sure the .NET CLR Version is at least v4.0.
Ensure that the Application Pool identity has read and write access to the cache directory set in local.config (the value of the lt.Cache.Directory setting).
If you do not modify these options, then IIS will use the built-in DefaultAppPool. This uses ApplicationPoolIdentity which by default does not have write access to the local hard drive and running the service with these options will result in errors.

We recommend creating a new Application Pool instead of changing the options of an existing one.

Here is a screenshot showing what should be turned on:


Edited by moderator Monday, February 24, 2020 10:32:51 AM(UTC)  | Reason: Not specified

Hadi Chami
Developer Support Manager
LEAD Technologies, Inc.


Try the latest version of LEADTOOLS for free for 60 days by downloading the evaluation: https://www.leadtools.com/downloads

Wanna join the discussion? Login to your LEADTOOLS Support accountor Register a new forum account.

You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Powered by YAF.NET | YAF.NET © 2003-2024, Yet Another Forum.NET
This page was generated in 0.049 seconds.