Hot answers tagged

5

You can choose any of the 3 options from below. Option 1: Replace the default PageNotFoundError.aspx in the Page Library – One of the easiest and Convenient way to replace default text in PageNotFoundError.aspx is to either edit the PageNotFoundError.aspx that resides in the Page Library or to delete it and replace it with a Custom error Page that has the ...


3

With the peace of the mp you provided what I can see is that it is 99% equal to oslo.master. The main difference is that you removed all security trimmed controls, which should not affect in this case. I cannot tell what is going on, I don't know how you deploy the masterpage, so if you have a composed look, difficult to say. So if you want to reset the ...


3

Judging from what the console is saying, it seems that the method RTE.Canvas.checkCurrentFocus fails because the element passed is null and the method doesn't expect it to be, so you get an error when it tries to call null.parentElement since parentElement is not a valid property of the object. Searching on Google it seems to be a issue several others are ...


3

On the impacted FE, run: psconfig -cmd applicationcontent Reference: https://technet.microsoft.com/en-us/library/cc263093%28v=office.14%29.aspx


3

Some notes that may help here: A solution is first added (installed) and then deployed. To remove a solution, you must first retract it, and then uninstall it. A solution can be deployed either globaly or on a Web app basis (depending on its content, so it's not your call, but an inherent property of the WSP). If you retract a solution deployed on a Web ...


2

Although all the servers "Installed Window update" shows patches were installed, it is not fully propagated in SharePoint binary. By checking in Central Administration > Upgrade and Migration > Check Product and patch installation status (/_admin/PatchStatus.aspx), I found our WFE1 and APP1 contains some updates Missing/Required highlighted in red color. ...


2

My 100% uncustomized OOB Team Site shows all those too. I've opened /_layouts/15/viewlsts.aspx page, set up Fiddler and it seems this one response from login.live.com is causing the described error being logged: Response has X-Frame-Options: deny header. Citing a post at IEInternals: If the X-FRAME-OPTIONS value contains the token DENY, browsers will ...


2

Several people ran into the issue that list views stop working after installing MS16-004. The security fix contains a code change which requires as well an update to the not localized and to the localized files of the SharePoint foundation component. Localized and not localized file are installed through two different msp files and the security fix package ...


2

It looks like at some point, you tried to configure Workflow Manager to work with SharePoint (so you can create/deploy/use 2013 mode workflows). To do so, you set up Workflow Manager (a dedicated -free- product) and then connected SharePoint to it. Workflow Manager generally sets up on http://<WFserver>:12291/, where WFserver is the Web server you ...


2

Your patch levels are different. Install May 2015 CU or MS15-046 to the production server, depending on what was installed in dev/test.


2

You can enable check-out on the library. So you could control the lock by yourself, as in check-out when you are modifying the document, and check it in once you are done.


2

The solution I came up with is a temporary fix. I created a shell script to retract, remove and redeploy the solution. So at first I would have a dedicated location to publish my .wsp file than a script using the new .wsp. Script is given below: $webApplicationUrl = "http://my-dev/" $siteUrl = "http://my-dev/site1" $solutionName = ...


2

Resetting the environment with an iisreset did the job.


1

I have found a workaround, but I still don't know what caused it. If I edit the workflow and have it write tasks in a "new task list", my issue is resolved.


1

Install the RTM version of SharePoint Server 2016. The message that you're receiving is pretty clear -- the product has expired.


1

I figured it out! I had to go into infopath->File->Form Options->Advanced->Edit Default Values->and uncheck the field causing the validation error->press OK->republish the form.


1

looks like you have some kind of solution deployed to this web app. you should check this Go to Central Administration>Operations>Solution Management .Here you can check whether there are any solutions deployed on the web application. if there is any, please remove it from the web app. from central admin check if there is any timer job running for ...


1

Get rid of the SPServices calls and it will work. You don't need them. Get the current user from the "Welcome" text on the page, instead. // Default the Requestor's Name var welcomeText = $('[id*="zz8_Menu"]').text(); // this is zz7_Menu in SP 2007 var user = welcomeText.split('Welcome ')[1]; var counter=0; $('div[title="People Picker"]').each(function() { ...


1

This was an issue with the SharePoint Database. We restarted the services and the Database and it started working fine.


1

Xavi's link should answer your question. Also here is PowerShell to set your page not found URL: $spsite = Get-SPSite "Web site URL" $spsite.filenotfoundurl $spsite.filenotfoundurl = "/sites/yoursite/Pages/PageNotFoundError.aspx"


1

Make sure to add the name of an existing application pool, the one from the TechNet article is just an example that should be replace with an existing one. To get a list of the application pools in your environment you can use Get-SPServiceApplicationPool detailed here: https://technet.microsoft.com/en-us/library/ff607544.aspx


1

Looks like this is your hardware related problem, You are running into the capacity issue. easy fix is increase the memory(ram) on the WFE to get the better result. You can monitor your WFE while all users hit the sites, check how CPU behave, how Memory behave, Hows the DB server respond. check this: ...


1

What you can do is: Create a page, with Content type of "Error Page" , which is now available in SharePoint 2013. Delete out of the box Page not found error page. Rename newly created error page with same name as default.


1

I see you are accessing personal sites of your users. Do you have access to them, e.g. when you paste in the browser https://tenantname-my.sharepoint.com/personal/firstname_lastname_tenantname_com? If not, you can temporarily assign yourself as the site admin for the users, using Set-SPOUser admin@tenant.onmicrosoft.com -Site ...


1

from Central admin, You Cannot back up directly to tape. The backup location must be a UNC path or local drive. But if you have load balanced Central admin( means hosted on multiple servers, by default it is hosted on one server), then you can select either server. or create the UNC path and it will place the backup over their. Choose backup and recovery ...


1

Your WebPart has error's, check the ULS logs, it Says ystem.NullReferenceException: Object reference not set to an instance of an object. at WebPart.CreateChildControls() and so on. You add your webpart in a test Page, and Then attach the (W3Wp)worker process to debug the code, Attach the breakPoint on Load and OnInit method, Then start debugging you will ...


1

The problem is fixed after I restarted the computer, such a shame I didn't try that earlier. I'm still unsure about the cause of the error though.


1

In order to make a lookup column work for a user with contribute permission level on one list, that same user need to have at least read permission level on the list to lookup. Probably, this is a system list which is intended to be used for functionality rather than content. To save admins from unintended edits, the permission inheritance was broken on the ...


1

I am not sure if this is recommended solution or not but I guess the the installer is trying to run the executable C:\Windows\System32\ServerManagerCMD.exe 2014-09-03 23:45:23 - "C:\Windows\system32\ServerManagerCmd.exe" -inputpath "somepath" Taking a look in the system32 directory, you'll see that in R2, ServerManagerCMD.exe doesn't exist! Source: Server ...


1

Add below code in OnInIt event of web part, if (Page.Request.Browser.Type.ToUpper().Contains("SAFARI")) { ScriptManager sm = ScriptManager.GetCurrent(this.Page); if (sm != null) { sm.EnablePartialRendering = false; } } Build and deploy. It fixes your issue :)



Only top voted, non community-wiki answers of a minimum length are eligible