/build/static/layout/Breadcrumb_cap_w.png

Microstation 7 writing advlogo.ole to C:\windows

I am trying to virtualize a suite of applications, Microstation7, Interplot , oracle 9.

Asan administrator I am able to open all the .dgn files without any error, but when I try to open as a locked down user, I get access denied for a file that is getting created in C:\windows.

the first one is advlogo.ole.
if i try to open a 10oa10.dgn file i get a access denied on 10oa10.ole file. cannot create these files in C:\windows as this one is locked down.

these error do not effect the fucntionality of the application but how to get rid of these errors.


0 Comments   [ + ] Show comments

Answers (2)

Posted by: bheers 16 years ago
Second Degree Blue Belt
0
Resequencing the application with the necessary rights to launch the application before doing a stop monitoring made this application work.
Posted by: kkaminsk 16 years ago
9th Degree Black Belt
0
Yep, that is one reason why it is recommended to launch the application at least once while sequencing. This helps better define the virtual file system so that the application files are all captured to the file system. I have some leaky sequences I need to clean up because the VFS wasn't defined well enough so some of the data is being written to the physical file system. Usually the sequencer is very good at figuring out the right places to set file system overrides but it doesn't necessarily do it well enough all the time.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ