I'd focus on the DV_Eloqua.
Seems like something (probably a service) is defined with a reference to a resource/variable called DV_Eloqua. You should find out what it is and what it is supposed to be good for. I assume a search on the file system in component's resources/source codes, should be able to find it.
If you test all your use cases and you are sure that they work you can probably ignore the error. Personally, I'd be nervous what other errors the component might also have.
I see this issue with install of all the custom components. The exception I pasted in previous post was just one of the many.
To give you some back ground,
- This was done as part of migration effort from UCM 10gR3 to UCM 11g.
- There custom components were developed for UCM 10gR3, we have updated the code to use RIDC and as part of migration to 11g.
- Custom components were then installed to 11g using component manager.
- This issue is not see in of the component installed, even that component was migrated from 10gR3.
Thanks and Regards,