Ic: Word, Excel
This is the fix.
Here are the revised steps.
Open the Run Window, this can be done by pressing the “Windows” and “R” Keys simultaneously on your keyboard.
- Type regedit in the window and click OK. This would open the Registry Editor.
On the Registry Editor, expand HKEY_CURRENT_USER.
- Then scroll down and expand Software.
Then similarly expand Microsoft->Office->16.0->Common->Identity
Right Click on Identity and select New-> DWORD (32-bit) Value.
Name the value as EnableADAL. Make sure you type this exactly as how it is listed, it is case sensitive.
Restart your computer.
Should all work
This article is 1 of 4 articles that cover creating, testing and maintaining a SharePoint DR plan. These articles are from a chapter extract from the book: Microsoft SharePoint 2013 Disaster Recovery Guide.
One of the first steps of a DR plan and introduces the reader to the activities around creating, testing, and maintaining an effective DR plan for their SharePoint environment. Before creating a test plan, one must have a clear understanding what each component of their SharePoint farm is, the role it plays, and the threats each of these components faces that could cause the disaster recovery plan to be exercised.
A SharePoint farm is a collection of SharePoint servers or SQL servers that work in together to provide a set of basic SharePoint services that support a single site.
The ability of multiple servers to work in conjunction and provides system is its failover capabilities and load balancing. The servers can also provide readily available backups that can scale to immense sizes. Useful for DR!
Within a farm, there are several services that run on one or more servers. These services provide basic functionality for SharePoint and regulate which services should run on which servers, in an effort to manage the impact on overall farm architecture and performance.
There are occasions when multiple SharePoint farms make sense. An enterprise might have a quality assurance (QA) and PROD farm. Geographically dispersed enterprises might have a farm in Europe, one in the Asia-Pacific region and another in North America.
In this article, we will cover:
- Identifying all components of your SharePoint Environment
- Identifying Threats to your SharePoint Environment
- Creating an Effective Disaster Recovery Plan
- Testing your Disaster Recovery Plan
- Maintaining your Disaster Recovery Plan
Imagine you are the administrator of a SharePoint implementation for a large company that uses SharePoint for their corporate intranet, collaboration sites, enterprise search, and other mission critical business processes. One day you are sitting at your desk and you get a call from a user saying they are receiving an error when trying to access the intranet.
As you begin taking a look at this, you receive several more phone calls as well as e-mails from other users experiencing the same problems. You attempt to log in remotely into the SharePoint Central Admin server to check on the server logs and Unified Logging System (ULS) logs; however, there is no response from the server. What do you do now?
You begin with basic troubleshooting to see if you can determine what the issue is and see if you can get it corrected in a timely manner; however, in this particular case you discover your server that runs Central Admin and several key SharePoint services has died.
This would be the time to refer to your DR plan (ideally not saved in SharePoint) to see what to do next assuming you had a plan. Even if you had a plan, are you sure it will work? Has it been tested? These are the kind of questions that need to be answered before a disaster occurs, not after you are in the midst of one.
So how do you start with a SharePoint DR plan? There are some preliminary steps you should take as part developing your SharePoint DR plan. These steps include identifying each component of your SharePoint environment and the threats to each that could cause a disaster
Identifying all components of your SharePoint environment
As a first step before creating a DR plan, you should take a complete inventory of each component of your SharePoint environment. This inventory should include:
- The physical architecture such as the servers, the database, and the network
- The logical architecture such as web applications, service accounts, service applications, and apps
- Custom software installed in the farm
You should begin the process of taking an inventory of each component of your SharePoint environment by starting with the physical architecture. The physical architecture should include all farms and related components in your SharePoint environment including any development, testing, staging, quality assurance (QA) and production farms.
While the other SharePoint farms aside from your production farm may not be part of your SharePoint DR plan it is good practice to make sure you have an inventory of each farm as you may need to utilize individual components of the physical architecture of any of these environments as part of your overall SharePoint DR plan should you experience a failure in any of the physical components of your production SharePoint farm.
As part of the process of identifying the Physical Architecture of your SharePoint farms you should create easy to read diagrams using a tool like Microsoft Visio.
Each server in each SharePoint farm in your environment needs to be identified. The information collected for each server should include the following:
- Server Name
- Server Description/Purpose
- Server Location
- Physical or Virtual
- Host Name (if Virtual)
Internet Protocol (IP) Addresses
- External (if applicable)
- Operating System (including Service Packs, patch level and hotfixes))
- Network Interface Cards (NIC)
- Drive Letter
- Drive Type (Internal, Storage Area Network (SAN))
- Backup Schedule
Services and Roles
- Application Server Role
- Internet Information Services (IIS)
- Simple Mail Transport Protocol (SMTP)
Installed Software (version, Service Packs, patch level and hotfixes)
A complete inventory of all SharePoint related database servers should be collected. It may be necessary to work with a DBA to gather this information. Information gathered should include:
- SQL Server Version (including Service Packs, patch level and hotfixes)
- SQL Server Configuration (Standalone, Mirrored, Clustered, Always On)
- Data File Name
- Data File Location
- Log File Name
- Log File Location
- Settings (Autogrowth, Log File Size, and so on)
- Additional Services (Reporting Services, Analysis Services, Integration Services, and so on)
- Backup Tools
In order to get as much detail about your SharePoint environment and to help you develop your SharePoint DR plan you should include details about the network(s) used by the SharePoint environment. Information collected about your network should include:
The next step in the process of taking an inventory of each component of your SharePoint environment deals with the logical architecture. The logical architecture should include the high level logical components in your SharePoint environment including any development, testing, staging, quality assurance (QA) and production farms.
The highest level in a SharePoint logical architecture for a SharePoint farm is the Web Application. The information collected for each Web Application in every one of your SharePoint farms should include the following:
- Web Application Name
- Uniform Resource Locator (URL)
- Alternate Access Mappings
- Content Database Name(s)
- Application Pool(s)
- Authentication Provider(s)
- Additional Settings
- web.config files
- IIS Settings (i.e. Host Headers)
It is important to identify each Service Account used by each SharePoint farm in the environment. Service Account information that should be captured is as follows:
- Service Account Name
- Local Rights
- Domain Rights
Each SharePoint Farm will have several associated Service Applications. Service Application information that should be captured is as follows:
- Service Application Name
- Service Application Description
- Server(s) Running Service Application
- Service Application Pool(s)
- Service Application Database Name(s)
- Service Application Service Account(s)
- Additional Settings (i.e. the Secure Store Service Application” needs to record and keeps the passphrase, used to encrypt the credential, in a secure location)
SharePoint 2013 introduces the concept of the Apps model to the product. Apps are essentially web applications that fit seamlessly into the SharePoint website where they are installed and therefore bring data and functionality to the users’ familiar work environment and provide them with a familiar user experience.
For example, let’s say you have a SharePoint site to collaborate with a team, and you want to create a survey to gather more data. In SharePoint 2013, you can get a “survey app” from the Office Store or from your SharePoint App Catalog and install it on your site.
Apps can be hosted in a variety of different ways including in a private cloud, a public cloud such as Windows Azure or directly within SharePoint. The following diagram summarizes the critical aspects of the various hosting approaches for the SharePoint 2013 App Model.
You should capture information about all of the apps that are installed and used in your SharePoint farm so if you need to recover you environment in the event of a disaster you can reconfigure all of the apps in the farm. Information about SharePoint Apps that should be collected is as follows:
- App Name
- App ID
- App Description/Purpose
- App Domain
- App Service Settings
- App Authentication Configuration
The name of the game in of this SharePoint book is SharePoint Disaster Recovery (DR), which also falls into the category of business continuity or high availability. The depth and breadth of the SharePoint DR can be quite daunting because often the reader is new to SharePoint and does not quite know how the pieces of the puzzle all fit together and is facing the challenge of determining how to implement a DR within their organization.
This book is structured to fill in the SharePoint knowledge gaps of how to apply a SharePoint DR approach that is documented, easy to understand and is executable.
By applying knowledge from each chapter, this book will demystify the DR process and you will learn how to identify risk and appropriate DR approaches, and out of the box SharePoint tools for your DR plans.
I’ve been working a lot with DVWP in recent weeks and have had a few issues which I’ve fixed or how to work around.
Web Connections. Often if there are multiple web part connections on a page you may suddenly get an error when opening a page.
Could not find the connection provider Web Part with ID “g_2f2eb8c3_d516_439f_8e67_ffa57b95212e”.
To avoid this…Or work round it, work on the page without the connections, make a copy of the page, then add in the connections. If further design requirements are needed, work on the page without connections and repeat the process of adding in the connections.
Unable to display this Web Part” on Data Views after restoring site from backup – SharePoint Designer Support Team Blog – Site Home – MSDN Blogs
This is a MS work around
Categorizing a column with the date value.
Need to have the Edit formula something like: string(ddwrt:FormatDate(string(@Review_x0020_Date),1033,1))
To avoid the date looking like: 12/12/2010-TXX23-433-12-12-10
This also works ddwrt:FormatDate(string(@EventDate) ,2057 ,3)
Dealing with UK dates. Click here
ddwrt:FormatDate(string(@EventDate) ,2057 ,3)
Modify the lengths of List Form Fields
SharePoint 2007 Quick Start Assessment and Roadmap
This program is designed to help organizations quickly and cost-effectively evaluate the significant new capabilities of Microsoft Office SharePoint Server (MOSS) 2007. The SharePoint Quick-Start Assessment and Roadmap program aims to model proven best practices to rapidly deploy a solution that meets both business and technical requirements. More…
E Forms (ERP Data Information)
Take advantage of this singe e-form engagement. Forms include: Requisition, Expense Reports, A/R, A/P, Expense Handling, New Hire Application, Journal Entries, or Timesheet Entry. More…
Analytics and Dashboards (ERP BI)
Understanding your business activities is critical to making quality decisions that keep your business competitive. Winning companies use objective, quantifiable measurements with BI tools based on factual data. More…
Information Productivity Assessment
This review examines the business and time management practices of information workers (the people who fill out the Word documents or approve them) and identifies opportunities for process automation to create consistent approaches. More…
Technical Infrastructure 10 Point Health Check
Our 10-Point Health Check provides you with a comprehensive inspection of SharePoint and the complementary technologies. Our SharePoint solution architects will view and diagnose the environment to recommend best practices and tools to improve administration. More…
Document Capture (ERP Automation)
SharePoint has the ability to be a high-volume, production-level capture system designed to eliminate these problems. It can gather documents from end users in your corporate headquarters and branch offices and easily scan and index documents, then store them in the appropriate SharePoint repository in TIFF, PDF and XPS file formats. Digital asset management: Invoices, Purchase Orders, and Vendor Management. More…
Building Highly Available SharePoint Farms
Do you have SharePoint running on a single server with performance slowing to a crawl? Are your development and production environment the same? These are recipes for a disaster. Can your environments recover from these disasters? More…
The next version of Groove is getting a new name; the successor to Microsoft Office Groove 2007 will be SharePoint Workspace 2010.
Microsoft claims that this is a natural progression since Groove is to SharePoint like Outlook is to Exchange. SharePoint Workspace 2010 won’t just be the same product with a new name: the software giant plans to add features that make it easier to deploy and manage. At the same time, Microsoft says that SharePoint Workspace will make it easier to access SharePoint content (or content from any server that implements the publicly documented protocols).
Microsoft also noted this week that SharePoint Workspace and OneNote will be added to Microsoft Office Professional Plus 2010. The addition of these two products into this SKU should be a big deal for Volume Licensing customers.
In the good old days of …..2007, when everyone used Explorer as their browser 🙂 cross browser compatibility wasn’t an issue.
Now Safari is making in roads.
I’ve noticed that Fire Fox is being used a lot unofficially with some of our clients. This is course problems with SharePoint if you customize the css files and master pages. Today IE, Firefox, and Safari handle CSS rendering and the code contained within HTML editor Web Parts in different ways. Firefox can be resolved without too much heavy lifting, but Safari is a different beast and it’s not just look and feel, but also authentication issues and lost cookies, plus missing Office integration features and menus, etc.
Also running Safari on a mac and pc is a different experience, not just with fonts.
It’ll be good to know the requirements before the work commences.
Brings back memories of the Netscape and Explorer wars of the 90’s.
Media Focused Webinar• Have you excelled quicker than you should?• Have an informal process that really should be formalized?
SharePoint has been the fastest growing product in Microsoft history. By making it easier to manage content and streamline processes.
Learn how to:• Display a media calendar of Digital, OOH , Print, Radio, Retail, TV, Other campaigns
• Automate campaign due dates • Stream line the process for each media type:Planning —> Approval —> Buying
• Authorizations of media plans, schedules, flow charts• Automate your performance metrics: Post-Analysis, Digital – Tracking, TV – Post-Buy Summaries
• Dashboard research from different sources: Nielson, Workhorse• View your billing schedule in 2 clicks• Reports: US budget, spending vs. marketing. With drill down functionality
• Provide metrics and data visibilities to monitor performance capacity forecasts and inventory availability to guide sales activities.
• Timesheet tracking of your campaignsIf you put your finger in the air, to get a sense of how your business is performing, this free webinar is for you.
Imagine a world where there is 1 version of the information, based on fact!! SharePoint can be that world..
Communicate + Collaborate + Coordinate = SharePoint