In general "yes" - since this issue is not reproducible and seems to occur spoardic on customer site.
I suspect that in some siutations fields passed as parameters are invalid. I've added some diagnostics code that will provide exactly that information and put it on it's way to the customer - but I would like to be able to reproduce the issue in the lab.
So far I was not able to reproduce exactly that issue. I always got different output from FPPool_GetLastErrorInfo(). Is this information dependend on the Centera system or is this string completely setup in the API ?
The cluster involved has no bearing on this type of error, but it does sound like they are occasionally using invalid values for the name or attribute.
After all I tried all kinds or invalid parameter scenarios for the FPClip_SetDescriptionAttribute() call and figured out that the combination I was asking for:
FP_PARAM_ERR "Attribute value is invalid"
is caused by an empty value string. All other scenarios that I was able to test returned other errors:
Invalid characters in value string: FP_INVALID_XML_ERR - "The specified string is not valid XML"
NULL value string: FP_PARAM_ERR - "Clip attribute value is NULL"
Value string too large (>100k): FP_OUT_OF_BOUNDS_ERR - "Attribute value is invalid. Exceeds limit"
Clipref invalid: FP_WRONG_REFERENCE_ERR - "Type is wrong"
Empty string value: FP_PARAM_ERR - "Attribute value is invalid"
Invalid characters in attribute name: FP_INVALID_XML_ERR - "The specified string is not valid XML"
Lars - I am glad you managed to figure this out and thank you for posting it to this forum.
However, based on your closing comment then you seem to misunderstand the point of these discussion forums. They are not support forums and at EMC we do not treat them as such. They are here for the entire community to comment on and interact in. If I have spare time, then I look at them - but with our resourcing levels just now, spare time is not something I have much of.
As you solved the issue yourself, then it just goes to show that it was not something that even needed my involvement .
Thanks for pointing that out. I feel the forum is helpful anyway. Communication is what keeps you going in "desperate" situations.
I didn't want to pick on you guys. In the past - when working on a Centera Integration with the EMC team in another project - I always felt well supported.
gstuartemc
2 Intern
•
417 Posts
0
March 19th, 2009 06:00
Are they supplying a valid FPClipRef for the first parameters, and two "normal" strings as the name and value (2nd and 3rd) parameters?
lars_diehl
5 Posts
0
March 19th, 2009 06:00
In general "yes" - since this issue is not reproducible and seems to occur spoardic on customer site.
I suspect that in some siutations fields passed as parameters are invalid. I've added some diagnostics code that will provide exactly that information and put it on it's way to the customer - but I would like to be able to reproduce the issue in the lab.
So far I was not able to reproduce exactly that issue. I always got different output from FPPool_GetLastErrorInfo(). Is this information dependend on the Centera system or is this string completely setup in the API ?
Thanks,
Lars
gstuartemc
2 Intern
•
417 Posts
0
March 19th, 2009 06:00
The cluster involved has no bearing on this type of error, but it does sound like they are occasionally using invalid values for the name or attribute.
lars_diehl
5 Posts
0
March 20th, 2009 10:00
After all I tried all kinds or invalid parameter scenarios for the FPClip_SetDescriptionAttribute() call and figured out that the combination I was asking for:
FP_PARAM_ERR "Attribute value is invalid"
is caused by an empty value string. All other scenarios that I was able to test returned other errors:
@Emc: I expected you to come up with such a list.
Cheers,
Lars
gstuartemc
2 Intern
•
417 Posts
0
March 20th, 2009 11:00
Lars - I am glad you managed to figure this out and thank you for posting it to this forum.
However, based on your closing comment then you seem to misunderstand the point of these discussion forums. They are not support forums and at EMC we do not treat them as such. They are here for the entire community to comment on and interact in. If I have spare time, then I look at them - but with our resourcing levels just now, spare time is not something I have much of.
As you solved the issue yourself, then it just goes to show that it was not something that even needed my involvement
.
lars_diehl
5 Posts
0
March 20th, 2009 12:00
Thanks for pointing that out. I feel the forum is helpful anyway. Communication is what keeps you going in "desperate" situations.
I didn't want to pick on you guys. In the past - when working on a Centera Integration with the EMC team in another project - I always felt well supported.
Regards,
Lars