The XML API server took an unexpected exception. This does not mean that it stopped functioning for other users. (In most casses it is an APL reply unmarshalling error).
If the problem persists, collect support materials by running the /nas/tools/collect_support_materials script or the newer /nas/tools/automaticcollection script. Note any symptoms. If you require more information on the materials collection process, refer to the Problem Resolution Roadmap for Celerra, available on EMC Powerlink, or EMC Knowledgebase Support Solution number emc135846.
For more information, use the text from the error message's brief description or the message's ID to search the Knowledgebase on Powerlink. After logging in to Powerlink, go to Support > Knowledgebase Search > Support Solutions Search.
You need to update your OS – its over 3 years old …..
We are now at 6.0.51.6
Relevant log is at /nas/log/cel_api.log*
Most likely you are hitting one of these problems fixed a long long time ago
Symptom Desc. When user queries for the capacity info or the capability info of the file systems, if there were checkpoints, XML API displayed the following error message and not the correct value: Unexpected exception of unknown nature.
Fix This issue occurred because VPFS file system did not have storageMB value and a null check was not performed. If the file system is of type - VPFS, no details of the file system will be displayed.
Fixed in version 6.0.41.0
Symptom Desc. The device type 10 gigabit and the speed 10000FD were not added in the code. When APL returned this device type and speed, XML API displayed the value as other.
Fix Added the new device type and the new value of speed to the code.
Fixed in version 6.0.41.0
Symptom Desc. When a CIFS share spanned across multiple CIFS servers, XML API identified only one server and sent the request to APL. APL expected all the servers as the key, and returned the following error:
Archiver::createDhsmConnections() Failed to query the file system of '' for server '10.10.17.153'. Error Reason = 'XmlApi::recvXmlResponse Error.
Fix The code has been modified to check for share name and CIFS server name and return the information correctly.
Fixed in version 6.0.41.0
Symptom Desc. For XML API clients, a query was made to get Shares with a filter of name="value", but the value field was specified as case-insensitive. Code enforced that values had to be case -sensitive, which caused older queries by XML API clients to fail if they did not specify the value correctly.
Fix The C3 code was modified to accept case in-sensitive values for share names in order to remain backward compatible.
Rainer_EMC
6 Operator
•
8645 Posts
403
0
Posted January 19th, 2012 02:00
Which DART / VNX OE release are you using?