can't start mssqlserver

I installed a copy of SQL server 2005 on a Win 2003 machine. I connected remotely from another machine and started Sql Server Configuration manager. The MSSQLServer is stopped. So, I click to start and it failed. The error it gave me was that it time out. I am new to SQL 2005 and I thought the next step after installing was to configure. Can anyone help me please.

Check in the SQL Server log file for any info. If SQL received the startup request, the log will show why the timeout occurred. Presumably there was a configuration problem that caused startup to fail.

Also check the network configuration. I believe local connections require shared memory to be enabled.

|||Hi, in addition to the aother post, try to make a snapshot of your event log if you can't figure out the problem and send the appropiate parts (like starting the service which breaks) to this forum again.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

Can't remotely access SQL 2005 named instance

SuHi,
I just installed SQL 2005 Developer Edition on a brand new W2K3 w/ SP1
server. I installed a default instance, and then a named instance called
"DEV".
Initially, I could not access either instance from a remote machine. I went
into SQL Server Surface Area Configuration and enabled TCP/IP and Named Pipes
under the Remote Access portion of the dialog for BOTH instances.
I can access the default instance from a remote machine. I still cannot
access the named instance from a remote machine. I have triple checked all
my settings. They are exactly the same for both instances.
The error message I receive is:
26 - Error locating server/instance specified
I can't see the DEV instance in the SQL Server browse list either.
Can anyone help?
Is the SQL Server Browser service started on the server?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
news:2B8ED4DB-E631-4C73-9C06-072557EC7FAA@.microsoft.com...
> SuHi,
> I just installed SQL 2005 Developer Edition on a brand new W2K3 w/ SP1
> server. I installed a default instance, and then a named instance called
> "DEV".
> Initially, I could not access either instance from a remote machine. I went
> into SQL Server Surface Area Configuration and enabled TCP/IP and Named Pipes
> under the Remote Access portion of the dialog for BOTH instances.
> I can access the default instance from a remote machine. I still cannot
> access the named instance from a remote machine. I have triple checked all
> my settings. They are exactly the same for both instances.
> The error message I receive is:
> 26 - Error locating server/instance specified
> I can't see the DEV instance in the SQL Server browse list either.
> Can anyone help?
|||Thanks! That fixed the issue. You have helped me before, Tibor, and I thank
you again for your expertise. I may be a MCDBA, but I'm still a 2005 novice

I read a blurb somewhere that enabling the Browser service opens security
holes in SQL Server. Is this true, and if it is how does it indeed open
security holes?
- Anthony
"Tibor Karaszi" wrote:

> Is the SQL Server Browser service started on the server?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
> news:2B8ED4DB-E631-4C73-9C06-072557EC7FAA@.microsoft.com...
>
|||You're welcome Anthony. :-)

> I read a blurb somewhere that enabling the Browser service opens security
> holes in SQL Server. Is this true, and if it is how does it indeed open
> security holes?
Every surface you open opens increases the threat area. I don't know of any particular issues with
the SQL Browser. The same functionality existed in 2000, but it was built-in to the database engine.
To be more specific I guess we would have to see that comment.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
news:B18F79B4-C704-4903-A98C-FC3D5F25323D@.microsoft.com...[vbcol=seagreen]
> Thanks! That fixed the issue. You have helped me before, Tibor, and I thank
> you again for your expertise. I may be a MCDBA, but I'm still a 2005 novice
>
> I read a blurb somewhere that enabling the Browser service opens security
> holes in SQL Server. Is this true, and if it is how does it indeed open
> security holes?
> - Anthony
> "Tibor Karaszi" wrote:
|||"Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
news:2B8ED4DB-E631-4C73-9C06-072557EC7FAA@.microsoft.com...
> SuHi,
> I just installed SQL 2005 Developer Edition on a brand new W2K3 w/ SP1
> server. I installed a default instance, and then a named instance called
> "DEV".
> Initially, I could not access either instance from a remote machine. I
> went
> into SQL Server Surface Area Configuration and enabled TCP/IP and Named
> Pipes
> under the Remote Access portion of the dialog for BOTH instances.
> I can access the default instance from a remote machine. I still cannot
> access the named instance from a remote machine. I have triple checked
> all
> my settings. They are exactly the same for both instances.
Have you tried the SQL Server Configuration Manager on the W2K machine.
This iw wher you open up the IP/Named pipes.

Can't remotely access SQL 2005 named instance

SuHi,
I just installed SQL 2005 Developer Edition on a brand new W2K3 w/ SP1
server. I installed a default instance, and then a named instance called
"DEV".
Initially, I could not access either instance from a remote machine. I went
into SQL Server Surface Area Configuration and enabled TCP/IP and Named Pipe
s
under the Remote Access portion of the dialog for BOTH instances.
I can access the default instance from a remote machine. I still cannot
access the named instance from a remote machine. I have triple checked all
my settings. They are exactly the same for both instances.
The error message I receive is:
26 - Error locating server/instance specified
I can't see the DEV instance in the SQL Server browse list either.
Can anyone help?Is the SQL Server Browser service started on the server?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
news:2B8ED4DB-E631-4C73-9C06-072557EC7FAA@.microsoft.com...
> SuHi,
> I just installed SQL 2005 Developer Edition on a brand new W2K3 w/ SP1
> server. I installed a default instance, and then a named instance called
> "DEV".
> Initially, I could not access either instance from a remote machine. I we
nt
> into SQL Server Surface Area Configuration and enabled TCP/IP and Named Pi
pes
> under the Remote Access portion of the dialog for BOTH instances.
> I can access the default instance from a remote machine. I still cannot
> access the named instance from a remote machine. I have triple checked al
l
> my settings. They are exactly the same for both instances.
> The error message I receive is:
> 26 - Error locating server/instance specified
> I can't see the DEV instance in the SQL Server browse list either.
> Can anyone help?|||Thanks! That fixed the issue. You have helped me before, Tibor, and I than
k
you again for your expertise. I may be a MCDBA, but I'm still a 2005 novice

I read a blurb somewhere that enabling the Browser service opens security
holes in SQL Server. Is this true, and if it is how does it indeed open
security holes?
- Anthony
"Tibor Karaszi" wrote:

> Is the SQL Server Browser service started on the server?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
> news:2B8ED4DB-E631-4C73-9C06-072557EC7FAA@.microsoft.com...
>|||You're welcome Anthony. :-)

> I read a blurb somewhere that enabling the Browser service opens security
> holes in SQL Server. Is this true, and if it is how does it indeed open
> security holes?
Every surface you open opens increases the threat area. I don't know of any
particular issues with
the SQL Browser. The same functionality existed in 2000, but it was built-in
to the database engine.
To be more specific I guess we would have to see that comment.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
news:B18F79B4-C704-4903-A98C-FC3D5F25323D@.microsoft.com...[vbcol=seagreen]
> Thanks! That fixed the issue. You have helped me before, Tibor, and I th
ank
> you again for your expertise. I may be a MCDBA, but I'm still a 2005 novi
ce
>
> I read a blurb somewhere that enabling the Browser service opens security
> holes in SQL Server. Is this true, and if it is how does it indeed open
> security holes?
> - Anthony
> "Tibor Karaszi" wrote:
>|||"Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
news:2B8ED4DB-E631-4C73-9C06-072557EC7FAA@.microsoft.com...
> SuHi,
> I just installed SQL 2005 Developer Edition on a brand new W2K3 w/ SP1
> server. I installed a default instance, and then a named instance called
> "DEV".
> Initially, I could not access either instance from a remote machine. I
> went
> into SQL Server Surface Area Configuration and enabled TCP/IP and Named
> Pipes
> under the Remote Access portion of the dialog for BOTH instances.
> I can access the default instance from a remote machine. I still cannot
> access the named instance from a remote machine. I have triple checked
> all
> my settings. They are exactly the same for both instances.
Have you tried the SQL Server Configuration Manager on the W2K machine.
This iw wher you open up the IP/Named pipes.

Can't remotely access SQL 2005 named instance

SuHi,
I just installed SQL 2005 Developer Edition on a brand new W2K3 w/ SP1
server. I installed a default instance, and then a named instance called
"DEV".
Initially, I could not access either instance from a remote machine. I went
into SQL Server Surface Area Configuration and enabled TCP/IP and Named Pipes
under the Remote Access portion of the dialog for BOTH instances.
I can access the default instance from a remote machine. I still cannot
access the named instance from a remote machine. I have triple checked all
my settings. They are exactly the same for both instances.
The error message I receive is:
26 - Error locating server/instance specified
I can't see the DEV instance in the SQL Server browse list either.
Can anyone help?Is the SQL Server Browser service started on the server?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
news:2B8ED4DB-E631-4C73-9C06-072557EC7FAA@.microsoft.com...
> SuHi,
> I just installed SQL 2005 Developer Edition on a brand new W2K3 w/ SP1
> server. I installed a default instance, and then a named instance called
> "DEV".
> Initially, I could not access either instance from a remote machine. I went
> into SQL Server Surface Area Configuration and enabled TCP/IP and Named Pipes
> under the Remote Access portion of the dialog for BOTH instances.
> I can access the default instance from a remote machine. I still cannot
> access the named instance from a remote machine. I have triple checked all
> my settings. They are exactly the same for both instances.
> The error message I receive is:
> 26 - Error locating server/instance specified
> I can't see the DEV instance in the SQL Server browse list either.
> Can anyone help?|||Thanks! That fixed the issue. You have helped me before, Tibor, and I thank
you again for your expertise. I may be a MCDBA, but I'm still a 2005 novice
:)
I read a blurb somewhere that enabling the Browser service opens security
holes in SQL Server. Is this true, and if it is how does it indeed open
security holes?
- Anthony
"Tibor Karaszi" wrote:
> Is the SQL Server Browser service started on the server?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
> news:2B8ED4DB-E631-4C73-9C06-072557EC7FAA@.microsoft.com...
> > SuHi,
> >
> > I just installed SQL 2005 Developer Edition on a brand new W2K3 w/ SP1
> > server. I installed a default instance, and then a named instance called
> > "DEV".
> >
> > Initially, I could not access either instance from a remote machine. I went
> > into SQL Server Surface Area Configuration and enabled TCP/IP and Named Pipes
> > under the Remote Access portion of the dialog for BOTH instances.
> >
> > I can access the default instance from a remote machine. I still cannot
> > access the named instance from a remote machine. I have triple checked all
> > my settings. They are exactly the same for both instances.
> >
> > The error message I receive is:
> >
> > 26 - Error locating server/instance specified
> >
> > I can't see the DEV instance in the SQL Server browse list either.
> >
> > Can anyone help?
>|||You're welcome Anthony. :-)
> I read a blurb somewhere that enabling the Browser service opens security
> holes in SQL Server. Is this true, and if it is how does it indeed open
> security holes?
Every surface you open opens increases the threat area. I don't know of any particular issues with
the SQL Browser. The same functionality existed in 2000, but it was built-in to the database engine.
To be more specific I guess we would have to see that comment.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
news:B18F79B4-C704-4903-A98C-FC3D5F25323D@.microsoft.com...
> Thanks! That fixed the issue. You have helped me before, Tibor, and I thank
> you again for your expertise. I may be a MCDBA, but I'm still a 2005 novice
> :)
> I read a blurb somewhere that enabling the Browser service opens security
> holes in SQL Server. Is this true, and if it is how does it indeed open
> security holes?
> - Anthony
> "Tibor Karaszi" wrote:
>> Is the SQL Server Browser service started on the server?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
>> news:2B8ED4DB-E631-4C73-9C06-072557EC7FAA@.microsoft.com...
>> > SuHi,
>> >
>> > I just installed SQL 2005 Developer Edition on a brand new W2K3 w/ SP1
>> > server. I installed a default instance, and then a named instance called
>> > "DEV".
>> >
>> > Initially, I could not access either instance from a remote machine. I went
>> > into SQL Server Surface Area Configuration and enabled TCP/IP and Named Pipes
>> > under the Remote Access portion of the dialog for BOTH instances.
>> >
>> > I can access the default instance from a remote machine. I still cannot
>> > access the named instance from a remote machine. I have triple checked all
>> > my settings. They are exactly the same for both instances.
>> >
>> > The error message I receive is:
>> >
>> > 26 - Error locating server/instance specified
>> >
>> > I can't see the DEV instance in the SQL Server browse list either.
>> >
>> > Can anyone help?
>>|||"Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
news:2B8ED4DB-E631-4C73-9C06-072557EC7FAA@.microsoft.com...
> SuHi,
> I just installed SQL 2005 Developer Edition on a brand new W2K3 w/ SP1
> server. I installed a default instance, and then a named instance called
> "DEV".
> Initially, I could not access either instance from a remote machine. I
> went
> into SQL Server Surface Area Configuration and enabled TCP/IP and Named
> Pipes
> under the Remote Access portion of the dialog for BOTH instances.
> I can access the default instance from a remote machine. I still cannot
> access the named instance from a remote machine. I have triple checked
> all
> my settings. They are exactly the same for both instances.
Have you tried the SQL Server Configuration Manager on the W2K machine.
This iw wher you open up the IP/Named pipes.

Cant login remotely even though membership data is present

(Sorry this was posted to VWD2005 Express by mistake)

I have created a simple project using ASP.NET 2.0 which enables a user to login. I created the login user using the Web Administration Tool in Visual Studio 2005.

I created everything locally and it worked.

Locally I have 2 databases. One containing normal data (which my site uses to populate a GridView control) and the other being ASPNETDB.MDF - which contains membership (login user) data. These 2 databases sit in the App_Data folder which is in the root of the project.

I have a remote database which is hosted in a shared environment.

This is just the one database and it appears to have all tables in the one database (membership tables and normal tables - such as the one I use to populate my GridView control).

I uploaded the website and using the Database Publishing Wizard I uploaded the database data to the shared host. I also changed the connection string to point to my remote database.

If I visit the website the GridView is populating correctly (pulling data from the remote database) but when I try to login it crashes. The error is "Access denied creating App_Data sub directory".

The membership login details for the user I created are in the remote database as I have compared the data in it to the data in my ASPNETDB.MDF local database.

If I launch from within Visual Studio 2005 then it allows me to login perfectly well.

Please does anybody know why it won't let me login when I access it via the website?

Many thanks for any help,

Graham

It seems that appropriate machine user (that is usualy NETWORK SERVICE) under which this web application is running has no write rights over App_Data subdirectory.

Check with your host if that is setup properly.

|||

Well I am pleased to say my work colleague fixed this one.

I had to change the ConnectionString name to LocalSqlServer and change my DataSource control (see below).

I had them named something else before. Please can somebody explain what is going on here and why it wasn't working before?

<connectionStrings>
<remove name="LocalSqlServer" />
<add name="LocalSqlServer" connectionString="BLAH BLAH BLAH"
providerName="System.Data.SqlClient" />
</connectionStrings>

<asp:SqlDataSource ID="SqlDataSource1" runat="server" ConnectionString="<%$ ConnectionStrings:LocalSqlServer %>"

Many thanks.

|||That's because LocalSqlServer is the connection string used by?default security providers. Take a look at this article for details:

http://weblogs.asp.net/scottgu/archive/2005/08/25/423703.aspx

Cant' log in anymore

Hi,
I pulled down all the files from my live
database which is running remotely.
When I did this, I overwrote my Web Page
connection string, which I used to log into a
local production instance of this database.
After a few weeks I got around to recreating
my connection string, but it won't work.
Neither does my partner's login info work and
we are both admins. I am the dbo. Now I am
wondering if coincidentally somehow my machine
was compromised. Is there someway I could be
kept out? I can still log onto the machine/server
which runs SQL Server for access to the drives.
I am running Windows/2000
and SQL 2000. My authentication
is set to Windows only. I run my network
as a workgroup and there is no "Active Directory".
Logging into the server to access the drives is
no problem. The login is of course the same, since
I am using Windows only authentication.
Is there anyplace I can look to see if there
is some way to get this working again?
It is not making sense to me that I can
log in to the HDs on the LAN but cannot
log into SQL databases via a webpage.
The folders are in folder needed a Windows
login, but the SQL server logs just keep showing
that access is denied because the login is not
a trusted login, which is not true, but I cannot
prove that to the server.
Could I have been compromised or does
this sound like some other confusion?
Thanks for anyone's feedback,
FoxIf the authentication is set to Windows Authentication and you're not in a
domain, then you're basically using Workgroup security to connect. The
same username and password must exists on both machines.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.