 | |
Cannot save - read-only
microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
Cannot save - read-only -
01-16-2006
, 11:16 PM
|
Hi Raman, I'm still on SQL 2000, in Analysis Services. I get an error "object or database is read-only". Rgds, "Raman Iyer [MS]" wrote: Are you using SQLServer 2005? What errors do you see when you try to save your project? -- -Raman Iyer SQL Server Data Mining [This posting is provided "AS IS" with no warranties, and confers no rights.] |
#2
| |||
| |||
|
|
This is from an earlier post elsewhere... Where can I set these access / permissions. Regards, CyberFox It's possible that you don't have access to the repository database used by DSO (the management object model in AS2000) to store your object definitions. If you have additional questions on this topic, please post them to the microsoft.public.sqlserver.olap newsgroup. |
#3
| |||
| |||
|
|
There is no specific setting for putting the repository into read-only mode. I am assuming that your repository is in the default access format and that you have not migrated it to a SQL database. By default the repository is stored in a file called msmdrep.mdb whose default location is c:\program files\microsoft analysis services\bin. There are 3 things I can think of that you can check: 1) Start by checking that this file has not had it's read-only flag set. 2) It is also possible that a copy of Analysis Manager crashed leaving open locks on the Access database. To check this you would need to close all copies of Analysis Manager, stop the Analysis Services service and check the "c:\program files\microsoft analysis services\bin" folder to see if there is a msmdrep.ldb file. If this file still exists after stopping the service, you should delete it and restart the service. (The ldb file only holds locking information and should delete itself once all connections to the mdb file have been closed.) 3) There is a hidden share called MsOlapRepository$ which is created when you install Analysis Services which the "Olap Administrators" group is given access to. Check that you can access this share and that you have read write access. The easiest way to do this is to open up an explorer window and type in \\<sever name>\MsOlapRepository$ when the window refreshes right click in the right hand pane and try to create a new text file. If you have any problems with this operation you will need to get them fixed. I have seen instances where either the Network Admin people had played with the permissions or the Active Directory policies had overridden access to the share. HTH -- Regards Darren Gosbell [MCSD] Blog: http://www.geekswithblogs.net/darrengosbell In article <9BD604DF-9339-4592-82F1-74D6839DD943 (AT) microsoft (DOT) com>, CyberFox (AT) discussions (DOT) microsoft.com says... This is from an earlier post elsewhere... Where can I set these access / permissions. Regards, CyberFox It's possible that you don't have access to the repository database used by DSO (the management object model in AS2000) to store your object definitions. If you have additional questions on this topic, please post them to the microsoft.public.sqlserver.olap newsgroup. |
#4
| |||
| |||
|
|
THANK YOU! Eventually! The problem was the sharing issue (your point no 3). i've added myself to have full access to all active directories, and voila@ Regards, "Darren Gosbell" wrote: There is no specific setting for putting the repository into read-only mode. I am assuming that your repository is in the default access format and that you have not migrated it to a SQL database. By default the repository is stored in a file called msmdrep.mdb whose default location is c:\program files\microsoft analysis services\bin. There are 3 things I can think of that you can check: 1) Start by checking that this file has not had it's read-only flag set. 2) It is also possible that a copy of Analysis Manager crashed leaving open locks on the Access database. To check this you would need to close all copies of Analysis Manager, stop the Analysis Services service and check the "c:\program files\microsoft analysis services\bin" folder to see if there is a msmdrep.ldb file. If this file still exists after stopping the service, you should delete it and restart the service. (The ldb file only holds locking information and should delete itself once all connections to the mdb file have been closed.) 3) There is a hidden share called MsOlapRepository$ which is created when you install Analysis Services which the "Olap Administrators" group is given access to. Check that you can access this share and that you have read write access. The easiest way to do this is to open up an explorer window and type in \\<sever name>\MsOlapRepository$ when the window refreshes right click in the right hand pane and try to create a new text file. If you have any problems with this operation you will need to get them fixed. I have seen instances where either the Network Admin people had played with the permissions or the Active Directory policies had overridden access to the share. HTH -- Regards Darren Gosbell [MCSD] Blog: http://www.geekswithblogs.net/darrengosbell In article <9BD604DF-9339-4592-82F1-74D6839DD943 (AT) microsoft (DOT) com>, CyberFox (AT) discussions (DOT) microsoft.com says... This is from an earlier post elsewhere... Where can I set these access / permissions. |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.