Archive

Archive for January, 2012

MOSS MA Not found error when create new synchronization connection

January 28, 2012 Leave a comment

Error message get in ULS Viewer

LoadConnections failed trying to fill the connections list. Most likely during RetriveResources because of permissions — {1}.  Available parameters: Microsoft.ResourceManagement.WebServices.Client.PermissionDeniedException: Access to the requested resource(s) is denied

at Microsoft.ResourceManagement.WebServices.Client.ResourceTemplate.EnumerateResources(SearchParameters parameters)

at Microsoft.ResourceManagement.WebServices.ResourceManager.RetrieveResources()

at Microsoft.Office.Server.UserProfiles.ConnectionManager.LoadConnections() .

ConnectionManager.LoadConnections(): Could not find MOSS MA despite being marked as fully configured, was it deleted?


I had recently Added New Web Servers to our farm, and the two FIM services Not working

At last, Start the User Profile Synchronization service in Central Administration -> Manage Services on  New Servers . Start the service will start the two FIM services.

Then the error dis appeared .

Advertisements

SharePoint Search Error – Event ID 6482

January 3, 2012 Leave a comment

Error message when you try to start User Profile Synchronization in SharePoint 2010: An update conflict has occurred, and you must re-try this action. The object UserProfileApplication Name=User Profile Service Application was updated by [User]

Symptoms:

When you try to start User Profile Synchronization (Full/Incremental) or start the “User Profile Synchronization Service” found under “Services on server” in SharePoint 2010, you receive an error
“An update conflict has occurred, and you must re-try this action. The object UserProfileApplication Name=User Profile Service Application was updated by [User]”Full details about this error as it is logged in various places has been detailed below:

ULS:

ConcurrencyException: Old Version : 241817 New Version : 241817 99a7a04b-0297-4ecc-9621-a38b05c8ccce Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object UserProfileApplication Name=User Profile Service Application was updated by [User], in the OWSTIMER (3456) process, on machine [Server Name]

ULS:

SharePoint Foundation Runtime Unexpected Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object UserProfileApplication Name=User Profile Service Application was updated by [User], in the OWSTIMER (3456) process, on machine [Server Name]

Event Viewer:

The Event 6482 is logged once every minute and has the following data:
An update conflict has occurred, and you must re-try this action. The object SearchDataAccessServiceInstance was updated by [User], in the OWSTIMER (1756) process, on machine [Server Name].

Troubleshooting:

Our initial thoughts went in the direction of Active Directory. We have started investigating whether any changes have been made to the AD that may be causing the issue. After confirming that no AD changes have been made, we tried to see why it is failing using the “Microsoft Forefront Identity Manager 2010” as it provides step by step detail about what happens. The “Microsoft Forefront Identity Manager 2010” failed to start because the “User Profile Synchronization Service” and the forefront windows services (Forefront Identity Manager Service and Forefront Identity Manager Synchronization Service) were in stopped state. When we tried to start the “User Profile Synchronization Service”, we got the same error detailed above.
We took the whole farm backup and investigated further.

Cause:

This issue occurs if the contents of the file system cache on the front-end servers are newer than the contents of the configuration database. After you perform a system recovery, you may have to manually clear the file system cache on the local server.

Resolution:
To resolve this issue, clear the file system cache on all servers in the server farm on which the Windows SharePoint Services Timer service is running.

Microsoft has provided a step by step procedure on clearing file system cache from the SharePoint front-end servers in this kb article.

  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.

Open a popup window on loading SharePoint Homepage

January 1, 2012 24 comments

Many times we need to open popup window on loading our homepage in SharePoint to tell to our users there are an important thing happened or to tell them we need to do something such as loading popup window while loading SharePoint homepage to tell to user we need  you to do specific survey . by clicking on any place inside the window redirect him to survey window.

Now , let us do something like this. We need to open POPUP window to enforce users to complete specific survey.

1-     Firstly, we need to create an  application page for the Page which will POPUP while loading the page. (this is not our topic now how to create new application page)

2-     Add content editor web part to homepage.

 

3-     Create JavaScript function and put it in a text file or script file. Then load this file to any document library . then take the URL of this file and add it in content editor web part which we have added in previous  step.

What happened here ?? we added link to our JavaScript function in content editor web part in homepage. While loading content editor web part in loading page phase, java script function will be called to popup our window in loading page.

JavaScript Code:

 

<SharePoint:ScriptLink ID=”ScriptLink1″ Name=”sp.js” runat=”server” OnDemand=”true” Localizable=”false” />

 

<script type=”text/ecmascript”>

 

ExecuteOrDelayUntilScriptLoaded(ShowDialog, “sp.js”);

 

function ShowDialog() {

        var options = {

            url: ‘http://PSDEMO/_layouts/POPUPWINDOW/POPUPWINDOW.ASPX&#8217;,

                        dialogReturnValueCallback:CloseCallback,

            height: 500

        };

 

        SP.UI.ModalDialog.showModalDialog(options);

        }

    function CloseCallback(result, target) {

     if(result==SP.UI.DialogResult.OK)

     {

       window.location.href=’http:// PSDEMO /Pages/Polls.aspx’

     }

        if(result==SP.UI.DialogResult.cancel)

     {

      

          SP.UI.ModalDialog.commonModalDialogClose(SP.UI.DialogResult.cancel,’cancel Clicked’);

     }

       

    }

 

</script>

 

4-     Upload java script file to any document library

5-     Then add link to JavaScript file in Content editor webpart.

6-     Then click apply and ok , u will see popup window in loading.