Showing posts with label localhost. Show all posts
Showing posts with label localhost. Show all posts

Saturday, February 25, 2012

Connection error

Hi there,

I installed Visual Web Developer Express and SQL Server Express. I then installed the Time Tracker Starter Kit on my localhost. My instance of SQL Server Express is 'Express'. So I updated the root web.config file. I try out the app. by creating a new user and then get this error:

Exception Details:System.Data.SqlClient.SqlException: 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)

I'm using a HTTP connection port 7080 (ie,http://localhost:7080/TimeTracker/), does that mean I have to update anything in the app?

I was told to update SQL Server 2005 Surface Area Configuration - Remote Connections to Using both TCP/IP and named pipes. So I already did that and rebooted.

Any suggestions?

Post your connection string, it may helpSmile|||

Hey it works.

I noticed that I had to modify the database connnection under the database explorer, even though I had updated the web.config

Take care

Friday, February 24, 2012

Connection cannot be made to http://localhost/ReportServer

I have developed a reports in Business Intelligence Development studio and when I am tring to deploy it.
It says that
Connection cannot be made to http://localhost/ReportServer
What does it really mean.Is SSRS service running ?|||

Do you have Reporting Services install on Localhost?

Has it been configured?

Is IIS running?

That's a start.

BobP

|||Yess, it is runnning .|||IIS install - > start, control panel, add remove progs, add/remove windows components ->
tick IIS, click next etc...

Think you need to be running XP pro to do this, don't think you can do it from Home edition

Shurely you need to do this before you install RS, no? I can't remember the install process of RS....|||

It wont let you install SSRS without IIS.

BobP

|||If IIS is running then it must be user permissions on the IIS folder.

Connection broken on localhost

Following error occurs when I execute stored procedure sp_updatestats to update
statistics:
...
Updating dbo.AttachmentFolderDefinition
Updating dbo.Branch
...
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionRead
(WrapperRead()). Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
I am running the procedure from the SQL Query Analyzer locally from the server.
Sometimes the same error occurs when I do a backup or when I run other stored
procedures.
The SQL Server log and Event Log didn't help.
Any ideas ?
Thanks
Radek
Radek,
You are probably running into this issue:
FIX: General network error when you try to back up or restore a SQL
Server database on a computer that is running Windows Server 2003
http://support.microsoft.com/?id=827452
Try using TCP/IP as your network library instead of Named Pipes.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Radek Pospisil wrote:
> Following error occurs when I execute stored procedure sp_updatestats to update
> statistics:
> ...
> Updating dbo.AttachmentFolderDefinition
> Updating dbo.Branch
> ...
> [Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionRead
> (WrapperRead()). Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
>
> I am running the procedure from the SQL Query Analyzer locally from the server.
> Sometimes the same error occurs when I do a backup or when I run other stored
> procedures.
> The SQL Server log and Event Log didn't help.
> Any ideas ?
> Thanks
> Radek
|||You are right. Thanks a lot.
Radek
Mark Allison <marka@.no.tinned.meat.mvps.org> wrote in
news:OdUmcoc4EHA.4092@.TK2MSFTNGP14.phx.gbl:

> Radek,
> You are probably running into this issue:
> FIX: General network error when you try to back up or restore a SQL
> Server database on a computer that is running Windows Server 2003
> http://support.microsoft.com/?id=827452
> Try using TCP/IP as your network library instead of Named Pipes.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>

Tuesday, February 14, 2012

Connecting to yukon db

Hi all,
This should be an easy question to answer...

I'm trying to connect to my SQL Server 2005 (running on localhost) from the code-behind of a test webpage that I made. The connection string I'm using is:

Data Source=localhost;Initial Catalog=dbname;User Id=username;Password=password;Timeout=160

I think the reason I'm confused is that I can't create a user in Yukon like in 2000, assigning it a username and password. In Yukon, there's no option to create a password for a user... I saw that I can create a username and password if I create an application role, so is this what I'm supposed to use?

Whenever I create a user or application role and try to connect to it w/this connection string, I get:

No process is on the other end of the pipe.

If I make the user or application role the owner of the db_owner schema then this error message goes away but I then get:

Invalid login for user ____

I already made sure that I have tcp/ip and named pipes enabled for local and remote conns.

Lastly, when I create a user, I have to give it a login name, which is a windows user account, so I have no idea what to put for that.

So I guess my question is, what is the proper way to set up a user or application role in sql server 2005 and then be able to connect to it w/ado.net 2.0?

Thanks,
JustinThere two permissions in SQL Server the server permissions in SQL Server 2005 are still under security in management studio but the database permissions are now under security in the database. Hope this helps.|||Thanks for the quick response, but what you posted is what I already know...

Can anyone give advice on how to set up a user or application role properly to be used from an application. Which is more appropriate to use: app role or user? What schema should be set for them? What permissions should be given to them?

Thanks,
Justin|||The answer I was looking for was "Logins".