CONNECT TO SERVER PROBLEM

I am getting this message when trying to connect to SQL SERVER 2005;
An error has occurred while establishing connection to the server.When connecting to SQL Server 2005, this failure may be caused by the fact that under default settings SQL Server does not allow remote connections(provider:shared memory provider , error 40-could not open a connection to SQL Server)(MicrosoftSQL SERVER, Error: 2)
Can anyone help to fix this problem please

Are you using SQL Express? If so, you need to enable remote connections. They are disabled by default.

Thanks,
Sam Lester (MSFT)

|||SQL SERVER 2005, STANDART
|||

On the server execute these statements:

sp_configure 'remote admin connections', 1

go

reconfigure

go

Then you should be able to connect from a client workstation.

Connect to remote RS in SSMS

Got following error when try to connect to remote reporting service in SSMS:

TITLE: Microsoft SQL Server Management Studio

The request failed with HTTP status 401: Unauthorized. (Microsoft.SqlServer.Management.UI.RSClient)

BUTTONS:

OK

No problem to connect to reporting service in SSMS on RS box locally. Use windows authentication with same account in both case. How to configure that? Thanks.

Odd - You're logged in on as the same user on both computers? Are both computers in the same domain?

Can you access the report server in a web browser from the remote computer?

If you can, try this:

in the SSMS connection dialog. Replace machine\instance in the server textbox with the URL to your report server, e.g. http://yourserver/reportserver.

Does that work?

-Lukasz

This posting is provided "AS IS" with no warranties, and confers no rights.

|||Yes, I can access the report server in a web browser from same remote computer where I tried to connect RS in SSMS. Replacing server name with RS url doesn't work either, got same 401 error.|||Is the user in the Administrators group on the box?|||Yes, it's local admin on both server and client machine.|||Very strange.. Since it is a 401 error, maybe you could look in the %windir%\system32\LogFiles\W3SVC1 for the latest log file to see what request is being denied.|||

Another thing to try is to change the Authentication Type to Digest in Management Studio when logging in from the remote machine. Type in your windows credentials and see if you get the same error.

-Lukasz

This posting is provided "AS IS" with no warranties, and confers no rights.

|||

I found followings in the log file, any hint? By the way, got same error when try to connect with basic authentication. Thanks.

2005-12-30 14:15:33 172.20.193.76 GET /reportsdr - 80 - 10.16.55.81 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322) 401 2 2148074254

2005-12-30 14:15:33 172.20.193.76 GET /reportsdr - 80 - 10.16.55.81 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322) 401 1 0

2005-12-30 14:15:33 172.20.193.76 GET /reportsdr - 80 corp\rmiao 10.16.55.81 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322) 301 0 0

2005-12-30 14:15:55 172.20.193.76 GET /reportsdr/home.aspx - 80 corp\rmiao 10.16.55.81 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322) 302 0 0

|||

Looks like you're passing the Report Manager virutal directory. You need to pass the report server virtual directory.

By default these are:

Report Manager: http://localhost/reports

Report Server: http://localhost/reportserver

-Lukasz

This posting is provided "AS IS" with no warranties, and confers no rights.

|||Worked with report server url, thanks for the help.|||Glad to see it worked for you.

Can you provide the IIS logs for when you try to connect using just

server\instance in the SSMS connection dialog. I'm curious to

know why you can't connect to RS with management studio.

Thanks,

-Lukasz

This posting is provided "AS IS" with no warranties, and confers no rights.|||

Did you ever find out why you couldn't just us the servername in SSMS? I am having this same problem.

Thanks,

Bryan

|||No, fine with me to use url.

Connect to remote RS in SSMS

Got following error when try to connect to remote reporting service in SSMS:

TITLE: Microsoft SQL Server Management Studio

The request failed with HTTP status 401: Unauthorized. (Microsoft.SqlServer.Management.UI.RSClient)

BUTTONS:

OK

No problem to connect to reporting service in SSMS on RS box locally. Use windows authentication with same account in both case. How to configure that? Thanks.

Odd - You're logged in on as the same user on both computers? Are both computers in the same domain?

Can you access the report server in a web browser from the remote computer?

If you can, try this:

in the SSMS connection dialog. Replace machine\instance in the server textbox with the URL to your report server, e.g. http://yourserver/reportserver.

Does that work?

-Lukasz

This posting is provided "AS IS" with no warranties, and confers no rights.

|||Yes, I can access the report server in a web browser from same remote computer where I tried to connect RS in SSMS. Replacing server name with RS url doesn't work either, got same 401 error.|||Is the user in the Administrators group on the box?|||Yes, it's local admin on both server and client machine.|||Very strange.. Since it is a 401 error, maybe you could look in the %windir%\system32\LogFiles\W3SVC1 for the latest log file to see what request is being denied.|||

Another thing to try is to change the Authentication Type to Digest in Management Studio when logging in from the remote machine. Type in your windows credentials and see if you get the same error.

-Lukasz

This posting is provided "AS IS" with no warranties, and confers no rights.

|||

I found followings in the log file, any hint? By the way, got same error when try to connect with basic authentication. Thanks.

2005-12-30 14:15:33 172.20.193.76 GET /reportsdr - 80 - 10.16.55.81 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322) 401 2 2148074254

2005-12-30 14:15:33 172.20.193.76 GET /reportsdr - 80 - 10.16.55.81 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322) 401 1 0

2005-12-30 14:15:33 172.20.193.76 GET /reportsdr - 80 corp\rmiao 10.16.55.81 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322) 301 0 0

2005-12-30 14:15:55 172.20.193.76 GET /reportsdr/home.aspx - 80 corp\rmiao 10.16.55.81 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322) 302 0 0

|||

Looks like you're passing the Report Manager virutal directory. You need to pass the report server virtual directory.

By default these are:

Report Manager: http://localhost/reports

Report Server: http://localhost/reportserver

-Lukasz

This posting is provided "AS IS" with no warranties, and confers no rights.

|||Worked with report server url, thanks for the help.|||Glad to see it worked for you.
Can you provide the IIS logs for when you try to connect using just server\instance in the SSMS connection dialog. I'm curious to know why you can't connect to RS with management studio.
Thanks,
-Lukasz

This posting is provided "AS IS" with no warranties, and confers no rights.|||

Did you ever find out why you couldn't just us the servername in SSMS? I am having this same problem.

Thanks,

Bryan

|||No, fine with me to use url.

Connect to remote RS in SSMS

Got following error when try to connect to remote reporting service in SSMS:

TITLE: Microsoft SQL Server Management Studio

The request failed with HTTP status 401: Unauthorized. (Microsoft.SqlServer.Management.UI.RSClient)

BUTTONS:

OK

No problem to connect to reporting service in SSMS on RS box locally. Use windows authentication with same account in both case. How to configure that? Thanks.

Odd - You're logged in on as the same user on both computers? Are both computers in the same domain?

Can you access the report server in a web browser from the remote computer?

If you can, try this:

in the SSMS connection dialog. Replace machine\instance in the server textbox with the URL to your report server, e.g. http://yourserver/reportserver.

Does that work?

-Lukasz

This posting is provided "AS IS" with no warranties, and confers no rights.

|||Yes, I can access the report server in a web browser from same remote computer where I tried to connect RS in SSMS. Replacing server name with RS url doesn't work either, got same 401 error.|||Is the user in the Administrators group on the box?|||Yes, it's local admin on both server and client machine.|||Very strange.. Since it is a 401 error, maybe you could look in the %windir%\system32\LogFiles\W3SVC1 for the latest log file to see what request is being denied.|||

Another thing to try is to change the Authentication Type to Digest in Management Studio when logging in from the remote machine. Type in your windows credentials and see if you get the same error.

-Lukasz

This posting is provided "AS IS" with no warranties, and confers no rights.

|||

I found followings in the log file, any hint? By the way, got same error when try to connect with basic authentication. Thanks.

2005-12-30 14:15:33 172.20.193.76 GET /reportsdr - 80 - 10.16.55.81 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322) 401 2 2148074254

2005-12-30 14:15:33 172.20.193.76 GET /reportsdr - 80 - 10.16.55.81 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322) 401 1 0

2005-12-30 14:15:33 172.20.193.76 GET /reportsdr - 80 corp\rmiao 10.16.55.81 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322) 301 0 0

2005-12-30 14:15:55 172.20.193.76 GET /reportsdr/home.aspx - 80 corp\rmiao 10.16.55.81 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322) 302 0 0

|||

Looks like you're passing the Report Manager virutal directory. You need to pass the report server virtual directory.

By default these are:

Report Manager: http://localhost/reports

Report Server: http://localhost/reportserver

-Lukasz

This posting is provided "AS IS" with no warranties, and confers no rights.

|||Worked with report server url, thanks for the help.|||Glad to see it worked for you.
Can you provide the IIS logs for when you try to connect using just server\instance in the SSMS connection dialog. I'm curious to know why you can't connect to RS with management studio.
Thanks,
-Lukasz

This posting is provided "AS IS" with no warranties, and confers no rights.|||

Did you ever find out why you couldn't just us the servername in SSMS? I am having this same problem.

Thanks,

Bryan

|||No, fine with me to use url.

Connect to remote RS in SSMS

Got following error when try to connect to remote reporting service in SSMS:

TITLE: Microsoft SQL Server Management Studio

The request failed with HTTP status 401: Unauthorized. (Microsoft.SqlServer.Management.UI.RSClient)

BUTTONS:

OK

No problem to connect to reporting service in SSMS on RS box locally. Use windows authentication with same account in both case. How to configure that? Thanks.

Odd - You're logged in on as the same user on both computers? Are both computers in the same domain?

Can you access the report server in a web browser from the remote computer?

If you can, try this:

in the SSMS connection dialog. Replace machine\instance in the server textbox with the URL to your report server, e.g. http://yourserver/reportserver.

Does that work?

-Lukasz

This posting is provided "AS IS" with no warranties, and confers no rights.

|||Yes, I can access the report server in a web browser from same remote computer where I tried to connect RS in SSMS. Replacing server name with RS url doesn't work either, got same 401 error.|||Is the user in the Administrators group on the box?|||Yes, it's local admin on both server and client machine.|||Very strange.. Since it is a 401 error, maybe you could look in the %windir%\system32\LogFiles\W3SVC1 for the latest log file to see what request is being denied.|||

Another thing to try is to change the Authentication Type to Digest in Management Studio when logging in from the remote machine. Type in your windows credentials and see if you get the same error.

-Lukasz

This posting is provided "AS IS" with no warranties, and confers no rights.

|||

I found followings in the log file, any hint? By the way, got same error when try to connect with basic authentication. Thanks.

2005-12-30 14:15:33 172.20.193.76 GET /reportsdr - 80 - 10.16.55.81 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322) 401 2 2148074254

2005-12-30 14:15:33 172.20.193.76 GET /reportsdr - 80 - 10.16.55.81 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322) 401 1 0

2005-12-30 14:15:33 172.20.193.76 GET /reportsdr - 80 corp\rmiao 10.16.55.81 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322) 301 0 0

2005-12-30 14:15:55 172.20.193.76 GET /reportsdr/home.aspx - 80 corp\rmiao 10.16.55.81 Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322) 302 0 0

|||

Looks like you're passing the Report Manager virutal directory. You need to pass the report server virtual directory.

By default these are:

Report Manager: http://localhost/reports

Report Server: http://localhost/reportserver

-Lukasz

This posting is provided "AS IS" with no warranties, and confers no rights.

|||Worked with report server url, thanks for the help.|||Glad to see it worked for you.
Can you provide the IIS logs for when you try to connect using just server\instance in the SSMS connection dialog. I'm curious to know why you can't connect to RS with management studio.
Thanks,
-Lukasz

This posting is provided "AS IS" with no warranties, and confers no rights.|||

Did you ever find out why you couldn't just us the servername in SSMS? I am having this same problem.

Thanks,

Bryan

|||No, fine with me to use url.sqlsql

Connect To Oracle 10g 64 Bit using SQL Server Integration Services 2005 64 Bit

I am trying to create a oracle 10g connection in SSIS using connection manager and i am getting the following error,

Test Connection failed because of an error in initializing provider. Oracle client and networking

components were not found. These components are supplied by Oracle corporation and are part of the

Oracle version 7.3.3 or later client software installation.

Provider is unable to function until these components are installed.

Can someone please help.

Thanks.

If your operating System and VS2005 are 32bits then you need to download and install the Oracle 10g client for Windows 32bits, when I last downloaded it was more than 1gig install it and create your connection to the database make sure your TNS ORA works before adding SSIS connection to Oracle. The client tools are free but you need an Oracle Technet account which you can create for free. The Developer is also free it let you see Oracle tables and databases. If you are in an employer's network I find connecting with Named Pipes is easier than TCP/IP. One more thing watch the installer. Hope this helps.

http://www.oracle.com/technology/software/index.html

I forgot to add you must compile your code with AnyCPU.

|||

Thanks for your reply Caddre..

But.. i have MS 2003 64 bit OS.. i have installed oracle 10g 64 bit server.. i can successfully connect thru sqlplus.. no problem...

I am missing something on SQL 2005 and i am not sure what it is...

|||

So you are saying you have installed Oracle 10g 64bits client tools in the box? I know connecting through SQL plus does not solve development connection issue you need the client tools in your box this time 64bits. Another thing you are not missing anything but I think VS2005 unless you buy 64bits full version is 32bits that is not all your setup is 64bits, so you need to either make it all 64bits or develop in 32bits and deploy in 64bits because I read there are issues known issues.

|||

yes - as far as i know all are 64bit

I cannot connect thru both providers - OLEDB and Net Oracle client

|||

Try this recent Microsoft support article steps, I will still look for more info.

http://support.microsoft.com/kb/255084

|||

Hi Caddre,

Either you can have a look at summarized article here. or You may look for "Getting SSIS Packages To Run On A 64 Bit Box" in Sutha Thiru's Blog .

Thanks

Subhash Subramanyam

|||

thanks subash.. awesome..

those articles helped me to fix the issue...

appreciate yours and caddre help on this..

|||I am glad to see your problem is resolved and Subhash thanks for the articles much appreciated.

Connect to Network SQL2k5 Database - ERROR

Hi,
eh! Finally I installed SQL 2005 yesterday. I have SQL 2000 also installed
on the same machine. When I started Microsoft SQL Server Management Studio
and tried to connect to another database running SQL 2005 using Windows
Authentication, I got following error.
TITLE: Microsoft SQL Server Management Studio
--
Unable to cast COM object of type 'System.__ComObject' to interface type
'Microsoft.VisualStudio.OLE.Interop.IServiceProvider'. This operation failed
because the QueryInterface call on the COM component for the interface with
IID '{6D5140C1-7436-11CE-8034-00AA006009FA}' failed due to the following
error: No such interface supported (Exception from HRESULT: 0x80004002
(E_NOINTERFACE)). (Microsoft.VisualStudio.OLE.Interop)
--
Although, this error does not affect connection to the database. It connects
successfully and I am able to perform other stuff too. Just curious, why
this error is coming.
Any ideas why am I getting this kind of error.
Regards,
AtulLooks like you have problem with Visual Studio. Try to connect your database
from visual studio. Might be your installation file is corrupt or improper
installation.
--
Thanks,
Sree
[Please specify the version of Sql Server as we can save one thread and time
asking back if its 2000 or 2005]
"Atul" wrote:
> Hi,
> eh! Finally I installed SQL 2005 yesterday. I have SQL 2000 also installed
> on the same machine. When I started Microsoft SQL Server Management Studio
> and tried to connect to another database running SQL 2005 using Windows
> Authentication, I got following error.
> TITLE: Microsoft SQL Server Management Studio
> --
> Unable to cast COM object of type 'System.__ComObject' to interface type
> 'Microsoft.VisualStudio.OLE.Interop.IServiceProvider'. This operation failed
> because the QueryInterface call on the COM component for the interface with
> IID '{6D5140C1-7436-11CE-8034-00AA006009FA}' failed due to the following
> error: No such interface supported (Exception from HRESULT: 0x80004002
> (E_NOINTERFACE)). (Microsoft.VisualStudio.OLE.Interop)
> --
> Although, this error does not affect connection to the database. It connects
> successfully and I am able to perform other stuff too. Just curious, why
> this error is coming.
> Any ideas why am I getting this kind of error.
> Regards,
> Atul
>
>|||While installing SQL 2005, I did not give DataBase Instance name. Now when I
try to connect to local SQL 2005 database (I dont know where the MDF files
have been created for the same), it fails to connect, instead it connects to
SQL 2000 Database server.
This is another problem I am facing.
"Sreejith G" <SreejithG@.discussions.microsoft.com> wrote in message
news:4F2D2233-BDDE-47FB-BB1C-7ED76E1D3359@.microsoft.com...
> Looks like you have problem with Visual Studio. Try to connect your
> database
> from visual studio. Might be your installation file is corrupt or improper
> installation.
> --
> Thanks,
> Sree
> [Please specify the version of Sql Server as we can save one thread and
> time
> asking back if its 2000 or 2005]
>
> "Atul" wrote:
>> Hi,
>> eh! Finally I installed SQL 2005 yesterday. I have SQL 2000 also
>> installed
>> on the same machine. When I started Microsoft SQL Server Management
>> Studio
>> and tried to connect to another database running SQL 2005 using Windows
>> Authentication, I got following error.
>> TITLE: Microsoft SQL Server Management Studio
>> --
>> Unable to cast COM object of type 'System.__ComObject' to interface type
>> 'Microsoft.VisualStudio.OLE.Interop.IServiceProvider'. This operation
>> failed
>> because the QueryInterface call on the COM component for the interface
>> with
>> IID '{6D5140C1-7436-11CE-8034-00AA006009FA}' failed due to the following
>> error: No such interface supported (Exception from HRESULT: 0x80004002
>> (E_NOINTERFACE)). (Microsoft.VisualStudio.OLE.Interop)
>> --
>> Although, this error does not affect connection to the database. It
>> connects
>> successfully and I am able to perform other stuff too. Just curious, why
>> this error is coming.
>> Any ideas why am I getting this kind of error.
>> Regards,
>> Atul
>>

Connect to Network SQL2k5 Database - ERROR

Hi,
eh! Finally I installed SQL 2005 yesterday. I have SQL 2000 also installed
on the same machine. When I started Microsoft SQL Server Management Studio
and tried to connect to another database running SQL 2005 using Windows
Authentication, I got following error.
TITLE: Microsoft SQL Server Management Studio
Unable to cast COM object of type 'System.__ComObject' to interface type
'Microsoft.VisualStudio.OLE.Interop.IServiceProvid er'. This operation failed
because the QueryInterface call on the COM component for the interface with
IID '{6D5140C1-7436-11CE-8034-00AA006009FA}' failed due to the following
error: No such interface supported (Exception from HRESULT: 0x80004002
(E_NOINTERFACE)). (Microsoft.VisualStudio.OLE.Interop)
Although, this error does not affect connection to the database. It connects
successfully and I am able to perform other stuff too. Just curious, why
this error is coming.
Any ideas why am I getting this kind of error.
Regards,
Atul
Looks like you have problem with Visual Studio. Try to connect your database
from visual studio. Might be your installation file is corrupt or improper
installation.
Thanks,
Sree
[Please specify the version of Sql Server as we can save one thread and time
asking back if its 2000 or 2005]
"Atul" wrote:

> Hi,
> eh! Finally I installed SQL 2005 yesterday. I have SQL 2000 also installed
> on the same machine. When I started Microsoft SQL Server Management Studio
> and tried to connect to another database running SQL 2005 using Windows
> Authentication, I got following error.
> TITLE: Microsoft SQL Server Management Studio
> --
> Unable to cast COM object of type 'System.__ComObject' to interface type
> 'Microsoft.VisualStudio.OLE.Interop.IServiceProvid er'. This operation failed
> because the QueryInterface call on the COM component for the interface with
> IID '{6D5140C1-7436-11CE-8034-00AA006009FA}' failed due to the following
> error: No such interface supported (Exception from HRESULT: 0x80004002
> (E_NOINTERFACE)). (Microsoft.VisualStudio.OLE.Interop)
> --
> Although, this error does not affect connection to the database. It connects
> successfully and I am able to perform other stuff too. Just curious, why
> this error is coming.
> Any ideas why am I getting this kind of error.
> Regards,
> Atul
>
>
|||While installing SQL 2005, I did not give DataBase Instance name. Now when I
try to connect to local SQL 2005 database (I dont know where the MDF files
have been created for the same), it fails to connect, instead it connects to
SQL 2000 Database server.
This is another problem I am facing.
"Sreejith G" <SreejithG@.discussions.microsoft.com> wrote in message
news:4F2D2233-BDDE-47FB-BB1C-7ED76E1D3359@.microsoft.com...[vbcol=seagreen]
> Looks like you have problem with Visual Studio. Try to connect your
> database
> from visual studio. Might be your installation file is corrupt or improper
> installation.
> --
> Thanks,
> Sree
> [Please specify the version of Sql Server as we can save one thread and
> time
> asking back if its 2000 or 2005]
>
> "Atul" wrote:

Connect to Network SQL2k5 Database - ERROR

Hi,
eh! Finally I installed SQL 2005 yesterday. I have SQL 2000 also installed
on the same machine. When I started Microsoft SQL Server Management Studio
and tried to connect to another database running SQL 2005 using Windows
Authentication, I got following error.
TITLE: Microsoft SQL Server Management Studio
--
Unable to cast COM object of type 'System.__ComObject' to interface type
'Microsoft.VisualStudio.OLE.Interop.IServiceProvider'. This operation failed
because the QueryInterface call on the COM component for the interface with
IID '{6D5140C1-7436-11CE-8034-00AA006009FA}' failed due to the followin
g
error: No such interface supported (Exception from HRESULT: 0x80004002
(E_NOINTERFACE)). (Microsoft.VisualStudio.OLE.Interop)
Although, this error does not affect connection to the database. It connects
successfully and I am able to perform other stuff too. Just curious, why
this error is coming.
Any ideas why am I getting this kind of error.
Regards,
AtulLooks like you have problem with Visual Studio. Try to connect your database
from visual studio. Might be your installation file is corrupt or improper
installation.
--
Thanks,
Sree
[Please specify the version of Sql Server as we can save one thread and
time
asking back if its 2000 or 2005]
"Atul" wrote:

> Hi,
> eh! Finally I installed SQL 2005 yesterday. I have SQL 2000 also installed
> on the same machine. When I started Microsoft SQL Server Management Studio
> and tried to connect to another database running SQL 2005 using Windows
> Authentication, I got following error.
> TITLE: Microsoft SQL Server Management Studio
> --
> Unable to cast COM object of type 'System.__ComObject' to interface type
> 'Microsoft.VisualStudio.OLE.Interop.IServiceProvider'. This operation fail
ed
> because the QueryInterface call on the COM component for the interface wit
h
> IID '{6D5140C1-7436-11CE-8034-00AA006009FA}' failed due to the follow
ing
> error: No such interface supported (Exception from HRESULT: 0x80004002
> (E_NOINTERFACE)). (Microsoft.VisualStudio.OLE.Interop)
> --
> Although, this error does not affect connection to the database. It connec
ts
> successfully and I am able to perform other stuff too. Just curious, why
> this error is coming.
> Any ideas why am I getting this kind of error.
> Regards,
> Atul
>
>|||While installing SQL 2005, I did not give DataBase Instance name. Now when I
try to connect to local SQL 2005 database (I dont know where the MDF files
have been created for the same), it fails to connect, instead it connects to
SQL 2000 Database server.
This is another problem I am facing.
"Sreejith G" <SreejithG@.discussions.microsoft.com> wrote in message
news:4F2D2233-BDDE-47FB-BB1C-7ED76E1D3359@.microsoft.com...[vbcol=seagreen]
> Looks like you have problem with Visual Studio. Try to connect your
> database
> from visual studio. Might be your installation file is corrupt or improper
> installation.
> --
> Thanks,
> Sree
> [Please specify the version of Sql Server as we can save one thread an
d
> time
> asking back if its 2000 or 2005]
>
> "Atul" wrote:
>

Connect to Database in SQL 2005 Express

I am trying to connect to the sample databases in SQL Express. I am getting this error.

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: Name Pipes Provider, error: 40 - could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

I have downloaded and installed AdventureWorks, Northwind, and Pubs. If I have to allow remote connections how do I do that? I am a studen and I am brand new at this.

first ensure the sample database you wish to use is registered (some of the samples must first be attached from the D/L .mdf files).

second startup the SURFACE AREA CONFIG TOOL via the start menu. after the splash screen display click on the configure services and connections link.

select the Remote Connection node in the tree and select the second radio button to enable remote connections.

if you still have problems you should look at the protocols your sql server has enabled and which protocol format you are using to connect.

|||

1. Open SQL Server Configuration Manager under "Microsoft SQL Sever 2005" "Configuration Tools"

2. Navigate to "Sql Server 2005 Network Configuration" --"Protocols for SQL2005"

3. Enable "Shared Memory" , "Named Pipes" & "TCP/IP"

This should solve the problem

|||I figured it out. I feel stupid now. I just had to right click on database and click attach. Then click add. This brought me out to the windows hierarchy where I was able to find the Northwind database and click on it to add it.|||

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: Name Pipes Provider, error: 40 - could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

Connect to Database in SQL 2005 Express

I am trying to connect to the sample databases in SQL Express. I am getting this error.

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: Name Pipes Provider, error: 40 - could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

I have downloaded and installed AdventureWorks, Northwind, and Pubs. If I have to allow remote connections how do I do that? I am a studen and I am brand new at this.

first ensure the sample database you wish to use is registered (some of the samples must first be attached from the D/L .mdf files).

second startup the SURFACE AREA CONFIG TOOL via the start menu. after the splash screen display click on the configure services and connections link.

select the Remote Connection node in the tree and select the second radio button to enable remote connections.

if you still have problems you should look at the protocols your sql server has enabled and which protocol format you are using to connect.

|||

1. Open SQL Server Configuration Manager under "Microsoft SQL Sever 2005" "Configuration Tools"

2. Navigate to "Sql Server 2005 Network Configuration" --"Protocols for SQL2005"

3. Enable "Shared Memory" , "Named Pipes" & "TCP/IP"

This should solve the problem

|||I figured it out. I feel stupid now. I just had to right click on database and click attach. Then click add. This brought me out to the windows hierarchy where I was able to find the Northwind database and click on it to add it.|||

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: Name Pipes Provider, error: 40 - could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

connect to AS2000 cube error

Here is my setup: I have Reporting Service and SQL Server 2000 in one box
(Box A), and IIS and Analysis Service in another box (Box B), which has
couple of cubes based on the database in Box A, using SQL Authentication and
Allow save password. Create AS2000 data source at Reporting Project, then
create a report, I can preview the report fine in VS.2003. But I got the
following error after deploying the report to the reportserver and browse the
report:

Cannot create a connection to data source 'Cube'. (rsErrorOpeningConnection)
Get Online Help
Database 'Cube' does not exist.
Do I miss anything?

Thanks

Reporting services and Analysis Services only support Windows authentication.

Another problem with your setup is that even if you use windows authentication you cannot validate users between to servers without using Kerberos and account delegation.

Its possible to use standalone servers and maintain the same windows accounts on the separate machines manually.

Regards

Thomas Ivarsson

sqlsql

Connect to a server from client

I'm receiving ths following error message when I try to connect to my server:
Cannot generate SSPI context. (.Net SqlClient Data Provider)
An idea?
Check this article:
http://blogs.msdn.com/sql_protocols/archive/2005/10/19/482782.aspx
Ayad Shammout
"Joseph" <Joseph@.discussions.microsoft.com> wrote in message
news:C22E4CA3-2289-47B0-B009-C7D63E590B78@.microsoft.com...
> I'm receiving ths following error message when I try to connect to my
> server:
> Cannot generate SSPI context. (.Net SqlClient Data Provider)
> An idea?

connect timeout , is it works ?..

hye
i set in the connection string "connect timeout=400" and the application send error after 30sec ... why ?

*in the sql server properties , the connection time set to 0 .
*i know the run time of the query is very long , but in this case its doesn't matter :)

You are setting the timeout for the connection, that is, how long does it try to connect before timeout. If you are using a Command object, there is a CommandTimeout property that you can set to allow the command to actually run longer before timeout.

Connect SQL server 2005 with ODBC drive “SQL Native Client"

Hi,

When I'm using SQL server 2005, and ODBC drive “SQL Native Client” I get an error when executing the below given code. Error Message: “Transaction cannot start because more than one ODBC connection is in use.”

But this works well with SQL Server 2000 with ODBC drive "SQL Native Client" and in SQL server 2005 also when I used ODBC drive “SQL Server”.

I used aTrgConn.Execute(“Begin Transaction”) and it's working properly. But unfortunately I cannot use this method, because I want to run the same code with Oracle ODBC as well.

Is this a known issue in SQL Native client drive with SQL server 2005? Do you know a solution for this?

Please Help..............

Thanks in advance.

Code:

Dim aTrgConn As New ADODB.connection
Dim aCmdIns As New ADODB.Command
Dim aCmdUpd As New ADODB.Command

aTrgConn.Open sConnStr

Set aCmdIns.ActiveConnection = aTrgConn
Set aCmdUpd.ActiveConnection = aTrgConn

aTrgConn.BeginTrans

Why are you using two separate commands here? Couldn't you just use one command and reset the values to execute?|||

Hi John,

You are correct. but I'm afraid, it's very difficult to change the design at this stage. and it worked perfectly with SQL Server 2000.

Thank you very much for your response.

|||

Hi Again,

I think the problem comes when using the provider as MSDASQL.1 , with SQL server 2005 Native Client.

When I add "Provider=SQLNCLI;Integrated Security=SSPI;DataTypeCompatibility=80;MARS Connection=True;" to my connection string, it works correctly.

But again, I need the same coding to access oracle too. so SQLNCLI won't work with that.

It's really appriciated, If anyone could find a solution to this.

Thanks

|||

Hi,

I have the same problem with my application.

I began to use SQL Express 2005 with Native Client ODBC rather than MSDE and found the same error.

My application must works with several databases.

If anyone find a solution for this problem tell me too.

Thanks advanced,

Wendel

|||

Do you see the same problem with SQLNCLI OLEDB provider and not using MARS?

Thanks

Waseem

Connect SQL server 2005 with ODBC drive “SQL Native Client"

Hi,

When I'm using SQL server 2005, and ODBC drive “SQL Native Client” I get an error when executing the below given code. Error Message: “Transaction cannot start because more than one ODBC connection is in use.”

But this works well with SQL Server 2000 with ODBC drive "SQL Native Client" and in SQL server 2005 also when I used ODBC drive “SQL Server”.

I used aTrgConn.Execute(“Begin Transaction”) and it's working properly. But unfortunately I cannot use this method, because I want to run the same code with Oracle ODBC as well.

Is this a known issue in SQL Native client drive with SQL server 2005? Do you know a solution for this?

Please Help..............

Thanks in advance.

Code:

Dim aTrgConn As New ADODB.connection
Dim aCmdIns As New ADODB.Command
Dim aCmdUpd As New ADODB.Command

aTrgConn.Open sConnStr

Set aCmdIns.ActiveConnection = aTrgConn
Set aCmdUpd.ActiveConnection = aTrgConn

aTrgConn.BeginTrans

Why are you using two separate commands here? Couldn't you just use one command and reset the values to execute?|||

Hi John,

You are correct. but I'm afraid, it's very difficult to change the design at this stage. and it worked perfectly with SQL Server 2000.

Thank you very much for your response.

|||

Hi Again,

I think the problem comes when using the provider as MSDASQL.1 , with SQL server 2005 Native Client.

When I add "Provider=SQLNCLI;Integrated Security=SSPI;DataTypeCompatibility=80;MARS Connection=True;" to my connection string, it works correctly.

But again, I need the same coding to access oracle too. so SQLNCLI won't work with that.

It's really appriciated, If anyone could find a solution to this.

Thanks

|||

Hi,

I have the same problem with my application.

I began to use SQL Express 2005 with Native Client ODBC rather than MSDE and found the same error.

My application must works with several databases.

If anyone find a solution for this problem tell me too.

Thanks advanced,

Wendel

|||

Do you see the same problem with SQLNCLI OLEDB provider and not using MARS?

Thanks

Waseem

Connect SQL server 2005 with ODBC drive “SQL Native Client"

Hi,

When I'm using SQL server 2005, and ODBC drive “SQL Native Client” I get an error when executing the below given code. Error Message: “Transaction cannot start because more than one ODBC connection is in use.”

But this works well with SQL Server 2000 with ODBC drive "SQL Native Client" and in SQL server 2005 also when I used ODBC drive “SQL Server”.

I used aTrgConn.Execute(“Begin Transaction”) and it's working properly. But unfortunately I cannot use this method, because I want to run the same code with Oracle ODBC as well.

Is this a known issue in SQL Native client drive with SQL server 2005? Do you know a solution for this?

Please Help..............

Thanks in advance.

Code:

Dim aTrgConn As New ADODB.connection
Dim aCmdIns As New ADODB.Command
Dim aCmdUpd As New ADODB.Command

aTrgConn.Open sConnStr

Set aCmdIns.ActiveConnection = aTrgConn
Set aCmdUpd.ActiveConnection = aTrgConn

aTrgConn.BeginTrans

Why are you using two separate commands here? Couldn't you just use one command and reset the values to execute?|||

Hi John,

You are correct. but I'm afraid, it's very difficult to change the design at this stage. and it worked perfectly with SQL Server 2000.

Thank you very much for your response.

|||

Hi Again,

I think the problem comes when using the provider as MSDASQL.1 , with SQL server 2005 Native Client.

When I add "Provider=SQLNCLI;Integrated Security=SSPI;DataTypeCompatibility=80;MARS Connection=True;" to my connection string, it works correctly.

But again, I need the same coding to access oracle too. so SQLNCLI won't work with that.

It's really appriciated, If anyone could find a solution to this.

Thanks

|||

Hi,

I have the same problem with my application.

I began to use SQL Express 2005 with Native Client ODBC rather than MSDE and found the same error.

My application must works with several databases.

If anyone find a solution for this problem tell me too.

Thanks advanced,

Wendel

|||

Do you see the same problem with SQLNCLI OLEDB provider and not using MARS?

Thanks

Waseem

Connect fails: Error 4064, Can not open user default DB

I just installed SQL Server 2005 CTP (9.00.1116) on Windows Server 2003 with SP1. Then I unzipped DotNetNuke portal site and tried to connect to it with various errors, generally relating to invalid login.

I never figured it out after many hours of exploring every SQL interface I could find, changing web.config's connection string, and editing the DotNetNuke ODBC Data Source. At one point I was able to intermittently sign in to the SQL Server Management Studio (but never to get DotNetNuke site to connect to the DB).

Late in this process I gave up, decided to reinstall DotNetNuke from scratch, and removed that directory with my default database. Maybe one isn't supposed to do this, but I did it and suspect that is the reason for the error message in the title of this post. I don't see a way to login in as another user either at this point.

If it is indeed possible for one to delete one's default database - and if so - is there any solution except a complete (multi-hour on my old system) reinstall of SQL Server?

If I try to connect using SQL user SA (user names are case insensative, right?!), I get error 18452: "The user is not associated with a trusted SQL Server Connection."

You can change default database for a user using ALTER LOGIN. You can check your current settings for all users using sys.server_principals.

As far as being unable to connect using ‘sa’ credentials, verify that you have mixed mode authentication enabled. If you do not that might explain why you are getting trusted connection error for ‘sa’.

This may also be affecting your inability to connect to the portal.

Overall, it is recommended that you upgrade to CTP 15 (build 1187), so reinstall might be the cleanest option. Make sure you select ‘mixed mode auth’ and set ‘sa’ password during setup.

Regards,

Boris.

|||Boris B is right , I had the same problem when i started using it and it turned out to be the default database i hat for the specific login .

Connect fails: Error 4064, Can not open user default DB

I just installed SQL Server 2005 CTP (9.00.1116) on Windows Server 2003 with SP1. Then I unzipped DotNetNuke portal site and tried to connect to it with various errors, generally relating to invalid login.

I never figured it out after many hours of exploring every SQL interface I could find, changing web.config's connection string, and editing the DotNetNuke ODBC Data Source. At one point I was able to intermittently sign in to the SQL Server Management Studio (but never to get DotNetNuke site to connect to the DB).

Late in this process I gave up, decided to reinstall DotNetNuke from scratch, and removed that directory with my default database. Maybe one isn't supposed to do this, but I did it and suspect that is the reason for the error message in the title of this post. I don't see a way to login in as another user either at this point.

If it is indeed possible for one to delete one's default database - and if so - is there any solution except a complete (multi-hour on my old system) reinstall of SQL Server?

If I try to connect using SQL user SA (user names are case insensative, right?!), I get error 18452: "The user is not associated with a trusted SQL Server Connection."

You can change default database for a user using ALTER LOGIN. You can check your current settings for all users using sys.server_principals.

As far as being unable to connect using ‘sa’ credentials, verify that you have mixed mode authentication enabled. If you do not that might explain why you are getting trusted connection error for ‘sa’.

This may also be affecting your inability to connect to the portal.

Overall, it is recommended that you upgrade to CTP 15 (build 1187), so reinstall might be the cleanest option. Make sure you select ‘mixed mode auth’ and set ‘sa’ password during setup.

Regards,

Boris.

|||Boris B is right , I had the same problem when i started using it and it turned out to be the default database i hat for the specific login .

connect error with Windows Security

My Windows2000\SQL2000 server uses Windows Only security from a NT 4 domain.
My Win2000 client logs in to AD, not the NT4 domain. I am getting sql conne
ct errors 123 and 53 when I try to create a DSN and add my NT4 domain creden
tials. Does anyone know how
to create a DSN using credentials other than the one I am logged in as?
Thanks.Could you post the exact error messages you get?
If you are creating a DSN to use Windows authentication, you
don't specify a user name and password. You just select NT
authentication for the login info. The login must exist on
the server and if you selected a database for the DSN, the
user must exist in the database.
-Sue
On Mon, 24 May 2004 13:36:07 -0700, "Jon S"
<anonymous@.discussions.microsoft.com> wrote:

>My Windows2000\SQL2000 server uses Windows Only security from a NT 4 domain. My Win
2000 client logs in to AD, not the NT4 domain. I am getting sql connect errors 123 a
nd 53 when I try to create a DSN and add my NT4 domain credentials. Does anyone know
ho
w to create a DSN using credentials other than the one I am logged in as?
>Thanks.|||I am trying to create a user DSN and specify server name on the first screen
. On the security screen, it defaults to my AD login credentials, so I click
sql security, enter my NT4 domain credentials, then click Windows security.
The error I get is " SQLSt
ate 2800, error 18452, Login failed for user'(null)'.Reason:Not associated w
ith a trusted SQL Server connection"|||The error means you are attempting to login to SQL Server
using windows authentication and the login was not able to
be validated. On the SQL Server end, make sure that the
login exists on the server.If the login exists, try dropping
and recreating and see if that makes a difference for that
login. But if the login is fine then it's likely a Windows
authentication issue. You can check the event logs for
network related issues, problems contacting a domain
controller, that type of thing. You can also try to force
the client to connect through named pipes by creating a
named pipe alias using the Client Network Utility.
-Sue
On Tue, 25 May 2004 07:06:03 -0700, "Jon S"
<anonymous@.discussions.microsoft.com> wrote:

>I am trying to create a user DSN and specify server name on the first screen. On th
e security screen, it defaults to my AD login credentials, so I click sql security,
enter my NT4 domain credentials, then click Windows security. The error I get is " S
QLS
tate 2800, error 18452, Login failed for user'(null)'.Reason:Not associated with a trusted S
QL Server connection"
>
>