She's dead Jim 🚀 SaaS down / crawling for anyone else?

Kinetic ERP
1

star trek GIF

Couldn’t get in. Now I’m in with frequent errors.

Crawling.

Anyone else?

2 Likes
2 
Application Error

Exception caught in: Epicor.ServiceModel

Error Detail 
============
Message: The underlying provider failed on Open.
Inner Exception Message: 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)
Program: Epicor.ServiceModel.dll
Method: CallWithCommunicationFailureRetry

Client Stack Trace 
==================
   at Epicor.ServiceModel.Channels.ImplBase.CallWithCommunicationFailureRetry(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, RestRpcValueSerializer serializer)
   at Epicor.ServiceModel.Channels.ImplBase.CallWithMultistepBpmHandling(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, Boolean useSparseCopy)
   at Epicor.ServiceModel.Channels.ImplBase.Call(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, Boolean useSparseCopy)
   at Erp.Proxy.BO.CompanyImpl.CompanyTaxConnectCertCaptureEnabled(String company)
   at Erp.Adapters.CompanyAdapter.CompanyTaxConnectCertCaptureEnabled(String companyID)

Inner Exception 
===============
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)
1 Like
3

image
image867×489 36.5 KB

4

As usual, zero actual information provided. I don’t know why they bother.

5

Good lord how late on a Friday were you working.

1 Like
6

I wasn’t.

Plant runs 24x7.

2 Likes
7

:pray:

1 Like
8

Looks like we got this error today. everyone was working fine, then all of a sudden we all get booted and can’t login. Submitted ticket.

3 Likes
9

I have access to both an AKS-based client and a pre-AKS client, both of them are up (at least I can login to both).

10

Looks like I can login now. But no word on the issue.

2 Likes