Access to Data Denied errors

We have a notes client application in Notes 7.0.2 version. Recently users started recieving “access to data denied” errors while working with the application. There is no consistent pattern involved. Both PC and Mac users use this applicaiton. PC users are on windows XP, however I believe it has all started as users started upgrading to Windows 7 from Windows XP but I am not sure if this could cause any issues. It started off with one user reporting the error and we ignored, but all users started recieving it with almost every click and now our users are really annoyed.users do have enough free space on the computer, deleting of temporary files, compacting workspace, recreating notes.ini file, none of this helped resolve the issue. Please help.

Thanks,

Vandana

Subject: Access to Data Denied errors

Hi,

Notes requires write access to the temp directory specified in the Notes.ini. If no temp directory is specified, it uses the OS default, which is usually c:temp or c:WINNT]temp. If you change the temp directory they have write access to drive, the problems should disappear.

Also See this link :

http://www-01.ibm.com/support/docview.wss?uid=swg21093347

Subject: RE: Access to Data Denied errors

We tried giving Full Control access to temp directory and also the data directory, however the error still remains. One of the scenarios it throws an error seems like at the line of code which calls the UI document refresh method. Do you know why this method could throw “Access to Data Denied” error?

Subject: Access to Data Denied errors

From past experience, my gut tells me it’s an issue with directory permissions on the PC (Windows 7). As I recall, I ran into a lot of issues with data access errors when I started using Windows 7. It seems a little worse with Windows 8.

What operation fails? Is it possible to reliably duplicate the issue?

Does the application store data outside of Notes (for example, on a server or on the PC itself?)

Does the application use lotusscript (or formula) agents? Do the agents do any logging or ‘Print’ statements?

Is it possible to narrow down what action the user is performing when the failure occurs, and start adding some logging (or print statements) to narrow down where the failure occurs?

Subject: RE: Access to Data Denied errors

Hello, Thank you for the quick response. The application is fully developed in formula language and Lotus script. There are multiple functionalities that deal with reading/writing to excel sheets on user’s computer. But the interesting part is the errors also show up while opening documents , while trying to edit documents. So far we could not see any consistency but may be i should start off with adding message box statements after every few lines and see if it helps. The users are adminstrator’s on the computer. Do you know how you were able to solve the issue? is it permissions to the Data directory?

Thanks,

Vandana

Subject: RE: Access to Data Denied errors

I agree with Mark. We had major issues with Windows 7 in our applications that write files to the user’s PC.

What you should do is run the application with the debugger turned on so you can see specifically what command(s) cause this error, or put error handling in the code so that it pops up a message indicating the error number and error line, and then the users can send that to you.

The two biggest problems we had are:

  1. The Lotusscript “Dir” command does not work in Windows 7. If you use this to build any lists of files, you will have to code a work-around - I coded one to use the built-in File > Open dialog, but it’s not as pretty nor is it seamless.

  2. If you reuse a filename (we have a generic extract routine that always uses the same file name for a temp file), that file will not be overwritten. There is no error or indication that this has occurred, we figured it out because users were running an extract to Excel and the Excel file would open with different data than what was in the view they were extracting. So we had to add a “Kill” statemenet before writing a file to ensure that if it existed, it would be deleted, and we also had to add error handling to handle the situation where the file didn’t exist, in which case the Kill statement itself would return an error.

You can search the forum to find alternate solutions.