The community will undergo maintenance on October 16th at 10:00 PM PDT and will be unavailable for up to one hour.
I just finished a dry-run migration from Intralink 3.4 to 9.1 and messed something up.
After I check-out and open something in Pro/E and modify it, when I attempt to save, it is being saved to "My Documents" and not the workspace. In fact, the workspace is not even shown as a place to save-to in the Save dialog.
Yet the workspace is available (and the default) when I open a model/drawing.
This is only happening with a regular user (Active Directory).
This is not an issue if I am logged in as wcadmin.
I normally would suspect I messed up on a domain policy, but have not found the possible cause (so far).
And I have been using loadfiles all along for policies, and they have not changed since my initial tests.
Prior migration tests did not have this saving problem.
Any suggestions as to where I should be looking to resolve this?
(maybe a preference setting?)
Gerry
Thanks to the many people that replied (mostly directly).
Several people suggested I delete the cache folder.
I had thought of this as well, and had done so several times to no avail.
However this did make me think about other types of cache, and I eventually used the principal administrator to "remove user from cache".
This fix the problem, but I don't know why.
Gerry
In Reply to Gerry Champoux:
I just finished a dry-run migration from Intralink 3.4 to 9.1 and messed something up.
After I check-out and open something in Pro/E and modify it, when I attempt to save, it is being saved to "My Documents" and not the workspace. In fact, the workspace is not even shown as a place to save-to in the Save dialog.
Yet the workspace is available (and the default) when I open a model/drawing.This is only happening with a regular user (Active Directory).
This is not an issue if I am logged in as wcadmin.
I normally would suspect I messed up on a domain policy, but have not found the possible cause (so far).
And I have been using loadfiles all along for policies, and they have not changed since my initial tests.
Prior migration tests did not have this saving problem.Any suggestions as to where I should be looking to resolve this?
(maybe a preference setting?)