Error#1337(The security ID structure is invalid.)

October 1, 2008

Hello,

Iam trying to create a database in SQLServer by pointing the database files

to a UNC location (\\bigserversnas01\sql_use\) which is a SAN. This requires

a trace flag as mentioned in http://support.microsoft.com/kb/304261. But

when trying to create the database, its giving me this error:

Msg 1802, Level 16, State 4, Line 1

CREATE DATABASE failed. Some file names listed could not be created.

Check related errors.

Msg 5123, Level 16, State 1, Line 1

CREATE FILE encountered operating system error 1337(The security ID

structure is invalid.) while attempting to open or create the physical file

' \\bigserversnas01\sql_use\sqldata.mdf '.

The CREATE DATABASE code will *always* run as the SQLServer service account.

So I RD-ed into the server as the service domain account and I was able to

access \\bigserversnas01\sql_use\ and also could create a test file.Also,

when I replace that UNC with another server share, it works fine. But I need

to use the original UNC as thats where I have the required huge disk space

for the database.

Does anyone have any idea about error#1337(The security ID structure is

invalid.) ?

Thank you,

SQL_Help

October 1, 2008

Re: Error#1337(The security ID structure is invalid.)

Hello msnews.microsoft.com,

Better post this to a SQL NG:

microsoft.public.sqlserver.setup

microsoft.public.sqlserver.server

microsoft.public.sqlserver

There also exist a lot more for SQL, just check with your newsreader.

Best regards

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Hello,

>

> Iam trying to create a database in SQLServer by pointing the database

> files to a UNC location (\\bigserversnas01\sql_use\) which is a SAN.

> This requires a trace flag as mentioned in

> http://support.microsoft.com/kb/304261. But when trying to create the

> database, its giving me this error:

>

> Msg 1802, Level 16, State 4, Line 1

> CREATE DATABASE failed. Some file names listed could not be created.

> Check related errors.

> Msg 5123, Level 16, State 1, Line 1

> CREATE FILE encountered operating system error 1337(The security ID

> structure is invalid.) while attempting to open or create the physical

> file

> ' \\bigserversnas01\sql_use\sqldata.mdf '.

>

> The CREATE DATABASE code will *always* run as the SQLServer service

> account. So I RD-ed into the server as the service domain account and

> I was able to access \\bigserversnas01\sql_use\ and also could create

> a test file.Also, when I replace that UNC with another server share,

> it works fine. But I need to use the original UNC as thats where I

> have the required huge disk space for the database.

>

> Does anyone have any idea about error#1337(The security ID structure

> is invalid.) ?

>

> Thank you,

> SQL_Help

October 2, 2008

Re: Error#1337(The security ID structure is invalid.)

Hello Meinolf,

Already posted in SQLServer NG. I posted here, only after I got the

recommendation to do so from Tibor.

http://www.developersdex.com/sql/message.asp?p=1870&r=6438987

The error reported is a Windows OS error and so it makes more sense too.

"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message

news:ff16fb6689868caf1dfd957b1a0@msnews.microsoft.com...

> Hello msnews.microsoft.com,

>

> Better post this to a SQL NG:

> microsoft.public.sqlserver.setup

> microsoft.public.sqlserver.server

> microsoft.public.sqlserver

>

> There also exist a lot more for SQL, just check with your newsreader.

>

> Best regards

>

> Meinolf Weber

> Disclaimer: This posting is provided "AS IS" with no warranties, and

> confers no rights.

> ** Please do NOT email, only reply to Newsgroups

> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>

>> Hello,

>>

>> Iam trying to create a database in SQLServer by pointing the database

>> files to a UNC location (\\bigserversnas01\sql_use\) which is a SAN.

>> This requires a trace flag as mentioned in

>> http://support.microsoft.com/kb/304261. But when trying to create the

>> database, its giving me this error:

>>

>> Msg 1802, Level 16, State 4, Line 1

>> CREATE DATABASE failed. Some file names listed could not be created.

>> Check related errors.

>> Msg 5123, Level 16, State 1, Line 1

>> CREATE FILE encountered operating system error 1337(The security ID

>> structure is invalid.) while attempting to open or create the physical

>> file

>> ' \\bigserversnas01\sql_use\sqldata.mdf '.

>>

>> The CREATE DATABASE code will *always* run as the SQLServer service

>> account. So I RD-ed into the server as the service domain account and

>> I was able to access \\bigserversnas01\sql_use\ and also could create

>> a test file.Also, when I replace that UNC with another server share,

>> it works fine. But I need to use the original UNC as thats where I

>> have the required huge disk space for the database.

>>

>> Does anyone have any idea about error#1337(The security ID structure

>> is invalid.) ?

>>

>> Thank you,

>> SQL_Help

>

October 2, 2008

Re: Error#1337(The security ID structure is invalid.)

Hello msnews.microsoft.com,

If i read the recommendation from Tibor and Ekrem, it will not work that way.

From: Ekrem Önsoy

Date Posted: 9/26/2008 1:15:00 AM

Well, actually recently we got many questions about this kind of

installation questions here. First, I'll suggest you to see a document which

talks about which components of SQL Server have fixed and configurable

paths. Here it's : http://msdn.microsoft.com/en-us/library/ms143547.aspx

It means, you can't install your whole SQL Server binaries to another drive

other than your root drive in your system on which you are installing a SQL

Server instance.

Note:

You can't locate your database files on a network share. They must be on

your local disks. If it's SAN and if this is a Cluster environment then that

disk must be of a Physical Disk resource and must be owned by your computer.

--

Ekrem Önsoy

Best regards

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Hello Meinolf,

>

> Already posted in SQLServer NG. I posted here, only after I got the

> recommendation to do so from Tibor.

> http://www.developersdex.com/sql/message.asp?p=1870&r=6438987

>

> The error reported is a Windows OS error and so it makes more sense

> too.

>

> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message

> news:ff16fb6689868caf1dfd957b1a0@msnews.microsoft.com...

>

>> Hello msnews.microsoft.com,

>>

>> Better post this to a SQL NG:

>> microsoft.public.sqlserver.setup

>> microsoft.public.sqlserver.server

>> microsoft.public.sqlserver

>> There also exist a lot more for SQL, just check with your newsreader.

>>

>> Best regards

>>

>> Meinolf Weber

>> Disclaimer: This posting is provided "AS IS" with no warranties, and

>> confers no rights.

>> ** Please do NOT email, only reply to Newsgroups

>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>>> Hello,

>>>

>>> Iam trying to create a database in SQLServer by pointing the

>>> database files to a UNC location (\\bigserversnas01\sql_use\) which

>>> is a SAN. This requires a trace flag as mentioned in

>>> http://support.microsoft.com/kb/304261. But when trying to create

>>> the database, its giving me this error:

>>>

>>> Msg 1802, Level 16, State 4, Line 1

>>> CREATE DATABASE failed. Some file names listed could not be created.

>>> Check related errors.

>>> Msg 5123, Level 16, State 1, Line 1

>>> CREATE FILE encountered operating system error 1337(The security ID

>>> structure is invalid.) while attempting to open or create the

>>> physical

>>> file

>>> ' \\bigserversnas01\sql_use\sqldata.mdf '.

>>> The CREATE DATABASE code will *always* run as the SQLServer service

>>> account. So I RD-ed into the server as the service domain account

>>> and I was able to access \\bigserversnas01\sql_use\ and also could

>>> create a test file.Also, when I replace that UNC with another server

>>> share, it works fine. But I need to use the original UNC as thats

>>> where I have the required huge disk space for the database.

>>>

>>> Does anyone have any idea about error#1337(The security ID structure

>>> is invalid.) ?

>>>

>>> Thank you,

>>> SQL_Help

October 3, 2008

Re: Error#1337(The security ID structure is invalid.)

Hello Meinolf,

What will not work that way? Using a undocumented trace flag, it is possible

create db files on UNC share.Also, as I mentioned

"when I replace that UNC with another server share, it works fine. But I

need to use the original UNC as thats where I have the required huge disk

space

for the database."

The CREATE DATABASE fails only for the share (\\bigserversnas01\sql_use\)

and my limited Windows OS knowledge prevents me from checking what needs to

be checked for error#1337(The security ID structure is invalid.).

"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message

news:ff16fb668b338caf2806c650fbb@msnews.microsoft.com...

> Hello msnews.microsoft.com,

>

> If i read the recommendation from Tibor and Ekrem, it will not work that

> way.

>

> From: Ekrem Önsoy

> Date Posted: 9/26/2008 1:15:00 AM

>

> Well, actually recently we got many questions about this kind of

> installation questions here. First, I'll suggest you to see a document

> which talks about which components of SQL Server have fixed and

> configurable paths. Here it's :

> http://msdn.microsoft.com/en-us/library/ms143547.aspx

>

> It means, you can't install your whole SQL Server binaries to another

> drive other than your root drive in your system on which you are

> installing a SQL Server instance.

>

> Note:

> You can't locate your database files on a network share. They must be on

> your local disks. If it's SAN and if this is a Cluster environment then

> that disk must be of a Physical Disk resource and must be owned by your

> computer.

>

> --

> Ekrem Önsoy

>

> Best regards

>

> Meinolf Weber

> Disclaimer: This posting is provided "AS IS" with no warranties, and

> confers no rights.

> ** Please do NOT email, only reply to Newsgroups

> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>

>> Hello Meinolf,

>>

>> Already posted in SQLServer NG. I posted here, only after I got the

>> recommendation to do so from Tibor.

>> http://www.developersdex.com/sql/message.asp?p=1870&r=6438987

>>

>> The error reported is a Windows OS error and so it makes more sense

>> too.

>>

>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message

>> news:ff16fb6689868caf1dfd957b1a0@msnews.microsoft.com...

>>

>>> Hello msnews.microsoft.com,

>>>

>>> Better post this to a SQL NG:

>>> microsoft.public.sqlserver.setup

>>> microsoft.public.sqlserver.server

>>> microsoft.public.sqlserver

>>> There also exist a lot more for SQL, just check with your newsreader.

>>>

>>> Best regards

>>>

>>> Meinolf Weber

>>> Disclaimer: This posting is provided "AS IS" with no warranties, and

>>> confers no rights.

>>> ** Please do NOT email, only reply to Newsgroups

>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>>>> Hello,

>>>>

>>>> Iam trying to create a database in SQLServer by pointing the

>>>> database files to a UNC location (\\bigserversnas01\sql_use\) which

>>>> is a SAN. This requires a trace flag as mentioned in

>>>> http://support.microsoft.com/kb/304261. But when trying to create

>>>> the database, its giving me this error:

>>>>

>>>> Msg 1802, Level 16, State 4, Line 1

>>>> CREATE DATABASE failed. Some file names listed could not be created.

>>>> Check related errors.

>>>> Msg 5123, Level 16, State 1, Line 1

>>>> CREATE FILE encountered operating system error 1337(The security ID

>>>> structure is invalid.) while attempting to open or create the

>>>> physical

>>>> file

>>>> ' \\bigserversnas01\sql_use\sqldata.mdf '.

>>>> The CREATE DATABASE code will *always* run as the SQLServer service

>>>> account. So I RD-ed into the server as the service domain account

>>>> and I was able to access \\bigserversnas01\sql_use\ and also could

>>>> create a test file.Also, when I replace that UNC with another server

>>>> share, it works fine. But I need to use the original UNC as thats

>>>> where I have the required huge disk space for the database.

>>>>

>>>> Does anyone have any idea about error#1337(The security ID structure

>>>> is invalid.) ?

>>>>

>>>> Thank you,

>>>> SQL_Help

>

October 8, 2008

Re: Error#1337(The security ID structure is invalid.)

For anyone interested...

I was able to figure out this one in a round-about way. Create the database

in another share, detach the database, copy the files across to the real

share destination and attach the database.

This problem seems to be somewhat common. Once the trace flag is set

everything works with using the database off of a NAS share except for

CREATE DATABASE. However, does not seem to happen when using a real Windows

server share. On a real Windows share there are no issues. I even found an

article referencing an EMC Celerra specifically and this problem. I assume

it has to do with the CIFS emulation done by the NAS devices. I could not

find any resolutions to this problem.

"msnews.microsoft.com" <SQL_Help@aaa.com> wrote in message

news:OpOfuIRJJHA.2208@TK2MSFTNGP02.phx.gbl...

> Hello Meinolf,

>

> What will not work that way? Using a undocumented trace flag, it is

> possible create db files on UNC share.Also, as I mentioned

> "when I replace that UNC with another server share, it works fine. But I

> need to use the original UNC as thats where I have the required huge disk

> space

> for the database."

>

> The CREATE DATABASE fails only for the share (\\bigserversnas01\sql_use\)

> and my limited Windows OS knowledge prevents me from checking what needs

> to be checked for error#1337(The security ID structure is invalid.).

>

> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message

> news:ff16fb668b338caf2806c650fbb@msnews.microsoft.com...

>> Hello msnews.microsoft.com,

>>

>> If i read the recommendation from Tibor and Ekrem, it will not work that

>> way.

>>

>> From: Ekrem Önsoy

>> Date Posted: 9/26/2008 1:15:00 AM

>>

>> Well, actually recently we got many questions about this kind of

>> installation questions here. First, I'll suggest you to see a document

>> which talks about which components of SQL Server have fixed and

>> configurable paths. Here it's :

>> http://msdn.microsoft.com/en-us/library/ms143547.aspx

>>

>> It means, you can't install your whole SQL Server binaries to another

>> drive other than your root drive in your system on which you are

>> installing a SQL Server instance.

>>

>> Note:

>> You can't locate your database files on a network share. They must be on

>> your local disks. If it's SAN and if this is a Cluster environment then

>> that disk must be of a Physical Disk resource and must be owned by your

>> computer.

>>

>> --

>> Ekrem Önsoy

>>

>> Best regards

>>

>> Meinolf Weber

>> Disclaimer: This posting is provided "AS IS" with no warranties, and

>> confers no rights.

>> ** Please do NOT email, only reply to Newsgroups

>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>>

>>> Hello Meinolf,

>>>

>>> Already posted in SQLServer NG. I posted here, only after I got the

>>> recommendation to do so from Tibor.

>>> http://www.developersdex.com/sql/message.asp?p=1870&r=6438987

>>>

>>> The error reported is a Windows OS error and so it makes more sense

>>> too.

>>>

>>> "Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message

>>> news:ff16fb6689868caf1dfd957b1a0@msnews.microsoft.com...

>>>

>>>> Hello msnews.microsoft.com,

>>>>

>>>> Better post this to a SQL NG:

>>>> microsoft.public.sqlserver.setup

>>>> microsoft.public.sqlserver.server

>>>> microsoft.public.sqlserver

>>>> There also exist a lot more for SQL, just check with your newsreader.

>>>>

>>>> Best regards

>>>>

>>>> Meinolf Weber

>>>> Disclaimer: This posting is provided "AS IS" with no warranties, and

>>>> confers no rights.

>>>> ** Please do NOT email, only reply to Newsgroups

>>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>>>>> Hello,

>>>>>

>>>>> Iam trying to create a database in SQLServer by pointing the

>>>>> database files to a UNC location (\\bigserversnas01\sql_use\) which

>>>>> is a SAN. This requires a trace flag as mentioned in

>>>>> http://support.microsoft.com/kb/304261. But when trying to create

>>>>> the database, its giving me this error:

>>>>>

>>>>> Msg 1802, Level 16, State 4, Line 1

>>>>> CREATE DATABASE failed. Some file names listed could not be created.

>>>>> Check related errors.

>>>>> Msg 5123, Level 16, State 1, Line 1

>>>>> CREATE FILE encountered operating system error 1337(The security ID

>>>>> structure is invalid.) while attempting to open or create the

>>>>> physical

>>>>> file

>>>>> ' \\bigserversnas01\sql_use\sqldata.mdf '.

>>>>> The CREATE DATABASE code will *always* run as the SQLServer service

>>>>> account. So I RD-ed into the server as the service domain account

>>>>> and I was able to access \\bigserversnas01\sql_use\ and also could

>>>>> create a test file.Also, when I replace that UNC with another server

>>>>> share, it works fine. But I need to use the original UNC as thats

>>>>> where I have the required huge disk space for the database.

>>>>>

>>>>> Does anyone have any idea about error#1337(The security ID structure

>>>>> is invalid.) ?

>>>>>

>>>>> Thank you,

>>>>> SQL_Help

>>

>

Sign In

Error#1337(The security ID structure is invalid.)

Recommended Posts

Guest msnews.microsoft.com

Popular Days

Popular Days

Guest Meinolf Weber

Guest msnews.microsoft.com

Guest Meinolf Weber

Guest msnews.microsoft.com

Guest msnews.microsoft.com

Browse

Activity

Site Info