Not long enough.
3 Likes
Kevin, were you impacted?
1 Like
I don’t think so. Not the new downtime.
The other, well uhm. Yeah, you could say that.
1 Like
The latest maintenance window seemed to come and go… never got any kind of all clear notice. So… I don’t even know if it took place.
1 Like
We were down for about an hour however after the maintenance concluded and we received the status update saying the maintenance window had closed most of our users started getting errors stating they were unable to log in.
Clearing the ProgramData cache directory didnt fix it but a reboot and clearing the cache for all users did.
It was another white knuckle start to the day in Epicor Land.
6 Likes
We miss this one also:
Kinetic - Americas will undergo an emergency change event that will involve a restarting windows failover cluster service for a subset of customers.
Not the data center messages I want to see in the morning before our last shipping day of the month.
3 Likes
Thanks @Patrick. I JUST received this alert at 9AM, haha:
In Epicor’s defense, I just received word from my IT group that we’re “experiencing issues with incoming/outgoing emails”… so… in my case, probably not Epicor’s fault. 
3 Likes
All day Monday, and half of Tuesday
1 Like
Just a subset of customers or all of americas?
1 Like
We were down 1/2 day Monday but had data loss form our Sales Team who worked Sunday Evening for a couple of hours.
1 Like
We are on the SaaS datacenter out of Iowa and we were up Sunday, but had issues with slowness till around 3 pm on Monday. Many users were waiting 1 to 3 minutes for processes that normally take 5 seconds or less.
2 Likes
What was this all about? Was it an upgrade of release/version?
1 Like
Same for us.
2 Likes
Upgrade to SQL 2022. Pilot install went fine a few weeks ago.
2 Likes
What you see on the Epicor Status Web Site is all the information we get.
Kinetic – Americas in Production environment
From Sunday, April 27 11:00 PM CST To: Monday, April 28 5:00 AM CST
Note; Due to an issue with database restoration after SQL Server 2022 upgrade, A subset of customers may not be able to access the Kinetic instance at this time. We are working quickly to restore all customers and expect to have this completed within 6 hours. Please refer back to this notice for updates on progress.
An all-clear message will be posted when the fix has been completed.
1 Like
Subset, we were fine luckily as we had users in starting at 6am Monday morning.
SQL2022 upgrade / migration depending how they did it.
1 Like
i was told that the performance issues were impacting people who have the read only database. I can deduce from this information that the issue was with replication, which would make sense because there is no read only database (and thus no replication) on non-prod environments.
3 Likes
We have the read only DB. Any one having issues today with performance again?
Nope.
Thanks seeing performance across all modules for us today. Has been internment. Saw there was another event last night too so wondering if we are the only LUCKY ones!
Kinetic - Americas will undergo an emergency change event that will involve a restarting windows failover cluster service for a subset of customers. This event is necessary to ensure the stability and reliability of our database systems and to correct the issues a subset of customers.
1 Like