Monday, April 15, 2013

One or more field types are not installed properly. Go to the list settings page to delete these fields.

This errors occurs when using CAML query with display names rather than internal names.

Solution is to use the internal name in the query. You can find out the internal names of the list columns using SharePoint Manager (http://spm.codeplex.com/releases/view/51438)

Happy coding!

Sunday, April 7, 2013

An update conflict has occured, you must re-try this action again.The object SPProcessIdentity was ...

Error :
An update conflict has occured, you must re-try this action again.The object SPProcessIdentity was ...
This error occurs when any timer job task is underway and it is preventing another task. For example when you are configuring service accounts I got this error.
The solution is to clear and reset the SharePoint timer job 'Cache' by doing following steps: 
  1. Stop the Windows SharePoint Services Timer service (Found in Windows Services)
  2. Navigate to the cache folder
    In Windows Server 2008, the configuration cache is in the following location:
    Drive:\ProgramData\Microsoft\SharePoint\Config
    In Windows Server 2003, the configuration cache is in the following location:
    Drive:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config
    Locate the folder that has the file "Cache.ini"
    (Note: The Application Data folder may be hidden. To view the hidden folder, change the folder options as required)
  3. Back up the Cache.ini file.
  4. Delete all the XML configuration files in the GUID folder. Do this so that you can verify that the GUID folder is replaced by new XML configuration files when the cache is rebuilt.
  5. Note When you empty the configuration cache in the GUID folder, make sure that you do not delete the GUID folder and the Cache.ini file that is located in the GUID folder.
  6. Double-click the Cache.ini file.
  7. On the Edit menu, click Select All. On the Edit menu, click Delete. Type 1, and then click Save on the File menu. On the File menu, click Exit.
  8. Start the Windows SharePoint Services Timer service
  9. Note The file system cache is re-created after you perform this procedure. Make sure that you perform this procedure on all servers in the server farm.
  10. Make sure that the Cache.ini file in the GUID folder now contains its previous value. For example, make sure that the value of the Cache.ini file is not 1.

Move-SPUser : The parameterless Read method can only be used when this instance was initialized with an SPUser object.

Correct way of doing it-

$user = Get-SPUser -web http://my.website.url -Identity DomainA\UserA
Move-SPUser -IgnoreSID -Identity $user -NewAlias 'DomainB\UserA'