Can you please share arerror.log and ardebug.log file at the time of export def.
Pls check if the objects you are trying to export are corrupted..try opening few of them and see
Error is "java.lang.NullPointerException" . It seems referenced object is not present on the server. e.g in case of filter, reference form should be exist on the server.
Can you open that particular filter and check if all the references are valid.
Is it an upgraded env.?
- there are no related error in arerror and ardebug files
- the objects are not corrupted.
- all the references exist on the server
-no this is not an upgraded environment.
Can you try with older version of developer studio? [something like 8.x or 7.6.04]. If reference objects are present on the server then it should work (atleast) with older version of dev studio. please give a try.
do you get this error only for specific filter or it is same for any object you want to export? I still feel there is something wrong with filter metadata definition.
Sure I'll try it.
if the problem occurs for all the objects..may be
try switching to a different work space in dev studio
check java version dev studio is pointing to...supported version? you may check this in devstudio configuration settings file
if it is for few specific objects..then what type of objects are they? custom? overlay?
This is not happening for all the objects. The filters are custom filters. However, no related objects are corrupted.
When we do a save as and delete the original one it works fine. But this we cannot do for each and every object.
Can you please enable the developer studio logs and try reproduce the issue again and share those logs file.
Well its happening with all those filters which has call guide action.
I have raised Ticket with BMC and they are working on it.
AR conf file issue it was
This cannot be a conf file issue. Can you share what you had fixed in the conf file which has fixed the issue? I strongly feel that there must be a use case which has to be fixed or we may be query some configuration parameter whose value is set to null and now your fix might have set it to some value. In any case this should be fixed.
If you can share def or create a simplified use case and share, this can be fixed in the product or any hotfix and going forward no one will face this issue.