Community Tip - Did you get an answer that solved your problem? Please mark it as an Accepted Solution so others with the same problem can find the answer easily. X
Issue:
Cause:
Resolution:
You can add another potential cause:
The filename contains a character that the converter doesn't like, such as '#'....
Luc
Hi LucMeekes,
Yes, you are correct; I will have this message passed to our technical team and have the article updated.
Thanks for your input
Regards,
Anurag
Better still, your technical team makes sure that file name characters accepted by Windows do NOT cause (such silly, unnecessary) errors in Prime and/or its converter.
Success!
Luc
Its the converter only. Prime will read and write files containing a hash (#) without troubles.
The converter also has no problem reading the legacy file with the hash in its name - the error occurs when the converter tries to create the converted file.
And I fully agree that this is a bug which should be fixed rather than just being documented 😉