From: Simon Darwent on 28 Aug 2005 20:31 Hi all, Hoping for some help with this problem. I keep getting Windows SharePoint Services 2.0 error messages in the Application event log with an Event ID 1000. The server runs fine most of the time, but these errors seem to occur a few times throughout the day : 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 0x0001291b. Faulting application w3wp.exe, version 6.0.3790.1830, stamp 42435be1, faulting module msdart.dll, version 2.82.1830.0, stamp 42437818, debug? 0, fault address 0x0000846d. Faulting application w3wp.exe, version 6.0.3790.1830, stamp 42435be1, faulting module msvcrt.dll, version 7.0.3790.1830, stamp 4243785e, debug? 0, fault address 0x00026f76. Faulting application w3wp.exe, version 6.0.3790.1830, stamp 42435be1, faulting module oledb32.dll, version 2.82.1830.0, stamp 424377e0, debug? 0, fault address 0x0001a646. Users will get an oscreen error message - usually "Exception from HRESULT: 0x80040E05." or just "Exception occurred." Seems to have started around the time I changed SQL Server to run as a domain account instead of the localsystem account. Could this be the cause of these errors? Thanks in advance! Cheers, Simon
From: Herman on 31 Aug 2005 08:43 Hello We also have this problem, same error but the faulting module is always ntdll.dll version 5.2.3790.1830. We haven't change anything with the SQL server. I hope too you/we can get some help here. "Simon Darwent" <SimonDarwent(a)discussions.microsoft.com> wrote in message news:3BD62C0C-357A-4066-B285-0465EC33D287(a)microsoft.com... > Hi all, > > Hoping for some help with this problem. I keep getting Windows SharePoint > Services 2.0 error messages in the Application event log with an Event ID > 1000. The server runs fine most of the time, but these errors seem to > occur > a few times throughout the day : > > 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 0x0001291b. > > Faulting application w3wp.exe, version 6.0.3790.1830, stamp 42435be1, > faulting module msdart.dll, version 2.82.1830.0, stamp 42437818, debug? 0, > fault address 0x0000846d. > > Faulting application w3wp.exe, version 6.0.3790.1830, stamp 42435be1, > faulting module msvcrt.dll, version 7.0.3790.1830, stamp 4243785e, debug? > 0, > fault address 0x00026f76. > > Faulting application w3wp.exe, version 6.0.3790.1830, stamp 42435be1, > faulting module oledb32.dll, version 2.82.1830.0, stamp 424377e0, debug? > 0, > fault address 0x0001a646. > > Users will get an oscreen error message - usually "Exception from HRESULT: > 0x80040E05." or just "Exception occurred." > > Seems to have started around the time I changed SQL Server to run as a > domain account instead of the localsystem account. Could this be the > cause > of these errors? > > Thanks in advance! > > Cheers, > Simon
From: Simon Darwent on 31 Aug 2005 18:28 Ok, I believe my problem was caused by a faulty web part. I was able to stop the error in the Application log by determining which page was causing the error to occur. I checked in the IIS logs to find the error messages (requests for page '/_layouts/1033/error.aspx') and then realised that they always occurred after a request to the home page of the root Sharepoint site. (/default.aspx) Sometimes it would open properly, sometimes it would fault. So I deleted all of the web parts on the home page and the problem has gone away. I am gradually re-adding the web parts one by one to see which one causes the problem. Don't know if this will help anyone else, but in my case it was the web part that did it. Cheers Simon "Herman" wrote: > Hello > We also have this problem, same error but the faulting module is always > ntdll.dll version 5.2.3790.1830. > We haven't change anything with the SQL server. > I hope too you/we can get some help here. >
|
Pages: 1 Prev: Disable the Shared Workspace pane? Next: Using WSS web serive and lookup field format. |