EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB41918: "Object XXX cannot be saved because it is only partially defined" error message appears when performing a Project Merge through the Project Merge Wizard


Community Admin

• Strategy


Whenever performing a Project Merge through the Project Merge Wizard in MicroStrategy 9.4.1 and MicroStrategy 10.0 - 10.3, the user receives an error message below and Project Merge is closed without merging the projects successfully.

SYMPTOM:
Whenever performing a Project Merge through the Project Merge Wizard in Strategy 9.4.1 and Strategy 10.0 - 10.3, the user receives the error message below and Project Merge is closed without merging the projects successfully.
 

ka04W00000148SiQAI_0EM440000002D2C.png

 


The following error has occurred and is not recoverable.  Once this message box is closed, Project Merge Wizard will close.  Object 'XXX' cannot be saved because it is only partially defined.

 
 
The DSSErrors.log will also reveal:

2017-12-05 09:04:07.392-06:00 Examining Object(Name="DEV" Type=Folder ID=F99DCF3E407D94757915FC9BB8E8A72D Proj=35634B814E1B9C3B45AA629E45AEF3A3 Ver=BFEDD2FB11E237DC59430080EF757035 ), replacement path = "Public Objects\Reports\Mail Quality Reporting"
2017-12-05 09:04:07.423-06:00 ... no corresponding object in destination, so object will be merged
2017-12-05 09:04:07.501-06:00 Failed while merging collection of extended objects, error code 0x8004142B
2017-12-05 09:04:08.439-06:00 Source manipulator exited abnormally while a bulk merge was in progress

 
NOTE: This issue can also occur during an Object Manager migration as well.
CAUSE:
The object ID referenced in the error message was a folder object in the source project.  The destination project was having problems with creating this particular folder object that did not exist in the destination project.
 
ACTION:
This issue is fixed in the Strategy 10.4 product release.
 
WORKAROUND:
In this particular instance there was a folder object called DEV as seen in the Client Services -> Source Manipulator trace that was causing the issue.
To workaround the issue, prior to performing the Project Merge, create a folder object in the same location within the destination project called "DEV" (the name of the object causing the error in the Source Manipulator trace).


Comment

0 comments

Details

Knowledge Article

Published:

May 31, 2017

Last Updated:

May 31, 2017