另一个 elmah 问题......除了生产之外到处都存在
我有 elmah 设置来使用 SqlErrorLog,这在我的本地使用开发人员 Web 服务器和 IIS 下的集成环境上都运行良好。在我的生产机器上,elmah 能够通过写入 app_data 目录的 XmlFileErrorLog 来记录异常。当我切换回 SqlErrorLog 时,我得到了一些信息。我已确保数据库存在所需的表和三个过程。我已经测试了连接字符串。我将本地的 web.configs 与产品进行了比较,唯一的区别是连接字符串中的数据库服务器名称。
关于生产安装中还有什么可能会受到阻碍的任何想法吗?
~-=迈克=-~
I have elmah setup to use SqlErrorLog and this is running fine on both my local using the developer webserver, and my integration environment under IIS. On my production box elmah is able to log exceptions with XmlFileErrorLog writting to the app_data directory. When I switch back to SqlErrorLog I get nadda. I have ensured that the database exists has the required table and three procedures. I have tested the connectionstring. I have compared the web.configs from my local to prod and the only differences are the database server name in the connection strings.
Any thoughts as to what else can be blocking in a production installation?
~-=Mike=-~
您是否正确设置了 ELMAH 数据库的权限?根据您是否在 Web 应用程序中使用模拟,您可能必须向其他用户授予存储过程/表的权限。
Have you properly setup the permissions on the database for ELMAH? Depending on if you are you using impersonation with your web application, you may have to grant privileges to additional users to the stored procedures/tables.