Invalid Semantic Model

Hello

While following the instructions on the tutorial "Creating a Report Model Based on an Analysis Services Cube", I got this error when trying to create the report model:

The semantic model is not valid. Details: The element 'Entity' in namespace 'http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling' has incomplete content. List of possible elements expected: 'IdentifyingAttributes' in namespace 'http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling'. (InvalidSemanticModel)

I have tried to use a SSAS cube of my own, which is working fine and tried to create a model based on it so I can create ad-hoc reports.

Parameters chosen on the data source creation:

Connection Type: Microsoft SSAS

Connection String: Data Source=localhost\SQL2005;Initial Catalog="TAP Analysis"

Connect Using: Windows Integrated Security

To SSAS using the Microsoft SQL Server Management Studio, I use Windows Authentication.

In the model creation, I have tried to switch to other credentials, but the error still remains... Can you help me with this one?

Thanks

Andr

I have the solution.

After the opening of the case in microsoft, this problem was analysed by the support teams and I got an answer today.

The problem seems to be one relationship i've built between a fact table and a dimension table.

In the current release of SSRS and SSAS, a relationship from one entity to another is implicitly to the key of the destination entity.

I was using a Time dimension (the dimension key was "day") and I was building a relationship based on the attribute "month".

So, the relationship was ignored and my fact table had no relationships and therefore, no identifyers, and that was the cause of the problem.

The solution for my case was relating the month to the first day of the month in the Time table.

I was told Microsoft plans to lift such limitation on the next releases.

Hope this helps for anyone with similar problems

Andr

Invalid object name 'OlapObjects'

Hi,

I installed the analysis server 2005 version.

When I'm trying to get the databases in an OLAP server using DSO it gave me the error, "Invalid object name 'OlapObjects' "

Following is my vb code.

dsoServer.Connect (sServer)
For i = 1 To dsoServer.MDStores.count
Set dsoTempDB = dsoServer.MDStores(i)
ComboboxName.AddItem dsoTempDB.name
Next

I tried installing Analysis server 2005 several times, and installed service pack 2 as well. But still I get this error.

Please help.

Thank you.

First. You should really take a look at using AMO object model to perform any tasks with Analysis Services 2005 . AS2005 is completely different from AS2000 and AMO is way better way to perform any tasks with it. You will be way better off investing your time and energy with looking into using AMO.

Having said that, if your application absolutely requres DSO here is set of instructions on how to get it working http://msdn2.microsoft.com/en-us/library/ms403370.aspx

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Hi,

Thank u very much for the information.

I was able to connect to my analysis server 2000 repository according to the steps given in the URL .

I have another question related to DSO. Is it possible to connect to analysis server 2005 using DSO as well ?

I also agree with you about using AMO. But for the moment I have to connect to the analysis server using DSO. But I would looking into using AMO later.

Thanks again for your help.

|||

It is possible to connect to AS2005 using DSO.

In fact DSO will under the covers invoke AMO, it will pass all the information to AMO and then AMO will make the conneciton.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

HI Again,

Do you know what's the provider I should use when giving the RepositoryConnectionString for DSO to get databases configured in Analysis server 2005.?

When I used OLE DB provider for Analysis service 9.0 , It gave the following error.

"Query (1, 10) Parser: The syntax for ',' is incorrect."

Thanks

Umanga.

|||

I think there is a little bit of misunderstanding. The paper on http://msdn2.microsoft.com/en-us/library/ms403370.aspx states you should use something like Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Program files\Microsoft SQL Server\MSSQL.n\OLAP\DSO\msmdrep.mdb;Persist Security Info=False

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Hi,

It worked for getting the databases configured in Analysis server 2000 from sql server 2005.

I want to get the newly created databases using SQL Server Business Intelligence Development Studio in sql server 2005 from DSO.

For example, now when I check from the sql server management studio, it shows food mart database (2000) and my new database created in 2005 ,

But using the "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Program files\Microsoft SQL Server\MSSQL.n\OLAP\DSO\msmdrep.mdb" it shows only database Food mart (configured in 2000)

Do you think it's possible to get databases added in 2005 using DSO as well, or should I use AMO?

Hope my question is clear now

Thanks

Umanga.

|||

As I mentioned earlier, support for DSO is very limited. It is there mainly for backward compartibility of existing applications and exisiting cubes.

The way DSO works with AS2005 is that it will not show you the server cube created using BI Dev studio. For that you will need to start using AMO object model.

If looks at functionality offered by AS2005 and new ideas it has, it is very different from AS2000. So many properties, objects and concepts are different. DSO simply not the way to manager AS2005.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||Hi.

When you configure Analysis Service, you need to create the "OlapObjects" table.

Script:
CREATE TABLE [dbo].[OlapObjects](
[ID] [varchar](36) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,
[ParentID] [varchar](36) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,
[ObjectName] [nvarchar](150) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,
[ClassType] [int] NOT NULL,
[ObjectDefinition] [ntext] COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[LastUpdated] [datetime] NULL,
[Changed] [bit] NULL,
[Version] [int] NULL
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]
GO

After you create it, you can build the cubes.

Cláudio Hidetoshi.
Rio de Janeiro.

Invalid Object Name 'OlapObjects'

We are using Microsoft Analysis Service with SP3 on Microsoft SQL Server. The Repository has been migrated to SQL server on the same machine. Recently for no reason, using Microsoft Analysis Manager, we would unable to log in to the repository. We have tried to do reinstallation of the Analysis Service component. After which when using local Analysis Manager to connect, it would show "Cannot connect to the repository. Analysis server: WEBTEST. Error: Not a valid account name or password."

Local Repository Connection String then was: Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Program Files\Microsoft Analysis Services\Bin\msmdrep.mdb

After confirming that the repository has been moved to SQL server, we changed the repository connection string to the following:

Local Repository Connection String:

Provider=SQLOLEDB.1;Password=sa_password;Persist Security Info=True;User ID=sa;Initial Catalog=DataMart; Data Source=WEBTEST;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=WEBTEST; Use Encryption for Data=False;Tag with column collation when possible=False

where DataMart was the database for the Analysis Service repository and WEBTEST is the server name.

After which when using local Analysis Manager to connect, it would show error "Invalid Object Name 'OlapObjects'".

Interestingly, when the Analysis Services component was just installed, the sample Food Mart also did not displayed.

Please advise on how to solve the problem, thank you.

It sounds as if something went wrong during migration. The error message makes me believe the OlapObjects table does not exist in the DataMart database. I would double-check the contents of this database. It should contain a Server table and an OlapObjects table.