Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 298
  • Last Modified:

File permissions ignored until a IIS restart

Greetings

We are using a .NET application to connect to authorize.net.  When first doing this, we were getting the following permissions error. "Unable to find an entry point named EnumerateSecurityPackagesW in DLL
security.dll"

To fix the issue, I added the ASPNET user group to the file that connects to authorize.net, gave it full control, re-started IIS,  and the error went away.  For about 5 days that is, then it returned generating the above error

When it returned, I noticed I could fix the problem by re-starting IIS.  Again, same thing.  It works again but every 4-5 days it stops working generating the above error.

In an attempt to resolve the issue once and for all, I added the ASPNET user group to the entire website and gave it modify permissions.  I also checked the box in IIS to allow script access for this site.  Again after 4 days it stopped working again generating the above error.

The least time,  I noticed that the ASPNET user group was removed from the entire web except the file I had originally set it on and the script access box had mysteriously become unchecked.  It would seem IIS permissions are being overwriiten and/or ignored.  Any clues as to why this happens and so sporadically?

Thanks....Rob
0
tconsult
Asked:
tconsult
  • 3
1 Solution
 
tconsultAuthor Commented:
Greetings all.....

My bad.  Please ignore the last paragraph above that starts with

"The least time,  I noticed that the ASPNET user group was removed from the entire web except the file I had originally..."

This was not the case.  BUT I still need to know why the file permissions are ignored every few days and why I have to re-start IIS to correct the problem.
0
 
What90Commented:
I found this and it seems to be on the right tracks:

http://www.paypaldev.org/topic.asp?TOPIC_ID=5022


Hope it helps!
0
 
tconsultAuthor Commented:
Thank you but that is not the issue.  I have seen that documentation before and there is not a name conflict.  If there were then it would not work at all.  Again, many thanks!
0
 
tconsultAuthor Commented:
I accept What90s answer.  The problem was a file named security.dll that existed on the server.  Please not the file doesn ot need to exist on the smae website - just on the server somewhere and it will casue a problem.  Details here.
http://tconsult.com/aspnet/server2003/entry_point_EnumerateSecurityPackagesW.aspx
0
 
riskyricky1972Commented:
0

Featured Post

Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now