RE: [Axapta-Knowledge-Village] "Insufficient licence rights" erro r starting Axapta for 2nd user onwards

[Steve Wright]

Hi Jim
 
We solved this issue using a windows registry setting on 
the server.
 
Axapta Technet article 9091 talks about Opportunistic Locking in 
Windows.
 
 
What I do not understand is how this is only a problem for 
Axapta 3 axdat.udb file.   Ax2.5 works fine.
Regards,
Steve.
 
 
 
 
 
 
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters\OplocksDisabled 
REG_DWORD 0 or 1Default: 0 (not disabled)NOTE: The OplocksDisabled 
registry value configures Windows clients toeither request or not request 
opportunistic locks on a remote file.You can also deny the granting of 
opportunistic locks by setting thefollowing registry entry to 
0:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\ParametersEnableOplocks 
REG_DWORD 0 or 1Default: 1 (Enabled by Default)NOTE: The 
EnableOplocks value configures Windows-based servers(including Workstations 
sharing files) to allow or deny opportunisticlocks on local 
files.


From: Jim Jo [mailto:[EMAIL PROTECTED] 
Sent: Thursday, 7 October 2004 12:25 PMTo: 
[EMAIL PROTECTED]Subject: RE: 
[Axapta-Knowledge-Village] "Insufficient licence rights" erro r starting Axapta 
for 2nd user onwards

Hi Steve,
 
  Jus curious ! have you solved the problem. If so how ? Share ?
 
JimMalcolm Burtt 
<[EMAIL PROTECTED]> wrote:

  
  
  
  

  

  Ah, well. 
  Buy BackupExec instead then. :-) 
  Although it 
  considered the .udb file a corrupt file (so I just excluded it from backup) at 
  least it didn't have your problem. Must be very annoying that ArcServe can't 
  cope with it. If the ArcServe agent is anything like the BackupExec one, it 
  isn't cheap.
   
  Malcolm.
  
    -----Original Message-----From: David VanEchaute 
    [mailto:[EMAIL PROTECTED]Sent: 06 October 2004 14:27To: 
    '[EMAIL PROTECTED]'Subject: RE: 
    [Axapta-Knowledge-Village] "Insufficient licence rights" erro r starting 
    Axapta for 2nd user onwards
    
    Hi,
     
    Tried 
    that too before removing the Agent. It didn't help to exclude the file. 
    Would be nice if it did though.
     
    David
     
    -----Original 
    Message-----From: Malcolm 
    Burtt [mailto:[EMAIL PROTECTED]Sent: Wednesday, October 06, 2004 8:26 
    AMTo: 
    [EMAIL PROTECTED]Subject: RE: [Axapta-Knowledge-Village] 
    "Insufficient licence rights" erro r starting Axapta for 2nd user 
    onwards
     
    Hi
     
    If 
    the ArcServe open file agent is the cause of the problem then maybe you 
    could get the backup to exclude the .udb file. As you say, its not needed 
    anyhow as Axapta will rebuild it if it needs to. That way you can keep 
    the benefits of the open file agent without the pain.
     
    Regards
     
    Malcolm 
    Burtt 
    -----Original 
    Message-----From: David 
    VanEchaute [mailto:[EMAIL PROTECTED]Sent: 06 October 2004 14:21To: 
    '[EMAIL PROTECTED]'Subject: RE: [Axapta-Knowledge-Village] 
    "Insufficient licence rights" erro r starting Axapta for 2nd user 
    onwards
                
    Hi,
     
    I 
    had the same exact problem. I could log in directly on the application 
    server but yet only one client at a time. I shut down the ArcServe services 
    but it didn't matter. I worked on the problem for weeks before trying to 
    remove\uninstalling the OpenFile Agent. The OpenFile agent locks the udb 
    file somehow and it will only allow one client on. The only file I don't get 
    during the nightly backup now that I have removed the OpenFile agent is the 
    .udb file which isn't a big deal because it is rebuilt if missing anyways. 
    The only way I could get more than 
    one 
    client on after a backup had ran was the get everyone off the system and 
    delete the .udb file and let it rebuild. It would work fine again until the 
    next backup had occurred. Something happens to the .udb file during each 
    backup that keeps more than one client PC from being able to access Axapta. 
    I would uninstall OpenFile agent and get everyone off the system, rename the 
    .udb file to .old and let it rebuild. Take a look at the backup after having 
    removed OpenFile agent and see if you cant backup any "important" files that 
    absolutely need backed up every night without 
    exception.
     
    GoodLuck,
     
    David
     
     
    -----Original 
    Message-----From: Steve 
    Wright [mailto:[EMAIL PROTECTED]Sent: Wednesday, October 06, 2004 8:20 
    AMTo: 
    [EMAIL PROTECTED]Subject: RE: [Axapta-Knowledge-Village] 
    "Insufficient licence rights" erro r starting Axapta for 2nd user 
    onwards
     
    Hi 
    David
     
    Thank 
    you for your post.
     
    I 
    stopped the ArcServe service (via the Windows 2000 Server "Services" 
    icon).   There were about 4 services of which one is the Open File 
    Agent.
     
    The 
    ArcServe backup job is set to run at 7pm each night, so even with this 
    service running, I would not expect it to lock the axdat.udb file until the 
    backup job started at 7pm.
     
    My 
    question is, Is shutting down the service as good as uninstalling 
    ArcServ?
     
    Thanks
    Steve
     
    
    
    
    From: David VanEchaute 
    [mailto:[EMAIL PROTECTED] Sent: Wednesday, 6 October 2004 8:56 
    PMTo: 
    '[EMAIL PROTECTED]'Subject: RE: [Axapta-Knowledge-Village] 
    "Insufficient licence rights" erro r starting Axapta for 2nd user 
    onwards
                
    Hi,
     
    If 
    you have ArcServe OpenFile agent loaded on the Server the Axapta application 
    files are located on you need to completely 
    
    uninstall 
    the agent. The ArcServe SQL agent doesn't cause a problem with the Axapta 
    application but the OpenFile agent locks the .udb 
    file.
     
    David
     
     
    -----Original 
    Message-----From: Steve 
    Wright [mailto:[EMAIL PROTECTED]Sent: Wednesday, October 06, 2004 7:08 
    AMTo: 
    [EMAIL PROTECTED]Subject: RE: [Axapta-Knowledge-Village] 
    "Insufficient licence rights" erro r starting Axapta for 2nd user 
    onwards
     
    Hi 
    Tobias
     
    Thank 
    you for your post.
     
    We 
    have taken read-only off all of the application folders...but I am unsure 
    about the client folders.
     
    Thanks
    steve
     
    
    
    
    From: Andrae, Tobias 
    [mailto:[EMAIL PROTECTED] Sent: 
    Wednesday, 6 October 2004 5:59 PMTo: 
    [EMAIL PROTECTED]Subject: AW: [Axapta-Knowledge-Village] 
    "Insufficient licence rights" error starting Axapta for 2nd user 
    onwards
    Are 
    there any read-only-flags in your Application directory? Try to reset 
    everything to read&write, including subdirectories. Important: Do this 
    for zhe user that runs that Axapta client ;-))
    Hth 
    Tobias
     
    -----Ursprüngliche 
    Nachricht-----Von: Steve 
    Wright [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 6. Oktober 2004 
    11:21An: 
    [EMAIL PROTECTED]Betreff: [Axapta-Knowledge-Village] 
    "Insufficient licence rights" error starting Axapta for 2nd user 
    onwards
     
    I 
    have a situation running Ax3 SP3 2-tier where I cannot get more than 1 
    person logged into Axapta.
     
    The 
    technet discussion below is exactly the same problem.   The 
    resolution was to shutdown ArcServe backup software but we have stopped all 
    services and still nothing.
     
     
    Has 
    anyone a suggestion?
    Thanks
    Steve
     
     
     
    Axapta 
    Technet 7316.4 
    
     
    Insufficient 
    licence rights. Can not start Axapta as more users are running the system 
    than the purchased rights allows".My license code in Axapta is for 20 
    users and when more than 1 user tries to connect the Axapta we get the 
    message above.
    We check the 
    permission (full access) on the Axapta folder and defined as 
    shared.
    We can 
    concurrently run Axapta on Axapta application server (Axapta install+ Sql 
    Server install same machine) and we can run one client machine, then no 
    other machine can connect, we receive the message that we can not login 
    because there are no available liceneses on any other machine . If 
    we log off client Machine 1 then we can start from client machine 2 but no 
    other machine then can login, or sometimes If we can run Axapta on server, 
    client machine 1, client machine 2 then no other client machine can 
    connect.
    Sharing 
    the knowledge on Axapta. 
    Sharing 
    the knowledge on Axapta. 
    Sharing 
    the knowledge on Axapta. 
    Sharing 
    the knowledge on Axapta. 
    Sharing 
    the knowledge on Axapta. 
    Sharing 
    the knowledge on Axapta. 
    Sharing 
    the knowledge on Axapta. Sharing 
    the knowledge on Axapta. 
  Sharing the knowledge on 
  Axapta. 


Do you Yahoo!?vote.yahoo.com - Register 
online to vote today! Sharing the knowledge on Axapta. 



Sharing the knowledge on Axapta.








Yahoo! Groups Sponsor


  ADVERTISEMENT 












Yahoo! Groups Links

To visit your group on the web, go to:http://groups.yahoo.com/group/Axapta-Knowledge-Village/ 
To unsubscribe from this group, send an email to:[EMAIL PROTECTED] 
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.