Problem in using MyDirect with SSAS 2005
-
- Posts: 9
- Joined: Mon 29 Oct 2007 16:53
Problem in using MyDirect with SSAS 2005
Hi!
I was very excited to see that this is the only driver that allowed me to get as far as I did when I used this with SSAS 2005. I was able to create Data Source, Data Source View and even define the Dimension/Facts etc.
When I went to deploy, I got the following message:
Error 1 Errors in the high-level relational engine. The following exception occurred while the managed IDbCommand interface was being used: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '[brs_mailing_dimension].[message_id] AS [brs_mailing_dimensionmessage_id0_0] F' at line 3. 0 0
Can you please help in understanding why I might be getting this message and how to over this?
Thanks!
Guran
I was very excited to see that this is the only driver that allowed me to get as far as I did when I used this with SSAS 2005. I was able to create Data Source, Data Source View and even define the Dimension/Facts etc.
When I went to deploy, I got the following message:
Error 1 Errors in the high-level relational engine. The following exception occurred while the managed IDbCommand interface was being used: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '[brs_mailing_dimension].[message_id] AS [brs_mailing_dimensionmessage_id0_0] F' at line 3. 0 0
Can you please help in understanding why I might be getting this message and how to over this?
Thanks!
Guran
-
- Posts: 9
- Joined: Mon 29 Oct 2007 16:53
The file CoreLab.MySql.xsl file exists in the "%ProgramFiles%\Microsoft SQL Server\MSSQL.\OLAP\bin\Cartridges\" folder on the PC where Analysis Services resides. Is that sufficient? I even tried creating this directory in the exact same folder where you'd suggested. But no luck. Any help will be appreciated.
-
- Posts: 9
- Joined: Mon 29 Oct 2007 16:53
-
- Posts: 9
- Joined: Mon 29 Oct 2007 16:53
I just noticed that I'm now getting a different error:
Error 1 Errors in the high-level relational engine. The following exception occurred while the managed IDbConnection interface was being used: License not valid. Please view "Licensing" topic in MySQLDirect .NET documentation for details or contact Core Lab technical support.. 0 0
As soon as I'm able to show the proof of concept, we definitely intend to buy these drivers. Is the licensing an issue?
Error 1 Errors in the high-level relational engine. The following exception occurred while the managed IDbConnection interface was being used: License not valid. Please view "Licensing" topic in MySQLDirect .NET documentation for details or contact Core Lab technical support.. 0 0
As soon as I'm able to show the proof of concept, we definitely intend to buy these drivers. Is the licensing an issue?
-
- Posts: 9
- Joined: Mon 29 Oct 2007 16:53
-
- Posts: 9
- Joined: Mon 29 Oct 2007 16:53
I tried to install the 4.25 driver again (after uninstalling the previous installation),
Noticed that the file CoreLab.MySql.xsl file DOES NOT exist in the "%ProgramFiles%\Microsoft SQL Server\MSSQL.\OLAP\bin\Cartridges\"
Copied that file there manually.
Rebooted the computer.
Tried to build a new project and got the same error again:
Error 9 Errors in the high-level relational engine. The following exception occurred while the managed IDbConnection interface was being used: License not valid. Please view "Licensing" topic in MySQLDirect .NET documentation for details or contact Core Lab technical support.. 0 0
Noticed that the file CoreLab.MySql.xsl file DOES NOT exist in the "%ProgramFiles%\Microsoft SQL Server\MSSQL.\OLAP\bin\Cartridges\"
Copied that file there manually.
Rebooted the computer.
Tried to build a new project and got the same error again:
Error 9 Errors in the high-level relational engine. The following exception occurred while the managed IDbConnection interface was being used: License not valid. Please view "Licensing" topic in MySQLDirect .NET documentation for details or contact Core Lab technical support.. 0 0
-
- Posts: 9
- Joined: Mon 29 Oct 2007 16:53
More information I can provide is that in my AS 2005 project:
I am able to setup/test the connection just fine
I am able to use the Data Source Views wizard to create a DSV just fine
I am able to run the Cubes wizard just fine and create Fact/Dimension tables just fine
If I view the data in any of the tables, it works fine and does show me the data
Just that when I try to deploy, I get the error mentioned above along with other failure errors which are due to the above mentioned error.
I am able to setup/test the connection just fine
I am able to use the Data Source Views wizard to create a DSV just fine
I am able to run the Cubes wizard just fine and create Fact/Dimension tables just fine
If I view the data in any of the tables, it works fine and does show me the data
Just that when I try to deploy, I get the error mentioned above along with other failure errors which are due to the above mentioned error.
-
- Posts: 9
- Joined: Mon 29 Oct 2007 16:53
I am sure that CoreLab.MySql.EnterpriseLibrary.dll has nothing to do with SSAS. Probably, you have changed something (restarted service, reopened VS, etc.) and this action did the trick. Actually, I had the same problems as you. But I haven't figured out yet what causes licensing problem. After one or two reinstalls of MyDirect .NET I got it to work.
We will investigate this problem deeply, but anyway MyDirect .NET does work with SSAS.
We will investigate this problem deeply, but anyway MyDirect .NET does work with SSAS.
-
- Posts: 9
- Joined: Mon 29 Oct 2007 16:53