Project and Portfolio Management Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

After implementing SSO, users often encounter Error 500

Highlighted
PPM Admin
Regular Collector

After implementing SSO, users often encounter Error 500

How can we avoid it? SSO runs using IIS.

This is an intermittent error.

Thanks.
6 REPLIES
Surendra Poosar
Frequent Visitor

Re: After implementing SSO, users often encounter Error 500

Chona,

Is your PPM instance integrated with any other system like EMC Documentum??

What does the error log display?
PPM Admin
Regular Collector

Re: After implementing SSO, users often encounter Error 500

Yes it has a documentum.

The error says:

Error 500: Unknown
Surendra Poosar
Frequent Visitor

Re: After implementing SSO, users often encounter Error 500

Chona,

We have the same issue sometimes. We have PPM, EMC documenti in place.

The issue we see is the login ID for EMC Documentum is case specicific. The user need to login using all lower case, whereas PPM login is not case specific. If the user logs into PPM using upper case,PPM would still accept it but the user would see an error as Error 500 while approving or saving the requests.

You may need to ask the user to login to PPM with the same case as Documentum Loign ID.

Thanks
Surendra
PPM Admin
Regular Collector

Re: After implementing SSO, users often encounter Error 500

Hi Surendra,

Thanks.

We have the same scenario, but I'm not sure if this is the root cause of this error. Because when I check my users logon attempts history who have this kind of issue, their username was already lowercased.

Can you tell me where can I find the error logs that will point to this kind of scenario?

Chona
Surendra Poosar
Frequent Visitor

Re: After implementing SSO, users often encounter Error 500

Chona,

I generally see these errors in the ServerLog.txt.

Thanks
Surendra
PPM Admin
Regular Collector

Re: After implementing SSO, users often encounter Error 500

I cannot find any documentum error.

Does anyone also encounter this error.

Thanks,
Chona
//Add this to "OnDomLoad" event