The options need to be separated by semi-colon. Look at that last option. SQL Server will try to use
for the master database log file a file named: "mastlog.ldf -g512". Set a semi-colon after the file
name.

Signature
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
> Hi,
>
[quoted text clipped - 11 lines]
>
> Thanks very much.
Brian Brian - 30 Nov 2007 14:52 GMT
Thanks Tibor,
I added a semi colon, and saved OK. when I tried to bring SQL online, it
failed. And I checked again in configuration manager, it is back to where it
was (without semi colon). Can you please help again? Maybe help me to get
this flag removed first?
Thanks.
Brian

Signature
Brian
> The options need to be separated by semi-colon. Look at that last option. SQL Server will try to use
> for the master database log file a file named: "mastlog.ldf -g512". Set a semi-colon after the file
[quoted text clipped - 15 lines]
> >
> > Thanks very much.
Tibor Karaszi - 30 Nov 2007 15:11 GMT
The semi-colon is probably removed by the cluster handling. Does it work if you use the SQL Server
Configuration Manager application (which I assume is cluster-aware)?

Signature
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
> Thanks Tibor,
>
[quoted text clipped - 28 lines]
>> >
>> > Thanks very much.
Brian Brian - 30 Nov 2007 14:57 GMT
Here is the error:
2007-11-30 09:54:43.45 spid5s Unable to open the physical file
"T:\Microsoft SQL Server\msql\MSSQL.1\MSSQL\DATA\mastlog.ldf -g512".
Operating system error 2: "2(The system cannot find the file specified.)".
Thanks very much.

Signature
Brian
> The options need to be separated by semi-colon. Look at that last option. SQL Server will try to use
> for the master database log file a file named: "mastlog.ldf -g512". Set a semi-colon after the file
[quoted text clipped - 15 lines]
> >
> > Thanks very much.