Hi
We have an issue which is irksome to say the least.
We installed ABD with the GB data set, which is supposedly the one to use.
Opening on the desk top all is good.
But if we create or open a file on PW, then access the data set lib, it shows as US_dataset.
The PW database belongs to the client, we have passport access.
I am looking for a reason this is happening so I can pass onto the client, as they claim its not their configuration issue.
1. MANAGED PROJECTWORK SPACE IN PLACE BY CLIENT
2. SE5 AND SE6 ABD
3. LAUNCH PW, THEN RIGHT CLICK/OPEN
4. NOT KNOWN
5.08.11.11.590
oh and PW server i beleive is hosted by bentley... company Flo (UK)
also its not only myself that has this issue.
Other user keeps getting crashes when choosing view attributes in a 3D file
All the issues I am sure are to do with PW credentials assigned to our log-ins..
But I have to convince the client that this is the case.
Hi Colin,
Could you clarify what you mean by SE5 and SE6? I'm assuming you're referring to V8i SELECTseries 5 and 6, but even if so, each should have its own workspace + dataset.
Hi Steve
yes, sorry Select series 5/6
Yes both have there own workspace within the PW environment
Where a managed workspace exists it should have been set up with a workspace for one specific version, not both. The ProjectWise administrator should have specified a version of AECOsim, either SS5 or SS6, but not both. The file associations within ProjectWise should open the specified version if it is present on the client machine.
The dataset should be downloaded from ProjectWise to the local cache folders along with the DGNs and other content. It may have been configured to use the local delivered dataset, if so the local version needs to match the version in the managed workspace, either SS5 or SS6 but not both..
Marc
hi Marc
this is what their PW config is.
The screen capture shows a separate Ss4 (not 5?) and Ss6 folder, with what appears to be standard sub-folders underneath. But that alone doesn't tell us what's in those folders and what is stored elsewhere - for example, the DataGroup System Reports folder at the bottom - or how the workspace variables are defined. is there a specific reason you suspect that your PW credentials might be a factor?
Compatibility is one of Bentley users’ worst nightmares, and dare I say it is getting worse by the day. Looking at the PW CE matrix for instance shows zero Building products compatible with PW version 280 for example... How is that even thinkable in Bentley’s universe? I wonder... Forget about running ABD SS6 with a PW CE version, that would be asking for trouble - in terms of managed workspaces. But who would want to use building products without managed workspaces... A truely vicious circle.
Hi Chris,
Let me look into this... I recently updated the PW Matrix to add Update 7 based on information I had on hand at the time, but now that I look I see that you are correct - .280 is not included and I'm not sure where I pulled .271 from. Thanks for pointing this out.