Cannot Create New Database

when i am trying to connect to sql server2005 thru Visual studio i am getting an Error:

"SQL Server does not allow remote connections (provider: Named Pipes Provider, error: 40 could not open connection to Sql Server)"

Can any body tell me why is it happening and its Solution....

You will have to enable Remote Connections for your SQL Server instance, by default this is turned off. See the screencast on the screencast section on my website for more details.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

Cannot create an instance of OLE DB provider "VFPOLEDB"

I created a view refer to a visual foxpro with ole db for visual foxpro which was working fine before. But now, I received an error while select the view

Msg 7302, Level 16, State 1, Line 1
Cannot create an instance of OLE DB provider "VFPOLEDB" for linked server "ORST3".

Please advise. Thanks in advance

Hi Stephanie,

You posted this question to microsoft.public.data.oledb on April 3. Later in the thread you said you were successful getting it working, partly due to enabling "Allow inprocess" in the OLE DB setup.

Is this a new problem since you posted on April 3?

Cannot create an instance of OLE DB provider "IBMDADB2" for linked server

System:Win 2003, SQL Server 2005, Using an AD win account that is not a member of the Admin group on the server.

Error message from Management Studio query window:

Msg 7302, Level 16, State 1, Line 1

Cannot create an instance of OLE DB provider "IBMDADB2" for linked server "Sname".

Event messages associated with this error:

App Event ID: 19036

The OLE DB initialization service failed to load. Reinstall Microsoft Data Access Components. If the problem persists, contact product support for the OLEDB provider.

Sys Event ID: 10016

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {2206CDB0-19C1-11D1-89E0-00C04FD7A829}

to the user domain\user SID (S-1-5-21-126051702-1034962659-2130403006-7826). This security permission can be modified using the Component Services administrative tool.

I’m getting this error message when trying to run an openquery statement through a linked server to DB2. (SELECT * FROM OPENQUERY(Sname, 'SELECT * FROM tablename’))

The linked server has a remote login and password that it uses to connect to DB2.

I found this from another post on how to fix this error:

Expand Component Services - Computers - My Computer - DCOM Config Select MSDAINITIALIZE Right Click properties then security

Under Security - Launch Permission: enable Local Launch and Local Activation for your SQL Service account

Under Security - Access permissions: Allow System: Local Access and Remote Access.

After completing these steps I still get the error message but the events are no longer generated.I’ve also tried different variations of these steps.The only way I can get this to work is to either make the AD user a member of the Admin group on the server or by putting in a user account that has admin rights to the server in the MSDAINITIALIZE properties – Identity Tab – Run this App as this User.

Can someone please tell me the steps that I’m missing?

Additional info:

If I set the providers allowinprocess to 1 with this,

EXEC master.dbo.sp_MSset_oledb_prop N'IBMDADB2', N'AllowInProcess', 1

It responds with this error:

OLE DB provider "IBMDADB2" for linked server "LName" returned message " SQL10007N Message "0" could not be retrieved. Reason code: "2".

".

Msg 7303, Level 16, State 1, Line 1

Cannot initialize the data source object of OLE DB provider "IBMDADB2" for linked server "LName".

Cannot create an instance of OLE DB Provider "MSDAC"

Hey Guys,
I'm trying to query a couple of Excel 2007 spreadsheets for some reports
using OpenDataSource in my query to pull in the data.
Everything is find with the preview inside the IDE, but when I deploy my
report I recieve the following error:
An error has occurred during report processing. (rsProcessingAborted)
Query execution failed for data set 'Regression'.
(rsErrorExecutingCommand)
Cannot create an instance of OLE DB provider "MSDASC" for linked
server "(null)".
I've installed 2007 Data Connectivity Components on the report server and
this allowed me to query the data while developing. I'm at a loss why this is
not working after I deploy.
The SQL I'm using to query the data is:
SELECT *
FROM OPENDATASOURCE('Microsoft.ACE.OLEDB.12.0',
'Data Source="\\server\document.xlsm";Extended Properties="Excel 12.0
Macro;HDR=YES"')...Sheet1$
Any ideas/suggestions?My guess if this works in development and not in deployment that it has to
do with file security. The report is executed under a different user account
and that account doesn't have rights to the folder where the Excel data
resides. Just a guess because I have never done this.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"shaggydog" <shaggydog@.discussions.microsoft.com> wrote in message
news:55853C99-FB58-422B-8FB7-EECD3EF37715@.microsoft.com...
> Hey Guys,
> I'm trying to query a couple of Excel 2007 spreadsheets for some reports
> using OpenDataSource in my query to pull in the data.
> Everything is find with the preview inside the IDE, but when I deploy my
> report I recieve the following error:
> An error has occurred during report processing. (rsProcessingAborted)
> Query execution failed for data set 'Regression'.
> (rsErrorExecutingCommand)
> Cannot create an instance of OLE DB provider "MSDASC" for linked
> server "(null)".
> I've installed 2007 Data Connectivity Components on the report server and
> this allowed me to query the data while developing. I'm at a loss why this
> is
> not working after I deploy.
> The SQL I'm using to query the data is:
> SELECT *
> FROM OPENDATASOURCE('Microsoft.ACE.OLEDB.12.0',
> 'Data Source="\\server\document.xlsm";Extended Properties="Excel 12.0
> Macro;HDR=YES"')...Sheet1$
>
> Any ideas/suggestions?
>|||Thanks for your response, while not directly related to file security, it was
a security problem. Here's what I did to solve my problem in case anyone
comes across this thread in the future...
I was using a shared data source which connected using windows
authentication. No matter how I tweaked and fiddled around I could not get
windows authentication to work.
So I setup a SQL account with limited rights. Then provided me with a new
error message stating:
Ad hoc access to OLE DB provider 'Microsoft.ACE.OLEDB.12.0' has been denied.
You must access this provider through a linked server.
While I have Ad hoc access enabled via Surface Configuration, it would not
allow me to perform an ad hoc query if the user account wasn't a sysadmin to
the SQL Server. Ugh!
I played around with tweaking the DisallowAdhocAccess registry setting for
the provider, but I didn't find a way to allow non-sysadmin accounts the
ability to perform ad hoc queries.
In the end using a SQL authentication with a sysadmin account allowed
OpenDataSource to pull in the external data.
For what it's worth....
"Bruce L-C [MVP]" wrote:
> My guess if this works in development and not in deployment that it has to
> do with file security. The report is executed under a different user account
> and that account doesn't have rights to the folder where the Excel data
> resides. Just a guess because I have never done this.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "shaggydog" <shaggydog@.discussions.microsoft.com> wrote in message
> news:55853C99-FB58-422B-8FB7-EECD3EF37715@.microsoft.com...
> > Hey Guys,
> >
> > I'm trying to query a couple of Excel 2007 spreadsheets for some reports
> > using OpenDataSource in my query to pull in the data.
> >
> > Everything is find with the preview inside the IDE, but when I deploy my
> > report I recieve the following error:
> >
> > An error has occurred during report processing. (rsProcessingAborted)
> > Query execution failed for data set 'Regression'.
> > (rsErrorExecutingCommand)
> > Cannot create an instance of OLE DB provider "MSDASC" for linked
> > server "(null)".
> >
> > I've installed 2007 Data Connectivity Components on the report server and
> > this allowed me to query the data while developing. I'm at a loss why this
> > is
> > not working after I deploy.
> >
> > The SQL I'm using to query the data is:
> > SELECT *
> > FROM OPENDATASOURCE('Microsoft.ACE.OLEDB.12.0',
> > 'Data Source="\\server\document.xlsm";Extended Properties="Excel 12.0
> > Macro;HDR=YES"')...Sheet1$
> >
> >
> > Any ideas/suggestions?
> >
>
>

Cannot connection to Oracle DB

I create my datasource using the OLE DB data provider for oracle an when i
test the connection it is successful. When I create the dataset it cannot
connect to the database and says "System.Data.Oracle Client requires Oracle
Client Software version 8.1.7 or greater". I am using PL/SQL Developer that
says it is 9i compatible. Im so lost here and need help. Thanks.We had the Oracle client set up quite a while ago so forgot the steps to set
it up. We did run into some issues. If my memory serves me right, the default
9i installation allows the oci.dll to admin group only, and the web app
(ASPNET by default) or reporting service account (the one you chose during
setup) may not have the necessary permission to see this file. It is one
possible reason.
"Steve" wrote:
> I create my datasource using the OLE DB data provider for oracle an when i
> test the connection it is successful. When I create the dataset it cannot
> connect to the database and says "System.Data.Oracle Client requires Oracle
> Client Software version 8.1.7 or greater". I am using PL/SQL Developer that
> says it is 9i compatible. Im so lost here and need help. Thanks.
>|||Specifically, you may want to check this KB article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;870668
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"Terence Leung" <TerenceLeung@.discussions.microsoft.com> wrote in message
news:9349134D-7982-4C1E-995B-3A761058945E@.microsoft.com...
> We had the Oracle client set up quite a while ago so forgot the steps to
> set
> it up. We did run into some issues. If my memory serves me right, the
> default
> 9i installation allows the oci.dll to admin group only, and the web app
> (ASPNET by default) or reporting service account (the one you chose during
> setup) may not have the necessary permission to see this file. It is one
> possible reason.
> "Steve" wrote:
>> I create my datasource using the OLE DB data provider for oracle an when
>> i
>> test the connection it is successful. When I create the dataset it
>> cannot
>> connect to the database and says "System.Data.Oracle Client requires
>> Oracle
>> Client Software version 8.1.7 or greater". I am using PL/SQL Developer
>> that
>> says it is 9i compatible. Im so lost here and need help. Thanks.|||Niether of those ideas worked. I do not have and oci.dll file on my system
and I am developing on an XP system not a 2003 server system.
"Robert Bruckner [MSFT]" wrote:
> Specifically, you may want to check this KB article:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;870668
>
> -- Robert
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Terence Leung" <TerenceLeung@.discussions.microsoft.com> wrote in message
> news:9349134D-7982-4C1E-995B-3A761058945E@.microsoft.com...
> > We had the Oracle client set up quite a while ago so forgot the steps to
> > set
> > it up. We did run into some issues. If my memory serves me right, the
> > default
> > 9i installation allows the oci.dll to admin group only, and the web app
> > (ASPNET by default) or reporting service account (the one you chose during
> > setup) may not have the necessary permission to see this file. It is one
> > possible reason.
> >
> > "Steve" wrote:
> >
> >> I create my datasource using the OLE DB data provider for oracle an when
> >> i
> >> test the connection it is successful. When I create the dataset it
> >> cannot
> >> connect to the database and says "System.Data.Oracle Client requires
> >> Oracle
> >> Client Software version 8.1.7 or greater". I am using PL/SQL Developer
> >> that
> >> says it is 9i compatible. Im so lost here and need help. Thanks.
> >>
>
>|||If there is no oci.dll on your machine, then the Oracle client software is
not installed. It won't work without it. You can download the Oracle client
software from Oracle Technology Network (www.oracle.com/otn).
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"steve" <steve@.discussions.microsoft.com> wrote in message
news:9BDF4BD5-DF7E-4134-8873-94FBFB5E35AD@.microsoft.com...
> Niether of those ideas worked. I do not have and oci.dll file on my
> system
> and I am developing on an XP system not a 2003 server system.
>
> "Robert Bruckner [MSFT]" wrote:
>> Specifically, you may want to check this KB article:
>> http://support.microsoft.com/default.aspx?scid=kb;en-us;870668
>>
>> -- Robert
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> "Terence Leung" <TerenceLeung@.discussions.microsoft.com> wrote in message
>> news:9349134D-7982-4C1E-995B-3A761058945E@.microsoft.com...
>> > We had the Oracle client set up quite a while ago so forgot the steps
>> > to
>> > set
>> > it up. We did run into some issues. If my memory serves me right, the
>> > default
>> > 9i installation allows the oci.dll to admin group only, and the web app
>> > (ASPNET by default) or reporting service account (the one you chose
>> > during
>> > setup) may not have the necessary permission to see this file. It is
>> > one
>> > possible reason.
>> >
>> > "Steve" wrote:
>> >
>> >> I create my datasource using the OLE DB data provider for oracle an
>> >> when
>> >> i
>> >> test the connection it is successful. When I create the dataset it
>> >> cannot
>> >> connect to the database and says "System.Data.Oracle Client requires
>> >> Oracle
>> >> Client Software version 8.1.7 or greater". I am using PL/SQL
>> >> Developer
>> >> that
>> >> says it is 9i compatible. Im so lost here and need help. Thanks.
>> >>
>>

Cannot connect with SQLCMD - VIA Provider : The specified module could not be found

I have the full version of SQL Server 2005 on my machine under XP. Installed ok and can connect with management studio, but if I try and connect with Analysis Services or even SQLCMD, I get the error below :

HResult 0x7E, Level 16, State 1
VIA Provider: The specified module could not be found.

Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establi
shing a connection to the server. When connecting to SQL Server 2005, this failu
re may be caused by the fact that under the default settings SQL Server does not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.

I have networking enabled, I've enabled all the protocols (apart from VIA because it doesn't start if you do that), and I have all the services running.

Any ideas what can be up ?

I have now fixed this issue and thought I'd just list what was wrong :

The VIA message was because in desperation to connect I had enabled some VIA connections - I think client side.

I disabled all connection types for both client and server except shared memory and TCP/IP.

Still didn't work - and gave a message that the server refused connection.

I then looked at the server side TCP options and found the port number, using SQLCMD tcp:servername,portnumber I could now connect !!

Finally changed the client side TCP to use this port number and now can connect with SQLCMD and no options.

My main gripe is why didn't it all work as installed and why did I have to go through all this to get it to connect !!!

Cannot connect using ADO with Excel Microsoft Jet Provider 4.0

Hi:

I have a vb 6 app that exports data from sql to excel. The user has the ability to select either local or server. When they select server, the connection string is modified to include the server name instead of the local msde instance to look like this:

"provider=sqloledb;data source=MyServer;initial catalog=MyDatabase;user id=UserX;password=PasswordX;database=MyDatabase"

I'm using Microsoft Jet Provider 4.0 and OpenDataSource.

SELECT * INTO TempXL FROM OPENDATASOURCE('Microsoft.Jet.OLEDB.4.0',
'Data Source=C:\test\xltest.xls;Extended Properties=Excel 8.0')...[Sheet1$]

This code works fine when user is accessing msde on local, but when using above DSN, I receive the following message:

"2147217900 - OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEdB.4.0' IDBInitialize:: Initialize returned 0x800040005: The provider did not give any information about the error.]

When I trace the connection, these error messages occur:

Failed to set proper user name ('NT AUTHORITY\SYSTEM') for the connection

[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot alter table 'TblXMyTable' because this table does not exist in database 'master'. (State 42S02) (Code 4902)

[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'TblxMytable'. (State 42S02) (Code 208)

[Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error. The provider did not give any information about the error. (State 42000) (Code 7399)

[Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0' IDBInitialize::Initialize returned 0x80004005: The provider did not give any information about the error.]. (State 01000) (Code 7300)

I am especially puzzled by the second message because I am specifying the database name in my connection string as:

"provider=sqloledb;data source=MyServer;initial catalog=MyDatabase;user id=UserX;password=PasswordX;database=MyDatabase"

I can read from the server copy and copy to Excel, but I cannot write back to SQL. Can someone please tell me what I'm doing wrong?

Thanks in advance for any help.,

I had a problem similar to this when working with VB6, DAO, ADO and SQL Server 2005.

One user could do a query, another user could not.

In fact, the error message was similar to yours. The error message claimed that the table we were trying to query did NOT EXIST.

So, I believe your problem lies with Security.

Try making the user a database owner of the database in question. If this solves your problem, then you can look for a way to set the permission/security correctly for the specifc tables they need access to.

Cannot connect using ADO with Excel Microsoft Jet Provider 4.0

Hi:

I have a vb 6 app that exports data from sql to excel. The user has the ability to select either local or server. When they select server, the connection string is modified to include the server name instead of the local msde instance to look like this:

"provider=sqloledb;data source=MyServer;initial catalog=MyDatabase;user id=UserX;password=PasswordX;database=MyDatabase"

I'm using Microsoft Jet Provider 4.0 and OpenDataSource.

SELECT * INTO TempXL FROM OPENDATASOURCE('Microsoft.Jet.OLEDB.4.0',
'Data Source=C:\test\xltest.xls;Extended Properties=Excel 8.0')...[Sheet1$]

This code works fine when user is accessing msde on local, but when using above DSN, I receive the following message:

"2147217900 - OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEdB.4.0' IDBInitialize:: Initialize returned 0x800040005: The provider did not give any information about the error.]

When I trace the connection, these error messages occur:

Failed to set proper user name ('NT AUTHORITY\SYSTEM') for the connection

[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot alter table 'TblXMyTable' because this table does not exist in database 'master'. (State 42S02) (Code 4902)

[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'TblxMytable'. (State 42S02) (Code 208)

[Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB provider 'Microsoft.Jet.OLEDB.4.0' reported an error. The provider did not give any information about the error. (State 42000) (Code 7399)

[Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB error trace [OLE/DB Provider 'Microsoft.Jet.OLEDB.4.0' IDBInitialize::Initialize returned 0x80004005: The provider did not give any information about the error.]. (State 01000) (Code 7300)

I am especially puzzled by the second message because I am specifying the database name in my connection string as:

"provider=sqloledb;data source=MyServer;initial catalog=MyDatabase;user id=UserX;password=PasswordX;database=MyDatabase"

I can read from the server copy and copy to Excel, but I cannot write back to SQL. Can someone please tell me what I'm doing wrong?

Thanks in advance for any help.,

I had a problem similar to this when working with VB6, DAO, ADO and SQL Server 2005.

One user could do a query, another user could not.

In fact, the error message was similar to yours. The error message claimed that the table we were trying to query did NOT EXIST.

So, I believe your problem lies with Security.

Try making the user a database owner of the database in question. If this solves your problem, then you can look for a way to set the permission/security correctly for the specifc tables they need access to.

Cannot connect to SQL Server 2005 DB from ASP.NET Configuration Tool

Hello,

I am trying to connect to a DB, which is hosted on an SQL Server 2005 by a provider, using ASP.NET Configuration Tool. The result is the following error when I click on the Security Tab:

--
There is a problem with your selected data store. This can be caused by an invalid server name or credentials, or by insufficient permission. It can also be caused by the role manager feature not being enabled. Click the button below to be redirected to a page where you can choose a new data store.

The following message may help in diagnosing the problem: 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)
--

The hosting provider checked that my connection string is correct. They do not know why I get the error, though. Here is a relevant snippet from my web.config:

<connectionStrings>

<removename="LocalSqlServer" />

<addname="LocalSqlServer"

connectionString="Data Source=ABC;Integrated Security=false;Initial Catalog=ABC;User ID=ABC;Password=ABC"

providerName="System.Data.SqlClient" />

</connectionStrings>

ABC is a mock :)

Could anyone pls help? It is much appreciated.

Can you ping the servername successully? Try to use IP address instead of servername as Data Source. Also make sure no firewall is blocking the TCP/IP port used by the SQL Server service (check the port in SQL Server Configuration Manager->SQL Server 2005 Network Configuration)|||

Iori_Jay:

Can you ping the servername successully? Try to use IP address instead of servername as Data Source. Also make sure no firewall is blocking the TCP/IP port used by the SQL Server service (check the port in SQL Server Configuration Manager->SQL Server 2005 Network Configuration)

I can ping the server name successfully. The VWD Express can also connect to the server just fine. So, the firewall does not block the port. But ASP.NET Configuration tool cannot connect to the server. Why? Any ideas are much appreciated.

|||

It did not help to replace the server name by IP address either...

|||

I solved the problem. The process WebDev.WebServer.exe was not allowed to access the internet by the Zone Alarm Firewall. This is a default Zone Alarm setting, which has to be changed manually.

Cannot connect to MSOLAP Provider

I could not get my ASP pages to connect to the Analysis services
Server on a different box. The code that is not working is:
Dim cat
Set cat = Server.CreateObject("ADOMD.Catalog")
cat.ActiveConnection = "Data Source=asServer;Initial
Catalog=MyMart;Provider=msolap;"
My environment is:
The web server box (Server A) : Windows 2003 Server with IIS6, SQL
Server Client sp3 and Analysis Service Client sp3 are both installed.
All other asp pages not using ADOMD all work fine. Most of the web
applications on this server are ASP.NET.
The AS Server box: Windows 2000 with SQL Server 2000 SP3 (8.00.760)
The problem page works fine on other Windows 2000 server with IIS 5.
And the strange thing is: from Server A, the MDX Sample Application
works fine.
Any help is greatly appreciatedHello Tommy,
I noticed that the issue was posted in several groups
(microsoft.public.sqlserver.olap, microsoft.public.sqlserver,
microsoft.public.sqlserver.datawarehouse
)._ I have added a reply to you at
http://msdn.microsoft.com/newsgroup...t.public.sqlser
ver.olap&lang=en&cr=US
If you have follow up questions, please post there and I will work with
you. Thanks.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Cannot connect to MSOLAP Provider

I could not get my ASP pages to connect to the Analysis services
Server on a different box. The code that is not working is:
Dim cat
Set cat = Server.CreateObject("ADOMD.Catalog")
cat.ActiveConnection = "Data Source=asServer;Initial
Catalog=MyMart;Provider=msolap;"
My environment is:
The web server box (Server A) : Windows 2003 Server with IIS6, SQL
Server Client sp3 and Analysis Service Client sp3 are both installed.
All other asp pages not using ADOMD all work fine. Most of the web
applications on this server are ASP.NET.
The AS Server box: Windows 2000 with SQL Server 2000 SP3 (8.00.760)
The problem page works fine on other Windows 2000 server with IIS 5.
And the strange thing is: from Server A, the MDX Sample Application
works fine.
Any help is greatly appreciated
Hello Tommy,
I noticed that the issue was posted in several groups
(microsoft.public.sqlserver.olap, microsoft.public.sqlserver,
microsoft.public.sqlserver.datawarehouse
).X I have added a reply to you at
http://msdn.microsoft.com/newsgroups...public.sqlser
ver.olap&lang=en&cr=US
If you have follow up questions, please post there and I will work with
you. Thanks.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Cannot connect to localhost

If I try to connect to localhost in the connection manager I get the error

"Test connection failed because of an error in initialising provider. Login timeout expired."

If I try to connect using server/instance in the connection mananger however, it connects just fine.

Any ideas?

Gary

hi Gary,

if you installed a named instance as it seems (server\Instance) you will not be able to just use "localhost".. you have to provide the full instance name, thus ServerName\InstanceName or "(Local)\InstanceName" or whatever... but the instancename must be provided as well..

regards

Cannot connect SQL 2005 with OLE DB Provider for SQL Server

Cannot connect SQL 2005 with OLE DB Provider for SQL Server

MSSQL 2000 Utilities & MSDE was uninstalled.
After installation SQL 2005 Standard Full all connections was OK (tested).
Aftert restarting the computer I cannot connect to MSSQL with OLE DB Provider for SQL Server.
I try to connect from Delphi 5 SP2 (ADOConnection) and from MS Access 2003 SP2.

Error "SQL Server denied or does not exists or access denied"

Versions:
Windows Xp Pro SP 2
ADO/MDAC: 2.81.1117.0 (xpsp_sp2_rtm.040803-2158)
Microsoft SQL Server Management Studio 9.00.1399.00
Microsoft Analysis Services Client Tools 2005.090.1399.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 6.0.2900.2180
Microsoft .NET Framework 2.0.50727.42
Operating System 5.1.2600

Connection sting:
Provider=SQLOLEDB.1;Persist Security Info=False;User ID=sa;Password=pwd;Data Source=GMSAlexHome;Initial Catalog=GMSSample;Application Name="GMS Office Tools Service Pack"

Question: how to connect to SQL 2005 with SQL DB Provider.
All old applications does not work.

On local machine when ServerName = 'localhost' or '.' - all OK.
When using SQL server name - error.
Before rebooting all was OK.

Thanks in advance.

If you try to connect from the local PC and it works fine, but does not work from the network then most likely SQL Server is not enabled to accept external network requests. Also if your server name contains instance name, then it also suppose to be specified in your connection string, like servername\instancename|||

On local computer connection avaible only as <localhost> and <.>.

There is no instance name and other sql servers.

SQLSRV Works more than 3 times slower than MSDE 2000 on small test DB (about 100 mb).

VERY many bugs in tools and very slow.... $(((

What comps in MS? I have P4 3MHz 1 Gb SATA - VERY slow.

Sory for digression.

|||

Do you compare performance based on exact same data and structure? If your indexes are not the same as in MSDE 2000 then you cannot compare performance.

About bugs. If you have any, you could report them here. If you do this and they really exist, I believe, it will help to improve product

|||

As Val mentioned, please double check using "SQL Server Configuration Manager" tool that your SQL instance has remote TCP and/or Named Pipe support enabled.

Also, please make sure that the Windows Firewall is not blocking the ports used by SQL Server. You can explicitly add TCP port 1433 to the exception list or you can add Sqlservr.exe program to the exception list (to ensure both TCP and Named Pipes are not blocked).

Jimmy Wu