Creating Local cube Using SQL Server / Analysis Services 2005

I am creating a local cube through a web page and everything is working properly when I am debugging but if I am not debugging, the following exception is returned:

x= Exception:File system error: Error opening file; \\?\C:\Program Files\Common Files\System\Ole DB\MDTempStore_1088_1_fm3by.tmp is not a disk file or file is not accessible.

StackTrace: at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.HandleCreateLocalCube(AdomdErrorResponseException ex) at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.IExecuteProvider.Execute(ICommandContentProvider contentProvider, AdomdPropertyCollection commandProperties, IDataParameterCollection parameters) at Microsoft.AnalysisServices.AdomdClient.AdomdCommand.Execute()

The role defined for the cube is:

General tab: Read definition

Cubes tab: Access: read

Cubes: Local Cube/Drillthrough Access

Thanks,

Yones

Looks like a problem with security. Make sure the process you running within IIS has sufficient privileges to create a files local cube files.

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

|||

Hi Edward,

Yes, it seems like it is a security problem. I have just found that it is working properly when using AS 2005 installed with (local) SQL server 2005 but it does not work with a named instance such as (ServerName\SQLServerInstanceName)

Could please be more specific about what privileges should be given?

Thanks,

Yones

|||

Not sure how named instance plays the role here.

Are you talking about SQL Server relational engine named instance or about Analysis Server named instance here?

If it is working with default instance, try and see what are the differences in the way named instance is setup.

There should be a little difference in the way you work against named instance.

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

|||

Hi Edward,

Concerning named instance (MachineName\InstanceName) and default instance ((local)), I think if we have a named instance, it is for both SQL Server relational engine and Analysis Services. I do not think we can have a named instance for SQL Server relational engine and a default instance for Analysis Services (Please correct me if I am wrong)

It is working for the default instance (local) because the Web Server (IIS) and Analysis Services are on the same machine but for a named instance (MachineName\InstanceName), it is not working even the “MachineName” is the same for the Web Server (IIS)

Thanks,

Yones

|||

Here is a similar thread :

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=686728&SiteID=1

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