Posts

How to change the owner of PowerApps

Image
I have seen many blog posts and videos about how to change the owner of a PowerApp. The problem is that all the blogs posts out there (as of 4/21/2020) don't tell you how to change the owner to someone other than the Global Administrator running these commands. Some blogs just tell you there is a command which is supremely unhelpful. So I plan to fix that. Q: Why would you change it? A: In case someone created an app that left the company you want to transfer it. Or perhaps you created the app and you want to transfer ownership of it to a Service Account that will live beyond you. Q: Why not just use the Export/Import process? A: You can, but that is not the point of this article. What you need 1) An Office 365 Global Administrator account and access to Azure Active Directory users portal 2) The App ID and Environment ID (more below) 3) PowerShell Get the details 1) In a browser, login to admin.powerapps.com as a Global Administrator 2) In the Environme

SqlException (0x80131904): profile name is not valid or Error 14607 Procedure: 'sp_send_dbmail'

Image
Recently I needed to patch my SharePoint 2013 on-premises environment with the August 2019 Cumulative Update (CU). After the binaries were installed on my farm, I proceeded to run the SharePoint Products and Configuration Wizard (henceforth, Config Wizard) to complete the process. Inevitably, this is where most SharePoint patches fail, but it usually takes a long time to do so. But this time, the failure was almost immediately, specifically Step 2 out of 10. Symptoms and Error Messages The error message indicated  Exception: System.Data.SqlClient.SqlException (0x80131904): profile name is not valid .  and gives you the link to the error log as shown below. A review of the log didn't really provide any other details. After restarting the necessary SharePoint services, I was able to get back into Central Administration. I increased the logging level to Verbose to try and get more information about the error. Restarting Config Wizard and using a ULS Viewer  to catch the error

Unknown server tag 'AdminControls:MigrationToolPromotionTip'.

Image
I was applying the August 2019 CU for SharePoint 2013 in my Test environment. After installing the binaries, I tried to go to Central Administration to view the Servers in Farm page to verify the status. Instead of loading the homepage, I got the error message Unknown server tag 'AdminControls:MigrationToolPromotionTip'. I was able to get to other pages within Central Admin by typing in the URL directly. After successfully completing the Products and Configuration Wizard (which you should do after every patch), Central Administration loaded successfully. I then noticed a new advertising banner touting their SharePoint Migration tool. Not a coincidence.

SharePoint Online bug: New page opens with 500 Internal Server Error

Image
Issue: In a SharePoint Online site collection, any publishing features (and Wiki pages) will not allow you to create a new item. Pages, Site Pages, Reusable HTML and Reusable Text using the modern interface. Error: Either a blank page with the standard "500 Internal Server Error" or nothing at all in the Reusable Content libraries. Workarounds: 1) Use the Return to classic SharePoint to create these items. The errors will persist in the modern interface and you will need to manually switch each time the site is in the modern interface. 2) Change Document Library default open behavior setting. This will allow each library you set this way to behave normally. Advanced Settings > Open Documents in the Browser and set to "Open in the browser". 3) Disable the Open Documents in Client Applications by Default Site collection feature. This will prevent the issue completely. Root cause: Microsoft has confirmed a bug in a code release is causing

Outlook cannot open a new form on SharePoint Workflow Open this Task buttons

Issue: Recently a user stated they were getting an error message in Outlook stating "Outlook cannot open a new form. The form contains schema validation errors." when they clicked on the Open this Task button in a SharePoint Task assignment email. Root Cause: The user had created an out-of-the-box Approval workflow and inside the Request box had entered several HTML tags like <a href="site">link</a> where the site reference in the href was outside of SharePoint. Resolution: While I don't recommend putting HTML tags in the Task assignment emails in workflows, it will work if you reference the same SharePoint site or site collection the Task is coming from.

SharePoint 2013 Site Owner cannot manage Access Requests (Updated)

I have been pulling my limited hair out for a week trying to figure out why a Site Owner will Full Control on the site would always get denied when they tried to respond to Access Requests. When they received the email and clicked on " Accept or decline this request " which goes to https://[siteurl]/ Access Requests/pendingreq.aspx they would get " Sorry, this site hasn't been shared with you. " Preliminary Troubleshooting Steps I went through each and every permission group on the site to make sure the Site Owner group was the owner of the group. I went through each list or library that had broken site permissions and made sure the Site Owners group had Full Control of those as well. They all did. Then I looked at the Permission Level of the Site Owner's group. It said Full Control, but it also had that awful "Limited Access" permission. This site had many owners and many times they all tried their best to limit access to certain things and

SharePoint Servers with underscores. Trouble ahead.

SharePoint_Server_Name = Trouble_Ahead I recently had a friend of mine ask for some SharePoint 2013 troubleshooting help. It seemed that the server was running fine (Single Server Farm) but trying to configure a Secure Store Target Application for Excel Services that was causing grief. The error message was  "Your session has expired. Restart this wizard to continue." The Correlation ID has a few errors, but one in particular stated  "_admin/sssvc/ managetargetapplicationinstanc e.aspx' doesn't match the Page '_admin/sssvc/ managetargetapplicationfields. aspx"  which in itself is not very useful.  But looking more into that error and noticing the server name is  sharepoint_dev  a light went on and a feeling of dread for said friend.  SharePoint doesn't like underscores in server names, especially service apps on a single server farm where Central Admin is using the server name as the URL.  You have two options really.  You can rebui