Community Tip - If community subscription notifications are filling up your inbox you can set up a daily digest and get all your notifications in a single email. X
I have a network drive where CREO is configured, when I try to open it, it gives me an error that it can't save or open, the folder is allowed to save, delete, and create.
Solved! Go to Solution.
Hi
when searching the warning message, we can find this article https://www.ptc.com/en/support/article/CS141967
that suggests to change the Start in directory.
By chance are you able to create a new file or a new folder in that F drive from Windows Explorer in the first place?
Hi
when searching the warning message, we can find this article https://www.ptc.com/en/support/article/CS141967
that suggests to change the Start in directory.
By chance are you able to create a new file or a new folder in that F drive from Windows Explorer in the first place?
Are other users also writing the trail file to the same folder? Perhaps you cannot write to the trail file because another user is running Creo Parametric and the trail.txt file already exists in the folder and is in use by them.
Unless your system folks are using the trail files for some purpose, you can create your own config.pro file and specify a trail file location local to your PC. You can do this temporarily for testing.
Trail files are serialized, so there is likely not a clash in this manner. When you start a session, Creo looks in wherever it is going to write the trail file and takes the next number, i.e. if the last file is trail.txt.333, Creo will make the next one trail.txt.334, etc.
You've blanked out the actual directory name where you're trying to save trail files.
Does the name have a space in it? Creo is bad at handling directory specifications that have spaces in them. Sometimes they might work, most times they don't. I save my trail files to a simple directory on my C: drive (c:\ptc\TrailFiles).
Or, there might be a strange character in the directory name, which Creo doesn't like?
This type of thing comes up a lot when using long directory specifications in search.pro files. I always enclose a directory specification in those with double quotes. I don't know if that will work in the config.pro setting for trail_dir.