Retrieve Metadata Failure

[Vivek M. Chawla]

I got this error while attempting to retrieve all metadata from a moderately sized org.

null: Need to specify full name, Name:Customer_Interactions, Delimiter:.

Additional information:

• The "Contents" selection in the "Select Retrieval Scope" dialog was "Module 'CommunitiesDemo'"
• The scope of the connection was all metadata in the org.
• I was retrieving from a Summer '16 org. The org has a very large number of unmanaged packages, and several managed packages.
• The same problem exists with "Apply Class Overlays" selected and unselected

The appropriate portion of the debug log is included below.

2016-07-09 15:11:44,609 [2009730]  DEBUG - lder.ForceComMetadataRetriever - Retrieving metadata for module CommunitiesDemo 
2016-07-09 15:11:44,611 [2009732]  DEBUG - lder.ForceComMetadataRetriever - Creating a retrieve request for API version 37.0 
2016-07-09 15:11:44,616 [2009737]  DEBUG - lder.ForceComMetadataRetriever - Retrieving all metadata. 
2016-07-09 15:11:44,738 [2009859]  DEBUG - tellij.builder.ForceComBuilder - Initialized local source caches for 55 files in 84 ms. 
2016-07-09 15:11:44,741 [2009862]  DEBUG - tellij.builder.ForceComBuilder - Initialized local source caches for 55 files in 120 ms. 
2016-07-09 15:11:44,790 [2009911]  DEBUG - tellij.builder.ForceComBuilder - Initialized local source caches for 55 files in 81 ms. 
2016-07-09 15:11:46,654 [2011775]  DEBUG - lder.ForceComMetadataRetriever - Submitted retrieve request with async process ID 09S36000008LMcdEAG 
2016-07-09 15:11:46,654 [2011775]  DEBUG - lder.ForceComMetadataRetriever - Polling the status of the retrieve request. 
2016-07-09 15:11:46,894 [2012015]  DEBUG - lder.ForceComMetadataRetriever - Status: Pending 
2016-07-09 15:11:46,894 [2012015]  DEBUG - lder.ForceComMetadataRetriever - Retrieve request is still processing. Waiting 5000 milliseconds and trying again. 
2016-07-09 15:11:51,898 [2017019]  DEBUG - lder.ForceComMetadataRetriever - Polling the status of the retrieve request. 
2016-07-09 15:11:52,473 [2017594]  DEBUG - lder.ForceComMetadataRetriever - Status: Failed 
2016-07-09 15:11:52,473 [2017594]  DEBUG - lder.ForceComMetadataRetriever - Retrieve complete. 
2016-07-09 15:11:52,716 [2017837]   WARN - .IlluminatedCloudExceptionUtil - null: Need to specify full name, Name:Customer_Interactions, Delimiter:. 
2016-07-09 15:12:16,361 [2041482]   WARN - ConfigurableExtensionPointUtil - ignore deprecated groupId: editor for id: editor.preferences.import 
2016-07-09 15:12:16,362 [2041483]   WARN - ConfigurableExtensionPointUtil - ignore deprecated groupId: build for id: gradle.compiler 
2016-07-09 15:12:30,170 [2055291]   WARN - ConfigurableExtensionPointUtil - ignore deprecated groupId: editor for id: editor.preferences.import 
2016-07-09 15:12:30,172 [2055293]   WARN - ConfigurableExtensionPointUtil - ignore deprecated groupId: build for id: gradle.compiler 

[Scott Wells]

Vivek, would you mind registering the following three entries under Help>Debug Log Settings and rerunning the retrieve process?

#com.illuminatedcloud.intellij.builder.RetrieveAction
#com.illuminatedcloud.intellij.builder.ForceComBuilder
#com.illuminatedcloud.intellij.builder.ForceComMetadataRetriever

Then send the corresponding section of the log. That should let me know what's happening.

[Vivek M. Chawla]

Hi Scott,

I've already got those entries in my Debugger Log Settings.

If there is missing log info, could that be a sign of another problem?

[Scott Wells]

Ah...yeah, now that I look at what you provided, I can see those classes enabled for debug. Unfortunately there's not much IC-specific going on here. IC is just just creating a Metadata API RetrieveRequest with unpackaged = true and nothing else specified and calling MetadataAPI.retrieve() with that request. Have you tried performing a similar type of retrieve using the Force.com Migration Tool or Workbench to see if it fails similarly or not?

I ask because I saw a very similar error with another user a few months back (error message pretty much like "null: Need to specify full name, Name:Customer_Interactions, Delimiter:."), and it turns out it was an issue with the metadata in the org. The user saw the same issue when using other Metadata API clients, and ultimately the only viable workaround was to identify the errant metadata and create a subscription that excluded it (i.e., not All/Package).

Please let me know your findings.

[Vivek M. Chawla]

Hi Scott. What you say makes sense. Go ahead and close this bug. If I can't work around it the way you suggest, I'll reopen.

Thanks!

[Scott Wells]

Sounds good. Feel free to reopen if needed.