Thursday, January 31, 2013

Unable to create new page "Data at the root level is invalid. line 1 position 1"

Unable to create new page in SharePoint 2007 subsite
Error:  "Data at the root level is invalid. line 1 position 1"

1. Deactivate Office SharePoint Server Publishing feature from the affected subsite - Site features
2. Deactivate Office SharePoint Server Publishing Infrastructure feature from the top level site - Site Collection features
3.  Activate  Office SharePoint Server Publishing Infrastructure feature from the top level site - Site Collection features
4.  Activate Office SharePoint Server Publishing feature from the affected subsite - Site features

Hope this helps.

Wednesday, January 30, 2013


FAST Search Server 2010 for SharePoint delivers an exceptional intranet and people search experience and a platform for building custom search-driven applications.

Basics that may Interest you:

FAST is a Norwegian company based in Oslo, On April 24, 2008, Microsoft acquired FAST. FAST is now known as Microsoft Development Center Norway.

FAST uses complementary technologies from BBN Technologies for speech recognition and Stellent (now part of Oracle) for the conversion of different file formats. 

Why do we need FAST with SharePoint 2010

Automatic Metadata – To avoid any confusion or ambiguous Meta tagging, FAST metadata generation occurs while the content is being created. Now you have terms and language that are familiar to your team and often unique to your business.

Relevance Tuning – Relevancy is key. You have a specific topic in mind when you search so why settle for receiving a slew of extra findings? This relevance is subjective among different users and locations in your company so FAST gives you the ability to fine tune your search model to the needs of different applications to benefit each user type or persona.

Contextual Matching – Think comprehensive. FAST highlights the context and intent of the query to give you the best results, all matched with terms and phrases that appear in the context of the matching text. After all, search is only as strong as its context and FAST captures these contextual results with precision to deliver a specific, superior search experience.

Visualizing Search Results – Why not see before you click? This speaks again to the productivity of FAST when you can see a search result before you click. Users can access thumbnails and preview images from search results so they can recognize the correct content quickly and with better context. Admins can add visual banners and apps with Visual Best Bets to pinpoint critical information for their users.

Backbone for Search-Driven Applications – FAST allows you to build search-driven apps for specific roles in your company. The apps gather specific content from defined sources and add structure to unstructured information and, as a result, specific user groups increase their productivity with a more contextual and interactive search experience.


Thursday, January 24, 2013

You receive “cannot complete this action” error message whenever you try to do anything on your site

This situation basically occurs when you try to backup restore or migrate the sites between two server farms, usually the biggest problem you may face while migration site between two farms is that the user SID gets Screwed for good and then the hell breaks loose when you cannot get users log in to the site the permissions are messed up,

Check these few things before your land up to a conclusion.

Symptoms Faced:
Cannot backup restore or Delete a site collection, you face “Cannot complete this action” error message from Both GUI and Command prompt (I mean stsadm, of course)

This error message sounds a permission problem to you so there you go … start checking these

Run the command stsadm -o migrateuser with the problem account, if its successful you are done otherwise try

stsadm -o updatefarmcredentials

Remember you will have to hit IIS reset after this

Check if the account is available on WSS_WPG; WSS_ADMIN_WPG; IIS_ADMIN_WPG

If the migrate user command fails because you use the same accounts both times then create a temporary account that you create in AD and run the command as

Stsadm –o migrateuser –oldlogin domain\problem account –new login domain\temporary account –ignoresidhistory
Then run
Stsadm –o migrateuser –oldlogin domain\ temporary account –new login domain\ problem account –ignoresidhistory

Make some other account as a site collection administrator, remove the problem account from site collection admin and re-add it
From the link

When permissions are established by NT/XP network ID, problems can arise when an ID is stopped and restarted. When a network user ID is (re)established and there are pre-existing permissions for that ID in a SharePoint site by virtue of membership in site groups by user name (as opposed to domain group membership) and/or as the owner of a site, the person will not be able to access the site. Instead they will get an error message like “Cannot complete this action. Please try again”.
In this case the ID must be removed from the site. This may be easier said than done.

Change the site owner to somebody else. This is done by the server administrator on page “siteusrs.aspx.”

Remove the ID as a site user by removing it from membership in site groups, including any custom list permissions.

This is complicated because SharePoint does not use the text of the user’s ID but a SID, which is different each time the network ID is re-established.

· Finally when you are convinced that this is not a permission problem run the hot fix 956994, which can be obtained from the Support professional also you can try running a very generic KB 936867, which is included in Service pack 1 for MOSS

This fixes the issue for the site with broken permissions problems

Traces of portal 2003 on my MOSS site

I just ran into an issue yesterday where,we have upgraded the environment from Portal 2003 to MOSS 2007 with Gradual upgrade everything is running just fine, but when we try to go into a sub site which has some lists inside it I try to browse through the lists and i find that the lists contain and interface of portal 2003
Just a little background here, the portal 2003 SharePoint site was heavily customized with banner and bread crumbs and quick launch bar, we took out all the customizations before we run the prescan which was successful. then we run the gradual upgrade and this bought the default pages of the site
The issue is I am running into is that the some document libraries still show the SPS2003 Interface. Initially you might think that this is a result of incorrect upgrade, you can try running the command

stsadm –o –upgrade –inplace –url <url of the site> –forceupgrade

If this does not help try resetting site to site definition from the top level site this works in 90% scenarios
I was able to get over the issue with creating a new view on my document libraries and which helped me get rid of the portal 2003 interface
That means when the upgrade was performed the Views did not get updated and sustained the old SPS 2003 look and feel so in short the default views got corrupt and so we have to work around it by creating a new view and replacing the default view.

SPD workflow Failed on start (retrying)

I have been wrestling with this issue for about 60 days, the issue occurs when you create a simple OOB SPD workflow or even a Nintex workflow.
The solution to this is two parts

The service account should be a part of
1. Looked at the groups in the local machine
· WSS_ Restricted
· WSS_Admin_WPG
2. Checked on the SQL management studio  > security > logins > Service account > properties > server roles were given as dbcreator > security & system admin > public
      Looked in user mappings the service account  was set db owner
3. >> Looked in the application content database in SQL
      service account should be  is a db owner
4. In  Central Admin page  > policy for web application > add service account as full control 
5. CA > operations tab > update farm administrators group > service account is added there
6. looked in the site > site settings > site collection administrator
7. looked in the component services > dcom config > IIS admin service > security > added the service account to launch and activation > access permissions > and Configuration permissions .

After doing all these settings the service account must have all the require permissions

Second part of the solution is change the service account from the central admin page & run an IIS reset
this is the main key and you will have to compulsorily do this to resolve the issue

hope it works for you

Diffrence between NTFS and FAT file system

Let’s see what is the difference between NTFS and FAT file system.

In computing, a file system (often also written as filesystem) is a method for storing and organizing computer files and the data they contain to make it easy to find and access them. File systems may use a data storage device such as a hard disk or CD-ROM and involve maintaining the physical location of the files, they might provide access to data on a file server by acting as clients for a network protocol (e.g., NFS, SMB, or 9P clients), or they may be virtual and exist only as an access method for virtual data (e.g., procfs).

FAT 32
Windows 95 OSR2, Windows 98, and Windows Me include an updated version of the FAT file system. This updated version is called FAT32. The FAT32 file system allows for a default cluster size as small as 4 KB, and includes support for EIDE hard disk sizes larger than 2 gigabytes (GB).

• FAT32 supports drives up to 2 terabytes in size. NOTE: Microsoft Windows 2000 only supports FAT32 partitions up to a size of 32 GB.
• FAT32 uses space more efficiently. FAT32 uses smaller clusters (that is, 4-KB clusters for drives up to 8 GB in size), resulting in 10 to 15 percent more efficient use of disk space relative to large FAT or FAT16 drives.
• FAT32 is more robust. FAT32 can relocate the root folder and use the backup copy of the file allocation table instead of the default copy. In addition, the boot record on FAT32 drives is expanded to include a backup copy of critical data structures. Therefore, FAT32 drives are less susceptible to a single point of failure than existing FAT16 drives.
• FAT32 is more flexible. The root folder on a FAT32 drive is an ordinary cluster chain, so it can be located anywhere on the drive. The previous limitations on the number of root folder entries no longer exist. In addition, file allocation table mirroring can be disabled, allowing a copy of the file allocation table other than the first one to be active. These features allow for dynamic resizing of FAT32 partitions. Note, however, that although the FAT32 design allows for this capability, it will not be implemented by Microsoft in the initial release.

Preferably, when using drives or partitions of over 200 MB the FAT file system should not be used. This is because as the size of the volume increases, performance with FAT will quickly decrease. It is not possible to set permissions on files that are FAT partitions. FAT partitions are limited in size to a maximum of 4 Gigabytes (GB) under Windows NT and 2 GB in MS-DOS. For additional information on this limitation, please see the following article in the Microsoft Knowledge Base:
ARTICLE-ID: 118335 (

TITLE: Maximum Partition Size in MS-DOS

NTFS is a high-performance and self-healing file system proprietary to Windows XP 2000 NT, which supports file-level security, compression and auditing. It also supports large volumes and powerful storage solution such as RAID. The most important new feature of NTFS is the ability to encrypt files and folders to protect your sensitive data
From a user's point of view, NTFS continues to organize files into directories, which, like HPFS, are sorted. However, unlike FAT or HPFS, there are no "special" objects on the disk and there is no dependence on the underlying hardware, such as 512 byte sectors. In addition, there are no special locations on the disk, such as FAT tables or HPFS Super Blocks.

The goals of NTFS are to provide:
• Reliability, which is especially desirable for high end systems and file servers
• A platform for added functionality
• Support POSIX requirements
• Removal of the limitations of the FAT and HPFS file systems

To ensure reliability of NTFS, three major areas were addressed: recoverability, removal of fatal single sector failures, and hot fixing. NTFS is a recoverable file system because it keeps track of transactions against the file system. When a CHKDSK is performed on FAT or HPFS, the consistency of pointers within the directory, allocation, and file tables is being checked. Under NTFS, a log of transactions against these components is maintained so that CHKDSK need only roll back transactions to the last commit point in order to recover consistency within the file system. Under FAT or HPFS, if a sector that is the location of one of the file system's special objects fails, then a single sector failure will occur.

NTFS avoids this in two ways: first, by not using special objects on the disk and tracking and protecting all objects that are on the disk. Secondly, under NTFS, multiple copies (the number depends on the volume size) of the Master File Table are kept.

NTFS is best for use on volumes of about 400 MB or more. This is because performance does not degrade under NTFS, as it does under FAT, with larger volume sizes. Disk quotas, file compression, file and folder level securities and more are other advantages.
Alternate data streams (ADS)
Sparse files
Reparse points
Volume mount points
Directory Junctions
Hierarchical Storage Management (HSM)
Native Structured Storage (NSS)
Volume Shadow Copy
File compression
Encrypting File System (EFS)
Symbolic links
Transactional NTFS

It is not recommended to use NTFS on a volume that is smaller than approximately 400 MB, because of the amount of space overhead involved in NTFS. This space overhead is in the form of NTFS system files that typically use at least 4 MB of drive space on a 100 MB partition. Currently, there is no file encryption built into NTFS. Therefore, someone can boot under MS-DOS, or another operating system, and use a low-level disk editing utility to view data stored on an NTFS volume. It is not possible to format a floppy disk with the NTFS file system; Windows NT formats all floppy disks with the FAT file system because the overhead involved in NTFS will not fit onto a floppy disk.

1) allows access local to w2k,w2k3,XP,win NT4 with SP4 &amp; later may get access for somefile.
2) Maximum size of partition is 2 Terabytes &amp; more.
3) Maximum File size is upto 16TB.4) File &amp; folder Encryption is possible only in NTFS.

FAT 32
1) Fat 32 Allows access to win 95,98,win millenium,win2k,xp on local partition.
2) Maximum size of partition is up to 2 TB.
3) Maximum File size is up to 4 GB.
4) File &amp; folder Encryption is not possible.