Try Microsoft Edge
A fast and secure browser that's designed for Windows 10
after installing the AOS für Dynamics AX2012 on a new server, I try to install der reporting services extensions. The setupprocess stops with following errormessage:
The AOS 'Name@2712' cannot be reached. Setup cannot continue.Verify that you entered the correct server information an that the AOS is running.
I have no Problem, to access via AX2012 client the AOS, but setup has problems and I cannot finish the setup.
I get this error by installing:
reporting services extensions, analysis services extensions and trace parser
Has anybody an idea, what I am doing wrong?
Same problem here :(
Can you verify if AOS was up ?
Yes AOS is up and reachable under the port which is mentioned in the error message.
I can connect to the AOS with an AX2012 client.
Maybe it's a problem with the right of the bcproxy user?
Hi, I have the same problem today.
Did you ever resolve this?
The only thing that worked for me was a new AOS installation with the required features enabled during this installation.
My workaround was following. Uninstall all AX-Components and run the CCcleaner. Delete any entry with Dynamics AX2012 in the regestry.
After that procedure, I could install everything.
Ok, tried uninstalling, reg cleanup, rebooting, reinstalling, but with the same result.
BUT, with some further invsetigating with SQL Profiler, it turned out to be a defect SP (CreateUserSession), as the initial installation never created the two SPs CreateUsersession and CreateServerSession, and I got hold of a scripted version of these, and installed them manually.
It turned out to be scripted versions from Ax2009, and after copying them from a AX2012 database everything worked just fine
Thats 10 hours down the drain, but perhaps a bit more clever !?
Thanks for your fast respons.
I meet that problem also, and find out my user account that install Reporting Services Extensions and Analysis Services Configuration does not exists in Ax 2012 users list. So I just need to create the user account into Ax 2012 and the connection is ok.
Possible answer if you were installing EP and got the error reported above: -
Ensure that the BCP account is correctly setup in the AX "System Service accounts" form. That is where the installer picks the BCP account from, and if for some reason it is not setup under the correct domain, you will get the error reported above.
To access this form: AX 2012>>System Administration Module>Setup Tab>System>System Service Accounts
Verifying "System Service accounts" worked perfectly for me ;) Thanks!!!
I had the same situation today and after the verification everything worked like a charm.
Even i have faced the same issue in installation, But i have rectified the issue.
1. This will happen due to installing of multiple AOS in server, and by default TCP/IP is 2712 and WSDL Port is 8101.
2.After installing second AOS ,it increments to TCP/IP is 2713 and WSDL Port is 8102 as follows.
3. But in our case we are not using 1 AOS and we are using 2nd AOS , at the time of installing Reporting services we are facing the problem in Port No conflits.
1. We have change the default port no and WSDL Port at client configuration -->Refresh-->Save ConfigFile.
2. Then Run the SetUp File.
Issue will resolve.
In this case we need to change the client configuration file as Port No to 2712 and save . Then run the setup you will move to next step.
Did you set up the connection for the businmess Connector properly? If the BC is connected to 2712 you will receive this problem.
Make sure you are logged into the computer that you are installing the AX component on with an account that has access to AX. If not you will get that error.
I had same error message: The AOS server@2712 cannot be reached
AOS service was running ok
Proxy account was configured ok in System Service Accounts
Solution for me was: I had to run the (AX 2012 R2) setup.exe as different user, ie. domain administrator account. I was previously using the account for which I had used for all other setups for Dynamics which had permissions to create databases etc, and access in AX, but once switched to use Domain Admin account, setup worked.
Hope that helps
Navigate to The Client Configuration from Administrative Tools, and change the Client Target to Local Client , and change the configuration to point to the correct AOS.
Navigate to Client Configuration Again, and change the Client Target to Business Connector, and point to the New AOS.
If you dont have the Client configuration, Dont select business connector, and the installation should proceed. After the installation, go back to solution 1 above.
If none of the suggested solutions work, then most likely you have a VM issue.
Running Sysprep tool on VM again and giving different machine names for Both AOS and SQL machines will resolve the problem.
When you run the Sysprep , You will have to join the machines to domain again and point AX Server Config and AX Client Config to newly changed Machine names.
the above issue solved for me by running the setup as different user.
I have same problem when installing Reporting Services on separate server with SQL. This does the trick! Thanks!
Goto System Administration > Setup > System service accounts and correct the alias and network domain in business connector proxy section. It will resolves the problem.
Most of the similar issues are because of Incorrect 'Service Account' and 'Domain Name'
Setup won't be able to connect with correct AOS.