Do you have more than one company? Does your screen do anything other than adding a button to print a report? Are you loading the screen dynamically or did you install and drop the screen into your VB6 application? Have you tried deleting any .exd files on the workstation?

Hi all,

Have this issue when running a macro. Had it at two different clients with different versions of Sage 300.
One is V6 and the other is 2012 (would need to confirm) and all use SQL.

You login into Sage 300 and try to run the macro and get the error about you do not have a licence to use this product on MC databases but another login dialogue box opens and you re-enter the credentials and the sign on manager comes up with the same error.
You then close and re-open another company or same one you get the error through Sage itself (hope that makes sense)

If they restart the server (using local install) or log off completely and log back in (RDP) it clears the error.

Any ideas?

TYIA
Debbie

Hi all,

Have this issue when running a macro. Had it at two different clients with different versions of Sage 300.
One is V6 and the other is 2012 (would need to confirm) and all use SQL.

You login into Sage 300 and try to run the macro and get the error about you do not have a licence to use this product on MC databases but another login dialogue box opens and you re-enter the credentials and the sign on manager comes up with the same error.
You then close and re-open another company or same one you get the error through Sage itself (hope that makes sense)

If they restart the server (using local install) or log off completely and log back in (RDP) it clears the error.

Any ideas?

TYIA
Debbie

What does the macro do?

One of the macros auto invoices and the other is a GL data extraction.

I've seen this before but can't remember what causes it. Check your macro references and confirm that your path environment variable is correct (doesn't point to an old Sage version, for example).

We also encountered the same issue recently. Not sure was it resolved.

If yes, could you share some lights.

Thanks

Someone posted the following on a different forum (http://www.tek-tips.com/viewthread.cfm?qid=1774001):

I have seen this issue at various clients that are using RDP to access Sage. After a great deal of research i discovered that the issue is caused by windows being slow to copy over registry keys for the user when they log in. I normally see this the most at clients using RDP and running Sage as part of their login. It is not limited to this as i also have it with full desktop users but not as much. Clicking the Sage icon several times does eventually get it to run.
This is what I found and used. I placed this is a batch files that runs when the user loggs in. This might not be your issue but it fixed mine!
#
# Author: Matthew Arnold ([email protected])
# Licese: This file may be freely distributed as long as it remains unchanged.
# Copyright: Copyright ©2014 Matthew Arnold. All Rights Reserved.
# Used to start Sage300 when you do not have a license to run this product is being displayed
# Issue is probably caused by userinit.exe not copying the user reg keys over before the accpac.exe runs

$userSID = ([wmi]"win32_userAccount.Domain='$env:UserDomain',Name='$env:UserName'").SID

Copy-Item -Path "HKLM:\SOFTWARE\Wow6432Node\ACCPAC International, Inc.\ACCPAC\Configuration" -Destination "HKCU:\SOFTWARE\ACCPAC INTERNATIONAL, INC.\ACCPAC" -Recurse -Force
Copy-Item -Path "HKLM:\SOFTWARE\Wow6432Node\ACCPAC International, Inc.\ACCPAC\Configuration" -Destination "Registry::HKEY_Users\$userSID\Software\ACCPAC INTERNATIONAL, INC.\ACCPAC" -Recurse -Force

$path = Get-Item -Path "HKCU:\SOFTWARE\ACCPAC INTERNATIONAL, INC.\ACCPAC\CONFIGURATION" | Get-ItemProperty -Name "Programs" | Select -ExpandProperty "Programs"
& "$path\Runtime\AccPac.exe"

Hi Debbie

2 of my clients are having the same issue as you when they running the macro.

Did you manage to resolve it? Thanks

Hi Sam,
I haven't tried the fix Phil posted yet.
I forwarded it to one of our client's IT team.
Haven't heard anything though.

Rgds
Debbie