I am facing problems in configuring role centre here. Will explain the scenario in detail…
Am working directly on the server on which
I have installed ssrs-reporting extensions/tools/analysis extensions//workflow/BC also installed and its been configured to AOS A with roll up 5
Also i have installed another AOS B with roll up 6 …now am trying to install role centre with ep framework.
Installed sharepoint services/ site created by default with port 80
It got installed successfully using the same site and by default its configured to AOS A but my intenion was to configure to AOS B.-- i dint get any option to choose the instance while running the set up…
Tho still there are some issues in regards to role centre in AOS A in processing cube-- coz when ever i login-- in role centre some parts i get “reporting services error”… is it beacuse cubes are not processed??
Also i would like to know how can i configure the role cente to AOS B??
Am i missing anything in set up part or anything regard to license…
According to my knowledge till date is that role centre comes with base package…
please correct if am wrong and also suggest me solutions.
Thanks in advance but please do help me in getting out of this problem.
You need to install the EP & role center again and make sure that if you want to install on the AOS B then it must be active in the client configuration utility.
In order to remove the SSRS error,all the cubes must be processed.For other error information please check the eventviewer & let me know.
Errors are related to cube issues and Kerberos it sounds like. Make sure Kerberos is configured correctly and you will need to perform the cube cleanup process as well, which is a pretty long, tedious, and can be difficult. Installing role centers with Kerberos is no easy task, so be prepared for a struggle. There are many steps that need to be performed.
You don’t need to uninstall the AOS A EP rather firstly you need to create a new site in WSS then install the EP for AOS B(it should be active in the configuration utility) on that site.Moreover if you want to configure EP with two different AX instances on the same server then visit the following link:
Thanks for the response.I had read your post very clearly on the first place and since in my case, all the applications ,sql server and everything are on same server only so its not reqd to go with kerberos authentication and anyways its been made off from the initial stage as we are not using it here.
And in regard to cleaning of cubes, as mentioned please go through my post i am facing challenges in cleaning the cubes.
Take the eg :Dimenions,Customers,vendors/warehouses— when i open it through visula studio to clean it, am reaching no where, all this remains locked and thats why i doubt is it a part of licensing??
Basically i need to knw whether licensing has got to do anything wth it??
I use SQL Server BIDS to clean the cubes and I have never experienced what you mention. Also when cubes are modified through VS and BIDS, you should be able to modify without any locking issue. Are you following ‘Configure Default cubes’ white paper?
Looking at the screen shot, the line starting with ‘OLE DB error…’ indicates an issue with a table. If you double click on the line you may get more detailed error message. Can you clear them first?
Before you make any changes to OLAP database, I recommend to take a backup of the whole OLAP database. Conceptually OLAP DB is similar like SQL DB. To take a backup, do backup and restore.
When you install analysis extensions, it merely deploys a pre-built OLAP DB. When you open BIDS and import it, you’ve downloaded that structure into a local project. If you backup that project, I believe that would be an adequate backup. Alternatively…if you’re just starting the cube cleanup process…a backup might not be necessary, because if you mess up, you only need to delete the “Dynamics AX” OLAP database, reinstall analysis extensions, then reimport, to get back to a fresh set of cubes to configure. Up to you.
The best thing to do is have SQL Management Studio open side-by-side with BIDS. When you are modifying objects, just copy the entire query out of BIDS into SQL management studio and run it against your AX OLTP database. Correct the errors there and then copy/paste the fixed query back into BIDS.
Note, out of the box, there are errors with the cubes that need fixed. I remember seeing CustTable.CustTable stuff where they somehow accidentally repeated objects.
in case of customer dimension : the detailed error:
OLE DB error: OLE DB or ODBC error: Invalid column name ‘PAYMIDTYPE’.; 42S22; Invalid column name ‘PAYMIDTYPE’.; 42S22; Invalid column name ‘ENTERPRISENUMBER’.; 42S22; Invalid column name ‘FORECASTDMPINCLUDE’.; 42S22; Invalid column name ‘FISCALCODE’.; 42S22; Invalid column name ‘EINVOICEEANNUM’.; 42S22; Invalid column name ‘TAXBORDERNUMBER_FI’.; 42S22; Invalid column name ‘FACTORINGACCOUNT’.; 42S22; Invalid column name ‘PAYMIDTYPE’.; 42S22; Invalid column name ‘ORGID’.; 42S22; Invalid column name ‘COMPANYIDNAF’.; 42S22; Invalid column name ‘COMPANYIDSIRET’.; 42S22.
all the mentioned fields has been removed from the cust table query and when i run the query at cust table level it works fine.
Wait…where are you processing the cubes at? Are you deploying back to the SSAS server? Or are you making changes in BIDS and then saving, then going to SQL Management Studio and trying to process.
