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.
Related
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 created some reports in Report Builder for SQL 2012, before I realized that managing multiple reports is substantially easier in VS 2012. I created a reporting project in VS2012 and added the existing reports by right-clicking on the Reports icon in the solution tree, selecting Add ==> Existing Item and then navigating to and selecting the reports. I also added or recreated the data sources and data sets as needed.
Most of my reports "migrated" with no problems, and I was able to deploy them to a new dashboard and get a more unified experience for the users. However, a couple of the reports give the following error when I try to preview them:
The given path's format is not supported
Some of these reports deploy successfully and run in the SharePoint site, others do not. But my ask at this point is, can someone give me any tips on where to look for the cause of these errors? The Error and Output windows in VS2012 don't give file, line, or column info, so I just have no idea where to look. I have searched for as many URL or path references as I can in the query results, action targets, etc., and removed them when I found them, but the problem persists. If someone has any thoughts, or can tell me some settings to turn on in VS that might give me more information, that would be appreciated.
I'm getting a DirectoryNotFound exception when attempting to add my custom web part to a page. It seems pretty straight forward since it's complaining about not being able to find the "feature.xml" file for the web part. What is odd is that the Directory that is showing up in the error message is completely different from the one that the Web Part is installed in. So the file it should be looking in is \12\Template\Features\WebPart1\feature.xml but it is looking in \12\Template\Features\WebPart2\feature.xml.
Can someone explain to me how Sharepoint performs feature activation or point me to a link that is helpful?
Thanks,
Jason
--Edit more information --
I'm using WSPBuilder to create and build the Sharepoint feature. My understanding of how this should work is that WSPBuilder will copy my feature.xml file to the Sharepoint site and my .webpart to the wp folder. When I activate a feature it will look into the feature xml file and reference the .webpart file that will contain the configuration for which webpart class to load. The webpart2 folder that it is currently referencing is an old feature that I uninstalled so it must somehow be confused as far as where the feature folder is but without knowledge on how it determines where to look I'm at a bit of a loss on how to correct it. Does it save the guid in the SP database somewhere? Any information on how this feature activation process works would be helpful.
I'd vote myself down if I could... that error message had nothing to do with the problem. It was an exception that was being thrown but being caught in Sharepoint.
The SharePoint install is a SP2010 install on a 2008 R2 server. Everything is fully patched. I am running the SP Designer on the SharePoint Server directly.
I have a workflow which is intended to send an email when a new document is created in a custom list. I have deliberately kept the workflow very simple in order to illustrate this problem.
After creating this single step workflow in SP Designer, I click "Check for Errors" and SP Designer reports "The workflow contains no errors".
I then click "Publish" but the Workflow Error dialog is displayed with the message
Errors were found when compiling the workflow. The workflow files
were saved but cannot be run.
Clicking the advanced button reveals more information:
Could not publish the workflow because the workflow configuration file
contains errors
Any suggestions gratefully received
I'll share what fixed it for me - deactivating all workflow features at the site collection level (that is, Workflows, Three-state workflow, Publishing Approval Workflow) and then reactivating the features. I was then able to publish my workflow. This post helped, not sure whether this only works for 365 though, but it's sure worth trying first if you are considering a reinstall.
after googling for quite some time, i think it's an authentication issue. How is your SharePoint set up? Do you use HTTPS for authentication? If so check out this article.
I know this error message from sharepoint. I got this by dealing with multiple lookup fields refering to other lists. Even when I check the worfklow for errors SharePoint says that its all fine but i can't publish it at all.
Try to build a new Test-Site on your Site Collection. Build a Custom Document Library, leave it standard and then set up a new simple workflow just sending a mail.
Fill out the needed fields in mail only using simple values. Send to your mailadress, simple mail subject and simple mail body.
Set the workflow to run only manually.
Try to publish the workflow.
When this is working, then compair to your existing workflow and change your values by trail and error.
After doing a clean install of the OS and SharePoint, workflows are working flawlessly. I can only conclude that the problems were caused by left over registry settings from MOSS 2007. Thanks for the suggestions that people made.
This could also happens if you chage the URL of the web application, all you have do is click the Design button from the library itself.
when changinf the URL from http://server/Site to example: http://server.xx1.net/site, and you try to publish it tries the old url.
what helped in my situation is changing from start workflow automatically to manually.some times answers for critical situation is very easy. hope it helps, many thanks
I ran into this problem and after digging for days and folks suggesting to rebuild the servers, disabling and re-enabling site features, remove previous workflow versions, etc. and trying everything except rebuilding the servers (not practical for clients production environment). I decided to try some tests and found that this issue was only happening on one particular list no matter how simple or complex the workflow was... And when I would check the box for start automatically on item create (or when item changed) it would fail to publish and give the error above, but if I published it with just manually start worked fine. Finally after deleting views and some more testing, I discovered that there was over 240+ columns in this list (I did not create it...) and 50+ workflows set to run on create... Thankfully I have a test environment I built out for the client so I sync'd the Site Collection database back to test environment from Production re-ran my tests and got same error... So what resolved the problem and what was the ultimate cause of the problem, there was to many columns defined in the list and I had to delete several columns to publish the workflow in the test environment. This actually issue translates into the there is a limit in SQL Server on how much data the list can store each type of column takes up so much space read more about it here:
https://technet.microsoft.com/en-us/library/cc262787(v=office.15).aspx#Column
So what I did in production was worked with my client to determine how to break up the list into multiple lists and have relationships between them, thus moving some of the columns and data to another list (Think database/list normalization)... I hope this solution helps someone.
Not quite sure what I've done to screw up SPD2010 (was working), but it displayed
Sharepoint Designer cannot display the item
What you can try:
Click refresh ... blah
Most likely causes
The file has been deleted from the site
The site is encountering problems
I can't see anything related in event viewer. I think is web service related as I think the queries are made via a WS?
In my case it wasn’t a solution. So, I made a backup of the site collection before to try anything. After a lot of time and different problems I figured out that some lists were causing the missreading. I tried one more time to get the lists in SharePoint Designer 2010 just to cause some entries in the log. After that I opened the log file and looked for something like: “Failed to determine the setup path of the list schema for feature {GUID}, list template XXX.”. With the GUID I looked for a match here. http://sharepoint-geek.com/2010/10/08/sharepoint-2007-moss-features/
With the feature name I used this blog: http://aurramu.blogspot.com/2011/03/failed-determine-setup-path-of-list.html.
With the feature re-installed I went to SPD and it worked like a charm.
I hope it helps someone else.
It appears this was caused by a "phantom" list definition. I experienced a number of other problems (some in SP some in SPD), all generating variations of this error;
<nativehr>0x8107058a</nativehr><nativestack></nativestack>
The problem list definition was deployed and undeployed from VS2010, so I have no idea why it was still around! The Sharepoint UI wont allow you to remove it (errors as above), so the trick is to use the stsadm powershell command with forcedeletelist as detailed here
http://technet.microsoft.com/en-us/library/cc262609(office.12).aspx
Hope this helps someone else !