Sometimes the DB2 Database can be a very trash application

Sometimes the DB2 Database can be a very trash application

Mainly   for the performance an in the uninstall tasks,

To workaround the issue you can run the scripts to install FEM
manually.

From a command line, run the following commands (adjust path as
necessary for your system):

cd c:\Program Files
(x86)\IBM\FileNet\ContentEngine\tools\configure
configmgr_cl generateConfig -task configureDotNetAPI -profile
dotnetclient -silent
configmgr_cl execute -task configureDotNetAPI -profile
dotnetclient -silent
configmgr_cl generateConfig -task registerEM -profile
dotnetclient -silent
configmgr_cl execute -task registerEM -profile dotnetclient
-silent

After a lot or reboots and reinstall of the system, finally we have fix the issue, 

also the following was useful: http://www-01.ibm.com/support/docview.wss?uid=swg1PJ39277

Troubleshooting the IBM FileNet Enterprise 

Manager Installation

Technote (troubleshooting)

http://www-01.ibm.com/support/docview.wss?uid=swg21504731

Problem(Abstract)

IBM FileNet Content Engine installer displays the message "Install Complete With Errors". 

Attempts to launch the Content Engine Enterprise Manager.msc result in the error message shown below.

Symptom

MMC could not create the snap-in.

Cause

Microsoft Windows (64-bit) Operating System fails to register the following IBM FileNet 

Enterprise Manager (EM) DLLs; FNK_ACLEditor.dll, FNK_EnterpriseManager.dll, using the

 Windows command line tool regsvr32.exe.

Environment

Microsoft Windows 7, Windows Server 2008 R2; 64-bit Operating System

Diagnosing the problem

IBM FileNet Content Engine (CE) installer runs with both options; .NET Clients and FileNet

Enterprise Manager, selected. The installation of IBM FileNet Content Engine finishes, 

but some errors occur during the install. Review the installation log located by default in:

c:\Program Files (x86)\IBM\FileNet\ContentEngine\ce_install_log_5.0.txt

and confirm errors like the following are reported:

Execute Script/Batch file: Remove profiles\dotnetclient

Status: ERROR

Additional Notes: ERROR - java.io.FileNotFoundException: 

C:\Users\p8admin_prod\AppData\Local\Temp\2\032010.tmp\executeScriptTmp.bat

 (The process cannot access the file because it is being used by another process.)

Execute Script/Batch file: Configure .Net API

Status: ERROR

Additional Notes: ERROR - java.io.FileNotFoundException: 

C:\Users\p8admin_prod\AppData\Local\Temp\2\032010.tmp\executeScriptTmp.bat 

(The process cannot access the file because it is being used by another process.)

Execute Script/Batch file: Configure FEM

Status: ERROR

Additional Notes: ERROR - java.io.FileNotFoundException:

 C:\Users\p8admin_prod\AppData\Local\Temp\2\032010.tmp\executeScriptTmp.bat

 (The process cannot access the file because it is being used by another process.)

Resolving the problem

Manually run the commands that were attempted to be executed by the script, 

after the install has completed. The commands will generate a profile in FileNet 

Configuration Manager and perform the required .dll registrations.

1. From a command line, run the following commands (adjust path as necessary for your system):

cd c:\Program Files (x86)\IBM\FileNet\ContentEngine\tools\configure

rmdir /S/Q profiles\dotnetclient

configmgr_cl generateConfig -task configureDotNetAPI -profile dotnetclient

configmgr_cl execute -task configureDotNetAPI -profile dotnetclient

2. Open a command prompt and browse to the CE Installation folder, where you 

will find the following DLL's: FNK_ACLEditor.dll, FNK_EnterpriseManager.dll

Run the commands below:

regsvr32 FNK_ACLEditor.dll

regsvr32 FNK_EnterpriseManager.dll

Note: regsvr32.exe is a command line tool provided by windows to register the dlls.

This file is commonly found in C:\Windows\System32 folder (On Windows 7 machine)

If the command prompt says that the command is not found, then either add the path to 'System32' folder to the PATH location (OR) run the commands as -

"C:\Windows\System32\regsvr32.exe" <dll>