Expected non-empty string. Parameter name: userPrincipalName RRS feed

  • Question

  • Hi,

    I have an IFD deployment that we recently updated to update rollup 0.1 for CRM 2016. The update completed and asked to be restarted. On the restart, the server received a drive fault and didn't boot right away. Someone had to push the boot process through. The drive was apart of a RAID 1 and it was swapped out and synced. We started noticing issues with reports not fully loading. The page would load, but no data. It would load fine if we used the external URL.

    I've since re-installed the CRM files because pages began to not load right. Certain css features were missing. Re-installing the CRM files fixed this, but then our internal urls and external urls are giving redirect loops. Also, I re-created both relying party trusts when I re-installed the CRM files. I wasn't seeing any errors in the event logs except that the session had hit the ADFS server 6 times and failed.

    I activated tracing and then saw this exception.

    Crm Exception: Message: Expected non-empty string., ErrorCode: -2147220989, InnerException: System.ArgumentException: Expected non-empty string.
    Parameter name: userPrincipalName

    I saw various posts that a rule is needed in the Claims Provider Trusts for Active Directory, but this is created. I re-created the rule, and that seemed to fix the internal redirect loop, but reports do not load still and I get the same exception as above. 

    I'm not sure what to do now. Everything seems to work fine when I disable IFD and claims. Anyone have any suggestions?


    Sunday, March 13, 2016 11:04 PM

All replies

  • The rule that you have in your screenshot is the same as in my claims rules for AD. I also have 10 other rules for Active directory. Did you set up the three claims rules for the claims and IFD relying party trusts?  This is all described in the download from Microsoft at this location, https://www.microsoft.com/en-gb/download/details.aspx?id=41701

    Monday, March 14, 2016 11:15 PM
  • Yes, all three rules are created for Claims and IFD. We had this same setup working before the update.
    Tuesday, March 15, 2016 12:00 PM
  • Of course, you said that. Perhaps AD FS became corrupted as well?

    I'm not sure what else to suggest.

    Tuesday, March 15, 2016 1:33 PM
  • AD FS is hosted on a separate server so I didn't think it could be the issue. I also brought up a whole separate environment and imported a backup of the database and it occurred on the test environment as well. It makes me think something in the database may not be right, but i'm not sure where to look.

    It's weird that I can get into CRM now using claims, but if I run a report I get the Exception.

    Thanks for your help.

    Tuesday, March 15, 2016 3:52 PM
  • Did you create SPNs for the CRM service accounts?
    Wednesday, March 16, 2016 7:25 PM
  • Yes, I have created them. I just finished contacting Microsoft and it appears to be a known issue with Update 0.1. We removed the update for the CRM server base and SSRS and that fixed the issue.

    So, if you are using ADFS then you shouldn't update CRM to 0.1.

    Wednesday, March 16, 2016 11:23 PM
  • We can confirm our CRM2016 ADFS enable On-Premise deployments reports have also stopped working, and we too have installed the 0.1 upgrade.

    We can also confirm this issue affects the internal URL and not the external one, which continues to operate correctly.

    With no other help or recourse available, removing update 0.1 is what we are going to attempt next.

    I guess installing anything referred to as 0.1 was asking for trouble :-(

    Monday, April 4, 2016 10:17 AM
  • Hi,

    I can confirm that I am having the same issue. We upgraded CRM 2013 to CRM 2016 and applied update 0.1 on top. Claims and IFD was then configured and reports stopped working. 

    The issue has something to do with CRM not knowing what the organization ID is when running reports via the internal URL. 

    However, reports will work when using the external URL. This is a potential workaround.

    Please feel free to contact me via any of the following methods:

    • Proposed as answer by Roshan Mehta Thursday, April 21, 2016 8:18 AM
    Thursday, April 21, 2016 8:14 AM
  • Hi,

    Contact Microsoft Support and ask them for a hotfix. We used this approach and I can confirm that reports are working as expected.

    Note that Update 0.1 also breaks the Interactive Service Hub on the internal IFD URL. This hotfix appears to resolve this issue as well.



    Please feel free to contact me via any of the following methods:

    • Proposed as answer by Roshan Mehta Thursday, April 28, 2016 8:18 PM
    Thursday, April 28, 2016 8:18 PM