Home     Products      Support      Corporate     Sign In 
Support Knowledge Base, Article 906
all versions
Basic Troubleshooting Steps for XFile

Using an intelligent client, such as XFile, adds another layer of complexity to troubleshooting a web application. When experiencing problems, you need to determine where the issue lies.

  1. Is it server-side or client side?
  2. Is the problem with XFile or FileUp? (if FileUp is used)
  3. Is the problem with XFile specifically, or does it occur without XFile?

Additionally, web developers may be accustomed to seeing the server response, including server-side errors, displayed directly in the browser. Since XFile receives the server response, you need to remember to take steps to display this response in order to see any server side error messages.

This article will explain the basic troubleshooting steps you should take when you suspect you have a problem with XFile.

Article Index:

  1. Find out if you are distributing the latest version of XFile.
    It is possible that the problem you are experiencing has been identified as a bug and has been corrected in a subsequent release. For a list of new features and bug fixes in each version, please see the
    Version Differences page on our website.

  2. Determine if the client is running the same version you are distributing.

    An important thing to determine with XFile is what version the client is running compared to the version that is available through your web application. There may be a discrepancy.

    When the browser encounters an object tag that instantiates XFile, it checks to see if the XFile CLSID can be found in the client's registry. If the CLSID is located, the next check performed is on the version of the associated dll. If a version has been specified in the <OBJECT> tag, the browser will make sure that the version of the dll registered on the client is at least as high as the one specified in the HTML. If the CLSID cannot be located, or if the version of the local dll is too old, the browser will make a request for the cab file so that it can obtain the dlls and register them on the client.

    Because of this behavior, your client could be running a version that does not match. The consequences of this are as follows:

    • The version is older than what you are distributing. A property or method that you are using in your application may not be supported in an older version of XFile.
    • The version is from the SoftArtisans signed cab. The SoftArtisans signed cab file contains different dlls than what you may want to use. Because these dlls are signed by SoftArtisans, these dlls warn of impending uploads and downloads.
    • The version is an expired evaluation version. This it the most easily identifiable situation, as XFile will notify the user that it is expired and will fail to upload or download.

    All three situations can be prevented by forcing a client-side upgrade by specifying the lastest version of XFile in the <OBJECT> tag. In any release, the retail version has a higher version number than the evaluation version. The unsigned dlls also have a higher version number than the SoftArtisans signed dlls.

  3. Determine if the problem behavior is client-side or server-side.

Created : 7/22/2005 5:26:55 PM (last modified : 7/22/2005 5:26:55 PM)
Rate this article!