Browsing Solutions For Dovetail Mobile Agent

  • .Net Web application returns HTTP Error 500.19 - Internal Server Error

    After installing a .Net based web application you may see the following error: HTTP Error 500.19 - Internal Server Error The requested page cannot be accessed because the related configuration data for the page is invalid. This is likely happening because your web application's application pool is not using the correct version of the .Net Framework. When the web application is installed a new application pool for it is created. The default settings of the application pool will come from IIS not the installer. When the application you are installing requires .Net 4.0 and your server has IIS configured to use .Net 2.0 by default you will need to reconfigure the application's app pool to use the correct version of the .Net framework.

  • Configuring the session timeout in Dovetail Mobile

    How to configure session timeouts in Dovetail Mobile.

  • Dovetail SDK : Setting the session timeout length using .Net.

    Dovetail SDK sessions have a default timeout of 20 minutes. It is often desirable to change the length of this timeout period.

  • What is the maximum upload file size in ASP.NET applications? How to increase it?

    What is the maximum upload file size in ASP.NET applications? How to increase the max upload file size in ASP.NET applications, including Dovetail Mobile. Error messages may include: Exception Details: System.Web.HttpException: Maximum request length exceeded. HTTP Error 404.13 - Not Found The request filtering module is configured to deny a request that exceeds the request content length.

  • Request timed out for new instance of Dovetail Mobile

    In a new installation of Dovetail Mobile, there was a chain of events that led up to an exception. The stack trace only showed one message: System.Web.HttpException: Request timed out. The first issue was that the license was not installed correctly, and this error message was shown when the application was first tested: (5246) Could not obtain license productId 1500 as all user and grace license limits are full or there is no license present for this product. The LicenseInstaller utility was run to add the Mobile product license to the database, and any subsequent attempt to load Dovetail Mobile showed the "request timed out" exception.

  • Platform Guide: List of supported platforms and versions

    Where can I find details on the list of supported platforms for Dovetail products? Keywords: Microsoft SQL Server MSSQL Oracle requirements operating system windows iis .NET Clarify Amdocs

  • Refreshing Dovetail SDK Caches

    Applications which use Dovetail SDK (which are pretty much all applications shipped by Dovetail Software) cache commonly used data to avoid repeated lookups in to the database. Each cache is loaded once, during application initialization. It is common to have objects that are cached get modified during the application's lifespan. When this happens the outdated cache should be refreshed. This article will show you how to refresh the caches at the application level and programatically in your own applications using the Dovetail SDK.

  • How many processors should my Dovetail application server have?

    A customer recently asked if they should provision multiple CPUs on virtual machines hosting Dovetail applications. Dovetail web and service applications can utilize more than one processor to get more work done concurrently.

  • Using Dovetail Software products with 32bit Oracle drivers can cause ORA-12154 error

    When running a Dovetail Product that is using 32bit Oracle drivers, a user may encounter a message as follows: ORA-12154: TNS:could not resolve the connect identifier specified The above message should be displayed to the user, or located in log files for the product being used. As an example, Dovetail Schema Editor shows the following: "Error Occurred : Database settings in "Default.SchemaEditor" are not valid. Please confirm that database type and connection string are correct." Within the SchemaEditor.log file, the following exists: 2010-10-12 14:44:51,259 ERROR Dovetail.DataDictionary.Persistence.Database.SqlHelperAdapter - Database connection could not be made: ORA-12154: TNS:could not resolve the connect identifier specified System.Data.OracleClient.OracleException: ORA-12154: TNS:could not resolve the connect identifier specified This issue is not specific to Dovetail applications, but is a known Oracle bug with respect to the path used for Oracle 32 bit software. Typically this occurs in 64bit OS environments where (by default) Windows likes to install 32-bit apps into the C:\Program Files (x86)\... folder. The problem is in the C:\Program Files (x86)\ directory name - specifically, the parenthesis. Calls made to the 32bit drivers fail because the calling program information is passed to Oracle, where it takes the () as a special command. Oracle Article ID 334528.1 provides detailed information (login required): https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=PROBLEM&id=334528.1

  • Internet Explorer 8 (IE8) compatibility and support

    Does Dovetail support Internet Explorer (IE8)?

  • AspNetHostingPermission exception occurs for a web application downloaded from Dovetail

    When setting up a ASP.Net web application using .Net assemblies you downloaded from Dovetail using the Internet. When using Windows Explorer to extract zipped files you may see this exception. Security Exception Description: The application attempted to perform an operation not allowed by the security policy. To grant this application the required permission please contact your system administrator or change the application's trust level in the configuration file. Exception Details: System.Security.SecurityException: Request for the permission of type 'System.Web.AspNetHostingPermission, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed. Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

  • Opening Dovetail.Agent.Mobile.sln throws an error: The application for the project is not installed.

    Opening Dovetail.Agent.Mobile.sln using Visual Studio 2008 throws an error: One or more projects in the solution could not be loaded for the following reason(s): The application for the project is not installed. These projects will be labeled as unavailable in Solution Explorer. Expand the project node to show the reason the project could not be loaded.

  • Cannot open the Dovetail Mobile solution using Visual Web Developer 2008 Express

    Dovetail Mobile (Agent Lite) comes with source code used for customizing the application. This application is developed using Visual Studio 2008. While it is ideal to obtain Visual Studio 2008 and install SP1 for the best development experience, it is possible to work with the solution using a free IDE from Microsoft Visual Web Developer (VWD) 2008 Express. http://www.microsoft.com/express/vwd/ When loading the Mobile solution in VWD 2008 you will get a few error notices. The first one will be: The project type is not supported by this installation. This error prevents the Mobile web project from loading.

  • Search results do not link to the correct page.

    It is possible to have documents in your search index that search client s do not know how to view. When this happens the search consuming application (e.g. Dovetail Agent) should do its best to communicate to the user that it doesn't know what to do. For example if you are using Dovetail Mobile and you are indexing Bugs in your search index. It is possible to have search results come back for bugs. Dovetail Mobile does not have a way to view bugs. It handles this by displaying the search results as normal but with a link to a page informing the user that there is no way to view this object.

  • Hosting Dovetail web applications build with Asp.Net MVC using IIS5 on Windows XP

    IIS 5 is not officially supported as a deployment platform for Dovetail web applications built on Asp.Net MVC. These applications currently include: Dovetail Mobile Agent Dovetail Seeker (as of version 1.2) It is possible to use IIS 5.1 on Windows XP do development testing of these applications.

  • Is Dovetail Mobile Agent compatible with BlackBerry devices?

    Is Dovetail Mobile Agent compatible with BlackBerry devices?

  • Dovetail Mobile Agent web pages are not being refreshed on BlackBerry phones

    Users of Dovetail Mobile Agent having Blackberry phones can have problems with web pages being cached locally and not getting refreshed. It appears that the Blackberry web browser does not check to see if a page has been updated.

  • Dovetail Mobile Agent on IIS 6 - pages return a HTTP 403 or 404 error

    Any page visited returns a HTTP 403 Forbidden or 404 Page not found error.