Hello all:
We just updated to wildfire and Intralink 3.3. I tried to use my old drawing templates in 3.3 by moving them to the /pdm/templates directory. When I try to create a new part or assy in intralink with the object - new command, I get the following error:
View attachment 104
I went to the knowledge base, and found the following:
***********************
Description
-----------------
If The default template contains an attribute with illegal value (i.e. a value which is NOT in the attribute's list of values), selecting #Object #New in the Workspace will return the non-Descriptive error message: 'An invalid handle WSPIHandle Was Passed To An API Function PDMWSPISetCurrWSPIVTargetFolder'
Alternate Technique
-----------------
Add the illegal value to parameter's list in Pro/ADMIN, or modify the template.
Resolution
-----------------
This issue will be resolved in Pro/INTRALINK 3.3 M020.
******************
I tried creating a brand new template file in Wildfire from scratch and placing it in the templates directory, but I still get the same error.
Any help would be greatly appreciated.
Phil
We just updated to wildfire and Intralink 3.3. I tried to use my old drawing templates in 3.3 by moving them to the /pdm/templates directory. When I try to create a new part or assy in intralink with the object - new command, I get the following error:
View attachment 104
I went to the knowledge base, and found the following:
***********************
Description
-----------------
If The default template contains an attribute with illegal value (i.e. a value which is NOT in the attribute's list of values), selecting #Object #New in the Workspace will return the non-Descriptive error message: 'An invalid handle WSPIHandle Was Passed To An API Function PDMWSPISetCurrWSPIVTargetFolder'
Alternate Technique
-----------------
Add the illegal value to parameter's list in Pro/ADMIN, or modify the template.
Resolution
-----------------
This issue will be resolved in Pro/INTRALINK 3.3 M020.
******************
I tried creating a brand new template file in Wildfire from scratch and placing it in the templates directory, but I still get the same error.
Any help would be greatly appreciated.
Phil