Error on starting AOS of Dynamics AX 4.0: Cannot create ... semaph

[Ronald]

I downloaded Microsoft Dynamics AX 4.0 on 30.6.2006.

I installed it on a Windows Server 2003 Service Pack 1;
Database is located on Windows Server 2003 using MSSQL Server 2005.

Types registered successfully
Assembly exported to 'C:\Program Files\Microsoft Dynamics >AX\40\Client\Bin\Microsoft.Dynamics.ElsterTransferHandler.tlb', and the type ibrary was registered successfully
RegAsm : warning RA0000 : Registering an unsigned assembly with /codebase can cause your assembly to interfere with other applications that may be installed on the same computer. The /codebase switch is intended to be used only with signed assemblies. Please give your assembly a strong name and re-register it.
Client.4: mofcomp C:\Program Files\Microsoft Dynamics AX\40\Client\Bin\ax_trace.mof
Client.5: regsvr32 C:\Program Files\Microsoft Dynamics AX\40\Client\Bin\smmphone.ocx
Client.6: rename C:\Program Files\Microsoft Dynamics AX\40\Client\Bin\LicenseTermsEN-US.txt

I can't start the AOS because of following message:

Could not start the Dynamics Server$01-Company1 service on Local Computer.
Error 100: Cannot create another system semaphore.

Any suggestions?
Thx

[Christine Hughes (MSFT)]

The install warning shouldn't cause a problem with the AOS. Is there an error
in the event log coming from the Dynamics Object Server?

Post by Ronald
I downloaded Microsoft Dynamics AX 4.0 on 30.6.2006.
I installed it on a Windows Server 2003 Service Pack 1;
Database is located on Windows Server 2003 using MSSQL Server 2005.

Types registered successfully
Assembly exported to 'C:\Program Files\Microsoft Dynamics >AX\40\Client\Bin\Microsoft.Dynamics.ElsterTransferHandler.tlb', and the type ibrary was registered successfully
RegAsm : warning RA0000 : Registering an unsigned assembly with /codebase can cause your assembly to interfere with other applications that may be installed on the same computer. The /codebase switch is intended to be used only with signed assemblies. Please give your assembly a strong name and re-register it.
Client.4: mofcomp C:\Program Files\Microsoft Dynamics AX\40\Client\Bin\ax_trace.mof
Client.5: regsvr32 C:\Program Files\Microsoft Dynamics AX\40\Client\Bin\smmphone.ocx
Client.6: rename C:\Program Files\Microsoft Dynamics AX\40\Client\Bin\LicenseTermsEN-US.txt

Could not start the Dynamics Server$01-Company1 service on Local Computer.
Error 100: Cannot create another system semaphore.
Any suggestions?
Thx

[Tao Wang [Microsoft]]

This error message is caused by AOS not been able to connect to the database.
Please check you database (either SQL server or Oracle) connectivity.
--
Thanks,

Tao Wang
Microsoft Business Solutions
***@microsoft.com
This posting is provide "AS IS" with no warranties and confers no rights.

Post by Ronald
I downloaded Microsoft Dynamics AX 4.0 on 30.6.2006.
I installed it on a Windows Server 2003 Service Pack 1;
Database is located on Windows Server 2003 using MSSQL Server 2005.

Types registered successfully
Assembly exported to 'C:\Program Files\Microsoft Dynamics >AX\40\Client\Bin\Microsoft.Dynamics.ElsterTransferHandler.tlb', and the type ibrary was registered successfully
RegAsm : warning RA0000 : Registering an unsigned assembly with /codebase can cause your assembly to interfere with other applications that may be installed on the same computer. The /codebase switch is intended to be used only with signed assemblies. Please give your assembly a strong name and re-register it.
Client.4: mofcomp C:\Program Files\Microsoft Dynamics AX\40\Client\Bin\ax_trace.mof
Client.5: regsvr32 C:\Program Files\Microsoft Dynamics AX\40\Client\Bin\smmphone.ocx
Client.6: rename C:\Program Files\Microsoft Dynamics AX\40\Client\Bin\LicenseTermsEN-US.txt

Could not start the Dynamics Server$01-Company1 service on Local Computer.
Error 100: Cannot create another system semaphore.
Any suggestions?
Thx

[Santhosh]

Hai Ronald,
Since u have a problem that could not start the Dynamics
Server$01-Company1 service on Local Computer.....Then just try with this step.
1)Go to My Computer & right click on it and go to manage.
2)Click on Services & Application.Go to services
3)Click on Dynamics Server$01-Company1 & check whether the service status is
started.
4)Try to check this option.It shud mostly work

thank you

Post by Ronald
I downloaded Microsoft Dynamics AX 4.0 on 30.6.2006.
I installed it on a Windows Server 2003 Service Pack 1;
Database is located on Windows Server 2003 using MSSQL Server 2005.

Types registered successfully
Assembly exported to 'C:\Program Files\Microsoft Dynamics >AX\40\Client\Bin\Microsoft.Dynamics.ElsterTransferHandler.tlb', and the type ibrary was registered successfully
RegAsm : warning RA0000 : Registering an unsigned assembly with /codebase can cause your assembly to interfere with other applications that may be installed on the same computer. The /codebase switch is intended to be used only with signed assemblies. Please give your assembly a strong name and re-register it.
Client.4: mofcomp C:\Program Files\Microsoft Dynamics AX\40\Client\Bin\ax_trace.mof
Client.5: regsvr32 C:\Program Files\Microsoft Dynamics AX\40\Client\Bin\smmphone.ocx
Client.6: rename C:\Program Files\Microsoft Dynamics AX\40\Client\Bin\LicenseTermsEN-US.txt

Could not start the Dynamics Server$01-Company1 service on Local Computer.
Error 100: Cannot create another system semaphore.
Any suggestions?
Thx

[jacobn]

Hi Ronald,

I´m facing a similar problem with the same error msg. Did you ever find a
solution?

Post by Ronald
I downloaded Microsoft Dynamics AX 4.0 on 30.6.2006.
I installed it on a Windows Server 2003 Service Pack 1;
Database is located on Windows Server 2003 using MSSQL Server 2005.

Types registered successfully
Assembly exported to 'C:\Program Files\Microsoft Dynamics >AX\40\Client\Bin\Microsoft.Dynamics.ElsterTransferHandler.tlb', and the type ibrary was registered successfully
RegAsm : warning RA0000 : Registering an unsigned assembly with /codebase can cause your assembly to interfere with other applications that may be installed on the same computer. The /codebase switch is intended to be used only with signed assemblies. Please give your assembly a strong name and re-register it.
Client.4: mofcomp C:\Program Files\Microsoft Dynamics AX\40\Client\Bin\ax_trace.mof
Client.5: regsvr32 C:\Program Files\Microsoft Dynamics AX\40\Client\Bin\smmphone.ocx
Client.6: rename C:\Program Files\Microsoft Dynamics AX\40\Client\Bin\LicenseTermsEN-US.txt

Could not start the Dynamics Server$01-Company1 service on Local Computer.
Error 100: Cannot create another system semaphore.
Any suggestions?
Thx

[Mike Frank]

I also experienced, what Tao Wang said, the problem is caused by a failing database connection (The
should actually change that error message).
So verify, that the user, that the AOS service is running under is created as a login in SQL Server
and that this login is mapped to a database user on the AX database and that you have the correct
server and database name in the server config.
If you are on Oracle I can't help you with the specifics.

Mike

[Maria]

Mike

I am encountering the Same Issue and I am using SQL 2005 can you give me the
specifics how to go about this as I am having issues getting this up and
running and its critical I get it up.

Your help is very much appreciated.

Rgds

Post by Mike Frank
I also experienced, what Tao Wang said, the problem is caused by a failing database connection (The
should actually change that error message).
So verify, that the user, that the AOS service is running under is created as a login in SQL Server
and that this login is mapped to a database user on the AX database and that you have the correct
server and database name in the server config.
If you are on Oracle I can't help you with the specifics.
Mike