Yammer - Native alignment tool, handeling errors

%3CLINGO-SUB%20id%3D%22lingo-sub-1331683%22%20slang%3D%22en-US%22%3EYammer%20-%20Native%20alignment%20tool%2C%20handeling%20errors%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1331683%22%20slang%3D%22en-US%22%3E%3CP%3ETenant%20has%20been%20using%20Yammer%20since%202016%2C%20we%20are%26nbsp%3Bgetting%20errors%20running%20the%20alignment%20tool.%20Red%20error%20message%20on%20top%2C%20and%20an%20error%20report%20is%20generated%2C%20nice.%20But%20I%20cant%20find%20any%20guidance%20on%20how%20to%20resolve%20these%20errors...%20Any%20help%20out%20there%3F%3C%2FP%3E%3CH4%20id%3D%22toc-hId--655337133%22%20id%3D%22toc-hId--655337103%22%20id%3D%22toc-hId--655337103%22%20id%3D%22toc-hId--655337103%22%20id%3D%22toc-hId--655337103%22%3E%3CSPAN%3EError%20message%3A%3C%2FSPAN%3E%3C%2FH4%3E%3CP%3E%3CSPAN%3EYour%20network%20is%20not%20in%20Native%20Mode%3C%2FSPAN%3E%3C%2FP%3E%3CUL%3E%3CLI%3E%3CSTRONG%3EAlignment%20Tool%20Status%3A%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FSTRONG%3EFailed.%3C%2FLI%3E%3CLI%3E%3CSTRONG%3ENext%20steps%3A%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FSTRONG%3EResolve%20errors%20listed%20in%20the%20Error%20Report%2C%20then%20re-run%20the%20Alignment%20Tool%3C%2FLI%3E%3C%2FUL%3E%3CH4%20id%3D%22toc-hId-1832175700%22%20id%3D%22toc-hId-1832175730%22%20id%3D%22toc-hId-1832175730%22%20id%3D%22toc-hId-1832175730%22%20id%3D%22toc-hId-1832175730%22%3EError%20log%20contains%20four%20types%20of%20errors%3A%3C%2FH4%3E%3CP%3E1.%20OrphanReason(fileId%3D%3CID%3E%2C%20groupId%3D0%2C%20reason%3DAllCompany)%3C%2FID%3E%3C%2FP%3E%3CP%3E2.%26nbsp%3BSome%20files%20in%20this%20group%20weren't%20migrated.%3C%2FP%3E%3CP%3E3.%26nbsp%3BSystemNotSupportedException.%20Callstack%3A%20The%20given%20path's%20format%20is%20not%20supported.%20CallStack%20--%20at%20System.Security.Permissions.FileIOPermission.EmulateFileIOPermissionChecks(String%20fullPath)%3C%2FP%3E%3CP%3E4.%26nbsp%3Borg.postgresql.util.PSQLException%3A%20ERROR%3A%20duplicate%20key%20value%20violates%20unique%20constraint%20%22groups_yammer_group_id_index%22%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1331683%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAligntment%20tool%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Enative%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1340046%22%20slang%3D%22es-ES%22%3ERe%3A%20Yammer%20-%20Native%20alignment%20tool%2C%20handeling%20errors%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1340046%22%20slang%3D%22es-ES%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F567563%22%20target%3D%22_blank%22%3E%40techrambler%3C%2FA%3Ewe%20have%20the%20same%20problem.%20In%20addition%2C%20I%20checked%20some%20files%2C%20for%20example%2C%20orphaned%20files%20in%20All%20Company%2C%20and%20I%20could%20open%20them%20without%20any%20problem.%20The%20same%20for%20the%20accessing%20files%20.%20I%20checked%20for%20random%20files%20and%20all%20of%20them%20are%20image%20files%2C%20not%20office%20365%20files...%3C%2FP%3E%3CP%3EI%20guess%20that%20we%20have%20to%20download%20all%20the%20files%20and%20then%20upload%20them%20again%20if%20asked%20someone%20for%20them...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1404788%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20-%20Native%20alignment%20tool%2C%20handeling%20errors%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1404788%22%20slang%3D%22en-US%22%3EI%20re-run%20the%20tool%20yesterday%20and%20the%20SQL-errors%20(point%204%20above)%20seems%20to%20be%20resolved%2C%20but%20the%20first%20three%20are%20still%20there.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1421166%22%20slang%3D%22en-US%22%3ERe%3A%20Yammer%20-%20Native%20alignment%20tool%2C%20handeling%20errors%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1421166%22%20slang%3D%22en-US%22%3ESeems%20like%20I%20was%20able%20to%20resolve%20errors%201-3%20by%20renaming%20the%20files.%3CBR%20%2F%3E%3CBR%20%2F%3EFrom%20the%20error-log%2C%20copy%20and%20paste%20URL%20to%20failing%20attachments%20into%20browser%20-%20press%20the%20name%20of%20the%20attachment%20(on%20top)%20and%20rename%20it.%20Re-run%20alignment%20tool.%3CBR%20%2F%3E%3CBR%20%2F%3ELooks%20like%20Yammer%20for%20iOS%20back%20in%202016%20named%20(or%20allowed%20naming)%20pictures%20taken%20with%20a%20tailing%20time%20in%20HH%3AMM%3ASS%20format.%20The%20colons%20where%20the%20problem%20in%20my%20case.%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Tenant has been using Yammer since 2016, we are getting errors running the alignment tool. Red error message on top, and an error report is generated, nice. But I cant find any guidance on how to resolve these errors... Any help out there?

Error message:

Your network is not in Native Mode

  • Alignment Tool Status: Failed.
  • Next steps: Resolve errors listed in the Error Report, then re-run the Alignment Tool

Error log contains four types of errors:

1. OrphanReason(fileId=<id>, groupId=0, reason=AllCompany)

2. Some files in this group weren't migrated.

3. SystemNotSupportedException. Callstack: The given path's format is not supported. CallStack -- at System.Security.Permissions.FileIOPermission.EmulateFileIOPermissionChecks(String fullPath)

4. org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "groups_yammer_group_id_index"

3 Replies
Highlighted

@techramblerwe have the same problem. In addition, I checked some files, for example, orphaned files in All Company, and I could open them without any problem. The same for the accessing files errors . I checked for random files and all of them are image files, not office 365 files...

I guess that we have to download all the files and then upload them again if someone asked for them...

Highlighted
I re-run the tool yesterday and the SQL-errors (point 4 above) seems to be resolved, but the first three are still there.
Highlighted
Seems like I was able to resolve errors 1-3 by renaming the files.

From the error-log, copy and paste URL to failing attachments into browser - press the name of the attachment (on top) and rename it. Re-run alignment tool.

Looks like Yammer for iOS back in 2016 named (or allowed naming) pictures taken with a tailing time in HH:MM:SS format. The colons where the problem in my case.