ABD in managed PWise

How can I configure ABD so that it runs as administrator when I open a document in ProjectWise managed workspace?
Even when I force ABD to run locally as administrator (shortcut settings), when I open a document in PW I still get the message "lock pages in memory not allowed for that user etc etc"... although every local user is included in the lock pages in memory settings...

Parents

0 Offline ChrisRevuelta Wed, Jun 24 2015 11:42 AM

Thanks Steve, I think that is right. Although I was logged on my computer with a local windows profile with admin rights and "lock pages in memory..." enabled, I was logged on the datasource (on integration server) with a domain profile.
The moment I logged on the computer with the same domain profile as PW - which I should do anyway - problem disappeared.

I haven't yet checked what are the user rights assignments on the server but maybe the answer is there... ?

In any case, not sure these "free limits" have any impact on performance, it's such an old question that seem to me unanswered to this day - but at least it's kinda satisfying to not get the message "...cannot use all the memory in your system etc..."

Answer Verified By: Steve Cocchi
Cancel
Vote Up 0 Vote Down

Sign in to reply

Reject Answer

Cancel
0 Offline Steve Cocchi Fri, Jun 26 2015 10:10 AM in reply to ChrisRevuelta
Hi Chris,
Cool, I would take that as a positive. :) Matching up permissions seemed like the right thing to do since PW managing the cached data (workspace + DGNs) could potentially conflict between client and server - it was really just a guess on my part but I'm glad that helped to narrow the scope.

Regarding the "lock pages in memory" environment variable, it was designed to extend the available memory for 32bit ABD (via MicroStation) on x64 systems (assuming the memory is available). While certainly not the same as native 64bit, it can give some processes a little extra bump in resources.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Offline Steve Cocchi Fri, Jun 26 2015 10:10 AM in reply to ChrisRevuelta
Hi Chris,
Cool, I would take that as a positive. :) Matching up permissions seemed like the right thing to do since PW managing the cached data (workspace + DGNs) could potentially conflict between client and server - it was really just a guess on my part but I'm glad that helped to narrow the scope.

Regarding the "lock pages in memory" environment variable, it was designed to extend the available memory for 32bit ABD (via MicroStation) on x64 systems (assuming the memory is available). While certainly not the same as native 64bit, it can give some processes a little extra bump in resources.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

0 ChrisRev Sat, Jun 27 2015 3:03 AM in reply to Steve Cocchi

Yes understand about the lock pages in memory, what i would like to know is what is the correct setup for MS_MEMORY_FREELIMIT, the default always being 50/150... or perhaps those number make no difference whatsoever? (which is my belief but i would like to be sure)... the maximum value is 2000 anyway, after which it will always revert to the default values....any reasons?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Offline ChrisRevuelta Wed, Jul 1 2015 8:07 AM in reply to Steve Cocchi

To clarify, when using ABD through Projectwise, on which computer the "lock pages in memory" is accessed by the application? Is it on the local or on the integration server?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Offline Steve Cocchi Wed, Jul 1 2015 1:54 PM in reply to ChrisRevuelta
The best reference to MS_MEMORY_FREELIMIT that I've found is in the second post here:
communities.bentley.com/.../98803

I think Darius' explanation is fairly clear. Well, as clear as things can be when working with memory allocation in Windows. :-)

In regards to Lock Pages in Memory, the machine where ABD is installed and running (the local machine) is where the variable would be set, since that's where the memory is being consumed. That isn't to say that the integration server can't make use of the additional memory (?), it's just not where ABD itself will be using those resources.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Offline ChrisRevuelta Wed, Jul 1 2015 9:56 PM in reply to Steve Cocchi

I see that reference to Darius and other links but none really explain anything...

" Let say setting it to MS_Memory_FREELIMIT = 100,700
100,700 -> 100 means that x32 bit program will start lock memory 2GB – 100 = 1,900 GB RAM (it can be set to 200). 700 mean how much RAM memory is installed minus from Operating System programs."

What means "will start lock memory" ? What is the impact if any on ABD? Any definitive answer ? I mean you guys wrote this program...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Offline Steve Cocchi Thu, Jul 2 2015 3:47 PM in reply to ChrisRevuelta
Unfortunately I don't have much more to offer since this isn't really an area I work within... I would suggest branching off this particular topic as a new thread on the MicroStation forum to see if any additional input is available.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel