Attempts to Validate a schema using IBM Rational ClearQuest Eclipse Designer results in the error "A CException occurred: An attempt was made to access an unnamed file past its end".
Steps to reproduce:
- Login to IBM Rational ClearQuest Eclipse Designer.
- Checkout the schema which you would like to modify.
- Right click on the schema > select Validate.
The following error will be seen:
ERROR : A CException occurred:
An attempt was made to access an unnamed file past its end.
Note: This lack of information in the error was reported as a defect and logged under APAR PM81092.
This error can occur when using SQL Server as the database for ClearQuest.
The possible causes to this error are as follows:
- The database referred to in the error, <Logical Database Name> , may be low on available space or has not been configured to grow beyond a specified threshold.
- The PRIMARY filegroup in the database is full for the CQ database.
- The physical database server has no available space.
Diagnosing the problem
When the error message with the CQ Eclipse Designer is not clear, try the same operation using the Old CQ Designer. So, to see the exact problem with the ODBC connection, and to check whether it is SQL server space issue, validate the schema using the Old CQ Designer as follows:
- Click on Start -> Run, type "cqdesign.exe" and press Enter to launch the Old CQ Designer.
- Login and select the problematic schema
- Go to File -> Validate.
If you get this error message:
ERROR! CRMDB0054E [Microsoft][ODBC SQL Server Driver][SQL Server]Could not allocate space for object 'CQApp.schemarev_binaries' in database 'CQSchema' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
The database connection is lost. You may need to close your application and start again.
- Work with your Database Administrator (DBA) to check if there is enough disk space available in your SQL Server database.
Resolving the problem
Steps to Resolve:
- Add additional space to the Primary filegroup
Note: On your SQL Server database, you can create disk space by
-Deleting unneeded files
-Dropping objects in the filegroup
-Adding additional files to the filegroup
-Setting auto growth on the existing files in the filegroup
- Increase the hard drive space on the SQL Server DB server (if necessary).