Showing posts with label connect. Show all posts
Showing posts with label connect. Show all posts

Thursday, March 22, 2012

cant seem to connect to a store procedure on SQL server

Hi,

I am trying to get a page to call on a store procedure in SQL server and can seem to get it right. Any advice would be appreiated

<%@. Page Language="vb" %>
<%@. import Namespace="System.Data" %>
<%@. import Namespace="System.Data.OleDb" %>
<script runat="server"
Dim Conn as new OleDbConnection("Provider=SQLOLEDB;Server=*;Database=WEST1;User ID=*;Password=*;Trusted_Connection=False")
Sub Submit(Sender as Object, e as EventArgs)
Dim objCmd as OleDbCommand = new OleDbCommand ("vendorPending 10031,85140109", Conn)

Dim objReader as OleDbDataReader

objCmd.CommandType = CommandType.StoredProcedure

Try
objCmd.Connection.Open()
response.write ("opening data")
objReader = objCmd.ExecuteReader

catch ex as OleDbException
Response.write ("Error retrieving data.")

end try

DataGrid1.DataSource = objReader
DataGrid1.DataBind()

objCmd.Connection.Close()

End Sub

</script>
<html>
<head>
<title></title>
</head>
<body>
<form method="post" runat="server">
<tbody>
<tr>
<td>
<br />
</td>
</tr>
<tr>
<td>
Login :
</td>
<td>
<asp:textbox id="user" runat="server"></asp:textbox>
</td>
</tr>
<tr>
<td>
Password :
</td>
<td>
<asp:textbox id="Pass" runat="server" textmode="Password" MaxLength="10"></asp:textbox>
<br />
</td>
</tr>
<tr>
<td>
</td>
<td>
<asp:button id="Button1" onclick="submit" runat="server" text="submit"></asp:button>
</td>
</tr>
<br />
<tr>
<td>
</td>
</tr>
</tbody>
<br />
<asp:DataGrid id="DataGrid1" runat="server" HorizontalAlign="Left" Font-Names="Arial" ItemStyle-BackColor="#FFFFFF" AlternatingItemStyle-BackColor="#CCCCCC" Font-Size="10pt" Font-Name="Arial" width="755px" cellpadding="2" gridlins="vertical" BorderColor="Black" AutoGenerateColumns="False">
<HeaderStyle font-size="Small" font-names="Arial" font-bold="True"></HeaderStyle>
<EditItemStyle horizontalalign="Left"></EditItemStyle>
<AlternatingItemStyle backcolor="#CCCCCC"></AlternatingItemStyle>
<ItemStyle horizontalalign="Right" backcolor="White"></ItemStyle>
<Columns>
<asp:BoundColumn DataField="invnum" HeaderText="<b>Invoice Number</b>"></asp:BoundColumn>
<asp:BoundColumn DataField="invdate" HeaderText="Invoice Date" DataFormatString="{0:MM-dd-yyyy}"></asp:BoundColumn>
<asp:BoundColumn DataField="duedate" HeaderText="Due Date" DataFormatString="{0:MM-dd-yyyy}"></asp:BoundColumn>
<asp:BoundColumn DataField="invamt" HeaderText="Invoice Amount" DataFormatString="${0:N2}"></asp:BoundColumn>
<asp:BoundColumn DataField="payamt" HeaderText="Pay Amount" DataFormatString="${0:N2}"></asp:BoundColumn>
</Columns>
</asp:DataGrid>
</form>
</body>
</html>

The store proceudure takes 2 int parameters. I have coded it inline in order to test it. I also will implement validation once I get this working

Thanksuse sqlclient instead oledb. there is built in support for sql server.
heres some sample code :


Dim myCommand As SqlCommand
Dim myParam As SqlParameter
dim objcon as new sqlconnection("...") ' check www.connectionstrings.com for the right connection string
myCommand = New SqlCommand()
myCommand.Connection = objcon
myCommand.CommandText = "usp_Test"
myCommand.CommandType = CommandType.StoredProcedure

myCommand.Parameters.Add(New SqlParameter("@.userid",SqlDbType.int))
myCommand.Parameters("@.userid").Value = Trim(userid)

'add other params
dim objreader as
If objCon.State = 0 Then objCon.Open()
objreader = mycommand.ExecuteReader() ' objdatareader is your sqldatareader.
myCommand.dispose()

hth

Tuesday, March 20, 2012

Can't see the SQL Server Express Instance on SQL Browser

Hi All,

I am using SQL Server Express to connect to the network using VPN on a local machine. I have done the following..

a.) Enabled the remote connections for the Express Instance and rebooted the machine.

b.) Connected to the machine with Express Edition locally and can also connect other SQL Server instances from it to verify connectivity.

c.) Yes, SQL Browser Service is running.

d.) Firewall is not turned on, so I do not have to configure any exceptions.

Now here is the big problem: When I browse for SQL Servers on the network the machine does not show up on the list, i.e "macinename\SQLExpress". I had uninstalled and reinstalled the Express edition and rebooted the machine several times with no luck on the SQL Express Instance showing up on the browser list. I even changed the default instance name to "machinename\MACHINE1" on one of the reinstalls. However, I can connect to other SQL Instances from it. But, I cannot connect to it from other machines since its not registered on the network. I have been working on this for the past few days by looking for a solution via this and other forumns. Is there some setting somewhere that I am missing that prevents this instance from not showing up on the browser list. This issue with SQL Express Edition is baffling as well as frustrating and any ideas that can resolve this issue is very much appreciated.

when you say you cant see it on the list, do you mean in the ODBC dialog list? or some other list? if its involves the ODBC dialog, ive had to actually type in the whole machinename \SQLExpress since it didnt show up initially for it to work.|||I am talking about the SQL Server Browser list, that one can see all of the live SQL Server database Instances. Not the dialog list...|||I have several of them that refuse to show up in any browser list. But, I can connect to just about all of them even though they don't show up in the browser list by just typing in the instance name. Is there a particular error that you are getting? Can you give us more detail on your configuration and exactly what steps you are doing?|||

After installing SQL Server Express Edition on a new HP laptop with WIN 2K sp2, I went to see if it was registered on the Network as "machinename/SQLEXPRESS", and what I can see on the Network is just the "machinename", with the instance name missing. So I reinstalled it with a new instance name "machinename/Machine1", and again it was missing the instance name "Machine1", but I can see the machinename. I tried to connect with the instance name only "Machine1" and believe me I have tried it every which way but I always get the infamous error:

"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server)"

Now here is the odd part, I had installed SQL Server Express Edition on a older (1 year) IBM laptop with WIN 2K sp2, about 1 month back and was able to see the complete instance name on the network and can connect just fine. The only difference in these two machines is the age, but they both have the same OS Software installed. I have been pulling my hair in trying to figure out what is going on with SQL Server Express Edition on this new HP laptop with WIN 2K sp2 installed. It just refuses to register itself correctly on the network.

|||I have several that the browser only sees the machine name. That still doesn't mean that is what you use for the connection string. If you are using a default instance of Express Edition, then you still need to connect to machinename\SQLExpress even if browsing only shows you just the machine name. Now, that doesn't mean that you aren't having issues similar to mine on one of my clients which refuses to allow me to connect, we just need to make sure there isn't something else wrong first.|||As I have mentioned before, I tried using "machinename\MACHINE1" as the complete instance name and it throws out the error as I posted before. I can connect other instances from this HP Laptop but cannot connect to it from other machines. Perhaps we are having the same issue. I have been asking our Network Admin, System Admin and Security Admin and they are all puzzled by this SQL Express behavior on this HP laptop. I am wondering if it has anything to do with particular PC machines as the IBM pc works fine, but not the HP, this is just a guess. But I am running out of ideas and my users are running out of patience as I try to find a solution to this big problem....|||

Not sure if this has anything to do with your issue, but you mentioned that you were using Win2000 SP2, that is not a supported platform for SQL 2005, you need to be running SP4. I'm surprised that install didn't block.

Mike

|||

Yes, it looks like you are having exactly the same issue as I'm having on one of my machines. I have everything configured correctly with all of the access configured the way it needs to be. I can quite literally do anything I want to on the client when I'm RDPed into the server including remotely launching applications, remotely stopping start services, etc. The only that that it refuses to do is recognize and connect to the SQL Server Express Edition instance. I'm having problem doing further troubleshooting and opening a support case is rather difficult since the problem machine is in CA and I'm in TX without any direct ability to get hands on with the machine. I thought I had another one exhibiting this behavior, but when I plugged the laptop into my network, it magically started working and it hasn't thrown the error since. Yes, I'm rather baffled. My only saving grace is that I don't have any more hair to pull out at this point. :)

I have several more machines to work through and I'm hoping that I can get at least one of them to exhibit this behavior.

|||

I'm getting a bit closer on my side and now have 2 machines that are having issues. So, I want to try something and see if your results duplicate mine.

Log on to the machine that is having problems using your accouunt. Once it is up and running, go over to another instance and login to the Express instance from the other machine using your Windows credentials. Let me know if that magically makes it work.

|||

Hi Michael,

Nope, I tried as you suggested and I keep getting that same error, from the other machine when I try to connect to the problem machine. However, I can connect from the problem machine to any other SQL Server 2005 instance...Do not know what to do at this point. Perhaps Microsoft needs to help out...I hope they are reading this Message.

|||I am wondering if this issue has anything to do with having 2 NIC cards in a Laptop machine, one for the Local Network and the other for the Wireless Network...That is the only difference I see with the 2 different Laptops I am working with. The IBM machine does not have a Wireless Network NIC and it works...The other newer HP has a Wireless NIC and it does not work..Is Microsoft listening.....|||I can rule that one out. I have machines that connect just fine with multiple NICs and a couple that don't that also have multiple NICs.|||Have you tried opening a support case with Microsoft. I am not sure how this particular Software is supported since it is freely distributed..|||

SQL Server Express Edition is fully supported. Just like you can call in and get support on Internet Explorer.

I found a couple of other things when I was doing additional configuration. Verify that your WINS scopes are set properly. Also verify that the machine is actually getting its IP address correctly registered into DNS. These two items fixed 100% of the connectivity issues that I was having within SQL Server.

Monday, March 19, 2012

Can't see a particular table in a database

Hello,
I am trying to get info from a SQL7 database via ODBC. I can connect and
view the vast majority of tables, but one particular table (ceninfo_data)
does not appear.
In SQL Enterprise manager, I have taken a look at the permissions on the
table and public can select from it.
What am I missing?
Cheers
CQMMAN
"See, free nations are peaceful nations. Free nations don't attack each
other. Free nations don't develop weapons of mass destruction." George W
Bush -Milwaukee, Wis., Oct. 3, 2003Doh!
Fixed it. I was replicating a database and had changed the permissions on
the original, but not on the replicated database.
Cheers
"CQMMAN" <cqmman@.yahoo.co.uk> wrote in message
news:bq2jmp$1uhsi3$1@.ID-215193.news.uni-berlin.de...
quote:

> Hello,
> I am trying to get info from a SQL7 database via ODBC. I can connect and
> view the vast majority of tables, but one particular table (ceninfo_data)
> does not appear.
> In SQL Enterprise manager, I have taken a look at the permissions on the
> table and public can select from it.
> What am I missing?
> Cheers
> CQMMAN
> "See, free nations are peaceful nations. Free nations don't attack each
> other. Free nations don't develop weapons of mass destruction." George W
> Bush -Milwaukee, Wis., Oct. 3, 2003
>

Sunday, March 11, 2012

can't run dta

I had installed a new sql server 2005 enterprise with windows server 2003 enterprise,all done,but when I click the connect button to conect ,I get the error " Could not find stored procedure 'msdb..sp_DTA_help_session'".

Please see the following link that describes the permissions required for running DTA.

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

Friday, February 24, 2012

Can't make Remote Connection to SQL Cluster

Have got multiple SQL environments, both 2000 & 2005. Of these two are
clusters, one 2000 & one 2005.
Over remote VPN connection I can connect to every non-clustered server but
can't to either cluster. I've made sure that local & remote connections are
enabled on the clusters.
I have no problems connecting to both clusters on my local network so I'm
definitely connecting with the correct virtual servername.
Anybody had this issue before?
Thanks, Andy.Hi Andy
Although I have never tried this I don't think there should be anything that
stops you doing it. How are you connecting to the Clustered instance
(connection string or SQLCMD command) ? Which protocol are you using/enabled
?
Which port is being used? Are there any firewalls? Is the name being
resolved/can you connect to the IP address?
John
"AndyT" wrote:

> Have got multiple SQL environments, both 2000 & 2005. Of these two are
> clusters, one 2000 & one 2005.
> Over remote VPN connection I can connect to every non-clustered server but
> can't to either cluster. I've made sure that local & remote connections ar
e
> enabled on the clusters.
> I have no problems connecting to both clusters on my local network so I'm
> definitely connecting with the correct virtual servername.
> Anybody had this issue before?
> Thanks, Andy.
>
>|||Have you tried connecting to one of the clustered instances from a node
within the cluster that currently does not currently own the SQL Server
instance (the so-called "passive") node? If that works, then I wonder if
there is a firewall rule between where you are and where the cluster is that
is preventing you from getting to the cluster. However, if you can't get to
SQL server from another node in the cluster, it suggests that SQL is not
listening for remote connections. Be sure to check the SQL Server error
log. It says what protocols it's actually listening on. Be sure to do a
tracert on the SQL Server virtual IP.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"AndyT" <tipton@.tpg.com.au> wrote in message
news:ukMBqehNIHA.4740@.TK2MSFTNGP02.phx.gbl...
Have got multiple SQL environments, both 2000 & 2005. Of these two are
clusters, one 2000 & one 2005.
Over remote VPN connection I can connect to every non-clustered server but
can't to either cluster. I've made sure that local & remote connections are
enabled on the clusters.
I have no problems connecting to both clusters on my local network so I'm
definitely connecting with the correct virtual servername.
Anybody had this issue before?
Thanks, Andy.|||Could be a firewall issue. When you connect to a cluster, it listens on the
virtual IP. Replies are sent from the regular IP address, according to the
packet headers. This drives some firewalls batty. See your network admin
about allowing the physical IP as well as the virtual one to have access
from the outside.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"AndyT" <tipton@.tpg.com.au> wrote in message
news:ukMBqehNIHA.4740@.TK2MSFTNGP02.phx.gbl...
> Have got multiple SQL environments, both 2000 & 2005. Of these two are
> clusters, one 2000 & one 2005.
> Over remote VPN connection I can connect to every non-clustered server but
> can't to either cluster. I've made sure that local & remote connections
> are enabled on the clusters.
> I have no problems connecting to both clusters on my local network so I'm
> definitely connecting with the correct virtual servername.
> Anybody had this issue before?
> Thanks, Andy.
>

Can't make Remote Connection to SQL Cluster

Have got multiple SQL environments, both 2000 & 2005. Of these two are
clusters, one 2000 & one 2005.
Over remote VPN connection I can connect to every non-clustered server but
can't to either cluster. I've made sure that local & remote connections are
enabled on the clusters.
I have no problems connecting to both clusters on my local network so I'm
definitely connecting with the correct virtual servername.
Anybody had this issue before?
Thanks, Andy.Hi Andy
Although I have never tried this I don't think there should be anything that
stops you doing it. How are you connecting to the Clustered instance
(connection string or SQLCMD command) ? Which protocol are you using/enabled?
Which port is being used? Are there any firewalls? Is the name being
resolved/can you connect to the IP address?
John
"AndyT" wrote:
> Have got multiple SQL environments, both 2000 & 2005. Of these two are
> clusters, one 2000 & one 2005.
> Over remote VPN connection I can connect to every non-clustered server but
> can't to either cluster. I've made sure that local & remote connections are
> enabled on the clusters.
> I have no problems connecting to both clusters on my local network so I'm
> definitely connecting with the correct virtual servername.
> Anybody had this issue before?
> Thanks, Andy.
>
>|||Have you tried connecting to one of the clustered instances from a node
within the cluster that currently does not currently own the SQL Server
instance (the so-called "passive") node? If that works, then I wonder if
there is a firewall rule between where you are and where the cluster is that
is preventing you from getting to the cluster. However, if you can't get to
SQL server from another node in the cluster, it suggests that SQL is not
listening for remote connections. Be sure to check the SQL Server error
log. It says what protocols it's actually listening on. Be sure to do a
tracert on the SQL Server virtual IP.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"AndyT" <tipton@.tpg.com.au> wrote in message
news:ukMBqehNIHA.4740@.TK2MSFTNGP02.phx.gbl...
Have got multiple SQL environments, both 2000 & 2005. Of these two are
clusters, one 2000 & one 2005.
Over remote VPN connection I can connect to every non-clustered server but
can't to either cluster. I've made sure that local & remote connections are
enabled on the clusters.
I have no problems connecting to both clusters on my local network so I'm
definitely connecting with the correct virtual servername.
Anybody had this issue before?
Thanks, Andy.|||Could be a firewall issue. When you connect to a cluster, it listens on the
virtual IP. Replies are sent from the regular IP address, according to the
packet headers. This drives some firewalls batty. See your network admin
about allowing the physical IP as well as the virtual one to have access
from the outside.
--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"AndyT" <tipton@.tpg.com.au> wrote in message
news:ukMBqehNIHA.4740@.TK2MSFTNGP02.phx.gbl...
> Have got multiple SQL environments, both 2000 & 2005. Of these two are
> clusters, one 2000 & one 2005.
> Over remote VPN connection I can connect to every non-clustered server but
> can't to either cluster. I've made sure that local & remote connections
> are enabled on the clusters.
> I have no problems connecting to both clusters on my local network so I'm
> definitely connecting with the correct virtual servername.
> Anybody had this issue before?
> Thanks, Andy.
>

Can't login with remote servers

Able to connect just fine at the main server but when trying to get the other
servers to connect get the following error.
Using SQL Server 2005 Express Edition:
Connection Failed:
SQLState: '01000'
SQL Server Error: 11004
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect()).
Connection Failed:
SQLState: '08001'
SQL Server Error: 6
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL server not
found.
Any ideas why I would be getting this error? All information is correct
according to where it is in the first server.
Dusitn D'Amour
Coyote Solutions Group
505.742.0066
www.coyotesolutions.com
Sure. See the archives of this list. We've discussed this any number of
times. Check back here if you don't find the answer(s).
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
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)
Between now and Nov. 6th 2006 you can sign up for a substantial discount.
Look for the "Early Bird" discount checkbox on the registration form...
------
Microsoft MVP, Author, Mentor
Microsoft MVP
"Dustin D''Amour" <DustinDAmour@.discussions.microsoft.com> wrote in message
news:B13047CD-D41D-43A4-B80D-350B30B372AF@.microsoft.com...
> Able to connect just fine at the main server but when trying to get the
> other
> servers to connect get the following error.
> Using SQL Server 2005 Express Edition:
> Connection Failed:
> SQLState: '01000'
> SQL Server Error: 11004
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
> (Connect()).
> Connection Failed:
> SQLState: '08001'
> SQL Server Error: 6
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL server
> not
> found.
>
> Any ideas why I would be getting this error? All information is correct
> according to where it is in the first server.
>
> --
> Dusitn D'Amour
> Coyote Solutions Group
> 505.742.0066
> www.coyotesolutions.com
|||Where is the archive located?
I should also mention that mixed authentication is selected and the remote
servers still can not connect.
Dusitn D'Amour
Coyote Solutions Group
505.742.0066
www.coyotesolutions.com
"William (Bill) Vaughn" wrote:

> Sure. See the archives of this list. We've discussed this any number of
> times. Check back here if you don't find the answer(s).
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> 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)
> Between now and Nov. 6th 2006 you can sign up for a substantial discount.
> Look for the "Early Bird" discount checkbox on the registration form...
> ------
>
> Microsoft MVP, Author, Mentor
> Microsoft MVP
> "Dustin D''Amour" <DustinDAmour@.discussions.microsoft.com> wrote in message
> news:B13047CD-D41D-43A4-B80D-350B30B372AF@.microsoft.com...
>
>
|||I found http://support.microsoft.com/kb/306865 which show the same error I'm
having but when I go through the steps for the workaround it still doesn't
work.
Anyone else have any other ideas?
Dusitn D'Amour
Coyote Solutions Group
505.742.0066
www.coyotesolutions.com
"Dustin D''Amour" wrote:
[vbcol=seagreen]
> Where is the archive located?
> I should also mention that mixed authentication is selected and the remote
> servers still can not connect.
>
> --
> Dusitn D'Amour
> Coyote Solutions Group
> 505.742.0066
> www.coyotesolutions.com
>
> "William (Bill) Vaughn" wrote:
|||This thread had an answer that seems to work for now.
Dusitn D'Amour
Coyote Solutions Group
505.742.0066
www.coyotesolutions.com
"Dustin D''Amour" wrote:
[vbcol=seagreen]
> I found http://support.microsoft.com/kb/306865 which show the same error I'm
> having but when I go through the steps for the workaround it still doesn't
> work.
> Anyone else have any other ideas?
>
> --
> Dusitn D'Amour
> Coyote Solutions Group
> 505.742.0066
> www.coyotesolutions.com
>
> "Dustin D''Amour" wrote:
|||Forgot t put the link in.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=129105&SiteID=1
Dusitn D''Amour
Coyote Solutions Group
505.742.0066
www.coyotesolutions.com
"Dustin D''Amour" wrote:
[vbcol=seagreen]
> This thread had an answer that seems to work for now.
> --
> Dusitn D'Amour
> Coyote Solutions Group
> 505.742.0066
> www.coyotesolutions.com
>
> "Dustin D''Amour" wrote:

cant login to sql 2005 express

when i installed visual web developer and sql management studio,i try to use sql management studio to connect to sql 2005 express,but a error ocurred.here is the error message.

TITLE: Connect to Server
----------

Cannot connect to DH\SQLEXPRESS.

----------
ADDITIONAL INFORMATION:

The type initializer for 'System.Data.SqlClient.SqlConnection' threw an exception. (System.Data)

----------

The type initializer for 'System.Data.SqlClient.SqlConnectionFactory' threw an exception. (System.Data)

----------

The type initializer for 'System.Data.SqlClient.SqlPerformanceCounters' threw an exception. (System.Data)

----------

Configuration system failed to initialize (System.Configuration)

----------

Unrecognized configuration section system.serviceModel. (C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Config\machine.config line 136) (System.Configuration)

and i wonder if anybody has experienced this error can tell me how to solve?

Can you post what in line 136 of your machine.config file?

|||

the following is the part of machine.config

line 136<system.serviceModel>
<extensions>
<behaviorExtensions>
<add name="persistenceProvider" type="System.ServiceModel.Configuration.PersistenceProviderElement, System.WorkflowServices, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<add name="workflowRuntime" type="System.ServiceModel.Configuration.WorkflowRuntimeElement, System.WorkflowServices, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<add name="enableWebScript" type="System.ServiceModel.Configuration.WebScriptEnablingElement, System.ServiceModel.Web, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<add name="webHttp" type="System.ServiceModel.Configuration.WebHttpElement, System.ServiceModel.Web, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<add name="Microsoft.VisualStudio.Diagnostics.ServiceModelSink.Behavior" type="Microsoft.VisualStudio.Diagnostics.ServiceModelSink.Behavior, Microsoft.VisualStudio.Diagnostics.ServiceModelSink, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/></behaviorExtensions>
<bindingElementExtensions>
<add name="webMessageEncoding" type="System.ServiceModel.Configuration.WebMessageEncodingElement, System.ServiceModel.Web, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<add name="context" type="System.ServiceModel.Configuration.ContextBindingElementExtensionElement, System.WorkflowServices, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
</bindingElementExtensions>
<bindingExtensions>
<add name="wsHttpContextBinding" type="System.ServiceModel.Configuration.WSHttpContextBindingCollectionElement, System.WorkflowServices, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<add name="netTcpContextBinding" type="System.ServiceModel.Configuration.NetTcpContextBindingCollectionElement, System.WorkflowServices, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<add name="webHttpBinding" type="System.ServiceModel.Configuration.WebHttpBindingCollectionElement, System.ServiceModel.Web, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<add name="basicHttpContextBinding" type="System.ServiceModel.Configuration.BasicHttpContextBindingCollectionElement, System.WorkflowServices, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
</bindingExtensions>
</extensions>
<client>
<metadata>
<policyImporters>
<extension type="System.ServiceModel.Channels.ContextBindingElementImporter, system.workflowservices, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL"/>
</policyImporters>
<wsdlImporters>
<extension type="System.ServiceModel.Channels.ContextBindingElementImporter, system.workflowservices, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL"/>
</wsdlImporters>
</metadata>
</client>
<commonBehaviors><endpointBehaviors><Microsoft.VisualStudio.Diagnostics.ServiceModelSink.Behavior/></endpointBehaviors><serviceBehaviors><Microsoft.VisualStudio.Diagnostics.ServiceModelSink.Behavior/></serviceBehaviors></commonBehaviors></system.serviceModel>]

it's no problem.it guess it may be the problem of FrameWork.because when i try to conncet by visual web developer,an error occur.it says Request .net data provider,you may not install.but as we know the .net FrameWork contains the .net data provider. and the visual web developer 2008 beta2 contains .Net Framework 3.5,So i really don't understand.

|||

Hi chance1,

After having consulted some of my collegues, it seems that your web.config file is somewhat corrupted.

The section "system.serviceModel" should be registered like the following (mine is from a 3.0 machine). <sectionGroup name="system.serviceModel" type="System.ServiceModel.Configuration.ServiceModelSectionGroup, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"> <section name="behaviors" type="System.ServiceModel.Configuration.BehaviorsSection, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" /> <section name="bindings" type="System.ServiceModel.Configuration.BindingsSection, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" /> <section name="client" type="System.ServiceModel.Configuration.ClientSection, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" /> <section name="comContracts" type="System.ServiceModel.Configuration.ComContractsSection, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" /> <section name="commonBehaviors" type="System.ServiceModel.Configuration.CommonBehaviorsSection, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowDefinition="MachineOnly" allowExeDefinition="MachineOnly" /> <section name="diagnostics" type="System.ServiceModel.Configuration.DiagnosticSection, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" /> <section name="extensions" type="System.ServiceModel.Configuration.ExtensionsSection, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" /> <section name="machineSettings" type="System.ServiceModel.Configuration.MachineSettingsSection, SMDiagnostics, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowDefinition="MachineOnly" allowExeDefinition="MachineOnly" /> <section name="serviceHostingEnvironment" type="System.ServiceModel.Configuration.ServiceHostingEnvironmentSection, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" /> <section name="services" type="System.ServiceModel.Configuration.ServicesSection, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />

</sectionGroup>

I would suggest you to install the same .Net Framework 3.5 on another machine and copied the "machine.config" from the good machine to the machine in question.See if this will work. Please feel free to let me know if you have any further questions. thanks.

|||

thank you Bo Chen .and i did what you suggest in a few days ago.but sadlly, it doesn't work. and later i reinstall xp and vs 2005. and the sql 2005 express works.later i try to install visual web developer express 2008.this time visual web developer 2008 can connect and use the sql 2005 express. but vs 2005 can't work nowCrying.but thank you for the people who have helped me.

|||

Hi ,

This problem might occur sometimes due to corrupt installation of sql server 2005. I was also facing the same problem.Uninstall Sql Server 2005 and reinstall it with a different instance(named). Dont try to install with the same instance which u had used previously.Try this and tell me if this works

Thanks & Regards

Keerti Somasundaram

|||

thank you.but before i install sql server 2005,i have reinstall windows xp.and there is no sql 2005 in it. and i think it may be theproblem of visual web developer2008 beta 2.

Sunday, February 19, 2012

Can't login into SQL Server Database

Hey
I get the following error when trying to connect to my named instance Sql
Server running locally on my laptop. Does anyone know how to resolve this
I get the following error : Login failed for user:acw
Here is my code:
SqlConnection sConn = new SqlConnection(server=ACLAPTOP\ACSQLSERVE
R;User
id=acw; Password=;Database=BookSpot);
Thanks,
AlAl
Open QA and try to log in with the user. Do you get the same error?
"Al Wilkerson" <ac527@.comcast.net> wrote in message
news:7aCdnUdO-Ipm37zfRVn-gA@.comcast.com...
> Hey
> I get the following error when trying to connect to my named instance Sql
> Server running locally on my laptop. Does anyone know how to resolve this
> I get the following error : Login failed for user:acw
> Here is my code:
> SqlConnection sConn = new SqlConnection(server=ACLAPTOP\ACSQLSERVE
R;User
> id=acw; Password=;Database=BookSpot);
>
> Thanks,
> --
> Al
>|||I assume this is C# code. Did you give this user a blank password?
Double-check the password for this user and the rights/roles granted to this
user in EM. I assume your connection string is properly quoted (or it
wouldn't even compile for you). Finally, are you using Integrated Security
or SQL Server Authentication?
Thx
Mike C.
"Al Wilkerson" <ac527@.comcast.net> wrote in message
news:7aCdnUdO-Ipm37zfRVn-gA@.comcast.com...
> Hey
> I get the following error when trying to connect to my named instance Sql
> Server running locally on my laptop. Does anyone know how to resolve this
> I get the following error : Login failed for user:acw
> Here is my code:
> SqlConnection sConn = new SqlConnection(server=ACLAPTOP\ACSQLSERVE
R;User
> id=acw; Password=;Database=BookSpot);
>
> Thanks,
> --
> Al
>

can''t log in to reporting services

I try to log in and I get this big long error that looks like html and starts with something like:

Cannot Connect to myServerName

Client found response content type of 'text/html; charset=utf-8 but expected 'text/xml'

-etc etc etc

is this a permissions issue?

Are you using SharePoint?

"Restrictions on using built-in accounts apply to some deployment topologies of Reporting Services that include a report server running in SharePoint integrated mode. The following combination of factors will result in service account requirements:

Report Server is integrated with a SharePoint farm comprising more than one computer.
The report server and SharePoint Central Administration web site run on separate computers.
|||

we are running a sharepoint site on the same physical server, but the app i'm working on is defined as an entirely separate app in IIS - so i'm wondering, does that qualify for the scenario above? the statement "accessing reporting services feature through a sharepoint site.." doesn't seem to apply to my scenario.

- to clarify, i am trying to login to reporting services through mssms console in sqlsvr 2005

|||

My issue similar to your citation http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1761909&SiteID=1

in that our admin indeed has configured IIS so that the default web site pointed to another folder. However, we do not have the luxury of

"simply setting this back to c:\inetpub and added my actual website as a virtual folder and hey presto it works!"

I need to get it to work pointed to the non-default website, which happens to be called "database" - so the user gets to my app by going http://database - http://localhost/ doesn't work.

Cant locate SQL Server Express from client pc

Hi,

I have a 5 user network running SBS 2000.

I have installed SQL Server Express on one of the client machines (not the SBS Server) I can connect locally without problem. However i cant connect from the other client machines.

I have enabled TCP/IP, Remote Connections Etc

I am attempting to test the connection using an .udl file. The server name is found but i still cant connect.

Any help would be apreciated.

Hi,

the error message would be helpful for us.

HTH, jens Suessmeyer.

http://www.sqlserver2005.de

|||

Hi

I am using the following information on the Data Link Properties Dialog:

Provider: Microsoft OLE DB Provider for SQL Server
Server Name: DIMENSION1100\SQLEXPRESS

Use Windows NT Integrated security

At "Select the database on the server" combo i recieve the following error:

[DBNETLIB] [ConnectionOpen (Connect()).]SQL Server does not exist or access denied

Loging Failed Catalog information can not be found

Thanks

|||

Hi,

I have now managed to connect to SQLServer Express from the remote machine, but the only databases available are:

Master, msdb and tempdb.

Any ideas?

Thanks

|||SQL Server 2005 introduced the feature that only objects where you have permissions on are reflected in the Information_Schemas and in the other interfaces. So, I guess the user you are connecting to the database isn′t priviledged to access the databases.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||

Hi,

Thanks for the quick reply. I have started to look at permissions but there's alot to take in, where do i begin? Is there an easy way to allow 100% access then lock down at a later date? (Just to test connectivity)

Thanks for your help

|||Grant the database role dbo to the user.

But keep in mind to change the role after testing (!) :-)

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||

Where is this done from?

Also are there any instruction available that outline security for sql express running in Windows Authentication mode?

Thanks again for all your help.

|||

Hi,

"Played around" < with 'user mapping' via ssms and gained access from remote pc's.

Thanks.

Friday, February 10, 2012

Can't get SQL Manager to connect to server instance SQLEXPRESS

I installed SQL Server Express and SQL Server manager, then tried to start manager. SQL Service is running, but SQL Manager attempt to connect to SQL Server instance times-out even though I correctly identify instance as SQLEXPRESS? Everything seems to be normal - both SQL Server and Manager are on a single Windows XP home machine. Any suggestions. ThanksHi,
Try using .\SQLEXPRESS as the instance name...

cheers,
Paul June A. Domag|||Great - It Works! Thanks|||After reading this thread and another one I've tried entering the following in express manager and I still can't connect:

.\MSSQLSERVER
(local)\MSSQLSERVER

I am running SQL Server Express June CTP on a Win2K3 box. SQL Express Manager is also running on the same Win2K3 box.

I have opened all the network protocols for SQL Server Express, I've also enabled the SQL Server browser. There are no firewalls involved. This is probably the most insecure setup, yet I still cannot connect locally Tongue Tied

Any ideas?

I followed all the instructions here:
http://download.microsoft.com/download/a/6/3/a63ec922-913e-4228-93e3-970abff3fd66/ReadmeSQLExpMgr.htm
and here
http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

Nothing seems to work.
|||Hi,
Actually its .\SQLServer not .\MSSQLSERVER.
Have you tried it? got any versions installed before the June CTP?
cheers,
Paul June A. Domag|||Unfortunately that didn't work either.
All I have installed is June CTP on a fresh install of Win2K3 Standard.
In the SQL Server Configuration Manager under "name" it says: SQL Server (MSSQLSERVER).
This would indicate the name of the SQL server is "MSSQLSERVER" correct? I chose "default" instance during the install and that is the name it gave itself.
This is getting frustrating... I thought programming with MS stuff would be easy. I could have connected to MySQL a hundred different ways by now.
|||Just a two cents worth general comment - the MS beta's tend to have problems that the production versions don't - having used SQL Server from the time it was Sybase Server to date I can say it is great software that occassionally suffers from growing pains. PS|||Yeah, I don't expect Beta software to be 100% functional but I do expect the basic functionality to be working and straightforward. Connecting to the server shouldn't be this difficult. Especially if you consider the target market for this product.
|||Hi,
Oops, I guess I had a typo. Its .\SqlExpress, If you choose default instance...
cheers,
Paul June A. Domag|||After all that I accidently stumbled upon a solution.
The only thing that works for my installation is just plain ".\" (no quotes) and nothing else. Go figure. Hopefully this post saves someone else a lot of time.
|||Hi,
Weird... Could you report a bug in Product Feedback? So that Microsoft would be aware of this...

cheers,
Paul June A. Domag|||thanks a lot this helped!!!!!

Paul Domag wrote:

Hi,
Try using .\SQLEXPRESS as the instance name...

cheers,
Paul June A. Domag

|||Thanks!!!! I have been pulling my hair out all night trying to figure out why I couldn't connect. That did the trick. Why doesn't MS tell you about these important details.|||

I'm getting error like

SqlDateTime overflow. Must be between 1/1/1753 12:00:00 AM and 12/31/9999 11:59:59 PM.

I want to set it bet 1/1/0001 to 31/12/9999. how to do this?

So do u have any solution over it pls.

I think u have solution over it because I have seen same problem u had .

At last Happy New Year 2006 at this first meet ing with u

Balasaheb

|||Hi,

There are only two datatypes that could handle date and time values in sqlserver. These are DateTime and SmallDateTime. Both of these types cold not handle data between 1/1/0001 to 31/12/9999. But you can store these dates as a varchar and just parse the dates to calculate them in your program...

cheers,

Paul June A. Domag