Showing posts with label wrong. Show all posts
Showing posts with label wrong. Show all posts

Tuesday, March 20, 2012

Connection Managers not installed?

apologies if this is the wrong group ..

whenever I create an Integrated Services project and attempt to add a Connection Manager I get the error

Connection Manager 'blah' is not properly installed on this computer.

(Microsoft.DataTransformationServices.Design)

This happens with all menu options except New Connection..

I have uninstalled and reinstalled both Visual Studio 2005 and SQL Server 2005 and made sure I have selected everything in each case

what am I missing?

Thanks

Chris

seems this has happened to others

see Jason Lodice thread for solution

Chris

Friday, February 17, 2012

connecting using a trusted connection

Hello,

I appologize if this is in the wrong spot, but it seemed like the appropriate place.

We have IIS installed on one box and SQL on another. We use a trusted connection to connect.

When we try an connect to our DB, we don't get an error, the page just refreshes. From what i have gathered, it looks like we are not being authenticated. We have the ASPNET domain user on both boxes and its configured with the correct permissions, but we still can't connect.

Do i need to set up or give permissions to another account i dont know about, or is there some file that needs access?

Have you checked SQL logs, or IIS logs? Event logs? If it's a securtiy issue it should be logged. Also make sure you really are using the ASP.NET account when you access the box, it could be an authenticated user's credentials that are passed. And keep in mind that by defualt the ASp.NET process account is not a domain account, it's local.

Jeff

|||There are two permissions in SQL Server, the server permissions in the management section of Enterprise Manager or Management Studio and the database permissions are in the database under permissions and in SQL Server 2005 under security in the database. You may have created one and not the other. Hope this helps.

Tuesday, February 14, 2012

Connecting to wrong SQL Server

I have a machine where I have installed Visual Studio 2005 including SQLExpr
ess. I have also installed MSDE2000. They are both named instances:
MyMachine\SQLExpress and MyMachine\S3MSDE.
Locally everything works fine. But when I connect to MyMachine from an other
machine with the connectstring containing '...Data
Source=MyMachine\S3MSDE,1234;...' I always end up beeing connected to the SQ
LExpress instance of SQL Server.
WHY?
ToschIt looks like you are always connecting to the default port. Try starting
the SQL Server Browser Service on MyMachine. It is the browser service that
resolves the name to the correct port.
--
Rick Byham
MCDBA, MCSE, MCSA
Documentation Manager,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Tosch" <tosch_nospam@.swissonline.ch> wrote in message
news:o50292l98e45ugu0j7cej427gm5qeaj5ju@.
4ax.com...
>I have a machine where I have installed Visual Studio 2005 including
>SQLExpress. I have also installed MSDE2000. They are both named instances:
> MyMachine\SQLExpress and MyMachine\S3MSDE.
> Locally everything works fine. But when I connect to MyMachine from an
> other machine with the connectstring containing '...Data
> Source=MyMachine\S3MSDE,1234;...' I always end up beeing connected to the
> SQLExpress instance of SQL Server.
> WHY?
> Tosch
>|||It looks like you are always connecting to the default port. Try starting
the SQL Server Browser Service on MyMachine. It is the browser service that
resolves the name to the correct port.
--
Rick Byham
MCDBA, MCSE, MCSA
Documentation Manager,
Microsoft, SQL Server Books Online
This posting is provided "as is" with
no warranties, and confers no rights.
"Tosch" <tosch_nospam@.swissonline.ch> wrote in message
news:o50292l98e45ugu0j7cej427gm5qeaj5ju@.
4ax.com...
>I have a machine where I have installed Visual Studio 2005 including
>SQLExpress. I have also installed MSDE2000. They are both named instances:
> MyMachine\SQLExpress and MyMachine\S3MSDE.
> Locally everything works fine. But when I connect to MyMachine from an
> other machine with the connectstring containing '...Data
> Source=MyMachine\S3MSDE,1234;...' I always end up beeing connected to the
> SQLExpress instance of SQL Server.
> WHY?
> Tosch
>|||ok, since I changed the port number to the port number msde2000 uses everyth
ing works fine. Apparently if you add the port number the name of the
sqlserver/instance doesn't seem to matter.
Tosch
On Thu, 15 Jun 2006 08:05:26 -0700, "Rick Byham [MS]" <rickbyh@.online.mi
crosoft.com> wrote:

>It looks like you are always connecting to the default port. Try starting
>the SQL Server Browser Service on MyMachine. It is the browser service that
>resolves the name to the correct port.|||ok, since I changed the port number to the port number msde2000 uses everyth
ing works fine. Apparently if you add the port number the name of the
sqlserver/instance doesn't seem to matter.
Tosch
On Thu, 15 Jun 2006 08:05:26 -0700, "Rick Byham [MS]" <rickbyh@.online.mi
crosoft.com> wrote:

>It looks like you are always connecting to the default port. Try starting
>the SQL Server Browser Service on MyMachine. It is the browser service that
>resolves the name to the correct port.

Connecting to SQLServer

I apologize if this is in the wrong place, I don't know where this
question would be appropriate.
We are doing a class project with ASP .Net and SQL Server. For this
exercise, we had to create tables and then connect to the tables from
a web form.
I have Visual Studio 2005, SQL Server Management Studio (Express) and
SQLServer Express. I can use Server Management studio and run SQL
against my database.
When I try to connect to the database from Visual Studio's Connection
Explorer, I get a long delay and then an error message pops us saying:
"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)"
Is there something I need to configure or can anyone give me some
advice on what I need to do to connect?
Thanks
MikeFirst off, make sure that SQL Server is started. I don't remember if
SQL Express has SQL Server Configuration Manager, but you can check this
out in the Services applet of the control panel. That'd be my first
guess.
MikeB wrote:
> I apologize if this is in the wrong place, I don't know where this
> question would be appropriate.
> We are doing a class project with ASP .Net and SQL Server. For this
> exercise, we had to create tables and then connect to the tables from
> a web form.
> I have Visual Studio 2005, SQL Server Management Studio (Express) and
> SQLServer Express. I can use Server Management studio and run SQL
> against my database.
> When I try to connect to the database from Visual Studio's Connection
> Explorer, I get a long delay and then an error message pops us saying:
> "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)"
> Is there something I need to configure or can anyone give me some
> advice on what I need to do to connect?
> Thanks
> Mike
>|||SQL Server Express does have Server Configuration Manager. It shows
the SQL Server (SQLEXPRESS) as running and SQL Server Browser as
stopped. As I said in my post, I can't seem to find a way to start the
SQL Server Browser, all the buttons are greyed out when I look at the
properties.
On Feb 27, 7:23 am, David Markle <new...@.markleconsulting.c0m> wrote:
> First off, make sure that SQL Server is started. I don't remember if
> SQL Express has SQL Server Configuration Manager, but you can check this
> out in the Services applet of the control panel. That'd be my first
> guess.
>
> MikeB wrote:
>
>
>
>
>
>
> - Show quoted text -|||I think you are correct that SQL Server is not started. If I open a
command prompt window and type
osql -L
I get a long pause and then the response
TRISTAN/SQLEXPRESS
Tristan is my computer name
When I type
CQLCMD -L
I get a long pause and then a blank list.
I really don't know what I should do to start SQL Server. Can you give
me a clue?
Thanks
On Feb 27, 7:23 am, David Markle <new...@.markleconsulting.c0m> wrote:
> First off, make sure that SQL Server is started. I don't remember if
> SQL Express has SQL Server Configuration Manager, but you can check this
> out in the Services applet of the control panel. That'd be my first
> guess.
>
> MikeB wrote:
>
>
>
>
>
>
> - Show quoted text -|||I'm so relieved, I got this fixed. It was the Server Browser that
wasn't started. I found this post that helped me locate the problem:
http://blogs.msdn.com/sqlexpress/ar.../23/192044.aspx
Just posting it here in case someone else come searching for the
answer...
On Feb 26, 4:39 pm, "MikeB" <MPBr...@.gmail.com> wrote:
> I apologize if this is in the wrong place, I don't know where this
> question would be appropriate.
> We are doing a class project with ASP .Net and SQL Server. For this
> exercise, we had to create tables and then connect to the tables from
> a web form.
> I have Visual Studio 2005, SQL Server Management Studio (Express) and
> SQLServer Express. I can use Server Management studio and run SQL
> against my database.
> When I try to connect to the database from Visual Studio's Connection
> Explorer, I get a long delay and then an error message pops us saying:
> "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)"
> Is there something I need to configure or can anyone give me some
> advice on what I need to do to connect?
> Thanks
> Mike

Connecting to SQLServer

I apologize if this is in the wrong place, I don't know where this
question would be appropriate.
We are doing a class project with ASP .Net and SQL Server. For this
exercise, we had to create tables and then connect to the tables from
a web form.
I have Visual Studio 2005, SQL Server Management Studio (Express) and
SQLServer Express. I can use Server Management studio and run SQL
against my database.
When I try to connect to the database from Visual Studio's Connection
Explorer, I get a long delay and then an error message pops us saying:
"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)"
Is there something I need to configure or can anyone give me some
advice on what I need to do to connect?
Thanks
Mike
I'm so relieved, I got this fixed. It was the Server Browser that
wasn't started. I found this post that helped me locate the problem:
http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx
Just posting it here in case someone else come searching for the
answer...
On Feb 26, 4:39 pm, "MikeB" <MPBr...@.gmail.com> wrote:
> I apologize if this is in the wrong place, I don't know where this
> question would be appropriate.
> We are doing a class project with ASP .Net and SQL Server. For this
> exercise, we had to create tables and then connect to the tables from
> a web form.
> I have Visual Studio 2005, SQL Server Management Studio (Express) and
> SQLServer Express. I can use Server Management studio and run SQL
> against my database.
> When I try to connect to the database from Visual Studio's Connection
> Explorer, I get a long delay and then an error message pops us saying:
> "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)"
> Is there something I need to configure or can anyone give me some
> advice on what I need to do to connect?
> Thanks
> Mike

Connecting to SQLServer

I apologize if this is in the wrong place, I don't know where this
question would be appropriate.
We are doing a class project with ASP .Net and SQL Server. For this
exercise, we had to create tables and then connect to the tables from
a web form.
I have Visual Studio 2005, SQL Server Management Studio (Express) and
SQLServer Express. I can use Server Management studio and run SQL
against my database.
When I try to connect to the database from Visual Studio's Connection
Explorer, I get a long delay and then an error message pops us saying:
"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)"
Is there something I need to configure or can anyone give me some
advice on what I need to do to connect?
Thanks
MikeFirst off, make sure that SQL Server is started. I don't remember if
SQL Express has SQL Server Configuration Manager, but you can check this
out in the Services applet of the control panel. That'd be my first
guess.
MikeB wrote:
> I apologize if this is in the wrong place, I don't know where this
> question would be appropriate.
> We are doing a class project with ASP .Net and SQL Server. For this
> exercise, we had to create tables and then connect to the tables from
> a web form.
> I have Visual Studio 2005, SQL Server Management Studio (Express) and
> SQLServer Express. I can use Server Management studio and run SQL
> against my database.
> When I try to connect to the database from Visual Studio's Connection
> Explorer, I get a long delay and then an error message pops us saying:
> "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)"
> Is there something I need to configure or can anyone give me some
> advice on what I need to do to connect?
> Thanks
> Mike
>|||SQL Server Express does have Server Configuration Manager. It shows
the SQL Server (SQLEXPRESS) as running and SQL Server Browser as
stopped. As I said in my post, I can't seem to find a way to start the
SQL Server Browser, all the buttons are greyed out when I look at the
properties.
On Feb 27, 7:23 am, David Markle <new...@.markleconsulting.c0m> wrote:
> First off, make sure that SQL Server is started. I don't remember if
> SQL Express has SQL Server Configuration Manager, but you can check this
> out in the Services applet of the control panel. That'd be my first
> guess.
>
> MikeB wrote:
> > I apologize if this is in the wrong place, I don't know where this
> > question would be appropriate.
> > We are doing a class project with ASP .Net and SQL Server. For this
> > exercise, we had to create tables and then connect to the tables from
> > a web form.
> > I have Visual Studio 2005, SQL Server Management Studio (Express) and
> > SQLServer Express. I can use Server Management studio and run SQL
> > against my database.
> > When I try to connect to the database from Visual Studio's Connection
> > Explorer, I get a long delay and then an error message pops us saying:
> > "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)"
> > Is there something I need to configure or can anyone give me some
> > advice on what I need to do to connect?
> > Thanks
> > Mike- Hide quoted text -
> - Show quoted text -|||I think you are correct that SQL Server is not started. If I open a
command prompt window and type
osql -L
I get a long pause and then the response
TRISTAN/SQLEXPRESS
Tristan is my computer name
When I type
CQLCMD -L
I get a long pause and then a blank list.
I really don't know what I should do to start SQL Server. Can you give
me a clue?
Thanks
On Feb 27, 7:23 am, David Markle <new...@.markleconsulting.c0m> wrote:
> First off, make sure that SQL Server is started. I don't remember if
> SQL Express has SQL Server Configuration Manager, but you can check this
> out in the Services applet of the control panel. That'd be my first
> guess.
>
> MikeB wrote:
> > I apologize if this is in the wrong place, I don't know where this
> > question would be appropriate.
> > We are doing a class project with ASP .Net and SQL Server. For this
> > exercise, we had to create tables and then connect to the tables from
> > a web form.
> > I have Visual Studio 2005, SQL Server Management Studio (Express) and
> > SQLServer Express. I can use Server Management studio and run SQL
> > against my database.
> > When I try to connect to the database from Visual Studio's Connection
> > Explorer, I get a long delay and then an error message pops us saying:
> > "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)"
> > Is there something I need to configure or can anyone give me some
> > advice on what I need to do to connect?
> > Thanks
> > Mike- Hide quoted text -
> - Show quoted text -|||I'm so relieved, I got this fixed. It was the Server Browser that
wasn't started. I found this post that helped me locate the problem:
http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx
Just posting it here in case someone else come searching for the
answer...
On Feb 26, 4:39 pm, "MikeB" <MPBr...@.gmail.com> wrote:
> I apologize if this is in the wrong place, I don't know where this
> question would be appropriate.
> We are doing a class project with ASP .Net and SQL Server. For this
> exercise, we had to create tables and then connect to the tables from
> a web form.
> I have Visual Studio 2005, SQL Server Management Studio (Express) and
> SQLServer Express. I can use Server Management studio and run SQL
> against my database.
> When I try to connect to the database from Visual Studio's Connection
> Explorer, I get a long delay and then an error message pops us saying:
> "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)"
> Is there something I need to configure or can anyone give me some
> advice on what I need to do to connect?
> Thanks
> Mike