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 am using Windchill PDMLink Release 11.1 and Datecode with CPS M020 CPS28
Windchill file system failed to initialize. Autocad 2022 will not connected with WGM. Resolve WFS & restart WGM. This issue occurred simultaneously for three user pc. removed shared drive & reinstalled. unable to edit Windchill folder full path in WGM .
Here are the errors that I faced
Windchill file system failed to initialize. Autocad 2022 will not connected with WGM.
Solved! Go to Solution.
When you say "local cache is shared [C-drive] from pc" do you mean to say that the cache folder your environment variable is pointing to is managed by some other sharing service (like OneDrive)? If yes, that may be causing your issue...
Or "shared" as in "shared between users"? As I understand it, the WGM doesn't allow shared users on a machine unless you're in Windchill 13. That has more to do with dlls. For this you'd get a different error at start up of WGM.
User environment variables should be fine, I think.
Take a look - "Unable to connect Windchill Workgroup Manager with AutoCAD, Inventor, NX or SolidWorks with warning: "A shared folder is selected for Windchill File System"": https://www.ptc.com/en/support/article/CS167483
already i followed and tried but you see
I found it necessary to explicitly set all the environment variables to someplace that is definitely not shared because everything would default to a OneDrive location if left to it's own devices.
PTC_WFS_DEFAULT_LOCATION sets the "PTC Places" location (although perhaps this is 12+ versions according to CS353857 ?) for your Windchill Folder Full Path.
AutoCAD, I don't think, needs all of those set.
If the WFS is consistently not starting up, it could also be an issue with the installation where you'd have to manually install just the Creo agent.
If you have any startup scripts for task kill, it may also help launch fresh every time.
Something like this:
tasklist|find /i "creoagent.exe" >NUL
if errorlevel 0 (taskkill /f /t /im creoagent.exe)
Hello @RR_10661622,
It looks like you have some responses from some community members. If any of these replies helped you solve your question please mark the appropriate reply as the Accepted Solution.
Of course, if you have more to share on your issue, please let the Community know so other community members can continue to help you.
Thanks,
Vivek N.
Community Moderation Team.
Hi everyone,
sorry for the late reply. since I was in the sick leave unable to respond to your suggestions.
Coming to the point. But client Windchill version is 11.1 M020 CPS28 so WGM CPS24 is used for AutoCAD 2022 so the suggested article wont applies for lower version's right? And also I wanted to inform you I've checked and followed all this points too.
Anyway, we have reinstalled the client machine OS and installed WGM freshly, now we are facing "drawing file is not valid" issue from Autocad 2022. Just following this article: https://www.ptc.com/en/support/article/CS370358?source=search .I'll update you the result sooner.
Where are your environment variables pointing right now?
It'd be best to create a cache folder somewhere on C:\ and point the 4 variables below to that folder set you create.
PTC_WF_ROOT C:\myCache\.wf
PTC_WFS_ROOT C:\myCache\.wfs
PTC_WGM_ROOT C:\myCache\.root
PTC_WLD_ROOT C:\myCache\.wwgm
The other thing to keep in mind if you have Creo running is that the Creo cache locations should be separate from your non-Creo cache. If you have a workspace you created with Creo and put AutoCAD files in there and then with the Workgroup Manager try to go to the same location, Windchill will know of the files but won't be able to necessarily get them since it's cache is pointing to a different physical location. That may also result in a "invalid file" error and often results in a workspace corruption.
Hi Dobi,
Actually issue got resolved after reinstalling OS also setting environment variable in client machine recently. But this issue has been raised from most of the production user team and its repeated two to three days once from some machines.
Suddenly why this behavior are getting from WGM Autocad & what may be the root cause ? .
Do you have an admin installation that sets the environment variables for all users?
Is the local cache in a OneDrive (or otherwise shared) folder?
Do you have anti-virus exclusions set? CS50545 helped us out on this front and really would be the last thing I can think of.
Hi @Dobi
We are waiting for client remote access to check & update here.
for question 1 : WGM have installed in non admin user level, so EV set for only the user level.
for question 2 ; local cache is shared [C-drive] from pc.
for question 3 : need to check...
When you say "local cache is shared [C-drive] from pc" do you mean to say that the cache folder your environment variable is pointing to is managed by some other sharing service (like OneDrive)? If yes, that may be causing your issue...
Or "shared" as in "shared between users"? As I understand it, the WGM doesn't allow shared users on a machine unless you're in Windchill 13. That has more to do with dlls. For this you'd get a different error at start up of WGM.
User environment variables should be fine, I think.