magma-ag

"File access denied" after Update to LogPlot 7.6.133.168

8 posts in this topic

Hi

After the latest update to LogPlot V. 7.6.133.168 we get on one of our Windows 7 machines the following error message when compiling a log: "File access denied".

The user has full write access to the folder C:\Users\Usrename\Documents\LogPlot 7\System where also a 0 KB temporary file is created when compiling a log.

We already did a fresh installation of the local LogPlot installation and also reassigned the path to the network license file.

Thanks

Valentin

error.jpg

post-12745-0-09940700-1424871219_thumb.jpg

Share this post


Link to post
Share on other sites

Hi Valentin,

What is the destination path for the compiled log? If it is a network drive, there may be a problem with write privileges or the network may have temporarily locked the file access. If there is a bug report generated by the error, please send the file to support@rockware.com.

Thanks,

Tom B

RockWare Inc

Share this post


Link to post
Share on other sites

Hi Tom

We get the same error for a local and a network destination path for the compiled log. Where would it if a bug report was generated?

Thanks

Valentin

Share this post


Link to post
Share on other sites

Hi Valentin,

You would be prompted to view or save the bug report if one was created, but it looks like you are not getting a bug report.

I will ask our tech support staff to take a look while I am out of the office.

Thanks,

Tom B

RockWare Inc

Share this post


Link to post
Share on other sites

Hi Valentin,

Does your user have the ability to compile any of the data files in the C:\Users\Username\Documents\LogPlot 7\Samples folder, such as the simple "Lithology1.dat" data file compiled into the "Lithology1.ldfx" log design?

Thanks

Molly Mayfield

RockWare Inc.

Share this post


Link to post
Share on other sites

Hi Valentin,

Another comment from the programmers, regarding the "create file for output..." message: "The program is only writing to memory at this point so I don't think the output file is actually the problem. It could possibly be a problem with the pattern or symbol file."

Can you check the libraries that this user is set up to use, via the Options | Program Files window? Are these local, or on the network? Can the user view the pattern and/or symbol libraries via the Tools menu?

Thanks

Molly Mayfield

RockWare Inc.

Share this post


Link to post
Share on other sites

Thanks Molly.

Reassigning the symbol library (on a network location) did the trick.

Share this post


Link to post
Share on other sites

Excellent! Thanks for letting us know that this worked.

Best regards,

Molly Mayfield

RockWare Inc

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now