I can make odbc connection (in .net code) using this connectionstring.............. and fetch the data also....
But somehow I don't know why... it gives the wrong result for my stored procedure.....
stored procedure is quite big and has many statements.......... after some digging I found that it gives the correct result if we use Server Explorer like Sql server, DBArtesian etc.. (not possible to copy it here, but it gives wrong result in date calculation)
But in Visual Studio Server Explorer when I make new connection and select "Microsoft OLEDB Provider for the odbc" and put the above connection string...it gives the correct result for the tables but wrong result for the stored procedure...
I feel that there is some problem with Provider....
I am not passing any provider here so it takes MSDASQL.1...
My question is What should be my connection string here..........????
In the VB 2005 Express, I can get the SqlConnection and ConnectionString of a Database "shcDB" in the Object Explorer of SQL Server Management Studio Express (SSMSE) by the following set of code: ///--CallshcSpAdoNetVB2005.vb--////
Imports System.Data
Imports System.Data.SqlClient
Imports System.Data.SqlTypes
Public Class Form1
Public Sub InsertNewFriend()
Dim connectionString As String = "Data Source=.SQLEXPRESS;Initial Catalog=shcDB;Integrated Security=SSPI;"
Dim connection As SqlConnection = New SqlConnection(connectionString)
Try
connection.Open()
Dim command As SqlCommand = New SqlCommand("sp_insertNewRecord", connection)
command.CommandType = CommandType.StoredProcedure ....................................... etc. /////////////////////////////////////////////////////// If the Database "shcDB" and the Stored Procedure "sp_inertNewRecord" are in the Database Explorer of VB 2005 Express, I plan to use "Data Source=local" in the following code statements to get the SqlConnection and ConnectionString: ......................... ........................
Dim connectionString As String = "Data Source=local;Initial Catalog=shcDB;Integrated Security=SSPI;"
Dim connection As SqlConnection = New SqlConnection(connectionString)
Try
connection.Open()
Dim command As SqlCommand = New SqlCommand("sp_insertNewRecord", connection)
command.CommandType = CommandType.StoredProcedure ........................ etc.
Is the "Data Source=local" statement right for this case? If not, what is the right code statement for my case?
I am getting this error when I try to bcp in or even when I try to create a Primary key or index on a Table.
- Unable to create index 'PK_CMCMessages'.
ODBC error: [Microsoft][ODBC SQL Server Driver][SQL Server] Backup, CHECKALLOC, bulk copy, SELECT INTO, and file manipulation (such as CREATE FILE) operations on a database must be serialized. Reissue the statement after the current backup, CHECKALLOC, or file manipulation operation is completed.
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not create constraint. See previous errors.
I ran CHECKALLOC and its running for days and I dont have any clue whats happening. If you have any idea please let me know how to solve this problem.
Error during Transformation 'DirectCopyXform' for Row number 813. Errors encountered so far in this task: 1. TransformCopy 'DirectCopyXform' conversion error: Destination does not allow NULL on column pair 1 (source column 'Customer' (DBTYPE_R8), destination column 'Customer' (DBTYPE_STR))
What does that mean?
I have an excel file named Customer List with fields such as Customer, Name, City. I want to import it into a syspro table called SyproCompanyF.ArCustomer.
My application works with the Connection pooling ODBC. Everything works well, when it data base this down the SQLConnect function finishes steeply my application.
Hello, am trying to run a SP in my class against my database. However, I get the error below. The connection string is in the web.config file as thus <connectionStrings> <add name="cell_ConnectionString" connectionString="Data Source=xxx.xxx.xxx.xxx,2433;Network Library=DBMSSOCN;Initial Catalog=day;User ID=day;Password=jdhje5rhydgd;" providerName="System.Data.SqlClient"/> </connectionStrings> and the connection string name is called in my class as thus 1 SqlConnection con = new SqlConnection(ConfigurationManager.AppSettings["cell_ConnectionString"]); 2 3 SqlCommand command = new SqlCommand("cell_ConnectionString", con); 4 command.CommandType = CommandType.StoredProcedure; 5
What is wrong here ? thanks Ehi
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.InvalidOperationException: The ConnectionString property has not been initialized.Source Error:
Line 49: command.CommandType = CommandType.StoredProcedure; Line 50: Line 51: con.Open(); Line 52: Line 53: command.Parameters.Add(new SqlParameter("@csv", SqlDbType.VarChar, 8000, "recipients")); Source File: c:inetpubwwwrootizevwwwrootwelcomesms.aspx.cs Line: 51
Hi guys, I'm getting this error:System.InvalidOperationException: The ConnectionString property has not been initialized when I'm trying to connect to an SQL database using the following code: Dim mySelectQuery As String = "SELECT [tabl_id] FROM [myTable]"Dim myConnection As New SqlConnection(System.Configuration.ConfigurationManager.AppSettings("myConnString"))Dim myCommand As New SqlCommand(mySelectQuery, myConnection)myConnection.Open()Dim myReader As SqlDataReadermyReader = myCommand.ExecuteReader()While myReader.Read() Response.Write(myReader("tabl_id") & "<br/>")End WhilemyConnection.Close() and in web.config: <appSettings/> <connectionStrings> <add name="myConnString" connectionString="Data Source=100.100.100.100;Initial Catalog=myDatabase;User ID=me;Password=password" providerName="System.Data.SqlClient"/> </connectionStrings> If I place the actual connection string inside instead of trying to reference the web.config setting it works, but using 'System.Configuration.ConfigurationManager.AppSettings' returns the error. Is there something I'm doing wrong?
Hello! I'm recieving an error when I submit a form to an Access database. I took this site over from someone else and kept their code as I'm more of a designer than a programmer. If anyone has any ideas as to how to fix it, I would really appreciate it. I'm pretty clueless when it comes to this. I've tried to figure it out on my own, but I seem to be failing. Any help would be great! Here's what I receive when I submit the form:
The ConnectionString property has not been initialized. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.InvalidOperationException: The ConnectionString property has not been initialized.Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace:
[InvalidOperationException: The ConnectionString property has not been initialized.] System.Data.OleDb.OleDbConnection.Open() +203 modern_foods.promotions_form.saveInfo(Object s, EventArgs e) +535 System.Web.UI.WebControls.Button.OnClick(EventArgs e) +108 System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +57 System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +18 System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33 System.Web.UI.Page.ProcessRequestMain() +1292 Thank you in advance!
I have some custom code in my report <Code> element that I use to query a database. I have hardcoded the connectionstring in this code but I would like to use the same datasource that the report uses. Is there some report property that allows me to access this datasource?
I apologize if this is not the correct forum for this posting. Looking at the descriptions, it appeared to be the best choice.
I am running Windows XP Pro SP2. I have installed the SQL Native Client for XP. However, when I try to add a new data source through ODBC Connection Manager, SQL Native Client is not listed as an option. I have followed this procedure on three other systems with no problems. What would be causing the SQL Native Client to not show up in the list of available ODBC data sources?
All of the books I have about Visual Basic 2005 Database Programming, gives examples of connecting to a database on a localhost computer. But what about the connection to a database on a sql server 2005 on a computer wich can only be reached via the internet ? Is that possible without using ASP.NET ?
My problem:
I have a desktop with a sqlserver 2005 database . This desktop is connected with the internet . The IP address is a dynamic IP address.
On my laptop is a ADO.NET 2.0 program that needs to be connected with the database on my desktop.
What kind of address do I have to specify in my connectionstring in order to get connected to the database on my desktop , which can only be reached via the internet ?
I'm I wright to suppose that in the case of a static IP address, all I have to do is put the IP address in the connectionstring in order to get connected with my desktop via the internet? Are there some changings to be made in the settings of the SQL SERVER 2005 on my desktop ? What about the security ?
On the other hand , because the address of my desktop is a dynamic IP address, how do I solve this problem.?
I've heard about a program DynDns that can solve the problem of the dynamic address. Can i use this program together with my ADO.NET program to solve the problem , and how do I specify in this case the address to the database on my desktop in the connectionstring?
Is there someone who has experience with that program and the problem I described here ?
On localhost this application works fine but when I put on remote server. I am getting following errors. For both localhost and server, I am using same remote sql 2000. I will appreciate any help.
Thanks,
Arif
Server Error in '/' Application. --------------------------------------------------------------------------------
ERROR [42000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax near ')'. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: Microsoft.Data.Odbc.OdbcException: ERROR [42000] [Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax near ')'.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
What different are there between connectionString (Part 1) and connectionString (Part 2) in web.config The CCWW is my PC's name, normally I can connect to the database ASPNETDB.MDF correctly either Part 1 or Part 2 in a web page,After I open Database Explorer panel and browse ASPNETDB.MDF, I can't connect to database using Part 2 when I open a webpage in Microsoft Visual Web Developer 2005 Express Edition,but I can correctly open a webpage using Part 1 after I open Database Explorer panel. What different are there between connectionString (Part 1) and connectionString (Part 2) in web.config? I guess while I use Part 1 to connect, maybe it will be cancel exclusive method of the database ASPNETDB.MDF first, but when I connect to database using Part 2, maybe two programms both Part 2 and Database Explorer visit ASPNETDB.MDF at the same time!
The following (VB.Net) code causes exceptions at seemingly random times. Any suggestions? Not sure if the problem is in .Net's ODBC support or in Sql Native Client.
If MARS is off, usually after less than 100 loops:
Code Snippet
System.Data.Odbc.OdbcException was unhandled ErrorCode=-2146232009 Message="ERROR [HY000] [Microsoft][SQL Native Client]Connection is busy with results for another command" Source="SQLNCLI.DLL" Turning MARS is on bypasses that error, so it will sometimes survive a thousand or so runs before hitting:
Code Snippet
System.Data.Odbc.OdbcException was unhandled ErrorCode=-2146232009 Message="ERROR [23000] [Microsoft][SQL Native Client][SQL Server]Cannot insert the value NULL into column 'Number', table 'tempdb.dbo.#TempTable___..(shortened to fit).. _________000000002F3F'; column does not allow nulls. INSERT fails. Source="SQLNCLI.DLL" Code here: (Console Application, empty database, Visual Studio 2005, .Net 2.0, Windows XP,SQL Server 2005 or SQL Express 2005, Local or Remote)
Code Snippet
Module Module1
Sub Main()
'Dim connection As New SqlClient.SqlConnection("database=TestDB;server=.sqlexpress;Integrated Security=SSPI;") 'Doesn't crash 'Dim connection As New OleDb.OleDbConnection("Provider=SQLNCLI;database=TestDB;Server=.sqlexpress;Trusted_Connection=yes;") 'Doesn't crash
'Dim connection As New Odbc.OdbcConnection("Driver={SQL Native Client};Database=TestDB;Server=.sqlexpress;Trusted_Connection=yes;") 'Crashes Dim connection As New Odbc.OdbcConnection("Driver={SQL Native Client};Database=TestDB;Server=.sqlexpress;Trusted_Connection=yes;MARS_Connection=yes") 'Crashes
VBMath.Randomize()
Dim run_count As Integer = 1 connection.Open() Console.WriteLine("Connected!!")
While True 'connection.Open()
Dim testcmd As New Odbc.OdbcCommand("CREATE TABLE [#TempTable] (Number int PRIMARY KEY)", connection) testcmd.ExecuteNonQuery() testcmd.Dispose() testcmd = Nothing
Dim dtTemp As New DataTable Dim daTemp As New Odbc.OdbcDataAdapter("SELECT * FROM [#TempTable]", connection) daTemp.MissingSchemaAction = MissingSchemaAction.AddWithKey daTemp.Fill(dtTemp) Dim cbTemp As New Odbc.OdbcCommandBuilder(daTemp) Dim viewTemp As New DataView(dtTemp, Nothing, "Number", DataViewRowState.CurrentRows)
Dim i As Integer For i = 1 To 1000 Dim test_number As Integer = CInt(Rnd() * 2000) If viewTemp.Find(test_number) = -1 Then 'Keep it unique Dim new_temp_row As DataRowView = viewTemp.AddNew() new_temp_row("Number") = test_number new_temp_row.EndEdit() End If Next
daTemp.Update(dtTemp)
'daTemp.Dispose() 'daTemp = Nothing
'cbTemp.Dispose() 'cbTemp = Nothing
'dtTemp.Dispose() 'dtTemp = Nothing
'viewTemp.Dispose() 'viewTemp = Nothing
Dim testcmd2 As New Odbc.OdbcCommand("DROP TABLE [#TempTable]", connection) testcmd2.ExecuteNonQuery() testcmd2.Dispose() testcmd2 = Nothing
'connection.Close() 'GC.Collect()
'Console.Write(".") run_count += 1 End While
End Sub
End Module
Usually the ".Update" triggers the exception, but sometimes the other sql commands do it. Have tried various experiments with disposing of objects immediately when finished, but no effect. Opening and closing the connection each loop seems to delay the errors, but it still happens eventually.
When our administrators login on the workstation the application works well. But when ordinary users login they get the following error. (We only have 1 domain)
SQLState: 28000
SQL Server Error: 18452
Login failed for user ". The user is not associated with a trusted SQL Server connection.
Then the standard SQL Server Login window pops up asking for the Login ID and Password. On the window the 'Use Trusted Connection' is checked and the name of the user on the workstation appears on the LoginID. What we do is uncheck the 'Use Trusted Connection' then login using the credentials above.
I keep getting this error: OLE DB error: OLE DB or ODBC error: You do not have permission to run 'SP_TRACE_CREATE'.; 42000
I do not want to add the login account to sysadmin role on my production server and giving the logon account db_reader rights to my database is not working. Is there another way around it.
We have a SQL database that uses Active Directory with Windows Authentication. Can users that are members of the Active Directory group that has read/write access to the SQL database create ODBC connections to access the database directly and update the data? They dont have individual logins on the server. They are only members of the Active Directory group that has a login?
I need detailed instructions on how to connect to a database from a Microsoft Access 2007 database to a Microsft Office Accounting 2007 database. The accounting database is an SQL 2005 datbase. It has an instance name of "MSSMLBIZ".
When I try I get an SQL error 53. Do not have permissions or database does not exist.
I have been searching high and low for days and I am perplexed and appalled at the lack of information regarding what can not be an isolated incident.
We are trying to get an Analysis Services 2005 to process on a x64 server. We have both versions of the Oracle client installed and .ora file in both places. I have seen a couple of posts regarding this issue, but they are 2 years old and MS was supposed to have resolved the 'parentheses' issue long ago.
The test connection succeeds, and I can explore the data in the datasource view, but I cannot process the cube. All I get is the "OLE DB error: OLE DB or ODBC error: Class not registered"
Microsoft Windows Server 2003 R2 Enterprise x64 Editon Service Pack 2
Installed Oracle Client 10g and ODAC home
I tried a few things that were suggested in posts, but nothing has worked. I tried the cmd line starting SSMS from progra~2 instead of (x86). I tried renaming the directory with no parentheses. This is the second time we've tried to get it to work in 2 years. We'll probably give up again and stay with x86, um, because it works without all these silly mickey-mouse tricks. Most of our relational DBs are ORACLE so this is a showstopper for us as far as trying to go x64.
Sorry for the attitude, but I'm really frustrated!
If anyone can tell me a way to resolve this (or that it can't be resolved), I'd really appreciate it!
I got this error message while I was trying to backup the last transaction log before I start restoring a database that is marked SUSPECT. SQL Server is running on Windows 9x. Please how can I handle it because I can't even restore the db. Thanks for your help!
Server: Msg 4060, Level 16, State 1, Line 0 [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database requested in login 'Memphis. Login fails.
We are using ASP to connect to a remote database running on SQL server 7.0. On our testmachine we get no trouble, maybe because the SQLserver and Webserver is running on the same machine. But when we upload our code to a webserver and make a copy of our database on a remote SQLserver we get this error :
Microsoft OLE DB Provider for ODBC Drivers error '80040e37'
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'Seksjon'.
As we are working on a student project and our deadline is tomorrow, any help whatsoever would be of great assistance!!
When I use the dsn to connect to the sybase system I get this error The setup routines for the sybase system 11 odbc driver could not be loaded due to system error code 127.
It also gives the following message when I hit ok for the above message Driver's configdsn,configdriver or config translator failed could not load the setup or translator library.
Hi All, I have a database using Access 2003 as a front end and SQL as a backend. I set up all permissions in SQL and linked all tables to the Access frontend. After putting the front end on the network for other users, they receive the following error: ODBC — connection to <name> failed. (Error 3151) What do I need to do please
Hi guys, I have not posted to this site before, but I am wondering if someone knows about DTS ODBC source files and maybe if I am having some kind of permsissions problem.
I am trying to create a DTS import through SQL Server 2000 and pull data via an Advantage Database ODBC. I can seem to get it to work on a remote server with the Management tools installed, but if I try to schedule it as a task it fails.
Anywas the files are on one server and the odbc is installed coorrectly, but when i try to import the tables I get this error message:
http://qa3.com/images/sqlbomb.bmp
Any one know why this is happening?
My goal is to set a scheduled task to import these tables every night from an export that is written by another team.
All, I have SQL 2005 on a virtual server. I have an access frontend and SQL backend. I need users to test the database I am working on. I gave the permissions to access the database. Now, I am trying to set up the odbc connection but I get an error:
Connection Failed: SQLSTATE: '01000' SQL Server Error: 233 [Microsoft] [ODBC SQL server driver][DBNETLIB]Connection open (PreLoginHandshake()) Connection failed: SQLState: '08001' SQL Server error: 11 [Microsoft] [ODBC SQL server driver][DBNETLIB]General Network error. Chcek your network documentation
Is there something am missing because this is a virtual server? Is it considered a remote connection and I need to do something else that am not aware of? Thanks
I am using Windows XP Pro to remotely connect to a Windows 2003 Server/SQL Server 2005 database. This connection works fine for some, but not all, remote PC's. On the PC's that have a connection failure I get the following error:
Microsoft SQL Server Login
Conection Failed:
SQL State: '28000'
SQL Server Error: 18452
[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user ''. The user is not associated with a trusted SQL Server connection.
I have looked up this error and most people suggest using mixed mode authentication, which I already am. This odbc source is logging in with a SQL Server account. The account information works correctly on some machines with the same ODBC connection properties as the PC's that fail.
The SQL Server 2005 machine is on an Active Directory Domain, but the PC's are on a remote workgroup environment.
When I look in the Event log for the SQL Server machine, the following error is also displayed.
Source: MSSQLSERVER
EventID: 17806
SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security. The connection has been closed. When looking up this error, people usually descibe firewall issues. But there is no firewall running on the SQL Server machine and the networks between the remote pc's and the SQL Server machine have hardware VPN's. Any help would be appreciated. Michael Pusatera
I have a ASP.Net application. I'm trying to access access data using SQL Server my web config has <add key="connectionString" value="DRIVER={Sql Server};Server=(local);initial catalog=ymquizco_registration;User ID=sa;pwd=test"/> MY CONNECTION STRING HAS THIS VALUE "DRIVER={Sql Server};Server=localhost;initial catalog=ymquizco_registration;User ID=sa;pwd=test" But the conn.Open();is throwing this error: {"ERROR [28000] [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'WORK\ASPNET'. ERROR [01S00] [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute ERROR [28000] [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'WORK\ASPNET'. ERROR [01S00] [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute" } My SQL Server is configured at mixed mode authentication. This seems like a install issue. Can someone think of something.
Error when i try to execute a SP with ADO connection, or ADO COMMAND [ODBC SQL Server Driver][SQL Server]The identifier that starts (XXXXXX)is too long. Maximum length is 128. can anyone help me.
