Sage 100

Client is working with a New Laptop with +2 external monitors (3 screens total).  When they launch Sage 100, they get the Login Screen.  Sage then appears to open but NEVER Shows up on the took bar.  When I open Task Manager, nothing shows up for Sage on the first APPS Tab.  When I look at Details, the pvxwin32.exe is running.  When I go into Master Console, the User is listed as logged into the Launcher.  But on the desktop, they see nothing.  IT says it worked for a day or two, then stopped working and "nothin has changed".  He has tried uninstalling and reinstalling again, that does not fix the problem.  Any ideas?

------------------------------
Madeline Stefanou
RKL eSolutions, LLC
------------------------------

Hi - try deleting the Sage100 folder in my documents....

Jeff F.

------------------------------
Jeff Fiddelman
Exeplex, LLC
------------------------------

That worked @Jeff Fiddelman  Thank you so much.​

------------------------------
Madeline Stefanou
RKL eSolutions, LLC
------------------------------

Original Message:
Sent: 06-17-2021 18:43
From: Jeff Fiddelman
Subject: v2016 Standard

Hi - try deleting the Sage100 folder in my documents....

Jeff F.

------------------------------
Jeff Fiddelman
Exeplex, LLC
------------------------------

I'm going to piggyback off this post.  I have the same thing going on v2016 Standard, started just in the last couple of days. 
I renamed the Sage100 in users\documents. 
If user (A) logs in to windows & Sage, Sage doesn't open but does show up in Task Manager. 
If I do a 'run as admin', it prompts for admin credentials but does open.  
I also tried a 'run in mas90 mode' (althought it already is standard) and it prompted for credentials but did launch/open successfully.
I had another user (B) log into the machine with their windows account and it worked as designed.
I had the problem child user (A) log into another machine with their windows account and it worked as designed.
What I'm not sure of is if they use Roaming Profiles which maybe would have given user (B) local admin rights?  Do local admin rights follow a Roaming Profile?
UAC was turned all the way up, did back it off a notch but no change.
Thoughts?
Nancy



------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN
------------------------------

Original Message:
Sent: 06-18-2021 16:19
From: Madeline Stefanou
Subject: v2016 Standard

That worked @Jeff Fiddelman  Thank you so much.​

------------------------------
Madeline Stefanou
RKL eSolutions, LLC
------------------------------


Original Message:
Sent: 06-17-2021 18:43
From: Jeff Fiddelman
Subject: v2016 Standard

Hi - try deleting the Sage100 folder in my documents....

Jeff F.

------------------------------
Jeff Fiddelman
Exeplex, LLC

@Nancy Hanson, My client uninstalled the workstation, set UAC to never, then installed again.  My client is a local admin of their PC.  The delete of the Sage 100 folder in the my documents folder, resolved the problem.   Sounds like UAC may be your problem, or the "run as admin" issue.  ​

------------------------------
Madeline Stefanou
RKL eSolutions, LLC
------------------------------

Original Message:
Sent: 06-18-2021 16:47
From: Nancy Hanson
Subject: v2016 Standard

I'm going to piggyback off this post.  I have the same thing going on v2016 Standard, started just in the last couple of days.
I renamed the Sage100 in users\documents.
If user (A) logs in to windows & Sage, Sage doesn't open but does show up in Task Manager.
If I do a 'run as admin', it prompts for admin credentials but does open.
I also tried a 'run in mas90 mode' (althought it already is standard) and it prompted for credentials but did launch/open successfully.
I had another user (B) log into the machine with their windows account and it worked as designed.
I had the problem child user (A) log into another machine with their windows account and it worked as designed.
What I'm not sure of is if they use Roaming Profiles which maybe would have given user (B) local admin rights?  Do local admin rights follow a Roaming Profile?
UAC was turned all the way up, did back it off a notch but no change.
Thoughts?
Nancy



------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN
------------------------------


Original Message:
Sent: 06-18-2021 16:19
From: Madeline Stefanou
Subject: v2016 Standard

That worked @Jeff Fiddelman  Thank you so much.​

------------------------------
Madeline Stefanou
RKL eSolutions, LLC


Original Message:
Sent: 06-17-2021 18:43
From: Jeff Fiddelman
Subject: v2016 Standard

Hi - try deleting the Sage100 folder in my documents....

Jeff F.

------------------------------
Jeff Fiddelman
Exeplex, LLC

FYI, setting UAC to "never" doesn't do anything other than silence the prompt.  It's still active unless you edit the registry key (directly or through the policy editor).  Set EnableLUA to 0 (zero) and reboot to properly disable UAC.


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

Original Message:
Sent: 06-21-2021 08:57
From: Madeline Stefanou
Subject: v2016 Standard

@Nancy Hanson, My client uninstalled the workstation, set UAC to never, then installed again.  My client is a local admin of their PC.  The delete of the Sage 100 folder in the my documents folder, resolved the problem.   Sounds like UAC may be your problem, or the "run as admin" issue.  ​

------------------------------
Madeline Stefanou
RKL eSolutions, LLC
------------------------------


Original Message:
Sent: 06-18-2021 16:47
From: Nancy Hanson
Subject: v2016 Standard

I'm going to piggyback off this post.  I have the same thing going on v2016 Standard, started just in the last couple of days.
I renamed the Sage100 in users\documents.
If user (A) logs in to windows & Sage, Sage doesn't open but does show up in Task Manager.
If I do a 'run as admin', it prompts for admin credentials but does open.
I also tried a 'run in mas90 mode' (althought it already is standard) and it prompted for credentials but did launch/open successfully.
I had another user (B) log into the machine with their windows account and it worked as designed.
I had the problem child user (A) log into another machine with their windows account and it worked as designed.
What I'm not sure of is if they use Roaming Profiles which maybe would have given user (B) local admin rights?  Do local admin rights follow a Roaming Profile?
UAC was turned all the way up, did back it off a notch but no change.
Thoughts?
Nancy



------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN


Original Message:
Sent: 06-18-2021 16:19
From: Madeline Stefanou
Subject: v2016 Standard

That worked @Jeff Fiddelman  Thank you so much.​

------------------------------
Madeline Stefanou
RKL eSolutions, LLC


Original Message:
Sent: 06-17-2021 18:43
From: Jeff Fiddelman
Subject: v2016 Standard

Hi - try deleting the Sage100 folder in my documents....

Jeff F.

------------------------------
Jeff Fiddelman
Exeplex, LLC

@Kevin Moyes; now I feel silly.  I never knew this.  Thank you for explaining so thoroughly.  ​

------------------------------
Madeline Stefanou
RKL eSolutions, LLC
------------------------------

Original Message:
Sent: 06-21-2021 12:53
From: Kevin Moyes
Subject: v2016 Standard

FYI, setting UAC to "never" doesn't do anything other than silence the prompt.  It's still active unless you edit the registry key (directly or through the policy editor).  Set EnableLUA to 0 (zero) and reboot to properly disable UAC.


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


Original Message:
Sent: 06-21-2021 08:57
From: Madeline Stefanou
Subject: v2016 Standard

@Nancy Hanson, My client uninstalled the workstation, set UAC to never, then installed again.  My client is a local admin of their PC.  The delete of the Sage 100 folder in the my documents folder, resolved the problem.   Sounds like UAC may be your problem, or the "run as admin" issue.  ​

------------------------------
Madeline Stefanou
RKL eSolutions, LLC


Original Message:
Sent: 06-18-2021 16:47
From: Nancy Hanson
Subject: v2016 Standard

I'm going to piggyback off this post.  I have the same thing going on v2016 Standard, started just in the last couple of days.
I renamed the Sage100 in users\documents.
If user (A) logs in to windows & Sage, Sage doesn't open but does show up in Task Manager.
If I do a 'run as admin', it prompts for admin credentials but does open.
I also tried a 'run in mas90 mode' (althought it already is standard) and it prompted for credentials but did launch/open successfully.
I had another user (B) log into the machine with their windows account and it worked as designed.
I had the problem child user (A) log into another machine with their windows account and it worked as designed.
What I'm not sure of is if they use Roaming Profiles which maybe would have given user (B) local admin rights?  Do local admin rights follow a Roaming Profile?
UAC was turned all the way up, did back it off a notch but no change.
Thoughts?
Nancy



------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN


Original Message:
Sent: 06-18-2021 16:19
From: Madeline Stefanou
Subject: v2016 Standard

That worked @Jeff Fiddelman  Thank you so much.​

------------------------------
Madeline Stefanou
RKL eSolutions, LLC


Original Message:
Sent: 06-17-2021 18:43
From: Jeff Fiddelman
Subject: v2016 Standard

Hi - try deleting the Sage100 folder in my documents....

Jeff F.

------------------------------
Jeff Fiddelman
Exeplex, LLC

The original UAC worked the way you would expect... but with Win server 2012 M$ changed it.
Link.

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

Original Message:
Sent: 06-21-2021 13:10
From: Madeline Stefanou
Subject: v2016 Standard

@Kevin Moyes; now I feel silly.  I never knew this.  Thank you for explaining so thoroughly.  ​

------------------------------
Madeline Stefanou
RKL eSolutions, LLC
------------------------------


Original Message:
Sent: 06-21-2021 12:53
From: Kevin Moyes
Subject: v2016 Standard

FYI, setting UAC to "never" doesn't do anything other than silence the prompt.  It's still active unless you edit the registry key (directly or through the policy editor).  Set EnableLUA to 0 (zero) and reboot to properly disable UAC.


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


Original Message:
Sent: 06-21-2021 08:57
From: Madeline Stefanou
Subject: v2016 Standard

@Nancy Hanson, My client uninstalled the workstation, set UAC to never, then installed again.  My client is a local admin of their PC.  The delete of the Sage 100 folder in the my documents folder, resolved the problem.   Sounds like UAC may be your problem, or the "run as admin" issue.  ​

------------------------------
Madeline Stefanou
RKL eSolutions, LLC


Original Message:
Sent: 06-18-2021 16:47
From: Nancy Hanson
Subject: v2016 Standard

I'm going to piggyback off this post.  I have the same thing going on v2016 Standard, started just in the last couple of days.
I renamed the Sage100 in users\documents.
If user (A) logs in to windows & Sage, Sage doesn't open but does show up in Task Manager.
If I do a 'run as admin', it prompts for admin credentials but does open.
I also tried a 'run in mas90 mode' (althought it already is standard) and it prompted for credentials but did launch/open successfully.
I had another user (B) log into the machine with their windows account and it worked as designed.
I had the problem child user (A) log into another machine with their windows account and it worked as designed.
What I'm not sure of is if they use Roaming Profiles which maybe would have given user (B) local admin rights?  Do local admin rights follow a Roaming Profile?
UAC was turned all the way up, did back it off a notch but no change.
Thoughts?
Nancy



------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN


Original Message:
Sent: 06-18-2021 16:19
From: Madeline Stefanou
Subject: v2016 Standard

That worked @Jeff Fiddelman  Thank you so much.​

------------------------------
Madeline Stefanou
RKL eSolutions, LLC


Original Message:
Sent: 06-17-2021 18:43
From: Jeff Fiddelman
Subject: v2016 Standard

Hi - try deleting the Sage100 folder in my documents....

Jeff F.

------------------------------
Jeff Fiddelman
Exeplex, LLC