InputAccel and PIXDFLTN.dll

I uninstalled InputAccel 6.x the other day and tried to reinstall it. I got an error “could not find PIXDFLTN.dll”. I dutifully went to EMC’s Powerlink site and searched for “pixdfltn.dll” and found two solutions: the first said to uninstall everything, even the database server and start over again, the second said to find this dll in /windows/system32 folder of another server and copy it over. Neither of these worked. 

What I ended up doing was looking in the /client folder of the IA installation folder and found the correct PIXDFLTN.dll and everything was good again. Now EMC support, it wasn’t that hard to tell us the correct way to deal with this, was it?

Documentum Java Method Server Recovery

Issue:

In the Dev Env. where multiple users could be restarting the docbase services, the method server service could get hung. In this case please try the following process to try to fix the issue.

Symptoms:

After trying to start the Documentum Java Method Server service, the service stops after a while.

Trouble Shooting Steps to Follow:

1.       Look at the following logs for any Errors (note the timestamp)

a.       JBoss location: C:\Documentum\jboss4.3.0\server\DctmServer_MethodServer\log

                                                               i.      server.log, boot.log

b.      Application location: C:\Documentum\jboss4.3.0\server\DctmServer_MethodServer\logs

                                                               i.      acs.log, serverApps.log, bpm.log, bam_server.log

2.       Look at the docbase logs in c:\Documentum\dba\log.

a.       Note the docbase restart timestamps

3.       Look at processes through the Task Manager

a.       Look for java.exe processes which are running C:\Documentum\jboss4.3.0 processes

b.      Note: there will be “mthdsrv.exe” processes running. These are Content Server processes, not to be confused with JBoss.

c.       Kill any of the java.exe processes running in jboss4.3

4.       Start the Documentum Java Method Service

5.       If this doesn’t work, try restarting the docbase, then start the Documentum Java Method Service

6.       If this doesn’t work, restart the server

7.       Check the logs for app deployments