We can't connect to Epicor through IDP this morning

Kinetic ERP
1

Our Epicor IDP appears to be down. Is anyone else experiencing outages this morning?

1 Like
2

I have several users reporting login issues this morning. I am not onsite yet so trying to get feedback from users onsite now before I get there to determine if they can login via browser or if it is just their Smart Client throwing them login errors.

1 Like
3

We just had something a little squirrely with reports failing to process but seems to have been a transient deal (~30m). Already opened a case FWIW - here’s the crux of the errors.

Program Ice.Services.Lib.RunTask when executing task 2698811 raised an unexpected exception with the following message: RunTask:

Microsoft.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

—> System.ComponentModel.Win32Exception (64): The specified network name is no longer available.

2 Likes
4

This was a strange issue this morning.

I was able to login with basic authentication, but not IDP.

However, I was able to login through IDP when I connected my laptop to a hotspot or internet outside of our network. It appeared to be an issue with authentication but was okay once it was authenticated.

We also had some issues with printing, so I don’t think it was just related to our network.

Anyway, it appears to be fixed now…but we will probably never know where the real issue came from since it just started working again.

5

Same. Opened case FWIW. If they at least came back and said “yup we had a brief problem” I’d be fine with it.

EDIT - and that’s exactly what they just did.
We apologize for the inconvenience caused. Upon reviewing the logs at the mentioned time of incident, we identified an alert in SolarWinds indicating a disconnection of the SSRS service, which led to the issue. To resolve this, we restarted the service, and after the restart, the servers are now back online and functioning normally.

1 Like
6

Well by the time I got to the office users could then start logging in. Had a couple of stragglers that took a bit for the system to behave and then got everyone in.

3 Likes