1

I'm running into a weird situation. I have two web applications, both using Windows Authentication. They are both using the default login page, both disallow anonymous access, no other special configuration.

Both site collections are publishing sites.

When I navigate to Web Application 1 (port 80), after logging in, I see the landing page for the site collection, and everything works as expected.

When I navigate to Web Application 2 (port 81), after logging in, SharePoint tries to redirect me to [MySiteUrl]/Account/Login. There is no such page, or configuration that I am aware where this is specified. Because the page cannot be found, it directs me to the PageNotFoundError screen. Oddly enough, I am authenticated, so clicking "go to the site home" link does take me back to the home page.

enter image description here

The situation happens when accessing it internally on the server, or externally, so I don't think it's related to Access Mappings.

This is a fresh install of SharePoint, so I'm not really sure what could be the problem.

Improve this question
3
  • 1
    It's interesting that you masked the IP address, despite that it's listed in your request URL.
    – Quinn Johns
    Mar 27, 2015 at 0:30
  • Can you confirm a few items for me? It's been awhile since I've done this, but can you go to "<enter your site>/_layouts/AreaWelcomePage.aspx" and see if it gives you the start page (and confirm that it isn't set to the Account/Logon page. If that doesn't work, can you check central administration (if this is a server versus multi-tenant) and go to Manage Web Application, and verify if everything is good on the ribbon under the "Authentication Providers".
    – Quinn Johns
    Mar 27, 2015 at 0:35
  • @QuinnJohns looks like my obfuscation skills are lacking. I confirmed that the welcome page for both sites are /pages/default.aspx
    – contactmatt
    Mar 27, 2015 at 5:08

1 Answer 1

Reset to default
0

This ended up being a very specific issue. Someone had added a reference to WebMatrix.WebData.dll in our SharePoint deployment project. Apparently the mere presence of this assembly caused this issue.

After removing this to the assembly, and making sure no packages referenced it, the problem was fixed.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.