I have developed a site, took a back up on the development site. I have created a empty site on the live environment. I have restored the blank site from the backup.
I need to change some parameters of the webpart. could anybody suggest me what those list of parameters as I have the following error.
Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Windows SharePoint Services-compatible HTML editor such as Microsoft Office SharePoint Designer. If the problem persists, contact your Web server administrator.
Many Thanks
Backup/restore in SharePoint doesn't include custom solutions (wsp file) which means you need to deploy them manually using stsadm tool. See example below:
stsadm -o deploysolution -name webparts.wsp -allowgacdeployment -immediate -url http://localhost
Related
I was not able to log into the website configured in Sharepoint 2010 due to this error message.
"The trial period for this product has expired"
The log shows that:
Exception thrown while adding control
'Microsoft.SharePoint.Portal.WebControls.SearchBoxEx'
Microsoft.Office.Server.dll
I wasn't able to access any pages in the website other than the site settings page.
I am using Sharepoint Enterprise edition. Please help me to remove this error and to continue the work
Microsoft.sharepoint.portal.dll is used in two features of Sharepoint, they are OSearchBasicFeature and OSearchEnhancedFeature. To fix this issue if you are not using the Search feature you can uninstall these features by
stsadm -o uninstallfeature -name OSearchBasicFeature -force
stsadm -o uninstallfeature -name OSearchEnhancedFeature-force
This will fix the issue :)
Just run the SharePoint 2010 Products Configuration Wizard again. It will solve the error in most of cases.
Other possible causes are AntiVirus program updates or some service pack installation.
Sometime even if Central Administration site’s application pool is running under Network Service account instead of the farm administrator account cause this. In that case just change the application pool identity to the Farm administrator account. You can do this either through the Service Accounts section of Central Admin or through the IIS.
Have you recently applied a service pack to your SharePoint site. I remember this issue happening before when Microsoft released SP1.
Please check the "Manage servers in this farm" (/_admin/FarmServers.aspx) and see if there are pending updates to be applied.
Also
http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/08bdfc4d-f83f-4a74-b53e-b70d91047015
I know its a bit late now however this seems to be an incorrect error
message being thrown.
To resolve simply run stsadm -o activatefeature -name
PublishingResources -url http://
I have a custom webpart for Sharepoint 2007. I am trying to deploy it to a new Sharepoint web application. I am using WSPBuilder with VS2010 to do the deploy. When I examine the wss\VirtualDirectories\ folder for the web app, the wpcatalog folder does not exist there. When I go to the Web Part Gallery and click "New" button, the web part is no there either. What could be causing this behavior? Are there any other ways to troubleshoot it?
Thanks.
the wpcatalog is actually a document library containing the .webpart definition files. It is stored in the content database, not the file system.
You need to verify the solution is in fact deployed to your web application, and then activate any features if necessary. You can verify the solution deployment under central administration\operations\solution management.
I have created a feature, a publishing site, in Visual Studio to MOSS - this feature contains a masterpage, some pages, some site columns etc. I have also created a site collection based on my template.
I have several times updated my mastepage and pages with succes. Now I want to update my site columns, adding some columns, but these changes does not appear in my site collection. If I delete my site collection and create a new the new one gets the correct site columns. What am I missing in my update?
I am using WSPBuilder to build and update my feature.
When you deploy your updated package are you deactivating and reactivating the Feature that provisions the site columns? If you don't, the site columns won't show.
There is no way to include this is the wsp, you could however script the deployment of the .wsp and after it has been deployed (i.e. retracted old version, added new version, then deployed to correct web apps) include an
stsadm -o deactivatefeature -url URL -name FEATURENAME
and
stsadm -o activatefeature -url URL -name FEATURENAME
In the deployment script after all the stsadm calls to deploy the solution.
I have created a wsp package and add it to
Central Administration > Operations > Solution Management
using the addsolution command of stsadm. When I click on the Deploy Solution menu, it transfers me to deploy to the solution page. In this page, in the "Deploy To?" section, it shows me a dropdown list with entries like 'All Content web Applications'.
I want to deploy my solution globally so that it is applicable to all new web applications created after the deployment. I have seen WSPs for which "Deploy To?" section shows only a message like "This solution deploys globally" and no dropdown list.
"Globally deployed" only applies to WSP files that don't have web controls and web parts in them. These cannot be "Globally deployed", because the web.config of the web application you choose to deploy to is changed, i.e. entries are inserted in order to register your .dll's containing web controls and web parts.
I think you need to install it into the GAC - However here's a more informed answer:
C:>stsadm.exe -o deploysolution -name
MossSolution.wsp -immediate
-allowgacdeployment
this will deploy it globally. i will
check some time later for
allcontenturl. i have couple of batch
files to deploy WSP files at some
customers. i will check them to see
again in which scenario we used
allcontenturl. but my above reply
about not specifying a URL is correct
that in case when WSP contains only
dll for GAC, you should not specify a
URL.
from this thread on the social.msdn.microsoft.com forums
I need to disable access to a SharePoint application between 6 PM and 7 AM. SharePoint 2007 doesn't seem to have an out-of-the-box "maintenance mode," so I'm looking for a solution. Presently someone moves users out of a security group to limit access to the application, so in the very least, automating that process would work.
Is there a PowerShell script or SharePoint feature or something I can add to my server to enable a maintenance mode for an application? Perhaps sample code for an SPJobDefinition?
you could automate the removal of users in a bat file with the
stsadm -o userrole -url <url> -userlogin <DOMAIN\name> -role <role name> [-add] [-delete]
Check out this link for a way to enumerate sharepoint with Powershell:
link
An IIS method is to restrict access by IP address. I've used that before successfully and it should be quite easy to write a PowerShell script to do it or use the IIS admin scripts.
I'm not aware of SharePoint methods that do this. There is the quiescefarm stsadm command but that applies to InfoPath forms only.
If you want to make the site completely inaccessible, you could write a script to add an app_offline.htm file to the SharePoint site's root directory.
This would prevent anybody from accessing the site, so it might not be ideal if you need to allow admins to login. But it might be a solution if you have a backdoor.