Hello everyone! If the steering
Analysis Services 2000 via the namespace DSO is extremely simple, as we saw earlier, it is nevertheless surprising that the connection is done properly without a connection string well formed.
Indeed, only the server name is provided in connection with the DSO. The connection string is then retrieved by the registry, decrypted, and provides access to the Analysis Services Repository.
In practice, Analysis Services stores two encrypted connection strings in the registry:
- a first string for local connections:
Provider = Microsoft.Jet.OLEDB.4.0; Data Source = C: \\ Program Files \\ Microsoft Analysis Services \\ Bin \\ Msmdrep.mdb
- a second channel for remote connections:
Provider = Microsoft.Jet.OLEDB.4.0; Data Source = \\ \\ \u0026lt;servername>
You'll notice here that the Repository for Analysis Services 2000 is stored in an Access database.
From SP3, a bug appeared on the connection with the DSO. Unfortunately, the HOTFIX realize at the time was not included in Service Pack 4 Analysis Services 2000.
Indeed, the encryption of the remote connection string fails. It follows that the connection string decrypted by the DSO is invalid.
Thus, when a remote connection via DSO, the following message may be granted:
The Can not connect to repository. OLAP Server:
The misunderstanding often comes from the fact that the same action performed with a local connection is not a problem, a blurring Just over the tracks of correction.
A bug so insidious, for which there is a HOTFIX here. The reference description is HOTFIX KB907323 .
More simply, you can change the value of containing the key chain remote connection by performing a right click on the name of your server in Analysis Manager in the menu "Edit Repository Connection String".
course, it is totally unnecessary to pass this HOTFIX if you have no problems ;-)
0 comments:
Post a Comment