olap4j errors after update Microsoft Analysis Server - ssas

I use olap4j 1.2.0 and olap4j-xmla 1.2.0 to request a Microsoft Analysis Server 11.0.5058.0 cube with MDX requests.
No problem at all.
Since a migration to Microsoft Analysis Server 14.0.249.14 (New cube, but same Cube) an error occurs:
org.olap4j.OlapException: Internal error: hierarchy '[HierarchyName]' not found in cube 'CUBE'
In debug mode I also observe when browsing the cube that the XmlaOlap4jDimensions objects do not contain hierarchies when they should.
The same queries work perfectly with Microsoft SQL Server Management Studio.
Thank you for your help.

Related

Data Flow Task : Error ODBC Source Failed Validation and returned error code 0x80004005

I am trying to migrate data from PostgreSQl to SQL Server, for which I have created a SSIS package in Visual Studio 2019 using OBDC Source (for connecting to PostgreSQL) and OLE DB Destination (to connect SQL Server in Visual Studio).
I was able to successfully establish the connection in both database and transfer the data in visual studio.
To create a SQL Agent job, I tried creating a SSISDB catalog in SQL Server under integration service catalogs and deployed my SSIS package in Visual Studio 2019 (Note: I tried to change Target server version in Visual studio same as SQL server version).
Although the execution happens successfully in Visual Studio but in SQL server when I execute the package in SSMS, it is throwing an error (highlighted in title and in the screenshot).
How to resolve this issue? Any insight on this will be very helpful.
Regards,
PKR
Things I have tried
I tried to check my access to SQL server, the error is happening even after gaining complete admin level access.
I tried to change the target server version in Visual Studio to match with SQL server version yet it didn't help.

What are the connection managers to connect to an external SSAS cube in SSDT 2012

We are experiencing issues when executing an SSIS package from a SQL Server job. However, when we execute the package locally, it is successful. The package connects to an external SSAS cube using MDX. I have attached the error message below. The connection manager is OLE DB Provider for Analysis Services 11.0. We can successfully ping the external site where the cube is located from the server
with the job.
Unfortunately, at this point, it appears that the issue is related to the windows server core install. I found this link which outlines the issues related to core - http://technet.microsoft.com/en-us/library/ee441257(v=ws.10).aspx. We can get the job to execute from a Windows Server with a full version install, but not on the core install.

Issue regarding SSAS features while trying to process a cube in BIDS

I recently adventured into BI and am currently trying to process a cube onto the ssas (by using a BIDS SASS project). I originally had the SQL 20008 R2 Standard version and therefore got the following error:
"Errors related to feature availability and configuration: The 'Perspectives' feature is not included in the '64 Bit Standard' edition of Analysis Services"
So...i downloaded the Enterprise version of SQL 2008 R2, upgraded my whole instance, restarted and proceeded to try again. STILL i got the same issue over again...
What could i do to fix this?
Thanks in advance!
The issues with Enterprise version.Use the Standard version.
Keep one thing in your mind give sysadmin permissions to NT AUTHORITY\NETWORK SERVICE
Thanks
Try restarting the SQL SERVER ,SQL SERVER ANALYSIS SERVICES from Services.msc . I got it resolved the same issue by doing this.

Connection failing when I try to process a cube in BIDS

There is probably a simple answer to this question but I do not have much experience with SQL Server/SSAS. I can connect to my local server PCNAME\SQLEXPRESS in SQL Server 2008. On that server I have made a database, some dimension tables, and a fact table that I intend to build a cube from.
I have been following tutorials on the internet on how to build a cube. I can successfully make a data source that connects to PCNAME\SQLEXPRESS, as well as make a data source view from it.
The problem is that after I build the cube, I get A connection cannot be made. Ensure that the server is running. and cannot process the cube. BIDS is displaying the star schema of my tables just fine, recognizes the relationships via foreign keys, etc... so I figured the server was running since it could access all of that data.
Does anyone know why this is happening, and if my server really isn't running can someone tell me how to start it? I am using SQL Server 2008 R2.
Thanks,
Logan
edit: I just tried to change the server name to PCNAME\SQLEXPRESS instead of localhost in the Properties->Deployment option menu. I get A connection cannot be made to redirector. Ensure that 'SQL Browser' is running.
I solved this problem - for people that find this page on Google in the future: when I first installed SQL Server, the SSAS part failed to install. I uninstalled SQL Server and when I reinstalled, I looked deeper into the issue. Apparently one of the services needed to run SSAS has a weird bug where it cannot be started if your Event Log is full. I finished the installation of SQL Server, cleared my Event Log (Administrative Tools -> Event Viewer -> Click Each Log and go to Action -> Clear All Events), and then started the SSAS service in the SQL Configuration Manager.
You can start by going to "Programs->Microsoft SQL Server 2008->Configuration Tools->SQL Server Configuration Manager". Once there, you need to start the services "SQL Server", "SQL Server Analysis Services", and maybe try starting "SQL Server Browser", though I believe that is not necessary.

Problems getting SQL Server 2005 Project REAL to work in SQL Server 2008 R2

I'm learning how to use SQL Server 2008's Analysis Services, and discovered Microsoft's Project Real. It looks like a great way to learn how to use Business Intelligence Tools on a real-world example.
Unfortunately, Project REAL's use SQL Server 2005 databases, and I get an error message when I try to attach them using SQL Server 2008 Management Studio: "Unable to open the physical file. Operating system error 5: Failed to retrieve text for this error. Reason: 15105".
Has anyone managed to get Project REAL working with SQL Server 2008 R2?
The solution is to run SSMS as Adminstrator (i.e. "Run as Administrator"). Then you have permission to attach databases.