When trying to import a parasolid assembly into ST7, I often erroneously get the message that the output folder is write protected or does not exist, despite the fact that it is neither. Manually selecting different locations for the output folder, such as another place on my network, my Desktop, and a created folder in the C drive with full permissions, are unsuccessful. Physically moving the file to be opened to these locations, and then selecting "Output folder is the same as input folder," is also unsuccessful.
Opening the same parasolid in a part template (all parts as part copies) is successful, and then after doing this, I can now close that out and go open it in an assembly template without an issue, as long as I am in the same SE instance!
Can anyone repeat this issue?
I have seen this as well - with ST6. I never found a resolution other than having the file resent to me as a STEP file.