I have a sharepoint page created and it works fine on local as well as on sharepoint ,problem is that after some days page goes down and we could not perform the operations which it intended to be ,but if i upload the same page again it works fine can any one tell me whats the problem
Related
I have created a SSRS report in SharePoint and its uploaded in to the SharePoint library. While running, its working fine. It taking less than 10 seconds to load the report. But If I kept the report in idle mode for the next 5 minutes, then I tried to enter the text in search box in report tool and then clicked find. But instead of displaying the result, it loads the report again. And If I pass the search criteria, it will works. So My assumption is that, it would be the problem of time out. So can you guys advise me where can I update the time out value to avoid this issue?
If this is SSRS SharePoint integrated mode I guess something should be available in Central Admin to which usually developers might not be having acces atleast in prod environment. Check with the administrators who manage your farm.
I used the Azure portal to install an instance of Umbraco.
I need to use the Umbraco forms for a simple contact form.
The Umbraco instance contains the forms and I can perfectly create and configure everything I need about forms (fields, workflows, ...).
Problem is that I can't get to have it on any page.
The video here shows how to do it but when I click on the button as shown 23 seconds in the video, I can't find the forms and therefore not add my forms.
I tried to add the Razor line that it seem to generate based on the guid I get on the Form configuration page but when I save, the online page (I mean, the page of the actual website) is crashing (Yellow asp.net error page).
Does anybody knows what is going on here?
EDIT: Maybe I should mention that I did click on the Install button in the Forms section and waited until it refreshed the page. Surprisingly, it continues to prompt for installation now.
I found the answer.
Seems like when we installed Umbraco at first on Azure, the auto install failed at taking the database into account.
We had to manually edit the config file to make sure everything was all right.
However, some bits for the Forms were not referenced properly.
So I uninstalled the forms completely and reinstalled them from scratch and it started to work fine.
I've built a custom SharePoint 2010 web part and deployed it to the home page of a publishing site. It's a very simple web part that just displays items from a SP list in a drop down list. The web part works fine if I'm logged in as a site owner or a member but not if I'm just a reader. The web part doesn't render at all to readers. I don't get any of the web part chrome or title, just nothing. I have other web parts (out-of-box ones) in the same zone that are displaying fine so it's not an issue of the whole zone not displaying.
As a reader, I can still view the list directly so it doesn't appear to be a problem with list permissions.
My web parts are being deployed as a farm solution, not sand-boxed and the assembly is being deployed to the GAC.
I feel like I must be missing something simple here but I'm stumped. Help.
Did you save / Check in the page after editing?
Regards,
Faiz
You may have to actually publish the page for a reader to see it
i create a website on my local machine but i can't add webpart to web page, it don't rise any error but th webpart don't display to the page. anyone help me.
Thanks
I know this is an old question, but it's ranking high in Google results, so I figured I'd answer it anyway.
Make sure you're not running any code in the layout page's codebehind that calls and then closes SPContext.Current.Web. I had this exact behavior and that was the culprit
To test, add a different web part to a default page layout. If it adds, then it's either your web part or your code behind. If you can't add any web parts to your custom layout, it's your code behind. If it's just your web part, it's your web part.
Remember, SPContext.Current.Web returns a reference to the current SPWeb object. SharePoint will close the object itself when it's done, and closing it early can cause "unpredictable behavior."
We had the same problem with Firefox some time ago, but the problem disappeared when we installed SP2 for SharePoint 2007. The only thing that surprises me is that you also have the problem with IE.
I have a custom feature which adds a few controls into the AdditionalPageHead DelegateControl. This works fine on any sites which use our default.master. However the project requires the use of a publishing site which has a master page derived from BlackBand.master (which does not have the AdditionalPageHead DelegateControl included), so I made a copy of the master page from the master page gallery on the appropriate site collection and then modified it to include the following line:
<SharePoint:DelegateControl
ID="DelegateControl1"
runat="server"
ControlId="AdditionalPageHead"
AllowMultipleControls="true"/>
This should therefore include this DelegateControl within all pages using this master page. However when this is uploaded as a new version of BlackBand.master and approved as such, all the pages in the site that use it get a 404 error as if they no longer exist. If I restore the previous version of the master page then everything return to normal.
Help is appreciated as always.
The answer was that I was approaching the solution to my problem incorrectly.
To fix this I opened SharePoint designer at my site collection root and clicked on _catalogs/masterpage. Then I made a copy of BlackBand.master in the masterpage catalog. Opened it and added my line of code. Saved it and then set it as my default and custom master page (to ensure that it applied to any straight up web part pages as well as layout pages).
This worked without a problem.