Differences between Internal/External Access

(0) Share

Report

Posted on by Community Member

Hi All,

Seeing some strange behavior in our Dynamics 2015 CRM environment between pages accessed internally vs externally. When we access using the external link everything works as expected. You would think it would work properly since it is a domain joined PC accessing the page and it properly loads the authenticated user...

When the initial dashboard loads we get the following error: "Message from Webpage: Generic Error"

Not a lot to go with there; click okay allows us to continue with the following posted under What's New: "An error occurred. Please wait a few moments and try again. If the problem persists, contact a system administrator."

If I attempt to post I get the following error: "Message from Webpage: your post was not saved. It's possible that this record was deleted before you finished or you do not have permission to post. Check the record and try again." It appears as if the post is successful; however, when the page is refreshed, the same two errors occur and the post is gone.

Allow me to state once more that everything works without error if the external link is used. Also, I am a Dynamics admin so I should have full rights locally.

This same behavior occurs in Dynamics 2013 CRM as I have tested with other admins. Has anyone seen this before? Know how to fix the issue? Online searches have not proved to be much help.

Thanks in advance.

*This post is locked for comments

I have the same question (0)

All responses (9)

Answers (0)

Community Member on at

Like (0)

Report

No one else has seen this behavior?

Was this reply helpful? Yes No
Daniel Wikell 2,360 on at

Like (0)

Report

I think I've stumbled upon something similar in the past. If you check the organization from the Deployment Manager tool you should be able to see and change the addresses that the web services use. Are they pointing towards the internal or the external address?

Since things are working for the external my guess would be that's also what they are set to.

Are the internal and external addresses using the same domain? If not you might be running into cross domain issues when trying to use the site from the other address (which would surely cause trouble when browsing the application).

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

They are all pointing to the external address as they are supposed to be...outside resource work flawlessly, and since Outlook required the outside URL it works. It is just browsing to the internal URL that has the issues noted. When I access the page, I am properly identified. To me it appears as if some permission is set properly on the local site.

Was this reply helpful? Yes No
Daniel Wikell 2,360 on at

Like (0)

Report

Just for the sake of it, you could try and temporarily change those to the internal address and see if it makes any difference when accessing the site through the internal address. This ofc won't solve your problem since outlook requires the external, but it might help us understand the nature of the issue better.

Was this reply helpful? Yes No
Arpita Saini on at

Like (0)

Report

Do you have claims and ADFS enabled in the environment?

If yes, then set web address tab to internal address only. and external address will be your orgname.domain.com.

I will try and check if we have any know issues on this in Dynamics CRM and will update you soon.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Sorry for the late response, yes we are using claims with ADFS, plus IFD.

Are you referring to the Deployment Properties, the Web Address Tab? Web Application Server line?

Thanks

Was this reply helpful? Yes No
cmillerlce 147 on at

Like (0)

Report

I believe I saw something similar in our CRM 2015 environment. Are you explicitly using https in the URL? Allowing the page to load as http is what was the cause of my issue when I would get that generic error on the social dashboard thing. I would get the generic error when loading the site with http://internalurl but when I used https://internalurl that error went away.

Was this reply helpful? Yes No
Community Member on at

Like (1)

Report

@cmillerLCE - you are a bit late to this thread, but your scenario shows that you have an unsupported configuration. CRM is only supported on one binding, so if you have IIS configured for http *and* https at the same time, this won't work, and is unsupported. You need to remove the http binding from CRM in IIS.

Was this reply helpful? Yes No
cmillerlce 147 on at

Like (0)

Report

@Adam Vero - Thanks for the clarification. I just happened to stumble upon this thread searching for something else and thought I'd share my similar experience and resolution that the OP described. If it helps someone else in the future then great.

Was this reply helpful? Yes No