A Blog about SharePoint knowledge. Here you can find most information related to SharePoint Administration, SharePoint Development, My experience with SharePoint client, Information on SharePoint server and End user computing, SharePoint Study Materials etc. HAPPY Reading...!
After talking with a job seeker the other day, I asked for his card so I could keep in touch with him. He replied that his company didn't give its employees business cards. He didn't have a personal business card either.
I was asking for his card because I had spoken with him a couple of months before, and he took my card and said he would contact me so I could pass job leads to him. But I didn't hear from him, and I had no way to initiate contact with him, so he missed a couple of good leads.
I realized that not everyone has been taught the value of a business card - their own personal business card - to their career.
A user tries to open an InfoPath form in the application instead of the browser, and get an error message:
The user can open in the browser just fine, and has been able to open the forms previously with no problem. User is able to download the form to their desktop and open the form in InfoPath. But when they try to open the form in the application from the context menu, the above error is shown.
In researching the error, I found a support posting that provided a clue to the problem. In it, the user is instructed to enable Add Ons in their Internet Explorer:
Go to Tools in IE, click Internet Options
Click Programs at the top
Click “Manage add-ons” near the bottom
Click Publisher, then you can see all of Microsoft Corporation together
Scroll to SharePoint names (May be one or several)
Make sure they are all enabled by clicking on the name; the Enable button is towards the bottom.
Your user will be raising a ticket for to create a replica of the production site in development environment.
Quite easy - correct? You can easily implement this by using PowerShell but now the problem starts from here. If your site collection admin has created a term store in production site then you will not get those in development environment. Hmm- seems to be difficult now, isn’t it?
Reason: Managed metadata terms and term sets each have a unique guid and the guids don't match up
Nothing to worry about as we have a solution for that :)
Let me brief some details as local terms can be created by 2 ways:
-centrally i.e. @Central Administration Level
-Locally i.e. @site collection level
Let me talk about ‘Centrally’ first: There are some ways by which you can implement this.
-By using Export and Import
-By using Database method
Let’s discuss about the first method i.e. Export and Import
Problem Description:Error in creating a SharePoint
Wiki site in SharePoint 2010
a subsite underneath site collection by using ‘enterprisewiki’ throws an
refer the following exceptions which is a series of error messages and helpful
to understand the cause behind it.
Failed to activate site-scoped features for template 'ENTERWIKI#0' in site ‘http://sharepoint2007/sites/SP2010Projects’.
Failed to activate web features when provisioning site at url " http://sharepoint2007/sites/SP2010Projects"
with site definition "ENTERWIKI#0"
Failed to apply template "ENTERWIKI#0" to web at URL " http://sharepoint2007/sites/SP2010Projects".
SPContentTypeBindingElement.ElementActivated(). ContentType '0x010100C568DB52D9D0A14D9B2FDCC96666E9F2007948130EC3DB064584E219954237AF39004C1F8B46085B4D22B1CDC3DE08CFFB9C'
not found on web ' http://sharepoint2007/sites/SP2010Projects'.
specified argument was out of the range of valid values. Parameter name:content
type not found(‘0x010100C568DB52D9D0A14D9B2FDCC96666E9F2007948130EC3DB064584E219954237AF39004C1F8B46085B4D22B1CDC3DE08CFFB9C’).
template is a dependency section of Publishing Infrastructure as per the
We will be
hosting lunch at the Microsoft Office in Alpharetta on April 30 to take a deep
dive into the things you really want to know about using Nintex to enhance your
SharePoint deployment. You'll hear from our top consultants and a key customer
or two. One attendee
will go home with a free Windows Surface!
With the launch of SharePoint 2013 came some exciting new
features and improvements in the realm of Web Content Management (WCM). Content
authoring improvements like Image Renditions and the ability to drag and drop
navigation items directly onto a page create a better experience for content
authors, while branding advancements like the new Design Manager and Device
Channels further empower web designers. Throw in Managed Navigation, Cross-site
Publishing, Catalog-enabled lists and libraries, Category pages, clean URLs and
the ability to capture a video thumbnail straight from the video and it is
clear that WCM has received quite the facelift courtesy of SharePoint 2013.
Today’s modern company is comprised of multiple offices,
telecommuters, business travelers and clients on various continents in
different time zones. In this global economy, business applications are
required to meet the needs of each employee and customer whether they are in
Atlanta or Hong Kong. No one wants to be sitting in an important meeting
not being able to access and interact with the data and processes they need.
For this month’s Tip of the Month, we’re examining the benefits of utilizing
the powerful cloud features of Nintex Live with Nintex Workflow and Nintex
One of the best improvements in SharePoint from version to
version has been with Search. Search Server Express was added for SharePoint
WSS 2007. Fast Search was introduced in SharePoint Server 2010 among other
great feature improvements around the search service. In SharePoint Server
2013, Fast Search technology is now included in the standard search service and
a new feature known as continuous search has been added. SharePoint's Search
service is far superior to list views to locating documents and item information
in SharePoint. There are so many features of search that can be easily utilized
or extended upon so much so that each deserves its own article. One feature
that this article will focus on is searching SharePoint content from your
computer using Windows Explorer and how to extend its capabilities.
We have created a new UAT environment for the deployment purposes and everything is new. Suddenly the requirement comes up for managed metadata. As this environment is newly built so we have not created all the service applications and work/create as per the requirement arises.
Creation of new service application named as ‘managed metadata’
I have created a new service application by providing the following data:
-name of the service application Example. Managedmetedata_DEVSP
-name of the application pool
-selecting the appropriate service account from the dropdown which has sufficient privileges to create the SA.
Now the service application is created without any issues.
As soon as I clicked on it then I got the following ERROR MESSAGE:
The Managed Metadata Service or Connection is currently not available. The Application Pool or Managed Metadata Web Service may not have been started. Please Contact your Administrator.
Make sure the managed metadata service is already started.
How to check this:
-manage services on server
-managed metadata service
Once the service is in started mode then check the results again by clicking on the managed metadata service application, it has to open the page without any errors\exceptions.
If you face the same error message as mentioned above then please execute IISRESET once and that’s it.
If you have any queries/questions regarding the above mentioned information then please let me know, Thank you.
Requirement comes up to transfer the backup of one site collection from production to development environment.
-Took the backup of the site collection by using PowerShell command without any issues
-As soon as I tried restoring the backup then I faced the following error message
Your backup is from a different version of Microsoft SharePoint Foundation and cannot be restored to a server running the current version. The backup file should be restored to a server with version '220.127.116.1134' or later.
-Compare the development SP version with the production version and found out the following info:
-it’s quite obvious from the above versions that it’s not going to work L and we should be ready to hear the answer “It seems that you need to update your development server with the same patch which is running in production and then you can restore the backup” / upgrade your destination farm to the same version of the source farm, After your farms are at the same product version, the restore will succeed.
You must be wondering as How exactly I have achieved this resolution?
Here are the details:
-Restored Production backup to staging application but in a separate database
-Took that database and restored to development environment – which automatically place that DB to the same version
-Attached the database to default application, that’s it- issue resolved J
Site is up and running, easily restored to the development environment without any waiting time.
If you have any queries/questions regarding the above mentioned information then please let me know, thank you.
The SharePoint Health Analyzer
detected an error. One or more services have started or stopped unexpectedly.
The following services are managed
by SharePoint, but their running state does not match what SharePoint expects:
SPAdminV4. This can happen if a service crashes or if an administrator starts
or stops a service using a non-SharePoint interface. If SharePoint-managed
services do not match their expected running state, SharePoint will be unable
to correctly distribute work to the service.
SharePoint was unable to automatically repair
To stop or start a service managed by
SharePoint, use the SharePoint service management interface in the SharePoint
Central Administration Site. If a service has crashed, restart the service
manually on the affected servers by running "net start [service
name]" from a command prompt. For more information about this rule, see
- All services are running fine.
- All SharePoint sites as well as web
applications are running without any issues.
Basically it’s a clear cut indication that the
one of the required service is un-reachable.
Resolutions you can try as there are multiple things by which we
can resolve this issue:
- Check the administration service is running
or not in services console. if its stopped/disable then please restart it.
- try to reboot the server and check the
- try restarting the services by using command
- after the above things and if you are still
facing the problem then please check the SP logs and surely you will find
theexact error which will tell you the
root cause behind it.
If you have any issues/queries
regarding the above mentioned information then please let me know, Thank you
type hub in SharePoint 2010 step by step
Content Type Hub is like a repository where we can store the
content types in a site collection and can be shared among all site collections
in a web application and multiple web applications in a farm.
It is one of the features available in Managed Metadata
service in SharePoint 2010
Create a site collection name it as content type hub