Clever Geek Handbook

Another problem elmah ... works everywhere but production

I have elmah set up to use SqlErrorLog and this works on both my local developer webserver and my integration environment in IIS. On my production box, elmah can log exceptions using the XmlFileErrorLog by writing to the app_data directory. When I go back to SqlErrorLog I get nadda. I have guaranteed that the database exists, has the required table and three procedures. I checked the connection string. I compared web.configs from my local to prod and the only differences are the name of the database server in the connection strings.

Any thoughts on what else might be blocking in a production setup?

~ - = Mike = - ~

+2


source to share


1 answer


Are you setting database permissions correctly for ELMAH? Depending on whether or not you are using impersonation in your web application, you may need to grant additional privileges to additional users for stored procedures / tables.



0


source






More articles:


All Articles