sharepoint server 2019
21 TopicsSharePoint Server 2019 Problem uploading and downloading documents with "form " in file name
Just wondering if anyone has seen this issue using SharePoint Server 2019. Users are getting an error "Sorry, there was a problem uploading this file. Please try again." when uploading documents with the word "form " as part of the filename to a document library. It's actually failing on any file name ending in "form ", so "transform ", "approval form - part I", "Form 111", etc. If I rename to "approval form-part I" (no spaces), then it will work. As long as the word "form" is not followed by a space character, it works. I'm sure "form" is not a reserved word but see nothing in the ULS logs to indicate what the error could be from. This happens on both .doc, .docx and PDF files. Does anyone know what may be causing this? I just recently began work on this site and know that it was migrated from SharePoint 2016 to 2019 recently. Also, if I switch to "classic view" on the document library, I can upload it, but not in modern view. Thanks for any input. ThaoSolved7.5KViews0likes3CommentsEvent Receiver in SharePoint 2019
Hello Guys, I am using SharePoint 2019 on-prem , Is it a good idea to use event receivers or it is going to depreciate from SharePoint. I am asking because I have created an event receiver but with modern experience and it is working as expected. But some weird things like it is not showing via Powershell. I have created it for Item added, Item adding or Item Updated. But nothing is showing. And also it is triggering for other lists and library even I am using ListUrl="Lists/listname" and correct scope. So my question is Is is good practice to use event receiver in SharePoint 2019 on-prem modern SharePoint site or someone can also help me to understand the why event receiver is weird in SharePoint 2019 modern site.5.8KViews0likes3CommentsApp launcher missing from from Modern Communication site collection in SharePoint 2019
The App launcher, settings cog and user profile info is missing from the nav-bar across the top of my Modern Communication & Team sites All classic sites are just showing the settings cog and User Profile info The only place this is working is the MySites Host web application for OneDrive and the SharePoint Home Page. This is a new SP2019 Standard install with the latest Feb updates applied.Solved5KViews0likes7CommentsRedirect modern search page to classic search center page in SharePoint 2019
Scenario: Consider you have a modern communication site in SP2019 where users perform search. Search query redirects to the modern search page whose look and feel is not the same as classic search page. Few users may not like the new look and feel. You are looking for ways to customize this new look and feel for modern search page. Cause: This is a by design behavior as you cannot customize the modern search page for modern sites in SharePoint 2019. Refer: https://docs.microsoft.com/en-us/sharepoint/search/differences-search-2016-2019 Workaround: Consider you have a classic search center site collection and are exploring options to redirect the search request from this modern search page to the classic search page. You can use below redirection using URL rewrite tool in IIS to achieve the goal. Modern Search page: http://Sharepoint/_layouts/15/search.aspx/sitefiles?q=document Classic search page: http://sharepoint/sites/search/Pages/results.aspx?k=document <rewrite> <rules> <clear /> <rule name="Modern to Classic" enabled="true" patternSyntax="Wildcard" stopProcessing="true"> <match url="*_layouts/15/search.aspx*" /> <conditions logicalGrouping="MatchAll" trackAllCaptures="true"> <add input="{QUERY_STRING}" pattern="*q=*" /> </conditions> <serverVariables> <set name="QUERY_STRING_A" value="{C:2}" /> </serverVariables> <action type="Redirect" url="http://SharePoint/sites/search/Pages/results.aspx?k={QUERY_STRING_A}" appendQueryString="false" redirectType="Found" /> </rule> </rules> </rewrite> Note: Please consider configuring URL rewrites using below article whether its supported or not by Microsoft. https://support.microsoft.com/en-us/office/supportability-of-rewrites-and-redirects-in-sharepoint-2016-2013-2010-and-2007-a74a19f2-a59a-4b39-8be4-ce63e50139fa2.6KViews0likes1CommentSharePoint 2019 with SQL Server 2014 SP1
Can SharePoint 2019 use SQL Server 2014 SP1? https://docs.microsoft.com/en-us/sharepoint/install/hardware-and-software-requirements-2019 lists Minimum requirements for a database server in a farm One of the following: Microsoft SQL Server 2016 RTM Standard or Enterprise Editions Microsoft SQL Server 2017 RTM Standard or Enterprise Editions for Windows SharePoint Servers 2016 and 2019 Databases technical diagram seems to suggest SQL Server 2014 SP1 can be used http://download.microsoft.com/download/7/9/7/79700E8E-9896-4657-B9E6-4940B295B71A/DBrefguideSPS2019_tabloid.pdf2KViews0likes2CommentsSharePoint Server 2019 Setup cannot continue because a required file is either corrupted or not avai
Hi I am trying to setup SharePoint Server 2019 volume license, noting that all prerequisites were installed successfully, i get the following error: Setup cannot continue because a required file is either corrupted or not available. Run Setup again from the original source disc or download location. Please Help and Advise. Regards. Najeeb Hajji2KViews0likes0CommentsSharePoint 2019 Home Page - Search Query Returns 401 Unauthorized
Hello, When working with SharePoint 2019, executing a Search query from the SharePoint Home/Start Page (i.e., sharepoint.aspx) results in 401 unauthorized. This only occurs when setting a Global Search Center URL (which is part of the requirements). See https://docs.microsoft.com/en-us/sharepoint/sites/enable-sharepoint-home-page-in-sharepoint-server-2019-farms for background. We have two hosts: https://home.domain.com https://my.domain.com The former hosts the Global Search Center and the latter hosts the SharePoint Home Page (sharepoint.aspx). If you run a search query, the following request is sent (supposing I search for the value "test"). https://home.domain.com/sites/search/_api/search/suggest?querytext='test'&inumberofquerysuggestions=3&culture=1033&inumberofresultsuggestions=0&fprequerysuggestions=true&fhithighlighting=true&fcapitalizefirstletters=false&fprefixmatchallterms=false&showpeoplenamesuggestions=false If I don't have a Global Search Center URL specified, then the search api query shown above will be sent to the MySites host and all is well. However, in this cross-domain scenario, where my.domain.com invokes the search api call on home.domain.com, it results in a 401 unauthorized response. My OPTIONS request (prior to the GET call) does pass with a 200 OK, so this doesn't appear to be CORS related on the surface; not dismissing any explanations though 🙂 Any advice on this? Have you successfully set this up and seen it work - mysites host calling the search api on a different host (due to having Global Search Center configured) through the SharePoint Home Page (sharepoint.aspx)? Thanks!Solved1.9KViews0likes1CommentSharePoint display error message while opening home page
Hi Sir We have migrated sharepoint 2013 foundation to Sharepoint 2019 enterprise version and the migration went on well and there is no error message. But while opening the sharepoint, it is displaying the error message as shown below. Sorry, something went wrong Could not load file or assembly 'Havivi.SharePointVideoPlayer, Version=1.0.0.0, Culture=neutral, PublicKeyToken=87a631227aaa0363' or one of its dependencies. The system cannot find the file specified. Technical Details Troubleshoot issues with Microsoft SharePoint Foundation. Correlation ID: 5c14869f-c8dc-e055-d97d-8b244621edd0 Date and Time: 22/10/2020 12:27:17 ------------------------------------------------------------- Request you kindly go through and suggest the resolution1.8KViews0likes2CommentsRTL support in Sharepoint 2019 server communication site search page
Hi, We built a communication site collection on Sharepoint 2019 Server platform. The site collection's langauage is Hebrew. The language of the browser and the operating system is Hebrew, too. All pages are right-to-left, like a mirror display of the LTR version, except for the search results page: People results are displayed before sites and documents results (in RTL display, they should be located on the left side of the screen). "Show all" link at the serach results section is displayed at the right side instaed of the left side, under the section title. Result thumbnail picture is located on the left side of the text (should be on the right). What can cause this problem? Is there a known issue with RTL support on sharepoint OOTB search results page? Thanks, Rumi1.6KViews0likes0Comments