User Guide > How to Work with... > Common Operations > Viewing > Viewing Using ASP.NET > Troubleshooting ASP.NET |
If you're running into issues while installing and configuring ASP.NET for the first time on a particular system, see the New to ASP.NET? section of "Viewing Using ASP.NET". |
This topic covers some of the Frequently Asked Questions (FAQ) of using ImageGear with ASP.NET:
If you are receiving an "80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG))." error while trying to use the LDK on a website created through IIS, it is likely because of a platform conflict (x32 vs x64). To fix it, try checking (or unchecking) "Enable 32-Bit Applications" for the App Pool associated with the website.
Please check the Windows Features to ensure that you have WCF and HTTP Activation installed for ImageGear Services to work.
In an ImageGear .NET web application, you will need to define the location of the images and annotations directory in the storageRootPath and artStorageRootPath configuration properties (see Built-In SqlImageDataProvider).
Currently, storageRootPath and artStorageRootPath do not work with a network drive path "\\SERVER-NAME\sharefilename".
The workaround for this is to create a Symbolic link from a local directory to the network drive directory.
To create a symbolic link:
> mklink /d "local path" \\SERVER-NAME\sharefilename
storageRootPath="local path"
artStorageRootPath="local path"
If you are using Microsoft Visual Studio, watch the output tab from the Debug view and see if any ImageGear.Web messages appear. If not, reconfigure the web.config file as outlined in Error Logging Configuration Settings. Try enabling verbose logging by setting the switch named imageGearSwitch value to Verbose. For example:
<switches >
<add name="imageGearSwitch" value="Verbose" />
</switches >
The IIS emulation package should have started the ASP.NET Development Server, and you should see the icon on the right side of the toolbar at the bottom of the screen. If not, also check the following:
There are numerous reasons why an image may not appear. Besides using a common web debugger, the ASP.NET controls are designed to generate logs. See Error Logging Configuration Settings for information on setting up logging. Please contact Accusoft for assistance in analyzing the log (see Getting Support).
This is done to give the web browser user a more responsive feel. A low resolution full-sized image is first loaded, which is fairly quick and responsive. Then, a higher resolution image will typically follow for the portion of the image being viewed in the client viewer. This higher quality image can be the one showing a full image at better resolution or one or more tiles showing a portion of the image, depending on how far zoomed in the image may be. When you scroll around or zoom into the client viewer, you may see the previously loaded low resolution view for a moment while a better quality image gets requested and then subsequently displayed.
Please be sure to copy the license strings exactly. Even trailing spaces in quoted strings must be applied. Also, with IIS services, it sometimes is necessary to restart or recycle the Application Pool for which the hosted ASP.NET application resides and not just the IIS service itself.
This issue can arise with multiple IIS app pools writing to the same folder and ASP temp directory. When one website creates files inside, others may not be able to read them. Try the following: