Category: Documentum

Custom DQL Query to show users logged in and out times.

1. To run a dql query first login to your content server.
2. Select IDQL for the repository
3. enter your username and password with dql access
4. run the query:
   • select event_name,user_name,time_stamp,session_id,user_id from dm_audittrail where event_name = ‘dm_connect’ and user_name not like ‘dm%’ and time_stamp between date(’06/30/2014′) and date(’07/08/2014′)
     union all
     select event_name,user_name,time_stamp,session_id,user_id from dm_audittrail where event_name = ‘dm_disconnect’and user_name not like ‘dm%’ and time_stamp between date(’06/30/2014′) and date(’07/08/2014′)order by 4,1
     GO
5. You will get the output in the cmd window.
6. If you wish to output the values to an excel/csv file you can run command via the command prompt with an output to csv file. To do this, run idql32.exe via command prompt
   1. Open the command prompt and type:
      • idql32.exe -u(username) -p(password) (docbase) >>c:\users\(username)\desktop\dqloutput.txt
      • idql32.exe -ujose -pMYPASS MYREPOSITORY>>c:\users\jderas\desktop\dqloutput.csv
   2. Run query
   3. All values will be saved in your dqloutput.csv file

Issue: When trying to load a file in Documentum EPFM you get the following error:

[DFC_CONT_CANT_ACCESS_FILE] Cannot access file //filserver/file.pdf

Unexpected critical error occurred whilst attempting to process this load

Solution:

1. Make sure the file exist and the location is correct
2. Check the extension and make sure it is correct.
   1. for example if on the file server the file is test.pdf and in your loading document it is listed as .PDF change the file name to match.
3. Retry loading the document.

Issue: When trying to search in Documentum you get the following error:

[DM_API_E_EXIST]error:Document/object does not exist

Solution: Make sure that the agent is running in DA

1. Log into DA
2. Expand Indexing Management
3. Select Index Agents and Index Server
4. Right click the index server and select start agent

When trying to load a document after validation in Documentum EPFM, you might come across the following error:

Unexpected Critical Error occurred whilst attempting to process this load

An error occurred during temporary file import

1. You will first want to check the load spreadsheet and make sure there are no validation errors that might make Documentum throw his error out.
2. If all documents are validated without any issues the issue is between the appserver and file server.
3. If you know where the file server is located make sure the folder and all subfolders have the correct permissions. If you don’t check this post to find out out. 
4. Specifically the folder should have the dmadmin account and the user uploading the file with full permissions.
5. If they do contain the rights the quickest way to test is to replace all child permission from the top level folder.
   • This will correct all permissions from the top level folder and down
6. Once you adjust the permissions then try loading the document again.

Issue: Need to create a new folder in EPFM.

Solution: You must create a new picklist value

1. Login to epfm with an admin account
2. Open project admin on the left nav bar
3. Go to > project configs > yourproject > picklist > thefolderyouwishtoaddto > then all values >
4. File new pick list value.
5. Once its created then you have to link it to the active value folder.
6. You can do that by selecting the new picklist value on the all values folder
7. Select file > copy to clipboard >
8. Go to the active values folder then select edit > link here.
9. Then create the new folder in the cabinet with the pick list value name

Once you have created a new report template you will then have to upload the new report. This is a continuation of my last post on how to modify an existing report.

Once you have the new .ecsfr package:

1. Log back into Documentum with an admin account
2. Go to Project Admin > Project Configs > Reports > Templates
3. Select File > import report template
4. Select the new report .ecsfr file
   • The type should be ECS Report
   • Format: ECSF Report Package
5. Once it is created then go to the types folder under reports
6. In this example we modified the Master Document Reports. Right click the Report type and select properties
7. Under templates select the edit link
8. Search for the name of new report you just uploaded
9. Add it to the list and select ok
10. Now you report is ready to be created.
11. Go to your reports folder in your cabinet.
12. Select file > new report
13. Create a new, and select the report type we just added the new report under
14. The report template should show the new report you just uploaded. Select next and edit all the properties you wish to add
15. Run report
    • If you get an error when running the report there is an issue with the modifications you made to the report.
      • Check the source code of the report and make sure the query gives the values you are trying to output.
      • Make sure the layout is correct and the report doesnt use any values that are not available

In this example I will be modifying the Master Documents Report. To modify a documentum report use the following steps:

1. Login to documentum and go to reports
2. Right click the Report you wish to modify and select export.
3. Save the package
4. You should see the filename.ecsfr
5. Using a file archiver unarchive – extract the package (I will be using 7-zip)
6. You’ll then see the a .jrxml file
7. 
8. The jrxml file is a jasper report file. You will need to download and install Jaspersoft Studio http://community.jaspersoft.com/project/jaspersoft-studio to view and edit the file
9. Once Jaspersoft Studio is installed then you can view and modify the the report
10. With Jaspersoft studio you can change the layout and modify what can be displayed.
11. There are 2 ways you can do this. If you are familiar with any reporting software you will notice jaspersoft is the same. You can modify the design and modify the source code
12. Using the source code view you can see in details the query the reports run
13. Once you are finished making the changes
14. You will need to use 7-zip to archive the .jrxml file back to the .ecsfr format.
15. Right click > 7-zip > add to archive > change the .zip to .ecsfr
16. That’s it!
17. To view how to upload the new report proceed to the next article

When trying to access the web front end for Documentum you might get the following error.

[DFC_DOCBROKER_REQUEST_FAILED] Request to Docbroker “ContentServerName:1489” failed

 

Typically this means that the appserver has lost the connection with the content server. You can check the content server Log files to see the errors.

Solution:

1. Check the all the services are running without any issues.
2. Check that the content server logs for any errors.
3. Restart both servers.

When loading a document within Documentum EPFM you might come across the following error:

No Content File can be found using the path in the cell

There can be a few errors occurring here…

The file is missing or path is incorrect:

1. Check that the file you are trying to upload is in the correct location that the content cell is pointing to.

Documentum cannot connect to the file server where you have the files located at:

1. Check that the application server can access the file server. (not sure what the file server is? See next option)
2. Ensure you can access both ways.
3. Ensure that you have the correct permissions when connecting to the server

I need to view or change the content location:

The content location is set in the RCF-schema file. It can be found in the <content_location> tags.

1. Export and edit your RCF-Schema file. Search for the content_location tag.
2. View/edit the server that is listed in the tag. (note that the path is case sensitive)
   1. If you edit the file make sure and set the lifecycle to Active
3. Map the file server to your appserver.
   1. If you appserver is Linux make sure that once you mount the cifs share you are able to browse the directory.
4. If you edited the RCF file be sure and re-read the rcf-configuration
   1. You can do this in EPFM > tools > Re-read RCF Configuration

After a server reboot your searches might not work and/or you might receive an error:

xPlore Watchdog Service failed to ping application IndexAgent. Instance: XPLORE_9200_IndexAgent  Cause:http://XPLORE:9200/IndexAgent is not reachable. Connection refused: connect

1. First check that the xplore index server is running.
2. Make sure the services are running on the server:
   1. Documentum Indexagent
   2. Documentum xPlore PrimaryDsearch
   3. Documentum xPlore Watchdog -C xPlore
3. Then make sure that the agent is running in DA
   1. Log into DA
   2. Expand Indexing Management
   3. Select Index Agents and Index Server
   4. Right click the index server and select start agent