I was hoping someone would be able to help me out. We have a .net MVC web application running on IIS that needs the ability to launch a batch file which opens up a Microsoft Access database with some command parameters and prints a specified report to pdf, to be downloaded to the client.
The database has the AutoExec macro, and all necessary forms in place to open the report (passed in through /cmd parameters), and exports it to pdf format. I created a bat file that works just fine.
When running it through the web app's server side code, the MSACCESS.exe process is started in task manager for the correct user, but the Access application does not open, nor is there any lock on the database file. If I change the appPool to run as Local system, the process starts and the lock file appears, but nothing is executed.
As far as user permissions, I've already set full control for the directory housing the MSACCESS.exe, DCOM component services for Microsoft Access, and any directories it interacts with, for the DefaultAppPool identity, and IIS_IUSRS. My appPool is running as ApplicationPoolIdentity, so the user is IIS AppPool/DefaultAppPool.
All permissions seem to be in place.
Does anyone have any suggestions (besides get rid of Access) on why the process would start, but not the application.
We are stuck with integrating Access Reports for the existing client base due to the customization they already have in place.
Thanks in advance