SAS EM - The application has encountered an unexpected problem

[MariaD]

Hi Folks,

We have SAS9.4 M5 and SAS EM 14.3 installed on Unix 7.1. Until yesterday, we could connect perfectly using SAS EM Client. Today, when we tried to open SAS EM Client the following error appear:

We reviewed the sassw.config and the SASENVIRONMENTSURL is defined and it's ok. We copied the URL value of SASENVIRONMENTSURL and paste on Internet Explorer and the xml opens.

SASENVIRONMENTSURL=http://server:7980/sas/sas-environment.xml

If we connect to SASEM using the link http://server:8080/SASEnterpriseMinerJWS/Status, we can access without any problem. We also restarted the SAS server but the problem continues. Any idea?

Regards.

[ballardw]

One of the first things I would do would be to contact your IT department and see if they have installed, upgraded or changed any security software or settings, next would be operating system upgrades. Anything that stops working on a given day leads me to suspect some change in environment and your IT folks likely have the best ideas on changes done organization wide, or just to your users.

[MariaD]

Hi @ballardw,

We have two servers one for development and other one for production. My first impulse was that. But If I change the SASENVIRONMENTSURL properties in sassw.config for the production environment, the client connects perfectly. I really don't understand what is going on.

Regards,

[SimonDawson]

Take the non-working SASENVIRONMENTSURL value, paste that into a browser on the machine. What happens?

[MariaD]

I copied and paste de URL on a browser and open the XML file as expected.

[PaulHomes]

It looks like you have a duplicate post at https://communities.sas.com/t5/Administration-and-Deployment/SAS-Enterprise-Miner-Client-Error-com-s... In the em_console output posted there it looks like there is a Kerberos ticket error. The stack trace has:

... LogonPackage - Failed to resolve login identity

... TicketCreationException: Unable to acquire ticket: (400 Bad Request  ...

When you are logging into SAS EM have you ticked the box to "Use Integrated Windows authentication (single sign-on)" or are you specifying a user id and password?

[MariaD · Accepted solution]

Finally, we find the solution. For some strange reason, the sas-environment.xml has a hide character. We replace the file with version used for link connections and now it's working fine.