Forum Discussion
Trying to update a content pack and received this error.
- Anonymous9 years ago
I found a workaround try this. I had 5 reports in my contente pack, so I removed 4 reports and updated my content pack with just one report and no error. I went back and added\updated one report at a time till I added all 5 I oringinally had in the content pack.
I opened a support ticket ticket with microsoft and they said that it is a known issue and they are working on it. Till then try this workaround.
Hi Anonymous,
Did you mean Content Pack or APP?
Did you encounter this issue when you republished a content pack or App after editing original one? I have tried several times but could always republish the modified one.
Could you republish other content packs or Apps without any error? If you were talking about App, please check that when you create a new workspace, do you have any group image defined? If yes, please try to remove it, or try a smaller (<33KB) JPG or PNG for a test.
By the way, I have noticed that this issue has been reported internally.
Best regards,
Yuliana Gu
I'm getting this when updating existing content pack.
- sebbayard9 years ago
Helper I
Same error message here when trying to update the content pack.
- v-yulgu-msft9 years ago
Microsoft Employee
Hi Anonymous,
It might be an issue that affects content pack updating. We have reported this issue internally to product team. Please be patient to wait for the fix. Thanks for your understanding.
Regards,
Yuliana Gu- jbjs58209 years ago
Helper I
hello,
Is there any solution?
This is kind of tricky!
This is happends since 31/7.
Thanks
JS
- Anonymous9 years agoNot applicable
I found a workaround try this. I had 5 reports in my contente pack, so I removed 4 reports and updated my content pack with just one report and no error. I went back and added\updated one report at a time till I added all 5 I oringinally had in the content pack.
I opened a support ticket ticket with microsoft and they said that it is a known issue and they are working on it. Till then try this workaround.