Anil Avula's Microsoft Technical SharePoint Blog

Wednesday, April 2, 2014

The form cannot be submitted because it contains validation error

When I am working on InfoPath forms that is downloaded from Google. Uploaded in My test site and tried to open the Form. It welcomes with error” The form cannot be submitted because it contains validation error. Errors are marked with either a red asterisk (required filed) or a red, dashed border (invalid values)”

Solution:

1. Ensure that the InfoPath feature enabled in list

2. Open the list in InfoPath via list tab > customize form

3. It will open up newform.aspx in InfoPath

4. Once it is open check mandatory fields available in that form.

5. Make sure all mandatory fields are available and deployed in newform.aspx

6. If you don’t want them to be displayed in newform.aspx just remove mandatory option

7. Republish the form and check behavior

If the above does not resolves the issue then it was a hidden field with an invalid value which caused the problem

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

Monday, March 31, 2014

BLOB cache for Sharepoint

Blob cache is used in Sharepoint that to cache the Larger files.In the below Article I explained in very details About the Caches

http://expertsharepoint.blogspot.de/2013/10/to-tune-sharepoint-2010-for-better.html

BLOB Cache/Disk-based caching controls caching for binary large objects (BLOBs) such as image, sound, video, and some static content files like CSS. Disk-based caching is fast. It eliminates the need for database round trips. BLOBs are retrieved from the database once and stored on the Web client. Further requests are served from the cache and trimmed based on security.

How to enable BLOB caching:

1. BLOB Cache needs to be enabled from Web.Config.

2. Make sure that there is enough space in the drive/server where blob cache is stored.

3. It’s important to understand that BLOB cache is per-machine. So make sure that the BLOB cache settings are consistent across the whole farm. You don’t want one server with 1 GB of BLOB cache and another server with 4 GB of BLOB cache. You might see strange and inconsistency in performance if you don’t configure BLOB cache consistently.

4. By default, the disk-based BLOB cache is off and must be enabled on the front-end Web server.

5. In order to enable BLOB cache, locate the Web.Config for the web application and edit it.

6. The recommended approach for making such changes in Web.Config file is through a feature receiver or PowerShell by making use of SharePoint’s SPWebConfigModification class.

In the Web.Config file, find the following line:

In this line, change the location attribute to specify a directory that has enough space to accommodate the cache size.

To add or remove file types from the list of file types to be cached, for the path attribute, modify the regular expression to include or remove the appropriate file extension. If you add file extensions, make sure to separate each file type with a pipe (|), as shown in this line of code.

To change the size of the cache, type a new number for maxSize. The size is expressed in gigabytes (GB), and 10 GB is the default. It is recommended that you not set the cache size smaller than 10 GB. When you set the cache size, make sure to specify a number large enough to provide a buffer at least 20 percent bigger than the estimated size of the content that will be stored in the cache.

To enable the BLOB cache, change the enabled attribute, from "false" to "true".

After enabling blob cache in web.config, do an IISRESET and browse to the /settings.aspx first, instead of home page (Collaboration portal site).

When we browse to the settings.aspx, it will create the following files change.bin, dump.bin and flushcount.bin (all the files will be 1KB in size).

Browse to the home page now, it will create a folder PUBLISHINGIMAGES, all the images rendered from the database will be stored here and the above bin files will also get updated (we can see the difference in file size)

You can use an STSADM command to flush all BLOB caches associated with a specified Web application on different Web front-end computers on the farm:

stsadm –o setproperty –propertyname blobcacheflushcount –propertyvalue 11 –url http://mywebapp::port

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

Thursday, March 27, 2014

User profile service and User Profile Synchronization service

This is a common question that many of SharePoint administrators think at the beginning, what is the difference between those and why they are used. Here is the answer for your question.

Explanation:

Coming to a background of user Profiles

The service application is used to import the users from other directories such as LDAP, Novell, Tivoli, Unix into SharePoint. There are many changes in user profile included in service application from Moss 2007 to SharePoint 2010 and 2013.there are two ways that we can import users. In Moss 2007 we have only option is to import users from AD to SharePoint. We cannot update the user information Vice Versa. When Coming into SharePoint 2010 and 2013,we have both the options depends on our Farm. It should be like we can only get the user from AD->SharePoint and It should be like the user update can be done from SharePoint t-> AD

FIM(Forefront identity manager)is also introduces in between AD and SharePoint in SharePoint 2010 to get the updates.

3 data bases will be created after creating the user profile service application, those are

· Profile database – used to store user profile information.

· Synchronization database – used to store configuration and staging information for synchronizing profile data from external sources such as the Active Directory Domain Services.

· Social tagging database – used to store social tags and notes created by users. Each social tag and note is associated with a profile ID.

Difference of User profile service and User Profile Synchronization service

It’s very simple to understand

· User profiles – contain detailed information about people in an organization. A user profile organizes and displays all of the properties related to each user, together with social tags, documents, and other items related to that user.

· Profile synchronization – provides a reliable way to synchronize groups and user profile information that is stored in the SharePoint Server 2013 profile database together with information that is stored in directory services across the enterprise.

User Profile Service:

This service should be used, If we just want to import the users from AD only not to update the user information in a way from SharePoint->AD. It’s a single way of communication

User Profile Synchronization service:

This service should be used, If we want to update the users information Vice versa. If the information for a user is updated in SharePoint, it should be reflected also in AD because of this service. It’s a Two way communication

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

Wednesday, March 26, 2014

SQL Reporting services Installation with SharePoint 2013

As we all know that we use Reporting services integrated with SharePoint. The Installation and configuration of reporting services with SharePoint 2010 is pretty straight forward but there are many changes in reporting services that to integrate with the SharePoint 2013. This post will walk through the steps required to set up SQL Server Reporting Services in Integrated mode with SharePoint 2013.

To start with, it’s important to understand that SSRS will install as a SharePoint service application. This obviously means that it must be installed on a machine that is part of the SharePoint farm. In a single SharePoint front end environment it is much better to add SSRS to your SharePoint server than it is to add SharePoint to your SQL server. Obviously, if you have a separate SharePoint application server, that’s the best place for it.

To install and configure the Reporting services, we need to have SQL Reporting features and the SharePoint 2013 Installation on the server.

· SQL 2012

· SharePoint 2013

How to Install the SQL reporting service Feature:

Follow the below article on how to install the shared feature for SQL

http://expertsharepoint.blogspot.de/2014/03/how-to-add-shared-feature-in-sql-2012.html

Check the Boxes as per the screen shot below to get the Reporting services feature.

How to Install the SharePoint 2013:

Follow the below article on how to install the SharePoint.

http://expertsharepoint.blogspot.de/2013/11/detailed-sharepoint2013-installation-i.html

After the Installation of SQL Feature and SharePoint:

Here, we need to consider two things to get the Reporting services feature

1. Install SharePoint First and then the Reporting services feature, Then You can see the Reporting Service Application Under Application management->service Applications

2. Another thing that you should note is that the order of operations is important here. If you install Reporting Services prior to SharePoint installation in the SharePoint on the farm, the option to create a Reporting Services application will not appear under the service application in SharePoint. That’s because it won’t be registered with the farm as a service application. If this happens, you can run the following Power Shell to register the Service Application

Go to SharePoint Management shell and run the below power shell commands.

Install-SPRSService

Install-SPRSServiceProxy

The next thing you need to do is to provision the service application from central administration.

Go to central administration->application management->Manage Service applications->Click on New on Ribbon

You can see the SQL server Reporting services Application, Click on the Service and fill out the details And select OK. Ensure that you navigate to the bottom of the form and select the applications to activate SSRS on

Once the service application and proxy have been created, click on it to access the management screen.

You’ll want to access each of the sections and fill out the appropriate options for your installation. you should back up your encryption key in the key management section, Set your unattended execution account, and your email server settings if you want to be able to deliver reports via email. If you want to enable self service subscriptions and alerts, fill out that section, and it contains instructions for setting up the SQL agent service to support it.

The most important section is System Settings, which controls the bulk of how Reporting Services will run. Clicking on it accessed the service itself,

If you can access your system settings, then you should be good to go. The next step is to enable SSRS in your site collections. To do this, Go to Every site>site settings->Check the Report services Option and enable settings.

That’s It. Your good to access the Reports now.

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

Monday, March 24, 2014

Installation of SQL server 2012

I am providing the step-by-step instructions in this article on how to install SQL server 2012 with a Single Instance on a windows server 2012.

· Run setup.exe

· Click on Installation

· Click on New SQL server stand alone or add feature to an existing installation

· Rule check in progress will start, Click OK once done

· Enter the product key, click Next

· Accept the License agreement, click next

· Install setup files will start

· Setup support rules will start, click next

· Select SQL server feature installation, Click next

· Select the Instance Features as you required, Change the directory of the Features if required,Select the Management tools on botom to open the SQL in management studio. click next