DB Connection From File Vs Local SQLServer Instance
Feb 12, 2007
I want to add a data source to a C# project that comes from a local SQLServer instance. But when I attempt to do a new connection, it only allows me to specify a file. That is, the only choices I have to select a data source type are "Access DB file" and "SQL Server DB file". I know that with the non-express VS edition there are more choices available. But reviewing limitations of express editions on the web, I find a frequent mention that one cannot access remote data, only a locally installed data source. But is not a SQL Server instance on my local machine a local data source?
This is an issue because if I proceed with connecting as a file, then VC#Express complains the file is in use. If I first go into SqlServer Expresss and detach the database there, then I can connect to it in VC#Express, but that is rather cumbersome!
So to put it another way, can I use this connection string...
Data Source=.SQLEXPRESS;Initial Catalog=testDB;Integrated Security=True
instead of this one?
Data Source=.SQLEXPRESS;AttachDbFilename=|DataDirectory| estDB.mdf;Integrated Security=True;Connect Timeout=30;User Instance=True
This is my first time to deploy an asp.net2 web site. Everything is working fine on my local computer but when i published the web site on a remote computer i get the error "Failed to generate a user instance of SQL Server due to failure in retrieving the user's local application data path. Please make sure the user has a local user profile on the computer. The connection will be closed" (only in pages that try to access the database) Help pleaseee
I am using the following C# code to establish a SQL connect to a SQL database file:
// connection string // attach a SQL database file to a local SQL server express instance string _connectionString = @"Server=.SQLExpress; AttachDbFilename=C:BalanceDatabase_1.mdf; Trusted_Connection=Yes; User Instance=True";
// using System.Data.SqlClient; SqlConnection _sqlConnection = new SqlConnection(_connectionString); // open the connection _sqlConnection.Open();
// do something
// close the connection _sqlConnection.Close();
So far, the connection works fine.
However, next, I want to copy the database file to another folder. So the following codes: // source database file name string sourceDatabaseFileName = @"C:BalanceDatabase_1.mdf"; // target database file name string targetDatabaseFileName = @"D:BalanceDatabase_1.mdf"; // copy database file System.IO.File.Copy(sourceDatabaseFileName, targetDatabaseFileName, true);
Then the program came with runtime exception: "IOException was unhandled: The process cannot access the file 'C:BalanceDatabase_1.mdf' because it is being used by another process."
Is it because the database file was sill attached to the local SQL Server express instance? What can I do to bypass this problem? Detach the database file? or dispose the local SQL Server express instance?
I've two instances(Default, Named[dynamicsFINANCE]) running on SQL server 2014. However, when I try to connect to named instance say (dynamicsFINANCE) using SQL authentication from local SSMS, I get below error message:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
I assigned a static port number to the named instance [dynamicsFINANCE] 1450. I also setup the firewall rule to allow access to Port 1450.
Hi experts, I have sql express installed on my machine and i'm using visual studio to create database files. After i've build a connection to my database file thru Server Explorer (choose Add attach files) i opened Management Studio Express and found that the new database has been attached to sqlexpress database engine----technically speaking it's under the user instance which i use to run my visual studio. right?? that's totally fine.My question is, after i'v closed the connection in visual studio, that attached database file still exist.I want it to be detached immediately after i've closed the connection in visual studio.How can i do that? I've searched through internet and was told that sp_config can solve this problem by setting the user instance time out. I ran sp_config against my database but did not find that item. Could anybody give me some directions? thanks in advance.
I have a SQL2K server installed , and it is given an instance name (like BoxSQLInstance). I have a connect string looking for "local" server, is it possible to make this instance name as the default local server ?
I am working on an existing project that uses sql server 2014 local db. I've installed it (there was no option to set an instance id). Using sql server 20014 management studio and setting the server name to (localdb) results in this error
Network related or instance specific error occurred while establishing a connection to sql server.......
So obviously its not there, how can i test this? There's no service I can see. The installation procedure completed without any errors, what could be going on here ?
I have just recently installed MS SQL Server 2005 Developer edition. I have installed SP2.
Today when I try to connect via Management Studio, I get the following 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: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (.Net SqlClient Data Provider)
I installed it as a default instance.
I recently added a login with dbo privileges. I have tried logging in with that sql account and also with windows authentication to no avail.
(New to SQL Server Installs)I installed SQL Server 2005 Developer Edition on a WinXP-SP2workstation and can see some enterprise databases on the network justfine.My problem is I cannot register a local database on the local drive fortesting/education purposes.(I accepted all of the defaults on the install and thought all waswell.)There are a couple of small databases that are in development in ourgroup and I need to work on when offline from the network.Short of uninstalling the whole product and doing it over, what stepscan I take to remedy this so I will be able to work with DB's locally?Thanks.
I have two databases (A and B )on the same SQL Server instance. Both have SSB enabled and running fine within themselves. All athorizations are at present set to dbo.
Recently I had a requirement to start a dialog and send a message from within data base A to a queue via a service that is in database B.
I tried coding the SSB instance in the BEGIN DIALOG then I set up a route and tried that. On both occoasions I got the following on sys.transmission_queue
"An exception occurred while enqueueing a message in the target queue. Error: 916, State: 3. The server principal "sa" is not able to access the database "B" under the current security context."
Is this sometjhing to do with security lock downs in 2005?
I have verified that the following services ARE running.SQL Server (SQLEXPRESS)SQL Server Browser SQL Server VSS Writer.This one however will not start ... For some reason it starts then automatically turns off.SQL Server Agent (SQLEXPRESS).When I try to connect using my <machine name>/instance and Windows Authentication I get the following error ...
"A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server)".The connection specified in the "Connect to Server" box was working perfectly fine before I upgraded. I thought it might have been my Norton 360 Premier but I uninstalled it.I AM having issues with the adapter frequently dropping the internet connection but I just disconnect and reconnect and that resolves itself.The other technique I tried was to replace the server name with the IP address ... <192.168.0.22>/Instance ... This actually seemed to find the SQL Server but rejected the Windows Authentication ...
"Login failed. The login is from an untrusted domain and cannot be used with Windows authentication." I have several databases on here and would hate to have to reinstall SQL Server and manually hook them back up.
Hi, I've installed SQL Server 2005 Express Edition, SQL Server Management Studio Express using Windows Authentification and IIS 5. The problem occurs when I try to access the default address of my local computer to test my installation. I've tried with both http://localhost and http://127.0.0.1. The system requires a password despite I don't use password for my Windows Authentification. Does IIS always demands a password regardless my settings for Windows Authentification or?
I am using the following connection string to connect to SQL Server 2005 Express Edition installed on my local PC. string sqlstr = "Server=(local);Database=MyDB;User ID=sa;Password=sa;Trusted_Connection=False";
And it gives me the following error. The string works fine in computer with SQL Server 2000 instance but fails with 2005. The string also fails for "Server = localhost". However the string works very fine if I use the name of Server 2005 i.e ./SQLExpress
===================================
Cannot connect to (local).
===================================
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) (.Net SqlClient Data Provider)
Now the main problem is that, of course I could use a named instance, but since I am embedding the Connection String in a dll file so that any user can use it to connect it to the local instance of the SQL Server 2005 installed in his/her computer, I need to use "server = localhost". Doesn't SQL 2005 support this. If yes, where could i find option to enable it?
I have enabled every option available in surface area configuration for SQL Server 2005, but nothing seems to help out. I even use local as well as remote connections using both TCP/IP and named pipes. Can nyone help me out?
Just when I think I have this stuff figured out, it bites me back everytime.
I'm trying to deploy an mdf out to a different machine, and attached to it with local user instance. I connect without problem from my development machine with a local user instance, which also has Express Manager resident, and I can connect to a server instance without problem.
What I can't do is copy the .mdf database over to another workstation, which has Sql Native Client installed, and connect to the database using a local user instance! I can connect to a server instance without problem from this other workstation. Here's my connect string for local user instance that works fine from my dev machine:
Provider=SQLNCLI.1;Persist Security Info=False;Integrated Security=SSPI;Data Source=.sqlexpress;AttachDBFileName=<full path_name and mdf filename>;User Instance=true;
The error I get upon trying to connect with other stations is:
Error -2147467259 Database not found or cound not connect to database
I've tried this every way I know how. I've copied the database from my dev machine both with and without having detached the database from the local instance. I've tried detaching from a server instance and copying the file over. Nothing works, and I've done this before! What gives with this thing?
We are using the Windows Task Scheduler as a substitute for the SQL Server Agent, which isn't available in the Express edition. The scheduled task just calls a batch file, which in turn, runs a stored procedure using osql with the -E option for a Trusted Connection.
SQL Server Express has been installed using the defaults, which means the service is running in the "NT AUTHORITYNETWORK SERVICE" account. The scheduled task we create is set to run using the "NT AUTHORITYSYSTEM" account.
Now we find that on Windows Vista (tested using Ultimate Edition) that the scheduled task fails to run the stored procedure until the machine is rebooted the first time after installing SQL Server Express. When I say "fail", I mean that the stored procedure isn't executed. The scheduled task however completes and reports no errors. On Windows XP, we do not run into this problem so I suspect it has something to do with the UAC in Vista?
We further found that after installing SQL Server Express and creating the scheduled task in the "NT AUTHORITYNETWORK SERVICE" account, the scheduled task (and stored procedure) runs fine WITHOUT requiring a reboot.
Can anyone explain why a reboot is needed to get SQL Server Express to run the scheduled task correctly under Windows Vista and the SYSTEM account?
I created a single step plan that does integrity checks. It fails with the error below. I created a new connection using our clusters virtual sql name.
Executed as user: ACCTCOMsqlagent. ...n 9.00.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 1:10:06 PM Error: 2008-02-15 13:10:49.02 Code: 0xC00291EC Source: {0CF32F3D-A8D1-492A-9C0F-AD4E0FC67D14} Execute SQL Task Description: Failed to acquire connection "Local server connection". Connection may not be configured correctly or you may not have the right permissions on this connection. End Error Warning: 2008-02-15 13:10:49.02 Code: 0x80019002 Source: OnPreExecute Description: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. End Warning Error: 2008-02-15 13:11:31.26 Code: 0xC0024104 Source: Check Database Integrity Ta... The package execution fa... The step failed.
The agent and db are running under domain accounts and the job is owned by sa.
Let me set the stage of my testbed configuration: On Windows XP SP2, my default connection to the Internet is via wireless express card modem using EV-DO via Verizon Wireless. Let's call this connection A. I also have a traditional wireless network connection (802.11g) that is always enabled. Let's call this connection B. Connection A is always connected during normal business hours. Connection B is not and is often searching for a wireless network to connect to when nothing is in range.
Yesterday, connection B was continuously trying to connect to a wireless network not under my control, meaning that the connection was never established and notification messages continually popped up to complain of this fact. Over time, I've learned to ignore these messages and go on doing my daily work without much thought of the possible implications.
Then, things started to get odd. I was running our application, WebWatchBot, to perform some simple tests of various websites and servers, when I started to get messages from the application that database connectivity was lost, which is a message that pops up to inform the user that the connection is forcibly dropped by SQL Server. After a few moments, the connection to the database was re-established and the message went away. Since I was actually working with SQL Server, I thought it was an anomoly, so I continued on. Then, it happened again. And again. Then, I noticed that the "database connectivity lost" message started to coincide with the wireless connection's (connection B) inability to connect with a wireless network.
Why would this be happening? The database and application are on the same exact computer. The connection to the database is via ODBC drivers over tcp/ip, but why would connection B affect this?
Some added information that may prove useful:
Client side:
What is the connection string in you app or DSN? (please specify) DRIVER=SQL Server;SERVER=HIGHNOTEWEBWATCHBOT;Database=WebWatchBot;UID=sa;PWD=*****
If client fails to connect, what is the client error messages? (please specify) [Microsoft][ODBC SQL Server Driver]Communication link failure
Is the client remote or local to the SQL server machine? [Remote | Local] Can you ping your server? [YES | NO ] In cmd.exe console, type €œping -a <server_name>€?.
Can you telnet to your SQL Server? [YES | NO, please specify the error message ] In cmd.exe console, type €œtelnet <server name> port, where port can be 135, 445 or sql_server_tcp_port. If your cmd.exe console turns into a complete black screen with a cursor flushing on top left corner, you are connected. Type ctrl+€™[€˜ to bring up telnet prompt and type €œquit€? <enter>.
What is your client database provider? [SNAC | MDAC | ADO.NET1.0 | ADO.NET2.0| other (please specify] Or/And, what is your client application? [SQL Management Studio | SQL Profiler | Visual Studio | Other (please specify): WebWatchBot - Website and Server Monitoring Software Is your client computer in the same domain as the Server computer? (Same domain | Different domains | WorkGroup) What protocol the client enabled? [Shared Memory | TCPIP | Named Pipes]. Do you have aliases configured that match the server name portion of your connection string? NO Do you select force encryption on server and/or client? NO [2] Server side:
What is the MS SQL version? [ SQL Server 2005 | SQL Sever 2005 ] What is the SKU of MS SQL? [Enterprise | Standard | Workgroup | Express (or MSDE) | other (please specify)]. Microsoft SQL Server Management Studio 9.00.3042.00 Microsoft Analysis Services Client Tools 2005.090.3042.00 Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158) Microsoft MSXML 2.6 3.0 4.0 5.0 6.0 Microsoft Internet Explorer 7.0.5730.11 Microsoft .NET Framework 2.0.50727.832 Operating System 5.1.2600
What is the SQL Server Protocol enabled? [Shared Memory | TCPIP | Named Pipes ]. Use SQL Server Configuration Manager to configure it and check ERRORLOG or event log to confirm. Does the server start successfully? [YES | NO] If not what is the error messages in the SQL server ERRORLOG? If SQL Server is a named instance, is the SQL browser enabled? [YES | NO] What is the account that the SQL Server is running under?[Local System | Network Service | Domain Account] Do you make firewall exception for your SQL server TCP port if you want connect remotely through TCP provider? [YES | NO | not applicable] Do you make firewall exception for SQL Browser UDP port 1434? In SQL2000, you still need to make firewall exception for UDP port 1434 in order to support named instance.[YES | NO | not applicable ] [2a] Tool Used to Connect
What tool or Application are you using to connect to SQL Server (eg: Visual Studio, SQL Server Management Studio, SQLCmd.exe, OSQL, etc) and especially the version of SQL Server (Express, Workgroup, Standard, Enterprise, Developer)
[3] Platform:
What is the OS version? [Windows XPSP2 | Windows 2003 | Windows 2000 | Windows 98 | others (please specify ) ]. Do you have third party antivirus, anti-spareware software installed? [Symantec | Norton | other (please specify)].
We are seeing some very strange behavior on installation for our application when it is trying to enumerate the available SQL Server instances. On some machines (not yet determined why) the SQL Browser service is apparently able to locate remote instances but not the local instance. This does not seem to map to any firewall or TCP/IP settings which we can determine. We have gone to the extent of uninstalling all associated firewall and antivirus products, and the problem persists.
For the moment, we are working around this problem by interrogating the registry for the instances installed locally, but this seems unsatisfactory in the long run. Is there any possibility that other instances of SQL Server Express or MSDE have somehow disabled our ability to see local instances? I would really like to find a better solution to this problem.
Not sure if this is the right place for my question but here goes anyway.
I have an instance of SQL Server 2005 installed on my DEV PC. A colleague of mine wants to access my server from his machine which connected to the same network.
I logged on to SSMS and added him as a new login.
Will he be able to connect to it now or do I have to do more than just that?
I'm getting "Access denied" error when I try to connect to SSIS from my desktop (Database Engine is fine). I'm a member of sysadmin within SQL, as well as an administrator on the server. I don't have any problem when I log on to the server directly via Remote Desktop and open SSIS.
I went into the surface area config tool, and I see that Database Engine and Analysis Services both expand and have a sub tabs to enable Services and Remote Connections, but Integration Services does not expand to a Remote Connections option, just Services. We're running MSDN Enterprise edition.
Does it matter if all the SQL services are using "Local System" for the logon ? I use an administrative logon on my SQL2000 boxes, and was fiddling with them on the 2005 box yesterday, but it seemed to cause more problems, so they are all Local System for now.
I have been reading through the article pointed to by the link below on msdn and its documented that one functional limitation of user instances is "Only local connections are allowed." I didn't understand the technical details(meaning) of that limitation and hopefully some one might explain it to me so that i can understand it better.
Hello, PLEASE Help me.I have just installed the Quick Starts on my local machine, and it mentions that you will need a new instance of SQL called (local)/NetSDK.I already have the MS Personal Edition and the tutorials say to download the MS Desktop Engine. So what do i need to do in order to get teh Quick Start samples to work locally???Can i not just use my own instance and use the Grocer and other Databases there???Please Help
Hello all, I'm a bit new to SQL Server and T-SQL (my background is in DB2), so hoping you can help me with this. I'm writing a T-SQL script that's hopefully going to scan a bunch of SQL server instances and record the results. We've got a mix of SQL2K and SQL2K5 instances, and for part of my script I only want to run something if the remote instance is SQL2K.
I'd tested this on my local PC with several instances created and it worked fine. When I try and run it for instances located on other servers it barfs :eek: . From what I've found from looking up the error message it looks like I've got myself a loopback -- but I don't know how to get around it - any ideas please?
INSERT INTO @tempdata (scratch) EXEC ('[' + @server + '].master.dbo.sp_executesql N''SELECT SERVERPROPERTY(''''ProductVersion'''')''') SELECT @version = convert(varchar(100),scratch) from @tempdata DELETE FROM @tempdata IF @debug>0 BEGIN PRINT @server + ' is running SQL Server version: ' + @VERSION END IF charindex('8.00',@version) > 0 BEGIN PRINT 'SQL2K-only code goes here' END
The error I get is: OLE DB provider "SQLNCLI" for linked server "SQLSERVER_INSTANCE" returned message "The transaction manager has disabled its support for remote/network transactions.". Msg 7391, Level 16, State 2, Line 1 The operation could not be performed because OLE DB provider "SQLNCLI" for linked server "SQLSERVER_INSTANCE" was unable to begin a distributed transaction.
I get this error running from a SQL2K5 instance against both SQL2K or SQL2K5
First time I've tried doing this - I have SQL Server 2012 installed on my local machine with an instance running (which was set up under an administrator account, not mine, which has no admin rights), and I'm trying to create a linked table from Access (also on the local machine) to a table on the server.
I tried creating a DSN using Windows Authentication, using the server name which is the same as my computer name, and got the error "Error 18452, Login failed. The login is from an untrusted domain and cannot be used with Windows authentication".
I then created a SQL authentication user ID and password, and tried the same thing using that instead, and got "Login failed for user <myusername>"
Is there some particular setting on the local instance I need to change to allow this kind of connection, or do I need to use something other than the server name to connect, such as an IP address? Remember that I have no admin access on this machine so any solution would have to avoid requiring that.
I've two instances(Default, Named[dynamicsFINANCE]) running on SQL server 2014. However, when I try to connect to named instance say (dynamics FINANCE) using SQL authentication from local SSMS, I get below error message.A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)I assigned a static port number to the named instance [dynamicsFINANCE]Â 1450. I also setup the firewall rule to allow access to Port 1450.
I installed SQL 2005 Developer addition on my Vista laptop. When I open Management Studio to connect to the local instance of the DB, I get the error below. Why can't I access? Is there something with Vista that is prohibiting?
Thanks
TITLE: Microsoft SQL Server Management Studio ------------------------------
Login failed for user 'xxxx'. (Microsoft SQL Server, Error: 18456)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18456&LinkId=20476
I am using SMO EnumAvailableSqlServer to make a list of available SQL servers in local network. I have tested it in two different local networks. In the first all works fine, but in the second I have noticed that when disconnected from the network the call fails to even detect the locally installed sql servers. I know that I can scan registry to get installed local servers, but I want to know what could be making problem.
The box I am trying to connect to is running two instances of SQL Server. There is a SQL Server 2005 instance which is the default. There is a SQL Server 2000 instance which is named 'SQLSERVER'. I can connect to the SQL Server 2000 instance no problem:<add key="ConnectionString" value="server=MYPCSQLSERVER;database=mydatabase;user id=****;password=****" /> However, I am having trouble connecting to the Default SQL Server 2005 instance. I have tried: <add key="ConnectionString" value="server=MYPC;database=mydatabase;user id=****;password=****" /> but it doesn't work. I have tried explicitly setting SQL Server 2005 to use port 1434 (as SQL Server 2000 is running on port 1433), and then used: <add key="ConnectionString" value="server=MYPC,1434;database=mydatabase;user id=****;password=****" /> but this doesn't work either.
Am I mssing something here? Any help much appreciated Thanks...
my web app was working fine but as soon as i added in a page and few store procedures and 2 tables it just pop up with that error message. Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.
i did go into the folder C:Documents and SettingsdnguyenLocal SettingsApplication DataMicrosoftMicrosoft SQL Server Datasqlexpress and delete the directory but this didnt help much. I still get the same error message. please help
I have just reinstalled windows xp pro with service pack 2 and framework 2.0. I am using SQL Express and visual studion 2005. I am trying to run my website and i keep getting this error message, i followed few instructions but i still failed to make it work. could someone who faced similar issues guide me,
thanks
MM
Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed
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: Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.
Source Error:
Line 112: Public Overridable Property Theme() As String Line 113: Get Line 114: Return CType(Me.GetPropertyValue("Theme"),String) Line 115: End Get Line 116: Set Source File: C:WINDOWSMicrosoft.NETFrameworkv2.0.50727Temporary ASP.NET Fileswroxunitedeecd65d2e1a6a798App_Code.ws-dzmjl.6.vb Line: 114
Stack Trace:
[SqlException (0x80131904): Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.] System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +437 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.DataAccess.SqlConnectionHolder.Open(HttpContext context, Boolean revertImpersonate) +84 System.Web.DataAccess.SqlConnectionHelper.GetConnection(String connectionString, Boolean revertImpersonation) +197 System.Web.Profile.SqlProfileProvider.GetPropertyValuesFromDatabase(String userName, SettingsPropertyValueCollection svc) +766 System.Web.Profile.SqlProfileProvider.GetPropertyValues(SettingsContext sc, SettingsPropertyCollection properties) +428 System.Configuration.SettingsBase.GetPropertiesFromProvider(SettingsProvider provider) +410 System.Configuration.SettingsBase.GetPropertyValueByName(String propertyName) +117 System.Configuration.SettingsBase.get_Item(String propertyName) +89 System.Web.Profile.ProfileBase.GetInternal(String propertyName) +36 System.Web.Profile.ProfileBase.get_Item(String propertyName) +68 System.Web.Profile.ProfileBase.GetPropertyValue(String propertyName) +4 ProfileCommon.get_Theme() in C:WINDOWSMicrosoft.NETFrameworkv2.0.50727Temporary ASP.NET Fileswroxunitedeecd65d2e1a6a798App_Code.ws-dzmjl.6.vb:114 Wrox.Web.GlobalEvents.ThemeModule.app_PreRequestHandlerExecute(Object Sender, EventArgs E) in C:WebsiteWroxUnitedApp_CodeThemeModule.vb:30 System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64
Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET Version:2.0.50727.832
Hi I have an sqlserver setup locally to chew thru pricefiles from our suppliers. The pricefiles comes in various formats mostly txt-files and are inserted via bulk-inserts and separeted by GO-statements, in the end I end up with a table containing unique partnumbers, the average price for the part, and number in stock. What i would like is to have a transact- statement in the end of all thoose sql-statements that copies the final table to a remote sqlserver that contains the DB used on my website. How do i connect to a remote server thru a sql-statement? is it possible? If i just get the connection part explained, i can figure out the rest by myself. Thanks /Jonas
Hi All,Im testing error handling on my website and if I stop my local sql server 2000 then run the web app, I get a SqlException which is good, but when I restart the sql server then I get a System.InvalidOperationException that will not go away. ( its coming from a ExecuteScalar() call) This happens on my remote database as well.It also happens if I kill the connection on my remote machine then reconnect. after I reconnect I can access the database using dbvis so I know its there.Am I not clearing something after the first error? If I restart the machine all is well.Thanks in advance for you help!-Keith
