Install Errors

Hello,

I've been trying to install SQL Server express edition all day and it errors out every time. I've tried it on two different servers and I get the same errors. Here's what the error log says:

2007-04-20 16:37:52.77 Server Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86)

Feb 9 2007 22:47:07

Copyright (c) 1988-2005 Microsoft Corporation

Express Edition on Windows NT 5.2 (Build 3790: Service Pack 2, v.2825)

2007-04-20 16:37:52.77 Server (c) 2005 Microsoft Corporation.

2007-04-20 16:37:52.77 Server All rights reserved.

2007-04-20 16:37:52.77 Server Server process ID is 1356.

2007-04-20 16:37:52.77 Server Authentication mode is MIXED.

2007-04-20 16:37:52.77 Server Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.

2007-04-20 16:37:52.77 Server This instance of SQL Server last reported using a process ID of 1964 at 4/20/2007 4:37:47 PM (local) 4/20/2007 8:37:47 PM (UTC). This is an informational message only; no user action is required.

2007-04-20 16:37:52.77 Server Registry startup parameters:

2007-04-20 16:37:52.77 Server -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf

2007-04-20 16:37:52.77 Server -e c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG

2007-04-20 16:37:52.77 Server -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf

2007-04-20 16:37:52.77 Server Command Line Startup Parameters:

2007-04-20 16:37:52.77 Server -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Template Data\master.mdf

2007-04-20 16:37:52.77 Server -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Template Data\mastlog.ldf

2007-04-20 16:37:52.77 Server -m SqlSetup

2007-04-20 16:37:52.77 Server SqlSetup

2007-04-20 16:37:52.77 Server -Q

2007-04-20 16:37:52.77 Server -q SQL_Latin1_General_CP1_CI_AS

2007-04-20 16:37:52.77 Server -T 4022

2007-04-20 16:37:52.77 Server -T 3659

2007-04-20 16:37:52.77 Server -T 3610

2007-04-20 16:37:52.77 Server -T 4010

2007-04-20 16:37:52.79 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

2007-04-20 16:37:52.79 Server Detected 1 CPUs. This is an informational message; no user action is required.

2007-04-20 16:37:52.88 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.

2007-04-20 16:37:52.92 Server Database Mirroring Transport is disabled in the endpoint configuration.

2007-04-20 16:37:52.93 spid5s Warning ******************

2007-04-20 16:37:52.93 spid5s SQL Server started in single-user mode. This an informational message only. No user action is required.

2007-04-20 16:37:52.93 spid5s Starting up database 'master'.

2007-04-20 16:37:52.93 spid5s Error: 17207, Severity: 16, State: 1.

2007-04-20 16:37:52.93 spid5s FCB:pen: Operating system error 5(Access is denied.) occurred while creating or opening file 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Template Data\master.mdf'. Diagnose and correct the operating system error, and retry the operation.

2007-04-20 16:37:52.97 spid5s Error: 17204, Severity: 16, State: 1.

2007-04-20 16:37:52.97 spid5s FCB:pen failed: Could not open file c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Template Data\master.mdf for file number 1. OS error: 5(Access is denied.).

2007-04-20 16:37:52.98 spid5s Error: 5120, Severity: 16, State: 101.

2007-04-20 16:37:52.98 spid5s Unable to open the physical file "c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Template Data\master.mdf". Operating system error 5: "5(Access is denied.)".

2007-04-20 16:37:53.05 spid5s Error: 17207, Severity: 16, State: 1.

2007-04-20 16:37:53.05 spid5s FCB:pen: Operating system error 5(Access is denied.) occurred while creating or opening file 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Template Data\mastlog.ldf'. Diagnose and correct the operating system error, and retry the operation.

2007-04-20 16:37:53.05 spid5s Error: 17204, Severity: 16, State: 1.

2007-04-20 16:37:53.05 spid5s FCB:pen failed: Could not open file c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Template Data\mastlog.ldf for file number 2. OS error: 5(Access is denied.).

2007-04-20 16:37:53.05 spid5s Error: 5120, Severity: 16, State: 101.

2007-04-20 16:37:53.05 spid5s Unable to open the physical file "c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Template Data\mastlog.ldf". Operating system error 5: "5(Access is denied.)".

What exact steps are you trying to perform here and what log file is this comming from?

Basically this is saying that you don't have permissions to a bunch of files that SQL Express is trying to access, the fact that it's happening on two different computers would suggest that they both share some kind of security policy that is limiting your user account in some way. If this is a corporate computer, check with your IT staff to see what kind of security policies they have running, you need to be a computer administrator to install SQL Express.

Mike

|||I'm logged in as administrator however I had to check the option to add my user to the SQL Server Administrator role in order for the install to work.

Now that I got it installed I can't connect, the service is running but the osql command fails every time I try it and Plesk cannot connect to the server to add a database.

Installation and licencing about MSSQL 2005 Standard edition and clustering mode

Hi,

I have a question about using MSSQL server 2005 standard edition in Clustering mode.
I would like to build a msql cluster with only 2 servers (2 nodes).

I read here -> http://www.microsoft.com/downloads/details.aspx?FamilyID=818234dc-a17b-4f09-b282-c6830fead499&DisplayLang=en
page 5 that you can use MSSQL server 2005 standard edition in Clustering mode with 2 nodes.

But my question is :
Can I use windows 2003 standard edition (Clustering mode managed ?) or I only can use windows 2003 enterprise edition ?

J.Windows 2003 Standard supports a 2 node cluster and SQL Server 2005 Standard also supports a 2 node cluster, so yes.

insertion into sql server table failed

Hi ,
At SQL server's end , i have put my windows id as a readonly for that
database.
however from MS Access when i specify the ODBC i used the sa id & pwd
from Ms Access , i linked to the SQL server db using ODBC connection ,when i
tried to insert some data into SQL server i was not allowed
why is that so as i was using sa pwd from the odbc connection
Could anyone kindly advise ?
tks & rdgs
Don't think it has much to do with the security context -
more likely related to how the tables are linked or an ODBC
issue depending on the details of the error you receive.
Make sure you have defined a primary key or unique
identifier for the tables you are linking.
-Sue
On Tue, 6 Sep 2005 18:10:03 -0700, "maxzsim"
<maxzsim@.discussions.microsoft.com> wrote:

>Hi ,
> At SQL server's end , i have put my windows id as a readonly for that
>database.
> however from MS Access when i specify the ODBC i used the sa id & pwd
>from Ms Access , i linked to the SQL server db using ODBC connection ,when i
>tried to insert some data into SQL server i was not allowed
> why is that so as i was using sa pwd from the odbc connection
> Could anyone kindly advise ?
>tks & rdgs
|||Hi
From the local table in Ms Access ,i have added a primary and tried
inserting it into the tbl in SQL Server in Production but i have got a key
violation error
However, when i insert into a local SQL Server it's ok
tks & rdgs
"Sue Hoegemeier" wrote:

> Don't think it has much to do with the security context -
> more likely related to how the tables are linked or an ODBC
> issue depending on the details of the error you receive.
> Make sure you have defined a primary key or unique
> identifier for the tables you are linking.
> -Sue
> On Tue, 6 Sep 2005 18:10:03 -0700, "maxzsim"
> <maxzsim@.discussions.microsoft.com> wrote:
>
>

Inserting records with value outside replication identity ranges

I have a live system that uses merge replication. We are upgrading the
system by setting up a whole new set of servers. When we go live on the new
servers, I would like to copy into the new server database, any changes that
have been made to the old databases. Unfortunately, replication adds check
constraints to identity columns starting with the last identity value in the
database. The old system is still adding id values below the maximum id
(e.g. each region is adding values within their own range which is below the
maximum id in the table.)
I can't just copy the entire database and then setup replication because the
snapshot would take way too long to get to one of the subscribers and we need
to be able to switchover relatively quickly.
Since SQL Server does not let me modify or drop the identity column check
constraint that replication added, how can I add these identity values after
replication has already been set up on the new system?
There could be other issues though. What if the subscriber record is updated
rather than inserted - how will you know which updated rows to take? I think
the simplest way is to sync all subscribers prior to migrating the production
database to the new server. Then using this as the master, set up replication
from the new publisher.
Paul Ibison
|||During the cutover, we will stop all changes to the old database, wait for
replication to sync up, then copy changes from the old publisher over to the
new publisher. then get everyone connected to the new servers.
One of our subscribers is in China where network connectivity is slow and
unreliable. I have tried getting a snapshot with all the data to this
subscriber and it just takes too long - days if it ever succeeds, which so
far it has not. I have to get the snapshot to China with some of the tables
empty, then add the data after.
"Paul Ibison" wrote:

> There could be other issues though. What if the subscriber record is updated
> rather than inserted - how will you know which updated rows to take? I think
> the simplest way is to sync all subscribers prior to migrating the production
> database to the new server. Then using this as the master, set up replication
> from the new publisher.
> Paul Ibison