Faulting application w3wp.exe, version 6.0.3790.3959, stamp 45d6968e, faulting module kernel32.dll, version 5.2.3790.3959, stamp 45d72003, debug? 0, fault address 0x0000bee7.在事件查看器里,一个周期大概三小时这样子,就出现五六条这样的出错信息,不知道这是什么原因.一直以为得不到很好的解决,不知道在场的高手们如何解决呢.我用的是.net2.0/C#
解决方案 »
- asp.net页面无法导入excel
- 问个简单的关于mvc模型验证的[DataType(DataType.Password)]作用问题
- windows media services 和windows media编码器不在同一网络中怎么捕获视频流
- 关于web.config文件的错误
- 如何设置硬盘上的目录为隐藏属性?看了CSDN只能设置文件的
- 未将对象引用设置到对象的实例
- 多数量多类型的多项目解决方案的部署问题?
- asp 爱好者必看!精彩!厉害!一起分享
- 菜鸟问题,如果不用serve版的系统,要装什么软件才能测试asp.net?
- !---------一个简单的问题(初学者)--------!
- 问下这个SQL
- 页面中“关键字: 描述问题” 问题 大家解决一下
我直接怀疑你的内存堆栈有问题,不一定是物理坏,但有可能是其它程序有冲突导致。
很有可能程序死循环引起的
1.从IIS日志排查,看看系统日志与IIS访问日志出错时间是哪一个页面
2.定时、定量回收应用程序池
When you run ASP.NET 2.0 on a domain controller check permissions on the following registry key:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ASP.NET_2.0.50727\Names .When ASP.NET 2.0 is installed, the local group IIS_WPG is given special permissions on this key. When the server is a domain controller the IIS_WPG group becomes a domain group (there are no local groups on domain controllers) and the NETWORK SERVICE account cannot be a member of it as it is a BUILTIN account. What you will need to do is give the NETWORK SERVICE account specific permissions to that key. Start Regedit and navigate to that key. Right-click "Names" and select “Permissions” on the context menu. Click Add and enter NETWORK SERVICE, click "Check Names" and click "Ok". With NETWORK SERVICE highlighted in the "Groups or User Names" list, click "Advanced". On the "Advanced Security Settings for Names" dialogue highlight NETWORK SERVICE and click "Edit". In the "Permission entry for Names" dialogue check that the "Name" box is showing "NETWORK SERVICE" and put check s against "Query Value", "Set Value", "Create Subkey", "Enumerate Subkeys", "Notify" and "Read Control". Click Ok on all the dialogues and close Regedit. Ensure your application pools are reconfigured to run as NETWORK SERVICE (or at least all the ones you want to be) and restart them.After a restart, there should be no more errors.