Error when Deploying Cube

Hey guys,

Have a really strange error, I have a AS Cube designed and ready to go. Have been deploying it previosly and was erroring out due to attributes not being found in the tables. So ive worked on fixing all of them and now, i have an error message occuring and all it says is:

Server: The Operation has been cancelled.

I havnt cancelled anything, it doesnt show any more details for the error either.. Is there a log file somewhere that i can look further into?

Or has anyone had this message before? I am stumpped and now its annoying me as i was so close to having my first cube up and deployed...

Thanks in advance

Scotty

If you have made some changes in the source DB, you can try re creating the Data source and data source view and processing the dimensions and the cube after that.

|||

Are you receiving the error when you build and deploy the cube? Or does the error happenwhen you process the cube *after* deploying. If you have the Processing Options set to "default", then your cube will automatically process after each deployment.

If Processing Options are set to "default", then first set this to "do not process" (Right click on Project name to find this).

Then go into the Data Source View tab and right click anywhere in the diagram pane and select "Refresh...." This will perform some comparisons between your DSV and your relational database.

At this point, you can start processing your cube. What I would do at this point is select all the dimensions and process them first. If you see any errors, look at the error messages and backtrack until they are all corrected. Keep in mind that because your dimensions are being processed in parallel any error will cause any dimensions that are still being processed to stop and they will display a "canceled" message.

One you get the dimensions processed then start processing the partitions.

This is somewhere tedius, but if you haven't been keeping the relational database and your cube structure in synch, you'll have to take the time to do it now.

Hope this helps,

Pam

|||

Thanks Pam, I am receiving the error when i am deploying the cube. Building the cube works fine.

I will go through your instructions and see if it works. i am thinking you are right as i have been changing one particular table,. keeping all the columns names the same, but the problem started happening after i did this..

Ill let you know how i go in a couple of minutes..

Once again,,thanks.. this place in invaluable for advice!!

|||

Pam,

I went through and did what you suggested. Everything processed correctly to i go to the partition and tried to process that. This is where i got the message : Server: The Operation has Been Cancelled.

Any ideas on this? Should i try to create a new partition? if so, can i base if of the old one? I havnt done much with partitions yet as im pretty new to SSAS but im willing to read up on it if need be..

Thanks

Scotty

|||

hi guys,

Even i have error while deploying the cube

Error is as follows:

Error 1 The project could not be deployed to the "Server name" server because of the following connectivity problems : A connection cannot be made. Ensure that the server is running. To verify or update the name of the target server, right-click on the project in Solution Explorer, select Project Properties, click on the Deployment tab, and then enter the name of the server.

but the server was working fine..

i didnt get what excatly was the error

could any help me out

lalitha

|||

Hi
I am getting the same error while running the MDX. The query uses subcube. Query runs ok when there is less data BUT it gives me error "Server: The operation has been cancelled." there is large amount of data.
Thanks in advance!
Rakesh

|||Looks like its a perfomance issue. long-running queries can lock the system as a whole. |||When I highlight a few partitions and start processing, the process occasionally stops with a message that operation has been canceled, like this:

Response 3
Server: the operation has been cancelled.
Response 4

Server: the operation has been cancelled.

Response 5
Server: the operation has been cancelled.

..etc...

(no further error message details are provided)
SQL profiler shows that batch was completed (but rowcount shown in process progress log is too small).
Analysis Services profiler shows no messages at that time at all. It just shows messages when it started, and when I restarted the processing.

This is an occasional error and sometime occurs within 15-20 minutes from starting to process. It could fail on 1st partition in the process list , or on some partition in the middle. Some partitions might run for a few hours and not error out, but sometimes it fails quickly.

Also looks like the profiler (engine and ssas) are not working correctly - they are skipping messages (not capturing or not showing). I do not have any filters on the Profiler.