Does anyone know the cause of this error : FATAL - [analytics.CountlyLogAdapter.()] [SessionImpl] Session is not began to update it
APC UPS Data Center & Enterprise Solutions Forum
Schneider, APC support forum to share knowledge about installation and configuration for Data Center and Business Power UPSs, Accessories, Software, Services.
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2023-03-1606:04 PM
Does anyone know the cause of this error : FATAL - [analytics.CountlyLogAdapter.()] [SessionImpl] Session is not began to update it
I have upgraded PowerChute Business Edition v10.0.5 from v9.1.1.604.
The setup is Dell server running Windows Server 2019 that is connected to a "Smart-UPS 1500" (SMC1500IC) over the USB port. The server has had serval reboots after the upgrade. The upgrade steps were complete uninstall of the old version and then a fresh new install of the new version. Followed by reconfiguring the UPS using the PowerChute webservice.
The web service looks perfect ... application event logs look great, reporting events as expected.
The concern is just the PCBE.LOG file has this strange repeating fatal error every 30 seconds. This error occurs on every site I have installed PowerChute on.
Here is an example of the error ... (also attached the log)
2023-03-16 11:16:10,086 [pool-4-thread-1] FATAL - [analytics.CountlyLogAdapter.()] [SessionImpl] Session is not began to update it 2023-03-16 11:16:40,089 [pool-4-thread-1] FATAL - [analytics.CountlyLogAdapter.()] [SessionImpl] Session is not began to update it
Is this a valid concern, can I ignore this error message or is there a way to mute this error.