1-Visitor

Solved

Select Working Directory UNC path

5 replies
3916 views
Translate All

When i want to change working directory to some other folder, it doen't take UNC path.

if mapped from network drive, it works.

am i doing something wrong? or Creo has limitations.

General

BenLoosliAnswer

23-Emerald III

Creo definately has limitations......................

I do not think UNC paths are supported and I have seen that documented someplace.

https://www.ptc.com/en/support/article?n=CS51143

UNC paths are not supported for Working Directory!

1-Visitor

Hi,

Are you trying to do so manually or using ToolKit?

Translate

24-Ruby III

Hi,

you can set windows registry according to https://support.microsoft.com/en-us/help/156276/cmd-exe-does-not-support-unc-names-as-the-current-directory and test whether it helped...

Note: I guess that UNC paths are not 100% supported by Creo.

Translate

Answer

23-Emerald III

Creo definately has limitations......................

I do not think UNC paths are supported and I have seen that documented someplace.

https://www.ptc.com/en/support/article?n=CS51143

UNC paths are not supported for Working Directory!

Translate

Author

1-Visitor

Thanks for the reply,

document was written in 2012 and still no progress from PTC.

i can live with mapped network drive.

Translate

5-Regular Member

5-Regular Member

I have been working with UNC path during the last 10 years with Windows versions. Working directory and Creo path files are using them. No problema found.

After changing to Win10, the system was working but we have found that after a period of 3 hours, Creo disconnects the UNC paths. users is not able to save his work and is not able to find any other file. After closing Creo and starting a new session, we application Works.

Alternative solution is to map drives but when complex environments need to be managed, is not the best way.

Windows registry keys that allow user to work with UNC are DisableUNCcheck set to 1, and also redefine NetHood value.

The reference to a Microsoft article is no longer valid.

Translate