Send to Record Center crashes (SharePoint Server 2019)
OfficialFile::SubmitFile: Encountered WebException when sending file /Shared%20Documents/1GB.bin to /_vti_bin/officialfile.asmx: The request failed with the error message: -- <html><head><title>Object moved</title></head><body> <h2>Object moved to <a href="/_layouts/15/error.aspx?ErrorText=Exception%20of%20type%20%27System%2EOutOfMemoryException%27%20was%20thrown%2E">here</a>.</h2> </body></html> This starts when the Filesize is larger for round about 350 MB and above. web.config of isapi folder was modified with <location path="OfficialFile.asmx"> <system.web> <httpRuntime maxRequestLength="10485760" executionTimeout="600" /> </system.web> </location>
SharePoint server 2019 - "Send To" in library
Hi All, On SPS 2013 - 2016 there is an option SendTo: https://support.microsoft.com/en-us/office/using-send-to-in-sharepoint-server-3fe1c568-021c-4c6b-a6c2-d55e6a3518de?ui=en-US&rs=en-US&ad=US On SharePoint server 2019 Enterprise edition this option doesn't work even it could be configured: Bellow url is saying only Copy / Move are in concideration: https://support.microsoft.com/en-us/office/move-or-copy-files-in-sharepoint-00e2f483-4df3-46be-a861-1f5f0c1a87bc#ID0EABAAA=Office_2019 Kindly advice if "Send To" has prerequisites in order to work or this option is deprecated. Best regards, Neno
SharePoint On-Premises migration
Hi, I have a question about SharePoint 19 On-Premises migration, I have 2 different SharePoint 2019 On-Premises farms, I need to migrate the documents libraries from one farm to another, the documents libraries its has a huge size its approximately more than 2TB, and it's from a different site collection. What is the best practice or plan to achieve this?
Duplication of extention name SharePoint 2019
Hi everyone, Intro We have a SharePoint 2019 on-prem environment with the CU from November 2019. We have created several of our own SPFx extensions that work good in 2019 and SPO. The same behavior happens as well on our SP2019 test environment which is identical to our production. So what's going on The strange thing is that if a user adds the extension to the site it will take the name of the last extension he/she added. Meaning if you added 3 apps all of them will take the same name as the last one you added. This will make it very difficult to see which apps you have on a site and if a update is available. Any idea or suggestion would be welcome, Regards, Maarten
Can't hide non-default or non-standard ports for SharePoint
I have created a new web application (SharePoint 2019 on Premise) on port 44444 as we already have one web application on port 80. We have two web front servers and I am using F5 for load balancing. To hide port 44444, I used DNS entry (A-NAME record) and created AAM in SharePoint Central Admin to hide ports. On browsing the default site under this web application with user friendly name(http://mblinternal), browser sends response back with port 44444 (http://mblinternal:44444/..) Internal URL Public URL http://mblinternal:44444 http://mblinternal (default zone) Mblinternal is a virtual server in F5 pointing to A-NAME in DNS. I have tried to add binding in IIS for ports with host header as mblinternal at port 80 but no luck. I appreciate if you could point me to the right direction. Thanks
