Error in Event Viewer after installing Forums webpart on SPS2003

Topics: Developer Forum
Oct 30, 2006 at 5:57 PM
After installing the webpart, everything looks and runs great so far. But... I looked in the Windows Event Viewer and saw an errir right after I installed the forums webpart:

Faulting application w3wp.exe, version 6.0.3790.1830, stamp 42435be1, faulting module onetutil.exe, version11.0.6568.0, stamp 42e17447, debug? 0, fault address 0x00077f8a

Any ideas?
Thans,
Scott
Nov 8, 2006 at 11:09 AM
I have the same problem too.

the version of the forum was 1.1.0.0 i uninstall that version and all right now.
and now i whant to install 1.2.0.0 enybody know how it works? maby this version have bugs too?
Jan 2, 2007 at 8:43 PM
We are having the same issue. Also, the page is taking about 8 seconds to load consistently. Is anyone else having this problem. It would make sense if a app pool was failing and having to recompile...just curious on anyone else's feedback. Here is an article below that may shed some light on the issue. I am not really sure since there is not any source readily available.


http://www.nivot.org/CommentView,guid,adcf66d9-a70d-4fca-bc67-28dd5bd4d0e9.aspx
Jan 3, 2007 at 12:44 AM
I am also facing the same problem. I get a lot of these errors after using the forums webpart. Here are the error messages from the Event Viewer:

Faulting application w3wp.exe, version 6.0.3790.1830, stamp 42435be1, faulting module stswel.dll, version 11.0.6568.0, stamp 42e17544, debug? 0, fault address 0x000b0a8d.

Faulting application w3wp.exe, version 6.0.3790.1830, stamp 42435be1, faulting module onetutil.dll, version 11.0.6568.0, stamp 42e17447, debug? 0, fault address 0x00077d59.

Faulting application w3wp.exe, version 6.0.3790.1830, stamp 42435be1, faulting module sqloledb.dll, version 2000.86.1830.0, stamp 424377fc, debug? 0, fault address 0x0000c6ad.

Faulting application w3wp.exe, version 6.0.3790.1830, stamp 42435be1, faulting module owssvr.dll, version 11.0.6568.0, stamp 42df9b14, debug? 0, fault address 0x000ace92.

Anyone has any ideas how to resolve this issue?


Jan 8, 2007 at 3:27 PM
Is there any chance we could get a response on this? It's a little frustrating not to have a response along with no source code to at least try to debug the issue.