Javascript Popup – Documentum DAM and WebTop

The credit for the solution goes to two people who work with me – Yih Wern and Su Sheng.

Problem: When the user goes to either Webtop or DAM URL, IE launches a separate popup window with the following messages:

appintgevents.js: AppIntgProcessEvent did not handle aiEvent(event=ShowDialog_,_id=invoker_,_title=Content Transfer Service_,_height=130_,_width=440_,_sizepreference=false)
appintgevents.js: AppIntgProcessEvent did not handle aiEvent(event=ShowBusyCursor)
appintgevents.js: AppIntgProcessEvent did not handle aiEvent(event=ShowBusyCursor)
appintgevents.js: AppIntgProcessEvent did not handle aiEvent(event=ShowBusyCursor)
appintgevents.js: AppIntgProcessEvent did not handle aiEvent(event=ShowBusyCursor)
appintgevents.js: AppIntgProcessEvent did not handle aiEvent(event=ShowBusyCursor)
appintgevents.js: AppIntgProcessEvent did not handle aiEvent(event=ShowBusyCursor)

This problem is irritating as the messages keep appearing repeatedly and the popup window is refreshed. In some extreme cases, the popup prevents people from logging in or viewing documents.

Solutions:
There seem to be two solutions.
1) If the user has Google toolbar installed, it could cause this issue.  You can test this by uninstalling the Google toolbar.  Or you can recommend the user to use older Google Toolbar.
2) The second solution is related to IE7  which tries to access a page – runonce.aspx.  This seems to fail for some browsers and leaves the registry in an inconsistent state.  To fix this you can do the following :  (Suggested by Yih Wern)
Run Registry.exe
search for: HKEY_CLASSES_ROOT\TypeLib\{EAB22AC0-30C1-11CF-A7EB-0000C05BAE0B}\1.1\ZERO\win32  (WordPress is not displaying slash-zero.  Replace ‘ZERO’ with a numeric ‘0′)
Change the (Default) value from C:\WINDOWS\system32\shdocvw.dll to C:\WINDOWS\system32\ieframe.dll
Restart your IE browser.

The full thread is here – http://www.google.com/support/forum/p/Toolbar/thread?tid=1b384f23ae01da52&hl=en&fid=1b384f23ae01da52000462aedade69c6

UCF Challenges – Less common ones

The user is unable to use UCF while viewing existing documents or creating new documents.

A message will be displayed (in IE7) – Your browser does not support Java.

Causes and Solution:

1) Verify that the user has MS JVM or Sun JRE installed correctly on his PC.  I have seen situations where the user installed Sun JRE, set IE to use this JRE and a few days later, deleted the C:\Program Files\Java files.
FIX: Reinstalled the JRE
2) The user has disabled the IE Add-ons needed to launch the applets.  This is tricky because we usually don’t look here.
FIX: Verify that the addins are enabled from the “Manage Add-ons” console of IE

Thumbnail Server and McAfee Anti-virus Port Clash

I recently installed Documentum Thumbnail Server on a Windows box and I had strange problem.   The thumbnail server showed status as “Started” in the Windows Services console.  But the DAM refused to show any thumbnails.  

 To test if the Thumbnail server was running correctly,  I used IE to hit this URL: http://localhost:8081/thumbsrv/getThumbnail? 

If the thumbnail server was running allright, IE should display a default document icon.  Instead I saw the logs of my McAfee Anti-virus.  This meant that McAfee was using the port:8081 which is the default port used by Thumbnail server.

Fix: 

 Since Thumbnail server uses Tomcat internally,  I had to change the port to 8082. 

a) Using Notepad, open the server.xml in the  D:\Documentum\product\5.3\thumbsrv\container\conf
b) Search for “<!– Normal HTTP –>” and in this section for connectors,  change the port number <parameter name=”port” value=”<newport>”/>  I used 8082 successfully.
c) Restart the thumbnail server
d) Test using http://localhost:<newport>/thumbsrv/getThumbnail? 

Update the configuration of the thumbnail file-store to change the base_url attribute. 
a) Open Documentum Administrator (DA), 
b) Look for  the file-store – “thumbnail_store_01″
c) View properties and update the base url.
d) Restart the docbase
e) Open DAM and test if thumbnails are being displayed correctly