In versions of SQL Server 2008 that are earlier than SQL Server 2008 Service Pack 2 (SP2) or in versions of SQL Server 2008 R2 that are earlier than SQL Server 2008 R2 Service Pack 2 (SP2) , you may receive an error message that resembles one of the following.
Note These error messages are displayed in SQL Server 2008 Analysis Services and in SQL Server 2008 R2 Analysis Services.
Server: The operation has been cancelled
The error message may be displayed in any of the following locations:
The text of the error that is returned to the client application
The SQL Profiler Error event text
The Errorcolumn for various events in SQL Profiler
Service pack information for SQL Server 2008
To resolve this problem, obtain the latest service pack for SQL Server 2008. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
968382 How to obtain the latest service pack for SQL Server 2008
Service pack information for SQL Server 2008 R2
To resolve this problem, obtain the latest service pack for SQL Server 2008 R2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2527041How to obtain the latest service pack for SQL Server 2008 R2
Microsoft recognizes that the error message for cancelation is too generic. Therefore, SQL Server 2008 SP2 and SQL Server 2008 R2 SP2 introduce some new error messages to better explain why the operations are canceled.
When you install SQL Server 2008 SP2 or SQL Server 2008 R2 SP2, the following six error messages are added to clarify some cases in which the generic “Server: The operation has been cancelled” error message is returned.
Note These messages do not replace the generic error message in every case. In some scenarios, you may still receive the generic error message.
Decimal return code
Error message text
The current operation was cancelled because another operation in the transaction failed.
Processing can run multiple operations in parallel. When one of these jobs fails, it causes all other active jobs to fail. The additional failures generate this error. Check for the cause of the failure in another error.
Proactive caching was cancelled because newer data became available.
Proactive caching starts to process, but a new notification is received that would cause the MOLAP cache to become stale. Therefore, the server cancels the processing operation and then restarts that operation so that the MOLAP cache reflects the new data.
The session was cancelled because session objects were modified by another transaction.
A session cube or grouping cube is created on the session. However, one of the objects on which the session cube or grouping cube was based is modified by another transaction. The state of the cube cannot be recovered when this happens. Therefore, the server cancels the session and generates this error.
The operation was cancelled because of locking conflicts.
When two concurrent transactions try to take locks that conflict with one another, the lock manager may detect a deadlock. If this occurs, the lock manager cancels one of the transactions. That cancelation causes this error.
The operation was cancelled by the user.
The user sends a Cancel request on the session. This causes the active operation to be canceled.
The session was cancelled because it exceeded a timeout setting (session orphaned timeout or session idle timeout) or it exceeded the session memory limit.
This error covers the following cases:
The session uses too much memory. This causes the memory manager to run low on memory and cancel this session.
The session is orphaned from its network connection and cannot be recovered. After the IdleOrphanSessionTimeout is exceeded, the system cancels the session.
The session remains idle for longer than the MinIdleSessionTimeout value. This causes the system to cancel the session.