can't get in anymore

I installed SQL 2005 on a new machine last week. Created a database using
scripts. Worked fine for a few days.
Yesterday, I attached a database that had been created on another machine,
with SQL 2000. Seemed to work fine. I closed SQL Server to work on something
else, then opened it back up. It won't let me in now. It says that it
doesn't allow remote connections, even though I am doing it from the same
machine that it resides on.
Text of the message is below the line at the bottom of this.
I tried changing the way I log in, including Windows Authentication, SQL
Server authentication, using my network name, and then using the user name I
created just for this thing when I installed SQL Server. I alwasy get the
same message. I also tried connecting remotely from another machine.
I was able to use this same machine to connect to another SQL Server
instance on the network, so it's apparent that the installation of SQL
Server isn't messed up.
I know that I will probably get asked about an admin username and password,
but I don't know what mine is. I tried sa with no password, but it didn't
work.
This is really causing some problems and I have something due at noon today.
Any help appreciated.
If I uninstalled SQL Server and re-install, will that let me in then?
-----
TITLE: Connect to Server
--
Cannot connect to SERV423.
--
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 2)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476
--
BUTTONS:
OK
--did you enable TCP/IP and gave a proper IP Address in network
configuration under configuration manager?|||I don't recall that being part of the installation. Is it something I can
change now?
"Shadow" <dinu_babu@.yahoo.com> wrote in message
news:1138289713.792093.149830@.z14g2000cwz.googlegroups.com...
> did you enable TCP/IP and gave a proper IP Address in network
> configuration under configuration manager?
>|||I had never seen Config mgr before you mentioned it. Opening it up showed me
that the services weren't running. I started them and it works now.
thanks
"Shadow" <dinu_babu@.yahoo.com> wrote in message
news:1138289713.792093.149830@.z14g2000cwz.googlegroups.com...
> did you enable TCP/IP and gave a proper IP Address in network
> configuration under configuration manager?
>

can't get in anymore

I installed SQL 2005 on a new machine last week. Created a database using
scripts. Worked fine for a few days.
Yesterday, I attached a database that had been created on another machine,
with SQL 2000. Seemed to work fine. I closed SQL Server to work on something
else, then opened it back up. It won't let me in now. It says that it
doesn't allow remote connections, even though I am doing it from the same
machine that it resides on.
Text of the message is below the line at the bottom of this.
I tried changing the way I log in, including Windows Authentication, SQL
Server authentication, using my network name, and then using the user name I
created just for this thing when I installed SQL Server. I alwasy get the
same message. I also tried connecting remotely from another machine.
I was able to use this same machine to connect to another SQL Server
instance on the network, so it's apparent that the installation of SQL
Server isn't messed up.
I know that I will probably get asked about an admin username and password,
but I don't know what mine is. I tried sa with no password, but it didn't
work.
This is really causing some problems and I have something due at noon today.
Any help appreciated.
If I uninstalled SQL Server and re-install, will that let me in then?
-----
TITLE: Connect to Server
Cannot connect to SERV423.
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 2)
For help, click:
http://go.microsoft.com/fwlink?ProdN...2&LinkId=20476
BUTTONS:
OK
did you enable TCP/IP and gave a proper IP Address in network
configuration under configuration manager?
|||I don't recall that being part of the installation. Is it something I can
change now?
"Shadow" <dinu_babu@.yahoo.com> wrote in message
news:1138289713.792093.149830@.z14g2000cwz.googlegr oups.com...
> did you enable TCP/IP and gave a proper IP Address in network
> configuration under configuration manager?
>
|||I had never seen Config mgr before you mentioned it. Opening it up showed me
that the services weren't running. I started them and it works now.
thanks
"Shadow" <dinu_babu@.yahoo.com> wrote in message
news:1138289713.792093.149830@.z14g2000cwz.googlegr oups.com...
> did you enable TCP/IP and gave a proper IP Address in network
> configuration under configuration manager?
>

can't get in anymore

I installed SQL 2005 on a new machine last week. Created a database using
scripts. Worked fine for a few days.
Yesterday, I attached a database that had been created on another machine,
with SQL 2000. Seemed to work fine. I closed SQL Server to work on something
else, then opened it back up. It won't let me in now. It says that it
doesn't allow remote connections, even though I am doing it from the same
machine that it resides on.
Text of the message is below the line at the bottom of this.
I tried changing the way I log in, including Windows Authentication, SQL
Server authentication, using my network name, and then using the user name I
created just for this thing when I installed SQL Server. I alwasy get the
same message. I also tried connecting remotely from another machine.
I was able to use this same machine to connect to another SQL Server
instance on the network, so it's apparent that the installation of SQL
Server isn't messed up.
I know that I will probably get asked about an admin username and password,
but I don't know what mine is. I tried sa with no password, but it didn't
work.
This is really causing some problems and I have something due at noon today.
Any help appreciated.
If I uninstalled SQL Server and re-install, will that let me in then?
----
--
TITLE: Connect to Server
--
Cannot connect to SERV423.
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 2)
For help, click:
tID=2&LinkId=20476" target="_blank">http://go.microsoft.com/fwlink?Prod...=2&LinkId=20476
BUTTONS:
OK
--did you enable TCP/IP and gave a proper IP Address in network
configuration under configuration manager?|||I don't recall that being part of the installation. Is it something I can
change now?
"Shadow" <dinu_babu@.yahoo.com> wrote in message
news:1138289713.792093.149830@.z14g2000cwz.googlegroups.com...
> did you enable TCP/IP and gave a proper IP Address in network
> configuration under configuration manager?
>|||I had never seen Config mgr before you mentioned it. Opening it up showed me
that the services weren't running. I started them and it works now.
thanks
"Shadow" <dinu_babu@.yahoo.com> wrote in message
news:1138289713.792093.149830@.z14g2000cwz.googlegroups.com...
> did you enable TCP/IP and gave a proper IP Address in network
> configuration under configuration manager?
>sql

Can't Deploy AdventureWorks Database

Hi All,

I created a named instance of SQL SERVER 2005 (Evaluation version) on Windows XP pro, attached the AdventureWorks and AdventureWorks DW databases to the database engine, and tried to deploy the AdventureWorks DW (Enterprise and Standard) database in Analysis Services using SQL SERVER Business Intelligence Development Studio.

For some reason, I encountered the following error (after deployment during processing):

Error 1 OLE DB error: OLE DB or ODBC error: Login timeout expired; HYT00; An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.; 08001; Named Pipes Provider: Could not open a connection to SQL Server [2]. ; 08001. 0 0

Please note that I used the configuration manager to enable named pipes and allow remote connections. I also, renamed the target server (to the named server instance instead of the localhost), disabled my Windows and Norton firewalls, and changed the deployment server edition to the Evaluation version in the Adventure Works DW Property page.

Nothing seems to work. Any help would be greatly appreciated!

Thanks,

Raj

Hi,

We also experienced a similar problem deploying the AdventureWorks DW using the Business Intelligence Development Studio. Our error is as follows:

Error 1 OLE DB error: OLE DB or ODBC error: Communication link failure; 08S01; Shared Memory Provider: The system cannot open the file. ; 08S01; Login failed for user 'NT AUTHORITY\SYSTEM'.; 28000; Cannot open database requested in login 'AdventureWorksDW'. Login fails.; 42000. 0 0

This error occurred after we had dropped and uninstalled the sample databases from a previous install. Please note we downloaded the samples from Microsoft and used the AdventureWorks Data Warehouse Database and Analysis Services Project to install the databases.

Brad

|||

We are having the exact same error. Did you all find a solution?

|||

I'm moving this post to the Tools forum since this isn't a setup or upgrade issue.

G'luck.

|||Hi everyone!
I just had the same problem and solved it. What you have to do is:
1) Right-click the project name, and choose properties
2) In the deployment tab change the server name from localhost to your instance name
3) Double-click the data source in solution explorer
4) In General tab click Edit to change the connection string
5) Choose Native OLE DB\Microsoft OLE DB Provider for SQL Server
6) Type in your server name
7) Select the AdventureWorksDW as database name and click OK
Now the deployment should be successfull...|||

Try:

Double click on AdvantureWork.ds from DataSource (From Solution Explorer). and in Impersonation Information Select the Use the Service Account.

Can't Deploy AdventureWorks Database

Hi All,

I created a named instance of SQL SERVER 2005 (Evaluation version) on Windows XP pro, attached the AdventureWorks and AdventureWorks DW databases to the database engine, and tried to deploy the AdventureWorks DW (Enterprise and Standard) database in Analysis Services using SQL SERVER Business Intelligence Development Studio.

For some reason, I encountered the following error (after deployment during processing):

Error 1 OLE DB error: OLE DB or ODBC error: Login timeout expired; HYT00; An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.; 08001; Named Pipes Provider: Could not open a connection to SQL Server [2]. ; 08001. 0 0

Please note that I used the configuration manager to enable named pipes and allow remote connections. I also, renamed the target server (to the named server instance instead of the localhost), disabled my Windows and Norton firewalls, and changed the deployment server edition to the Evaluation version in the Adventure Works DW Property page.

Nothing seems to work. Any help would be greatly appreciated!

Thanks,

Raj

Hi,

We also experienced a similar problem deploying the AdventureWorks DW using the Business Intelligence Development Studio. Our error is as follows:

Error 1 OLE DB error: OLE DB or ODBC error: Communication link failure; 08S01; Shared Memory Provider: The system cannot open the file. ; 08S01; Login failed for user 'NT AUTHORITY\SYSTEM'.; 28000; Cannot open database requested in login 'AdventureWorksDW'. Login fails.; 42000. 0 0

This error occurred after we had dropped and uninstalled the sample databases from a previous install. Please note we downloaded the samples from Microsoft and used the AdventureWorks Data Warehouse Database and Analysis Services Project to install the databases.

Brad

|||

We are having the exact same error. Did you all find a solution?

|||

I'm moving this post to the Tools forum since this isn't a setup or upgrade issue.

G'luck.

|||Hi everyone!
I just had the same problem and solved it. What you have to do is:
1) Right-click the project name, and choose properties
2) In the deployment tab change the server name from localhost to your instance name
3) Double-click the data source in solution explorer
4) In General tab click Edit to change the connection string
5) Choose Native OLE DB\Microsoft OLE DB Provider for SQL Server
6) Type in your server name
7) Select the AdventureWorksDW as database name and click OK
Now the deployment should be successfull...|||

Try:

Double click on AdvantureWork.ds from DataSource (From Solution Explorer). and in Impersonation Information Select the Use the Service Account.

Can't Deploy AdventureWorks Database

Hi All,

I created a named instance of SQL SERVER 2005 (Evaluation version) on Windows XP pro, attached the AdventureWorks and AdventureWorks DW databases to the database engine, and tried to deploy the AdventureWorks DW (Enterprise and Standard) database in Analysis Services using SQL SERVER Business Intelligence Development Studio.

For some reason, I encountered the following error (after deployment during processing):

Error 1 OLE DB error: OLE DB or ODBC error: Login timeout expired; HYT00; An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.; 08001; Named Pipes Provider: Could not open a connection to SQL Server [2]. ; 08001. 0 0

Please note that I used the configuration manager to enable named pipes and allow remote connections. I also, renamed the target server (to the named server instance instead of the localhost), disabled my Windows and Norton firewalls, and changed the deployment server edition to the Evaluation version in the Adventure Works DW Property page.

Nothing seems to work. Any help would be greatly appreciated!

Thanks,

Raj

Hi,

We also experienced a similar problem deploying the AdventureWorks DW using the Business Intelligence Development Studio. Our error is as follows:

Error 1 OLE DB error: OLE DB or ODBC error: Communication link failure; 08S01; Shared Memory Provider: The system cannot open the file. ; 08S01; Login failed for user 'NT AUTHORITY\SYSTEM'.; 28000; Cannot open database requested in login 'AdventureWorksDW'. Login fails.; 42000. 0 0

This error occurred after we had dropped and uninstalled the sample databases from a previous install. Please note we downloaded the samples from Microsoft and used the AdventureWorks Data Warehouse Database and Analysis Services Project to install the databases.

Brad

|||

We are having the exact same error. Did you all find a solution?

|||

I'm moving this post to the Tools forum since this isn't a setup or upgrade issue.

G'luck.

|||Hi everyone!
I just had the same problem and solved it. What you have to do is:
1) Right-click the project name, and choose properties
2) In the deployment tab change the server name from localhost to your instance name
3) Double-click the data source in solution explorer
4) In General tab click Edit to change the connection string
5) Choose Native OLE DB\Microsoft OLE DB Provider for SQL Server
6) Type in your server name
7) Select the AdventureWorksDW as database name and click OK
Now the deployment should be successfull...|||

Try:

Double click on AdvantureWork.ds from DataSource (From Solution Explorer). and in Impersonation Information Select the Use the Service Account.

can''t connect to local user instance

Just when I think I have this stuff figured out, it bites me back everytime.

I'm

trying to deploy an mdf out to a different machine, and attached to it with local user instance. I connect without problem from my development

machine with a local user instance, which also has Express Manager resident,

and I can connect to a server instance without problem.

What I can't do is

copy the .mdf database over to another workstation, which has Sql Native

Client installed, and connect to the database using a local user

instance! I can connect to a server instance without problem from this

other workstation. Here's my connect string for local user instance

that works fine from my dev machine:

Provider=SQLNCLI.1;Persist

Security Info=False;Integrated Security=SSPI;Data

Source=.\sqlexpress;AttachDBFileName=<full path_name and mdf

filename>;User Instance=true;

The error I get upon trying to connect with other stations is:

Error -2147467259
Database not found or cound not connect to database

I've

tried this every way I know how. I've copied the database from my dev

machine both with and without having detached the database from the

local instance. I've tried detaching from a server instance and copying

the file over. Nothing works, and I've done this before! What gives with this thing?

Rick

Hi,

is SQL Server Service allowed to access the datafiles ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||Jens ... How can tell this? What service should I examine? I don't see any reference to the Sql Native client, other than I know it's installed.

I thought this process consisted of:

- install the Sql Native Client on target machine
- put a local copy of the database on target machine
- connect to the mdf with a local user instance

As I said, I can connect to remote server database from the machine. The folder names differ from my development machine to the target machine, but that shouldn't make difference, should it? I will say that in Sql Express Manager on my dev machine (which works), the full path and database name (i.e..c:\_source\project\mydata.mdf) shows in the database tree.

Rick|||

Hi Rick,

SQL Express does not allow attaching database from a UNC or mapped drive. It wasn't totally clear, but it reads like that what you're trying to do. Also, you can not connect to a User Instance on a different machine as User Instances only support local named pipes connections.

Mike

|||Nevermind. I'm apparently having a mental episode and forgot the one vital requirement of installing SqlExpress on the target instead of just the Sql Native Client. Hadn't had to do this in a while since I've been hitting a server for Sql Express databases. Sorry!

Rick

can't connect to local user instance

Just when I think I have this stuff figured out, it bites me back everytime.

I'm

trying to deploy an mdf out to a different machine, and attached to it with local user instance. I connect without problem from my development

machine with a local user instance, which also has Express Manager resident,

and I can connect to a server instance without problem.

What I can't do is

copy the .mdf database over to another workstation, which has Sql Native

Client installed, and connect to the database using a local user

instance! I can connect to a server instance without problem from this

other workstation. Here's my connect string for local user instance

that works fine from my dev machine:

Provider=SQLNCLI.1;Persist

Security Info=False;Integrated Security=SSPI;Data

Source=.\sqlexpress;AttachDBFileName=<full path_name and mdf

filename>;User Instance=true;

The error I get upon trying to connect with other stations is:

Error -2147467259
Database not found or cound not connect to database

I've

tried this every way I know how. I've copied the database from my dev

machine both with and without having detached the database from the

local instance. I've tried detaching from a server instance and copying

the file over. Nothing works, and I've done this before! What gives with this thing?

Rick

Hi,

is SQL Server Service allowed to access the datafiles ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||Jens ... How can tell this? What service should I examine? I don't see any reference to the Sql Native client, other than I know it's installed.

I thought this process consisted of:

- install the Sql Native Client on target machine
- put a local copy of the database on target machine
- connect to the mdf with a local user instance

As I said, I can connect to remote server database from the machine. The folder names differ from my development machine to the target machine, but that shouldn't make difference, should it? I will say that in Sql Express Manager on my dev machine (which works), the full path and database name (i.e..c:\_source\project\mydata.mdf) shows in the database tree.

Rick|||

Hi Rick,

SQL Express does not allow attaching database from a UNC or mapped drive. It wasn't totally clear, but it reads like that what you're trying to do. Also, you can not connect to a User Instance on a different machine as User Instances only support local named pipes connections.

Mike

|||Nevermind. I'm apparently having a mental episode and forgot the one vital requirement of installing SqlExpress on the target instead of just the Sql Native Client. Hadn't had to do this in a while since I've been hitting a server for Sql Express databases. Sorry!

Rick