Error: "Ceedata error: can't open cds.dir" when opening MYOB Accountants Enterprise
This support note applies to:
- Profiles (AU)
- AE Tax Series 6 & 8 (AU)
- AE Accounts (AU)
In MYOB Accountants Enterprise (MYOB AE) you may experience the following error "Ceedata error: can't open cds.dir" when opening Contacts, Configuration, My Work, or the Employees module.
The error message can be caused by a path or permission problem, such as:
- A blank or invalid database path in the CHOME line in the user's ceedata.ini
- Ceedata.ini does not exist for the user
- Incorrect drive mappings
- A desktop icon pointing to the wrong directory
- Insufficient security settings for the program and data directories
- The cds.dir file is corrupt.
If the error is caused by incorrect drive mappings, or an invalid database path in ceedata.ini, the error message incorporates a path, for example "...can't open s:\MYOB\bin\cds.dir".
Where is my ceedata.ini file?
The location of the ceedata.ini file can change depending on your network and operating system. Refer to the table below for standard locations.
Network or Operating System | Location |
---|---|
Windows 7 | C:\Windows\ceedata.ini |
Windows 8 | C:\Windows\ceedata.ini |
Windows 10 | C:\Windows\ceedata.ini |
Terminal Server - users copy | C:\Users\<UserName>\Windows |
Terminal Server - server copy | C:\Windows\Ceedata.ini |
The ceedata.ini may reside in other directories on a terminal server environment.
If there is no ceedata.ini in the respective directory, run a workstation setup, for example, from s:\MYOB \setup\setup.exe if your program directory is s:\MYOB\bin.
Complete the follow checks to resolve this error:
For further queries on this error message, please contact MYOB Support quoting this article number and the checks you have performed.
MYOB INTERNAL STAFF ONLY
If the above checks do not clear the error message, ask the client to email module.ini, ceedata.ini from the computer with the error and ceedata.ini from a computer without the error.
To verify the integrity of cds.dir, In Datasafe select Support Tools and run the Utility dbchk for the database cds.dir.
If any tables display a p# record out of range/record out of sequence/suspicious padding/index etc error then the cds.dir file requires restoring from a previous backup.