Sage 100

Sage worked wonderfully yesterday for warehouse user. 

If you click yes, an override screen appears.  I enter my credentials (ALL ACCESS role).  Message says I am not authorized.  Click on the link to determine what role is missing and the second message pops.  Doesn't seem to be related at all to the date issue.........

Warehouse is logged in as different user for the time being.

Thoughts?




------------------------------
Jeff Schwenk
Bottomline Software, Inc.
------------------------------

The date message is just a warning, and easy to disable if they don't like it (Company Maintenance).  Ignore it.

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

The first message appears to be due to the option to "Restrict Accounting Date to Current and one Future Period"  and that is a company specific setting (company maintenance > preferences tab. The inventory period from the message shows that is is in June of  2020.Since you said that logging in as a different user seems to fix the issue, could it be that the user that is getting the error is accidentally logging into a different company code? 

that is the only thing I can think of that would make sense.

------------------------------
David Overholt
DWD Technology Group
------------------------------

Thanks for the feedback.

@Kevin Moyes - is more than a warning.  You can override, then prompted to log in with credentials having the ability to override.  If I (with full rights) can't override, who ​can?  In company set up, the two fields addressing this are not selected.  Never have been.  I even selected the fields, accepted, then deselected fields.  Saved record  @David Overholt, all modules are set to the current period (6/22).  Workstation was rebooted.
​

------------------------------
Jeff Schwenk
Bottomline Software, Inc.
------------------------------

Original Message:
Sent: 06-15-2022 10:46
From: David Overholt
Subject: Sage Date Issues - v2021 ADV

The first message appears to be due to the option to "Restrict Accounting Date to Current and one Future Period"  and that is a company specific setting (company maintenance > preferences tab. The inventory period from the message shows that is is in June of  2020.Since you said that logging in as a different user seems to fix the issue, could it be that the user that is getting the error is accidentally logging into a different company code?

that is the only thing I can think of that would make sense.

------------------------------
David Overholt
DWD Technology Group
------------------------------

I'm just saying the date warning is a red herring... ignore it.  Your role / permission issues are unrelated.

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

Original Message:
Sent: 06-15-2022 11:01
From: Jeff Schwenk
Subject: Sage Date Issues - v2021 ADV

Thanks for the feedback.

@Kevin Moyes - is more than a warning.  You can override, then prompted to log in with credentials having the ability to override.  If I (with full rights) can't override, who ​can?  In company set up, the two fields addressing this are not selected.  Never have been.  I even selected the fields, accepted, then deselected fields.  Saved record  @David Overholt, all modules are set to the current period (6/22).  Workstation was rebooted.
​

------------------------------
Jeff Schwenk
Bottomline Software, Inc.
------------------------------


Original Message:
Sent: 06-15-2022 10:46
From: David Overholt
Subject: Sage Date Issues - v2021 ADV

The first message appears to be due to the option to "Restrict Accounting Date to Current and one Future Period"  and that is a company specific setting (company maintenance > preferences tab. The inventory period from the message shows that is is in June of  2020.Since you said that logging in as a different user seems to fix the issue, could it be that the user that is getting the error is accidentally logging into a different company code?

that is the only thing I can think of that would make sense.

------------------------------
David Overholt
DWD Technology Group

@Kevin Moyes - If I try to override, I can't.  If I click no to over ride, I am exited.  Try a second time, I am "not authorized to run program"  message.  Pretty big red herring from my vantage point.  I looked for the JSON files but apparently local WS permissions are a stumbling block now.  Waiting for owner to return.

------------------------------
Jeff Schwenk
Bottomline Software, Inc.
------------------------------

Original Message:
Sent: 06-15-2022 11:08
From: Kevin Moyes
Subject: Sage Date Issues - v2021 ADV

I'm just saying the date warning is a red herring... ignore it.  Your role / permission issues are unrelated.

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


Original Message:
Sent: 06-15-2022 11:01
From: Jeff Schwenk
Subject: Sage Date Issues - v2021 ADV

Thanks for the feedback.

@Kevin Moyes - is more than a warning.  You can override, then prompted to log in with credentials having the ability to override.  If I (with full rights) can't override, who ​can?  In company set up, the two fields addressing this are not selected.  Never have been.  I even selected the fields, accepted, then deselected fields.  Saved record  @David Overholt, all modules are set to the current period (6/22).  Workstation was rebooted.
​

------------------------------
Jeff Schwenk
Bottomline Software, Inc.


Original Message:
Sent: 06-15-2022 10:46
From: David Overholt
Subject: Sage Date Issues - v2021 ADV

The first message appears to be due to the option to "Restrict Accounting Date to Current and one Future Period"  and that is a company specific setting (company maintenance > preferences tab. The inventory period from the message shows that is is in June of  2020.Since you said that logging in as a different user seems to fix the issue, could it be that the user that is getting the error is accidentally logging into a different company code?

that is the only thing I can think of that would make sense.

------------------------------
David Overholt
DWD Technology Group

Disable this checkbox in Company Maintenance and try again.
The Accounting Date warning has no security.  You have to set the module date, but that's it.

The "not authorized" error has to be something else.

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

Original Message:
Sent: 06-15-2022 13:37
From: Jeff Schwenk
Subject: Sage Date Issues - v2021 ADV

@Kevin Moyes - If I try to override, I can't.  If I click no to over ride, I am exited.  Try a second time, I am "not authorized to run program"  message.  Pretty big red herring from my vantage point.  I looked for the JSON files but apparently local WS permissions are a stumbling block now.  Waiting for owner to return.

------------------------------
Jeff Schwenk
Bottomline Software, Inc.
------------------------------


Original Message:
Sent: 06-15-2022 11:08
From: Kevin Moyes
Subject: Sage Date Issues - v2021 ADV

I'm just saying the date warning is a red herring... ignore it.  Your role / permission issues are unrelated.

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


Original Message:
Sent: 06-15-2022 11:01
From: Jeff Schwenk
Subject: Sage Date Issues - v2021 ADV

Thanks for the feedback.

@Kevin Moyes - is more than a warning.  You can override, then prompted to log in with credentials having the ability to override.  If I (with full rights) can't override, who ​can?  In company set up, the two fields addressing this are not selected.  Never have been.  I even selected the fields, accepted, then deselected fields.  Saved record  @David Overholt, all modules are set to the current period (6/22).  Workstation was rebooted.
​

------------------------------
Jeff Schwenk
Bottomline Software, Inc.


Original Message:
Sent: 06-15-2022 10:46
From: David Overholt
Subject: Sage Date Issues - v2021 ADV

The first message appears to be due to the option to "Restrict Accounting Date to Current and one Future Period"  and that is a company specific setting (company maintenance > preferences tab. The inventory period from the message shows that is is in June of  2020.Since you said that logging in as a different user seems to fix the issue, could it be that the user that is getting the error is accidentally logging into a different company code?

that is the only thing I can think of that would make sense.

------------------------------
David Overholt
DWD Technology Group

As I said in earlier post, this field has (never?) been activated.  But I selected it, accepted the panel to write the change, went back and deselected and accepted again.  No Luck.  Next step is to reinstall the workstation tomorrow.

------------------------------
Jeff Schwenk
Bottomline Software, Inc.
------------------------------

Original Message:
Sent: 06-15-2022 14:19
From: Kevin Moyes
Subject: Sage Date Issues - v2021 ADV

Disable this checkbox in Company Maintenance and try again.
The Accounting Date warning has no security.  You have to set the module date, but that's it.

The "not authorized" error has to be something else.

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


Original Message:
Sent: 06-15-2022 13:37
From: Jeff Schwenk
Subject: Sage Date Issues - v2021 ADV

@Kevin Moyes - If I try to override, I can't.  If I click no to over ride, I am exited.  Try a second time, I am "not authorized to run program"  message.  Pretty big red herring from my vantage point.  I looked for the JSON files but apparently local WS permissions are a stumbling block now.  Waiting for owner to return.

------------------------------
Jeff Schwenk
Bottomline Software, Inc.


Original Message:
Sent: 06-15-2022 11:08
From: Kevin Moyes
Subject: Sage Date Issues - v2021 ADV

I'm just saying the date warning is a red herring... ignore it.  Your role / permission issues are unrelated.

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


Original Message:
Sent: 06-15-2022 11:01
From: Jeff Schwenk
Subject: Sage Date Issues - v2021 ADV

Thanks for the feedback.

@Kevin Moyes - is more than a warning.  You can override, then prompted to log in with credentials having the ability to override.  If I (with full rights) can't override, who ​can?  In company set up, the two fields addressing this are not selected.  Never have been.  I even selected the fields, accepted, then deselected fields.  Saved record  @David Overholt, all modules are set to the current period (6/22).  Workstation was rebooted.
​

------------------------------
Jeff Schwenk
Bottomline Software, Inc.


Original Message:
Sent: 06-15-2022 10:46
From: David Overholt
Subject: Sage Date Issues - v2021 ADV

The first message appears to be due to the option to "Restrict Accounting Date to Current and one Future Period"  and that is a company specific setting (company maintenance > preferences tab. The inventory period from the message shows that is is in June of  2020.Since you said that logging in as a different user seems to fix the issue, could it be that the user that is getting the error is accidentally logging into a different company code?

that is the only thing I can think of that would make sense.

------------------------------
David Overholt
DWD Technology Group

Very odd!  Maybe check for a bad value in SY_ModuleDate?

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

Original Message:
Sent: 06-15-2022 15:32
From: Jeff Schwenk
Subject: Sage Date Issues - v2021 ADV

As I said in earlier post, this field has (never?) been activated.  But I selected it, accepted the panel to write the change, went back and deselected and accepted again.  No Luck.  Next step is to reinstall the workstation tomorrow.

------------------------------
Jeff Schwenk
Bottomline Software, Inc.
------------------------------


Original Message:
Sent: 06-15-2022 14:19
From: Kevin Moyes
Subject: Sage Date Issues - v2021 ADV

Disable this checkbox in Company Maintenance and try again.
The Accounting Date warning has no security.  You have to set the module date, but that's it.

The "not authorized" error has to be something else.

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


Original Message:
Sent: 06-15-2022 13:37
From: Jeff Schwenk
Subject: Sage Date Issues - v2021 ADV

@Kevin Moyes - If I try to override, I can't.  If I click no to over ride, I am exited.  Try a second time, I am "not authorized to run program"  message.  Pretty big red herring from my vantage point.  I looked for the JSON files but apparently local WS permissions are a stumbling block now.  Waiting for owner to return.

------------------------------
Jeff Schwenk
Bottomline Software, Inc.


Original Message:
Sent: 06-15-2022 11:08
From: Kevin Moyes
Subject: Sage Date Issues - v2021 ADV

I'm just saying the date warning is a red herring... ignore it.  Your role / permission issues are unrelated.

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


Original Message:
Sent: 06-15-2022 11:01
From: Jeff Schwenk
Subject: Sage Date Issues - v2021 ADV

Thanks for the feedback.

@Kevin Moyes - is more than a warning.  You can override, then prompted to log in with credentials having the ability to override.  If I (with full rights) can't override, who ​can?  In company set up, the two fields addressing this are not selected.  Never have been.  I even selected the fields, accepted, then deselected fields.  Saved record  @David Overholt, all modules are set to the current period (6/22).  Workstation was rebooted.
​

------------------------------
Jeff Schwenk
Bottomline Software, Inc.


Original Message:
Sent: 06-15-2022 10:46
From: David Overholt
Subject: Sage Date Issues - v2021 ADV

The first message appears to be due to the option to "Restrict Accounting Date to Current and one Future Period"  and that is a company specific setting (company maintenance > preferences tab. The inventory period from the message shows that is is in June of  2020.Since you said that logging in as a different user seems to fix the issue, could it be that the user that is getting the error is accidentally logging into a different company code?

that is the only thing I can think of that would make sense.

------------------------------
David Overholt
DWD Technology Group