are u using Dynamics Ax 4.0? I had faced this situation when i tried to connect Ax 4.0 to a database which was hosted on an another machine. what i did was : first added myself to the said database as a admin user. then i created a new instance of axapta. this worked for me. hope it helps u also! regards.
________________________________ From: [email protected] on behalf of Jake Sent: Wed 12/6/2006 9:58 PM To: [email protected] Subject: [development-axapta] Re: Error 100: Cannot create another system semaphore One thing to check , that I have run into before, is to make sure that the database that you have moved, has the new machines NT_Authority login as DB owner. Might not be related, might have already checked it, but that is one idea that comes to mind. Thanks, Jake http://axatptasource.com <http://axatptasource.com> --- In [email protected] <mailto:development-axapta%40yahoogroups.com> , "cdlmalherbe01" <[EMAIL PROTECTED]> wrote: > > Hi all, > > We have 2 identical(drive letters, file systems etc) environments > (although one is a VPC and the other has a physical host). We want to > move the application and database from the one to the other on a > regular basis. > > We consistently receive the above-mentioned error message when trying > to start up the AOS. > > Any ideas regarding the purpose, type(file, registry etc) and location > (path, key etc) will be highly appreciated. > > Regards, > > Christoph Malherbe > [Non-text portions of this message have been removed]
