22 January, 2011

Word experience an error trying to open the file / Word has encountered a problem

Right from last few days, i am trying to explorer office 2010 which is very advanced as compare to previous office suites n thats why i am heavily testing 'Word,Excel n PowerPoint' documents which are most commonly used by users.

while testing, i had found some strange errors which causes a lot of headache if you don't find the resolution quickly.

But don't worry and say cheers :-) as i have the resolution for this which will help everybody to get rid of this.

Whenever I try to open the Word 2010 /PowerPoint 2010/Excel 2010 documents stored in the SharePoint document libraries, I get the following error.



Resolution:

Please follow the below mentioned steps that will resolves your issues:1. Run one οf the Personnel 2010 application (e.g. Word 2010).
2. Click οn File menu, аnԁ select Options.
3. In the “Options” dialog, select Trust Center іn the left pane.
4. Click οn Trust Center Settings іn the rіɡht pane.
5. Select Protected View іn the left pane οf “Trust Center” dialog.
6. Disable аnу οf аƖƖ οf the protected view options аѕ below bу unticking thе check boxes:
* Enable Protected View fοr files thаt fail substantiation
* Enable Protected View fοr files originating frοm the Internet
* Enable Protected View fοr files located іn potentially unsafe locations
* Enable Protected View fοr Outlook attachments

Please refer the below mentioned screen-shot for detailed information:


I hope the above information will helps you resolve your issues...In case of any queries/questions then please let me know.. I would be more than happy to help you as well as resolves your issues, Thanks again :-) :-)

 

18 January, 2011

DataSheet views in Sharepoint 2007 don't work with Office 2010



I have installed Office 2010 (64 bit) in my windows 7 machine and did some testing with sharepoint 2007 sites.

As list and document libraries are the most common used components in SharePoint sites so i had started my testing with these ones and found out one problem /error message which takes some time to resolved it completely.

I would like to share my resolution with all of you so that you do not have to waste your time while digging the same problem.

I went to my SharePoint 2007 site and tried to edit a custom list in datasheet view. I’ve got an above mentioned error message :

The list cannot be displayed in Datasheet view for one or more of the following Reasons

Resolution:

Various editions of Microsoft Office 2007 include SharePoint support component, which is installed by default:

-Microsoft Office
-Office Tools
-Windows SharePoint Services Support.

Specifically the “Edit in datasheet” feature is supported by the sub-component named “Microsoft Office Access Web Datasheet Component”. I went and checked out the components installed for my Office 2010 – and the various unnecessary components were marked as installed:

What you have to do:

install back Windows SharePoint Services Support for Office 2007. Below is a screen shot – I only needed this specific part of the office and nothing else:




Now the “View in Datasheet” worked for me.

If you have any queries/questions regarding the above mentioned information then please let me know, Thanks..












Office 2010 does not open SharePoint 2007 documents

I have been using Office 2010 but have been getting into complications while updating documents in a Share Point 2007 atmosphere. When I attempt to open a sharepoint document in Office 2010 . I got an error-'cannot open document' . The strange thing is if I save the same document from sharepoint to the Hard-Drive it opens without an issue.

I would like to share the resolution that worked for me and hope it will work for all the users too :-)

1. Open up Internet Explorer
2. Click Tools –> Internet Options
3. Click the Connections tab
4. Click LAN settings
5. Check “Use a proxy server for your LAN (These settings will not apply to dial-up or VPN connections).”
6. Enter 127.0.0.1 for the address
7. Click Advanced
8. In the Exceptions type: *.*
9. Click Ok

You should now be able to browse to a SharePoint site, click an Office document and have it successfully open in your Office 2010 client.

If you have any queries/questions regarding the above mentioned info then please let me know, Thanks...I would be more than happy to help you as well as resolves your issues :-)

16 January, 2011

Exam 70-668: Microsoft SharePoint 2010, Administrator

Designing a SharePoint 2010 Farm Topology

# Design physical architecture.
-This objective may include but is not limited to: translating information architecture to physical architecture, determining capacity for a SharePoint farm (storage, number of users, bandwidth utilization, intranet/extranet, hardware), and scaling Web farm and services infrastructure

#Plan for farm deployment.
-This objective may include but is not limited to: sequential deployment, planning standalone deployment (Microsoft SQL Server Express), planning single-server farm (SQL Server), planning multi-server deployment in an N-Tier Farm, and designing a SharePoint virtual environment

# Plan for availability.
-This objective may include but is not limited to: designing SQL Server failover clustering strategy, types of availability (high-performance, acceptable downtime, Recovery Point Objective, Recovery Time Objective ), types of mirroring, high availability, high protection, whole farm as a failover cluster, and designing the Web Front-End NLB strategy

#Design SharePoint integration with network infrastructure.
-This objective may include but is not limited to: planning for internal and external farm communications, establishing network perimeter configuration, networking, Active Directory, DNS, SQL storage, IIS, and analyzing infrastructure services

# Design logical taxonomy.
-This objective may include but is not limited to: planning sites and site collections, planning for collaboration sites, planning My Site sites, planning for zones, planning for Service Applications, Web applications, content databases, sites and sub-sites vs. libraries, libraries vs. folders vs. document sets, security boundaries, site hierarchy, and content deployment path methodology

#Plan for sandbox solutions.
-This objective may include but is not limited to: content isolation, feature deployments, and trusted solutions


Planning for Search and Business Solutions

#Define search requirements.
-This objective may include but is not limited to: types of data, types of distribution (Internet, extranet), segregation of data, index file location, index size, federation requirements, content sources, search scopes, search taxonomy, server name mappings, promoting or demoting exclusions, synonyms and compound search processing, and defining facets for search

#Enterprise content management.
-This objective may include but is not limited to: records management, BPM (record deployment), document management, metadata planning, information management policies, implement data taxonomy structure, Web Content Management (WCM), and Information Rights Management (IRM)

#Social computing and collaboration.
-This objective may include but is not limited to: user profile service, user profiles, organization profiles, audiences, My Sites, social tags, and planning enterprise wikis, blogs, and personalization sites

#Business intelligence strategy.
-This objective may include but is not limited to: PerformancePoint service (dashboards and scorecards), Excel Services Service, Visio Graphics Service, SQL Reporting Services, chart Web parts, and report center


Planning SharePoint 2010 Deployment

#Service applications.
-This objective may include but is not limited to: formulating a Business Connectivity Services (BCS) strategy, planning a Microsoft Excel Services strategy, implementing a BI solution, planning service application server roles, and planning a Web server forms strategy (Plan InfoPath Forms Services)

#SharePoint component strategy.
-This objective may include but is not limited to: Web parts, Web applications, Microsoft .NET, Microsoft Silverlight, SharePoint features and solutions, workflow, site templates, site definitions, multilingual deployment, master pages and layout files, and e-mail integration

#An upgrade strategy.
-This objective may include but is not limited to: supporting hardware upgrades (for example, 32 to 64 bit), OS upgrade, in-place upgrade, MOSS upgrade, and SQL Server upgrade

#Design a migration strategy.
-This objective may include but is not limited to: database migration, custom features, read-only and detached databases, designing a test and QA implementation plan (for example, development to production), migrating content databases, moving content between farms, moving content to and from the farm, moving content within the farm, and rollback

#Design security architecture.
-This objective may include but is not limited to: planning security for WebApp site collection, designing SharePoint users and groups administration, taxonomy of SharePoint security groups, managed accounts, site security (permission levels , list permissions, site permissions, personal permissions, default and custom security groups), and planning for Secure Sockets Layer (SSL)

#Plan and deploy authentication methods.
-This objective may include but is not limited to: planning for integration of multiple authentication sources/types, planning for NTLM authentication, planning for Kerberos authentication, planning for Forms-Based Authentication (FBA), planning for Claims Authentication (Identity and Access Management), planning for Secure Store Service

Defining a SharePoint 2010 Operations Strategy and Business Continuity

#Design a maintenance strategy.
-This objective may include but is not limited to: preparing test plans for patching and maintenance, SharePoint Maintenance Manager, rebuilding SQL indexes, search maintenance

#Recommend provisioning strategies.
-This objective may include but is not limited to: managing self-service components (My Sites, service architecture administration), delegating site administration, limiting site templates and page layouts, assigning quotas, defining policy for Web application

# Establish an enterprise monitoring plan.
-This objective may include but is not limited to: developing monitoring points for performance and availability, utilizing performance monitoring, analyzing search reports, Web analytics, diagnostic logging, usage logging, analyzing health and usage data (SharePoint Health Analyzer), and validating farm topology against performance requirements

#Plan SharePoint backup and restore.
-This objective may include but is not limited to: developing and testing recovery strategy and implementation plan, server recovery, site recovery, granular backup and recovery strategy, exporting a site or list, recovering data from an unattached content database, and backup and restore of the following: farm, farm configuration, site collection, Web applications, Secure Store Service, snapshots, content database, configuration database, custom features, solutions, code, service, site, list, document library, performance site collection, and recycle bin

Resources:-

Here are a few of the resources I utilized to help prepare for the exam.

SharePoint 2010 Advanced IT Professional Training – This is a boiled down set of videos made available to those who passed the 2007 IT Pro exams. While some of the videos tend to drag on, it’s a good place to learn & understand 2010.
http://technet.microsoft.com/en-us/sharepoint/ff420396.aspx

TechNet Virtual Labs: SharePoint Products and Technologies
http://technet.microsoft.com/en-us/virtuallabs/bb512933.aspx

if you have any doubts or queries regarding the above mentioned information then please let me know, Thanks...


Exam 70-668: Microsoft SharePoint 2010, Administrator

Designing a SharePoint 2010 Farm Topology

# Design physical architecture.
-This objective may include but is not limited to: translating information architecture to physical architecture, determining capacity for a SharePoint farm (storage, number of users, bandwidth utilization, intranet/extranet, hardware), and scaling Web farm and services infrastructure

#Plan for farm deployment.
-This objective may include but is not limited to: sequential deployment, planning standalone deployment (Microsoft SQL Server Express), planning single-server farm (SQL Server), planning multi-server deployment in an N-Tier Farm, and designing a SharePoint virtual environment

# Plan for availability.
-This objective may include but is not limited to: designing SQL Server failover clustering strategy, types of availability (high-performance, acceptable downtime, Recovery Point Objective, Recovery Time Objective ), types of mirroring, high availability, high protection, whole farm as a failover cluster, and designing the Web Front-End NLB strategy

#Design SharePoint integration with network infrastructure.
-This objective may include but is not limited to: planning for internal and external farm communications, establishing network perimeter configuration, networking, Active Directory, DNS, SQL storage, IIS, and analyzing infrastructure services

# Design logical taxonomy.
-This objective may include but is not limited to: planning sites and site collections, planning for collaboration sites, planning My Site sites, planning for zones, planning for Service Applications, Web applications, content databases, sites and sub-sites vs. libraries, libraries vs. folders vs. document sets, security boundaries, site hierarchy, and content deployment path methodology

#Plan for sandbox solutions.
-This objective may include but is not limited to: content isolation, feature deployments, and trusted solutions


Planning for Search and Business Solutions

#Define search requirements.
-This objective may include but is not limited to: types of data, types of distribution (Internet, extranet), segregation of data, index file location, index size, federation requirements, content sources, search scopes, search taxonomy, server name mappings, promoting or demoting exclusions, synonyms and compound search processing, and defining facets for search

#Enterprise content management.
-This objective may include but is not limited to: records management, BPM (record deployment), document management, metadata planning, information management policies, implement data taxonomy structure, Web Content Management (WCM), and Information Rights Management (IRM)

#Social computing and collaboration.
-This objective may include but is not limited to: user profile service, user profiles, organization profiles, audiences, My Sites, social tags, and planning enterprise wikis, blogs, and personalization sites

#Business intelligence strategy.
-This objective may include but is not limited to: PerformancePoint service (dashboards and scorecards), Excel Services Service, Visio Graphics Service, SQL Reporting Services, chart Web parts, and report center


Planning SharePoint 2010 Deployment

#Service applications.
-This objective may include but is not limited to: formulating a Business Connectivity Services (BCS) strategy, planning a Microsoft Excel Services strategy, implementing a BI solution, planning service application server roles, and planning a Web server forms strategy (Plan InfoPath Forms Services)

#SharePoint component strategy.
-This objective may include but is not limited to: Web parts, Web applications, Microsoft .NET, Microsoft Silverlight, SharePoint features and solutions, workflow, site templates, site definitions, multilingual deployment, master pages and layout files, and e-mail integration

#An upgrade strategy.
-This objective may include but is not limited to: supporting hardware upgrades (for example, 32 to 64 bit), OS upgrade, in-place upgrade, MOSS upgrade, and SQL Server upgrade

#Design a migration strategy.
-This objective may include but is not limited to: database migration, custom features, read-only and detached databases, designing a test and QA implementation plan (for example, development to production), migrating content databases, moving content between farms, moving content to and from the farm, moving content within the farm, and rollback

#Design security architecture.
-This objective may include but is not limited to: planning security for WebApp site collection, designing SharePoint users and groups administration, taxonomy of SharePoint security groups, managed accounts, site security (permission levels , list permissions, site permissions, personal permissions, default and custom security groups), and planning for Secure Sockets Layer (SSL)

#Plan and deploy authentication methods.
-This objective may include but is not limited to: planning for integration of multiple authentication sources/types, planning for NTLM authentication, planning for Kerberos authentication, planning for Forms-Based Authentication (FBA), planning for Claims Authentication (Identity and Access Management), planning for Secure Store Service

Defining a SharePoint 2010 Operations Strategy and Business Continuity

#Design a maintenance strategy.
-This objective may include but is not limited to: preparing test plans for patching and maintenance, SharePoint Maintenance Manager, rebuilding SQL indexes, search maintenance

#Recommend provisioning strategies.
-This objective may include but is not limited to: managing self-service components (My Sites, service architecture administration), delegating site administration, limiting site templates and page layouts, assigning quotas, defining policy for Web application

# Establish an enterprise monitoring plan.
-This objective may include but is not limited to: developing monitoring points for performance and availability, utilizing performance monitoring, analyzing search reports, Web analytics, diagnostic logging, usage logging, analyzing health and usage data (SharePoint Health Analyzer), and validating farm topology against performance requirements

#Plan SharePoint backup and restore.
-This objective may include but is not limited to: developing and testing recovery strategy and implementation plan, server recovery, site recovery, granular backup and recovery strategy, exporting a site or list, recovering data from an unattached content database, and backup and restore of the following: farm, farm configuration, site collection, Web applications, Secure Store Service, snapshots, content database, configuration database, custom features, solutions, code, service, site, list, document library, performance site collection, and recycle bin