MisterChris
New member
- Local time
- Tomorrow, 00:19
- Joined
- Apr 16, 2013
- Messages
- 5
Hi there,
Thank you for taking the time to view and potentially assist me in my issue.
I am an Access(and IIS) newbie.
I am currently running an Access .accdr file from a remote Windows server through System.Diagnostics.Process.Start("REMOTE_SERVER__FILES_URL").
The reason I am doing this is because the client I have requires that we run the .accdr file using the server resources without using TS.
The user also requires that the application supports roughly 50 concurrent users.
The problem I'm having is that when I test this script to a remote server using Visual Web Developer it assigns a dynamic port number to the URL which allows me to access the .accdr file without issue, but when I run it on port 80 it throws "Access is denied" error.
I have disabled the firewall veeery temporarily to check as to whether that might be the issue but alas I received the same error.
Please may you help me to understand why IIS would be rejecting the process initialization method on port 80 when it works without issue on Visual Web Developer's dynamic port 53971.
Thank you again.
Thank you for taking the time to view and potentially assist me in my issue.
I am an Access(and IIS) newbie.
I am currently running an Access .accdr file from a remote Windows server through System.Diagnostics.Process.Start("REMOTE_SERVER__FILES_URL").
The reason I am doing this is because the client I have requires that we run the .accdr file using the server resources without using TS.
The user also requires that the application supports roughly 50 concurrent users.
The problem I'm having is that when I test this script to a remote server using Visual Web Developer it assigns a dynamic port number to the URL which allows me to access the .accdr file without issue, but when I run it on port 80 it throws "Access is denied" error.
I have disabled the firewall veeery temporarily to check as to whether that might be the issue but alas I received the same error.
Please may you help me to understand why IIS would be rejecting the process initialization method on port 80 when it works without issue on Visual Web Developer's dynamic port 53971.
Thank you again.
