Blogroll

Wednesday, March 26, 2014

Performance Point Service could not connect to the specified data source

Error Message:
PerformancePoint Services could not connect to the specified data source. Verify that either the current user or Unattended Service Account has read permissions to the data source, depending on your security configuration. Also verify that all required connection information is provided and correct.



How to reproduce this error?
1.   Open your site in browser
2.   Click on Run Dashboard designer


3.   You will see two options Data connections and PerformancePoint content
4.   Right click on Data connections -> New Data source


5.   Select the data that you are trying to connect (SP list, SQL Server table, analysis servicesexcel services)
6.   BOOM -> You will get the error at this step!

How to resolve this issue?

Here are the details: [2 step resolution]

Make sure the unattended account has already created. If this is not yet created then please use this linkhttp://sharepointknowledgebase.blogspot.com/2013/10/unattended-service-account-for.html

Before you start any troubleshooting, please ensure you check your ULS logs as it will give you the exact root cause behind it. When we checked our ULS logs then we found out that “the account needs Read Permission”)

It’s pretty simple once I know the cause. How to check this?
1.   Central administration
2.   Manage web applications
3.   Select the web application which is associated with your site
4.   User Policy
5.   Assign full read permission to unattended service account.


Wow, that's a big workbook. Unfortunately, we can't open a workbook larger than 10 MB. You'll need to open this in Excel.

Problem description:
One user has reported an issue where he was getting an error while accessing the excel files from SharePoint site.

Before contacting the user, I tried uploading one dummy excel file to check the behavior and it works fine so I thought it might user who is doing some mistake. Further probing on the issue, I got the following details.

Entities:
1.   SharePoint 2013
2.   Excel 2013 / Office 2013
3.   Internet explorer 8.0

How to reproduce this error?
a)   Upload your excel document in the document library
b)   Try to open this document by directly clicking on it or excel dropdown ->view in browser.
c)   You will get the following error:

Error Message#1:
Wow, that's a big workbook. Unfortunately, we can't open a workbook larger than 10 MB. You'll need to open this in Excel.


Error message#2:
Couldn't Open the Workbook. Wow, that’s a big workbook. Unfortunately, we can't open a workbook larger than 10MB. You'll need to open this in Excel.

Error message#3:

The form submission cannot be processed because it exceeded the maximum length allowed by the web administrator. Please resubmit the form with less data.

Resolution:
a)   Central administration
b)   Application management
c)   Service applications
d)   Manage service applications
e)   Excel Services Application
f)    Trusted File locations
g)   Select the document library where your web part is failing
h)   Refer the section named as “workbook properties”
i)     Change the maximum workbook size
j)    By default its 10MB
k)   Change it to 50MB / 100MB as per your requirement
l)     Click OK.

Product applies to:
1.   SharePoint 2013
2.   SharePoint Foundation 2013
3.   SharePoint 2010
4.   SharePoint Foundation 2010

Tuesday, March 25, 2014

SharePoint Timer Service Delays

Timer job plays a very vital role in the SharePoint environment as so many task’s, jobs, schedules as well as workflows are depend on it.

Bottom line (important one):
1.    Clearing the timer job history
2.    Recycling the timer service
3.    Workflows

Microsoft SharePoint Server 2010 uses the Windows SharePoint Services Timer V4 (SPTimerV4) service to run most system tasks.

How you will conclude that the timer jobs are not working as expected?
Here is the list:
o   Alerts are not working
o   Workflow: either not running / taking a long time to update
o   Updates to the farm configuration are not synchronized to the local server.

Make sure / Resolution:
a)   Start-> Run -> services.msc -> will open the services console.
b)   Press ‘S’ in the list of services and it will show you the list of SharePoint Services
c)    Right click on ‘SharePoint Timer Service” and Restart it.

d)   Ensure- it gets started successfully. If not then use the following way

e)   Start ->Run- >cmd ->it will open the console window -> net start sptimerv4

f)     If the service does not start, ensure the following parameters are correct:

g)    It should be a domain user account and is a member of the following:
·         dbcreator fixed SQL Server role
·         securityadmin fixed SQL Server role
·         db_owner fixed database role for all databases in the server farm

h)   If the account has sufficient permissions, confirm the password by typing the password for the account, retyping the password in the Confirm password box, and then clicking OK.

If the workflows are taking long time to complete then please change the frequency:
stsadm -o setproperty -propertyname "job-workflow" -propertyvalue "every 1 minutes between 0 and 59" -url http://webapplication
For more information, please see http://technet.microsoft.com/en-us/library/cc424970.aspx. The default value is "every 5 minutes between 0 and 59"

Monday, March 24, 2014

The server was unable to save the form at this time. Please try again - SharePoint 2013

SharePoint 2013 is always full of mysteries as it’s a starting time and most of the firms are doing the migration of their SharePoint 2010 environment to SP2013 platform. So it’s quite obvious it will take some time to make your farm stable!

Note:
If you find a different solution, please report it as a comment to this post. Be sure to double-verify it: undo your solution and verify that the problem comes back, then redo it and verify that the problem goes away.

Problem description:
We have recently done the migration from SP2010 -> SP2013 in our development environment and given access to limited number of high profile users and developers for the testing. While doing the testing, one of the developers has reported an incident mentioning he is facing some error while editing the list item. Further exploration reveals that we can’t add a new item also.

So bottom line, this error comes up while: Adding a new item in a list or at the time of editing the item

Error Message:
The server was unable to save the form at this time. Please try again.



Troubleshooting done:
1.   Tried creating different list with some different template / type but same issue.
2.   Checked the list in SharePoint Designer 2013 but didn’t find anything relevant.
3.   Checked the site settings for any customized content type but it was using default settings
4.   Checked the event viewer for any critical errors but didn’t not find anything
5.   Checked the services console, did some try & error funda but that did the trick. Later I did some research on my “trial and error method” and understood the complete process via Microsoft articles (reference article –bottom of this page)

Resolution:
1.   Go to your SharePoint Server
2.   Start
3.   Run
4.   Type – services.msc
5.   It will open the services console
6.   Search for this service - SharePoint Search Host Controller
7.   Restart it.

It fixed the issue and I was able to create new items as well as edit the existing items too.

Happy SharePoint once again!

Few suggestions if the above solution doesn’t work:-
1)   IISRESET on SharePoint Servers
2)   Restart all the SharePoint Servers
3)   Enable anonymous authentication for the website in IIS.



Product applies to:
a)   SharePoint 2013
b)   SharePoint Foundation 2013

ShareThis

snow flakes

blogger widgets Blogspot Tutorial

LinkWithin

Related Posts Plugin for WordPress, Blogger...