I am new here and new to SQL Express. I've searched for my issue, but can 't quite find anything close to the problem or how to solve it, if it's even solvable. I am using SQL Express on a pc to connect to the back end of a database. The front end application (an access runtime) also runs on the same pc. This pc is on a domain. I think I've tried every combination of protocols, and although connectivity via ODBC is successful, the application can't connect - gives the "server doesn't exist or access denied". When I log on to this computer with the "machine" logon (not the domain), I have SQL Express configured to use shared memory, the application runs just fine. I need to use this database for testing in a non productivity environment, but I really hate to log off the domain to run it. Ideas?
I am still trying to figure some last issues before installing sql 2005 standard edition. vista issues, sql 2005 sql sp2 etc My question is simple actually, It is about configuring administrative accounts on my computer. I wish to use configure the administrative account? I wish to use a third party in deploying sql reporting services Do I need to set up a local account in report manager? the article in setting up reporting services in vista uses domain/instance name or computer name/instance name how do I do correctly set this up? I will be using july 2007 dvd for sp2 ( I believe) is their any article explaining the steps in sql sp2 some people seem to have trouble in the restore step.....Thanks I just want to be prepared....can I install cd's without the use of the internet....
In an attempt to improve security for our web server/db server setup, we have a SQL Server 2005 server set for Windows authentication only and a web server (both behind a firewall together on a single local domain).
The web server is using IIS7, and the default NetworkService account to run the ASP.NET processes.
I've given the NT AUTHORITYNETWORK SERVICE account access to the database in question.
The SQL authentication fails, but the account failing is NOT the NetworkService account, but the <DOMAIN><COMPUTER>$ account.
Note that if I use identity impersonation with a specific domain account, I can get the app to work. However, I do NOT want to use impersonation, I want the default NetworkService account to work.
Does anyone know why IIS, which is supposed to be using NetworkService, is instead using the <DOMAIN><COMPUTER>$ account to connect to SQL, which is then failing?
Hi all. I am a bit new to SQL but I have studied much info, BOL, various best practices and so on. The problem is - I cannot find any tutorial which could tell me step by step how to set SQL server on a PC and connect to it from another computer (they all are on a domain). So I decided that I am doing something wrong...
I have done the following (all is done on virtual PCs): 1.I have installed a virtual PC with windows 2003, which acts as a domain controller.
2.I installed Win2003 on a second PC and added it to the domain. Installed MS SQL Server 2005 and SP2 on it. Server uses Windows auth. and all the services are running from a dedicated domain account which I added on the first PC.
I added a domain account (let's call it USER_X) to the SQL server Security/Logins
Everything is OK locally, I can connect to the server using USER_X from the same PC.
3.I installed Win2003 on a second PC and added it to the domain. Installed MS SQL Server 2005 client componenst, SSMS and SP2 on it. Logged on as USER_X. And tried to connect to the PC number 2. And failed. SSMS gives an error (1396) Named pipes error "Could not open a connection to SQL server". But the server appears on the list if I click Server name->Browse for more->Network servers. Why I cannot connect to it if I see it? Tried to enable Windows and SQL auth, created a pure SQL user USER_Y, checked locally - ok, can connect. But cannot connect as USER_Y from the third PC.
Finally 4.I installed Win2003 on a fourth PC (did not add it to the domain). Installed MS SQL Server 2005 and SP2 on it. Server uses Windows and SQL auth. Enabled Windows and SQL auth, again created a pure SQL user USER_Y, checked locally - ok, can connect. And checked connection from the third PC - I can connect fine as SQL USER_Y to the SQL server on a PC which is not on the domain but cannot connect as SQL USER_Y to the SQL server on a PC which is on the domain!
What am I doing wrong? How to connect from a PC on a domain to another SQL server on the same domain? It is just a basic config which (I think) SQL admins have gone through many times but I am stuck.
Help, please! I hope to hear from someone who has installed SQL server on a domain and successfully created remote connections.
One of my production SQL Server 2000 systems is listening on TCP and Named Pipes, but not on Shared Memory.
This server has a lot of scheduled jobs that are internal to this box. I assume these jobs would benefit from using shared memory instead of TCP/IP, but I can't figure out why it doesn't use shared memory already and how to correct that.
A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.).Net SqlClient Data Provider at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error) at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected) at System.Data.SqlClient.TdsParserStateObject.ReadBuffer() at System.Data.SqlClient.TdsParserStateObject.ReadByteArray(Byte[] buff, Int32 offset, Int32 len) at System.Data.SqlClient.TdsParserStateObject.ReadUInt32() at System.Data.SqlClient.TdsParser.ReadSqlValueInternal(SqlBuffer value, Byte tdsType, Int32 typeId, Int32 length, TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.ReadSqlValue(SqlBuffer value, SqlMetaDataPriv md, Int32 length, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlDataReader.ReadColumnData() at System.Data.SqlClient.SqlDataReader.ReadColumnHeader(Int32 i) at System.Data.SqlClient.SqlDataReader.ReadColumn(Int32 i, Boolean setTimeout) at System.Data.SqlClient.SqlDataReader.GetInt32(Int32 i)
Ive just started getting this on a stable application thats used a datareader on millions of records.
Not sure where to got from here and I can't find anyone else whos getting the failure during the processing.
I could disable shared memory protocol but that seems extreme. I'm on Sql Enterprise 9.00.2047. Maybe the process is hammering the server very hard? Personally I've rarely ever seen SQL be the cause of an error, only user config, bad disks or power issues.
I'm running the app again with SQL Profiler capturing "standard" events.
Just need it to blow up again.
I can run the app on another machine of course and I wouldn't get Shared Memory Provider being used. Maybe I ought to do that as well. At least if the error is not really in the Shared Memory I'd have another avenue to explore.
Our 32-bit applications connect to SQL Server 32-bit through OLEDB with Shared memory as preferred protocol. Our client applications and SQL Server generally reside on same machine. We are evaluating possible impact when SQL Server 2008 64-bit is accessed with our 32-bit client applications running on 64bit WindowsServer 2008. Can shared memory protocol will be still used by underlying SQL server OLEDB dll considering the client application is 32-bit where as SQL Server is 64-bit ? Or it will switch to Named pipes or TCP/IP automatically ?
I have a SQL 2005 SP2 fail-over cluster with several named instances. It has been running for sometime with no problems. Recently I had to add a new windows group to a named instance. From Management Studio I brought up the "Login - new " gui hit search to find the group in out doamin and got the following error mesage:
The program cannot open the required dialog box because it cannot determine whether the computer named "<instance_name>" is joined to a domain.
The id I am using is a domain authenticated account and I used this same proceedure to add windows groups in the past. If I ignore the message and type in the group as domaingroup_name I can still add the group and users of that group can log into the instance. The other named instances have the same probelm. There are no errors in the event log or SQL's log. Any ideas on how to get the domain search back would be appriciated.
Apparently this error was fixed in CU12 for SQL 2008, but it seems to have raised it's head again in SQL 2012.[SSIS.Pipeline] Warning: Warning: Could not open global shared memory to communicate with performance DLL; data flow performance counters are not available. To resolve, run this package as an administrator, or on the system's console.
I've got a client who is seeing it. but I've not seen a fix in CU1 or CU2 for 2012.
[SSIS.Pipeline] Warning: Could not open global shared memory to communicate with performance DLL; data flow performance counters are not available. To resolve, run this package as an administrator, or on the system's console.
I'm busy rewriting DTS packages as SSIS packages. As and when I finish a package I run it in debug mode via Microsoft Visual Studio and then examine the Exection Results to see the messages generated.
Now it may or may not matter how I run the package but the following warning has been generated :-
[SSIS.Pipeline] Warning: Warning: Could not open global shared memory to communicate with performance DLL; data flow performance counters are not available. To resolve, run this package as an administrator, or on the system's console.
When I try to install MsSQL Server 2005 Develop Edition do I get the error:
[Microsoft][SQL Native Client]Shared Memory Provider: No process is on the other end of the pipe.
I have trying to look at other posts on this forum and elsewhere, but cant find any solution that works for me - mainly cuz all solutions is after the installing.
Before trying to install MsSQL Server 2005 Dev did I install VS.Net 2005 Pro. First did the Native Client make troubles, but got it to work with reinstalling it, but now does the SQL setup stop on every try with the error above.
I have tried looking if the MSSQLServer is running when it tries to connect during install, and everything says it is running (Services, Net start, Taskman.).
I dont run any special setup on my system - it is a normal Windows XP Pro SP2 with all updates. I just need the SQL server installed so I can develop locally without access to out main SQL server.
I have been using MsSQL 2000 before and never had any problems, but the 2005 keep on bugging me.
The only solution I havent tried is to reinstall Windows itself, but I will pref. not to do so.
And to be honest, then have I no idea what a "pipe" is - I am used to develop webapplications and not so much on server maintaince/troubleshooting.
I am getting the following warning for my SSIS08 package: Could not open global shared memory to communicate with performance DLL; data flow performance counters are not available. To resolve, run this package as an administrator, or on the system's console. I did check Warning in SSIS 2008 , but didn't find any solution. The package processes data and executes fine , but why do I see this warning? When I run this package on my machine, I see no such warning, it's only when I deploy it to our DEV SSIS server, I get this warning.
When running the etl I'm getting the error: <SSIS Task>: Shared Memory Provider: Timeout error [258] ; followed by the message "Communication link failure".
What is special about this message that it happens on a SQL Execute task (random task) and the Timeout is after 2 minutes.
When executing the packages separatly it is working fine. The SQL Tasks that are failing are also quit heavy, but reasonable and takes between >2min and 10 - 15 min. Statements are stored procedures that puts an index on 3 mil. records or update statements,...
I had a look to all my (SSIS-etl)Â timeouts and they have the default value 0, the "remote query timeout" of the server is set to 10 minutes. According to me, these are the only one that exists?
There are 2instances on the server each instance has 24GB allocated, the server has 64 in total. Also when the etl runs (that results in an error) no other etl is running on the 2 instances. I'm working with the oledb sql server native client11.0 provider : SQLNCLI11.1.
I would like to know what happens when a very large reference data set for a lookup transform with full caching enabled is getting loaded during package execution and the computer memory runs out or is very low. Does SSIS a) give an out of memory error of some sort b) resort to a no caching or partial caching mode c) maintain the full caching mode but will switch to using the paging file(virtual memory).
I think it will resort to using the page file in which case the benefits of in memory lookups are lost and performance would suffer. If I cannot upgrade the memory or shrink the reference set somehow, i should switch that lookup task to use partial caching or no caching with an indexed lookup table. Would this make sense?
I am receiving the following error when starting a program called ShelbySystems that is supposed to connect to a local database. I don't think this is a security issue but I don't know much about SQL server either so...
  DIAG [08001] [Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied. (17)   DIAG [01000] [Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (Connect()). (2)
System Info: Windows 10Â Home -Â upgrade from 8 64 bit SQL server 2012 Express SQL Backwards compatibility 2005 64 bit ShelbySystems software v5.4
I am including the trace log in case it is useful.
I am getting the following error when i try to connect to the my web site using froma different server. A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) i am using sql express and i attach the database through the connection string in the web config. Any ideas
Hi guys, I hope this is the correct place to post this question. 1) My website makes use of the Membership and Roles of asp.net 2. 2) I have uploaded my website to a shared hosting server, which doesn't support sql express (mdf files). It does support mysql, so I used a custom Membership provider for MySql. 3) It worked greate on my local computer, however (!!) it still creates a aspnetbd.mdf file in the AppData folder. 4) Obviously, when I tried to run it on the website, I got an error. My questions: Why my website still creates a aspnetbd.mdf file even if I am not using it anymore for the Membership ? How can I disable it, in order for it to run on a server which does not support it ? Thanks, Itye.
I've created a new website using the new Visual Studio 2005 Express edition. This site uses SQL Server Express (free software) as a storage for personalization data, etc. Now I want to deploy my site, but here it ends for me:My web site hoster does not support the SQL Express edition in a shared hosting environment. I think most people have a website running in a 'shared hosting' plan. How can this large group enjoy the new Express line when SQL Server Express is not supported? "SQL Server Express is not a part of the SPLA SPUR (Services Provider License Agreement)", they all say. Here it ends for me, my ISP and their licence supplier. Even at Microsoft's Response Management Team, 'no' is the answer. What to do now? Move on to an expensive 'dedicated hosting' plan? Write a membershipprovider for MySQL?I feel as if I was given a free ticket for a nice journey but there's no traffic possible. Who can help me out here? What can I do...
All-- Please help. I have deployed my site to my shared host and I am getting the following RTE... An attempt to attach an auto-named database for file... ..App_DataCommerceDB.mdf failed ...and I cannot find the issue. Note that I have given Full-Permissions on root folder for the IUSR account and for the ASPNET account. The full error message is below. Anyway, do you have an suggestions? My web hosting provider has advertised that they do support SQL Express 2005. What exactly do I need to ask them to do in order to get this working? Please advise. Thank you. --Mark Kamoski
Server Error in '/mkamoski/S16' Application. -------------------------------------------------------------------------------- An attempt to attach an auto-named database for file c:hostingwebhost4lifemembermkamoskiS16App_DataCommerceDB.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share. 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 attempt to attach an auto-named database for file c:hostingwebhost4lifemembermkamoskiS16App_DataCommerceDB.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share. Source Error: Line 88: ''' <returns></returns> Line 89: Public Shared Function GetCart() As ShoppingCart Line 90: Dim rdr As IDataReader = ShoppingCartProvider.Instance.CartGetCurrentCart(GetUserName()) Line 91: Dim cart As ShoppingCart = New ShoppingCart() Line 92: cart.Load(rdr) Source File: c:hostingwebhost4lifemembermkamoskiS16App_CodeBLLShoppingCartManager.vb Line: 90
I have a web app and database created in sql server 2005 express. In addition to using the membership and role providers I have added custom tables and stored procedures to my db. When I try to export this with Sql Server Management Studio (not the express version) to my db on my shared host(sql server 2005) the custom tables and stored procedures are not transferred. How can this be accomplished? Thanks in advance.
I have an XP Pro machine running a classic ASP site in IIS - the version that comes on the XP Pro CD. The site makes a connection to an MSDE database on the same machine named InControl. I have moved that database to SQL Express 2005 and want to test it with the ASP site. SQL Express 2005 is running on a separate Vista machine. I am currently using this connection string: objConn.ConnectionString = "Provider=SQLOLEDB;Data Source=400SC;Initial Catalog=InControl;User ID=" & uid & ";Password=" & upass & "" Where 400SC is the name of the XP Pro machine and InControl is the database. The variables uid and upass are pulled from Session when the connection string is created. I have tried different Provider names and various combinations of server name and ip address with and without port numbers for the Data Source. All of them yield some variation of this error: Microsoft OLE DB Provider for SQL Server (0x80004005)[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. What should the connection string look like? Thanks for the help. PS - If the solution involves a port, do I need to make that port an exception in the Vista Firewall?
I recently come to problem. I want to deploy my web site, which uses SQL2005EE extensively, so I began searching for host, SHARED HOSTING solution. I haven't find one offering SQL2005EE on .NET2.0 final frameworkI have been told that there isn't ONE host which would offer SQL2005EE on Final .NET2.0 shared hosting, that it is illegal! Only if the shared host provided is free, which is insufficient in my needs (free hosts have low trafic/disk space etc).Is it true? If I pay for hosting, I can't have SQL2005EE as an option in their hosting plan? Just SQL2005 full as an option? This way I need to pick up some expensive shared hosting plan?How you ppl solved this problem?
Hi expertsI use a sqlserver on a local computer. i want to access the sqlserver from other computers on the network using the VWD. When trying to connect to the database i get the error:"An error has occured 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 enabled the TCP/IP and the Named Pipes protocols on the server and still the same error. Thanks
I have a asp.net 2.0 app that has a sql server express backend. I have been scratching my head for weeks trying to find a good wasy to encrypt my connection string. I store the string in web.config (which in itself is in theory "safe" because it's not servable) and I have scoured the web to try to find a simple way to encrypt the connection string. Even using user store would require running aspreg_iis.exe on the host with a command prompt (which clearly I cannot do). It seems that everyone's solution requires running a command prompt executable on the server.
So I am left to wonder what everyone else does. I am not comfortable using just the web.config because a determined hacker could get to that info. Then again, a determined hacker could get into any system , I guess. There are no credit card #'s stored in this app, but in theory there must be a way. I run all access to the db through stored procedures with permissions, for whatever it's worth.
Hello, Sorry for my question, I know, that there were several topics about sql 2000 vs SQL 2005, I read all them but unfortunately I haven't got the correct answer. I must install my intranet application that uses asp.net 2.0 and SQL 2005 Express to a Windows 2003 server with SQL 2000. It is possible to install SQL 2005 Express beside the 2000 server? It is very important, because I have no possibility to test and that Win2003 server there are a few programs that use SQL 2000. What will happen with the 2000 databases and their programs if I install the 2005 Express to the server? They will work fine with 2000 and my application will work with 2005? Or instead it should I configure my application to use 2000 capable connentionstrings?
I just got a Virtual Dedicated Server and installed SQL Server Express 2005 on it and while I was installing choose Mix Mode authentication and setup a sa password.....
I want to connect to that database remotely from my machine using VS 2005 or Management Studio....both are encountering the same problems.....
On the Virtual Dedicated machine if I install management studio I run has no problem....it asks me for the server name : somethingSQLEXPRESS then username and password and works fine...
The same thing I try to do remotely is not happy with ....I tried to give the IP address of the server same thing no luck.....
Can somebody tell me what I'm doing wrong and where....
I have a very basic console application whose sole purpose is to query a database on the same local computer. When i run the application, i get the error message below: Cannot open user default database. Login failed.Login failed for user 'someDomainSomeUserName'. Below is my connection string also myconnection_string = New SqlConnection("Data Source=.SQLEXPRESS;AttachDbFilename=C:Reporting SystemApp_Datasafetydata.mdf;Integrated Security=True;Connect Timeout=30;User Instance=True"). After some googling, some post pointed to deleting a user folder at : C:Documents and SettingsmyusernameLocal SettingsApplication DataMicrosoftMicrosoft SQL Server DataSQLEXPRESS but still deleting that folder and restarting the machine doesn't help and i also have remote connections enabled. Help is really needed. NOTE: The same application runs on a different computer with XP but fails on the Pc with windows server 2003.
I have a user who is trying to load SQL server 2005 Express on a new Acer laptop computer. The computer has the following: Windows Vista Home Premium 32 bits AMD Turion 64 mobile technology CPU 1790 MB of RAM When the user tries to load SQL server 2005 Express it does not load. The user after the load is getting an €œUnhandled exception has occurred in your application€? when he tries to run the application. Does anyone know how to fix this problem?
We have 10+ MSDE 2000 installations on the same network. Each install has a named instance and the machines connect to eachother via VB application. We have a couple SQL 2000 Standard boxes and a SQL 2005 box all running on the same network with no issues. The problem we have recently run into is with a SQL Express box. When the box is on the network OSQL stops finding the MSDE 2000 named instances on the network and only the SQL Express named instance appears in the list. The second the SQL Express box is removed from the network the named instances are visible. I monitored the UDP traffic and suspect there is an issue with the response from SQL Express to OSQL. Can't find any issues for this problem only report I found is if MSDE and Express are on the same machine.
We have 10+ MSDE 2000 installations on the same network. Each install has a named instance and the machines connect to eachother via VB application. We have a couple SQL 2000 Standard boxes and a SQL 2005 box all running on the same network with no issues. The problem we have recently run into is with a SQL Express box. When the box is on the network OSQL stops finding the MSDE 2000 named instances on the network and only the SQL Express named instance appears in the list. The second the SQL Express box is removed from the network the named instances are visible. I monitored the UDP traffic and suspect there is an issue with the response from SQL Express to OSQL. Can't find any issues for this problem only report I found is if MSDE and Express are on the same machine.
