This content has been marked as final. Show 4 replies
The adapter .exe normally only opens when you are attempting to configure the adapter via the workbench, or it is communicating with essbase.
What shows in Essbase when this happens?
Is anyone attempting to configure the adapter?
Have you done any configuration of the adaptor Load or consolidate Scripts? If not, then if you load as "Replace", or have consolidation switched on, then the default details contained in the adaptor scripts are rather generic and can cause issues. (On my current project the FDM screen would just appear to lock-up resulting in the type of issues you indicate.
You have not indicated if this is a test or production environment you are talking about or whether you are using the adpator scripts to load / consolidate or using an attached load script.
Theres is no one configuring the adapters at this moment.
Maybe there were running some calculations scripts before, but the processes stay open even after calculations.
It is a productive system.
Is there a way to find the calculation scripts which are causing the trouble?
Try the following things:
1. I assume that you mentioned calculation scripts are Essbase calculations scripts, check the essbase log and find what scripts were running before the CUP gets 100%.
2. Check Windows event log and see if you can come up with something.
3. Check virus software as well.