This project has moved and is read-only. For the latest updates, please go here.


Unhandled exception on W2k3 MOSS2007



When I hit the "Find Faultu Feature in Farm" I get the folling error:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.DirectoryNotFoundException: The system cannot find the path specified. (Exception from HRESULT: 0x80070003)
at Microsoft.SharePoint.Library.SPRequestInternalClass.GetAllWebsOfSite(String bstrUrl, Object& pvarWebs, Object& pvarWebIds, Object& pvarParentWebs, Object& pvarLangs, Object& pvarTitles)
at Microsoft.SharePoint.Library.SPRequest.GetAllWebsOfSite(String bstrUrl, Object& pvarWebs, Object& pvarWebIds, Object& pvarParentWebs, Object& pvarLangs, Object& pvarTitles)
at Microsoft.SharePoint.SPSite.SPWebCollectionProvider.GetWebsData(String[]& strNames, String[]& strServiceRelUrls, Guid[]& guidWebIds, Int32[]& nLanguages, String[]& strTitles, String[]& strDescriptions, String[]& strCreationTimes, String[]& strModifiedTimes, Boolean[]& bUserIsWebAdmins, Int32[]& nWebTemplates, Int16[]& nProvisionConfigs, Int16[]& nMeetingCounts)
at Microsoft.SharePoint.SPWebCollection.EnsureWebsData()
at Microsoft.SharePoint.SPWebCollection.Undirty()
at Microsoft.SharePoint.SPBaseCollection.System.Collections.IEnumerable.GetEnumerator()
at FeatureAdmin.FrmMain.btnFindFaultyFeature_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
Assembly Version:
Win32 Version: 2.0.50727.3634 (GDR.050727-3600)

CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll

Assembly Version:
Win32 Version:

CodeBase: file:///P:/My%20Documents/SP2010_Project/FeatureAdmin.exe

Assembly Version:
Win32 Version: 2.0.50727.3637 (GDR.050727-3600)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/

Assembly Version:
Win32 Version: 2.0.50727.3634 (GDR.050727-3600)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/

Assembly Version:
Win32 Version: 2.0.50727.3639 (GDR.050727-3600)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/

Assembly Version:
Win32 Version: 12.0.6608.1000

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SharePoint/

Assembly Version:
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)

CodeBase: file:///C:/WINDOWS/assembly/GAC_64/System.Data/

Assembly Version:
Win32 Version: 12.0.4518.1016

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SharePoint.Security/

Assembly Version:
Win32 Version: 2.0.50727.3082 (QFE.050727-3000)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/

Assembly Version:
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/

Assembly Version:
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)

CodeBase: file:///C:/WINDOWS/assembly/GAC_64/System.Transactions/

Assembly Version:
Win32 Version: 2.0.50727.3634 (GDR.050727-3600)

CodeBase: file:///C:/WINDOWS/assembly/GAC_64/System.Web/

Assembly Version:
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.DirectoryServices/

Assembly Version:
Win32 Version: 12.0.6602.1000

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.Office.Server/

Assembly Version:
Win32 Version: 12.0.6500.5000

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.Office.Server.intl/

Assembly Version:
Win32 Version: 12.0.6604.1000

CodeBase: file:///C:/WINDOWS/assembly/GAC_64/Microsoft.SharePoint.Search/

Assembly Version: 8.0.50727.6195
Win32 Version: 8.00.50727.6195

CodeBase: file:///C:/WINDOWS/WinSxS/amd64_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.6195_x-ww_76301166/msvcm80.dll

Assembly Version:
Win32 Version: 12.0.6602.1000

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SharePoint.Library/

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the section.
The application must also be compiled with debugging

For example:

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

System is:

Windows 2003 x64
MOSS 2007 SP3

It is no problem to list the information from each SiteCollection/Web.

Any clue on what could be wrong..

Closed Apr 10, 2013 at 5:55 PM by PerrySharePoint
Closing as obsolete per previous comment


ismailia wrote Jan 21, 2013 at 7:33 PM

Hm, not sure, what it is, here are just a few suggestions:- do you have web applications with host headers defined, that the local system does not know?
  • can your user account access all web apps, all site collections and all webs? (try to add it to farm admin group, give full control in all web apps via policy and grant owner rights to config db and all content dbs on SQL Management Studio)- also make sure, you are in the local administrators group
  • do you already know of any issues or problems in the farm?
  • try to detach all content databases or even delete web applications

PerrySharePoint wrote Feb 4, 2013 at 1:50 AM

The exception trapping I've just added to this method should help give more specific location information.

ismailia wrote Feb 24, 2013 at 9:13 PM

Please try again with Version 2.3 of the FeatureAdmin.

ismailia wrote Feb 24, 2013 at 10:45 PM

This Problem should be fixed with the release 2.3 of FeatureAdmin for SP2013.

There is a new property Compatibility Level available in SP2013, when Feature definitions are uninstalled(/removed).This was not recognized before. Now, this property is tracked and set when removing Feature definitions.

Issue solved.

ismailia wrote Feb 24, 2013 at 10:56 PM

Sorry, this issue is not fixed, as stated in my other comment, a problem in SP2013 was fixed regarding a discussion, not regarding this topic ...

PerrySharePoint wrote Feb 27, 2013 at 6:27 AM

Please try again with version 2.3 and post results.

PerrySharePoint wrote Mar 20, 2013 at 7:46 AM

Submitter has not responded to any questions and nearly two months have gone by. This is probably obsolete.

ritdominion wrote May 2, 2013 at 10:20 PM

This is still an issue with Windows 2003 x64MOSS 2007 SP3

We get the same error with version 2.3. Pl. Help