Skip to main content

Hello,

I just wanted to throw this out there and see if any other users are having similar issues.  Our applications are on the 10.1.0 and after the latest windows update quite a few of our customers on Windows 10 are getting 3707 errors [user does not have appropriate access permissions to the file (open)] when we are creating some temporary files.  The odd thing is that it is not happening every time, they go back into the same process and everything works fine.  Some of these routines that create the temporary files have been in place for a very long time and have never had problems till this week.  We have not been able to duplicate the problem yet, so I just wanted to see if anyone else was having the same problem and if they have been able to solve it.  It seems like the last update has messed something up, just not sure what yet.

 

Thanks,

Scott Meiners

Hello,

I just wanted to throw this out there and see if any other users are having similar issues.  Our applications are on the 10.1.0 and after the latest windows update quite a few of our customers on Windows 10 are getting 3707 errors [user does not have appropriate access permissions to the file (open)] when we are creating some temporary files.  The odd thing is that it is not happening every time, they go back into the same process and everything works fine.  Some of these routines that create the temporary files have been in place for a very long time and have never had problems till this week.  We have not been able to duplicate the problem yet, so I just wanted to see if anyone else was having the same problem and if they have been able to solve it.  It seems like the last update has messed something up, just not sure what yet.

 

Thanks,

Scott Meiners

Not sure if this is related or not (we haven't seen that exact error), but we have had issues which seem to be related to a combination of Webroot antivirus and a recent Windows update. Adding the runtime as an exception in the Webroot console has been the solution/workaround.

Hello,

I just wanted to throw this out there and see if any other users are having similar issues.  Our applications are on the 10.1.0 and after the latest windows update quite a few of our customers on Windows 10 are getting 3707 errors [user does not have appropriate access permissions to the file (open)] when we are creating some temporary files.  The odd thing is that it is not happening every time, they go back into the same process and everything works fine.  Some of these routines that create the temporary files have been in place for a very long time and have never had problems till this week.  We have not been able to duplicate the problem yet, so I just wanted to see if anyone else was having the same problem and if they have been able to solve it.  It seems like the last update has messed something up, just not sure what yet.

 

Thanks,

Scott Meiners

Our company have had 2 client sites thus far impacted in a similar way. AcuCobol error 9107 file permissions error encountered when attempting to delete a temporary file that we have just opened. at both sites it was intermittent. We believe that some form of scanning has kicked in after the windows security updates were installed on the Windows Server 2008 R2 systems. We are running version 9.2.0 AcuGt
One Client ended up unionstalling the following windows security patches:

KB4050946, KB4049068, KB4048961, KB4047206. Removal of these stopped our issues with 9107 on work files.

Anther client removed the following:
KB4049068, KB4054521, KB4054518

The common factor was KB4049068 ... but the online description for this update refers to Fijian time zone settings !
I believe what GMCfourX4 suggested is what is actually happening... but I cannot prove it.
I will check if either are using Webroot antivirus
Jim

Hello,

I just wanted to throw this out there and see if any other users are having similar issues.  Our applications are on the 10.1.0 and after the latest windows update quite a few of our customers on Windows 10 are getting 3707 errors [user does not have appropriate access permissions to the file (open)] when we are creating some temporary files.  The odd thing is that it is not happening every time, they go back into the same process and everything works fine.  Some of these routines that create the temporary files have been in place for a very long time and have never had problems till this week.  We have not been able to duplicate the problem yet, so I just wanted to see if anyone else was having the same problem and if they have been able to solve it.  It seems like the last update has messed something up, just not sure what yet.

 

Thanks,

Scott Meiners

We've recently narrowed down multiple customer sites with strange file errors, who were able to resolve them by removing and hiding KB4054518.

Hello,

I just wanted to throw this out there and see if any other users are having similar issues.  Our applications are on the 10.1.0 and after the latest windows update quite a few of our customers on Windows 10 are getting 3707 errors [user does not have appropriate access permissions to the file (open)] when we are creating some temporary files.  The odd thing is that it is not happening every time, they go back into the same process and everything works fine.  Some of these routines that create the temporary files have been in place for a very long time and have never had problems till this week.  We have not been able to duplicate the problem yet, so I just wanted to see if anyone else was having the same problem and if they have been able to solve it.  It seems like the last update has messed something up, just not sure what yet.

 

Thanks,

Scott Meiners

Thanks for the information!! It appears that the issue is actually only with our customers on Windows 7 with the KB4054518 update installed. Having them remove this update seems to have solved the issue, for now. We are not sure what the other commonality is with these computers yet to determine why it is happening. Other users have this update installed on windows 7 and have never received the errors. Hopefully the next Patch Tuesday does not bring the errors back.

Hello,

I just wanted to throw this out there and see if any other users are having similar issues.  Our applications are on the 10.1.0 and after the latest windows update quite a few of our customers on Windows 10 are getting 3707 errors [user does not have appropriate access permissions to the file (open)] when we are creating some temporary files.  The odd thing is that it is not happening every time, they go back into the same process and everything works fine.  Some of these routines that create the temporary files have been in place for a very long time and have never had problems till this week.  We have not been able to duplicate the problem yet, so I just wanted to see if anyone else was having the same problem and if they have been able to solve it.  It seems like the last update has messed something up, just not sure what yet.

 

Thanks,

Scott Meiners

We now have the same problem. The problem does (not always) occur if a temporary file is deleted after processing with "delete file". The runtime version plays no role. We are now checking to see if KB4054518 is installed on the affected clients. Until now the status 37/07 has not been related to the acuserver.

Hello,

I just wanted to throw this out there and see if any other users are having similar issues.  Our applications are on the 10.1.0 and after the latest windows update quite a few of our customers on Windows 10 are getting 3707 errors [user does not have appropriate access permissions to the file (open)] when we are creating some temporary files.  The odd thing is that it is not happening every time, they go back into the same process and everything works fine.  Some of these routines that create the temporary files have been in place for a very long time and have never had problems till this week.  We have not been able to duplicate the problem yet, so I just wanted to see if anyone else was having the same problem and if they have been able to solve it.  It seems like the last update has messed something up, just not sure what yet.

 

Thanks,

Scott Meiners

We too have had multiple customers report this problem and we agree it does not seem to be runtime version specific and we are also seeing that it is random in nature even within the very same program and always seems to be on temporary files. We are asking customers to uninstall KB4054518 for now and keep it from reinstalling, but of course they are asking how long they will have to keep it off. I guess we can naively hope Microsoft will "fix" whatever it is they have "broken" in a future update such as January which should be out this week. Thus far we have not had any clients report it that use AcuServer, only those that access their data files via a mapped drive.

Hello,

I just wanted to throw this out there and see if any other users are having similar issues.  Our applications are on the 10.1.0 and after the latest windows update quite a few of our customers on Windows 10 are getting 3707 errors [user does not have appropriate access permissions to the file (open)] when we are creating some temporary files.  The odd thing is that it is not happening every time, they go back into the same process and everything works fine.  Some of these routines that create the temporary files have been in place for a very long time and have never had problems till this week.  We have not been able to duplicate the problem yet, so I just wanted to see if anyone else was having the same problem and if they have been able to solve it.  It seems like the last update has messed something up, just not sure what yet.

 

Thanks,

Scott Meiners

Has anyone verfied the cause, and the fix yet? Or has anyone from MicroFocus chimed in here yet?

I am having the same problem, also starting in the middle of December, same symptoms as described here ... 37-07 error when trying to delete a temporary file the process just created. AND, only on a Windows-7 PC accessing a mapped network drive. I am working to have one user remove MS patches that were installed in December, and having another user get the latest MS patches to see if they've fixed the problem. I'll let people know what I find.

Hello,

I just wanted to throw this out there and see if any other users are having similar issues.  Our applications are on the 10.1.0 and after the latest windows update quite a few of our customers on Windows 10 are getting 3707 errors [user does not have appropriate access permissions to the file (open)] when we are creating some temporary files.  The odd thing is that it is not happening every time, they go back into the same process and everything works fine.  Some of these routines that create the temporary files have been in place for a very long time and have never had problems till this week.  We have not been able to duplicate the problem yet, so I just wanted to see if anyone else was having the same problem and if they have been able to solve it.  It seems like the last update has messed something up, just not sure what yet.

 

Thanks,

Scott Meiners

Hi All following on from my previous post ... we have been getting 9107 as previously described... both clients that get it are using Symantek Endpoint Protection. I believe that the updates ... and unfortunately there are several involved are some how stuffing update the Anti Virus software. Now this has ALWAYS been the case and we have ALWAYS had to maintain "EXCLUSION" on our data folders... but I think the updates are stuffing this up.
I had alerted all of our clients to NOT install the updates and to temporarily cease installing. We have just had one client install all the latest ... they are using MS Endpoint ... and have had no problems since installing last Thursday.
I also saw an article on the web where Symantek had reported 2 MS updates had stuffed them up ...MS actually reversed the updates. I did not record the numbers as they were not in my set of suspects ... theye were earlier numbers. Can anyone else report Symantek Endpoint being involved?

Hello,

I just wanted to throw this out there and see if any other users are having similar issues.  Our applications are on the 10.1.0 and after the latest windows update quite a few of our customers on Windows 10 are getting 3707 errors [user does not have appropriate access permissions to the file (open)] when we are creating some temporary files.  The odd thing is that it is not happening every time, they go back into the same process and everything works fine.  Some of these routines that create the temporary files have been in place for a very long time and have never had problems till this week.  We have not been able to duplicate the problem yet, so I just wanted to see if anyone else was having the same problem and if they have been able to solve it.  It seems like the last update has messed something up, just not sure what yet.

 

Thanks,

Scott Meiners

We have still had no luck being able to reproduce the errors well enough to be able to send anything in to support line yet, but we are still having the errors and they seem like they are increasing. We initially had some users remove KB4054518 which helped, but the latest updates for January appear to have caused the errors to come back. For us it appears that the error is occurring during the deleting of a temporary file that we had just recent created. The errors appear to just be on Windows 7 but there has been many different versions of security software. This has been occurring with Security Essentials, Vipre Business Agent, McAfee, Vipre Endpoint Security 9.6, Webroot v. 9.0.18.34, Sophos Endpoint 11.5.11 and AVG. They all appear to be using mapped drives connected to windows server. The server version vary also. Some are Windows Server 2012 R2, Server 2016 and Windows server 2008 R2.

Hello,

I just wanted to throw this out there and see if any other users are having similar issues.  Our applications are on the 10.1.0 and after the latest windows update quite a few of our customers on Windows 10 are getting 3707 errors [user does not have appropriate access permissions to the file (open)] when we are creating some temporary files.  The odd thing is that it is not happening every time, they go back into the same process and everything works fine.  Some of these routines that create the temporary files have been in place for a very long time and have never had problems till this week.  We have not been able to duplicate the problem yet, so I just wanted to see if anyone else was having the same problem and if they have been able to solve it.  It seems like the last update has messed something up, just not sure what yet.

 

Thanks,

Scott Meiners

Others have reported that the January updates reinstalled KB4054018, and so they had to remove it again.

Hello,

I just wanted to throw this out there and see if any other users are having similar issues.  Our applications are on the 10.1.0 and after the latest windows update quite a few of our customers on Windows 10 are getting 3707 errors [user does not have appropriate access permissions to the file (open)] when we are creating some temporary files.  The odd thing is that it is not happening every time, they go back into the same process and everything works fine.  Some of these routines that create the temporary files have been in place for a very long time and have never had problems till this week.  We have not been able to duplicate the problem yet, so I just wanted to see if anyone else was having the same problem and if they have been able to solve it.  It seems like the last update has messed something up, just not sure what yet.

 

Thanks,

Scott Meiners

We are now also being told that some users on Windows 10 are now getting the error. We also have people who removed KB4054518 (the errors stopped), had the latest windows updates installed and their system still shows that update as blocked and now they are getting the errors again. We have written a test program to simulate what is going on with these files but we have been unsuccessful in duplicating the error.

Hello,

I just wanted to throw this out there and see if any other users are having similar issues.  Our applications are on the 10.1.0 and after the latest windows update quite a few of our customers on Windows 10 are getting 3707 errors [user does not have appropriate access permissions to the file (open)] when we are creating some temporary files.  The odd thing is that it is not happening every time, they go back into the same process and everything works fine.  Some of these routines that create the temporary files have been in place for a very long time and have never had problems till this week.  We have not been able to duplicate the problem yet, so I just wanted to see if anyone else was having the same problem and if they have been able to solve it.  It seems like the last update has messed something up, just not sure what yet.

 

Thanks,

Scott Meiners

What's the exact location in which you save these temporary files?
Local c:\\ drive or %temp% or a mapped drive or anything else?

Hello,

I just wanted to throw this out there and see if any other users are having similar issues.  Our applications are on the 10.1.0 and after the latest windows update quite a few of our customers on Windows 10 are getting 3707 errors [user does not have appropriate access permissions to the file (open)] when we are creating some temporary files.  The odd thing is that it is not happening every time, they go back into the same process and everything works fine.  Some of these routines that create the temporary files have been in place for a very long time and have never had problems till this week.  We have not been able to duplicate the problem yet, so I just wanted to see if anyone else was having the same problem and if they have been able to solve it.  It seems like the last update has messed something up, just not sure what yet.

 

Thanks,

Scott Meiners

The data files that we are having issues with are files that are getting stored mapped drives. Something like f:\\program\\data. These temporary files are initially getting open output, closed, opened i-o, records written out to it, records read then file deleted. The directory that these files are in are the same as the rest of our data files. The issue is that it is so random, a user can do the same process 10-15 times with no problem then they get the 3707 error then go back in and run again without issue.

Hello,

I just wanted to throw this out there and see if any other users are having similar issues.  Our applications are on the 10.1.0 and after the latest windows update quite a few of our customers on Windows 10 are getting 3707 errors [user does not have appropriate access permissions to the file (open)] when we are creating some temporary files.  The odd thing is that it is not happening every time, they go back into the same process and everything works fine.  Some of these routines that create the temporary files have been in place for a very long time and have never had problems till this week.  We have not been able to duplicate the problem yet, so I just wanted to see if anyone else was having the same problem and if they have been able to solve it.  It seems like the last update has messed something up, just not sure what yet.

 

Thanks,

Scott Meiners

Scott, you described that exactly.

Hello,

I just wanted to throw this out there and see if any other users are having similar issues.  Our applications are on the 10.1.0 and after the latest windows update quite a few of our customers on Windows 10 are getting 3707 errors [user does not have appropriate access permissions to the file (open)] when we are creating some temporary files.  The odd thing is that it is not happening every time, they go back into the same process and everything works fine.  Some of these routines that create the temporary files have been in place for a very long time and have never had problems till this week.  We have not been able to duplicate the problem yet, so I just wanted to see if anyone else was having the same problem and if they have been able to solve it.  It seems like the last update has messed something up, just not sure what yet.

 

Thanks,

Scott Meiners

Yes, I was sure it was a problem related to mapped drives.
Windows is introducing stronger security and doing quick and repeated I-O operations on mapped drive may be considered as an undesired behaviour by the OS itself.
As these are temporary files, is there a reason you're not using the %temp% folders set by the system itself?

Hello,

I just wanted to throw this out there and see if any other users are having similar issues.  Our applications are on the 10.1.0 and after the latest windows update quite a few of our customers on Windows 10 are getting 3707 errors [user does not have appropriate access permissions to the file (open)] when we are creating some temporary files.  The odd thing is that it is not happening every time, they go back into the same process and everything works fine.  Some of these routines that create the temporary files have been in place for a very long time and have never had problems till this week.  We have not been able to duplicate the problem yet, so I just wanted to see if anyone else was having the same problem and if they have been able to solve it.  It seems like the last update has messed something up, just not sure what yet.

 

Thanks,

Scott Meiners

We want to keep all of our data in one location whether its temporary or not. Some of the information that is in some of these file can be rather sensitive and the idea of having files stored on local computers is not ideal.

Hello,

I just wanted to throw this out there and see if any other users are having similar issues.  Our applications are on the 10.1.0 and after the latest windows update quite a few of our customers on Windows 10 are getting 3707 errors [user does not have appropriate access permissions to the file (open)] when we are creating some temporary files.  The odd thing is that it is not happening every time, they go back into the same process and everything works fine.  Some of these routines that create the temporary files have been in place for a very long time and have never had problems till this week.  We have not been able to duplicate the problem yet, so I just wanted to see if anyone else was having the same problem and if they have been able to solve it.  It seems like the last update has messed something up, just not sure what yet.

 

Thanks,

Scott Meiners

Not sure if this helps, but to get around this temporary, I change the code to delete the records instead of 'delete file' and it seems to be working, at least I have not heard any problems since then.

Hello,

I just wanted to throw this out there and see if any other users are having similar issues.  Our applications are on the 10.1.0 and after the latest windows update quite a few of our customers on Windows 10 are getting 3707 errors [user does not have appropriate access permissions to the file (open)] when we are creating some temporary files.  The odd thing is that it is not happening every time, they go back into the same process and everything works fine.  Some of these routines that create the temporary files have been in place for a very long time and have never had problems till this week.  We have not been able to duplicate the problem yet, so I just wanted to see if anyone else was having the same problem and if they have been able to solve it.  It seems like the last update has messed something up, just not sure what yet.

 

Thanks,

Scott Meiners

Claudio,
Our issue stems from COBOL SORT files.
-Chris

Hello,

I just wanted to throw this out there and see if any other users are having similar issues.  Our applications are on the 10.1.0 and after the latest windows update quite a few of our customers on Windows 10 are getting 3707 errors [user does not have appropriate access permissions to the file (open)] when we are creating some temporary files.  The odd thing is that it is not happening every time, they go back into the same process and everything works fine.  Some of these routines that create the temporary files have been in place for a very long time and have never had problems till this week.  We have not been able to duplicate the problem yet, so I just wanted to see if anyone else was having the same problem and if they have been able to solve it.  It seems like the last update has messed something up, just not sure what yet.

 

Thanks,

Scott Meiners

We can not change the code. It's about a huge amount of programs that have been running smoothly for years.

Hello,

I just wanted to throw this out there and see if any other users are having similar issues.  Our applications are on the 10.1.0 and after the latest windows update quite a few of our customers on Windows 10 are getting 3707 errors [user does not have appropriate access permissions to the file (open)] when we are creating some temporary files.  The odd thing is that it is not happening every time, they go back into the same process and everything works fine.  Some of these routines that create the temporary files have been in place for a very long time and have never had problems till this week.  We have not been able to duplicate the problem yet, so I just wanted to see if anyone else was having the same problem and if they have been able to solve it.  It seems like the last update has messed something up, just not sure what yet.

 

Thanks,

Scott Meiners

It appears as though this was a "FIX" for a problem with MS Office files? That's our best guess based on what's included in the patches we've been removing to temporarily work around the problem.
support.microsoft.com/.../windows-7-update-kb4051034
"Addressed delays when accessing shared Microsoft Office documents from a remote network drive. Files open, but accessing and saving files are affected. Access delays increase dramatically with increased file size."

Hello,

I just wanted to throw this out there and see if any other users are having similar issues.  Our applications are on the 10.1.0 and after the latest windows update quite a few of our customers on Windows 10 are getting 3707 errors [user does not have appropriate access permissions to the file (open)] when we are creating some temporary files.  The odd thing is that it is not happening every time, they go back into the same process and everything works fine.  Some of these routines that create the temporary files have been in place for a very long time and have never had problems till this week.  We have not been able to duplicate the problem yet, so I just wanted to see if anyone else was having the same problem and if they have been able to solve it.  It seems like the last update has messed something up, just not sure what yet.

 

Thanks,

Scott Meiners

So let me make sure I understand this. Microsoft thinks reading and writing to a disk is undesired behavior?

Changing our entire application to use a local drive for work files is not going to be even remotely possible.

Hello,

I just wanted to throw this out there and see if any other users are having similar issues.  Our applications are on the 10.1.0 and after the latest windows update quite a few of our customers on Windows 10 are getting 3707 errors [user does not have appropriate access permissions to the file (open)] when we are creating some temporary files.  The odd thing is that it is not happening every time, they go back into the same process and everything works fine.  Some of these routines that create the temporary files have been in place for a very long time and have never had problems till this week.  We have not been able to duplicate the problem yet, so I just wanted to see if anyone else was having the same problem and if they have been able to solve it.  It seems like the last update has messed something up, just not sure what yet.

 

Thanks,

Scott Meiners

It just seems like there is something else that is triggering this event. It is not happening at all of our users all the time and its not happening for every user in the same office. We have written a test program that does the open output, closes, opens i-o, writes 500 records, reads 500 records, closes the file then deletes it that runs 90,000 times and it runs fine in our office. The PC we are running it on is a windows 7 pro computer with all the latest updates, using security essentials virus software, connected to a window 12 server using mapped drives.

Hello,

I just wanted to throw this out there and see if any other users are having similar issues.  Our applications are on the 10.1.0 and after the latest windows update quite a few of our customers on Windows 10 are getting 3707 errors [user does not have appropriate access permissions to the file (open)] when we are creating some temporary files.  The odd thing is that it is not happening every time, they go back into the same process and everything works fine.  Some of these routines that create the temporary files have been in place for a very long time and have never had problems till this week.  We have not been able to duplicate the problem yet, so I just wanted to see if anyone else was having the same problem and if they have been able to solve it.  It seems like the last update has messed something up, just not sure what yet.

 

Thanks,

Scott Meiners

I wanted to pass along that I was incorrectly informed earlier today that a user was on a Windows 10 computer when they were actually on Windows 7. So as of now, we have NOT had any user (to my knowledge) have this issue on Windows 10.

Hello,

I just wanted to throw this out there and see if any other users are having similar issues.  Our applications are on the 10.1.0 and after the latest windows update quite a few of our customers on Windows 10 are getting 3707 errors [user does not have appropriate access permissions to the file (open)] when we are creating some temporary files.  The odd thing is that it is not happening every time, they go back into the same process and everything works fine.  Some of these routines that create the temporary files have been in place for a very long time and have never had problems till this week.  We have not been able to duplicate the problem yet, so I just wanted to see if anyone else was having the same problem and if they have been able to solve it.  It seems like the last update has messed something up, just not sure what yet.

 

Thanks,

Scott Meiners

We too were thinking and assuming that changing the storage path of these problem temp files to the user's local temp folder would probably fix the problem. However, we too have so many programs that would need to be changed. Part of this is due to many of these basic programs have been in use since the days of Unix servers and character terminals where all files were server based anyways. However, the other issue we are having with these that moving them to a local temp folder would not solve is situations such as an A/P Purchase Journal or A/R Cash Receipts Journal where multiple users are entering data and then posting it once a day or a few times a day. Here we need them to all enter data into a combined journal, not their own local temp files. So if the journal is posted and deleted successfully after posting, then all is fine, however if the journal posts but then fails to delete, the users end up with duplicate entries the next time they try to run it, unless they catch it and they have become sort of numb to these Error 3707's since they are so rampant now, yet inconsistent. I suppose deleting records as they are posted would resolve that, but that too becomes a lot of work and a little dangerous messing in programs that have worked for years.

Hello,

I just wanted to throw this out there and see if any other users are having similar issues.  Our applications are on the 10.1.0 and after the latest windows update quite a few of our customers on Windows 10 are getting 3707 errors [user does not have appropriate access permissions to the file (open)] when we are creating some temporary files.  The odd thing is that it is not happening every time, they go back into the same process and everything works fine.  Some of these routines that create the temporary files have been in place for a very long time and have never had problems till this week.  We have not been able to duplicate the problem yet, so I just wanted to see if anyone else was having the same problem and if they have been able to solve it.  It seems like the last update has messed something up, just not sure what yet.

 

Thanks,

Scott Meiners

I was wondering if anyone has reported this as an indecent to support line yet?