9D File Errors
This article lists the various error codes beginning with status 9D.
|9D/9002||The SQL log file for RTAFleet or RTALocks is out of diskspace. |
You will need to backup the log and possibly shrink it depending on the circumstances (ie if the physical disk is full, you will need to shrink the file before any other data can be written to the disk). If you are going to use the full recovery model, you must do Transaction log backups regularly in order to free up space in the log file and keep the over all size of the log file down.
The RTALocks table doesn't exist or is corrupt so it can not create the locks necessary to get into RTA. Users will receive this error when trying to log in.
Inside of the Fleet folder, there is a file named 1000-Locks_and_Procs_NOMASTER.sql. You will need to take this and run in in SQL management studio and it will recreate the RTALocks table. You should then be able to log in.
|9D/102, incorrect syntax near '\'||This issue is caused because the table name is owned by a domain user rather than dbo, so the table name looks something like RTA-Host\UserName.tablename instead of dbo.tablename.|
You will need to have access to SQL management studio or else get with a DBA to make the change. Open up the RTAFleet database and expand the tables. Look through the list for your problem table(s) and make note of any owner. You will now need to run the following script leaving out the lines that have the --:
declare @OldOwner varchar(100)
--Type the exact owner name that is in front of any of the RTA Tables
select 'ALTER SCHEMA ['+ @NewOwner + '] TRANSFER [' + table_schema + '].[' + table_name + ']'
Before executing the script, make sure you edit the following: