Sage 100

These are the only logs I have found... but trying to read them a few times, I'm not sure how much help they'd be.

Are they getting any error messages?  I might look at permissions.  Have you had access or are you just going off their feedback?

These are the only logs I have found... but trying to read them a few times, I'm not sure how much help they'd be.

Are they getting any error messages?  I might look at permissions.  Have you had access or are you just going off their feedback?

These are the only logs I have found... but trying to read them a few times, I'm not sure how much help they'd be.

A few years ago, I had a 2019 Premium upgrade where the customer was running VDI. At the 11:59:59 hour of go-live they suddenly would get "Cannot open activation key file. No valid activation found".

I have noted that one thing that worked as a temporary workaround was they renamed activate.pvx to activate.old on the local workstation ( not the server ). Then they renamed it back from activate.old to activate.pvx.

From day one, I suspected user rights, and I think - though I'm not positive - that expanding user rights may have been the resolution.

I know that this may not match exactly to your reported error so take it for what it's worth.

Thanks everyone for the input. I think we were fighting multiple issues. It seems to be solved now. They will roll out testing to a wider user group and we will see.

They were testing with a domain admin account (not the built in administrator) that was not a normal Sage user. This admin did not have proper access to the ..\Lib\keys folder on the term server. It said she had full control but Sage gave the "cannot open activation file, no valid activation found" error until she added herself to the MAS90 security group, then it worked fine. Sage did not like something they did in Group Policies that was corrected by being a member of the MAS90 group.

The are also having DNS issues. Long story short, they are a global company and because of EU GDPR they have put restrictions on DNS and it is screwing with their network. Sometimes RDP can find the server and sometimes it cannot. I think this was the randomness they were reporting. Bottom line, they had to use an IP address instead of a server name in the RDP.

This morning when we tested multiple users all using a shortcut with an IP address they were fine.

A few years ago, I had a 2019 Premium upgrade where the customer was running VDI. At the 11:59:59 hour of go-live they suddenly would get "Cannot open activation key file. No valid activation found".

I have noted that one thing that worked as a temporary workaround was they renamed activate.pvx to activate.old on the local workstation ( not the server ). Then they renamed it back from activate.old to activate.pvx.

From day one, I suspected user rights, and I think - though I'm not positive - that expanding user rights may have been the resolution.

I know that this may not match exactly to your reported error so take it for what it's worth.

They also mentioned they are using OneDrive and that everyone's My Documents folder is under OneDrive.

Does anyone know of any issues with OneDrive?

Thanks everyone for the input. I think we were fighting multiple issues. It seems to be solved now. They will roll out testing to a wider user group and we will see.

They were testing with a domain admin account (not the built in administrator) that was not a normal Sage user. This admin did not have proper access to the ..\Lib\keys folder on the term server. It said she had full control but Sage gave the "cannot open activation file, no valid activation found" error until she added herself to the MAS90 security group, then it worked fine. Sage did not like something they did in Group Policies that was corrected by being a member of the MAS90 group.

The are also having DNS issues. Long story short, they are a global company and because of EU GDPR they have put restrictions on DNS and it is screwing with their network. Sometimes RDP can find the server and sometimes it cannot. I think this was the randomness they were reporting. Bottom line, they had to use an IP address instead of a server name in the RDP.

This morning when we tested multiple users all using a shortcut with an IP address they were fine.

A few years ago, I had a 2019 Premium upgrade where the customer was running VDI. At the 11:59:59 hour of go-live they suddenly would get "Cannot open activation key file. No valid activation found".

I have noted that one thing that worked as a temporary workaround was they renamed activate.pvx to activate.old on the local workstation ( not the server ). Then they renamed it back from activate.old to activate.pvx.

From day one, I suspected user rights, and I think - though I'm not positive - that expanding user rights may have been the resolution.

I know that this may not match exactly to your reported error so take it for what it's worth.

Wayne and Dan had issues in 2021, which Sage recommended:

Option I: Stop synching the …\Documents\Sage 100 folder with One Drive

Option II: Uninstall Microsoft Edge WebView2 Runtime using Programs and Features.

They also mentioned they are using OneDrive and that everyone's My Documents folder is under OneDrive.

Does anyone know of any issues with OneDrive?

Thanks everyone for the input. I think we were fighting multiple issues. It seems to be solved now. They will roll out testing to a wider user group and we will see.

They were testing with a domain admin account (not the built in administrator) that was not a normal Sage user. This admin did not have proper access to the ..\Lib\keys folder on the term server. It said she had full control but Sage gave the "cannot open activation file, no valid activation found" error until she added herself to the MAS90 security group, then it worked fine. Sage did not like something they did in Group Policies that was corrected by being a member of the MAS90 group.

The are also having DNS issues. Long story short, they are a global company and because of EU GDPR they have put restrictions on DNS and it is screwing with their network. Sometimes RDP can find the server and sometimes it cannot. I think this was the randomness they were reporting. Bottom line, they had to use an IP address instead of a server name in the RDP.

This morning when we tested multiple users all using a shortcut with an IP address they were fine.

A few years ago, I had a 2019 Premium upgrade where the customer was running VDI. At the 11:59:59 hour of go-live they suddenly would get "Cannot open activation key file. No valid activation found".

I have noted that one thing that worked as a temporary workaround was they renamed activate.pvx to activate.old on the local workstation ( not the server ). Then they renamed it back from activate.old to activate.pvx.

From day one, I suspected user rights, and I think - though I'm not positive - that expanding user rights may have been the resolution.

I know that this may not match exactly to your reported error so take it for what it's worth.

@Steve Iwanowski Interesting. I have not been able to speak with the team that handles the OneDrive configuration, so not really sure how they have it setup or if they can disable syncing a folder.

I find it very interesting that Sage recommends uninstalling WebView!? It is required during the installation, but can be uninstalled afterwards!?

Has anyone followed this advice and uninstalled WebView on Sage 100 2022?

Wayne and Dan had issues in 2021, which Sage recommended:

Option I: Stop synching the …\Documents\Sage 100 folder with One Drive

Option II: Uninstall Microsoft Edge WebView2 Runtime using Programs and Features.

They also mentioned they are using OneDrive and that everyone's My Documents folder is under OneDrive.

Does anyone know of any issues with OneDrive?

Thanks everyone for the input. I think we were fighting multiple issues. It seems to be solved now. They will roll out testing to a wider user group and we will see.

They were testing with a domain admin account (not the built in administrator) that was not a normal Sage user. This admin did not have proper access to the ..\Lib\keys folder on the term server. It said she had full control but Sage gave the "cannot open activation file, no valid activation found" error until she added herself to the MAS90 security group, then it worked fine. Sage did not like something they did in Group Policies that was corrected by being a member of the MAS90 group.

The are also having DNS issues. Long story short, they are a global company and because of EU GDPR they have put restrictions on DNS and it is screwing with their network. Sometimes RDP can find the server and sometimes it cannot. I think this was the randomness they were reporting. Bottom line, they had to use an IP address instead of a server name in the RDP.

This morning when we tested multiple users all using a shortcut with an IP address they were fine.

A few years ago, I had a 2019 Premium upgrade where the customer was running VDI. At the 11:59:59 hour of go-live they suddenly would get "Cannot open activation key file. No valid activation found".

I have noted that one thing that worked as a temporary workaround was they renamed activate.pvx to activate.old on the local workstation ( not the server ). Then they renamed it back from activate.old to activate.pvx.

From day one, I suspected user rights, and I think - though I'm not positive - that expanding user rights may have been the resolution.

I know that this may not match exactly to your reported error so take it for what it's worth.

I haven't had this issue with 2022 and I wouldn't uninstall WebView since Microsoft expects it to be there for many services nowadays. The other Sage workaround was:

@Steve Iwanowski Interesting. I have not been able to speak with the team that handles the OneDrive configuration, so not really sure how they have it setup or if they can disable syncing a folder.

I find it very interesting that Sage recommends uninstalling WebView!? It is required during the installation, but can be uninstalled afterwards!?

Has anyone followed this advice and uninstalled WebView on Sage 100 2022?

Wayne and Dan had issues in 2021, which Sage recommended:

Option I: Stop synching the …\Documents\Sage 100 folder with One Drive

Option II: Uninstall Microsoft Edge WebView2 Runtime using Programs and Features.

They also mentioned they are using OneDrive and that everyone's My Documents folder is under OneDrive.

Does anyone know of any issues with OneDrive?

Thanks everyone for the input. I think we were fighting multiple issues. It seems to be solved now. They will roll out testing to a wider user group and we will see.

They were testing with a domain admin account (not the built in administrator) that was not a normal Sage user. This admin did not have proper access to the ..\Lib\keys folder on the term server. It said she had full control but Sage gave the "cannot open activation file, no valid activation found" error until she added herself to the MAS90 security group, then it worked fine. Sage did not like something they did in Group Policies that was corrected by being a member of the MAS90 group.

The are also having DNS issues. Long story short, they are a global company and because of EU GDPR they have put restrictions on DNS and it is screwing with their network. Sometimes RDP can find the server and sometimes it cannot. I think this was the randomness they were reporting. Bottom line, they had to use an IP address instead of a server name in the RDP.

This morning when we tested multiple users all using a shortcut with an IP address they were fine.

A few years ago, I had a 2019 Premium upgrade where the customer was running VDI. At the 11:59:59 hour of go-live they suddenly would get "Cannot open activation key file. No valid activation found".

I have noted that one thing that worked as a temporary workaround was they renamed activate.pvx to activate.old on the local workstation ( not the server ). Then they renamed it back from activate.old to activate.pvx.

From day one, I suspected user rights, and I think - though I'm not positive - that expanding user rights may have been the resolution.

I know that this may not match exactly to your reported error so take it for what it's worth.