Sage 100

Power options on the local computer set for hard drive and or network adapter to sleep?

Anything in the Sage Activity Log?

Anything in the Windows Event Viewer?  (Server / workstation).

Nothing in Sage and according to IT nothing in Windows on workstation or server. They've been much more proactive re this than some IT, but of course that doesn't mean they didn't miss seeing something.

------------------------------
Beth Bowers
(269) 358-0989
------------------------------


Original Message:
Sent: 07-16-2024 12:49
From: Kevin Moyes
Subject: More Sage going poof, but in a different way

Anything in the Sage Activity Log?

Anything in the Windows Event Viewer?  (Server / workstation).

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON

Perhaps DFDM SY_User to make sure there are no weird values in the two auto logoff fields.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------


Original Message:
Sent: 07-16-2024 12:53
From: Beth Bowers
Subject: More Sage going poof, but in a different way

Nothing in Sage and according to IT nothing in Windows on workstation or server. They've been much more proactive re this than some IT, but of course that doesn't mean they didn't miss seeing something.

------------------------------
Beth Bowers
(269) 358-0989


Original Message:
Sent: 07-16-2024 12:49
From: Kevin Moyes
Subject: More Sage going poof, but in a different way

Anything in the Sage Activity Log?

Anything in the Windows Event Viewer?  (Server / workstation).

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON

Ooh, good thought, but no.  HOWEVER, there was a blank record in the SY_User file, which I deleted.  Never seen that before...

Perhaps DFDM SY_User to make sure there are no weird values in the two auto logoff fields.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 07-16-2024 12:53
From: Beth Bowers
Subject: More Sage going poof, but in a different way

Nothing in Sage and according to IT nothing in Windows on workstation or server. They've been much more proactive re this than some IT, but of course that doesn't mean they didn't miss seeing something.

------------------------------
Beth Bowers
(269) 358-0989


Original Message:
Sent: 07-16-2024 12:49
From: Kevin Moyes
Subject: More Sage going poof, but in a different way

Anything in the Sage Activity Log?

Anything in the Windows Event Viewer?  (Server / workstation).

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON

The blank row could actually be the cause.  We've seen seriously bad things with blank rows in GL_Bank.

Ooh, good thought, but no.  HOWEVER, there was a blank record in the SY_User file, which I deleted.  Never seen that before...

Perhaps DFDM SY_User to make sure there are no weird values in the two auto logoff fields.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 07-16-2024 12:53
From: Beth Bowers
Subject: More Sage going poof, but in a different way

Nothing in Sage and according to IT nothing in Windows on workstation or server. They've been much more proactive re this than some IT, but of course that doesn't mean they didn't miss seeing something.

------------------------------
Beth Bowers
(269) 358-0989


Original Message:
Sent: 07-16-2024 12:49
From: Kevin Moyes
Subject: More Sage going poof, but in a different way

Anything in the Sage Activity Log?

Anything in the Windows Event Viewer?  (Server / workstation).

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON

Do NOT get my hopes up.  :-)

The blank row could actually be the cause.  We've seen seriously bad things with blank rows in GL_Bank.

Ooh, good thought, but no.  HOWEVER, there was a blank record in the SY_User file, which I deleted.  Never seen that before...

Perhaps DFDM SY_User to make sure there are no weird values in the two auto logoff fields.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON


Original Message:
Sent: 07-16-2024 12:53
From: Beth Bowers
Subject: More Sage going poof, but in a different way

Nothing in Sage and according to IT nothing in Windows on workstation or server. They've been much more proactive re this than some IT, but of course that doesn't mean they didn't miss seeing something.

------------------------------
Beth Bowers
(269) 358-0989


Original Message:
Sent: 07-16-2024 12:49
From: Kevin Moyes
Subject: More Sage going poof, but in a different way

Anything in the Sage Activity Log?

Anything in the Windows Event Viewer?  (Server / workstation).

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON

Perhaps I overlooked this and if so I apologize - is this on a network, remote desktop, published app, Sage Partner Cloud? 

And multiple things running - does that refer to multiple Sage screens open or is it multiple applications on the local workstation?

Nope, I didn't get into those important points.  It's on a plain old network - not RDP. And the "multiple things" is multiple Sage screens/reports open.

Perhaps I overlooked this and if so I apologize - is this on a network, remote desktop, published app, Sage Partner Cloud? 

And multiple things running - does that refer to multiple Sage screens open or is it multiple applications on the local workstation?

I'd be tempted to try and reproduce it directly at the server by logging into a Sage session on the server and then seeing if that session logs out when the other users report that they are being logged out as well. 

Have you ruled out the sever rebooting? That's probably a longshot but I do have customers where they create a virtual server that runs nothing but Sage so it's not completely crazy.

Nope, I didn't get into those important points.  It's on a plain old network - not RDP. And the "multiple things" is multiple Sage screens/reports open.

Perhaps I overlooked this and if so I apologize - is this on a network, remote desktop, published app, Sage Partner Cloud? 

And multiple things running - does that refer to multiple Sage screens open or is it multiple applications on the local workstation?

Beth,

By chance is the client using virtual servers? Does the issue happen at a certain time during the day or start with one user (then has a snowball effect with the other Sage users) in Sage?