As I continue to go into more configuration around 2013 it is bringing back the memories of all the strange things that were encountered when deploying 2010 farms not long after it released. Fortunately 2013 has been out for a little while now and there are a lot of good folk's out there that started digging in early and have posted a lot of really good information on the issues they have run across during their configurations.
This is another one of the many issues that I have run across and was fortunate to find someone else out there that posted a good article on the issue and the resolution.
This error was due to the service account that is used to run the UPA service application not having permissions on the UPA it self. After adding the service account that the UPA application pool runs under to the UPA the My Sites news feed's begain showing up correctly.
Thanks to Andy Dawson for posting his detailed article on the issue with the details of the fix. He also provides a handy powershell script so you can automate this more in your farm configurations.
Article for doing it via Central Admin
http://blogs.blackmarble.co.uk/blogs/adawson/post/2012/10/30/SharePoint-2013-MySite-Newsfeed-displays-There-was-a-problem-retrieving-the-latest-activity-Please-try-again-later.aspx#id_0034c967-d124-45ac-a539-1e710d5f2391
Article on powershell script
http://blogs.blackmarble.co.uk/blogs/adawson/post/2012/11/23/Setting-SharePoint-2013-User-Profile-Service-Application-Permissions-Using-PowerShell.aspx
SharePoint 2010/2013 Tech Notes
Monday, June 24, 2013
SharePoint 2013 My Site tasks not updating and show old updated date - Last updated at 1/1/1901 12:00AM
While working through some SharePoint 2013 configuration for an upcoming demo I ran across an issue where when you go to your my site and click on the tasks link you will get the error below
Sorry, we are having trouble refreshing your tasks
or
Last updated at 1/1/1901 12:00AM
After doing some research I ran across the following article that described the issue and provided a fix. It seems that the UPA security setup in 2013 has changed from 2010 as adding additional accounts to the UPA was not required.
For me the issue ended up being that the account I used for the work management service application had not been added to the UPA. After doing this and running an incremental crawl the tasks were showing up from other site collections for the user.
Thanks to Hong Gyem for publishing the information on the issue and the fix
http://honggyem.blogspot.com/2013/05/my-tasks-not-updating-seen-following.html
Sorry, we are having trouble refreshing your tasks
or
Last updated at 1/1/1901 12:00AM
After doing some research I ran across the following article that described the issue and provided a fix. It seems that the UPA security setup in 2013 has changed from 2010 as adding additional accounts to the UPA was not required.
For me the issue ended up being that the account I used for the work management service application had not been added to the UPA. After doing this and running an incremental crawl the tasks were showing up from other site collections for the user.
Thanks to Hong Gyem for publishing the information on the issue and the fix
http://honggyem.blogspot.com/2013/05/my-tasks-not-updating-seen-following.html
Tuesday, May 14, 2013
SharePoint 2013 - Central Admin site prompts for authentication over and over and fails to load from remote server
Noticed something on a recent 2013 farm build where Central Administration site opened correctly from the server it was running on, but when you tried to open it from another server in the farm or a workstation you were prompted for authentication three times and it never succeeded.
This seemed like a behavior I have seen in the past when working with Kerberos based web applications that did not have the SPN's configured correctly. I checked the authentication provider on Central Admin and found it was set to Kerberos instead of NTLM. Since the client is not utilizing Kerberos I changed to NTLM, saved changes, and after this could access CA from other servers in the farm.
I looked again at my script and realized that I had not set the authentication provider switch correctly so this is why it had been set to Kerberos
This seemed like a behavior I have seen in the past when working with Kerberos based web applications that did not have the SPN's configured correctly. I checked the authentication provider on Central Admin and found it was set to Kerberos instead of NTLM. Since the client is not utilizing Kerberos I changed to NTLM, saved changes, and after this could access CA from other servers in the farm.
I looked again at my script and realized that I had not set the authentication provider switch correctly so this is why it had been set to Kerberos
Monday, May 13, 2013
Microsoft SQL Server 2012, 2008R2, 2008, 2005, 2000 and 7.0 Builds
Ran across this site and it has all the needed SP build numbers for multiple versions of the product. Also has some other helpful links on how to get build numbers, etc.
Microsoft SQL Server 2012, 2008R2, 2008, 2005, 2000 and 7.0 Builds
http://sqlserverbuilds.blogspot.com/
Microsoft SQL Server 2012, 2008R2, 2008, 2005, 2000 and 7.0 Builds
http://sqlserverbuilds.blogspot.com/
March and April CU for 2013
It seems that the CU's for 2013 are coming quicker than they did for 2010. The March CU was launched and now has to be installed in order to apply any future updates.
April 2013 CU also released and looking through the details for SP Server it appears that most of the issues are around sites and service applications that were migrated from 2010.
March CU
http://blogs.technet.com/b/stefan_gossner/archive/2013/03/21/march-public-update-for-sharepoint-2013-available-and-mandatory.aspx
April CU
http://blogs.technet.com/b/stefan_gossner/archive/2013/04/27/april-2013-cu-for-sharepoint-2013-has-been-released.aspx
Hopefully we don't see the same issues that we did with 2010 where CU's are released, pulled, and then released again.
April 2013 CU also released and looking through the details for SP Server it appears that most of the issues are around sites and service applications that were migrated from 2010.
March CU
http://blogs.technet.com/b/stefan_gossner/archive/2013/03/21/march-public-update-for-sharepoint-2013-available-and-mandatory.aspx
April CU
http://blogs.technet.com/b/stefan_gossner/archive/2013/04/27/april-2013-cu-for-sharepoint-2013-has-been-released.aspx
Hopefully we don't see the same issues that we did with 2010 where CU's are released, pulled, and then released again.
Saturday, September 15, 2012
Passed 70-668 for MCITP
I finally sat the 70-668 SharePoint 2010 Administration test this past Thursday. I have been working with 2010 for a couple years now, but was still nervous about sitting the test as I am just not a good test guy. I was very pleased when It was all over and I passed with an acceptable score.
Now its time to start working toward the first dev test.
Now its time to start working toward the first dev test.
My Install of SharePoint 2013 on Windows Server 2012 VM
I decided to dive into Windows Server 2012 and SharePoint 2013 this weekend as I had downloaded the software ofr each a while back and wanted to get started. I am using Vmware workstation 8 for this.
Windows Server 2012 Installation
I created a new VM, selected Windows 7 x64 in Vmware, set the ISO to my OS ISO and powered up the VM.
I ran into an issue almost immediately when booting up from the iso.The error was
Windows Cannot Read The ProductKey Setting From The Unattend answer file
When you click OK, the VM would just reboot.
I did a bit of googling and found the solution here
The fix was easy, just uncheck the power on, or turn off the floppy settings in the VM. I chose to just turn off the floppy drive. After this the installation routing ran as I would have expected.
The installation time was quick, seems like it only took 30 or 40 min to complete the installation.
I had not gone through any 2012 docs prior to this install, so when I logged on for the first time and loaded up the GUI it was a bit of a surprise. No start menu, icons, or anything else that looked familiar. I poked around server manager a bit and back to google I went.
I found that in order to get to some desktop type icons that another feature had to be installed "Windows Desktop Experience", so I installed this feature and after reboot had some tiles on the screen for things like control panel, IE, etc. I then found an article here that goes over the various keyboard shortcuts for Windows 8 and they seem to work in 2012 as well.
So at this point I had at least a base install up to begin digging into and to try and install SharePoint 2013 on.
Share Point 2013 Installation
I started with the prerequisiteinstaller package and everything installed and correctly, after a couple reboots it was all wrapped up.
I performed a standalone installation as all I want to do at this point is go through the installer and have a look at some of the interface and feature differences.
The installation of the binaries went fine, but it did error out when it kicked off psconfig with the error below
ErrorCode:SubStatus:
Service running under Network Service account in workgroup environment is not supported.
Back to google and found the solution to the issue here, I only had to change the app fabric service account and did not encounter the TCP port in use error. I then ran
and this completed with no errors.
When I then proceeded to run psconfig from the GUI as the article mentions, it kicks off, but then fails at the end with an error on installing "sample data". I looked this up and found that this does not stop the completion of the configuration, so for now i just ignored it.
I launched Central Admin and the new CA interface loaded up. Yet again the look and feel have changed further and I see some new options that are not in 2010.
Even with the few errors encountered I had my new VM built in under 2 a couple hours and up and running.
Windows Server 2012 Installation
I created a new VM, selected Windows 7 x64 in Vmware, set the ISO to my OS ISO and powered up the VM.
I ran into an issue almost immediately when booting up from the iso.The error was
Windows Cannot Read The ProductKey Setting From The Unattend answer file
When you click OK, the VM would just reboot.
I did a bit of googling and found the solution here
The fix was easy, just uncheck the power on, or turn off the floppy settings in the VM. I chose to just turn off the floppy drive. After this the installation routing ran as I would have expected.
The installation time was quick, seems like it only took 30 or 40 min to complete the installation.
I had not gone through any 2012 docs prior to this install, so when I logged on for the first time and loaded up the GUI it was a bit of a surprise. No start menu, icons, or anything else that looked familiar. I poked around server manager a bit and back to google I went.
I found that in order to get to some desktop type icons that another feature had to be installed "Windows Desktop Experience", so I installed this feature and after reboot had some tiles on the screen for things like control panel, IE, etc. I then found an article here that goes over the various keyboard shortcuts for Windows 8 and they seem to work in 2012 as well.
So at this point I had at least a base install up to begin digging into and to try and install SharePoint 2013 on.
Share Point 2013 Installation
I started with the prerequisiteinstaller package and everything installed and correctly, after a couple reboots it was all wrapped up.
I performed a standalone installation as all I want to do at this point is go through the installer and have a look at some of the interface and feature differences.
The installation of the binaries went fine, but it did error out when it kicked off psconfig with the error below
ErrorCode:SubStatus:
Service running under Network Service account in workgroup environment is not supported.
Back to google and found the solution to the issue here, I only had to change the app fabric service account and did not encounter the TCP port in use error. I then ran
PS C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\BIN>
.\PSCONFIG.EXE -cmd Configdb create SkipRegisterAsDistributedCacheHostand this completed with no errors.
When I then proceeded to run psconfig from the GUI as the article mentions, it kicks off, but then fails at the end with an error on installing "sample data". I looked this up and found that this does not stop the completion of the configuration, so for now i just ignored it.
I launched Central Admin and the new CA interface loaded up. Yet again the look and feel have changed further and I see some new options that are not in 2010.
Even with the few errors encountered I had my new VM built in under 2 a couple hours and up and running.
Subscribe to:
Posts (Atom)