Marc,
Do install backward compatability components and then try this:
The solution to this is to get a copy of the msmdrep.mdb file from a AS2000
installation folder(should be available in the Bin directory) and copy it
over onto AS2005 installation folder of the DBA's choice.( Possibly a New
folder created in the MSSQL.n folder, n is the number for OLAP directory.
Generally this is 2).
After this is done please follow the following procedure.
START-> PROGRAMS->SQL SERVER2005-> SQL MANAGEMENT STUDIO
a) Once the Management Studio Opens it shows Connecting Options.
b) Select Analysis Engine and click connect.
c) On the Object Explorer on the Right the connection to the server is shown.
d) Right click on the server and select Properties.
e) A window opens with the options on the left showing General... Security.
By default the General properties are shown on the right
f) At the end of the window there is a check box saying SHOW ADVANCED or
ADVANCED Properties.
g) Please check the check box.
h) there will many other options added now to the General properties to the
existing ones.
i) On scrolling down you see DSO and then there are 4 fields, one after the
other saying DSO\Repository Connection String etc...
the following options are available for DSO.
RemoteRepositoryConnectionString
RepositoryConnectionString
RemoteLocksDirectory
LocksDirectory
Create a folder in the same folder where the .MDB file was placed and name
it as LocksDirectory. This folder logs any locks that happen when trying to
process a cube, if in instance 2 people try to process the cube at the same
time.
RepositoryConnectionString: Place the path of the .mdb file in this. Or you
can browse and select the .MDB file. Please do not forget to test the
connection before accepting this.
LocksDirectory: This folder is used to log any locks if they are come
across.
RemoteRepositoryConnectionString: For using applications across a network
which need access to the cube definitions this is necessary. the folder
created for RepositoryConnectionString can be shared and the path as
\\machinename\\sharedfolder\file name against this.
RemoteLocksDirectory: Similar to the Remote Repository Connection string
this needs to be done.
This gives access of the cube definitions to other applications which try
using AS2005 cubes.
Hope this helps.
Regards,
Sumit.
Marc said:
Hi,
i have a virtual Server with SQL Server 2005 SP1 (including Analysis Server)
and Project Server 2007 BTR.
Now i want to build a OLAP Cube in Project Server.
I get following error:
[11/9/2006 8:48 AM] Cube build session started
[11/9/2006 8:48 AM] Analysis Services session started
[11/9/2006 8:48 AM] Analysis Services session failed with the following
error: Invalid object name 'OlapObjects'.
Can anybody heln me?
Thanks
Marc