Page 2 of 2

Posted: Sun Oct 21, 2007 10:01 am
by smaamirj
Hi, easiest way to handle concurrent manager in windows in case of inactivity,
recreate it using ccmsetup.exe and after this run auto config on Application side and then bounce the instance or machine.
Hope then you will not get this abnormality.

Posted: Sun Oct 21, 2007 12:57 pm
by ramkic
Hi,
Re-create the Concurrent Manager and re-start it.
To do that ( make sure this is Vision instance and installed on Windows platform)

1) de-install concurent manager
a) go the APPL_TOP and set up the apps environment
b) check the environment setup properly
c) go to FND_TOP/bin and run the following command
ccmsvc.exe -r -a <APPL_CONFIG>
ex: ccmsvc.exe -r -a vis_localhost
2) run adsvcm.cmd to re-create the service.
a) go to viscomn/admin/install directory
b) open adsvcm.cmd file
c) look for localdb entry
d) replace %APPS_PWD% apps user and password
e) save he file
f) run adsvcm.cmd
this will create the service.
3) Start the service
you can do this by two ways
1) go to control panel services and start from there
or 2) use net start

***** don't do this on production instance*****

Thanks
ramkic