I'm wondering if anyone has run into a similar issue or has ideas towards resolution... I have successfully connected client side Arbortext (5.4 M060) to Windchill (9.1 M050) using my machine. I am running into problems getting another user connected from their machine, but am able to connect from mine using their Windchill log-in. On the client side, both set-ups use identical userprefs.xml pointing to a common network located siteprefs.xml. User is able to browse to and read the siteprefs.
So I'm a bit stumped... any insights are greatly appreciated!
hosts file? I don't think we're using it... but will look into.
no error message, just no available severes to select from (there should be two, Production and Development)
able to connect through IE Browser
the Folders structure for cache (Workspace) and Logs is the same on both machines as well, and is defined by siteprefs.xml. userprefs points to a central siteprefs per best practice
The next thing I've run into (and this is on my machine and connection... I'll keep the list updated on resolution of the issue connecting the other user) is an error when attempting to Save As Server Object. Error reads;
"The autonumbering feature should be enabled for "WCTYPE|wt.epm.EPMDocument|com.westport.DynamicDocument" soft type.
Please contact your server administrator."
We do need EPMDefaultDocuments (CAD/Pro-E) files to be manually numbered... and probably some (future) Dynamic Documents as these numbers come from ERP System. I realize this is probasbly more of a Windchill issue, but I'm trying my luck here. I am aware of TPI 149705 in the PTC Knowledge base and I've tried setting parent epm and dynamic types to auto number and the EPMDefault (CAD) to manual through OIR's in Windchill at the site level.
nothing has worked so far and I'm stumped... Any insights?
As an update I have been able to resolve this issue with much help from the PTC Tech Support Team (Amit rocks!). It turned out to be the cross-cutting "walk" described. I had convinced myself that I was doing the right things and setting OIR's at the Org level but it turns out I was doing so at the Site level. Root cause was an "ancestor" EPMDocument Rule with auto numbering disabled at the Org level (which was found first, and used). Obvious now, but I couldn't see it for looking at the time despite guidance provided here.