cancel
Showing results for 
Search instead for 
Did you mean: 

FPM component usage error

Former Member
0 Kudos

Hello All

I ma facing a new error in the GAF action from portal. Its a deployed content from 2007, its working properly in the test servers. In one IDES server i am getting the following error.

com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: ComponentUsage(FPMConfigurationUsage): Active component must exist when getting interface controller. (Hint: Have you forgotten to create it with createComponent()? Should the lifecycle control of the component usage be "createOnDemand"?

Is it a temporary problem or some configuration issue?

Thanks in advance

Senon

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

i faced the same problem,

there are several case for this error:

1. usage declaration as part ur dc may be it is create on demand

2. authorization issue with the backend

3. your standard DC's are not in activition mode

4. the JCo's are not working - check this first

5. if the logon ticket - sso ticket fails the jcos cannot work - this is the problem i faced.

6. your satndard that is used dc's must be deployeed an active.

may be this can help you,

Cheers,

Apparao

Former Member
0 Kudos

Hello Guys,

the problem was with my self-service configuration. the name of the component used in the self service step was renamed, thus removing it from the configuration step. SO FPM was throwing the error

Thanks

Senon

Answers (1)

Answers (1)

former_member197348
Active Contributor
0 Kudos

Hi Senon,

In developemnt we get this exception if we miss to add the reference of BLC in onInit() of the corresponding component controller.

fpm.attachComponentToUsage(
			wdThis.wdGetAPI().getComponent(),
			wdThis.wdGetBEcmPlanningCompComponentUsage());

Check if you are missing any such statement in VAC.

Sometimes this error disappears when we restart the server.

regards,

Siva

Former Member
0 Kudos

Hello Siva,

Thank you so much for the response.

Its working application for a long time, suddenly started getting this error in one server.

may be your second suggestion could be the reason.

Thanks

Senon

former_member197348
Active Contributor
0 Kudos

Hi Senon,

I want to raise some more points here

Please check

any function module or function group changes happend or

transports not happened in the backend after change or

function group is not activated after change

or any change in the referenced components of the DC

Try to build like

Select the DC-> right click and select Development Component -> Build.(Uncheck the check box) and select OK

Check in entire Task View, whether there are any errors.

Regards,

Siva