Good evening everybody,
In my company we working with a SharePoint Server OFFLINE, and we are trying to audit logs from share files, delete files, etc.
In the Site we setting like we read in Microsoft Community but the Logs dont give us much info we need, just some info but it's not clear
Site collection audit setting
And we know the Logs are left in the URL: C:\Program Files\Common Files\microsoft shared\Web Server Extensions\16\LOGS
My question if you know more ways to check all info with logs from Sharepoint.
Per my knowledge, audit logs are the only option to konw information about share files nad delete files.
Logs in the Program Files are about behind scenes of services in the SharePoint.
Related
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
I have noticed that IIS of Azure Web-Roles is generating a lot of logs, most indicating access of web-spiders.
They are stored in the "wad-iis-logfiles" blob container.
What is the easiest way of disabling these kind verbose unuseful logs?
Windows Azure is simply transferring the IIS logs to blob storage, so whatever's in them is going to get transferred. If you don't want those logs at all, just change your Diagnostics config. If you do want IIS logs but somehow want to filter out these requests, I think you'll have to do that on the IIS side.
(I'm not clear on which of those things you want to do.)
not a direct answer to your question but 'The David Aiken' has a nice blog post and script how to handle these at a deployment level...
How To Clean up old Windows Azure diagnostics
http://www.davidaiken.com/2011/10/26/how-to-clean-up-old-windows-azure-diagnostics/
I'm interested to know how to do it in Azure/IIS (start-up task against IIS?)
Update you need to add WaIISHost.exe.config file like the diagnostics.wadcfg***
Yesterday, I was having trouble trying to publish a Visual Studio web app to the wwwroot folder. I could publish it to other folders. The suggested solution to fix the issue was to give the logged on user full rights to the folder. That worked, but I was puzzled because the active user, BESI-CHAD/CHAD, was an Admin user (see image at the bottom of the linked page.)
Now, I am trying to uninstall and re-install TFS and I get the following error suggesting that the user Chad is not in the ServerAdmin role-but I am in that role!
What is going on here?
Error [ Configuration Database ] TF255286: An error occurred while verifying you have the SQL server permission or role membership: serveradmin. You may not even have enough permissions to check. Consider adding your account to the sysadmin server role. The server hosting the databases is BESI-CHAD. The error was: TF30040: The database is not correctly configured. Contact your Team Foundation Server administrator.. See the log for more details.
I ended up using another SQL instance for my TFS db server, an express instance. That worked. I didnt really want another instance. Now, I want to know what happened. If there is a good theory, I might blow away Express and reinstall TFS again.
THis was a while back, but if memory serves, I was an Amdin on the SQL server but did not have rights to the db.
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.
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