I have encountered an error from AOS service last few days as reintall the Dynamics Ax 4.0, the error message as below:
Could not start the Dynamics Server$01-Company1 service on Local Computer.
Error 100: Cannot create another system semaphore.
i intalled at the below environment:
• Windows XP Professional (SP2+)
• SQL Server 2005
At the meantime, i got some enquiries for expertise and tried my best to troubleshoot this error. Finally, i fixed it successfully. During the time of fixing this thing, i have got one solution from Microsoft website was telling me "Please try again later" for this "semaphore error".
What does it means for this "Please try again later"? There is no specific guideline on how to fix the error. It is very funny and inevitable guideline would turn a green line to solve the problem.
From my troubleshooting and research; this "semaphore error" is a general error indicating that the AOS cannot connect to the database for some reason. The following rules must be followed:
1. Check your database connectivity
2. Ensure the user has appropriate permissions to access the database files when running
the AOS service (normally NetworkService).This means that the following roles
should be assigned to the specific database
• db_ddladmin
• db_datareader
• and db_datawriter.
3. Ensure the user has enough rights to access the file server/folder
After you have setting up the permissions , now you may follow suggestion from Microsoft "Please try again later".
Wednesday, January 9, 2008
AOS fails to start for Dynamics Ax 4.0 intallation
Posted by November Princess at 7:12 PM
Labels: admin, AOS, Axapta, database, Dynamics Ax, Error 100, Goods and Services Tax, microsoft, permission, problem, semaphore error, SQL Server, system semaphore, windows XP
Subscribe to:
Post Comments (Atom)
1 comment:
Good summary. If you're using an existing database and it still doesn't work, you may also need to grant execute permission on 2 stored procedures (create*sessions).
Post a Comment