18 January, 2011

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


14 January, 2011

Exam 70-667 - Configuring Microsoft Sharepoint

This exam is intended to validate the configuration skills needed to administer a SharePoint 2010 installation.

Candidates for this exam typically have more than one year of experience configuring SharePoint and related technologies, including Internet Information Services (IIS), Windows Server 2008, and Active Directory, and networking infrastructure services.

+Is proficient with the infrastructure and security of Windows Server 2008.
+ Has experience with business operations for IT, including data backup, restoration, and high availability.
+ Has experience with Windows PowerShell 2.0 and command-line administration.

The following are the course blueprint

#Installing and Configuring a SharePoint Environment

-Deploy new installations and upgrades:

This objective may include but is not limited to: running Visual Upgrade, performing an in-place upgrade, performing a database attach upgrade, analyzing a PreUpgradeCheck report, installing language packs, and scripting installations; analyzing ULS logs, installation error logs, and event logs to identify installation problems; and repairing installation errors


#Configure SharePoint farms.

-This objective may include but is not limited to: configuring inter-server communications, server roles, high availability, InfoPath Forms Services (IPFS), Alternate Access Mappings (AAM), external sites, host headers, and applying and managing patches


#Configure service applications.

-This objective may include but is not limited to: configuring service applications such as Business Connectivity Services (BCS), Access Services, Visio Services, Microsoft Office PerformancePoint Server 2007, user profiles, Microsoft Office Excel services, Managed Metadata Services (MMS), and IPFS

#Configure indexing and search.

-This objective may include but is not limited to: configuring FAST Search for SharePoint, crawl schedules, iFilters, crawl rules, content sources, scopes, managed properties, content types, search components, index partitioning, and federated search locations


Managing a SharePoint Environment

#Manage operational settings.

-This objective may include but is not limited to: configuring logging, quotas, monitoring levels, health reports, security, and SQL Server Reporting Services (SSRS) integration


- Manage accounts and user roles.

This objective may include but is not limited to: managing user accounts, group accounts, managed accounts, computer accounts, and service accounts; and delegating site collection administration

-Manage authentication providers.

This objective may include but is not limited to: managing NTLM, Kerberos, claims-based, and forms-based authentication; and configuring Secure Store Service (SSS) and Active Directory Federation Services (AD FS).

#Deploying and Managing Applications

-Manage Web Applications.

-This objective may include but is not limited to: managing databases, Web Application settings, security, and policies.

-Manage site collections.

This objective may include but is not limited to: managing site collection policies, features, caching, and auditing; configuring site collection security; configuring multi-tenancy; and configuring site collection quotas and locks.


-Deploy and manage SharePoint solutions.

This objective may include but is not limited to: deploying and managing SharePoint solution packages, managing sandbox solutions, and managing user solutions

#Maintaining a SharePoint Environment

-Backup and restore a SharePoint environment.
This objective may include but is not limited to: configuring backup settings; backing up and restoring content, search, and service application databases; detaching and attaching databases; and exporting lists and sites

-Monitor and analyze a SharePoint environment.

This objective may include but is not limited to: generating health, administrative, and Web analytics reports; interpreting usage and trace logs; identifying and resolving health and performance issues

Please let me know in case of any queries or questions, Thanks...

11 January, 2011

Cannot connect to SQL Server - Event 3355 (SharePoint Server 2010)

Microsoft SharePoint Foundation 2010 uses Microsoft SQL Server 2008 databases to store configuration settings and most of the content for the Microsoft SharePoint Foundation Web site.

For example, all pages in the site, files in document libraries, files attached to lists, and information in lists are stored in the content database, and security and permission settings along with other configuration settings are stored in the configuration database in SQL Server. SharePoint Foundation 2010 uses a service account to communicate with the database on behalf of a user request. This service account can be either a specific user name or password (domain name and password), or a predefined system account, such as Local System or Network Service. When a SQL Server database is created, a value for the maximum database size is set. Each database has a separate database size setting. Note that a Web application might be associated with one or many databases.

This error indicates that Microsoft SharePoint Foundation could not connect to the SQL Server database.

One or more of the following symptoms might appear:
• Attempts to communicate with SQL Server fail and no content from databases hosted on the SQL Server can be accessed.
• This event appears in the event log: Event ID: 3355 Cannot connect to SQL Server.
not found. Additional error information from SQL Server is included below.

One or more of the following might be the cause:
1. The SQL Server might be offline.
2. The SharePoint Foundation database access account might not have the necessary permissions to communicate with the SQL Server.
3. A firewall that runs on either the local server or on SQL Server might be blocking network communications.

Troubleshooting Steps:

Grant correct permissions to the database access account:
You must be a member of the Farm Administrators group to perform this task.

Assign the database access account:
a. On the Central Administration home page, click Security and in the General Security section click Configure service accounts.
b. On the Service Accounts page, in the Credential Management section, in the upper dropdown list click the correct Web application pool for your Web application.
c. In the Select an account for this component drop-down list, click the domain account that you want to associate with this Web application pool, or click Register new managed account to associate a new domain account with this application pool.
d. Click OK to save changes.

Verify that the account has correct permissions in SQL Server:
a. Connect to the computer that runs SQL Server by using an account that has Administrator permissions.
b. In SQL Server Management Studio, Object Explorer navigation pane, expand the Security node, and then expand the Logins node. The name of the database access account indicates that it is a SQL login.
c. If the account exists, in the Object Explorer navigation pane, expand the Databases node, expand the configuration database node, expand the Security, and then click Roles.
d. Expand the Database Roles node, right-click db_owner role and select Properties.
e. In the Database Role Properties dialog box, check whether the database access account is in the Members of this role list. If the account is not listed, click Add.

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