Connect to SQL Server: message

Showing posts with label message. Show all posts

Sunday, March 25, 2012

connecting to SQL DATABASE ENGINE

hello everybody!!!

I am very new to SQL SERVER 2005 EXPRESS EDITION

while connecting to DATABASE ENGINE i got this error message.....

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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (.Net SqlClient Data Provider)

any solution please?

Hi,

If you are trying on a local machine.

server instance: computer_name\SQLSERVER_INSTANCE_NAME

user name : computer_name\user_name

If trying on a remote machine:

have a look in the following link:

http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

Hope it'll help.

|||

this error is very common... You check whether the instance is configured for Remote connection

Start --Microsoft sql server 2005-- Configuration Tools -- SQL Server Surface Area Configuration -- Surface Area configuration for services and connections -- Select Remote Connection -- Select Local and remote connection Radio button and using both TCP/IP and named pipes

ALso check whether the firewall is enabled. if yes create exception for 1433 and 1434

Madhu

sql sql

Thursday, March 22, 2012

Connecting to SQL 2005 from a client pc

I am getting this message. On the actual server I can pull up the report builder, but from a client on the network when trying to connect to the sql report builder I get this message:

PLATFORM VERSION INFO
Windows : 5.1.2600.131072 (Win32NT)
Common Language Runtime : 2.0.50727.42
System.Deployment.dll : 2.0.50727.42 (RTM.050727-4200)
mscorwks.dll : 2.0.50727.42 (RTM.050727-4200)
dfdll.dll : 2.0.50727.42 (RTM.050727-4200)
dfshim.dll : 2.0.50727.42 (RTM.050727-4200)

SOURCES
Deployment url : http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application

ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application resulted in exception. Following failure messages were detected:
+ Downloading http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application did not succeed.
+ The remote server returned an error: (401) Unauthorized.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [3/16/2006 10:10:28 AM] : Activation of http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application has started.

ERROR DETAILS
Following errors were detected during this operation.
* [3/16/2006 10:10:28 AM] System.Deployment.Application.DeploymentDownloadException (Unknown subtype)
- Downloading http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application did not succeed.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
at System.Deployment.Application.SystemNetDownloader.DownloadAllFiles()
at System.Deployment.Application.FileDownloader.Download(SubscriptionState subState)
at System.Deployment.Application.DownloadManager.DownloadManifestAsRawFile(Uri& sourceUri, String targetPath, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirectBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
Inner Exception
System.Net.WebException
- The remote server returned an error: (401) Unauthorized.
- Source: System
- Stack trace:
at System.Net.HttpWebRequest.GetResponse()
at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

Remote connections is enabled and I am connecting as the servers admin. Any suggestions. I think it might be a user thing, but I am not sure. Do I need to add a user to the report builder folder in iss or what.

Thank you for any suggestions

Have you had any luck with your issue? I am having a similar issue and have posted about it, but so far, no response.

ANY info you might have would be appreciated, thanks!

|||

I'm having the same problem, seams like reportbuilder can't connect to host when you try to use it in an EXTRANET, because if you try it in an INTRANET works perfectly.

I hope someone could help us on this matter. (ASAP)

|||

Couple of things about Report Builder -

1) Report Builder requires the .net framework 2.0 to be installed on the client machine. I think that's the problem you're encountering related to to the .application file.

2) Report Builder requires a direct connection back to the report server in order to work. That means that you have to expose your report server on the extranet. This has security implications for your deployement - when report server is available on the extranet, so are all the other reports that are on that report server. Also, the report server SOAP API is available on the internet - so application authors can try to have programmatic access to your report server.

When pursuing this type of deployment you should evaluate your security story for your corporate data. Often what is sufficient is to provide the actual report output to the user through the use of a ReportViewer control in an ASP.Net application - this reduces the amount of data that is accessible from outside your company's firewall.

Hope that helps,

-Lukasz

|||Hi Lukasz,
I have the same issue, however I am trying to execute the report builder from the server itself. If I login as the domain administrator then it works. If I log in as any one else (even users that are part of the Administrators and Domain Admin accounts) then it fails with this error.

Thoughts?|||

Have you had any luck with this issue? If so, please let me know what you did to figure it out.

|||Have you had any luck with this problem. If so please inform me on your solutions.|||

Your users, are they able to see the report builder button in report manager?

What is the exact error they get when they try to launch report builder?

-Lukasz

|||Yes, they can see the button.

When they click on the Report Builder button a dialog pops up saying that it is Launching Application.

This is quickly replaced by a dialog titled "Cannot start application" which says:
"Cannot retrieve application. Authentication error."

When I click on the details button then I can see the error "The remote server returned an error: (401) Unauthorized."|||We are trying to get the report builder to be accessed from the url and at the time we can, due to the fact that we are allowing the users to access it using the administrator login. At the moment it is not asking for credentials, but we are wanting to add users and allow them access through the users credentials, not the administrators. We are also wanting to allow users to access reports on the server through their credentials and allow certain users access to certain folders on the server. Could you walk us through adding a user and allowing the user access to certain folders on the server and finally the report builder?|||

I think your issue is different than that of the others on this thread. You can get started with security in reporting services here:

http://msdn2.microsoft.com/en-us/library/ms156014.aspx

-Lukasz

|||

Are your users in the same domain or a trusted domain as your report server? Do you use forms authentication for your report server?

-Lukasz

|||I had this same problem and found a good solution here.|||I have the same problem except Reporting Services is running in SharePoint integration mode, setting anonymous access on the report builder directory doesn't help.

Any ideas how to fix this problem when running Reporting Services in integrated mode?

Connecting to SQL 2005 from a client pc

I am getting this message. On the actual server I can pull up the report builder, but from a client on the network when trying to connect to the sql report builder I get this message:

SOURCES
Deployment url : http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [3/16/2006 10:10:28 AM] : Activation of http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application has started.

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

Thank you for any suggestions

Have you had any luck with your issue? I am having a similar issue and have posted about it, but so far, no response.

ANY info you might have would be appreciated, thanks!

|||

I'm having the same problem, seams like reportbuilder can't connect to host when you try to use it in an EXTRANET, because if you try it in an INTRANET works perfectly.

I hope someone could help us on this matter. (ASAP)

|||

Couple of things about Report Builder -

1) Report Builder requires the .net framework 2.0 to be installed on the client machine. I think that's the problem you're encountering related to to the .application file.

Hope that helps,

-Lukasz

Thoughts?|||

Have you had any luck with this issue? If so, please let me know what you did to figure it out.

|||Have you had any luck with this problem. If so please inform me on your solutions.|||

Your users, are they able to see the report builder button in report manager?

What is the exact error they get when they try to launch report builder?

-Lukasz

|||Yes, they can see the button.

When they click on the Report Builder button a dialog pops up saying that it is Launching Application.

This is quickly replaced by a dialog titled "Cannot start application" which says:
"Cannot retrieve application. Authentication error."

I think your issue is different than that of the others on this thread. You can get started with security in reporting services here:

http://msdn2.microsoft.com/en-us/library/ms156014.aspx

-Lukasz

|||

Are your users in the same domain or a trusted domain as your report server? Do you use forms authentication for your report server?

-Lukasz

Any ideas how to fix this problem when running Reporting Services in integrated mode?

Connecting to SQL 2005 from a client pc

I am getting this message. On the actual server I can pull up the report builder, but from a client on the network when trying to connect to the sql report builder I get this message:

SOURCES
Deployment url : http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [3/16/2006 10:10:28 AM] : Activation of http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application has started.

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

Thank you for any suggestions

Have you had any luck with your issue? I am having a similar issue and have posted about it, but so far, no response.

ANY info you might have would be appreciated, thanks!

|||

I'm having the same problem, seams like reportbuilder can't connect to host when you try to use it in an EXTRANET, because if you try it in an INTRANET works perfectly.

I hope someone could help us on this matter. (ASAP)

|||

Couple of things about Report Builder -

1) Report Builder requires the .net framework 2.0 to be installed on the client machine. I think that's the problem you're encountering related to to the .application file.

Hope that helps,

-Lukasz

Thoughts?|||

Have you had any luck with this issue? If so, please let me know what you did to figure it out.

|||Have you had any luck with this problem. If so please inform me on your solutions.|||

Your users, are they able to see the report builder button in report manager?

What is the exact error they get when they try to launch report builder?

-Lukasz

|||Yes, they can see the button.

When they click on the Report Builder button a dialog pops up saying that it is Launching Application.

This is quickly replaced by a dialog titled "Cannot start application" which says:
"Cannot retrieve application. Authentication error."

I think your issue is different than that of the others on this thread. You can get started with security in reporting services here:

http://msdn2.microsoft.com/en-us/library/ms156014.aspx

-Lukasz

|||

Are your users in the same domain or a trusted domain as your report server? Do you use forms authentication for your report server?

-Lukasz

Any ideas how to fix this problem when running Reporting Services in integrated mode?
sql sql

Connecting to SQL 2005 from a client pc

I am getting this message. On the actual server I can pull up the report builder, but from a client on the network when trying to connect to the sql report builder I get this message:

SOURCES
Deployment url : http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [3/16/2006 10:10:28 AM] : Activation of http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application has started.

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

Thank you for any suggestions

Have you had any luck with your issue? I am having a similar issue and have posted about it, but so far, no response.

ANY info you might have would be appreciated, thanks!

|||

I'm having the same problem, seams like reportbuilder can't connect to host when you try to use it in an EXTRANET, because if you try it in an INTRANET works perfectly.

I hope someone could help us on this matter. (ASAP)

|||

Couple of things about Report Builder -

1) Report Builder requires the .net framework 2.0 to be installed on the client machine. I think that's the problem you're encountering related to to the .application file.

Hope that helps,

-Lukasz

Thoughts?|||

Have you had any luck with this issue? If so, please let me know what you did to figure it out.

|||Have you had any luck with this problem. If so please inform me on your solutions.|||

Your users, are they able to see the report builder button in report manager?

What is the exact error they get when they try to launch report builder?

-Lukasz

|||Yes, they can see the button.

When they click on the Report Builder button a dialog pops up saying that it is Launching Application.

This is quickly replaced by a dialog titled "Cannot start application" which says:
"Cannot retrieve application. Authentication error."

I think your issue is different than that of the others on this thread. You can get started with security in reporting services here:

http://msdn2.microsoft.com/en-us/library/ms156014.aspx

-Lukasz

|||

Are your users in the same domain or a trusted domain as your report server? Do you use forms authentication for your report server?

-Lukasz

Any ideas how to fix this problem when running Reporting Services in integrated mode?

connecting to SQL 2000 Server gives SQL 2005 error message

Hi,

Here is the syntax of the connection string within the web.config file:

<addname="MyConnectionString"connectionString="Data Source=000.000.000;Initial Catalog=Database Name;Persist Security Info=True;User ID=XXXXXX;Password=XXXXXX;"providerName="System.Data.SqlClient" />

</connectionStrings>

The test page has a GridView in it which uses the connectionstring fron the web.config file.

Error Message:

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)

Not sure why .NET thinks it's a SQL 2005 server

I can connect to the database via VS 2005, and through Enterprise Manager... just from the ASP.NET page.

Any ideas?

Thanks,
Roland

By default SQ2005 does not have remote connections enable, you need to go to Surface Configuration and the first tap change from pipe to remote connections. That shall fix the problem.

|||

Thanks Al, but the problem is that the server is SQL 2000 and NOT SQL 2005.

So, I'm not sure why .NET thinks, or is getting the information to say that the SQL server is SQL 2005.

So to reiterate the question:

Why do I get a SQL 2005 error while connecting to a SQL 2000 database?

Thanks again,

Roland

|||

Then must be a firewall between or again you can change SQL 2000 to use only pipes, check that and let me know

|||

Why you got a message about MS SQL Server 2005 while the version you have is MS SQL Server 2000?

This is beacuse you are using MS Viusal Studio.NET 2005 which install a SQL Express (lite SQL Server - similar to MSDE) on your machine and by default it will coneect to it.

This SQL Express uses a SQL Server 2005 engine, and that is why you saw "When connecting to SQL Server 2005, ...." message.

Ok, what to do?

Change the default connection string from your IIS.

Open your IIS, then click on your "Virtual Directory" (e.g. your ASP.NET Website) then go to its configuration and change the Server name part in the ConnectionString.

Hope this will help you as it helped me eairler.

Regards,

sql sql

Sunday, February 12, 2012

Connect to SQLExpress via Internet with Windows Authentication?

I posted this message on Google but never received an answer so I thought I would try here.

Is it possible to connect to SQLExpress over the Internet (TCP/IP) using Windows Authentication? I can connect using SQL Authentication but the client would rather use Windows Authentication to avoid manageing another set of user names and passwords.

I have tried connecting with a workstation using cached credentials but I just receive an error "Cannot generate SSPI context".

Any assistance is appreciated.

By “Internet” do you mean the network around world, or just “across TCP/IP within your client’s intranet”?

Zlatko

|||Your client would need to open up 'windows' ports on their server in order to get windows auth to work. (i.e. SMB and other ports, including kerberos, etc.)

Typically, this is the WORST possible move to do on a web facing server, it effectively puts the server 'out' on the internet. Yes, Windows Authentication IS more secure than SQL Server auth, but when you put your server 'out' like that on the internet, then you're exposing it to hackers who may stumble across it and attempt to brute-force their way on to the box. Even if they don't succeeed, they may DOS the box with all of the traffic.

In other words, YES, you can use windows authentication on the "internet" but that requires your server to therefore be on the "internet" - i.e. it's no longer effectively behind a firewall and in your 'LAN' it's just 'out' and ready to be hacked.

If you really need more security than what SQL Server auth provides (which can be made pretty secure using pass phrases instead of passwords (like "When will the world end, I wonder?"), then maybe look at getting a VPN.

|||Internet as in worldwide.|||

I was afraid someone was going to say that but I appreciate the feedback. I know SQL authentication is not very secure and was hoping Windows authentication would be a better solution.

Ideally I would lik to find a way to have users connect to the SQL server using RPC over HTTP similar to how Outlook 2003 remotley connects to Exchange 2003 without VPN or openning ports on the firewall.

Does anyone happen to know how I might do this with SQL?

|||SQL Server 2005 natively supports SOAP over http.

Sunday, March 25, 2012

connecting to SQL DATABASE ENGINE

Thursday, March 22, 2012

Connecting to SQL 2005 from a client pc

Connecting to SQL 2005 from a client pc

Connecting to SQL 2005 from a client pc

Connecting to SQL 2005 from a client pc

connecting to SQL 2000 Server gives SQL 2005 error message

Sunday, February 12, 2012

Connect to SQLExpress via Internet with Windows Authentication?

Connect to SQL Server

Blog Archive

About Me