Just transferred a model from a different office (where the resident PDMS expert is no longer there) and had some reports of some very strange errors.
First there was a splash error about not being able to find %PDMSDFLTS% - DES-FWT and how it couldn't enter design.
Once it entered design (because PDMS was being economical with the truth on the error message) there was an issue regards using the red cross to delete items. Which failed due to a !ADMCONTROL variable not being present.
I've played around with the Evars settings for PDMSDFLTS and the SPLASH error would appear to have gone but I am still getting the ADMCONTROL error when trying to delete.
I should add that the command line DELETE NAME still works, but you know these new designers - talking about comand lines is like talking in a foreign language.
Does anyone have any ideas as to where I should be directing my efforts to resolve the issue???
[QUOTE=randalf72;62511]Just transferred a model from a different office (where the resident PDMS expert is no longer there) and had some reports of some very strange errors.
First there was a splash error about not being able to find %PDMSDFLTS% - DES-FWT and how it couldn't enter design.
Once it entered design (because PDMS was being economical with the truth on the error message) there was an issue regards using the red cross to delete items. Which failed due to a !ADMCONTROL variable not being present.
I've played around with the Evars settings for PDMSDFLTS and the SPLASH error would appear to have gone but I am still getting the ADMCONTROL error when trying to delete.
I should add that the command line DELETE NAME still works, but you know these new designers - talking about comand lines is like talking in a foreign language.
Does anyone have any ideas as to where I should be directing my efforts to resolve the issue???
Do you mean the Delete button in Desing?
It's sometimes helpful deletind the serialization files in such situations.
Hmm, ADMCONTROL is an Object defined in the admin objects of the pmllib. It seems to control a lot of operations.
PDMS version used? Any searchpaths for PMLLIB or PDMSUI in front of the official libs from Aveva which might host modified Aveva routines? Global project or not?
there are three paths for both PMLLIB and PDMSUI, the first two have been supplied by the other office and appear to relate to an additional menu option that fires up a form (unfortunately there is no one I can talk to regards exactly what it does and how it does it) and the third is the standard Aveva path.
I would try to start it without the leading own libs in the rearch paths.
And/Or to start it with 11.6.SP5 which you can do without any risk of incompatibility. We run a mixture of both on several PCs for the same contract without problems.
I have traced behaviour of the Delete button in 11.6.SP4 and 11.6.SP5: No differences, such the release can't be the reason.
But there are methods called of object !!admcontrol. Is this available when you query that in the command line with
Q !!admcontrol
????
When not, something migth be wrong with your PDMS start-up. That's why I recommended to take away the own folders from the search paths for PDMSUI and PMLLIB which can be easily performed by renaming these folder as long as they are NOT residing on a public server!
Otherwise you need a particular start-up procedure
[QUOTE=pdmselder;62527]I have traced behaviour of the Delete button in 11.6.SP4 and 11.6.SP5: No differences, such the release can't be the reason.
But there are methods called of object !!admcontrol. Is this available when you query that in the command line with
Q !!admcontrol
????
When not, something migth be wrong with your PDMS start-up. That's why I recommended to take away the own folders from the search paths for PDMSUI and PMLLIB which can be easily performed by renaming these folder as long as they are NOT residing on a public server!
Otherwise you need a particular start-up procedure
Thank you,
Model is currently locked while doing a db copy so I can't check
but I'm going to try selectively disabling the PDMSUI and PMLLIB paths until the delete button works - if indeeed it does.
And apparently according to one of the PMs he thinks that access control has been enabled on the model which I should be able to test by going in under one of the other offices super user accounts and seeing if that behaves any differently from our standard designer accounts.
This may be a tricky one but discussing it here is certainly giving me a direction and ideas.
I bounced this one back to Aveva who advised that there is a fix in later SP's of PDMS but that I needed to edit C:\AVEVA\Plant\PDMS12.0.SP6\PMLLIB\admin\function\ADMINSTART.PMLFNC
Obviously depending upon your setup this location may vary.
and comment out lines 44 and 46 (basically taking out an IF statement) to leave call !!comDefineGlobal(object ADMCONTROL())
Which also works a a direct command, albeit one that needs reentering every time you start up PDMS
