Hi All,
For those who are trying to learn MicroStrategy with MicroStrategy 10 and Microsoft SQL Server as database, you are likely to get the following issue discussed below and today we will see how to resolve the same.
As of what I have seen with MicroStrategy 10 when using Configuration Wizard it does not detect the already available system DSN's in your machine. So you would need to configure the DSN with the help of the connectivity wizard.
And when I tried test connecting with connectivity wizard got the below error....
Connection test failed: Error in testing connection: Connect failed.
Error type: Odbc error. Odbc operation attempted: SQLDriverConnect.
[HY000:0: on SQLHANDLE] [MicroStrategy][ODBC SQL Sserver Wire Protocol
driver]General error. recvfrom failed:10054
Cause:
SQL Server Browser service was not running. This service needs to be started when connecting to SQL Server named instances.
Resolution: Follow the steps given in the below article
https://technet.microsoft.com/en-us/library/ms191454%28v=sql.105%29.aspx
Then post the above step I got the below error
Connection test failed: Error in testing the connection: Connect faild.
Error type: ODBC error. Odbc operation attempted: SQLDriverConnect.
[HY000:0: on SQLHANDLE] [MicroStrategy][ODBC SQL Sserver Wire Protocol
driver] General error. not TCP/IPServerName; InstanceName; SQLExpress
IsClustered; No; Version; 11.0.2100.60;;
Cause:
The driver communicates using the TCP/IP network protocol which needs to be enabled for the database.
Resolution: Follow the steps given in the below article
https://msdn.microsoft.com/en-us/library/bb909712%28v=vs.90%29.aspx
Final challenge was very simple... it was just to configure the DSN connection with the MicroStrategy Connectivity Wizard. The thing here is that the MicroStrategy connectivity wizard expects the database username and password to configure the DSN connection successfully unlike the older approach for database hosted in the local machine with Windows/NT authentication.
To overcome this we would need to just provide the DB credentials for the Metadata.
Thats it we are done!
Bottom Line:
From MicroStrategy 10 onwards the local system DSN configured in the Intelligence Server machine is not detected by the configuration wizard and it requires MicroStrategy Connectivity Wizard to create the connection to the Metadata.
For those who are trying to learn MicroStrategy with MicroStrategy 10 and Microsoft SQL Server as database, you are likely to get the following issue discussed below and today we will see how to resolve the same.
As of what I have seen with MicroStrategy 10 when using Configuration Wizard it does not detect the already available system DSN's in your machine. So you would need to configure the DSN with the help of the connectivity wizard.
And when I tried test connecting with connectivity wizard got the below error....
Connection test failed: Error in testing connection: Connect failed.
Error type: Odbc error. Odbc operation attempted: SQLDriverConnect.
[HY000:0: on SQLHANDLE] [MicroStrategy][ODBC SQL Sserver Wire Protocol
driver]General error. recvfrom failed:10054
Cause:
SQL Server Browser service was not running. This service needs to be started when connecting to SQL Server named instances.
Resolution: Follow the steps given in the below article
https://technet.microsoft.com/en-us/library/ms191454%28v=sql.105%29.aspx
Then post the above step I got the below error
Connection test failed: Error in testing the connection: Connect faild.
Error type: ODBC error. Odbc operation attempted: SQLDriverConnect.
[HY000:0: on SQLHANDLE] [MicroStrategy][ODBC SQL Sserver Wire Protocol
driver] General error. not TCP/IPServerName; InstanceName; SQLExpress
IsClustered; No; Version; 11.0.2100.60;;
Cause:
The driver communicates using the TCP/IP network protocol which needs to be enabled for the database.
Resolution: Follow the steps given in the below article
https://msdn.microsoft.com/en-us/library/bb909712%28v=vs.90%29.aspx
Final challenge was very simple... it was just to configure the DSN connection with the MicroStrategy Connectivity Wizard. The thing here is that the MicroStrategy connectivity wizard expects the database username and password to configure the DSN connection successfully unlike the older approach for database hosted in the local machine with Windows/NT authentication.
To overcome this we would need to just provide the DB credentials for the Metadata.
Thats it we are done!
Bottom Line:
From MicroStrategy 10 onwards the local system DSN configured in the Intelligence Server machine is not detected by the configuration wizard and it requires MicroStrategy Connectivity Wizard to create the connection to the Metadata.
