Problems Connecting To SQL Server 2005 From C# Code
Jan 31, 2008
I have an ASP.NET application that access an SQL Server 2005 DB. I develop my C# code using MS Visual Studio. I was happily developing and testing for many months on my machine and then I lost a hard disk. I've replaced the hard disk and reinstalled everything and am getting back to my work. Now though when I try to open the database in my code I get an error saying it was unable to connect to the database perhaps due to SQL Server 2005 not being configured for remote access.
I can see the database using MS SQL Server Management Studio Express and open it. The properties shows the box checked to allow remote access. I restored the database from another hard drive so it should be no different.
I dont' recall having to do anything special the first time to access my database from my code. If I did I forget. What could be causing this? My code hasn't changed so the connection string is the same as is the location of the database.
Hi all--I'm trying to convert a function which I inherited from a SQL Server 2000 DTS package to something usable in an SSIS package in SQL Server 2005. Given the original code here: Function Main() on error resume next dim cn, i, rs, sSQL Set cn = CreateObject("ADODB.Connection") cn.Open "Provider=sqloledb;Server=<server_name>;Database=<db_name>;User ID=<sysadmin_user>;Password=<password>" set rs = CreateObject("ADODB.Recordset") set rs = DTSGlobalVariables("SQLstring").value
for i = 1 to rs.RecordCount sSQL = rs.Fields(0).value cn.Execute sSQL, , 128 'adExecuteNoRecords option for faster execution rs.MoveNext Next
Main = DTSTaskExecResult_Success
End Function
This code was originally programmed in the SQL Server ActiveX Task type in a DTS package designed to take an open-ended number of SQL statements generated by another task as input, then execute each SQL statement sequentially. Upon this code's success, move on to the next step. (Of course, there was no additional documentation with this code. :-)
Based on other postings, I attempted to push this code into a Visual Studio BI 2005 Script Task with the following change:
public Sub Main()
...
Dts.TaskResult = Dts.Results.Success
End Class
I get the following error when I attempt to compile this:
Error 30209: Option Strict On requires all variable declarations to have an 'As' clause.
I am new to Visual Basic, so I'm on a learning curve here. From what I know of this script: - The variables here violate the new Option Strict On requirement in VS 2005 to declare what type of object your variable is supposed to use.
- I need to explicitly declare each object, unless I turn off the Option Strict On (which didn't seem recommended, based on what I read).
Given this statement:
dim cn, i, rs, sSQL
I'm looking at "i" as type Integer; rs and sSQL are open-ended arrays, but can't quite figure out how to read the code here:
This code seems to create an instance of a COM component, then pass provider information and create the recordset being passed in by the previous task, but am not sure whether this syntax is correct for VS 2005 or what data type declaration to make here. Any ideas/help on how to rewrite this code would be greatly appreciated!
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 had SQL Server Express Edition installed. I then uninstalled both it and Visual C#. I then installed SQL Server 2005 Developer's Edition and reinstalled Visual C# -- both on the same machine. I can connect to SQL Server 2005 using SQL Server Management Studio. However, Visual C# is a different story. When I try to add a new Data Connection, it defaults the data source to .SQLEXPRESS, which is no longer on my machine. I can select .MSSQLSERVER, but when I click on either OK or Test Connection, I time out with an error message -- error 25 - Connection string is not valid. The connection string that is shown at the bottom of the Advanced dialog box is -- Data Source=.MSSQLSERVER;AttachDbFilename=E:InventoryDataInventory_Data.MDF;Integrated Security=True;Connect Timeout=30;User Instance=True
ok so i have set up SQL server 2005 on a Windows server 2003 machine. I am trying to connect to it via ODBC and/or Visual Studio 2005 on a computer running off the same switch. I have set SQL server to accept remote connections and named pipes as well as had the port unblocked. when i try and connect to it via Vista ODBC wizard or visual studio wizard it says that the server is not there or access is denied.
The server is set up for SQL authentication and i am 100% pos that the username/password i am using is correct. i am at a total loss as to what to do to get my vista machine to talk to that SQL server.
We are using VB.NET 2005 (Winform) and the backend SQL Server Express 2005. We would like to connect the Express (.mdf) database from Remote Machine. What type of connection string we have to use?
We tried the following ConnectionString but we got the error: Provider=SQLNCLI.1;Server=.SQLEXPRESS;AttachDbFileName=S:MLJData.mdf;Database=MLJData;Trusted_Connection=Yes;
Also suggest what are all the prerequisites to run sql server express 2005 database in client machine.
We did installed the following tools in client machine:
I'm getting a code page conflict when I try to import the data into SQL Server. This happens when I edit the OLE DB Source component:
Code Snippet The component reported the following warnings: Warning at {47FF55CB-AA24-45A4-B0DC-2807EC6D3EC1} [OLE DB Source [3570]]: Cannot retrieve the column code page info from the OLE DB provider. If the component supports the "DefaultCodePage" property, the code page from that property will be used. Change the value of the property if the current string code page values are incorrect. If the component does not support the property, the code page from the component's locale ID will be used.
and at package validation level when trying to run:
Code SnippetError at Data Flow Task [OLE DB Destination [970]]: Column "ACRC10" cannot convert between unicode and non-unicode string data types.
I've tried using the default code page on the component, that doesn't work. I've tried changing the code page to 285 (which is what it is on the AS/400), that doesn't work.
I am getting an sql Server 2005 connection error from c#.net 2005.
following is the 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)"}
i have changed the default settings. local and remote connection are enabled.
following are the code i am using in C# .Net 2005 --------------------------------------------------------------------------------------------------------------- using System; using System.Collections.Generic; using System.ComponentModel; using System.Data; using System.Drawing; using System.Text; using System.Windows.Forms; using System.Data.SqlClient;
SqlConnection conn = new SqlConnection("server=localhost; user id= sa; pwd =; Initial Catalog=testdb;");
Is there any way to connect to Hosting SQL Server using VS 2005. I have only VS 2005 on my computer and Dont have SQL Server. I have a SQL Server credentials on the Hosting server but the problem is the hosting website control panel didnt provide any enterprise manager to work on the database. Thanks in advance.
Hoi, Can someone help me? I have made a website with a database. Local on my pc all work fine. but now i need to set it op on my webhost. all pages with no database access work but the ones with database controls i get : Server Error in '/' Application.
Login failed for user 'username'.. I got from my webhost: db server:
I installed the SQL Server 2005 Trial and am now having trouble connecting. When I bring up the ASP.NET Configuration tool and Go to "Provider configuration" "Select a single provider for all site management data" AspNetSqlProvider Test I get the following message. "Could not establish a connection to the database. If you have not yet created the SQL Server database, exit the Web Site Administration tool, use the aspnet_regsql command-line utility to create and configure the database, and then return to this tool to set the provider. " I have already run the aspnet_regsql command-line utility. Can anybody give me some information on how to set this up. I am currently working with the club web site starter kit.
I have a VB.Net Winform application installed at a client’s site using .net 1.0 and sql server 2000. I am in the process of upgrading to them to sql server 2005. The installation of sql server 2005 is on a different machine then the 2000 version. I have installed SQL Server 2005, SP2 and converted the database from SQL Sever 2000. Everything is good at this point. I can even establish a connection through a user’s login.
The Problem is when I try to connect from a client machine using my .net 1.0 application. The client test machine that I am using is a Windows NT Server which may have something to do with the problem. Any way I am getting the following error message.
SSL Security error
From other topics I have read I believe this is something to do with a certificate. The application only needs to connect from within the local network. I have tried connecting using the ODBC Data Sources tool from the client machine I get the following error.
Microsoft SQL Server ODBC Driver Version 03.81.9001
Running connectivity tests...
Attempting connection [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SSL Security error
TESTS FAILED!
Should I be using the TCP/IP? Do I need to install anything on the client machines? Do I need to open ports on the firewall? Is there anything else that I am overlooking?
I am new to sql server 2005 and I am having some problems connecting to it. Hope you guys can help!
I have install the sql server management studio express. At the login page, there is one field which is Server name. However, in my studio express that field is empty. I believe that field should have my server name on it but it is empty. Due to the empty field in the server name, I am not able to connect to the server. Did I set up my server wrongly that explains why the server name field is empty???
HiWe are planning to move over to SQL Server 2005 in near future.At the moment Website is on a seperate server then the Database.OS for both the server is Window 2003 and currently our data is on SQLServer 2000(on which everything works fine).Part of the testing process we tried to connect our website on SQL 2005and it does not work at all.I get this----------------------------------------------------------------ADODB.Connection error '800a0e7a'Provider cannot be found. It may not be properly installed.When i use following connection string"Provider=SQLNCLI;Server=127.0.0.1;Database=dbName; UID=UserName;PWD=UserPassword;"(Above string has fixed problem for few people- googled it, but not forme.)--------------------------------------------------------------------------------------------------------------------------------This is the message i get for all the following connectiong stringMicrosoft OLE DB Provider for SQL Server error '80004005'[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist oraccess denied.1) - "Provider=SQLOLEDB.1;Password=UserPassword;Persist SecurityInfo=True;User ID=UserName;Initial Catalog=ABC;DataSource=XXX.XX.X.XX,1433"2) - "Provider=sqloledb;Data Source=XXX.XX.X.XX,1433;NetworkLibrary=DBMSSOCN;Initial Catalog=ABC;UserID=UserName;Password=UserPassword"3) - "Provider=SQLOLEDB.1;Persist Security Info=True;UserID=UserName;Initial Catalog=ABC;Data Source = ServerNameSQLInstance"----------------------------------------------------------------I tried connecting to SQL Server 2005 through our system developed inVB.Net 2003 and it works fine and here is the Connection String :"Data Source=ServerNameSQLInstance;Initial Catalog=ABC;PersistSecurity Info=False;user id=UserName;password=UserPassword"I would really appreciate any help.Mits
I want to connect to database using sql server 2005 through Visual web developer 2005 express edition . what will be the connection string for this....
Hi We are planning to move over to SQL Server 2005 in near future.
At the moment Website is on a seperate server then the Database. OS for both the server is Window 2003 and currently our data is on SQL Server 2000(on which everything works fine).
Part of the testing process we tried to connect our website on SQL 2005 and it does not work at all.
I get this
---------------------------------------------------------------- ADODB.Connection error '800a0e7a' Provider cannot be found. It may not be properly installed.
When i use following connection string "Provider=SQLNCLI;Server=127.0.0.1;Database=dbName;UID=UserName;PWD=UserPassword;"
(Above string has fixed problem for few people- googled it, but not for me.) ----------------------------------------------------------------
---------------------------------------------------------------- This is the message i get for all the following connectiong string
Microsoft OLE DB Provider for SQL Server error '80004005'
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
I tried connecting to SQL Server 2005 through our system developed in VB.Net 2003 and it works fine and here is the Connection String :
"Data Source=ServerNameSQLInstance;Initial Catalog=ABC;Persist Security Info=False;user id=UserName;password=UserPassword" Then i downloaded SQL Native Client and installed on the web server.
I looked in SAC Tool and "Local and Remote Connection" and "Using Both TCP/IP and Named Pipes" options are selected. I have checked SQL Browser service is running.
I have searched the web and this forum relentlessly for past 2 days but I haven't been able to solve the problem.
Here is the description
I work for company X and log on to my computer with my credentials Xme. Now I have the ability to log in into my customers environment using VPN. I can do this by logging in into the customer network by another set of credentials Yme2. (where Y is customers domain and me2 is the id given to me by the customer)
Post this, I am able to ping the customers server.
Now when I use SSMS to connect to sql server, I get the error message"Login failed for user Xme"
Why doesn't SSMS ask me whether I want to use Xme or Yme2 credentials? why doesn't SSMS try with Yme2 credentials? Why does SSMS only use Xme credentials?
I also tried to run SSMS as Yme2 but that also didn't work.
It will be kind if you could let me know how can I specify what credentials should SSMS use.
My site works fine in VWD2008 express, but I get this error when I try to use it on my live website. 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. According to this article: http://support.microsoft.com/kb/914277 I am supposed to:
1. Click Start, point to Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Surface Area Configuration. Ok, there is no such program in this folder. The only thing in there is "SQL Server Error and Usage Reporting"... The other thing I am greatly concerned with is this: All is want is for my webpages to be able to access my database for user authentication. I DO NOT want to grant the internet rights to remote connect to my database.
In my webconfig file I have this. <add name="vau" connectionString="Data Source=.SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|vau.mdf" providerName="System.Data.SqlClient"/>
I understand that there are several different ways to connect and manage information to the database. I think I want to use the behind the codes (.aspx.vb) and on the top of the page I have this. Imports System.Data.
That is where I am stuck. Can you push me in the direction by either explaing to me or post a link that has more information about this.
I have not been able to find any substantive documentation on connecting a DataSource to the database via the IP address of the SQL Server. Does anyone know of a good reference on the topic? I want to be able to access the data on the server while developing and testing locally on my laptop (not on the same network).
Hi All, I have a problem with Sql Server 2005. When I deploy Web Application (ASP.NET 2.0 using Sql Server 2005) on server, There is a problem while connecting to the database. The problem is some thing like Sql Server 2005 is not accepting Remote procedure calls. What should I do? Please help me out in solving this problem.
My environment: Home PC Vista Ultimate SQL Server Developer 2005
I'm about to go absolutely nuts. I've tried so many things including: 1) Of course making sure Remote connections and both TCP/IP and named pipes are enabled for SQL 2005 2) Verified my connection string works. I even tested it in Enterprise Library using the tool and it connects successfully via windows authentication 3) Made sure of course my logged in user is a member of the administrator group and that my user in SQL 2005 logins has db_owner and full rights to the DB I am connecting to. I also made sure the NT AUTHORITY as well as the 3 sql service users have db_owner rights as well as the adminstrator in the SQL Server logins all have db_owner to the DB 4) Started the SQL Server Browser service, SQL Server DB engine, and SQL Server Agent 5) Made sure my site is setup right in IIS 7. I checked the connection string in there as well as it shows up in IIS7 in one of the sections. Using Windows authentication and it is enabled for my site 6) Tried running the .net site using both localhost (IIS) and also tried using the Visual Studio built-in web server. Both give this message still When I test my connection through Enterprise Library it shows test successful!
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) 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.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)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:
[SqlException (0x80131904): An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)] System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +800131 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +186 System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject) +737554 System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject) +114 System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart) +381 System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +181 System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +173 System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +357 System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +30 System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +424 System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66 System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +494 System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +82 System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105 System.Data.SqlClient.SqlConnection.Open() +111 System.Web.SessionState.SqlStateConnection..ctor(SqlPartitionInfo sqlPartitionInfo) +79
Hi - I have Web Developer, SQL Express 2005 running locally on my pc, and on my remote server. Everything is fine locally, but when I copy my files over to my server (have setup a virtual dir, and ensured it is running .net2) I get the following message when trying to connect: An attempt to attach an auto-named database for file C:websitessicknessApp_DataDatabase.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share. I have tried attaching and detaching the database from within SSME on the server - my connection string is: <connectionStrings> <add name="SicknessConnectionString" connectionString="Data Source=.SQLEXPRESS;AttachDbFilename=|DataDirectory|Database.mdf;Integrated Security=True;User Instance=True" providerName="System.Data.SqlClient" /> </connectionStrings> I've tried it with and without the User Instance = True set Has anyone got an actual fix for this? Thanks, Mark
I had been using Excel to connect to SQL server. This worked merrily for about 6 months then I had reason to reinstall Visual Studio.
Now I've reinstalled that, my connection between Excel ans SQL Server won't work. I thought the ADO code I had put in my VBA macro would be sufficient to connect, but obviously I need to do something else, but what? Please help!
Do I need to create an ODBC connection in Control Panel? Or something else?
The code is unchanged from before and the VBA project does reference the ADO object Library.
Hi Everyone, i would like to know if we can connect from SQL Server 2005 to PostgreSQL at Database level without using any programming language , like we do connect from Oracle to Oracle.?
When I try to attach an ".mdf" to a project by right clicking on the project name the software looks for an instance of SQL Server 2005 Express. How do I alter this behavior to have it look to my full copy of SQL Server 2005 which appears to be working correctly?
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)
I am having major issues connecting to SQL Server 2005 Express from Visual Basic 2005 Express, which I have tried on multiple PCs but to no avail. Can somebody please explain to me what I'm doing wrong?
1) I install SQL Server 2005 Express and Visual Basic 2005 Express (With .NET framework and SQL native client of course) 2) I open SQL Server using Management Studio and going in with windows authentication. It automatically sets the log on name to computernameSQLEXPRESS. 3) I create a new database called Test and add one table to it 4) I go into Visual Basic 2005 and create a new project. 5) I go to the projects application settings (Properties - Settings). 6) I set up a new connection string, choosing SQL server as the conection type and then on the Connection Properties window it asks me to select the mdf file for the database. I choose the file Test.mdf from the directory C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLData 7) I click on Test Connection.
When I do this on two out of the three home PCs I get the error: Unable to open the physical file "C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDataTest.mdf".Operating system error 32: "32 (error not found)". An attempt to attach an auto-named database for file C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDataTest.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.
The third PC gives me a different error:
Cannot open user default database. Login failed. Login failed for user 'DAVEDavid'.
I get the same errors when I try to use a connection string inside the code directly. Does anyone have a clue as to why these errors are occuring? Do I need to set up security or something else on the database first, or is there another reason? If anyone can please help me get to the bottom of this or provide a web address where I can get the answer (step by step instructions on how to connect) then I would be most grateful.
I have set up a SQL Server 2005 to use for testing before moving to another production server. The server works fine when I connect to it with a program on the same computer but not when accessed remotely.
I have set it to to allow remote connections and use TCP IP only and have opened TCP port 1433 on the Windows XP firewall and am using the Teredo service on Port UDP 3544 Also the Server Browser service is running. The server is connected directly to the internet on a static IP (eg. 67.156.18.167) I have set the server to Windows authentication.
When I try to connect to the database from a data grid in Visual Studio on another computer it fails.
I am pretty surethat the problem is that I am not giving the correct information when asked to fill in the information for the data source to find the server as I am new to remote connections in SQL Server.
I am trying to return multiple recordsets to a classic ASP web page from SQL Server 2005 and then use GetRows() in ASP to fill 2 arrays with the data. I'm using a command object to run a stored procedure which performs 2 simple selects in SQL Server. The stored procedure works fine in SQL Server Management Studio so I'm guessing it's an ADO issue.
The ASP code looks like this: strConnect = "DRIVER={SQL Native Client};SERVER=MyServer.IsAtMyIsp.com;DATABASE=MyDb;UID=Me;PWD=MyPwd; MARS Connection=True;"
Set conn = Server.CreateObject("ADODB.Connection") conn.ConnectionString = strConnect conn.Open
Set objCommand = Server.CreateObject("ADODB.Command") Set objRecordset = Server.CreateObject("ADODB.Recordset") Set objRs = Server.CreateObject("ADODB.Recordset")
If Len(strBeginDate) And IsDate(strBeginDate) Then .Parameters.Append .CreateParameter("@i_DateStart",adDate,adParamInput,,strBeginDate) If Len(strEndDate) And IsDate(strEndDate) Then .Parameters.Append .CreateParameter("@i_DateEnd",adDate,adParamInput,,strEndDate) End If End If End With
I can connect to amachine using SQL server 2000 using IIS 6.0. However, I am having trouble connecting to my server that has SQL server express using IIS 6.0. I'm using similar setting for both servers. Is there something else i have to do for SQL server express?
I'm not sure why this is the case. Any information that could help resolve this failed connection would be greatly appreciated.
Unfortunately, this provider seems to behave different to the one i use in 32bit :
Lets say i have a stored procedure"
create spName as
select * from mytable
when i execute the following
<%sqlstr = "exec spname"
set myRecSet = CreateObject("ADODB.Recordset")
myRecSet.open SQLStr, myConn
response.write(myRecSet(0)) %>
it gives the first value of the first row with the Connection to a 32bit SQL-Server
but myRecSet seems to be empty on my 64bit SQL Server the response.write leads to an error message.
As far as i understand this, the provider used when connecting to a 32bit Server returns the records selected by the last row of the stored procedure into the recordset, but the provider when connecting to a 64bit server does not return these results.
What can i do, if i dont want to rewrite my asp-programming. I hope somebody has the correct naming / syntax for an connection string which allows me to connect my asp-application to the 64bit SQLServer which behaves like the "old" one for 32bit.
I hope my comments are clear enough - english is obviously not my mother-tongue - and somebody can give me a hint.
