I did a restoration of the complete site collection using the stsadm restore into a new farm. The site as it is work good but I have one wiered issue that whenever I visit the root site I get the following error.
If I visit the sub sites directly this is what I see in the top navigation
Here is what I have found in troubleshooting it
If I do a app pool recycle or IISReset the issue is gone and site works perfect
The error comes back after few minutes of site usage
The different steps that I took after looking at few other places are
Deactivate and reactivate the SharePoint Publishing Infrastructure
Change the master page
Reset the blob cache, output cache and object cache (I doubt this was the fix, cause cache is not enabled)
Clear the sharepoint configuration cache as per this site
Please let me know your thoughts on how I can fix this and following in the farm details
Server - Windows 2003 x86
SharePoint - MOSS 2007 with build number 12.0.0.6656
Thanks
Deepak
Deactivating and reactivating the publishing site feature in the Site Collection and Web fixed it.
I have made a new web application on sharepoint foundation 2013 using the steps mentioned in link below.But when i try to access it using both server and client i get the message "401 UNAUTHORIZED".what to do?
http://sharepointgeorge.com/2012/create-web-application-site-collection-sharepoint-2013-preview/
I made it on a client pc having rights of administrator.I have tried quite a few thing by changing iis settings but this problem is not getting solved.Any help would be greatly appreciated.
Do you have kerberos enabled in this environment? If it's not configured correctly, this behavior can happen. You might check your logs to see if there is any additional information.
I am publishing the site using VS 2012 Publish website option. But the site does not get updated. I have to restart the website from manage.windowsazure.com every time after publishing.
I have been running the website on both free and shared mode. Same situation in both mode.
Any suggestion how to update the website automatically after publish?
Mmm. If your change regards CSS and JavaScript, try browse your website by using Ctrl+F5. If it seems totally not being updated, you might need to check the deployment page of your website on azure portal to see if it's get updated or not, or something wrong.
HTH
We are looking at logs on our sharepoint and see a call to this web service from several PC's.
The calls apprear very regular every 5 mins, when the PC is on.
Anyone know what is causing this?
Edit
The agent in the iis log is: Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.1;+HO32602;+HO32600;+HO32501;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727)
In addition to the above (which is likely) it could be one of the desktop search products that MS has created.
Maybe:
Office
Workspace/Groove sync
Some custom client application
SharePoint Designer
Browser
Whats the user agent reported in the logs?
We have a SharePoint 2010 feature that works fine on my development machine, but won't activate on the staging system. It's SiteCollection scoped, the containing solution was successfully deployed on one WebApplication.
When we try to activate the feature, we get an error message with a Correlation ID. But we can't find this ID or the name of the feature in the SharePoint Logs nor in the Windows Event Log.
Maybe logging wasn't configured right or there is an error with ULS on the machine, but we haven't changed the SharePoint Logging options from the state they were after installation. Where can I find exception / error messages that happen in ULS? How must Logging be configured to allow the failed feature activation to be logged?
Under SharePoint 2010, go to Central Administration. There is a Monitoring link. Click there and under reporting is a Configure Diagnostic logging link. If you set the Least Critical event to Trace and Least Critical Event items to verbose, you should get more information in the SharePoint log files. Make sure you switch back though after diagnosing because the process is chatty and can result in extra IO and large files.
Out of the box, I don't believe logging is set. You can also verify the location of the log files to make sure they are not on setup elsewhere on this page.
More information at TechNet
Download the ULS Viewer tool from here: link text and filter by the correlation ID.
This is an old post, but if soone gets the same problem, please try the following:
Check who is your farm account user (the user under which SharePoint Timer Service is running).
Add this user to local administrators
Restart Timer Service.
Please mark this as answer if my solution works for you.
You can always get information from the logs from all servers in the farm using the Merge-SPLogFile cmdlet. The example below filters on a correlation ID, but there are more filter options (tip: Get-Help Merge-SPLogFile -Full).
$corrID="some correlation id"
Merge-SPLogFile -Path "path to output file" -Correlation $corrID
It is worth emphasizing that the OP's substantive question,
Where can I find exception / error messages that happen in ULS?
is answered by the OP himself in a comment to #noebierzo,
I found the log entry ... by checking all log files on all front-end
servers.
So be aware if you have a multi-server farm; look at all servers in the farm when checking or searching for errors and trace log messages.
Fortunately Microsoft recently released an updated ULS Viewer v16.0.3129.1000 that provides basic multi-server aggregation of the trace logs. Bill Baer, Senior Technical Product Manager for SharePoint at Microsoft has a nice blog post on the new version which outlines this feature.
The new version of ULS Viewer is available from the Microsoft Download Center. Note that this version of ULS Viewer requires at least .NET 4.0 which your SharePoint 2010 farm may or may not have installed. Bill blogs about this but doesn't comment on the impact of installing .NET 4.0 on your SharePoint 2010 farm.
If you want the old version of ULS Viewer v2.0.3530.27850 that only requires .NET 2.0 you can no longer count on Microsoft as they took down the Archive Gallery where it used to live. Fortunately a few people have posted it online, include Benjamin Athawes on his blog.
Given the .NET version dependency, and the fact that SharePoint 2010 is still a supported product, Microsoft really should keep an official link around for this prior version ULS Viewer. Suggest you ask Bill about this on his blog. Perhaps SharePoint 2010 SP2 is fully supported side-by-side with .NET 4.0, it would be good to know.