Troubleshooting Assets

This section explains how to fix problems that may occur with Ektron assets.

Cannot drag and drop assets into Ektron.

Cannot drag and drop assets into Ektron

Symptom: You cannot drag and drop assets into Ektron.

Resolution: See Removing Front Page Server Extensions.

File opens instead of generating an upload notification

File Opens Instead of Generating an Upload Notification

Symptom: When a user drags a document, the file opens in the browser instead of generating an “Uploading” notification.

Resolution: Ektron KB Article: http://dev.ektron.com/kb_article.aspx?id=14204

Target directory already exists

Target Directory Already Exists

Symptom: While trying to drag and drop an asset, an error message appears: The target directory already exists.

Resolution: Check the impersonate element of the web.config file. If it is set to true, make sure the anonymous access account has at least write access to the dmdata and assets directories.

Cannot update published DMS documents

Cannot Update Published DMS Documents

Symptom: When you try to publish DMS documents, Ektron sometimes does not allow them to update.

Resolution: Make sure your production server is not running Windows XP. You cannot use XP as a production server for DMS.

Removing aspnet_isapi.dll from the list of wildcard application maps

Removing aspnet_isapi.dll from the List of Wildcard Application Maps

Symptom: When you try to upload an asset, you get the error message “Failed to upload documents.”

Cause: Remove the aspnet_isapi.dll from the list of Wildcard Application Maps.

Resolution:

  1. Open IIS.
  2. Go to your Ektron Web site.
  3. Underneath the Web site, click Asset Management > dmdata.
     

  4. Right click dmdata and choose Properties.
  5. Click the Virtual Directory tab.
  6. Click Configuration.
  7. Look in the Wildcard Application Maps area. If aspnet_isapi.dll appears, remove it.
     

  8. Click OK.
Using Microsoft Windows Server 2003 as a client (Web folders setup)

Using Microsoft Windows Server 2003 as a Client (Web Folders Setup)

Symptom: You receive the following error message:

Windows Server 2003 no longer ships MSDAIPP.DLL, thus connecting to an FPSE server through Webfolders, is no longer possible.

Resolution: Per MS Licensing, you can obtain webfldrs.msi from any down-level OS, or any Office product that shipped before Windows2003 (not Office 2003) and install the WebFolders client. Doing so will keep you compliant with licensing.

Installing WebFolders from Office 2003 is only allowed if you have an Office 2003 license for each Windows2003 server you plan to install WebFolders on.

Web folders setup for Microsoft Windows Server 2003

Web Folders Setup for Microsoft Windows Server 2003

NOTE: You only need to run the Web Folders Setup if there is a problem during the install. The Ektron install performs the setup when needed.

The MSDAIPP.DLL is no longer shipped with Microsoft Windows Server 2003, making communication with Web folders impossible. To correct this, Ektron setup runs the Web folder setup when it detects Microsoft Windows Server 2003.

The following steps explain installing Web Folders. You will need to obtain a copy of the webfldrs.msi file.

  1. Double click the webfldrs.msi file. The Web Folders install screen appears.
     

  2. Click Next to continue. The Web Folders Identity dialog box appears.
     

    1. Add your Name.
    2. Add your Organization.
    3. Click Next.
  3. The Web Folders Product ID dialog box appears displaying your product ID number.
     

  4. Click Next. The Web Folders Selection Choice dialog box appears.
     

    • Complete—installs all components.
    • Custom—you choose the components to install.
    • Typical—installs the most frequently used components.
  5. After making a selection, click Next. The Verify Ready All dialog box appears.
     

  6. Click Install Now. The Action dialog box appears. The Setup is installing Web folders.
     

  7. The We Are Done dialog box appears. Click OK.
ERRMSG: AssetManagement error: failed to save asset

ERRMSG: AssetManagement error: Failed to save asset

Symptom: After recently moving the ASM database to a new SQL server that has never hosted an ASM database, the following error appears while adding a DMS asset.

AssetManagement error: Failed to save asset. 
Internal Message: RAISERROR could not locate entry for error 2000000002 in sysmessages. at 
Ektron.ASM.Documents.Asset.Create(enAssetStatus state) at 
Ektron.ASM.Documents.AbstractAssetManagement.Create(AssetMetaData 
  assetMetaData, enAssetStatus state) at 
Ektron.ASM.PluginManager.PluginHandler.Create(AssetMetaData 
  assetMetaData, enAssetStatus state) at 
AssetManagement.AssetManagementService.Create(AssetMetaData 
  assetMetaData, enAssetStatus state) at 
Mojave.AssetManagementProxy.Create(AssetMetaData assetMetaData, 
  enAssetStatus state) at 
Ektron.Cms.DataIO.EkContentRW.AddContentv2_0(Collection ContObj) at 
Ektron.Cms.EkException.ThrowException(Exception ex) at 
Ektron.Cms.DataIO.EkContentRW.AddContentv2_0(Collection ContObj) at
Ektron.Cms.Content.EkContent.AddNewContentv2_0(Collection ContObj)

Cause: During the creation of the ASM database, a total of 7 messages are written to the sysmessages table in SQL Server’s master database. Each installation of SQL Server has its own master database and, in a typical move from one location to another, changes to the master database are not brought over.

If the ASM database was moved, and these messages are not in the sysmessages table in the new location's master table, the above error appears instead of a standard error message.

Resolution: Run this set of SQL scripts against your database. They add appropriate messages to the sysmessages table in the master database.

/********************************************************************************/
sp_addmessage 2000000001, 10, N'Error in %s: Error %d inserting into %s. %s',
  US_ENGLISH, FALSE, REPLACE
go
/********************************************************************************/
sp_addmessage 2000000002, 10, N'Error in %s: Insert into %s returned %d rows. %s',
  US_ENGLISH, FALSE, REPLACE
go
/********************************************************************************/
sp_addmessage 2000000003, 10, N'Error in %s: Failed creating record because
  primary key already exists. %s', US_ENGLISH, FALSE, REPLACE
go
/********************************************************************************/
sp_addmessage 2000000004, 10, N'Error in %s: Error %d updating into %s. %s',
  US_ENGLISH, FALSE, REPLACE
go
/********************************************************************************/
sp_addmessage 2000000005, 10, N'Error in %s: Update into %s returned %d rows. %s',
  US_ENGLISH, FALSE, REPLACE
go
/********************************************************************************/
sp_addmessage 2000000007, 10, N'Error in %s: Error %d deleting into %s. %s',
  US_ENGLISH, FALSE, REPLACE
go
/********************************************************************************/
sp_addmessage 2000000008, 10, N'Error in %s: Delete into %s returned %d rows. %s',
  US_ENGLISH, FALSE, REPLACE
go

This snippet utilizes the sp_addmessage stored procedure from the master database, which adds the appropriate messages to the correct table.

NOTE: Although it is possible to recode these as an INSERT statement that can run directly against the sysmessages table, that procedure is not recommended.