How to find the error detail on Sharepoint Services 3? - sharepoint

I remembered that there is a log file that you can check for Sharepoint Services 3.0. I don't remember where I can find this. The reason I ask this I have an error when implementing the new template and it works on one, but not on the other machine. The error on the page is very generic: "The template you have choosen is invalid or can not be found".
Thanks

SharePoint log files are usually in the "Logs" folder in the '12 Hive' which by default is in C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\Logs.

It's easier to have the error displayed completely. You can enable this by modifying the web.config.
Find the SafeMode entry in your web.config and change CallStack="false" to CallStack="true". Then find the customErrors entry and set mode to mode="Off".
Now errors will be shown as a complete ASP.NET error screen

Related

SharePoint 2013 Central Administration

A few years ago we moved SP 2013 Central Administration to another box. Now we moved it back to original box (on a 2 wfe Farm) because box has hardware issues and needs to be replaced. The web config file is coming up with errors.
**Server Error in '/' Application.
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed.
Details: To enable the details of this specific error message to be viewable on the local server machine, please create a tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "RemoteOnly". To enable the details to be viewable on remote machines, please set "mode" to "Off".
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's configuration tag to point to a custom error page URL.
Can I delete all files in virtual directory of this web config and have SharePoint wizard remake it? Is that a viable solution?

Unable to delete Sharepoint site

I'm trying to delete a subsite in my site collection, but I get an error that says "Can not reach the Messages.xml file!"
A few days ago I was able to delete a site, but now it seems to be impossible to delete any sub sites.
If I use the stsadm deleteweb with force parameter I'm able to delete, but I would like to be able to delete sites via the interface.
I'm thinking that the error might be coming from some feature because the error message is in english and all other Sharepoint msg is in danish(Running a danish version of Sharepoint 2007)
Any suggestions?
Regards
Birger
The problem was happening because the MSITDeleteFeature had been installed some time ago and after moving the site to a new server som of the feature was not correctly installed on the new server.
The missing Messages.xml was a part of the feature and should have been placed in this folder
C:\program files\common files\Microsoft shared\web server extensions\12\template\layouts\1030
After copying the file to the folder the problem was solved.
/Birger

Problem with custom MembershipProvider in SharePoint 2010

I'm having a problem getting a custom membership provider to work in SharePoint. The login page is displayed, but when I enter any credentials - right or wrong - I get the following error:
The given assembly name or codebase was invalid. (Exception from HRESULT: 0x80131047) (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\Root\web.config line 22)
Line 22 is where my membership provider is configured. Its also configured in the root web sites web.config (since it needs to be configured in every virtual directory). If I remove line 22, I get the error complaining about the provider not being in every web.config, so that part seems to be working.
On the same web server, I have set up a default MVC project and confirmed that the membership provider works fine. I know sharepoint is loading it at least partially, because if I make it throw an exception in the constructor, I get a different error (Exception thrown by the invocation etc.), and the login form isn't even displayed.
The DLL is built as AnyCPU, against .NET Framework 3.5, and is in the GAC. The server is running Windows 2008 R2, 64-bit.
Can anyone point me in a direction to try?
Have you entered a <SafeControl> entry for the Membership provider?

An unexpected error has occurred

I have created an asp.net web application on my local machine and I am deploying it to sharepoint. For that I am refereing the following
Deploying ASP.NET Web Applications in the Windows SharePoint Services 3.0 _layouts Folder
[http://msdn.microsoft.com/en-us/library/cc297200.aspx]
Its works perfect on my local machine but when I was trying to deploy the same on clients machine it was giving me the "An unexpected error has occurred." Error.
The scenario is, There is not visual studio install on my clients machine so what I was doing is I simply copying my solution folder in 12'hives LAYOUT folder along with the bin folder. Then when I was try to access it by hitting the URL
http://[machineName]/_layouts/[MyCustomFolder]/default.aspx it was giving me the error mention above.
Can anyone help me to solve this issue..?
Thanks in advance..
Sachin
Unexpected error might be anything, You need to see what is the root cause of the Error,
Open the Web.Config file of the IIS SharePoint WebSite
Search for the CallStack and change it to CallStack="true"
Search for the CustomError and change it to CustomError="Off"
Browse the page you will get to know the actual issue that causes the error
You yourself can rectify it , it might be as simple as missing dll
Try to watch the logfiles, set logging level to maximum to be sure you see what sharepoint says about your page.
To do that, if you have access to the server:
open SharePoint Central Admin
go to Operations tab, select "Diagnostic logging"
select category 'All' and change the trace log level to 'Verbose', save changes
reset IIS server (for the purpose of a clean experiment)
open \\server\c$\Program Files\Common Files\Microsoft Shared\web server extensions\12
logs and order by modification date
try to load your webpage in /_layouts folder, see the error again
open the newest logfile you can see and search for [MyCustomFolder] name
Then post the error message here.
An unexpected error can have multiple reasons.
Go to C:\inetpub\wwwroot\wss\VirtualDirectories\80
Open Web.Config
Change
<SafeMode MaxControls=”200″ CallStack=”false”
to
<SafeMode MaxControls=”200″ CallStack=”true”
Turn off custom errors
<customErrors mode=”Off”/>
I know that is an old question but for me the fix was to stop and start again the SharePoint Web Application from IIS.

"Class not Registered" restoring a Sharepoint ( WSS ) 2003 backup.dat file

I need to do some work with a backup WSS .dat file and I'm having real trouble making it do anything.
I've got it installed through stsadm and that appears to have gone smoothly, but the site now redirects me to an error page - just the classic "File Not Found" one, but in the URL it suggests the errortext would be "Class not Registered" if there was a more informative error message.
When I run "stsadm -0 enumsites -url=http://my-restored-site/" I get this:
C:\>"C:\Program Files\Common Files\Microsoft Shared\web server extensions\60\BIN
\stsadm" -o enumsites -url http://my-restored-site
<Sites Count="1">
<Site Url="http://my-restored-site" Error="Class not registered" />
</Sites>
Is there any way for me to tell what class is not registered or is there something else altogether going on here? I have enabled Sharepoint logging but it appears to have had absolutely no effect, certainly no file exists on the path I have asked it to use.
Here is what I do in such a case:
Use procmon to track down registry usage. Have an eye on HKCR\CLSID and NAME NOT FOUND results therein.
Take note of the CLSIDs it is not finding, Google them up to get a clue if they might have to do with your problem. Find out which .dll provides them, and register that .dll with regsvr32 (or use the respective installer for the missing component, if a whole bunch of stuff is missing).

Resources