Gear -> Add page give modern page when modern is disabled
Hi SharePoint Server Subscription Edition. We have a classic team site STS#0 with Modern disabled at site level: $site = Get-SPSite http://spwfe #Disable modern Lists and libraries at the Site Collection Level $featureguid = new-object System.Guid "E3540C7D-6BEA-403C-A224-1A12EAFEE4C4" $site.Features.Add($featureguid, $true) If we go to site pages and click "New page" we get a classic page. If we click "top ribbon gear" icon -> "Add a page" we get a MODERN page. How do we disable that so we get a classic page
Styles Button Disabled for Tables in Enhanced Rich Text Column (SharePoint 2019)
Hi, In a SharePoint 2019 on-premises environment, the issue arises when a column of the type "Multiple lines of text" is created in a list with the setting "Enhanced rich text (Rich text with pictures, tables, and hyperlinks)." After adding a table to the column field, the "Styles" button under the "Design" tab is found to be disabled. Could this be a bug in SharePoint 2019? Regards, Adam
Sharepoint excel file wont stop loading
Hi guys. Is it just me or is everyone facing a problem with Sharepoint excel files constantly just loading and not opening? My company runs on the sharepoint excel file and we cant access it suddenly since yesterday. It just says loading and wont stop loading and then it says it cant be opened. Any solutions?
Status Change tracker
#Sharepoint Hello, I have a list with a column " Status" . We have "open" " rejected" " sent to vendor" " closed" Can we track the status changes in Sharepoint and measure how long it takes for each case from the " open " to the "closed " status? We would like to measure performances if this is possible. Best Regards GD.
SharePoint On Premises Farm Restoration Question:
my unofficial supervisor broke the farm: I asked him to copy over a production content database to the test SQL Server we were using for the new farm I was building out. He accidentally overwrote the SharePoint 2016 Configuration database. His remedy: he used a database snapshot to restore the database to a point in time. He also may have restored the CA server to near that same point in time. Now, we have had several issues: patches that were installed show as not installed. the farm server went from "No action required" to "Needs Installation" The Search Service App won't communicate on port 808, even though it's open. The Search Service App was re-provisioned and the same symptoms persist. I believe that our issues are the result of this "restoration method" my supervisor employed. Can someone provide some concrete reasoning why the restoration method wouldn't work? I've explained that it severs the ties between the farm features and the configuraiton database. But it would be great to have a more expansive explanation.
Tahoe Server
25 years ago, I was a Windows Admin in Austin, TX at a place called Vignette (bought by OpenText years later). Back in the day, if you were Windows admin, you likely had an MSDN subscription with Microsoft. If so, every so often, they’d send big plastic cases filled with CD's including lots of their software, Windows versions, SQL, Exchange, etc. They’d send pre-released software sometimes. I remember pulling a “Tahoe Server” CD out of the case, installing it one of our dev servers & standing up Vignette’s first instance of SharePoint (circa 2000). That same night, I found a feature in the interface for indexing PDF’s. I made a ‘site’ for their legal department & pointed the PDF indexer at a folder that had thousands of PDF legal case files. By the next morning it was fully indexed, and I sent an email to the legal team with link to the site. They began working much faster than they’d ever done before. It was like having Google for all their legal cases where previously they’d manually dig through one PDF at a time & even print paper and hire people to read to find, highlight, review, etc. Several months later, I received a call from the CIO in the middle of the night. “Tyler, this is John C. That tool you setup our legal dept. is offline, and they need it back up ASAP!” I drove an hour into the office (cause that’s what we did in those days) and discovered that ‘Tahoe Server’ had expired. I was on the phone with Microsoft until long after the sun rose, migrating the Tahoe database to a fully licensed & officially titled “SharePoint” server. Lessons learned: PDF Data Extraction. SUPER POWERFUL!! Don’t put pre-released software into production… unless you’re prepared to suffer the consequences. Share the story someday.
