We are pleased to present below all posts tagged with 'error'. If you still can't find what you are looking for, try using the search box.
One of my clients running SharePoint 2013 on-premises contacted me with a strange issue. They had some SharePoint 2013 platform workflows that were getting suspended and wasn’t sure why. We got past that initial issue, but what I wanted to talk about today is what we did with all the active workflows that were suspended. Learn how I use PowerShell to make all those workflows resume instead of resorting to canceling them...
I had this come up with a client recently and wanted to be sure to share the easy resolution given the vague information out there on this topic. This just reminds me how important it is to not just blindly troubleshoot the symptom, but investigate fully before continuing in your attempts at resolution.
If you are like my unfortunate client, your installation of Office Web Apps (or WAC) was humming along just fine until that one day comes that you wish you never got out of bed. This turned out to be a simple fix but took some hair-pulling to get there so let me share my journey.
I recently had an interesting issue with a client’s SharePoint environment that I wanted to hopefully help someone else out as it wasn’t the most intuitive cause. What do you do when you try to save list items or InfoPath-customized list items and it fails? It turned out to be really simple if you know what to look for.
Getting the dreaded "Currency Field Missing" on a rollup field? Read on for info on solving this frustrating Dynamics 365 configuration problem.
You know how the story goes... We were prepping for a CRM 2013 on premise client going live and it was Outlook client configuration time. I was doing some last minute Outlook client testing and hit the sync button to test my Outlook filters when I got this message. Read more to find out how to activate data encryption when syncing Outlook to CRM.
This blog details my chat with Microsoft, how we discovered the problem child, and the fix for the error!
I was recently doing some routine maintenance on a SharePoint server and I happened to check the event viewer logs. Wow was I surprised! It seemed that every minute, we were getting this error message, event ID 6481:
Application Server job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (GUID).
On a recent client project, we implemented a solution that heavily used article pages / page layouts from the SharePoint 2010 Pages library. Most of them had images. While working through use cases with these articles, I came across some strange behavior that someone else had found but not documented (to my knowledge). As a result, I wanted to blog about the topic to make it easier for others to find.
I had a client call me the other day as he was having an issue with a couple of his SharePoint 2010 sites that seemed strange, the sites just stopped working. When anyone tried to access the sites, they would get HTTP 500 errors. I was able to resolve this issue for the client so I thought I should share some of my troubleshooting tips.
A database attach upgrade is the only supported method for upgrading SharePoint 2010 Products to SharePoint 2013 (unless you use a third-party migration tool). Database attach is used to upgrade SharePoint content and service applications. I was doing some testing with doing database attach upgrades from SharePoint 2010 to SharePoint 2013 and found an issue.
There are numerous cool new features in SharePoint 2010, and I’ve found that integrating them into custom solutions are not always straightforward. I found this to be true with ratings as well. Ratings are one of the new social tagging features that gives users a 1–5 star graphic to rate content. You can find a high level overview of social tagging features here on TechNet.
Normally this isn’t a problem. For example, you have your normal Shared Documents library, and you want users to be able to rate content. No problem right? We go into the library settings, and then click on Rating Settings. We simple click Yes, and hit ok. Too easy:
Have you run into a problem with the Outlook client and someone suggested, “Hey, turn on tracing and let me know what you find”?
Gee, thanks. That’s helpful, right?
Here’s what you need to know about tracing for the Outlook client:
What is tracing?
Tracing is a way to gather a list of the information passed back and forth between a program and a computer. For the CRM Outlook client, tracing will show a chronological, readable play-by-play of what the add-in is trying to do, inc ...
I went to go run a manual sync of the User Profile Service in SharePoint, and was unable to get to the Service Application. After reviewing the ULS logs, I found this error:
UserProfileConfigManager.StartSynchronizationForOneManagementAgent: Unexpected exception: System.ServiceModel.EndpointNotFoundException: Could not connect to http:///ResourceManagementService/MEX. TCP error code 10061: No connection could be made because the target machine actively refused it IP address:port. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it IP address:port.
Luckily this error has an easy fix. This error occurred because one of the two ForeFront Identity Manager services that the User Profile Service depends on wasn’t started. Go into Services.msc and check to ensure both services are started:
You should be able to start the service without an issue and this should allow you to connect to the User Profile Service again.
I had setup a test environment to test out and play with the new hosting functionality of SharePoint, also called multi-tenancy. When you create your main web application that will be used to house the tenants, you have the option to have it use Claims Based or Classic Mode authentication.
While configuring a SharePoint farm for a client the other day, I came across a simple but problematic error with search. We had requested a full SSL certificate for the farm, but I was a self-signed certificate so I could work with the site. After configuring search content sources and I kicked off a full crawl, I got this error in the crawl log:
“The secure socks layer (SSL) certificate sent by the server was invalid and this item will not be crawled.”
Wells that’s a bummer. Luckily there’s an easy fix. What you need to do is configure search to “Ignore SSL certificate name warnings” via Central Administration. TechNet has the documented steps. After making this change and running a full crawl, voilà!
Success! Of course you should get an official SSL certificate, but sometimes you get by with what you have.
Recently while working on a client engagement, we needed to move users around to different business units in Dynamics CRM 4.0. No problem right? Well we very quickly determined things weren’t going to go smoothly. When we attempted to change a user’s business unit, it would sit for 30 seconds and throw the lovely unhelpful generic message “An error has occurred”. Gotta love Microsoft developer’s strong attention to error messages. A lot of users have apparently run into this with no real good resolution. We were able to find the true cause (at least in our case), so I wanted to share it to hopefully help others struggling with this.
A client of ours recently reported that they could no longer create custom attributes to an entity in Microsoft Dynamics CRM 4.0. They received a generic "An error has occured" error message when the CRM administrator tried to do this.
After some investigation, we disocvered that they had changed the name of their network's local domain to reflect a change in their company's name. Their network folks went through all the proper processes to implement the change in the Active Directory domain name - except when it came to CRM.
I recently came across this and wanted to be sure everyone is aware of this limitation. With the new release of Office 2010 including 64-bit support, there has been some confusion about which version to install. Microsoft has been clear in their recommendation:
For whatever reason, say you installed Office 2010 64-bit on your machine, and you happily go to your shiny SharePoint 2010 site (or WSS/MOSS), open up a list, and hit Datasheet View. To your surprise, you see this:
When I was configuring a new installation of SharePoint Server 2010 the other day, I hit a snag when creating a Managed Service Account while creating a new Web Application. My existing Application Pool account wasn’t listed and I couldn’t choose the “Configurable” option to manually type it in. I attempted to make the existing application pool AD account a managed account, but got the error:
“The given key was not in the dictionary”
To correct this error, you need to go into Active Directory and make a security change:
During a recent migration, we ran into an issue when attempting to migrate users from one domain to another using stsadm migrateuser. Hopefully this will help any others that are getting this strange error. Our environment was a small MOSS 2007 64-bit farm installed with slipstreamed SP2, with the February 2010 cumulative update applied.
We were moving from an on-premise to Hosted solution, so this required a new domain and user accounts. Since the new domain wouldn’t know anything about the old domain’s user accounts, we added the –ignoresidhistory switch. We ran the following command:
The complementary paper includes over 12 years of research, recent survey results, and CRM turnaround success stories.
This 60-second assessment is designed to evaluate your organization's collaboration readiness.
Learn how you rank compared to organizations typically in years 1 to 5 of implementation - and which areas to focus on to improve.
This is a sandbox solution which can be activated per site collection to allow you to easily collect feedback from users into a custom Feedback list.
Whether you are upgrading to SharePoint Online, 2010, 2013 or the latest 2016, this checklist contains everything you need to know for a successful transition.