quinn johns

If attempting to utilize Site Manager, to COPY an entire site or any particular pages, and receive the following error. The current operation could not be completed. Try again, or contact your system administrator. You may re-try the operation, and you may need to clean up the half-created data first before re-trying. If the problem persists, please contact your system administrator. If you review the logs, and the following is displayed, System.ArgumentException (0×80070057) Microsoft.SharePoint.Library.SPRequestInternalClass.GetMetadataForUrl(String bstrUrl, Int32 METADATAFLAGS, Guid& pgListId, Int32& plItemId, Int32& plType, Object& pvarFileOrFolder) at Microsoft.SharePoint.Library.SPRequest.GetMetadataForUrl(String bstrUrl, Int32 METADATAFLAGS, Guid& pgListId, Int32& plItemId, Int32& plType, Object& pvarFileOrFolder) at Microsoft.SharePoint.SPWeb.GetFileOrFolderObject(String strUrl) at Microsoft.SharePoint.Publishing.CommonUtilities.GetFile...

Without writing code, you can populate User Profile Service (UPS) information into your fields in InfoPath forms. This process is clearly defined in the following  blog . However, as this works perfectly, in the classic-based authentication there are several modifications that will need to be made, to fully utilize the forms, as a result of product limitations caused by Claims-based authentication. Firstly, a Secure Store ID will need to be created in Central Administration (Manage Service Applications), you’ll need to assign the Target Application ID, and add the Target Application Administrators which would ideally need to be a generic ID that never expires, and the members that are mapped to the credentials defined. You’d need to then set the credentials on that domain account for the secure store target application. Lastly, under Central Administration (General Application Settings), and InfoPath Forms Services, the option to ‘Allow user form templates to use authentication ...

If you've ever encountered the need the disable themes on a site collection, there are a few options you may have available. Firstly, there are policies in Central Administration to remove the ability to change the themes across the entire web application, which can be done by the following: Visit Central Administration > Application Management > Web Applications > Manage Web Applications. Select the Web Application that you want to restrict the themes on. Click on "Permission Policy Level" on the Ribbon. Name the policy, and find the permission "Apply Themes and Borders" and toggle the "Deny" check box. Click save. Click on "User Policy" on the Ribbon. Add the users and groups you want to restrict, and then apply the policy you just created. Alternatively, if you want to manually remove the themes, you can update the theme entries, in a file called: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\...

Issue: If you're encountering the following error, when trying to run a powershell script, you may not have sufficient permissions on the database. Get-SPWeb : Cannot access the local farm. Verify that the local farm is properly configured, currently available, and that you have the appropriate permission to access the database before trying again. The issue can be remedied with a few quick powershell commands. Workaround: Perform the following script in the SharePoint Management Shell, as a farm administrator and it will remove the error. Get-SPDatabase | Add-SPShellAdmin SomeDomain\SomeUserName This will grant the user both access to the configuration database as well as the content database. Alternatively, you can revoke that granted access with the opposite command. Get-SPDatabase | Remove-SPShellAdmin SomeDomain\SomeUserName

Issue: On some library views when you drop down the edit control block (ECB) you will see the following error. This item is no longer available. It may have been deleted by another user. Click 'OK' to refresh the page. To resolve this issue it is necessary to re-create the library view. Workaround: On the library with the view issue, go to "Library Settings" and scroll to the bottom of the page. Click on "Create View," choose to start the view from an existing view, be sure to select "Make this the default view." Choose to create the new view from the view that is having the issue. (e.g. Versions). When creating your new library view, choose any name you please. If you are replacing the default view, be sure to select "Make this the default view." Be sure to make it a public view and keep all other settings to duplicate the other view, and click "OK".

When operating on a hosted or Office 365 Dedicated (including BPOS-D) environment, you will need to utilize MSOCAF to both validate your code, do a test deployment, and submit to Microsoft. With the following cmdlet, you’ll need to set two environmental variables, CAF_ANALYSIS_ROOT_PATH, CAF_SHORTCUT_PATH. Basically, this MSOCAF cmdlet, allows you to simplify the process of testing individual solutions during your development cycle. This cmdlet will copy the files to the necessary location and launch MSOCAF directly. @echo off SET WSP=SolutionName.wsp SET PDB=SolutionName.pdb SET CAF_ANALYSIS_ROOT_PATH=%CAF_ANALYSIS_ROOT_PATH% SET CAF_SHORTCUT_PATH=%CAF_SHORTCUT_PATH% @echo on @echo. cls @echo. @echo Clearing Solutions artifacts folder… rmdir /s /q %CAF_ANALYSIS_ROOT_PATH%”\Caf Reports” rmdir /s /q %CAF_ANALYSIS_ROOT_PATH%”\Solutions artifacts\” md %CAF_ANALYSIS_ROOT_PATH%”\Solutions artifacts\” REM del /q %CAF_ANALYSIS_ROOT_PATH%”\Solutions artifacts\*.*” @echo. @echo Copying fil...

This script allows you to to deploy to your on-premise SharePoint farm or local VM with relative ease. Unless, you want to use powershell. @echo off SET WSP=SolutionName.wsp SET URL=http://SharePointServer @set PATH=C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN;%PATH% @echo on @echo. cls @echo. @echo Begin deploying %WSP% @echo. @echo display solution stsadm -o displaysolution -name %WSP% @echo schedule the retraction of the solution stsadm -o retractsolution -name %WSP% -immediate -url %URL% @echo execute the retraction timer job immediately stsadm -o execadmsvcjobs @echo delete the solution from the solution store stsadm -o deletesolution -name %WSP% @echo add the solution to the solution store stsadm -o addsolution -filename DeploymentFiles\%WSP% @echo schedule the deployment of the solution stsadm -o deploysolution -name %WSP% -immediate -allowgacdeployment -force -url %URL% @echo execute the deployment timer job immediatelystsadm -o execadmsv...

If you are using the following code: SPWeb web = properties.OpenWeb(); and are getting the following error: Call to Microsoft.SharePoint.SPItemEventProperties.OpenWeb() on Sharepoint 2010.  Use Microsoft.SharePoint.SPItemEventProperties.get_Web Property instead. You will need to update the code to the following, and it should remedy the error: SPWeb web = properties.Web;

If you ever get the following warning through the MSOCAF Wizard, Disposable type not disposed Microsoft.SharePoint.SPWeb modify the the following contents: using (SPSite _SPSite = properties.Feature.Parent as SPSite) { using (SPWeb _SPWeb = _SPSite.RootWeb) { ... } } to the following: using (SPSite _SPSite = properties.Feature.Parent as SPSite) { SPWeb _SPWeb = _SPSite.RootWeb; ... } as no explicit rootweb dispose is required. Alternatively, you could also do, SPWeb _SPWeb = SPContext.Current.Site.RootWeb;

When attempting to install NewsGator into a SharePoint 2010 Farm Environment, you may encounter the following error, when the installer checks the SharePoint version: Unable to access the farm. To resolve the error, make sure your account is logged into an account that has access to the SharePoint Farm SQL instance, as well as, a SharePoint Farm Administrator role.