The specs for a project work fine, but whenever any user tries to go into Spec Browser it gives me an error message saying:
"APSpecEng: This key is already associated with an element of this collection"
Why am I getting this error and how can I get rid of it so Spec Browser works properly. It only happens in this one project which I reccently pulled from a different site, upgraded to XM, and integrated with Projectwise. All related product info is below:
Plant Framework 8.9.4.47 Plant Design 8.9.3.30 w .49 SP2 update Projectwise 8.9.4.89
Where the specs from this project moved as well or was it using default specs and you are just trying to use the new ones from the XM folder?
It is possible that the old specs had different sys_ids for components and this might have something to do with the error. What you could do is move those specs to a project folder and then point the project to those specs. I would then test out the project to see if the error repeats. If it does, then try opened up each spec in the XM SpecGen and rebuild the specs. Then go back in and see if the problem continues or not. Let me know how this goes.
EDIT - One other thing, if you are getting this error on opening up any spec in the spec browser, even the new ones, you might need to change out one of the files in that project with another file from a working project. I would first just try loading this project in SpecGen. This builds some of the files that are needed and should rewirte them. It might fix the issue without needing to deal with the original specs. Also, if this is happen with any specs,with this project, then let me know.
Was this moved with project package or was it just upgraded without moving it? It it was packaged, could you post the package on our ftp site below.
ftp://ftp.bentley.com/pub/incoming/
Let me know what the ST number is and if that link doesn't work for you.
If it was just upgraded were it was just go ahead and attach the config folder in a zip file to the ticket or send it to the ftp. Make sure that the name of the files is some like ST#######.zip so that it doesn't override any thing already there. If I can't find anything from the config files, then we can more on to the package.
I think this is due to a setting in Project Administrator. Compare the path settings in the CONFIG.INI from a sample V8i project to the upgraded XM project. It could be something as simple as a trailing backslash on the root spec directory.
Derek