Add aspx page to Page Library / U

I am using SPO-D. I have a need where I have to accept user input and without persisting in SharePoint, pass the information to a web service. Curious which of the following solution options are supported and which is recommended.
1) With Server Side .NET code only no SharePoint code (not an App)
2) Only Client Side JavaScript/JQuery code and no SharePoint code involved (not an App)
3) CAM - Write an App
Thanks for your opinions.
-tp

If you plan to use this for SPO, the server side coding will have limitation
Incase of "Only Client Side JavaScript/JQuery code " it will be unmanaged and difficult to
maintain on a site
If this helped you resolve your issue, please mark it Answered

Similar Messages

Unable to add aspx file to document library using REST and JSOM in SharePoint Hosted App

Hi,
I am unable to add an aspx file to document library. I was actually trying to create a WIKI page and upload to Pages library but that wasn't working so I tried simple document library. It keeps failing with Access Denied error. I have checked
the blocked types and aspx is not included. I can upload it directly from the browser so that shouldn't be the case. I have read that it can be achieved with CSOM but I need this to work with a SharePoint Hosted App. Here is my JSOM:
factory = new SP.ProxyWebRequestExecutorFactory(appweburl);
context.set_webRequestExecutorFactory(factory);
appContextSite = new SP.AppContextSite(context, hostweburl);
oWeb = appContextSite.get_web();
oList = oWeb.get_lists().getByTitle('Documents');
fileCreateInfo = new SP.FileCreationInformation();
fileCreateInfo.set_url("mywiki.aspx");
fileCreateInfo.set_content(new SP.Base64EncodedByteArray());
fileContent = "<%@ Page Inherits=\"Microsoft.SharePoint.Publishing.TemplateRedirectionPage,Microsoft.SharePoint.Publishing,Version=15.0.0.0,Culture=neutral,PublicKeyToken=71e9bce111e9429c\" %> <%@ Reference VirtualPath=\"~TemplatePageUrl\"
%> <%@ Reference VirtualPath=\"~masterurl/custom.master\" %>";
for (var i = 0; i < fileContent.length; i++) {
fileCreateInfo.get_content().append(fileContent.charCodeAt(i));
newFile = oList.get_rootFolder().get_files().add(fileCreateInfo);
context.load(newFile);
context.executeQueryAsync(function () {
alert('yo');
}, function (sender, args) {
alert(args.get_message() + '\n' + args.get_stackTrace());
If I change the file extension to "txt", it works. Same with REST implementation, it works with "txt" but fails with "aspx". Maybe what I am trying to do will not work using JSOM or REST. Any suggestions? Your
help is always appreciated.
Regards,
kashif

Your code works fine in both my on-premises and SharePoint Online. I have given the app full control, so I suspect this is a permissions issue. I would check your permissions on your appmanifest. Must be something to do with publishing permissions. Try
giving full control and work the permissions down.
Blog | SharePoint Field Notes Dev Tools |
SPFastDeploy | SPRemoteAPIExplorer

Using Aspx page insted of default portal page

Hi,
Is there a way to add aspx page in a portal.
After login I want aspx page to display hosted on different domain instead of portal default page.
Thanks in advance.

Oh, I see the misunderstanding. The EXE you talk about is your LV built application - not related to ASP.NET. Okay...
What you want to look up in your LV docs is "remote front panels". This allows you to either embed a dynamically generated image of the VI into the HTML or actually the front panel itself (requires the RTE on the client machine). The second form means the display is interactive. Unfortunately, the only web server supported for this right now is the LV web server. However, you could do some tricks to get the image (option #1 of RFP) from a LV server and then post it up on the IIS server.
For example, you could create a little LV application that uses the IE control in LV to hit the LV web server, grab the page and then save it in the IIS virtual directory.
You other questions...
5. Manage to get your C# code to VB.NET.
I'm not a VB.NET programmer so I can only tell you what you need to do...The PumpMessages dll is C++ so that isn't going to change. To call it from VB.NET, you need to create a DllImport statement. Trying to convert what is in the MSDN sample, it should be something like
<DllImport("C:\Inetpub\wwwroot\MyWebApp\bin\MyLVApp.dll", EntryPoint := "LVDLLStatus", _
   ExactSpelling := True, _
   CallingConvention := CallingConvention.Cdecl)> _
Public Shared Function MoveFile(errStr As IntPtr, errStrLen As Integer, module As IntPtr) As Integer
    ' Leave function empty -
End Function
The other code just calls it. You need to create a VB.NET class with a static constructor (the static Global() in my example), static member (Thread) and static method (ThreadProc).
6. Even though there were few explanations on this area from you this summer , I was not quite clear or to follow  .
Was there any workaround in this area from you on this.
I am not sure what you are asking here..I said of lot of stuff over the summer *grin*, just reply with the specific question
Brian Tyler
http://detritus.blogs.com/lycangeek

How to create a new aspx page in Pages library using Elements.xml without including any aspx page layout in my feature?

Is it possible to have the elements.xml file create a page in the Pages (or SitePages) library without actually including any sort of page layout or aspx artifact in the feature?
I see no reason to add a mywebpartlayout.aspx to my feature just so I can deploy a Home.aspx based on the BlankWebPart.aspx page layout.
I'm sure there is something obvious I am missing with regards to the Elements schema (which is why I've almost given up on using it completely and just gone to pure C#) but
I would really like to do this kind of simple stuff with declarations if at all possible. Must less code to write, debug, test and maintain.

I don't see how my question keeps getting misunderstood. This seems to be very clear and clearly not answered: "Is it possible to have the Elements.xml file
create a page in the Pages (or SitePages) library without actually including any sort of page layout or aspx artifact in the feature?"
I can't be more clear than "without including ANY sort of page layout or aspx artifact (meaning anything ending in aspx) IN THE FEATURE". I am not capitalizing to yell,
only to emphasize. Your disagreement is based on a link that shows ADDING AN ARTIFACT (the dummy MyPage.aspx) to a feature. I am asking if it
is possible (again, I cannot be more clear) to just use an Elements.xml file to instruct SharePoint to make a new item in a Pages or SitePages library.
Your definition of page includes Page Layouts and what you call Web Part Pages (again, a type of page layout + data in a site pages list that says what webparts
to display). Page Layouts are clearly NOT items stored inside of a SitePages or Publishing Pages library. Those libraries are just lists whose records
define the parts to show inside a specific layout.
When I refer to a Page I mean an entry into a pages (site pages/publishing pages) list. If I wanted to deploy a page layout then, quite obviously, I would need
to include it into my solution. I think maybe you are assuming that I do not know the difference. I do. The question is, can an Elements file alone be enough to instruct SharePoint to make a new entry into a Pages or SitePages library.
Now, your second link does show how to reference an existing Page Layout. Thank you for that. It is excellent. But this still leaves the problem of having to
add some sort of aspx page into the solution. Let me try to explain why I feel this SHOULD BE unnecessary: The aspx file will not have anything on it if I am referring to the ~sitecollections/.../BlankWebPartPage.aspx layout.
All web parts and content that should appear on the new page can be described IN the Elements.xml file. Any sort of aspx file is unnecessary, it seems to me.
So, if I am referencing a ~sitecollections/.../BlankWebPartPage.aspx page layout and specifying the web parts to add to the page, why should there be a
requirement to have some aspx file within the feature? That's what I am trying to figure out.
I am not asking for source code as proof. I am asking for an Elements file that does NOT reference anything AT ALL inside the Visual Studio solution for reasons I just described.
If you do not know how to do it then perhaps it cannot be done but I would like the question to stay unanswered for a little while until someone can demonstrate either a) it CAN
be done or b) a link to some Microsoft document stating that it is MANDATORY to have a physical element within the feature that gets copied to the environment.
I think it is important to understand what is being asked before insisting you have answered. It is clear from your posts that you have not fully understood the question yet but
I am hoping this posts makes it clear. I really appreciate you taking the time to respond, though. You seem to be the only one up for the challenge! :)

Unable to add page in Page library of SharePoint 2007 site

The site is not valid. The 'Pages' document library is missing.   at Microsoft.SharePoint.Publishing.PublishingWeb.get_PagesList()
   at Microsoft.SharePoint.Publishing.Internal.CodeBehind.BasePageSettingsPage.LoadValues()
   at Microsoft.SharePoint.Publishing.Internal.CodeBehind.CreatePagePage.LoadValues()
   at Microsoft.SharePoint.Publishing.Internal.CodeBehind.BasePageSettingsPage.OnLoad(EventArgs e)
   at Microsoft.SharePoint.Publishing.Internal.CodeBehind.CreatePagePage.OnLoad(EventArgs e)
   at System.Web.UI.Control.LoadRecursive()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
above error is occuring when trying to add page in Page library through UI.
Office SharePoint Server Publishing feature is active.
Please help to resolve the issue.
Rushikesh_Khadtare

Hi,
Running the below PowerShell script fixes the issue, you need to change the site url. The script actually looks for the pages library in the site for which url is given and assigns the ID of the pages library to the __PagesListId property.
# Load the SharePoint assemblies
[Void][System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint")
$web = get-spweb http://site-collection/path-to-affected-site
$correctId = $web.Lists["Pages"].ID
$web.AllProperties["__PagesListId"] = $correctId.ToString()
$web.Update()
Then try to de-activate and re-activate the publishing feature again.
Reference:
http://www.rjesh.com/2014/02/the-site-is-not-valid-pages-document.html
http://blogs.technet.com/b/praveenh/archive/2013/01/22/running-powershell-on-moss-2007.aspx
Best Regards,
Eric
Eric Tao
TechNet Community Support

Create aspx page without masterpage and add visual webpart into it

Hi
I have to create aspx page programatically and add it to the site pages library of team site.
Requirements for this page are
1) Page should not use masterpage
2) Add a visual web part to this page
3) on feature activation add this page with webpart should be added to site and set this page as welcom page
We are using TeamSite template in our project
Please provide me solutions with examples if possible
Thanks
Bhavin

Hey,
is the visual webpart a custom webpart which is created by yourself or is it a standard webpart such as content editor?
Not to use the masterpage is quite difficult because the masterpage is necessary for several things. As far as I know there is no way to create a page without a masterpage. As a workaround I would recommend to try the "isDlg=1" parameter in the
url. This flag hides most of the elements in the masterpage. As an example it is used by the modal dialog framework. Every page which pops up as a modal dialog (such as the forms of lists and libraries) is a ordinary page (including the masterpage) but it
has the flag in its url. So only the actual content of the page is displayed while the elements of the masterpage are hidden.
Try to set the welcome page like this: http://[webUrl]/SitePages/YourCustomPage.aspx?isDlg=1

I need to add the Description for a field to the dispForm.aspx page

I have some information stored in the description area of a field that needs to show up on the dispform.aspx page. It shows up on the editform.aspx but not dispform.aspx
I know there has got to be a way to do it with some JQuery or something, can someone steer me?
L.

Hi, I know this is an older post but I was looking for the same guidance. I couldn't find it either. :)
So I started working backwards from this command that I know works for displaying the history of the multiline boxes when there are multiple versions:
<tr><td class="ms-formlabel">Comments</td>
<td class="ms-formbody" colspan="3"><xsl:value-of select="@Comments" disable-output-escaping="yes" />
<SharePoint:AppendOnlyHistory runat="server" FieldName="Comments" ControlMode="Display" ItemId="{@ID}"/></td></tr>
So checking out the “SharePoint: AppendOnlyHistory” brought me here:
http://msdn.microsoft.com/en-us/library/office/microsoft.sharepoint.webcontrols.appendonlyhistory(v=office.15).aspx
Which I followed until I found this …
http://msdn.microsoft.com/en-us/library/office/microsoft.sharepoint.webcontrols.fielddescription(v=office.15).aspx
So with some experimenting I found that this works:
<td class="ms-formlabel"><SharePoint:FieldDescription runat="server" FieldName="ESCFReason" ControlMode="Edit" ItemId="{@ID}"/></td>
<td class="ms-formbody"><xsl:value-of select="@ESCFReason" disable-output-escaping="yes" /></td>

Add a page still visible under the gear even Read permissions for the Pages Library

Hi,
Some of the employees have Read permissions on the Pages Library. The permissions have been broken for this Library.
They still see the 'Add a page' action under the gear. So if they want to create a page, SP asks for a page name and then they received the request to get access.
Is it a bug or is it standard?
Thanks,
Christophe

Hi,
I have done a test in my SharePoint 2013 to reproduce your issue, but I can't reproduce the issue.
If the users only have read permission on the Pages Library. They can't see the 'Add a page' action under the gear.
I suggest you use check permission to check the permission for the users, make sure they only have read permission on the Pages library.
Then you can do a test in another library and compare whether the issue is exists. if not, remove the user from the Page library and set read permission for him again.
If the issue still exists, Please offer a screenshot about the issue.
I am looking forward to your reply back.
Best Regards,
Lisa Chen
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Aspx page giving error while migrating to another site

Hi there,
I have an existing aspx page on one SharePoint site. I have created a new site, where I want to move this page.
I have downloaded the aspx page to my local system and uploaded the same to the new site.
But when I click on the page it is giving me the following error:
Error
This
page is not using a valid page layout. To correct the problem, edit page
settings and select a valid page layout."
Troubleshoot
issues with Microsoft SharePoint Foundation.
Correlation ID:
However, on both sites, the page exists on Document library named Pages.
Thanks for your concern.

Hi aquariusabhi,
According to your description, my understanding is that the Page Layouts was missing for a site in SharePoint Designer.
For this issue, there is a common scenario:
You have a subsite in a site collection
The publishing feature is activated in the subsite, but not in the site collection
You want to edit/add page layouts on the site collection level, to be used within your subsite
When you open the site collection in SharePoint Designer, you can't see Page Layouts in the Site Objects panel
You now have 2 options: you can either activate the publishing feature in the site collection (and the Page Layouts link comes back), or you can use the All Files link and browse to the master pages and page layouts library (_catalogs > masterpage.)
Either option will do, unless you really don't want the publishing feature in the site collection.
More information, please refer to the link:
http://www.myspblog.com/2011/04/page-layouts-missing-sharepoint.html
Best Regards,
Wendy
Wendy Li
TechNet Community Support

Question about including JQuery in a Survey list DispForm.aspx page

In SharePoint 2010, I was able to hide the links for editing, deleting... an existing survey entry in the DispForm.aspx page using the following technique:
1 - Save jquery .js file to the Style Library in the top level site
2 - Save the .js file that has the jquery code to hide the link in the Style Library in the top level site
3 - Reference the .js files in the DispForm.aspx page like this:
<asp:content contentplaceholderid="PlaceHolderAdditionalPageHead" runat="server">
<script type="text/javascript" language="javascript" src='<asp:Literal runat="server" Text="<%$SPUrl:~SiteCollection/Style Library/jquery-1.5.0.min.js%>"'></script>
<script type="text/javascript" language="javascript" src='<asp:Literal runat="server" Text="<%$SPUrl:~SiteCollection/Style Library/hideedit.js%>"'></script>
</asp:content>
The hideedit.js file contains the following:
$(document).ready(function(){
$('#ctl00_m_g_d3bec7ca_bd25_448d_8874_da35856854c5_ctl00_ctl01_ctl00_toolBarTbl').hide();
I am trying to use this same technique in SharePoint 2013 but it is not working.
It appears that neither of the js files are loading properly.
As a test, I put the following in the hideedit.js:
alert('test');
$(document).ready(function(){
alert('from jquery');
Neither of the alerts are displayed when navigating to the DispForm.aspx file.
How do I get JQuery loaded in a survey DispForm.aspx file in SharePoint 2013?

Have you tried this within Designer? Copy the DispForm, edit it and add the JD references below the PlaceHolderMain section and then save. Set this as the default Displat Form and your changes should load.
Steven Andrews
SharePoint Business Analyst: LiveNation Entertainment
Blog: baron72.wordpress.com
Twitter: Follow @backpackerd00d
My Wiki Articles:
CodePlex Corner Series
Please remember to mark your question as "answered" if this solves (or helps) your problem.

Title of Page from Pages library not appearing as expected from custom pagelayouts VS solution

hi,
i have created a custom web page from pages library using custom page layouts library with the help of a wsp.
here is my sample page.
now my issue is, when i go to the page / the title of the page is not displaying correctly.
as per my requirement the ttile of the page should be APPROVE/REJECT Doc
which is mentioned in the <title>APPROVE/REJECT Doc</title></head>.
and in my VS 2012 pagelayouts solution i have added this page name approve1.aspx.
hence i am getting the Page title from the pages lib as approve1 .
can someone pls help what should i do to get this title issue resolved.
i cant rename the page again from the solution.i would like to see the title of this page takes from <title>APPROVE/REJECT Doc</title></head> .
<%@ Page Inherits="Microsoft.SharePoint.Publishing.TemplateRedirectionPage,Microsoft.SharePoint.Publishing,Version=15.0.0.0,Culture=neutral,PublicKeyToken=71e9bce111e9429c" %> <%@ Reference VirtualPath="~TemplatePageUrl" %>
<%@ Reference VirtualPath="~masterurl/custom.master" %><%@ Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"
%>
<html xmlns:mso="urn:schemas-microsoft-com:office:office" xmlns:msdt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882"><head>

<title>APPROVE/REJECT Doc</title></head>

Hi,
As there is no complete code at hand, you can take the snippet below about updating the name of a page in a page library as a reference:
if((Get-PSSnapin | Where {$_.Name -eq "Microsoft.SharePoint.PowerShell"}) -eq $null) {
Add-PSSnapin Microsoft.SharePoint.PowerShell;
$web = Get-SPWeb http://yoursite
$list = $web.Lists["Site Pages"]
$listItems = $list.Items
foreach($item in $listItems)
if ($item.Name -eq "Page1.aspx")
$file = $item.File
$file.MoveTo($item.ParentList.RootFolder.Url + "/" + "Page1_changed.aspx")
$file.Update()
#dispose of web
$web.dispose();
Best regards
Patrick Liang
TechNet Community Support

Hidden Report Viewer Confiugration Error on aspx pages that use report viewer web control

I try to fix the problem. The error below is embedded on aspx pages that use report viewer web control. Please note that the div element is hidden, and the reportviewer is displaying correct contents.
Div element hidden on aspx page
<div id="ReportViewer1_HttpHandlerMissingErrorMessage" style="border-color:Red;border-width:2px;border-style:Solid;padding:10px;display:none;font-size:.85em;">
<h2>
Report Viewer Configuration Error
</h2><p>The Report Viewer Web Control HTTP Handler has not been registered in the application's web.config file. Add <add verb="*" path="Reserved.ReportViewerWebControl.axd" type = "Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" /> to the system.web/httpHandlers section of the web.config file, or add <add name="ReportViewerWebControlHandler" preCondition="integratedMode" verb="*" path="Reserved.ReportViewerWebControl.axd" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" /> to the system.webServer/handlers section for Internet Information Services 7 or later.</p>
</div>
I tried adding the two elements to web.config, but to no avail.
Add below to system.web/httpHandlers
<add verb="*" path="Reserved.ReportViewerWebControl.axd" type = "Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
or add below to system.webServer/handlers for Internet Information Services 7 or later.
<add name="ReportViewerWebControlHandler" preCondition="integratedMode" verb="*" path="Reserved.ReportViewerWebControl.axd" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
The required assemblies below are installed under C:\Windows\assembly folder. I have installed both Microsoft ReportViewer 2010 Redistributable, and 2008 SP1.
Microsoft.ReportViewer.WebForms, version 10
Microsoft.ReportViewer.Common, version 10
Below is the whole web.config:
<?xml version="1.0" encoding="utf-8"?>

<configuration>
<connectionStrings>
<add name="ApplicationServices" connectionString="data source=.\SQLEXPRESS;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|\aspnetdb.mdf;User Instance=true" providerName="System.Data.SqlClient" />
</connectionStrings>
<appSettings>
<add key="car" value="myCar" />

</appSettings>
<system.web>
<httpHandlers>
<add verb = "*" path = "Reserved.ReportViewerWebControl.axd" type = "Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />

</httpHandlers>
<compilation debug="true" targetFramework="4.0">
<assemblies>
<add assembly="Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
<add assembly="Microsoft.ReportViewer.Common, Version=10.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
<add assembly="Microsoft.Build.Framework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
<add assembly="System.Management, Version=4.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A" />
</assemblies>
<buildProviders>
<add extension=".rdlc" type="Microsoft.Reporting.RdlBuildProvider, Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
</buildProviders>
</compilation>
<authentication mode="Forms">
<forms loginUrl="~/Account/Login.aspx" timeout="2880" />
</authentication>
<membership>
<providers>
<clear />
<add name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider" connectionStringName="ApplicationServices" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="false" requiresUniqueEmail="false" maxInvalidPasswordAttempts="5" minRequiredPasswordLength="6" minRequiredNonalphanumericCharacters="0" passwordAttemptWindow="10" applicationName="/" />
</providers>
</membership>
<profile>
<providers>
<clear />
<add name="AspNetSqlProfileProvider" type="System.Web.Profile.SqlProfileProvider" connectionStringName="ApplicationServices" applicationName="/" />
</providers>
</profile>
<roleManager enabled="false">
<providers>
<clear />
<add name="AspNetSqlRoleProvider" type="System.Web.Security.SqlRoleProvider" connectionStringName="ApplicationServices" applicationName="/" />
<add name="AspNetWindowsTokenRoleProvider" type="System.Web.Security.WindowsTokenRoleProvider" applicationName="/" />
</providers>
</roleManager>
<pages>
<controls>
<add tagPrefix="ajaxToolkit" assembly="AjaxControlToolkit" namespace="AjaxControlToolkit" />
</controls>
</pages>
</system.web>
<system.webServer>
<modules runAllManagedModulesForAllRequests="true" />
<validation validateIntegratedModeConfiguration="false" />
<handlers>
<add name="ReportViewerWebControlHandler" preCondition="integratedMode" verb="*" path="Reserved.ReportViewerWebControl.axd" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
</handlers>
<httpProtocol>
<customHeaders>
<remove name="X-Powered-By" />
</customHeaders>
</httpProtocol>
</system.webServer>
<system.serviceModel>
<bindings>
<basicHttpBinding>
<binding name="WebService1Soap" />
</basicHttpBinding>
</bindings>
<client>
<endpoint address="http://localhost:58269/WebService1.asmx" binding="basicHttpBinding"
bindingConfiguration="WebService1Soap" contract="ServiceReference1.WebService1Soap"
name="WebService1Soap" />
</client>
</system.serviceModel>
</configuration>
Any idea?
Update:
IIS is7.5, AppPool is Integrated.
I have tried below, none of them works:
1) Add it only to system.web\httpHanders. Changed AppPool to classic, still got hidden error.
2) Add it only to system.webServer\handlers. Integrated mode,still got hidden error.
3) Add both to both element. Integrated mode, still got hidden error.

Hi Kingofwebguru,
According to your description, when you use reportviewer control, you got the error message: The Report Viewer Web Control HTTP Handler has not been registered in the application's web.config file.
To troubleshoot the problem, please refer to the following steps:
Click Start, click Run, then type InetMgr.exe and click OK.
Click plus sign next to server name to expand it.
Click Application Pools in left pane.
In Application Pools list, click DefaultAppPool.
In the Actions pane, in Edit Application Pool section, click Edit Settings to check the Pipeline mode.
Configuration settings for the HTTP handlers are specified in the system.web/httpHandlers element and the system.webServer/handlers element. of your application Web.config file. The handler specified in system.web/httpHandler is used by Internet Information
Services (IIS) 6.0 or IIS 7.0 in Classic mode, whereas the handler specified in system.webServer/handlers is used by IIS 7.0 in Integrated mode. To use IIS 7.0 in Integrated mode, you must remove the HTTP handler in system.web/httpHandlers. Otherwise, IIS
will not run the application, but will display an error message instead.
For more information about Web.config Settings for ReportViewer, please refer to the following document:
http://msdn.microsoft.com/en-us/library/ms251661.aspx
If you have any more questions, please feel free to ask.
Thanks,
Wendy Fu
If you have any feedback on our support, please click
here.
Wendy Fu
TechNet Community Support

Cannot edit properties of pages in Pages Library

We have a site's Pages Library with a problem
If we attempt to edit a pages properties, and save a change to the properties, we will get an error with a correlation id.
the error will read "The URL 'Pages/test9.aspx' is invalid. It may refer to a nonexistent file or folder, or refer to a valid file or folder that is not in the current Web. "
That's if we do the change via the editform view.
If we turn on inline editing on a view of the Pages Library, and we edit properties of a page where the editform view was never used and never caused that error... we can edit the properties at will.
So our quick reaction was that the editform view is corrupted, or somehow corrupts the properties so they can't be edited.
I've tried creating a new editform view in spd... but it appears to cause the same issue.
so looking for ideas on how to root out the problem.

Looking at the logs, just prior to seeing the error text, I do see these lines with the same correlation id
05/19/2014 13:25:24.38 w3wp.exe (0x0B7C) 0x0D04 Web Content Management Publishing 7fz3 Medium Setting [Edit] as the FormContext.FormMode for the current page e1f96b75-c427-4ae4-a02c-cb7edc57be21
05/19/2014 13:25:24.38 w3wp.exe (0x0B7C) 0x0D04 SharePoint Foundation General 27dw Medium Attemping to add or update webpart id 843C9884-ED69-4BC0-B751-2198B0A98670, list <not specified>, flags -1, type -1, base view id -1. e1f96b75-c427-4ae4-a02c-cb7edc57be21
05/19/2014 13:25:24.39 w3wp.exe (0x0B7C) 0x0D04 SharePoint Foundation General 27dw Medium Attemping to add or update webpart id E8DBBE9F-72AC-4097-99D7-4F4D6E33EFE8, list <not specified>, flags -1, type -1, base view id -1. e1f96b75-c427-4ae4-a02c-cb7edc57be21
05/19/2014 13:25:24.41 w3wp.exe (0x0B7C) 0x0D04 SharePoint Foundation General 27dw Medium Attemping to add or update webpart id D8219681-E0A5-4E7F-834A-C0B03EF3AF67, list <not specified>, flags -1, type -1, base view id -1. e1f96b75-c427-4ae4-a02c-cb7edc57be21
05/19/2014 13:25:24.41 w3wp.exe (0x0B7C) 0x0D04 Web Content Management Publishing 7fz3 Medium Setting [Edit] as the FormContext.FormMode for the current page e1f96b75-c427-4ae4-a02c-cb7edc57be21
05/19/2014 13:25:24.41 w3wp.exe (0x0B7C) 0x0D04 Web Content Management Publishing 7fz3 Medium Setting [Edit] as the FormContext.FormMode for the current page e1f96b75-c427-4ae4-a02c-cb7edc57be21
05/19/2014 13:25:24.52 w3wp.exe (0x0B7C) 0x0D04 SharePoint Foundation Database d0d6 High System.Data.SqlClient.SqlException: Parameter '@ntext3' was supplied multiple times. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlDataReader.HasMoreRows() at System.Data.SqlClient.SqlDataReader.ReadInternal(Boolean setTimeout) at System.Data.SqlClient.SqlDataReader.NextResult() at Microsoft.SharePoint.SPSqlClient.ExecuteQueryInternal(Boolean retryfordeadlock) at Microsoft.SharePoint.SPSqlClient.ExecuteQuery(Boolean retryfordeadlock) e1f96b75-c427-4ae4-a02c-cb7edc57be21
05/19/2014 13:25:24.52 w3wp.exe (0x0B7C) 0x0D04 SharePoint Foundation General 8kh7 High The URL 'Pages/tours.aspx' is invalid. It may refer to a nonexistent file or folder, or refer to a valid file or folder that is not in the current Web. e1f96b75-c427-4ae4-a02c-cb7edc57be21

Printing SharePoint 2013 Wiki Page Library as a whole

Hi! I'm trying to find a good solution for printing an entire SharePoint 2013 Wiki page library. In SharePoint 2010 I built a site and created a printer friendly view that used "Wiki Content" column that only printed the contents
of the wiki pages as a whole using the solution from this link:
https://mail.americredit.com/owa/redir.aspx?C=Wl_sVZBaUUqYaSN9F2Qq6Mc3RL-ZwtEIzEWL5ULgM7U6Hr1eoqsoq26BC3E89ofm2Liksb54EjM.&URL=http%3a%2f%2fwww.eblogin.com%2feblogin%2fpost%2f2011%2f11%2f24%2fsharepoint-wikiPagePrint.aspx%23.VDVWdPldVBc
It was very easy to do and my client loved it. However, now that we are starting to migrate over to SharePoint 2013 I don't see the same column option and I haven't been able to create a printable view like the one above. Is there a way
to do this in 2013 like what was available in 2010?

Hi Jeremy,
That link take me through to an Exchange Login. Can you provide another link for the solution you've used.
An older solution that sounds familiar is in this thread. It's for an older version of SharePoint but should still work
https://social.technet.microsoft.com/forums/sharepoint/en-US/1612dfdb-f85c-4e6f-90f4-3d6c24b6472c/how-do-you-print-a-sharepoint-wiki
Steven Andrews
SharePoint Business Analyst: LiveNation Entertainment
Blog: baron72.wordpress.com
Twitter: Follow @backpackerd00d
My Wiki Articles:
CodePlex Corner Series
Please remember to mark your question as "answered" if this solves (or helps) your problem.

Error on modifying the SharePoint excel services viewer (xlviewer.aspx) page

I am working on SharePoint 2013 and am following this
article to modify the xlviewer.aspx page in order to pass into it URL parameters. After following the instruction when I reload the new webpage (MyXLViewer.aspx) I am getting the foll. error:-
Sorry, something went wrong An error occurred during the compilation of the requested file, or one of its dependencies. 'Microsoft.Office.Excel.WebUI.ExcelWebRendererInternal' does not contain a definition for 'RowsToDisplay' and no extension method 'RowsToDisplay'
accepting a first argument of type 'Microsoft.Office.Excel.WebUI.ExcelWebRendererInternal' could be found (are you missing a using directive or an assembly reference?) Technical Details
Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: db9b709c-966c-80de-156d-15c4b2783b09
Date and Time: 2/3/2014 5:15:03 PM
Go back to site
Can you please try this and replicate and let me know if you are facing the same issue..? Or whether I am doing something wrong here? Foll.
is the procedure I have followed:-
Create a copy of XLViewer.aspx which is located in C:\Program Files\Common Files\Microsoft Shared\web server extensions\15\TEMPLATE\LAYOUTS. I named my copy MyXLViewer.aspx. you can try /14/ incase of SharePoint2010..
Open MyXLViewer.aspx in Notepad and do the following;
<%@ Page language="C#" Codebehind="XlViewer.aspx.cs" AutoEventWireup="false"... --> Change This To --> <%@ Page language="C#" Codebehind="XlViewer.aspx.cs" AutoEventWireup="true"...
Placed foll code before head tag closes </head> on
the page:
<script runat="server">
private void Page_Load(object sender, System.EventArgs e)
if (Request.QueryString["RowsToDisplay"] != null)
m_excelWebRenderer.RowsToDisplay =
Int32.Parse(Request.QueryString["RowsToDisplay"]);
if (Request.QueryString["ColumnsToDisplay"] != null)
m_excelWebRenderer.ColumnsToDisplay =
Int32.Parse(Request.QueryString["ColumnsToDisplay"]);
if (Request.QueryString["ToolbarVisibilityStyle"] != null)
if (Request.QueryString["ToolbarVisibilityStyle"] == "1")
m_excelWebRenderer.ToolbarStyle =
ToolbarVisibilityStyle.FullToolbar;
else
m_excelWebRenderer.ToolbarStyle =
ToolbarVisibilityStyle.None;
</script>

Hi,
The article you referenced might be applied to SharePoint 2007, however, in SharePoint 2013, the
RowsToDisplay property and
ColumnsToDisplay property are no longer supported, so these properties are not guaranteed
to work as they were in SharePoint 2007.
If you want to customize the Excel Web Access Web Part, it is recommended to take a look at the two documentations about Excel Web Access Web Part custom properties:
http://office.microsoft.com/en-001/sharepoint-server-help/excel-web-access-web-part-custom-properties-HA010377893.aspx
http://office.microsoft.com/en-001/sharepoint-server-help/excel-web-access-web-part-summary-HA010105454.aspx
Best regards
Patrick Liang
TechNet Community Support
Hello Patrick,
As I have posted in my question I am interested in customizing the Excel viewer aspx page which opens up when you open an excel book via the document library in SharePoint 2013. The solution you are talking about is to modify the properties of the excel
web part and this does not answer my question.
Again, can you tell me if there is any possible way to customize the XLVIEWER.ASPX page sitting in LAYOUTS folder so that I can access certain properties like AllowInteractivity, etc? Or has this been completely discontinued by Microsoft in SharePoint 2013?
If the RowsToDisplay
property and ColumnsToDisplay
property are no longer supported, are there
any other property that this tag supports?
We have opened the xlviewer.aspx page from layouts folder and can see the foll. control:
<Ewa:ExcelWebRendererInternal id="m_excelWebRenderer" runat="server"
AllowInteractivity="false" AllowPivotSpecificOperations="false"/>
However, there is no documentation available from Microsoft or any other dev sites on this control/tag. This
link mentions that the ExcelWebRendererInternal is a totally useless instance.
I need clarification on this.
We also tried to edit the "C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\TEMPLATE\LAYOUTS\1033\ewa.strings.moss.js" file. But, any edits corrupts what is rendered on the right click of the pivot chart/table on xlviewer.aspx
page.

Add aspx page to Page Library / U

Similar Messages

Maybe you are looking for