Article ID: 243545
Article Last Modified on 3/14/2006
APPLIES TO
- Microsoft SQL Server OLAP Services
This article was previously published under Q243545
BUG #: 3823 (plato7x)
SYMPTOMS
When a cube or dimension is processed using the DTS Addin and the processing fails for some reason, the error message that displays is incorrect.
An operating system error message displays instead of the Decision Support Object (DSO) error message. For example, if the program should fail with the following 206 error:
the following operating system 206 error displays instead:
Similarly, the following 207 error:
displays as:
WORKAROUND
Refer to the table in the More Information section to find out the actual error message and troubleshoot the problem accordingly.
STATUS
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
254561 INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.
MORE INFORMATION
The following table lists some of the possible error messages from the Data Transformation Services (DTS) Addin and the corresponding correct error message. This may help you to identify the true error when your processing fails.
| Error From DTS Addin | Actual Error | Error number |
|---|---|---|
| The operating system cannot run %1 | Error(202): Could not establish connection to the OLAP server | 202 |
| The system could not find the environment option that was entered. | Error(203): Initialization failed (%s2) | 203 |
| " " | Error(204): Server object not found (%s2) | 204 |
| No process in the command subtree has a signal handler | Error(205): Could not open server object (%s2)" | 205 |
| The filename or extension is too long | Process operation failed | 206 |
| The ring 2 stack is in use | Error(207): Internal error (%s2) | 207 |
| The global filename characters, * or ?, are entered incorrectly or too many global filename characters are specified. | Error(208): SQL error (%s2) | 208 |
| The signal being posted is not correct | Error(209): Could not initiate dimension update (Dimension %s1) | 209 |
| The signal handler cannot be set | Error(210): The object structure is invalid (%s2) | 210 |
| " " | Error(211): Unknown dimension member '%s2' | 211 |
| The segment is locked and cannot be reallocated | Error(212): More than the allowed maximum of 64,000 dimension member children for a single parent %s2 | 212 |
| " " | Error(213): Invalid measure data type found in returned SQL rowset '%s2' | 213 |
| Too many dynamic link modules are attached to this program or dynamic link module. | ODBC error: %s1 | 214 |
| Can't nest calls to LoadModule. | OLAP Server Error: %s1 | 215 |
| The image file %1 is valid, but is for a machine type other than the current machine. | Error(216): Object structure changed '%s2' | 216 |
| " " | Could not lock object (%s1) | 218 |
| " " | Could not unlock object (%s1) | 224 |
| All pipe instances are busy | %s | 231 |
Note that most of the preceding error messages have a second part, which are shown correctly and can help you find the root cause of the problem. For example, when you get error 207, you would see an error like:
instead of:
And when you see error 231, it will be:
Keywords: kbbug kbfix KB243545
