Event Id | 1802 |
Source | MSSQLServer |
Description | CREATE DATABASE failed. Some file names listed could not be created. Check previous errors. |
Event Information | "According To Microsoft: CAUSE: If another error occurred at the same time as this error, this error could be a side effect of the other error. The file path and/or file names specified in the CREATE DATABASE or ALTER DATABASE statement could not be accessed. If no path is specified, the default path configured for new databases for this instance of SQL Server must be valid. Some examples that could cause this: 1. You specified a path that does not exist on the local machine or, in the case of a clustered instance, does not exist on one of the shared drives. 2. You specified a file name that is not valid. 3. You did not specify a path for the data or log file in your CREATE DATABASE or ALTER DATABASE statement, and the default data or log directory configured for new databases does not exist. 4. You attempt to create a database for a clustered instance on a shared cluster drive when the SQL Server resource does not depend on that drive. RESOLUTION: 1. If another error occurred at the same time as this error, troubleshoot the other error first. 2. If you specified a path in your CREATE DATABASE or ALTER DATABASE statement, verify that the entire path is valid and is accessible. The path must be on the local computer for a nonclustered instance or on a shared clustered drive on which the SQL Server Resource is dependent for a clustered instance. 3. Verify that the specified file name is valid by manually creating a file with that name in the specified path. 4 .If you are not specifying the full path in the CREATE DATABASE or ALTER DATABASE statement, check to see if the default data and log directories for new databases are correct, valid directories. If they are blank in SQL Enterprise Manager, verify that the underlying registry keys exist and that they have a valid path. If the keys do not exist at all, SQL Server will default to the data path specified during installation for all new data |
Reference Links | Microsoft product: SQL Server Version: 2000.80.760.0 Event Source: MSSQLServer Event ID: 1802 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.