Unfortunately, I mistakenly clicked the "Solved" button in the topic https://communities.sas.com/t5/SAS-Enterprise-Guide/Errors-quot-Invalid-object-DNA-quot-and-quot-Root-element-is/m-p/708474#M37909, but problem is actual. The problem was described like this: One of my users have 2 errors: "Invalid object DNA" and "Root element is missing" in one. Machine: Windows 8, Sas EG version 7.13 HF5 (7.100.3.5486) I read thread https://communities.sas.com/t5/SAS-Enterprise-Guide/Invalid-object-DNA/m-p/363310 She don't have two EG sessions in parallel which both updated the file and then got a garbled content back Also I made profile changes, as sade in https://support.sas.com/kb/58/672.html - no change. I thought: that file(project) is damaged - but it propertly on the machine of other user. They use the same file from the same sharred sourse. We tried to reinstall EG and make this algoritm: -Close any open instances of SAS or SAS Enterprise Guide. -Open a Windows Explorer window and navigate to C:\Users\your-user-ID\AppData\Roaming\. -Locate the folder titled SAS and rename it SAS_old. -Restart SAS Enterprise Guide (the error should no longer occur). -Close SAS Enterprise Guide. -Again navigate to C:\Users\your-user-ID\AppData\Roaming\ and open the SAS_old folder. -Copy the MetadataServerProfiles directory into the new C:\Users\your-user-ID\AppData\Roaming\SAS directory (overwrite the new MetadataServerProfiles directory). This step ensures that the existing connection information is still available. It didn't helped. Today user came back with the same error: "Invalid object DNA" and "Root element is missing". We will try to remove %appdata%\SAS\EnterpriseGuide\7.1 at all and recreate connection profile from the begining.
... View more
