webtamer https://docs.microsoft.com/archive/blogs/webtamer/feed.xml Tue, 16 Apr 2019 05:34:40 GMT en-US hourly 1 Demand for Surface and Windows 8 https://docs.microsoft.com/archive/blogs/webtamer/demand-for-surface-and-windows-8 Tue, 30 Oct 2012 18:28:00 GMT https://blogs.msdn.microsoft.com/webtamer/2012/10/30/demand-for-surface-and-windows-8/ Despite hurricane Sandy there was alot of interest and demand for Surface and Windows 8, here are a couple of pictures I took when I went to pick up my first Surface! :)
 

]]> Bill Gates shares his excitement for Windows 8 and Surface!! https://docs.microsoft.com/archive/blogs/webtamer/bill-gates-shares-his-excitement-for-windows-8-and-surface Tue, 23 Oct 2012 05:53:13 GMT https://blogs.msdn.microsoft.com/webtamer/2012/10/23/bill-gates-shares-his-excitement-for-windows-8-and-surface/ I have been around Microsoft software since Windows 3.51 as a hobbyist and Windows NT 4.0 as an IT professional, where I have grown to love to hear Bill Gates speak about each new version of windows. this time was no different: 
I almost jumped out of my seat when I got to watch the visionary of modern home and office computing Bill Gates share his excitement for Windows 8 and Surface at the Microsoft Blog on TechNet! With all the excitement in the world, here is the link to the original post and video!

https://blogs.technet.com/b/next/archive/2012/10/22/exclusive-video-bill-gates-on-windows-8-windows-phone-8-and-surface.aspx

]]> My new video blogs for MSPFE: https://docs.microsoft.com/archive/blogs/webtamer/my-new-video-blogs-for-mspfe Wed, 17 Oct 2012 06:58:00 GMT https://blogs.msdn.microsoft.com/webtamer/2012/10/17/my-new-video-blogs-for-mspfe/ Recently I was in Redmond attending a developer training and while there I thought it would be great to create a video blog to talk about some of the great work and services my colleagues are working on to induce the best return on ivesments in SharePoint.
the following are the first two blogs of many more to come!

Enjoy!!:

SharePoint Custom Code Review Service (MSPFE Video Blog)
https://blogs.msdn.com/b/mspfe/archive/2012/10/15/sharepoint-custom-code-review-service-mspfe-video-blog.aspx

SharePoint 2013 Developer Ignite Training (MSPFE Video Blog)
https://blogs.msdn.com/b/mspfe/archive/2012/10/09/sharepoint-2013-developer-ignite-training-mspfe-video-blog.aspx

]]> SharePoint 2010 User Profile Sync Job has been running for a week with no end in sight? https://docs.microsoft.com/archive/blogs/webtamer/sharepoint-2010-user-profile-sync-job-has-been-running-for-a-week-with-no-end-in-sight Tue, 11 Sep 2012 19:00:00 GMT https://blogs.msdn.microsoft.com/webtamer/2012/09/11/sharepoint-2010-user-profile-sync-job-has-been-running-for-a-week-with-no-end-in-sight/ Problem:

As I was working with one of my customers this week we encountered a seemingly strange issue! Their user profile synchronization has been running for over a week to no end in sight. So I covered the basics to ensure the User Profile Synchronization Service and Service application are configured properly and according to the configuration guide titled Configure profile synchronization (SharePoint Server 2010) and it was.!?!?! But still the Synch job in question was still running; no errors in the logs both System and ULS.

 At this point I thought to myself it could be a performance issue so I went down the path of Performance Monitor and SQL Profiler still no solution in sight; so I decided to comb the Application Logs for anything small and big that maybe related and bingo there I see the following events:

Source: MsiInstaller
Event ID: 1004
Level: Warning
Keywords: Classic
User: NETWORK SERVICE
Description:
Detection of product '{90140000-104C-0000-1000-1000000FF1CE}', feature 'PeopleILM', component '{1C12B6E6-898C-4D58-9774-AAAFBDFE273C}' failed. The resource %programfiles%\Microsoft Office Servers\14.0\SQL\DatabaseSettings.SQL' does not exist.

Source: MsiInstaller
Event ID: 1001
Level: Warning
Keywords: Classic
User: NETWORK SERVICE

Detection of product '{90140000-104C-0000-1000-1000000FF1CE}', feature 'PeopleILM' failed during request for component '{1681AE41-ADA8-4B70-BC11-98A5A4EDD046}'

Source: MsiInstaller
Event ID: 1015
Level: Warning
Keywords: Classic
User: NETWORK SERVICE

Failed to connect to server. Error: 0x80070005

 

At this point I decided to chase the databasesettings.sql file only to successfully locate it within the same path indicated in event ID 1004, hmmmm now I am thinking I am running into an undocumented issue.

Not so fast; doing a little research I found the following

 Cause:

The Network Service account does not have rights to the %programfiles%\Microsoft Office Servers\14.0 folder.

 Problem Resolution: 

1)       Grant the Network Service account read access to the %programfiles%\Microsoft Office Servers\14.0 folder

2)       Start a full User Profile Synchronization and voila :)

3)      Almost 5 hours later job is done successfully!!

4)       For More details review the full KB article https://support.microsoft.com/kb/2473430/de

]]> SharePoint 2010 Management Shell Issue "the local farm is not accessible cmdlets with feature dependency are not registered" https://docs.microsoft.com/archive/blogs/webtamer/sharepoint-2010-management-shell-issue-the-local-farm-is-not-accessible-cmdlets-with-feature-dependency-are-not-registered Wed, 05 Sep 2012 08:46:00 GMT https://blogs.msdn.microsoft.com/webtamer/2012/09/05/sharepoint-2010-management-shell-issue-the-local-farm-is-not-accessible-cmdlets-with-feature-dependency-are-not-registered/ Issue:

 When you launch a SharePoint 2010 Management Shell you receive one or both of the following errors:

 “microsoft sharepoint is not supported with version 4.0.30319 of the microsoft .net runtime”

“the local farm is not accessible cmdlets with feature dependency are not registered”

 Diagnostics:

 At the command prompt run the following commands:

PS C:\ > $ver=$host | select version

PS C:\ > $ver.Version

 

Major  Minor  Build  Revision

-----  -----  -----  --------

3     0      -1     -1

 If the version indicated is not “2” this causes the shell console to execute in the context of the unsupported runtime as indicated in the error above.

 Workaround:

 First try to import system modules and as indicated in the following screen capture:

  
 
 
 
 
If the above step does not resolve the issue; navigate to the PowerShell shortcut properties then add the “-version 2” operator to the string in the Target Field:

 

Example:

  • C:\Windows\System32\WindowsPowerShell\v1.0\PowerShell.exe –version 2 -NoExit   " & ' C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\POWERSHELL\Registration\\sharepoint.ps1 ' "

 

Many Thanks and Kudos to Mr. Darrin Dyson of Venable LLP. for his collaborative efforts on this post.

 

 

]]> The Brilliance of SharePoint 2013's new Work Management service application!! https://docs.microsoft.com/archive/blogs/webtamer/the-brilliance-of-sharepoint-2013s-new-work-management-service-application Wed, 22 Aug 2012 10:09:00 GMT https://blogs.msdn.microsoft.com/webtamer/2012/08/22/the-brilliance-of-sharepoint-2013s-new-work-management-service-application/ Have you ever walked into your office in the morning and wondered if you were forgetting a task or a project? 

Fret no more my friend SharePoint is on the way with a fantastic new feature and service application which would help aggregate your tasks into the state of union :) with the new Work Management Service Application (WMSA for short)

The Work Management Service Application provides functionality to aggregate tasks to a central location.
    - Users get the possibility to view and track their to-dos and tasks.
    - Tasks can be cached to a users personal site.
    - tasks can be aggregated from Exchange, Project Server and SharePoint.
    - Based on 'Provider model' so that other systems can be integrated in the future.

 Learn more on this awesome new feature by watching this SP15 Ignite video:

 

 

 

]]> The Dawn of SharePoint 2013 has been announced!!!! https://docs.microsoft.com/archive/blogs/webtamer/the-dawn-of-sharepoint-2013-has-been-announced Fri, 17 Aug 2012 05:34:00 GMT https://blogs.msdn.microsoft.com/webtamer/2012/08/17/the-dawn-of-sharepoint-2013-has-been-announced/ Hello Friends, Colleagues and SharePoint fans!!! I am sure by now you are as excited as I am! about the anoucement of Office 2013 Preview :) and so here is a wealth of information and resources to satisfy your hunger for the new version of SharePoint

  MSDN & TechNet Articles

Architecture 

Upgrades

Backup and Restore

]]> SharePoint Governance plans and why are they important? https://docs.microsoft.com/archive/blogs/webtamer/sharepoint-governance-plans-and-why-are-they-important Tue, 05 Jun 2012 11:27:00 GMT https://blogs.msdn.microsoft.com/webtamer/2012/06/05/sharepoint-governance-plans-and-why-are-they-important/ Before we dive into answering this question we have to acknowledge that technology is meant to empower our work force to achieve more with ease and not necessarily an everyday struggle because we are challenged to manage underpowered resources. That said I am sure by now you have had some exposure to “SharePoint Governance Planning” and as often more than not you have faced many challenges prohibiting you from devising a governance plan that guides the growth of your SharePoint implementation hence this governance plan is incomplete of non-existent. While this scenario does not preclude us from installing and operating a SharePoint farm and web applications it could become a problem when our users start to exceed the forecasted farm hardware capacity and present the IT Team with challenges maintaining the info structure. Keep in mind technology is as good as its performing speedy functionality and so as best as can be; try to remain proactive on devising suitable governance plans in their simplest forms.

The first set of questions I ask when I am approached about creating a new SharePoint web application is;

what is the business impact if the data intended to be hosted in SharePoint is unavailable or lost?

Is there a daily operational impact and possible revenue or operational cost loss riding on this data?

Asking these two simple questions opens up a lot to learn from and many more to properly plan for. Having worked with and supported SharePoint for the last 10 years taught me the fact a SharePoint server in itself is the not the most important part of SharePoint but rather the actual user data that drives business and productivity. Putting business productivity at the center of what we do; we cannot neglect devising a sound governance plan that sets expectations and drives a best performance high availably solution. How does a governance plan help your design? At its basic premise it helps determine how much hardware investment is needed to architect a given SharePoint farm and more so it establishes a foundation for which how we will operate said server farm hence allowing us to build enough safety nets in our architecture design.

Do not know where to start? Here is a wealth of resources and information on the subject:

Governance in SharePoint Server 2010
https://technet.microsoft.com/en-us/sharepoint/ff800826

Stay SharePoint Awesome!!

]]> Fault Isolation + SharePoint = SharePoint Resilience! https://docs.microsoft.com/archive/blogs/webtamer/fault-isolation-sharepoint-sharepoint-resilience Fri, 01 Jun 2012 16:00:51 GMT https://blogs.msdn.microsoft.com/webtamer/2012/06/01/fault-isolation-sharepoint-sharepoint-resilience/ One of the common poor design decisions I have seen in the field is using a single Web Application to host everything (My Site & any other team sites etc..); to me this is like putting all your eggs in one basket; instead consider creating multiple web applications one for each of the high level functional segments of your SharePoint farm; so one to host My Sites and maybe one or more to host your actual team sites and organization content where each is provisioned with its own application pool and designated service accounts. segmenting your web applications to this extent provides a good level of fault isolation and better manageability for each; so that if a custom solution would to experience memory or CPU issues you can easily triage it by itself without having to reset the entire web server causing a wider outage than necessary. Also consider creating multiple content databases per web application to host the various site collections you might provision and in the context of each web application so that you drive a bit more resilience into your content taxonomy and design.

So here is what happens; when you create a web application in SharePoint you also create an associated content database (Example: WSS_Content) then you will need to create at least one site collection in order to be able to start browsing the web application you had created. so far so good.

Now over time your customers, team mates, etc.. will ask you to create more site collections and work spaces; as some might ask for a site with a calendar and a document library and others might ask for a performance and business intelligence sites; over time each new site collection you create by default gets stored in that original content database so in a way you end up with a possible single point of failure content database; instead why not create additional content databases and split each of these site collections across multiple databases?! doing so establishes a bit more fault isolation into your design and gives you the flexibility of more granular backup and restore abilities.

Stay SharePoint Awesome!! :)

]]> Sanitizing Customized SharePoint Pages for best performance. https://docs.microsoft.com/archive/blogs/webtamer/sanitizing-customized-sharepoint-pages-for-best-performance Wed, 30 May 2012 18:41:00 GMT https://blogs.msdn.microsoft.com/webtamer/2012/05/30/sanitizing-customized-sharepoint-pages-for-best-performance/ As we do collaborative business across teams and business groups we tend to modify SharePoint pages on the fly. While this is the nature of doing business with SharePoint; one thing we always forget is to sanitize our SharePoint pages and clearing out the dead weight. Dead weight usually comes in by adding web parts on a page then closing them, over time we end up creating cluttered pages with long load times. If you are like me in the business of maximizing return on investments in whatever we take on you’ll want to reduce user wait times and induce top SharePoint performance. That said here is one of the ways to optimize SharePoint page load times:  

  1. On your client machine that resembles your organization’s standard laptop or desktop specifications; download and install Fiddler Web Debugging Proxy https://www.fiddler2.com/fiddler2/
  2. Close all applications and web browsers to maintain the integrity of the recorded page load times.
  3. Launch Fiddler, Clear IE cache, Launch Browser then ensure the Capture Traffic is checked and as indicated in the following screen capture.
  5. Using the only IE instance open; Navigate to the problematic SharePoint page with the slow load times.
  6. Wait until the full page has loaded and Fiddler has recorded the last HTTP 200 response.
  7. Note the complete page load times for all http responses.
  8. Now the initial capture is complete; navigate to the File menu in Fiddler and stop capturing traffic then click “save” >> “all sessions” as a file named (Before.saz)
  9. Close Fiddler.
  10. At the address bar of the already opened IE window; append “?contents=1” to the aspx file name (Example: https://SharePoint/Sites/SiteCollection/Default.aspx?contents=1)
  11. On the web parts maintenance you might notice a list of on page web parts where the “Open on Page?” indicated as “No”
  12. Although these web parts are not showing when you normally navigate to the page they make up the HTML rendered at the client browser and will need to be downloaded on every request hence the dead weight on the page.
  13. Proceed to “Delete” these web parts where “Open on Page?” is indicated as “No” and after you ensure none of them is being utilized on the page as a query source for another web part that is visible on your page.
  14. Once you have completed sanitizing your page close the active IE window; repeat Steps 1 through 7 and compare the response times on the before.saz file and the after.saz file.
  15. Happy Page Load Times :)

Stay SharePoint Awesome!!

 

]]>