I have a project which uses SharePoint lists as data sources to create the reports. I'm using Visual Studio 2013 for this.
I have this real annoying issue at this moment, ie. when I want to edit a dataset I created a while ago and I press 'Query Designer...' in the dataset properties to see all fields from my list I get an error which says that I am unauthorized.
My DataSource is configured to link to the SharePoint Site Url with Windows Credentials. I have also tried this out for multiple datasets on multiple reports but the error is everywhere.
Because of this I'm also not able to run my reports. They just say "An error occurred during local report processing.".
I have been working on this project since March and this is the first time this has occurred so I have no idea what might have gone wrong nor how to solve it.
Does anyone know what might cause this error and how to solve it please?
If you have any questions or remarks about my question/problem, please, don't hesitate to leave a comment.
Kind regards
EDIT 1:
I have just tried deploying a report that I finished last week and for the first time I got a prompt that asked for my credentials. I haven't even put my credentials anywhere in the project for past authorisation so I have no idea why the project would suddenly need it now...
EDIT 2:
I have just tried changing the DataSource credentials to my own login for the SharePoint Site. If I run the report I get the same error as before but when I go to Query Designer for one of the datasets I get following error:
EDIT 3:
I just restored a back-up I made a couple of weeks ago. I can now run my reports but I still get the Unauthorized error when I try to open a dataset's query designer and the prompt for my credentials when I try to deploy a report.
So, the solution has been found!
Apparently something has gone wrong with my PC and I had to reconfigure my user accounts.
To do this go to Control Panel -> User Accounts
Then click on 'Manage User Accounts'. Go to the 'Advanced' tab and click on 'Manage Passwords'
Next, go to 'Windows Credentials' and change the credentials for your site or recreate them.
Related
Last month, I had a Sharepoint addin installed into a clients Project Web Access (pwa) server working quite well.
This month, when I try to compile and run a new version of that same project in Visual Studio, I'm getting a popup asking "Do you want to switch the project to Offline mode?" and if I say 'No', I get a "Communication with the SharePoint server is Cancelled" error when uploading my project.
There have been no configuration changes. The only code changes were to a .JS file (and we reverted those changes, just in case).
There may have been updates to Visual Studio during that time.
I have...
Ensured that the server name is correct and unchanged.
Ensured that the 'Server Connection' property for the project is 'Online'
I can't find any useful diagnostic information anywhere.
Does anyone have any suggestions about how to resolve this, or at least how to get some diagnostic information about why it's happening?
It appears that Office365/SharePoint Online has new defaults that prevent access from external applications ( I was also unable to connect via PowerShell scripting using my Sharepoint Online credentials).
I updated the settings under Policies|Access Control in the Sharepoint Online admin console to allow connection, and now I can connect from PowerShell, and I've got a different issue in Visual Studio.
While I still don't have diagnostic information about communication problems, I've managed to get a little further.
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 am new to Sharepoint and was playing with the webparts. I downloaded a zip file called LyteBoxForSharePoint and uploaded the webpart using add a web part function. Now I am getting errors. The good thing is, that it's only my dept page. The bad thing is I have no clue what happened. All other pages beside the dept landing page is working. So, I am guessing it's only the landing page that has the issue. Is there a way to find out what code was added or to revert to old code. The error I get is the following, and it keeps on changing every time I refresh the page.
An unexpected error has occurred.
Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: e8eca359-70f9-42d0-b41e-834fbe0fc910
Date and Time: 2/23/2012 2:47:39 PM
Could be anything, most common error in SharePoint is authentication errors where a web part is trying to reach content the logged in user cannot reach
You should check the logs, they are available in the directory C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS
Open the last modified log file and search for your Correlation ID, e8eca359-70f9-42d0-b41e-834fbe0fc910
When you find the errors there you will now and also be able to post something that we can use to help you.
Then there is always the webpart maintenance page: /_layouts/spcontnt.aspx?url= http://sharepointserver.com/_layouts/spcontnt.aspx?url=default.aspx
Rex,
first browse the page which is giving webpart error and copy the new correlation id and go to the log folder under 14 hive and open the latest log file and find the correlation id. it should give you the error details if logging is not disabled.
also you can go to the webpart manger on the page to revert the page to the previous state by adding contents=1 as query string and in this page you will get list of webparts with checkbox against each. select the faulty one and revert to previous version if any or delete it.
you can also use SPD2010 to remove the webpart with error. alternating powershell can be also used.
One way to check if the webpart is installed is to type ?contents=1 after your url. There is also stsadm -o preupgradecheck and unfortunitely stsadm has another command to list all webparts but I cannot think of it at this time
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.
When adding or editing a page in a SharePoint Pages library we get the following exception:
[COMException (0x81020016): Item does not exist
The page you selected contains an item that does not exist. It may have
been deleted by another user. Click "Home" at the top of the page to return
to your Web site.]
at Microsoft.SharePoint.Library.SPrequestInternalClass.RenderColumn.
The weird thing is, when we first do "Check in" and then click the Publish button it works perfectly. But clicking "Publish" directly generates theis error, BUT NOT ALWAYS!
The Pages library has publishing and item planning on, NO workflow (seeing as the person who adds / edit pages is also the approver) and Major/ Minor versions.
We use a content type derived from publishing page and a custom PageLayout.
I'm sure you would have already checked this but is there any more information in the ULS logs?
Also have you tried setting the debugger to break on all exceptions and does this give you more information? Go to Debug, Exceptions and tick Common Language Runtime Exceptions. Then go to Tools, Options, Debugging and untick Enable Just My Code. Finally attach to w3wp.exe.
If you are running Windows Server 2008 you could also try taking a dump file at the point the debugger breaks above. ADPlus might help if you are running Server 2003 but I don't have experience with it. You should then be able to open the dump file with DumpChk or WinDbg.
Edit: As discussed in the comments, this is code deployed to production that can't have its service interrupted. The only way you could create a dump file is programmatically. Have a look at this question I asked that will hopefully help you if you need to go down this route.
Other things to try if you don't want to get down and dirty with debugging is to try deploying your custom bits to a clean server. See if you can still reproduce the problem or if it changes.
I am assuming that you are using load balancing with 2 web servers.
The fact that it does not happen always points to there being a difference between the servers.
There are then a few things that you could check:
Are all the versions and service packs are the same on both machines
Have any of the servers had beta software installed
Is your code the same on both servers
One thing you could do to test without taking the system down: Is to remove the first web server from the cluster see if the error occurs, then add it back and do the same thing with the second web server.