Friday, March 23, 2012

problem with access to analysis services: repository structure cannot be created

Hello,

I have a problem with Analysis Services. We use this product because it's needed for NetIQ Analysis Center, our OLAP reporting tool.

When I try to open the Analysis Manager, I can see the server but when I try to access it, the following error message is displayed: "repository structure cannot be created on the target server: the specified object cannot be found. For more information, see the section 'service pack installation' in the service pack readme file."

I checked this service pack readme file, but couldn't find anything relevant to this problem.
The files for both the sample foodmart and the NetiQ Analysis Center databases are still on this server, so I suppose something happened with the configuration information of this server, not with the databases themselves.

Event entries in the system and application log files do not reveal anything, nothing points to a problem with OLAP/Analysis Services.

The connection string to this server seems to be ok as well.

Unregistering and reregistering this server does not resolve the problem: as soon as I try to register, the same error message is displayed.

SQl, sqlsrvagent, MSDTC and Olap services are all running.

Did anyone see this behaviour before? Or does anyone know how to resolve or how to at least troubleshoot this particular problem?

Help will be much appreciated!

Timur

This sounds like a corruption issue with your repository although possibly it's as simple as a permissions problem with the relational database the repostitory is stored in.

First check your access to the relational database (SQL or Jet) that the repository is stored in. If this is okay, you can restore the default msmdrep.mdb by resetting the repository connection strings. (provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\Program Files\Microsoft Analysis services\Bin\msmdrep.mdb) Then you can migrate this to SQL if you wish. It is strongly recommended that you use the native format and not the Meta Data Services (previously named Microsoft Repository) format and the latest services packs will even enforce this during migration)

sql

No comments:

Post a Comment