Troubleshooting Development (Analysis Server)
What problem are you having?
A database on a server (in ADOMD.Catalogs) does not appear in the DSO.Server.MDStores collection and cannot be deleted.
Cause: The repository is corrupted or changed, or the server failed during a transaction.
Solution: To remove the database and free the used disk space, use Decision Support Objects (DSO) to create a database with the same name, and then use the Remove method of the clsServer object to immediately delete it.
Received the "License information for this component not found" message for Microsoft® Visual Basic® controls.
Cause: Microsoft SQL Server™ 2000 Analysis Services installs controls with a license for run-time use. Visual Basic was installed after Analysis Services and failed to install these components correctly for use in the design environment.
Solution: On the Internet, go to the Microsoft Product Support Services Web site, http://search.support.microsoft.com/kb/c.asp.
On the search screen:
- Under My search is about, select Visual Basic.
- Under I want to search by, select Specific article ID number.
- Under My question is, type Q181854.
- Click Find, and then follow the instructions in the article.
After selecting the Optimize Schema menu command in Cube Editor, received the "The cube schema is already optimized" message. Subsequent saving of the cube results in the following message: "A loop was detected in the schema. Please remove the extra joins".
Cause: Optimizing the schema through the Optimize Schema command may not have deleted a join that is not valid between a fact table and a dimension table or between two dimension tables for a snowflake-schema dimension.
Solution: In the schema view of Cube Editor, identify joins that are not valid, and then remove them with the Remove Join command. For more information about optimizing cube schemas, see Optimizing Cube Schemas.
Cause: A cube with an optimized schema may not display all available tables for use when you specify drillthrough options. For more information, see Optimizing Cube Schemas.
Solution: You can join a table to the schema for drillthrough when you specify drillthrough options. Add the table and define a SQL WHERE clause to establish the join.
After an application obtains a lock with the LockObject method on a DSO object, other applications sharing the DSO object behave unexpectedly when referring to certain properties or methods of the object.
Cause: The originating application may have destroyed the original DSO object. If so, all other applications will have references that are not valid to that object, because DSO automatically refreshes updated objects after a lock is obtained.
Solution: Use the Parent property of the DSO object to check the validity of the object reference. An object reference that is not valid will have its Parent property set to Nothing.