Missing Files During Verify
After migrating the Perforce database and versioned files, running p4 verify produces errors similar to:
//depot/foo/verrckt.c#1 - edit change 46102 (text) 252F3099E90B3F453841BE2800EC7D08 MISSING!
You confirm that the versioned file is present on the Perforce server, but the file name is displayed differently:
Perforce cannot find this versioned file because it is looking for "verrckt.c" instead of "verrckt.c ". This is most common after moving a checkpoint from a Windows server to a Unix based server -- the file names with special characters are encoded as LATIN1 under Windows, which might not match the UTF-8 encoded file names.
Cannot Convert Server to Unicode Mode
Regardless of server platform, file names submitted from Windows clients using extended characters can cause a Perforce server error when switching to Unicode mode:
Perforce Server Error:
Database has N tables with non-UTF8 text and can't be switched to Unicode mode.