I was going through the Extensibility Hands-on Labs for Microsoft Enterprise Library 5.0 and found an error in the "Lab 2: Custom Logging Trace Listener" lesson. It applies to exercises 2,3 and 4 in the lab. I searched through the issues tracker on the CodePlex site but could not anything related to this error.
Overview of the problem:
When attempting to add the trace listener via the Enterprise Library Configuration tool I get a validation error : “The field ListenerDataTypeName is missing a required value”. Therefore the configuration tool will not save the config file.
Looking for suggestions.
Found the solution myself see the following blog post for full description of fix:
http://mvvmdevotee.wordpress.com/2012/12/30/fixing-an-error-in-extensibility-hands-on-labs-for-microsoft-enterprise-library-5-0/
Related
I am having a problem with Microsoft Projects (Online Only). Getting the error as shown in the image below. Anyone knows how to resolve this issue?
Found the solution to the problem on this blog:
https://blogs.msdn.microsoft.com/brismith/2018/03/05/project-online-why-might-my-site-go-read-only/
In my case, the issue was that I required at least one Project Online Professional or Premium license to keep the Free Projects Online for EDU working.
I have been trying to deploy a sandbox solution on SharePoint online but unable to deploy it. The technique I am following is to develop a sandbox solution on SharePoint 2013 on premises and extract .wsp file which I take to SharePoint online and upload this .wsp in Site Settings --> Web Designer Galleries --> Solution. But when I upload the solution it gives me the error below:
enter image description here
After googling this issue I came across this article http://www.sharepointnutsandbolts.com/2016/08/sandbox-code-disabled-in-Office-365.html which says that the activation of sandboxed solution is disabled last couple of weeks before.
After more googling I found the solution of this issue from an article which asks me to set Include Assembly in Package property of my solution to False. This resolves the above activation of sandboxed solution issue but when I go to my page and try to add the web part it gives me this error “$Resources:core,ImportErrorMessage;”.
I tried a lot and invested my 2 days with no solution. Your support will be appreciated.
Thank You,
You are right that the activation of sandbox solutions in O65 has been disabled. Microsoft has publicly announced the same with different articles.
http://dev.office.com/blogs/removing-code-based-sandbox-solutions-in-sharepoint-online
https://blogs.msdn.microsoft.com/sharepointdev/2014/01/14/deprecation-of-custom-code-in-sandboxed-solutions/
Try the following and check if retracting and deploying the solution works for you.
Open Visual Studio -> Build -> Select 'Retract'
I am uploading my wsp file and when I'm trying to activate it getting this error:
Exception from HRESULT: 0x8107054A
TECHNICAL DETAILS
Troubleshoot issues with Microsoft SharePoint Foundation.
I can't comment so this is posted as answer.
You have to analyze the ULS-logs concerning the given correlation ID.
Vardhaman Deshpande has put togehter a great article on this on his blog
http://www.vrdmn.com/2014/03/view-tenant-uls-logs-in-sharepoint.html
It's merely based on using the and namespace Microsoft.Online.SharePoint.TenantAdministration and the class TenantLog.
Best of luck
Ben
I have deployed an SSRS 2008 R2 project into our SharePoint Integration. This worked no problem. I then wanted to add report parts. I converted the DataSource and DataSets to Shared Components and re-deployed. No problem. I then selected the parts that I wanted to publish. Now when I deploy the project I get the error message:
Warning : Referenced item ReportsTo doesn't exist at http://dev-sp01/sites/CompanyName/Shared Documents/Reporting/Datasets/ReportsTo.rsds.
The item ReportsTo is a part that is trying to get published. This has me a little confused. I was under the impression that the rsds file type is soley for DataSources. Given that the path that is in the error is Datasets should it not be looking for a DataSet file?
Any help in resolving this to get the parts published would be greatly appreciated.
I am working in BIDS 2008 R2 not Report Builder
UPDATE:.. After Reviewing the Logs on the Reporting Server I noticed this.
GetPropertiesAction(http://dev-sp01/sites/ThriveReporting/http://dev-sp01/sites/CompanyName/Shared Documents/Reporting/Report Parts/TeamUtilizationOverWeeks_Chart.rsc, PathBased).
It looks like it is trying to merge the Site name with the Fully Qualified Path to the Reports Parts. In BIDS I've tried to change the Report Parts path in the deployment properties to the relative path to the Site Name provided, but it errors out and requests the Fully Qualified path. It would seem that this might be a bug.
So to Recap
When trying to Publish Report Parts
1) Bids Gives me the Warning:
Warning : Referenced item ReportsTo doesn't exist at 'http://dev-sp01/sites/CompanyName/Shared Documents/Reporting/Datasets/ReportsTo.rsds.'
Where ReportsTo is a Shared Dataset, so I beleive this should be looking for an rsd extention. In the Log there is a corresponding action for this but not error
Warning : Referenced item ReportsTo doesn't exist at 'http://dev-sp01/sites/CompanyName/Shared Documents/Reporting/Datasets/ReportsTo.rsds.'
GetItemTypeAction(http://dev-sp01/sites/CompanyName/Shared Documents/Reporting/Datasets/ReportsTo.rsds).
2) Reporting Services does not appear to be creating a path correctly to access a Report Part during deployment.
GetPropertiesAction(http://dev-sp01/sites/CompanyName/http://dev-sp01/sites/CompanyName/Shared Documents/Reporting/Report Parts/TeamUtilizationOverWeeks_Chart.rsc, PathBased).
From Microsoft, I am submitting Feedback now.
Hi Matt,
I can reproduce the issue. It seems to be a known issue.
I would suggest you submitting a feedback at https://connect.microsoft.com/sqlserver.
Your feedback enables Microsoft to make software and services the best that they can be, and you can learn about and contribute to exciting projects.
Thanks,
Jin Chen
Jin Chen - MSFT
UPDATE:
Please go to this link and vote this issue as important so that it will get looked at sooner.
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.