I installed, configured and deployed it. Everything was working fine.
The following day it was not working (we had to shutdown the server due to maintenance).
When I enter the AX client there is no more role center and I receive the message: Manage
Deployment can not run because Enterprise Portal is not deployed on this
computer.
I have found out the following explanations on the web:
1)AX Enterprise Portal does NOT currently
work on 64-bit machines
In our current work
environment we are looking at running Microsoft AX 4.0 (Axapta) along side an
installation of Microsoft Server (MOSS) 2007. The idea was to have Microsoft AX
do all the business financial's, and for any user access they would go via
SharePoint web parts and web forms. This is of course the Microsoft concept. So
we went ahead and have had MOSS running for some time now on a 64bit server,
and AX running separately on its own server. Yesterday we decided to try and
expose Enterprise Portal (the web facing part of AX) on SharePoint. After
closely following all of Microsoft's instructions we kept getting the same
message when we tried to deploy the Enterprise Portal Templates and WebParts:
"enterprise portal
cannot be deployed because windows SharePoint services is not installed on this
computer."
This made no sense at all
as we have had SharePoint running for some time now. It is of course our
Intranet. After trying almost everything and ripping all my hair out I posted on the AX news group. I am glad I did this as they gave
me the answer I (didn't want) to hear. I checked the Microsoft documentation
and it confirmed my thoughts:
"Enterprise Portal is currently
not supported on 64-bit computers."
Wow! Top work Microsoft.
You go and release some great, brand new Enterprise tools for an
organisation, however you overlook the small fact that we might be running
64-bit servers. I am so annoyed. Hopefully some kind of fix comes out for this
soon. In the meantime, I have to go deliver the bad news to the organisation...
2) http://blogs.msdn.com/emeadaxsupport/archive/2009/05/13/updating-enterprise-portal-from-dynamics-ax-2009-client-fails-on-a-64bit-microsoft-windows-server.aspx
3) Verify that the computer is not a 64-bit computer. Enterprise Portal is
currently not supported on 64-bit computers.
Lo trovi a pag. 4 del manuale dell’EP.
4) With Dynamics AX 2009 it is getting more
appropriate to have the AOS and .NET Business Connector installed on a 64bit
version of Microsoft Windows Server as both components are shipped also as
64bit (x64) versions. The Dynamics AX 2009 Client is however still a 32bit
(x86) application.
In the context of Enterprise
Portal this introduces an issue. If you have Windows SharePoint Services and
the .NET Business Connector installed as 64bit versions, you cannot use the
32bit Dynamics AX Client to deploy or update Enterprise Portal sites.
The error message you are getting
in the Dynamics AX 2009 Client when you try is:
Manage
Deployment can not run because Enterprise Portal is not deployed on this
computer.
The Dynamics AX Client is not
able to find Enterprise Portal because in order to verify if Windows SharePoint
Services is installed locally a Registry Key added by Windows SharePoint
Services is checked for existence.
If a 32bit application is however
accessing certain parts of the Registry on a 64bit Microsoft Windows Operating
System the application is usually redirected to a different Registry
location.
And exactly this is also
happening for the Dynamics AX Client, that is looking for the Registry Key at
the wrong place (see also: 32-bit and
64-bit Application Data in the Registry).
This information is more or less
meant as explanation for the strange error message. Fixing the
Registry Key lookup will not make deployment possible, because after
ensuring Enterprise Portal is locally installed the Dynamics AX Client is
loading several other DLLs. Unfortunately a 32bit process cannot load any 64bit
DLL (see also: Running
32-bit Applications) which would be needed in our case.
