Can't Connect

I have just installed Sql server 2005 on my Win XP Pro machine.
When I go into the sql server management studio, there is only
one entry under the "database engine" entry in the registered servers'
panel on the left. It is MyServerName\SQLEXPRESS.
When I click on it and then select connect, either new query
or object explorer, I get one of the following errors.
An error has occurred while establishing a connection to there server.
When connecting to SQL Server 2005, the 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 )
An error has occurred while establishing a connection to there server.
When connecting to SQL Server 2005, the 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.
I have looked all over the internet, but couldn't find anything that
would help.
I went into the sql server configuration manger, and enabled the name
pipes and rebooted.
I didn't work. In the sql service configuration manager I have five
services that are status of
running and startup mode of automatic. However they are not for the
SQLExpress server.
They are for another sql server name, that I put in for the server name
when I installed
sql server 2005. I thought that would be the server name.
There are two entries under sql server 2005 network configuration
Protocals for SQLEXPRESS and
Protocals for Myotherservername
How can I connect.
Why do I have two instances are those instances of servers,
I thought that there was only server.
What do I do?
Thanks in Advance,
Laurence
I suggest starting with my blog entry on connecting. Just search
www.betav.com/blog/billva. There are several relevant articles there.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Larry" <NoSpam@.Something.com> wrote in message
news:e5O9nLU3HHA.5316@.TK2MSFTNGP04.phx.gbl...
>I have just installed Sql server 2005 on my Win XP Pro machine.
> When I go into the sql server management studio, there is only
> one entry under the "database engine" entry in the registered servers'
> panel on the left. It is MyServerName\SQLEXPRESS.
> When I click on it and then select connect, either new query
> or object explorer, I get one of the following errors.
> An error has occurred while establishing a connection to there server.
> When connecting to SQL Server 2005, the 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 )
> An error has occurred while establishing a connection to there server.
> When connecting to SQL Server 2005, the 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.
> I have looked all over the internet, but couldn't find anything that would
> help.
> I went into the sql server configuration manger, and enabled the name
> pipes and rebooted.
> I didn't work. In the sql service configuration manager I have five
> services that are status of
> running and startup mode of automatic. However they are not for the
> SQLExpress server.
> They are for another sql server name, that I put in for the server name
> when I installed
> sql server 2005. I thought that would be the server name.
> There are two entries under sql server 2005 network configuration
> Protocals for SQLEXPRESS and
> Protocals for Myotherservername
>
> How can I connect.
> Why do I have two instances are those instances of servers,
> I thought that there was only server.
> What do I do?
> Thanks in Advance,
> Laurence
>
>
>
>
|||Thank You.
William Vaughn wrote:
> I suggest starting with my blog entry on connecting. Just search
> www.betav.com/blog/billva. There are several relevant articles there.
>
sql

Can't connect

I've installed Visual Studio 2005 (including SQL Express) on a XP Home
machine. I've currently problems to connect to the SQL-Server getting the
following error message
C:\Dokumente und Einstellungen\Robert>sqlcmd
HResult 0x2, Level 16, State 1
Named Pipes Provider: Could not open a connection to SQL Server [2].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
establi
shing a connection to the server. When connecting to SQL Server 2005, this
failu
re may be caused by the fact that under the default settings SQL Server does
not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
I've allready
- enabled the Protocolls via the SQL Server Configuration Manager
- stopped the firewall
- tried it via Access, VS 2005 Server Explorer, ...
I get access to the database when I use SSEUTIL ! Using this tool it was
e.g. possible to attach/dettach a database.
Any idea whats wrong?
Are you in fact trying to connect remotely? If you are, you will need to
enable and start SQLBrowser also. If not, are you using .\sqlexpress as
your server name in the connection string?
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Robert" <Robert@.discussions.microsoft.com> wrote in message
news:B34E3E09-A80B-43C8-B164-4D4B299C10BF@.microsoft.com...
> I've installed Visual Studio 2005 (including SQL Express) on a XP Home
> machine. I've currently problems to connect to the SQL-Server getting the
> following error message
> C:\Dokumente und Einstellungen\Robert>sqlcmd
> HResult 0x2, Level 16, State 1
> Named Pipes Provider: Could not open a connection to SQL Server [2].
> Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
> establi
> shing a connection to the server. When connecting to SQL Server 2005, this
> failu
> re may be caused by the fact that under the default settings SQL Server
> does
> not
> allow remote connections..
> Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
> I've allready
> - enabled the Protocolls via the SQL Server Configuration Manager
> - stopped the firewall
> - tried it via Access, VS 2005 Server Explorer, ...
> I get access to the database when I use SSEUTIL ! Using this tool it was
> e.g. possible to attach/dettach a database.
> Any idea whats wrong?
|||Hi Roger,
thank you very much. I missed the ".\sqlexpress". Adding this to the
connection string everything worked.
"Roger Wolter[MSFT]" wrote:

> Are you in fact trying to connect remotely? If you are, you will need to
> enable and start SQLBrowser also. If not, are you using .\sqlexpress as
> your server name in the connection string?
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Robert" <Robert@.discussions.microsoft.com> wrote in message
> news:B34E3E09-A80B-43C8-B164-4D4B299C10BF@.microsoft.com...
>
>

Can't Connect

I have just installed Sql server 2005 on my Win XP Pro machine.
When I go into the sql server management studio, there is only
one entry under the "database engine" entry in the registered servers'
panel on the left. It is MyServerName\SQLEXPRESS.
When I click on it and then select connect, either new query
or object explorer, I get one of the following errors.
An error has occurred while establishing a connection to there server.
When connecting to SQL Server 2005, the 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 )
An error has occurred while establishing a connection to there server.
When connecting to SQL Server 2005, the 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.
I have looked all over the internet, but couldn't find anything that
would help.
I went into the sql server configuration manger, and enabled the name
pipes and rebooted.
I didn't work. In the sql service configuration manager I have five
services that are status of
running and startup mode of automatic. However they are not for the
SQLExpress server.
They are for another sql server name, that I put in for the server name
when I installed
sql server 2005. I thought that would be the server name.
There are two entries under sql server 2005 network configuration
Protocals for SQLEXPRESS and
Protocals for Myotherservername
How can I connect.
Why do I have two instances are those instances of servers,
I thought that there was only server.
What do I do?
Thanks in Advance,
LaurenceI suggest starting with my blog entry on connecting. Just search
www.betav.com/blog/billva. There are several relevant articles there.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Larry" <NoSpam@.Something.com> wrote in message
news:e5O9nLU3HHA.5316@.TK2MSFTNGP04.phx.gbl...
>I have just installed Sql server 2005 on my Win XP Pro machine.
> When I go into the sql server management studio, there is only
> one entry under the "database engine" entry in the registered servers'
> panel on the left. It is MyServerName\SQLEXPRESS.
> When I click on it and then select connect, either new query
> or object explorer, I get one of the following errors.
> An error has occurred while establishing a connection to there server.
> When connecting to SQL Server 2005, the 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 )
> An error has occurred while establishing a connection to there server.
> When connecting to SQL Server 2005, the 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.
> I have looked all over the internet, but couldn't find anything that would
> help.
> I went into the sql server configuration manger, and enabled the name
> pipes and rebooted.
> I didn't work. In the sql service configuration manager I have five
> services that are status of
> running and startup mode of automatic. However they are not for the
> SQLExpress server.
> They are for another sql server name, that I put in for the server name
> when I installed
> sql server 2005. I thought that would be the server name.
> There are two entries under sql server 2005 network configuration
> Protocals for SQLEXPRESS and
> Protocals for Myotherservername
>
> How can I connect.
> Why do I have two instances are those instances of servers,
> I thought that there was only server.
> What do I do?
> Thanks in Advance,
> Laurence
>
>
>
>|||Thank You.
William Vaughn wrote:
> I suggest starting with my blog entry on connecting. Just search
> www.betav.com/blog/billva. There are several relevant articles there.
>

Can't connect

I've installed Visual Studio 2005 (including SQL Express) on a XP Home
machine. I've currently problems to connect to the SQL-Server getting the
following error message
C:\Dokumente und Einstellungen\Robert>sqlcmd
HResult 0x2, Level 16, State 1
Named Pipes Provider: Could not open a connection to SQL Server [2].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
establi
shing a connection to the server. When connecting to SQL Server 2005, this
failu
re may be caused by the fact that under the default settings SQL Server does
not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
I've allready
- enabled the Protocolls via the SQL Server Configuration Manager
- stopped the firewall
- tried it via Access, VS 2005 Server Explorer, ...
I get access to the database when I use SSEUTIL ! Using this tool it was
e.g. possible to attach/dettach a database.
Any idea whats wrong?Are you in fact trying to connect remotely? If you are, you will need to
enable and start SQLBrowser also. If not, are you using .\sqlexpress as
your server name in the connection string?
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Robert" <Robert@.discussions.microsoft.com> wrote in message
news:B34E3E09-A80B-43C8-B164-4D4B299C10BF@.microsoft.com...
> I've installed Visual Studio 2005 (including SQL Express) on a XP Home
> machine. I've currently problems to connect to the SQL-Server getting the
> following error message
> C:\Dokumente und Einstellungen\Robert>sqlcmd
> HResult 0x2, Level 16, State 1
> Named Pipes Provider: Could not open a connection to SQL Server [2].
> Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
> establi
> shing a connection to the server. When connecting to SQL Server 2005, this
> failu
> re may be caused by the fact that under the default settings SQL Server
> does
> not
> allow remote connections..
> Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
> I've allready
> - enabled the Protocolls via the SQL Server Configuration Manager
> - stopped the firewall
> - tried it via Access, VS 2005 Server Explorer, ...
> I get access to the database when I use SSEUTIL ! Using this tool it was
> e.g. possible to attach/dettach a database.
> Any idea whats wrong?|||Hi Roger,
thank you very much. I missed the ".\sqlexpress". Adding this to the
connection string everything worked.
"Roger Wolter[MSFT]" wrote:

> Are you in fact trying to connect remotely? If you are, you will need to
> enable and start SQLBrowser also. If not, are you using .\sqlexpress as
> your server name in the connection string?
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Robert" <Robert@.discussions.microsoft.com> wrote in message
> news:B34E3E09-A80B-43C8-B164-4D4B299C10BF@.microsoft.com...
>
>

Cant Connect

I have installed SQL 2005 and just done a normal install. I have opened
Server Management Studio and try and connect but I get the error;
...this failure may be caused buy the face that under the default settings
SQL server does not allow remote connections (provider: TCP Provider, error:
0 - No connection could be made because the target machine actively refused
it) (Microsoft SQL Server, error 10061)
Now this error only happens when connecting to the DB engine, it works fine
connecting to analysis services. I have chosen Windows Auth and also
specifying my sql account with the password with is a member of the SQL
groups in the users container but still doesn't work. I am logged in as
Administrator but I get this error.
I have installed SQL before and it worked fine, then it messed up so I
installed SQLExpress now I installed 2005 beta again to play some more and
its done this.
I am using server 2003 SP1
Thanks for your help
ChrisFIXED :D
I just needed to manually create the MSSQL ODBC connector and its fine
learn something new everyday
"kicken18" <chrisflyer@.blueyonder.co.uk> wrote in message
news:ytiQf.138242$DM.34380@.fe3.news.blueyonder.co.uk...
>I have installed SQL 2005 and just done a normal install. I have opened
>Server Management Studio and try and connect but I get the error;
> ...this failure may be caused buy the face that under the default settings
> SQL server does not allow remote connections (provider: TCP Provider,
> error: 0 - No connection could be made because the target machine actively
> refused it) (Microsoft SQL Server, error 10061)
> Now this error only happens when connecting to the DB engine, it works
> fine connecting to analysis services. I have chosen Windows Auth and also
> specifying my sql account with the password with is a member of the SQL
> groups in the users container but still doesn't work. I am logged in as
> Administrator but I get this error.
> I have installed SQL before and it worked fine, then it messed up so I
> installed SQLExpress now I installed 2005 beta again to play some more and
> its done this.
> I am using server 2003 SP1
> Thanks for your help
> Chris
>|||Going on from this however, if i wanted a desktop machine to connect, say,
Microsoft Access to my SQL database, do i need to create a MSSQL client
connection in the desktop ODBC?
Thanks
Chris
"kicken18" <chrisflyer@.blueyonder.co.uk> wrote in message
news:zsjQf.138255$DM.65219@.fe3.news.blueyonder.co.uk...
> FIXED :D
> I just needed to manually create the MSSQL ODBC connector and its fine
> learn something new everyday
> "kicken18" <chrisflyer@.blueyonder.co.uk> wrote in message
> news:ytiQf.138242$DM.34380@.fe3.news.blueyonder.co.uk...
>|||> Going on from this however, if i wanted a desktop machine to connect,
> say, Microsoft Access to my SQL database, do i need to create a MSSQL
> client connection in the desktop ODBC?
This is one of two possible choices.
The other one is to create an ADP and use OLE DB provider.
PBsoft di Gabriele Bertolucci
www.pbsoft.it
skype: pbsoftsolution|||sorry to sound dumb, but could you dumb that down a bit please lol
thanks
chris
"Gabriele Bertolucci" <info@.REMOVEpbsoft.it> wrote in message
news:875ea355bbff8c8132b72f2d7d6@.news.virgilio.it...
> This is one of two possible choices.
> The other one is to create an ADP and use OLE DB provider.
> --
> PBsoft di Gabriele Bertolucci
> www.pbsoft.it
> skype: pbsoftsolution
>|||> sorry to sound dumb, but could you dumb that down a bit please lol
Sorry for my poor english, but I was not able to welle translate your senten
ce.
May you explain better, please?
PBsoft di Gabriele Bertolucci
www.pbsoft.it
skype: pbsoftsolution|||Can you explain what you mean by
"The other one is to create an ADP and use OLE DB provider."
I dont know what it is, also, would it be better to do it your way or my
way?
Thanks
Chris
"Gabriele Bertolucci" <info@.REMOVEpbsoft.it> wrote in message
news:875ea355bc088c813301ae47a36@.news.virgilio.it...
> Sorry for my poor english, but I was not able to welle translate your
> sentence. May you explain better, please?
> --
> PBsoft di Gabriele Bertolucci
> www.pbsoft.it
> skype: pbsoftsolution
>|||> 2) ODBC driver
> 2) this method lets you use Access as simply as with any other MDB.
> Indeed, you have to define a system DSN in Windows Data Source, then
> you create an MDB and link tables from the ODBC source you defined.
> Yet, you are not able to exploit stored procedures, views, functions,
> and so on.
I forgot to say that using ODBC driver you cannot see relationships too.
PBsoft di Gabriele Bertolucci
www.pbsoft.it
skype: pbsoftsolution|||Ah yes I do remember now, I think I have tried to use these befor.
Thanks for your assistance
Chris
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:hr2612lvbhhr1teiojvhb7aba44nb3huoe@.
4ax.com...
> ADP is an Access Data Project - an Access front end that
> uses SQL Server as the backend and doesn't involve Jet or
> mdb files. You can find more information on this in the
> Access help files - look for Access Project topics.
> -Sue
> On Sat, 11 Mar 2006 15:16:14 GMT, "kicken18"
> <chrisflyer@.blueyonder.co.uk> wrote:
>
>|||Thank you for the good help there, I can now go and test this.
Thank you for your time
Chris
"Gabriele Bertolucci" <info@.REMOVEpbsoft.it> wrote in message
news:875ea355bc418c813581ba41986@.news.virgilio.it...
> From Access you have two possibilities to use a MS SQL database.
> 1) OLE DB provider
> 2) ODBC driver
> 1) this is the best choice, in conjuntion to an Access Data Project.
> Microsoft created ADPs in order to interface SQL Server databases by
> Access via OLE DB provider and Jet Data Provider. ADPs connect to a SQL
> instance and let you see tables, stored procedures, views, functions, and
> so on.
> 2) this method lets you use Access as simply as with any other MDB.
> Indeed, you have to define a system DSN in Windows Data Source, then you
> create an MDB and link tables from the ODBC source you defined. Yet, you
> are not able to exploit stored procedures, views, functions, and so on.
> I suggest you to use the first method.
> Bye.
> --
> PBsoft di Gabriele Bertolucci
> www.pbsoft.it
> skype: pbsoftsolution
>sql

Cant Connect

I have installed SQL 2005 and just done a normal install. I have opened
Server Management Studio and try and connect but I get the error;
...this failure may be caused buy the face that under the default settings
SQL server does not allow remote connections (provider: TCP Provider, error:
0 - No connection could be made because the target machine actively refused
it) (Microsoft SQL Server, error 10061)
Now this error only happens when connecting to the DB engine, it works fine
connecting to analysis services. I have chosen Windows Auth and also
specifying my sql account with the password with is a member of the SQL
groups in the users container but still doesn't work. I am logged in as
Administrator but I get this error.
I have installed SQL before and it worked fine, then it messed up so I
installed SQLExpress now I installed 2005 beta again to play some more and
its done this.
I am using server 2003 SP1
Thanks for your help
Chris
FIXED :D
I just needed to manually create the MSSQL ODBC connector and its fine
learn something new everyday
"kicken18" <chrisflyer@.blueyonder.co.uk> wrote in message
news:ytiQf.138242$DM.34380@.fe3.news.blueyonder.co. uk...
>I have installed SQL 2005 and just done a normal install. I have opened
>Server Management Studio and try and connect but I get the error;
> ...this failure may be caused buy the face that under the default settings
> SQL server does not allow remote connections (provider: TCP Provider,
> error: 0 - No connection could be made because the target machine actively
> refused it) (Microsoft SQL Server, error 10061)
> Now this error only happens when connecting to the DB engine, it works
> fine connecting to analysis services. I have chosen Windows Auth and also
> specifying my sql account with the password with is a member of the SQL
> groups in the users container but still doesn't work. I am logged in as
> Administrator but I get this error.
> I have installed SQL before and it worked fine, then it messed up so I
> installed SQLExpress now I installed 2005 beta again to play some more and
> its done this.
> I am using server 2003 SP1
> Thanks for your help
> Chris
>
|||Going on from this however, if i wanted a desktop machine to connect, say,
Microsoft Access to my SQL database, do i need to create a MSSQL client
connection in the desktop ODBC?
Thanks
Chris
"kicken18" <chrisflyer@.blueyonder.co.uk> wrote in message
news:zsjQf.138255$DM.65219@.fe3.news.blueyonder.co. uk...
> FIXED :D
> I just needed to manually create the MSSQL ODBC connector and its fine
> learn something new everyday
> "kicken18" <chrisflyer@.blueyonder.co.uk> wrote in message
> news:ytiQf.138242$DM.34380@.fe3.news.blueyonder.co. uk...
>
|||> Going on from this however, if i wanted a desktop machine to connect,
> say, Microsoft Access to my SQL database, do i need to create a MSSQL
> client connection in the desktop ODBC?
This is one of two possible choices.
The other one is to create an ADP and use OLE DB provider.
PBsoft di Gabriele Bertolucci
www.pbsoft.it
skype: pbsoftsolution
|||sorry to sound dumb, but could you dumb that down a bit please lol
thanks
chris
"Gabriele Bertolucci" <info@.REMOVEpbsoft.it> wrote in message
news:875ea355bbff8c8132b72f2d7d6@.news.virgilio.it. ..
> This is one of two possible choices.
> The other one is to create an ADP and use OLE DB provider.
> --
> PBsoft di Gabriele Bertolucci
> www.pbsoft.it
> skype: pbsoftsolution
>
|||> sorry to sound dumb, but could you dumb that down a bit please lol
Sorry for my poor english, but I was not able to welle translate your sentence.
May you explain better, please?
PBsoft di Gabriele Bertolucci
www.pbsoft.it
skype: pbsoftsolution
|||Can you explain what you mean by
"The other one is to create an ADP and use OLE DB provider."
I dont know what it is, also, would it be better to do it your way or my
way?
Thanks
Chris
"Gabriele Bertolucci" <info@.REMOVEpbsoft.it> wrote in message
news:875ea355bc088c813301ae47a36@.news.virgilio.it. ..
> Sorry for my poor english, but I was not able to welle translate your
> sentence. May you explain better, please?
> --
> PBsoft di Gabriele Bertolucci
> www.pbsoft.it
> skype: pbsoftsolution
>
|||ADP is an Access Data Project - an Access front end that
uses SQL Server as the backend and doesn't involve Jet or
mdb files. You can find more information on this in the
Access help files - look for Access Project topics.
-Sue
On Sat, 11 Mar 2006 15:16:14 GMT, "kicken18"
<chrisflyer@.blueyonder.co.uk> wrote:

>Can you explain what you mean by
>"The other one is to create an ADP and use OLE DB provider."
>I dont know what it is, also, would it be better to do it your way or my
>way?
>Thanks
>Chris
>"Gabriele Bertolucci" <info@.REMOVEpbsoft.it> wrote in message
>news:875ea355bc088c813301ae47a36@.news.virgilio.it ...
>
|||Ah yes I do remember now, I think I have tried to use these befor.
Thanks for your assistance
Chris
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:hr2612lvbhhr1teiojvhb7aba44nb3huoe@.4ax.com...
> ADP is an Access Data Project - an Access front end that
> uses SQL Server as the backend and doesn't involve Jet or
> mdb files. You can find more information on this in the
> Access help files - look for Access Project topics.
> -Sue
> On Sat, 11 Mar 2006 15:16:14 GMT, "kicken18"
> <chrisflyer@.blueyonder.co.uk> wrote:
>
|||Thank you for the good help there, I can now go and test this.
Thank you for your time
Chris
"Gabriele Bertolucci" <info@.REMOVEpbsoft.it> wrote in message
news:875ea355bc418c813581ba41986@.news.virgilio.it. ..
> From Access you have two possibilities to use a MS SQL database.
> 1) OLE DB provider
> 2) ODBC driver
> 1) this is the best choice, in conjuntion to an Access Data Project.
> Microsoft created ADPs in order to interface SQL Server databases by
> Access via OLE DB provider and Jet Data Provider. ADPs connect to a SQL
> instance and let you see tables, stored procedures, views, functions, and
> so on.
> 2) this method lets you use Access as simply as with any other MDB.
> Indeed, you have to define a system DSN in Windows Data Source, then you
> create an MDB and link tables from the ODBC source you defined. Yet, you
> are not able to exploit stored procedures, views, functions, and so on.
> I suggest you to use the first method.
> Bye.
> --
> PBsoft di Gabriele Bertolucci
> www.pbsoft.it
> skype: pbsoftsolution
>

Can't attach to database

Hi,

I have a database that I developed using both Toad for SQL and SQL Server Managment Studio.

All was working fine. I could connect to the database with one of the above and also run two an applications I developed (one in C# and One in VB.NET using VS Express) using the standard SQLConnection class.

the following connection string worked fine...

Server="(local)"; Trusted_Connection="yes"; Database="CDEvolution";

Now, for one reason or another I decided to create a new data source in my Visual Studio project and pointed it to the database fine.

At first it seemed ok as I could see all tables from teh database. However somethign strage has happened. I now can't access the database in TOAD or SQL Server Managment Studio. I also couldn't connect using the above string.

I finally managed to get the two appllications I developed to access database using the following connection string...

Data Source=.\SQLEXPRESS;AttachDbFilename=C:\Program Files\Microsoft SQL Server\MSSQL\Data\CDEvolution.mdf;Integrated Security=True;Connect Timeout=6000;User Instance=True;

and the applications work fine, however I can access the database using the DB tools.

In SQL Server Managment Studio I remove the database and tried to attach it again but I keep getting the following error message...

Could not find row in sysindexes for database ID 5, object ID 1, index ID 1. Run DBCC CHECKTABLE on sysindexes.
Could not open new database 'C:\PROGRAM FILES\MICROSOFT SQL SERVER\MSSQL\DATA\CDEVOLUTION.MDF'. CREATE DATABASE is aborted. (.Net SqlClient Data Provider)

Any ideas on how I can get access back?

Cheers in advance,

Kevin

The latter error looks similar to what you get if you try to attach a SQL 2005 database to a SQL 2000 instance. SQL 2000 will not work with databases that have been upgraded to SQL 2005.|||

Hi,

Thanks for the response. before all this happened I was connecting to the database using SQL Manager Studio with no problems. This all started when I created a data source connection to the database in Visual Studio Express. After that I needed to change the connection string if I wanted to connect at run time using SQLConnection and have still not been able to connect using any of the DB managment tools.

Cheers,

Kevin

|||

This error is from SQL 2000, not SQL 2005, and incidates you are trying to attach a SQL 2005 database to SQL 2000.

Could not find row in sysindexes for database ID 5, object ID 1, index ID 1. Run DBCC CHECKTABLE on sysindexes.
Could not open new database 'C:\PROGRAM FILES\MICROSOFT SQL SERVER\MSSQL\DATA\CDEVOLUTION.MDF'. CREATE DATABASE is aborted. (.Net SqlClient Data Provider)

When you attached the databaes to Visual Studio Express, it would have been upgraded to SQL 2005 format and can no longer be used by SQL 2000.

|||

Thanks,

I was under the impression that SQL Express was 2005, I will look into it further and see what I can find.

Cheers,

Kevin.

|||

Sorted!

It seems that another instance of the SQL server has been created called SQLEXPRESS and you have the option to connect to it when the application starts.

Once I connected It created a new folder called MSSQL.1 (MSSQL already exists) so I simply coppied the database files into the new folder and attached them. So now I should be able to change to application to connect at the new location and I should be good to go.

Cheers,

YNWA

Kevin.

Can't Attach sqlexpress db

Hi,

After having published the timetracker starterkit from visual studio 2005 to local wwwroot,

I try to access my homepage with ie.

But still get the same error message :

An attempt to attach an auto-named database for file C:\Documents and Settings\Emmanuel\My Documents\Visual Studio 2005\WebSites\GestWares\App_Data\TimeTracker.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.

This is how i configure my web.config :

<connectionStrings>

<remove name="LocalSqlServer"/>

<add name="LocalSqlServer" connectionString="Data Source=.\SQLExpress;Integrated Security=True;AttachDBFilename=|DataDirectory|\TimeTracker.mdf;User Instance=true"/>

<add name="aspnet_staterKits_TimeTracker" connectionString="Data Source=.\SQLExpress;Integrated Security=True;AttachDBFilename=|DataDirectory|\TimeTracker.mdf;User Instance=true"/>

<add name="ConnectionString" connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\TimeTracker.mdf;Integrated Security=True;User Instance=True" providerName="System.Data.SqlClient"/>

</connectionStrings>

Has someone any idea how my connectionstrings statement has to look like?

thanks in advance.

Manu.

Hi,

Refer below links for work around.

http://www.aspspider.com/resources/Resource170.aspx

http://www.sqljunkies.com/WebLog/ktegels/archive/2005/11/15/17401.aspx

http://www.ozzu.com/ftopic43909.html

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=989092&SiteID=1

Hemantgiri S. Goswami

Can't Attach Database using SQL Server Management Studio Express

I am having a problem Attaching, well actually not being able to see a database when attempting to attach it. I suspect this is more of a security issue rather than a problem with Management Studio, but I can't figure out what is happening.

If I copy a database to Documents and Settings\All Users\... and attempt to attach I can see the file in the selection tree. This also is the case if I copy it to Documents and Settings\Default User\... But if I copy it to Documents and Settings\ADynarski\... which is the account I normally log into, when I expand the folder in the selection tree, nothing is visible. And the same thing occurs if I copy the file to Documents and Settings\Guest\...

I've looked at the security settings and everything appears to be normal. This is on a box with XP Home and SQL Server Express. Can anyone tell me what I'm missing?

Thanks,

Al

What is the account your SQL Server service running under?

If it's domain account, make sure the account has access to the folder you are trying attach database from.

|||Thanks for your input. It is a domain account and the account does have access to the folder. What is really strange is that I used Visual Web Developer Express to create the database in C:\Documents and Settings\Al Dynarski\My Documents\... and it functions properly. But logged into the same account, Server Management Studio sees nothing in the folder C:\Documents and Settings\Al Dynarski or below. I can copy the database out to another folder and then use Server Manangement Studio to work on it. Very strange. I'll continue to look around. Thanks again.|||

Why are you copying the database files to a user folder rather than a common system folder ? If you want to attach the database files not via the userinstance feature, the SQL Server Service need to have access to the specified file for the database, so make sure that the service the SQL Server Account is running on, has access to this file destination.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||Thanks for your suggestion. I don't want to have to copy it; I only tried that to be sure it was in fact a valid database. And I agree with your assessment about SQL service having access rights to the folder containing the database. My problem appears to be figuring out why it doesn't Thanks again.|||

I got it working. I switched SQL Server Express to Local System Login and I now can see the database files and attach them. Since this server instance is just for my local testing, this configuration should work for me. Thanks to all for your suggestions.

Al

|||

Hi Al,

I am having the same problem.... how do you switch SQL Server Express to Local System Login, and in doing so what else does this affect?

Thanks,

Claude.

|||

Go to the SCM (Service Control Manager) of Windows, sleect the service you want to change the logon settings for, right click properties, go to the LogOn Tab and change the account to "Local System". Keep in min d that the service needs a restart after changing the settings.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

Hi Claude,

The solution Jens indicated is exactly what I did.

Good Luck!

Al

cant add sql endpoint to my visual studio project. trying "add as web reference" does

i have created a database endpoint that just retuns some data. i am trying to call this endpoint as a web service in visual studio by adding a web reference, but i cannot find my endpoint. it seems to just check iis for endpoints, but how do i make it look for my sql endpoint? here is the code for my endpoint.

create endpoint testEndpoint authorization [FINTAN-PC\Fintan]
state=STARTED
as http
(
path ='/sql',
authentication=(INTEGRATED),
ports = (CLEAR),
site='SERVER'
)
For SOAP
(
webmethod'ProvideSQLData'(name='adventureWorks.dbo.testEndpointProcedure'),
WSDL=DEFAULT,
SCHEMA=STANDARD,
DATABASE='adventureworks',
NAMESPACE='http://thenamespace.org'
);
GO

the account that visual studio is running under has been granted connect permissions on the endpoint. can anyone say where im going wrong here?

I'm a little unclear on your mentioning of using Visual Studio to look for this SOAP endpoint. Are you referring to using UDDI?

Regarding "add as web reference" in Visual Studio, the method that has worked best for me is to type in the HTTP URL that points to the WSDL document.

In this scenario it will be: http://SERVER/sql?wsdl

This URL comes from:

site='SERVER'

path='/sql'

So, if the endpoint was configured with:

site='foobar'

path='/myOwnPath/subPath'

then the WSDL document URL will be http://foobar/myOwnPath/subPath?wsdl

One easy way to ensure the user account running Visual Studio has access to retrieve the WSDL document is to use a Web Browser (such as IE) and point to the WSDL document URL.

HTH,

Jimmy|||ok, tiny bit of progress made. when i use the http://sitename/path?wsdl , rather than getting a 404 error, i get a page cannot be displayed. this is in IE7. any ideas?

cant add sql endpoint to my visual studio project. trying "add as web reference" does

i have created a database endpoint that just retuns some data. i am trying to call this endpoint as a web service in visual studio by adding a web reference, but i cannot find my endpoint. it seems to just check iis for endpoints, but how do i make it look for my sql endpoint? here is the code for my endpoint.

create endpoint testEndpoint authorization [FINTAN-PC\Fintan]
state=STARTED
as http
(
path ='/sql',
authentication=(INTEGRATED),
ports = (CLEAR),
site='SERVER'
)
For SOAP
(
webmethod'ProvideSQLData'(name='adventureWorks.dbo.testEndpointProcedure'),
WSDL=DEFAULT,
SCHEMA=STANDARD,
DATABASE='adventureworks',
NAMESPACE='http://thenamespace.org'
);
GO

the account that visual studio is running under has been granted connect permissions on the endpoint. can anyone say where im going wrong here?

I'm a little unclear on your mentioning of using Visual Studio to look for this SOAP endpoint. Are you referring to using UDDI?

Regarding "add as web reference" in Visual Studio, the method that has worked best for me is to type in the HTTP URL that points to the WSDL document.

In this scenario it will be: http://SERVER/sql?wsdl

This URL comes from:

site='SERVER'

path='/sql'

So, if the endpoint was configured with:

site='foobar'

path='/myOwnPath/subPath'

then the WSDL document URL will be http://foobar/myOwnPath/subPath?wsdl

One easy way to ensure the user account running Visual Studio has access to retrieve the WSDL document is to use a Web Browser (such as IE) and point to the WSDL document URL.

HTH,

Jimmy|||ok, tiny bit of progress made. when i use the http://sitename/path?wsdl , rather than getting a 404 error, i get a page cannot be displayed. this is in IE7. any ideas?

Can't Add Reference to Microsoft.SQLServer.RMO.dll

Hi All,
I'm trying to add a reference to this DLL in Visual Studio 2003 so I
can programmatically trigger replication. When I try and add the
reference I get the following exception:
"A reference to 'C:\Program Files\Microsoft SQL Server\90\SDK
\Assemblies\Microsoft.SqlServer.Rmo.dll' could not be added. This is
not a valid assembly or COM component. Only assemblies with extension
'dll' and COM components can be referenced. Please make sure that the
file is accessible, and that it is a valid assembly or COM component."
As you can see it does have a .dll extension.
The file I try to reference indicates it was created on 14 October
2005, 03:43:34 and is version 9.0.1399.0
C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies
\Microsoft.SqlServer.Rmo.dll
Can I doenload another version of the DLL from somewhere?
Any help appreciated!
Thanks
Rajl
On 13 Jul, 13:16, rajpate...@.hotmail.com wrote:
> Hi All,
> I'm trying to add a reference to this DLL in Visual Studio 2003 so I
> can programmatically trigger replication. When I try and add the
> reference I get the following exception:
> "A reference to 'C:\Program Files\Microsoft SQL Server\90\SDK
> \Assemblies\Microsoft.SqlServer.Rmo.dll' could not be added. This is
> not a valid assembly or COM component. Only assemblies with extension
> 'dll' and COM components can be referenced. Please make sure that the
> file is accessible, and that it is a valid assembly or COM component."
> As you can see it does have a .dll extension.
> The file I try to reference indicates it was created on 14 October
> 2005, 03:43:34 and is version 9.0.1399.0
> C:\Program Files\Microsoft SQL Server\90\SDK\Assemblies
> \Microsoft.SqlServer.Rmo.dll
> Can I doenload another version of the DLL from somewhere?
> Any help appreciated!
> Thanks
> Rajl
Also got a newer version of the file version 9.0.242.0, created 10th
Feb 2007 but that has the same problem
|||On 13 Jul, 16:22, rajpate...@.hotmail.com wrote:
> On 13 Jul, 13:16, rajpate...@.hotmail.com wrote:
>
>
>
>
>
>
>
> Also got a newer version of the file version 9.0.242.0, created 10th
> Feb 2007 but that has the same problem- Hide quoted text -
> - Show quoted text -
OK, this is resolved now. I think the issue is to do with the fact I'm
using VS2003. I tried adding the reference to a VS2005 project and
that works fine. I'm guessing that the dll is a .NET 2.0 dll and so
not compatible against VS2003?
|||If you want to programmatically start replication, you probably will also
need to add a reference to the "Replication Agent Library" assembly.
For more information, see
http://msdn2.microsoft.com/de-de/library/ms146869.aspx.
Cheers!
Glenn Gailey
SQL Server User Education
This posting is provided "AS IS" with no warranties, and confers no rights.
"rajpatel50@.hotmail.com" wrote:

> On 13 Jul, 16:22, rajpate...@.hotmail.com wrote:
> OK, this is resolved now. I think the issue is to do with the fact I'm
> using VS2003. I tried adding the reference to a VS2005 project and
> that works fine. I'm guessing that the dll is a .NET 2.0 dll and so
> not compatible against VS2003?
>

Can't Add New Report

In Visual Studio when I create a new Report Project, once it's created I go
into Solution Explorer, right click on the "Reports" folder and select "Add
New Report", and I get the following error:
Exception from HRESULT: 0x8013141A
I've re-installed Visual Studio, the .NET framework, and Reporting Services,
and after all that it still gives me the error.
Any suggestions?
Michael BodnarSome DLL is failing to load. The only sure way to diagnose the problem is
to attach a debugger and see what exceptions it's throwing.
--
Bruce Johnson [MSFT]
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Michael Bodnar" <blah@.blah.com> wrote in message
news:eX63pJHWEHA.4064@.TK2MSFTNGP11.phx.gbl...
> In Visual Studio when I create a new Report Project, once it's created I
go
> into Solution Explorer, right click on the "Reports" folder and select
"Add
> New Report", and I get the following error:
> Exception from HRESULT: 0x8013141A
> I've re-installed Visual Studio, the .NET framework, and Reporting
Services,
> and after all that it still gives me the error.
> Any suggestions?
> Michael Bodnar
>|||Can you dump out a list of DLLs that are loaded into the VS process when the
error occurs? You can either use a tool like procexp.exe
(http://www.sysinternals.com/ntw2k/freeware/procexp.shtml) or attach another
instance of VS as a debugger. Using VS, display the Modules window, select
all rows, copy, and paste into a text file.
--
Albert Yen
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Michael Bodnar" <blah@.blah.com> wrote in message
news:eX63pJHWEHA.4064@.TK2MSFTNGP11.phx.gbl...
> In Visual Studio when I create a new Report Project, once it's created I
go
> into Solution Explorer, right click on the "Reports" folder and select
"Add
> New Report", and I get the following error:
> Exception from HRESULT: 0x8013141A
> I've re-installed Visual Studio, the .NET framework, and Reporting
Services,
> and after all that it still gives me the error.
> Any suggestions?
> Michael Bodnar
>|||The whole problem was I was trying to install it off a network drive. It
must not have been seeing some files over the network or something, or maybe
some files got corrupt. I installed it with the CD and it works fine now.
"Michael Bodnar" <blah@.blah.com> wrote in message
news:eX63pJHWEHA.4064@.TK2MSFTNGP11.phx.gbl...
> In Visual Studio when I create a new Report Project, once it's created I
go
> into Solution Explorer, right click on the "Reports" folder and select
"Add
> New Report", and I get the following error:
> Exception from HRESULT: 0x8013141A
> I've re-installed Visual Studio, the .NET framework, and Reporting
Services,
> and after all that it still gives me the error.
> Any suggestions?
> Michael Bodnar
>

Can't add DataSource or connect to database with Wizard

Hi,

I installed Visual Studio 2005 Beta 2 and could connect with it to my SQL 2000 Server. Now I installed on the same laptop SQL Server 2005, but the installation failed on some error. Now I uninstalled SQL Server 2005, but now I can't connect anymore to any datasource. The "Add new Data Source" is just not highlited and the Wizard from Tools Menu "Connect to Database" does not launch at all.

Any one has a solution?

thanks,
ImmanuelThe solution was to repair the Visual Studio 2005 installation.

Can't access Reporting with Management Studio

Bonjour!
I can't have access with my management studio to Reporting services
(2005)installed on my web server. (Cannot connect to...)Do my developpers
needs special rights?
Regards, Joel :)What do you mean access? You should be able to design reports without any
access to RS. It is only when deploying that you need special rights. Either
they need to be part of the local administrators group on the server where
RS is running OR they need to be put into the appropriate role (read up on
roles for Reporting Services).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Joel" <Joel@.discussions.microsoft.com> wrote in message
news:598AD496-F255-4AB9-9DFD-DEE860D45F6F@.microsoft.com...
> Bonjour!
> I can't have access with my management studio to Reporting services
> (2005)installed on my web server. (Cannot connect to...)Do my developpers
> needs special rights?
> Regards, Joel :)|||Did you check SQL Server Configuration Manager to see if the Reporting
Services service is started? It could also be a rights issue. Do you have
sysadmin rights on your MSSQL server?
--
Alain Quesnel
alainsansspam@.logiquel.com
www.logiquel.com
"Joel" <Joel@.discussions.microsoft.com> wrote in message
news:598AD496-F255-4AB9-9DFD-DEE860D45F6F@.microsoft.com...
> Bonjour!
> I can't have access with my management studio to Reporting services
> (2005)installed on my web server. (Cannot connect to...)Do my developpers
> needs special rights?
> Regards, Joel :)|||Whoa! To deploy a report to RS does not need sysadmin rights. There is no
way that developers should have sysadmin rights on SQL server. RS does
everything based on its roles.
The local administrators role on the server (server not SQL Server)
automatically puts all users in that role with the rights to do anything
(subscriptions, deploy reports etc) to Reporting Services. However,
individual users or groups can be added to roles.
In Report Manager, be at Home. Click on the Properties tab, Click New Role
Assignments. Try Content Manager or Publisher. One of those roles will work.
All other folders inherit from home.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Alain Quesnel" <alainsansspam@.logiquel.com> wrote in message
news:uAqaWJKHIHA.4228@.TK2MSFTNGP02.phx.gbl...
> Did you check SQL Server Configuration Manager to see if the Reporting
> Services service is started? It could also be a rights issue. Do you have
> sysadmin rights on your MSSQL server?
> --
> Alain Quesnel
> alainsansspam@.logiquel.com
> www.logiquel.com
>
> "Joel" <Joel@.discussions.microsoft.com> wrote in message
> news:598AD496-F255-4AB9-9DFD-DEE860D45F6F@.microsoft.com...
>> Bonjour!
>> I can't have access with my management studio to Reporting services
>> (2005)installed on my web server. (Cannot connect to...)Do my developpers
>> needs special rights?
>> Regards, Joel :)
>|||Thanks Guys, when we are with the browser on Reports Server, they can deploy
and access it, I made a special role for them, but with management studio we
cannot connect to it at all.
Joel:)
"Bruce L-C [MVP]" wrote:
> Whoa! To deploy a report to RS does not need sysadmin rights. There is no
> way that developers should have sysadmin rights on SQL server. RS does
> everything based on its roles.
> The local administrators role on the server (server not SQL Server)
> automatically puts all users in that role with the rights to do anything
> (subscriptions, deploy reports etc) to Reporting Services. However,
> individual users or groups can be added to roles.
> In Report Manager, be at Home. Click on the Properties tab, Click New Role
> Assignments. Try Content Manager or Publisher. One of those roles will work.
> All other folders inherit from home.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Alain Quesnel" <alainsansspam@.logiquel.com> wrote in message
> news:uAqaWJKHIHA.4228@.TK2MSFTNGP02.phx.gbl...
> > Did you check SQL Server Configuration Manager to see if the Reporting
> > Services service is started? It could also be a rights issue. Do you have
> > sysadmin rights on your MSSQL server?
> >
> > --
> >
> > Alain Quesnel
> > alainsansspam@.logiquel.com
> >
> > www.logiquel.com
> >
> >
> > "Joel" <Joel@.discussions.microsoft.com> wrote in message
> > news:598AD496-F255-4AB9-9DFD-DEE860D45F6F@.microsoft.com...
> >> Bonjour!
> >>
> >> I can't have access with my management studio to Reporting services
> >> (2005)installed on my web server. (Cannot connect to...)Do my developpers
> >> needs special rights?
> >>
> >> Regards, Joel :)
> >
>
>|||Have you specified the path to deploy to? Right mouse click on the project
in BI Studio/VS. You need to set the target server URL to something like
this:
http://yourserver/ReportServer
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Joel" <Joel@.discussions.microsoft.com> wrote in message
news:BD19004F-06AF-48FD-8592-2B8AB74A2BF0@.microsoft.com...
> Thanks Guys, when we are with the browser on Reports Server, they can
> deploy
> and access it, I made a special role for them, but with management studio
> we
> cannot connect to it at all.
> Joel:)
> "Bruce L-C [MVP]" wrote:
>> Whoa! To deploy a report to RS does not need sysadmin rights. There is no
>> way that developers should have sysadmin rights on SQL server. RS does
>> everything based on its roles.
>> The local administrators role on the server (server not SQL Server)
>> automatically puts all users in that role with the rights to do anything
>> (subscriptions, deploy reports etc) to Reporting Services. However,
>> individual users or groups can be added to roles.
>> In Report Manager, be at Home. Click on the Properties tab, Click New
>> Role
>> Assignments. Try Content Manager or Publisher. One of those roles will
>> work.
>> All other folders inherit from home.
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "Alain Quesnel" <alainsansspam@.logiquel.com> wrote in message
>> news:uAqaWJKHIHA.4228@.TK2MSFTNGP02.phx.gbl...
>> > Did you check SQL Server Configuration Manager to see if the Reporting
>> > Services service is started? It could also be a rights issue. Do you
>> > have
>> > sysadmin rights on your MSSQL server?
>> >
>> > --
>> >
>> > Alain Quesnel
>> > alainsansspam@.logiquel.com
>> >
>> > www.logiquel.com
>> >
>> >
>> > "Joel" <Joel@.discussions.microsoft.com> wrote in message
>> > news:598AD496-F255-4AB9-9DFD-DEE860D45F6F@.microsoft.com...
>> >> Bonjour!
>> >>
>> >> I can't have access with my management studio to Reporting services
>> >> (2005)installed on my web server. (Cannot connect to...)Do my
>> >> developpers
>> >> needs special rights?
>> >>
>> >> Regards, Joel :)
>> >
>>|||Yes that's what I do. My little issue here is not in Visual Studio, it is
when I try to connect to report server with MS SQL Server management studio,
on my test server that I have, everything on one box, it is connecting but
with my prod it doesn't. My prod is different, the Reporting is installed on
a web server with the database on another server.
Regards, Joel :)
"Bruce L-C [MVP]" wrote:
> Have you specified the path to deploy to? Right mouse click on the project
> in BI Studio/VS. You need to set the target server URL to something like
> this:
> http://yourserver/ReportServer
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Joel" <Joel@.discussions.microsoft.com> wrote in message
> news:BD19004F-06AF-48FD-8592-2B8AB74A2BF0@.microsoft.com...
> > Thanks Guys, when we are with the browser on Reports Server, they can
> > deploy
> > and access it, I made a special role for them, but with management studio
> > we
> > cannot connect to it at all.
> >
> > Joel:)
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Whoa! To deploy a report to RS does not need sysadmin rights. There is no
> >> way that developers should have sysadmin rights on SQL server. RS does
> >> everything based on its roles.
> >>
> >> The local administrators role on the server (server not SQL Server)
> >> automatically puts all users in that role with the rights to do anything
> >> (subscriptions, deploy reports etc) to Reporting Services. However,
> >> individual users or groups can be added to roles.
> >>
> >> In Report Manager, be at Home. Click on the Properties tab, Click New
> >> Role
> >> Assignments. Try Content Manager or Publisher. One of those roles will
> >> work.
> >>
> >> All other folders inherit from home.
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >>
> >>
> >> "Alain Quesnel" <alainsansspam@.logiquel.com> wrote in message
> >> news:uAqaWJKHIHA.4228@.TK2MSFTNGP02.phx.gbl...
> >> > Did you check SQL Server Configuration Manager to see if the Reporting
> >> > Services service is started? It could also be a rights issue. Do you
> >> > have
> >> > sysadmin rights on your MSSQL server?
> >> >
> >> > --
> >> >
> >> > Alain Quesnel
> >> > alainsansspam@.logiquel.com
> >> >
> >> > www.logiquel.com
> >> >
> >> >
> >> > "Joel" <Joel@.discussions.microsoft.com> wrote in message
> >> > news:598AD496-F255-4AB9-9DFD-DEE860D45F6F@.microsoft.com...
> >> >> Bonjour!
> >> >>
> >> >> I can't have access with my management studio to Reporting services
> >> >> (2005)installed on my web server. (Cannot connect to...)Do my
> >> >> developpers
> >> >> needs special rights?
> >> >>
> >> >> Regards, Joel :)
> >> >
> >>
> >>
> >>
>
>|||I'm sorry. You asked about the developers so I immediately thought the issue
was not being able to deploy. Hence the thrust of all my posts. I never use
Management studio for anything with RS. I pulled it up just to see what it
offers and it does very little. It shows you some things but Report Manager
can easily do everything and more than what you can do with Management
Studio.
The other poster mentioned sysadmin rights on SQL Server. I don't think this
is necessary because when I look at what information is provided and changes
allowed, it is all straight Reporting Services. If you want developers to be
doing this (adding roles for instance) then have them either be in the local
administrators account on the server that is hosting Reporting Services or
add their account to the System Administrator role.
I suggest first making sure the developers can do what they need to do with
Report Manager.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Joel" <Joel@.discussions.microsoft.com> wrote in message
news:AA154A4E-229A-4F8D-BCBA-8AC2391496A5@.microsoft.com...
> Yes that's what I do. My little issue here is not in Visual Studio, it is
> when I try to connect to report server with MS SQL Server management
> studio,
> on my test server that I have, everything on one box, it is connecting but
> with my prod it doesn't. My prod is different, the Reporting is installed
> on
> a web server with the database on another server.
> Regards, Joel :)
> "Bruce L-C [MVP]" wrote:
>> Have you specified the path to deploy to? Right mouse click on the
>> project
>> in BI Studio/VS. You need to set the target server URL to something like
>> this:
>> http://yourserver/ReportServer
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Joel" <Joel@.discussions.microsoft.com> wrote in message
>> news:BD19004F-06AF-48FD-8592-2B8AB74A2BF0@.microsoft.com...
>> > Thanks Guys, when we are with the browser on Reports Server, they can
>> > deploy
>> > and access it, I made a special role for them, but with management
>> > studio
>> > we
>> > cannot connect to it at all.
>> >
>> > Joel:)
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> Whoa! To deploy a report to RS does not need sysadmin rights. There is
>> >> no
>> >> way that developers should have sysadmin rights on SQL server. RS does
>> >> everything based on its roles.
>> >>
>> >> The local administrators role on the server (server not SQL Server)
>> >> automatically puts all users in that role with the rights to do
>> >> anything
>> >> (subscriptions, deploy reports etc) to Reporting Services. However,
>> >> individual users or groups can be added to roles.
>> >>
>> >> In Report Manager, be at Home. Click on the Properties tab, Click New
>> >> Role
>> >> Assignments. Try Content Manager or Publisher. One of those roles will
>> >> work.
>> >>
>> >> All other folders inherit from home.
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >>
>> >>
>> >> "Alain Quesnel" <alainsansspam@.logiquel.com> wrote in message
>> >> news:uAqaWJKHIHA.4228@.TK2MSFTNGP02.phx.gbl...
>> >> > Did you check SQL Server Configuration Manager to see if the
>> >> > Reporting
>> >> > Services service is started? It could also be a rights issue. Do you
>> >> > have
>> >> > sysadmin rights on your MSSQL server?
>> >> >
>> >> > --
>> >> >
>> >> > Alain Quesnel
>> >> > alainsansspam@.logiquel.com
>> >> >
>> >> > www.logiquel.com
>> >> >
>> >> >
>> >> > "Joel" <Joel@.discussions.microsoft.com> wrote in message
>> >> > news:598AD496-F255-4AB9-9DFD-DEE860D45F6F@.microsoft.com...
>> >> >> Bonjour!
>> >> >>
>> >> >> I can't have access with my management studio to Reporting services
>> >> >> (2005)installed on my web server. (Cannot connect to...)Do my
>> >> >> developpers
>> >> >> needs special rights?
>> >> >>
>> >> >> Regards, Joel :)
>> >> >
>> >>
>> >>
>> >>
>>|||Thanks, that's what I will do.
Regards, Joel :)
"Bruce L-C [MVP]" wrote:
> I'm sorry. You asked about the developers so I immediately thought the issue
> was not being able to deploy. Hence the thrust of all my posts. I never use
> Management studio for anything with RS. I pulled it up just to see what it
> offers and it does very little. It shows you some things but Report Manager
> can easily do everything and more than what you can do with Management
> Studio.
> The other poster mentioned sysadmin rights on SQL Server. I don't think this
> is necessary because when I look at what information is provided and changes
> allowed, it is all straight Reporting Services. If you want developers to be
> doing this (adding roles for instance) then have them either be in the local
> administrators account on the server that is hosting Reporting Services or
> add their account to the System Administrator role.
> I suggest first making sure the developers can do what they need to do with
> Report Manager.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Joel" <Joel@.discussions.microsoft.com> wrote in message
> news:AA154A4E-229A-4F8D-BCBA-8AC2391496A5@.microsoft.com...
> > Yes that's what I do. My little issue here is not in Visual Studio, it is
> > when I try to connect to report server with MS SQL Server management
> > studio,
> > on my test server that I have, everything on one box, it is connecting but
> > with my prod it doesn't. My prod is different, the Reporting is installed
> > on
> > a web server with the database on another server.
> >
> > Regards, Joel :)
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Have you specified the path to deploy to? Right mouse click on the
> >> project
> >> in BI Studio/VS. You need to set the target server URL to something like
> >> this:
> >> http://yourserver/ReportServer
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Joel" <Joel@.discussions.microsoft.com> wrote in message
> >> news:BD19004F-06AF-48FD-8592-2B8AB74A2BF0@.microsoft.com...
> >> > Thanks Guys, when we are with the browser on Reports Server, they can
> >> > deploy
> >> > and access it, I made a special role for them, but with management
> >> > studio
> >> > we
> >> > cannot connect to it at all.
> >> >
> >> > Joel:)
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> Whoa! To deploy a report to RS does not need sysadmin rights. There is
> >> >> no
> >> >> way that developers should have sysadmin rights on SQL server. RS does
> >> >> everything based on its roles.
> >> >>
> >> >> The local administrators role on the server (server not SQL Server)
> >> >> automatically puts all users in that role with the rights to do
> >> >> anything
> >> >> (subscriptions, deploy reports etc) to Reporting Services. However,
> >> >> individual users or groups can be added to roles.
> >> >>
> >> >> In Report Manager, be at Home. Click on the Properties tab, Click New
> >> >> Role
> >> >> Assignments. Try Content Manager or Publisher. One of those roles will
> >> >> work.
> >> >>
> >> >> All other folders inherit from home.
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >>
> >> >>
> >> >> "Alain Quesnel" <alainsansspam@.logiquel.com> wrote in message
> >> >> news:uAqaWJKHIHA.4228@.TK2MSFTNGP02.phx.gbl...
> >> >> > Did you check SQL Server Configuration Manager to see if the
> >> >> > Reporting
> >> >> > Services service is started? It could also be a rights issue. Do you
> >> >> > have
> >> >> > sysadmin rights on your MSSQL server?
> >> >> >
> >> >> > --
> >> >> >
> >> >> > Alain Quesnel
> >> >> > alainsansspam@.logiquel.com
> >> >> >
> >> >> > www.logiquel.com
> >> >> >
> >> >> >
> >> >> > "Joel" <Joel@.discussions.microsoft.com> wrote in message
> >> >> > news:598AD496-F255-4AB9-9DFD-DEE860D45F6F@.microsoft.com...
> >> >> >> Bonjour!
> >> >> >>
> >> >> >> I can't have access with my management studio to Reporting services
> >> >> >> (2005)installed on my web server. (Cannot connect to...)Do my
> >> >> >> developpers
> >> >> >> needs special rights?
> >> >> >>
> >> >> >> Regards, Joel :)
> >> >> >
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||I agree that developers shoudn't have sa rights. I just wanted to know if he
could access SSRS through Management Studio with such rights. I've had a
similar issue that had to do with renaming a machine that hosts SSRS. I
still can't make the SSRS webserver work with a new machine name.
Alain Quesnel
alainsansspam@.logiquel.com
www.logiquel.com
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:O1BeNPKHIHA.4228@.TK2MSFTNGP02.phx.gbl...
> Whoa! To deploy a report to RS does not need sysadmin rights. There is no
> way that developers should have sysadmin rights on SQL server. RS does
> everything based on its roles.
> The local administrators role on the server (server not SQL Server)
> automatically puts all users in that role with the rights to do anything
> (subscriptions, deploy reports etc) to Reporting Services. However,
> individual users or groups can be added to roles.
> In Report Manager, be at Home. Click on the Properties tab, Click New Role
> Assignments. Try Content Manager or Publisher. One of those roles will
> work.
> All other folders inherit from home.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Alain Quesnel" <alainsansspam@.logiquel.com> wrote in message
> news:uAqaWJKHIHA.4228@.TK2MSFTNGP02.phx.gbl...
>> Did you check SQL Server Configuration Manager to see if the Reporting
>> Services service is started? It could also be a rights issue. Do you have
>> sysadmin rights on your MSSQL server?
>> --
>> Alain Quesnel
>> alainsansspam@.logiquel.com
>> www.logiquel.com
>>
>> "Joel" <Joel@.discussions.microsoft.com> wrote in message
>> news:598AD496-F255-4AB9-9DFD-DEE860D45F6F@.microsoft.com...
>> Bonjour!
>> I can't have access with my management studio to Reporting services
>> (2005)installed on my web server. (Cannot connect to...)Do my
>> developpers
>> needs special rights?
>> Regards, Joel :)
>|||Accessing Reporting Services through SQL Server Management Studio DOES have
some good uses.
Mainly, you can organise reports much easier than in Report Manager, you can
also create the rdl from the report.
Having said that, I live with out it because I nearly always hit connection
problems on different sites and I'm not sure of the correct way to set it up.
Anyone got an idiots guide to setting the security up so that this facility
can be done. I have full administrator rights.
Thanks
Chris McGuigan
"Alain Quesnel" wrote:
> I agree that developers shoudn't have sa rights. I just wanted to know if he
> could access SSRS through Management Studio with such rights. I've had a
> similar issue that had to do with renaming a machine that hosts SSRS. I
> still can't make the SSRS webserver work with a new machine name.
>
> --
> Alain Quesnel
> alainsansspam@.logiquel.com
> www.logiquel.com
>
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:O1BeNPKHIHA.4228@.TK2MSFTNGP02.phx.gbl...
> > Whoa! To deploy a report to RS does not need sysadmin rights. There is no
> > way that developers should have sysadmin rights on SQL server. RS does
> > everything based on its roles.
> >
> > The local administrators role on the server (server not SQL Server)
> > automatically puts all users in that role with the rights to do anything
> > (subscriptions, deploy reports etc) to Reporting Services. However,
> > individual users or groups can be added to roles.
> >
> > In Report Manager, be at Home. Click on the Properties tab, Click New Role
> > Assignments. Try Content Manager or Publisher. One of those roles will
> > work.
> >
> > All other folders inherit from home.
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> >
> >
> > "Alain Quesnel" <alainsansspam@.logiquel.com> wrote in message
> > news:uAqaWJKHIHA.4228@.TK2MSFTNGP02.phx.gbl...
> >> Did you check SQL Server Configuration Manager to see if the Reporting
> >> Services service is started? It could also be a rights issue. Do you have
> >> sysadmin rights on your MSSQL server?
> >>
> >> --
> >>
> >> Alain Quesnel
> >> alainsansspam@.logiquel.com
> >>
> >> www.logiquel.com
> >>
> >>
> >> "Joel" <Joel@.discussions.microsoft.com> wrote in message
> >> news:598AD496-F255-4AB9-9DFD-DEE860D45F6F@.microsoft.com...
> >> Bonjour!
> >>
> >> I can't have access with my management studio to Reporting services
> >> (2005)installed on my web server. (Cannot connect to...)Do my
> >> developpers
> >> needs special rights?
> >>
> >> Regards, Joel :)
> >>
> >
> >
>sql

Can't access properties on Stored Procedures

Hi. I have set up an instance of SQL 2005 on my local computer. I use MS SQL Server Management Studio to login into my 2005 instance via Windows login. When I expand "Stored Procedures" under "Programmability" of the Database I want and go to a stored procedure and right click, I don't see the "properities" selection.

I know it's there because I can get to it on other instances but I can't get to it on my local instance. I added my windows user to my Logins and then to my database users but it didn't help.

Can anyone please tell me what I need to do so I can access the properties of the stored procedures?

Thanks

Your procedure was created with encryption option. Because this you can′t see the contents.

|||Its either an encryption problem (like already mentioned by the other poster) or you don′t have the appropiate permissions viewing the properties. Which access level does the account you are using have ? Is there a pas lock on the stored procedure symbol ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de

Cann't execute integration service package with SQL server agent

hi, can anyone explain, how to execute package with sql server agent:

the problem is::

i made a integration service package (in visual studio 2005). When I 'm in visual studio and do "execute" the package it works well. Then I build a dtsx file. When i double click on it, it opens and if i do execute, it works well.

I want to execute the package every week automatically. I write a job in SQL server agent, in Steps I choosed Type=SQL server Integration service packege, then General->packacge source -> file system, and then wrote where the dtsx file is (which was built). "Run as" I choose my user name.

then i'm trying to start a job, but it fails, and writes "The package execution failed."

What I'm doing wrong.

(sorry for my english)

The error message you are getting indicates that you are running the package in the SQL Serve agent as a 'Integration services package' step; right?

The problem with that is that if there is any problem with the execution you message error won't provide any details. To start change the step type to use CmdExec, so the error message is more descriptive. Most of the times the error is due to permission (when the agent executes the job it uses the account that it is being used to run the agent) or the protection level you used to saved your package (a package property).Look into this article for more details:

http://support.microsoft.com/default.aspx/kb/918760

Rafael Salas

Rafael Salas

|||

Some more notes on permissions, such as those for the file store, and a nice example that illustrates the difference between what you can get from the CmdExec step versus the SSIS subsystem-

Scheduled Packages
(http://wiki.sqlis.com/default.aspx/SQLISWiki/ScheduledPackages.html)

Cann't create Legacy (SQL 2000) Maintenance Plans

I recently installed the SQL Server 2005 Management Studio on my workstation
and the install of this new tool removed the old SQL Server 2000 Enterprise
Manager.
Since 99% of my installed server base is still SQL Server 2000, here’s my
question.
How am I supposed to manage my SQL Server 2000 instances with the SQL Server
2005 tools?
When I connect to a SQL Server 2000 instance, using SQL 2005 Management
Studio, I can see under Legacy -> Database Maintenance Plans, the existing
plans; however I cannot create any new Legacy Maintenance plans.
Kurt
It sounds bad but you should have thought of that before you upgraded then.
The documentation in 2005 clearly spells this out. If you need to change or
create new 2000 maintenance plans then you should have a machine with 2000
EM on it for that purpose. You must have chosen to upgrade your existing
instance instead of doing a side by side installation. There is no problem
running 2000 and 2005 on the same box and having both EM and SSMS running at
the same time. You can reinstall 2000 client tools but I am not sure if you
need to uninstall 2005 first or not. I would try it first and see.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"kmoskal@.newsgroups.nospam" <zork@.newsgroups.nospam> wrote in message
news:1FC128B9-88F0-42CA-8684-1445A06BA3B0@.microsoft.com...
>I recently installed the SQL Server 2005 Management Studio on my
>workstation
> and the install of this new tool removed the old SQL Server 2000
> Enterprise
> Manager.
> Since 99% of my installed server base is still SQL Server 2000, here’s my
> question.
> How am I supposed to manage my SQL Server 2000 instances with the SQL
> Server
> 2005 tools?
> When I connect to a SQL Server 2000 instance, using SQL 2005 Management
> Studio, I can see under Legacy -> Database Maintenance Plans, the existing
> plans; however I cannot create any new Legacy Maintenance plans.
>
>
>
> --
> Kurt

Cannot view sql server object properties in vstudio .net 2003

Hi!

Sudenly I stoped being able to view sql server object properties in the visual studio properties window . When I selected an sql server object in the server explorer i could see its properties in the prop. window . Now I can't see them anymore, the properties window apears blank.

Can anyone tell what do I need to do to be able to view them again.

Thanks & Best Regards
Pedro CostaHey-

I'm having this exact same problem. I'm researching to see if I can find anything, so if you beat me to it, please post the fix here. I'll do the same.|||What has changed between the time you COULD see them and right now? Did you install something? Apply a service pack? Remove something?|||I uninstalled VS.NET and installed VS.NET 2003. I'm using MSDE, BTW. I'm currently uninstalling and reinstalling MSDE, just for kicks. We'll see if it makes any difference. I'm wondering if the issue is permissions related somehow? But I'm logged in as a user with full admin rights on this machine, and I was under the impression that the IDE uses windows auth to connect to the database. Is this correct?
I've poked throught the environment preferences and I don't see anything that looks pertinent.

Cannot View My Database Diagrams

I recently reinstalled Visual Studio and SQL Server 2005 Developer Edition
onto a new (larger) hard drive and so far everything has been working as
before for my database, but when I went to view my database diagrams, I am
now getting this message. I tried as the message suggested to change the
database owner, but this only results in error messages. Neither can I add
any new database diagrams.
Anyone have any ideas as to how to solve such a problem?
Thanks,
Paul
---
TITLE: Microsoft SQL Server Management Studio
--
Database diagram support objects cannot be installed because this database
does not have a valid owner. To continue, first use the Files page of the
Database Properties dialog box or the ALTER AUTHORIZATION statement to set
the database owner to a valid login, then add the database diagram support
objects.What is the compatibility mode of the database?
You can check with:
select compatibility_level
from sys.databases
where name = 'YourDatabase'
It needs to be at 90 to use the diagrams. I think this was
fixed in the service pack so the other alternative is to
apply SP1.
-Sue
On Tue, 17 Oct 2006 08:37:01 -0700, a
<a@.discussions.microsoft.com> wrote:

>I recently reinstalled Visual Studio and SQL Server 2005 Developer Edition
>onto a new (larger) hard drive and so far everything has been working as
>before for my database, but when I went to view my database diagrams, I am
>now getting this message. I tried as the message suggested to change the
>database owner, but this only results in error messages. Neither can I add
>any new database diagrams.
>Anyone have any ideas as to how to solve such a problem?
>Thanks,
>Paul
>---
>
>TITLE: Microsoft SQL Server Management Studio
>--
>Database diagram support objects cannot be installed because this database
>does not have a valid owner. To continue, first use the Files page of the
>Database Properties dialog box or the ALTER AUTHORIZATION statement to set
>the database owner to a valid login, then add the database diagram support
>objects.
>--