Msg 5133, Level 16, State 1, Line 1

I am using SQL Server 2005 64 bit SP2 on a cluster with SAN. I am getting
the error in subject when I try to create a database using this statement:
CREATE DATABASE [ESBMessageTracking] ON PRIMARY
( NAME = 'ESBMsgTrack_Data', FILENAME = 'F:\Microsoft SQL
Server\MSSQL.1\Data\ESBMessageTracking\ESBMessageTracking_Data.MDF' , SIZE = 33536KB , MAXSIZE = UNLIMITED, FILEGROWTH = 10%)
LOG ON
( NAME = 'ESBMsgTrack_Log', FILENAME = 'E:\Microsoft SQL
Server\MSSQL.1\MSSQL\TLogs\ESBMessageTracking\ESBMessageTracking_Log.LDF' ,
SIZE = 218752KB , MAXSIZE = UNLIMITED, FILEGROWTH = 10%)
COLLATE SQL_Latin1_General_CP1_CI_AS
GO
I have confirmed the path is correct. Don't know what is going on. Help
please."SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:F5366135-EE7C-4C97-A782-C9A088E0FD96@.microsoft.com...
>I am using SQL Server 2005 64 bit SP2 on a cluster with SAN. I am getting
> the error in subject when I try to create a database using this statement:
> CREATE DATABASE [ESBMessageTracking] ON PRIMARY
> ( NAME = 'ESBMsgTrack_Data', FILENAME = 'F:\Microsoft SQL
> Server\MSSQL.1\Data\ESBMessageTracking\ESBMessageTracking_Data.MDF' , SIZE
> => 33536KB , MAXSIZE = UNLIMITED, FILEGROWTH = 10%)
> LOG ON
> ( NAME = 'ESBMsgTrack_Log', FILENAME = 'E:\Microsoft SQL
> Server\MSSQL.1\MSSQL\TLogs\ESBMessageTracking\ESBMessageTracking_Log.LDF'
> ,
> SIZE = 218752KB , MAXSIZE = UNLIMITED, FILEGROWTH = 10%)
> COLLATE SQL_Latin1_General_CP1_CI_AS
> GO
> I have confirmed the path is correct. Don't know what is going on. Help
> please.
Did you confirm both PATH*S* are correct? Your MDF is on F: but your LDF is
on E: Next time, it would help if you included the entire error message
so - most people have not memorized the error numbers.|||Scott,
Thanks. I Did confirm both paths exist. Here's the error message:
Msg 5133, Level 16, State 1, Line 1
Directory lookup for the file "F:\Microsoft SQL
Server\MSSQL.1\Data\ESBMessageTracking\ESBMessageTracking_Data.MDF" failed
with the operating system error 1008(An attempt was made to reference a token
that does not exist.).
Msg 1802, Level 16, State 1, Line 1
CREATE DATABASE failed. Some file names listed could not be created. Check
related errors.
What is interesting is that when I use xp_cmdshell 'dir f:\microsoft sql
server' it does not find the path even though it exists. It is like it
connot deal with the embedded blank.
"Scott Morris" wrote:
> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
> news:F5366135-EE7C-4C97-A782-C9A088E0FD96@.microsoft.com...
> >I am using SQL Server 2005 64 bit SP2 on a cluster with SAN. I am getting
> > the error in subject when I try to create a database using this statement:
> > CREATE DATABASE [ESBMessageTracking] ON PRIMARY
> > ( NAME = 'ESBMsgTrack_Data', FILENAME = 'F:\Microsoft SQL
> > Server\MSSQL.1\Data\ESBMessageTracking\ESBMessageTracking_Data.MDF' , SIZE
> > => > 33536KB , MAXSIZE = UNLIMITED, FILEGROWTH = 10%)
> > LOG ON
> > ( NAME = 'ESBMsgTrack_Log', FILENAME = 'E:\Microsoft SQL
> > Server\MSSQL.1\MSSQL\TLogs\ESBMessageTracking\ESBMessageTracking_Log.LDF'
> > ,
> > SIZE = 218752KB , MAXSIZE = UNLIMITED, FILEGROWTH = 10%)
> > COLLATE SQL_Latin1_General_CP1_CI_AS
> > GO
> >
> > I have confirmed the path is correct. Don't know what is going on. Help
> > please.
> Did you confirm both PATH*S* are correct? Your MDF is on F: but your LDF is
> on E: Next time, it would help if you included the entire error message
> so - most people have not memorized the error numbers.
>
>|||"SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
news:EC0C75CA-DF07-42D6-A414-565C1B1EBF79@.microsoft.com...
> Scott,
> Thanks. I Did confirm both paths exist. Here's the error message:
> Msg 5133, Level 16, State 1, Line 1
> Directory lookup for the file "F:\Microsoft SQL
> Server\MSSQL.1\Data\ESBMessageTracking\ESBMessageTracking_Data.MDF" failed
> with the operating system error 1008(An attempt was made to reference a
> token
> that does not exist.).
> Msg 1802, Level 16, State 1, Line 1
> CREATE DATABASE failed. Some file names listed could not be created. Check
> related errors.
> What is interesting is that when I use xp_cmdshell 'dir f:\microsoft sql
> server' it does not find the path even though it exists. It is like it
> connot deal with the embedded blank.
The embedded blank shouldn't be a problem - the log file has one as well.
Apparently you have the exact same path on two different disks, using one
for data and one for logs. A bit strange that these paths appear to be sql
server installation paths - but what do I know.
First, things like this generally mean that there is a security or account
issue. Just because you personally have access to an E or F drive doesn't
mean that sql server and the accounts it uses internally do. Second,
clusters have their own complicated setup - something beyond my experience.
BTW - it appears that you posted this question last month in the cluster NG.
Is this a follow-on? Have you done the same things Geoff recommended?
http://groups.google.com/group/microsoft.public.sqlserver.clustering/browse_thread/thread/63ea092f04d74333/e447afb0ba5e592b?lnk=st&q=&rnum=1&hl=en#e447afb0ba5e592b|||I agree with Scott, in your SQL cluster group, both E:\ and F:\ disks must
have a cluster resource in the same group and SQL Server cluster resource
must depend on both drives in order to use them.
Ayad Shammout
"Scott Morris" <bogus@.bogus.com> wrote in message
news:OCN$M014HHA.600@.TK2MSFTNGP05.phx.gbl...
> "SQLGuru_not" <SQLGurunot@.discussions.microsoft.com> wrote in message
> news:EC0C75CA-DF07-42D6-A414-565C1B1EBF79@.microsoft.com...
>> Scott,
>> Thanks. I Did confirm both paths exist. Here's the error message:
>> Msg 5133, Level 16, State 1, Line 1
>> Directory lookup for the file "F:\Microsoft SQL
>> Server\MSSQL.1\Data\ESBMessageTracking\ESBMessageTracking_Data.MDF"
>> failed
>> with the operating system error 1008(An attempt was made to reference a
>> token
>> that does not exist.).
>> Msg 1802, Level 16, State 1, Line 1
>> CREATE DATABASE failed. Some file names listed could not be created.
>> Check
>> related errors.
>> What is interesting is that when I use xp_cmdshell 'dir f:\microsoft sql
>> server' it does not find the path even though it exists. It is like it
>> connot deal with the embedded blank.
> The embedded blank shouldn't be a problem - the log file has one as well.
> Apparently you have the exact same path on two different disks, using one
> for data and one for logs. A bit strange that these paths appear to be
> sql server installation paths - but what do I know.
> First, things like this generally mean that there is a security or account
> issue. Just because you personally have access to an E or F drive doesn't
> mean that sql server and the accounts it uses internally do. Second,
> clusters have their own complicated setup - something beyond my
> experience. BTW - it appears that you posted this question last month in
> the cluster NG. Is this a follow-on? Have you done the same things Geoff
> recommended?
> http://groups.google.com/group/microsoft.public.sqlserver.clustering/browse_thread/thread/63ea092f04d74333/e447afb0ba5e592b?lnk=st&q=&rnum=1&hl=en#e447afb0ba5e592b
>