<appSettings>
<add key="strConn" value="server=10.100.1.2;uid=sa;pwd=;database=MyDB/>
</appSettings
and I am getting the following error message --
"SQL Server cannot be found or access denied"
if I replace the server IP address with server name, it works fine.
Am I missing something here? Help!
Thanks
Bugme
See the linkhttp://blogs.msdn.com/sql_protocols/archive/2005/10/29/486861.aspx has some information. Hope that helps you!
My guess is name resolution faild!
I've open Web Dev and tried to create a new SQL Database Item, only to receive this error:
"Connections to SQL Server files (*.mdf) require SQL Server Express 2005 to function properly. Please verify the installation of the component or download from the URL http://microsoft.com"
I'm totally new to this, but this still makes no sense.
hi Brad,
only SQLExpress is designed to use User Instances, the feature you are supposed to use via all "Express editions" of Visual Studio ..
as you can see, all other SQL Server 2005 editions do not provide this feature so you have to directly code your connection to access these editions, as the builtin designers of Express editions of VS do not grant the possibility to connect to traditionals instances..
or... you can install a SQLExpress instance side by side on your pc..
regards
Hello all,
this is my first post to asp.net!
I am having a problem getting a drill through to work in the web report viewer. In report1 i have a table with groups and on the key field i want to drill down through i right click >properties> navigation and select jump to report. From there I select the predesigned report2 from the list and add the appropriate parameters.
It works fine when i test it in the dev enviroment and when i deploy it to the report server it works fine there. but when I debug and run it through the website itself and go to the report then click on the hyperlink it goes to a "page cannot be displayed' page.
I have been working on this for 2 days googling the heck out of it and testing several scenarios, but to no avail. I'm sure its something stupidly simple.
has anyone else had this problem?
Help!
thanks so much!
HI,CodeSquirrelMonkey:
Make sure you have put the target report in the right place which is defined in the drill through setting.
Second, you can have a try to open the target report directly on the website.
If i misunderstand you about your question, please feel free to correct me and i will try to help you with more information.
I hope the above information will be helpful. If you have any issues or concerns, please let me know. It's my pleasure to be of assistance
|||Hi Rex,
Thanks for the response. I did make sure that the drill through report is in the right place and it didnt work on the live site either.
I did get around the problem though. I created an fresh new aspx page and dropped a fresh report viewer on it and tried it again and it works fine now. I did a comparison of the two pages' code and couldnt find anything obvious that could have caused it. It does work fine now.
the only other thing was to make sure that the page_load has an if not ispostback on it so that it would refresh and drilldown properly.
Thanks again
Craig
I am using SQL express and Visual web developer on windows Vista.
When I try to create a new database the following message appears.
CREATE DATABASE permission denied in database master (error 262)
I log on to my computer as an administrator.
Help appreciated
Prontonet
How do you login to sql server? Do you use sql authentication? If so, check the account you login with has appropriate permissions. Or are you using windows authentication?
|||Can you login to database engine and read data anyway??
You need "CREATE DATABASE" permission to create new database. However, to make things easier, i would suggest you use sys_admin permission over your database.Open sql express and click "security"-->Logins, see if your login name is listed there. Rigth click your user name and select "properties", click "server roles" or "User Mappings" to see which role has been assigned to your account. If you are not a sys_admin/db_owner role, login agin using a dbo account(if you have one) and assign you account a sys_admin/dbo permission.
Hope my suggestion helps
I'm trying to copy a database from my web host to local Sql Server 2005 instance using the Copy Database wizard. I get this error:
An exception occurred while executing a Transact-SQL statement or batch.
Server user 'celestine' is not a valid user id database 'db2'.
However, 'db2' isn't the database I was trying to copy! I am trying to copy db1, but this error is complaining about db2, which is in fact somebody else's database that I don't have a login for. Why am I getting an error about db2 when I'm not trying to do anything with db2?
I can however export the tables from db1 just fine using Export. But then I have to go back and generate script to re-create the stored procs, views, etc., so it is rather tedious to do it that way.
This may be possible. For example if there is a view in db1 which references a table in db2, and the celestine login does not have access to db2, you may encounter this error.
So to avoid such issue, you can move/copy database by taking a full backup of the source database and then restore it on the destination server.
|||Good idea but -- No, this is not the case. This is a shared hosting situation, the 2nd database is owned by someone else, I have absolutely no access to it at all. There is no relationship whatsoever between the databases.
I can't do a backup/restore either because I don't have access to the remote filesystem.
|||
Urgh...that's really a trouble. Then check whether your login has sufficient permissions to perform copy database task:
Required permissions
For the Copy Database Wizard to work, you must have the correct permissions, depending on how you are copying the database, as follows:
For the Detach and Attach Method, you must be a member of thesysadmin fixed server role on the both source and destination servers.|||Right. But a) I do have correct permissions for both source/destination for the database I'm trying to copy, and b) The error is not pertaining to the database I want to copy. The error mentions a different database, that I have zero permissions for, that I will never have permissions for, that I don't want permissions for. I am trying to copy db1 and the error says "you don't have permissions for db2". Why is it even checking anything for db2?
I ham trying to convert a 'System.Data.CommandType' to 'System.Web.UI.WebControls.SqlDataSourceCommandType'.
but I get
Error 4 Cannot implicitly convert type 'System.Data.CommandType' to 'System.Web.UI.WebControls.SqlDataSourceCommandType'. An explicit conversion exists (are you missing a cast?) D:\Inetpub\wwwroot\Help_Desk\App_Code\HelpDeskSql.cs 99 42 http://localhost/Help_Desk/
My problem is I cant seem to get a explicit conversion to work. if it cast it I get an.
Specified argument was out of the range of valid values.
Parameter name: value . when running the page. but no build errors, does anyone know how to cast this?
if (cmdUpdate !=null)
{
HDS.UpdateCommand = cmdUpdate.CommandText;
HDS.UpdateCommandType = (SqlDataSourceCommandType)cmdUpdate.CommandType; //errror line
for (int i = 0; i < cmdUpdate.Parameters.Count; i++)
{
HDS.UpdateParameters.Add(cmdUpdate.Parameters[i].ParameterName, cmdUpdate.Parameters[i].Value.ToString());
}
}
Hi
I can't connect to sql server 2005 from my asp.net web page. I seem to be able to connect to it when i run the application from within visual studio but i can't connect to it when i run the application from IIS.
I am new to sql server 2005 express so please bear with me.
The error message i get is:
Cannot open database "Vets" requested by the login. The login failed.
Login failed for user 'OSCAR2K4\ASPNET'.
I don't know where this user OSCAR2K4\ASPNET came from but i looked in sql server 2005 and there he is. In the left hand pane I went to Security and then logins and found oscar2k4\asp.net there. I went to the properties for this user and went to User Mappings. There was no tick next to my Vets database so I added one and ran the application from IIS. I also added the user to every single role in the vets database (including dbowner). I also went into the vets database itself and found the oscar/aspnet user and made sure he was added to every role.
I ran the application again. This time i got a lots of different errors. If the page was trying to run a select procedure I got the error user does not have select permission. If the page was running an SP i got the error or user does not execute permission
I have never had this problem before so I don't understand.
Where did this user come from? Was he created automatically when i configured my database for membership and roles? How do i set up this user so he can access the databsae from IIS.
The only way I could get the application to run from IIS was to go to Security - Logins for sql server and add the oscar2k4\asp.net user to the sysadmin role.
I find this very strange. Naturally i don't want to leave oscar2k4 in sysadmin.
Please help :) I can't upload my website until i fix this
Thanks, andrea
<server>\ASPNET is 'ASP.NET Machine Account', one of the access control lists (ACLs) that are set by default on the Machine.config file and the root Web.config file.
What's the OS version (e.g. Window2000 or Xp) of the box? You can take a look at this articlehttp://msdn2.microsoft.com/en-us/library/ab4e6cky.aspx
By default the database connection string is configured by SQL express and I do not know how to change it.
Not all, it is said that just upload everything to the server and that's all but it is not that. To work with database I had to use SQL server 2005 to upload the database by using import wizard and import tables into the database folder in my server. Do I need to do them same with membership and role database? I tried but it still says error .
I am just beginer so need help form you, the masters.
The URL show error is www.tinhtran.com/Default.aspx
thanks
Hi,
take a look at this site for connectionstrings. Personally, I find it strange that you don't get the correct connectionstring from the helpdesk.
Grz, Kris.
Hi all,
I'm new to this forum and haven't worked with SQL Server for a couple of years. Now it seems I'm getting back into it. I have SQL Express and SQL 2005 installed on an XP sp2 machine with IIS 5.1. I have a C#/ASP.NET web app in Visual Studio 2005 that keeps getting an error on attempting to connect (SqlConnection object). It's a generic error saying a probable cause is SQL Express default setup not allowing remote connections. Remote connections are turned on for both TCP and UDP. I can connect from within a small C# windows application using the same uid and pwd, so I suspect it's something related to IIS talking to SQLExpress. I would appreciate any help on other things to check. I am also fairly new to using IIS in the development environment.
Thanks
It could be because you didn't specify the instance name when you tried to connect from the C# app? It could also be that SQLBrowser isn't running.
Hope that helps,
John
|||This is because SQL Server 2005 Express Edition does not accepts remote connections by default:
How to: Enable Network Access During Installation of SQL Server 2005 Express Edition
|||Thanks John,
Yes, I specified the instance name and verified SQLBrowser is running. COnnection string = "Server=BUTTERFLY\SQLExpress; Initial Catalog=catalog; uid=username; pwd=password;
|||Ronald,
Thanks for pointing me to this information. It didn't actually solve my dilemma, but it did get the juices flowing. This is related to a project I inherited and upgraded from .NET 1.1 to 2.0. The sql connection string referenced a property for "server=", changing this to "data source=" allowed the connection to open properly. I am reading the links you pointed and they are very helpful. Thanks
Hi all,
I'm new to this forum and haven't worked with SQL Server for a couple of years. Now it seems I'm getting back into it. I have SQL Express and SQL 2005 installed on an XP sp2 machine with IIS 5.1. I have a C#/ASP.NET web app in Visual Studio 2005 that keeps getting an error on attempting to connect (SqlConnection object). It's a generic error saying a probable cause is SQL Express default setup not allowing remote connections. Remote connections are turned on for both TCP and UDP. I can connect from within a small C# windows application using the same uid and pwd, so I suspect it's something related to IIS talking to SQLExpress. I would appreciate any help on other things to check. I am also fairly new to using IIS in the development environment.
Thanks
It could be because you didn't specify the instance name when you tried to connect from the C# app? It could also be that SQLBrowser isn't running.
Hope that helps,
John
|||This is because SQL Server 2005 Express Edition does not accepts remote connections by default:
How to: Enable Network Access During Installation of SQL Server 2005 Express Edition
|||Thanks John,
Yes, I specified the instance name and verified SQLBrowser is running. COnnection string = "Server=BUTTERFLY\SQLExpress; Initial Catalog=catalog; uid=username; pwd=password;
|||Ronald,
Thanks for pointing me to this information. It didn't actually solve my dilemma, but it did get the juices flowing. This is related to a project I inherited and upgraded from .NET 1.1 to 2.0. The sql connection string referenced a property for "server=", changing this to "data source=" allowed the connection to open properly. I am reading the links you pointed and they are very helpful. Thanks
Hi all,
I'm new to this forum and haven't worked with SQL Server for a couple of years. Now it seems I'm getting back into it. I have SQL Express and SQL 2005 installed on an XP sp2 machine with IIS 5.1. I have a C#/ASP.NET web app in Visual Studio 2005 that keeps getting an error on attempting to connect (SqlConnection object). It's a generic error saying a probable cause is SQL Express default setup not allowing remote connections. Remote connections are turned on for both TCP and UDP. I can connect from within a small C# windows application using the same uid and pwd, so I suspect it's something related to IIS talking to SQLExpress. I would appreciate any help on other things to check. I am also fairly new to using IIS in the development environment.
Thanks
It could be because you didn't specify the instance name when you tried to connect from the C# app? It could also be that SQLBrowser isn't running.
Hope that helps,
John
|||This is because SQL Server 2005 Express Edition does not accepts remote connections by default:
How to: Enable Network Access During Installation of SQL Server 2005 Express Edition
|||Thanks John,
Yes, I specified the instance name and verified SQLBrowser is running. COnnection string = "Server=BUTTERFLY\SQLExpress; Initial Catalog=catalog; uid=username; pwd=password;
|||Ronald,
Thanks for pointing me to this information. It didn't actually solve my dilemma, but it did get the juices flowing. This is related to a project I inherited and upgraded from .NET 1.1 to 2.0. The sql connection string referenced a property for "server=", changing this to "data source=" allowed the connection to open properly. I am reading the links you pointed and they are very helpful. Thanks
Hi all,
I'm new to this forum and haven't worked with SQL Server for a couple of years. Now it seems I'm getting back into it. I have SQL Express and SQL 2005 installed on an XP sp2 machine with IIS 5.1. I have a C#/ASP.NET web app in Visual Studio 2005 that keeps getting an error on attempting to connect (SqlConnection object). It's a generic error saying a probable cause is SQL Express default setup not allowing remote connections. Remote connections are turned on for both TCP and UDP. I can connect from within a small C# windows application using the same uid and pwd, so I suspect it's something related to IIS talking to SQLExpress. I would appreciate any help on other things to check. I am also fairly new to using IIS in the development environment.
Thanks
It could be because you didn't specify the instance name when you tried to connect from the C# app? It could also be that SQLBrowser isn't running.
Hope that helps,
John
|||This is because SQL Server 2005 Express Edition does not accepts remote connections by default:
How to: Enable Network Access During Installation of SQL Server 2005 Express Edition
|||Thanks John,
Yes, I specified the instance name and verified SQLBrowser is running. COnnection string = "Server=BUTTERFLY\SQLExpress; Initial Catalog=catalog; uid=username; pwd=password;
|||Ronald,
Thanks for pointing me to this information. It didn't actually solve my dilemma, but it did get the juices flowing. This is related to a project I inherited and upgraded from .NET 1.1 to 2.0. The sql connection string referenced a property for "server=", changing this to "data source=" allowed the connection to open properly. I am reading the links you pointed and they are very helpful. Thanks
I have a web app running on a laptop (for demo purposes) with the following connect string:
"datasource=<machine name>\SQLExpress;initial catalog=BlueTarp;User ID=sa;Password=xxx"
I can connect to this instance using both oSQL or sqlcmd and can select from the tables within BlueTarp, but my web app won't connect, and I can't figure out why!!
When I installed SQL Express, I used a named instance, called "SQLExpress".
I'm using mixed mode authentication.
One strange thing is that I can connect to either SQLExpress or MSSQLSERVER instances, but they appear to be the same instance -- I can use bluetarp in both.
when I use SQLExpress for instance name in web.config I get "SQL Server does not exist or access denied"
when I use MSSQLServer for instance name in web.config I get "Invalid connection"
And in fiddling with the web.config, I somehow did something to get a machine.config error, something like "machine.config couldn't be loaded because of an unloaded appdomain".
It's driving me nuts because I've spent a good 40 hours on this stupid problem, throwing the whole margin down the toilet.
Does anyone have any ideas?
Thank you,
Aarron
First, SQL Server has support for multiple protocols for remote connections (shared memory, named pipes, tcp/ip, and via) and if the client is trying a protocol the server has disabled then it will fail to connect.
To see what protocols are enabled, goto Computer Management -> SQL Server Configuration Manager -> SQL Server 2005 Network Configuration -> Protocols for <Instance Name>. If you change the protocols the server supports, you will need to restart the server.
Try using a protocol such as named pipes instead of shared memory. Try np:<machine name>.
http://msdn2.microsoft.com/en-US/library/system.data.sqlclient.sqlconnection.connectionstring(VS.80).aspx
For general troubleshooting of .NET connectivity issues, see this blog entry: http://blogs.msdn.com/sql_protocols/archive/2005/12/22/506607.aspx
For the ASP.NET issue, try restarting IIS/ASP.NET, and make sure machine.config is valid xml with the XML editor in Visual Studio.
|||Mark,
Thanks so much for your help. I've been all over the web trying to find info about this problem -- people have pointed me to Mcaffe, to the .NET frameworks possibly having issues, to my web.config being poorly formatted.... and it turns out that I wasn't using a supported protocol. I enabled named pipes and it works like a charm.
You da man!
Aarron
I have installed SQL 2005 Express Edition on a Windows 2003 Web Edition server. Everything installed correctly, no errors to be found. I also have:
Local & Remote Connections using TCP/IP only turne don
SQL Browser is running as well.
I have tried connecting with the most recent CTP of Microsoft SQL Server Management Studio Express 9.00.1399.00
When trying to connect using the SA account I recieve:
'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) (Microsoft SQL Server, Error: 53)
After that failed I tried creating a connection locally on the server using ODBC Manager with no luck as well.
Microsoft SQL Native Client Version 09.00.1399
Running connectivity tests...
Attempting connection
[Microsoft][SQL Native Client]TCP Provider: No connection could be made because the target machine actively refused it.
[Microsoft][SQL Native Client]Login timeout expired
[Microsoft][SQL Native Client]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.
TESTS FAILED!
Any help would be appreciated.
Try this.
Start > All Programs > Microsoft SQL Server 2005 > Configuration tools > SQL Server Surface Area Configuration
Then click Surface Area Configuration for Services and Connection. Select your instance of sql server (by default MSSQLSERVER). Then expand Database Engine and click on remote connections. On the right side select Local and remote connections > Using both TCO/IP and named pipes.
|||I'm having the same issue, i've tried all of the above. My server has 9 active IP addresses, and I've tried connecting to the one which I use to remote in to the server. Is this the correct approach?
Also, in the SQL Server Configuration Manager, I've set that IP address to 'Active' and 'Enabled' with no luck. Same error as the gentleman above.
Any other suggestions?
Thank you,
Bret
|||I still can't get it to work. I've even tried the old remove and reinstall approach. This is very aggravating as I've tried everything under the sun that I can think of.|||Got it working:
Under Protocols for SQLEXPRESS and tcp/ip and the ip addresses tab
Tcp dynamic ports – set to blank
Disabled other ips except the loopback
At the bottom, set dynamic ports to blank and the tcp port to 1433
Stopped and restarted the sql server.
I have installed SQL 2005 Express Edition on a Windows 2003 Web Edition server. Everything installed correctly, no errors to be found. I also have:
Local & Remote Connections using TCP/IP only turne don
SQL Browser is running as well.
I have tried connecting with the most recent CTP of Microsoft SQL Server Management Studio Express 9.00.1399.00
When trying to connect using the SA account I recieve:
'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) (Microsoft SQL Server, Error: 53)
After that failed I tried creating a connection locally on the server using ODBC Manager with no luck as well.
Microsoft SQL Native Client Version 09.00.1399
Running connectivity tests...
Attempting connection
[Microsoft][SQL Native Client]TCP Provider: No connection could be made because the target machine actively refused it.
[Microsoft][SQL Native Client]Login timeout expired
[Microsoft][SQL Native Client]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.
TESTS FAILED!
Any help would be appreciated.
Try this.
Start > All Programs > Microsoft SQL Server 2005 > Configuration tools > SQL Server Surface Area Configuration
Then click Surface Area Configuration for Services and Connection. Select your instance of sql server (by default MSSQLSERVER). Then expand Database Engine and click on remote connections. On the right side select Local and remote connections > Using both TCO/IP and named pipes.
|||I'm having the same issue, i've tried all of the above. My server has 9 active IP addresses, and I've tried connecting to the one which I use to remote in to the server. Is this the correct approach?
Also, in the SQL Server Configuration Manager, I've set that IP address to 'Active' and 'Enabled' with no luck. Same error as the gentleman above.
Any other suggestions?
Thank you,
Bret
|||I still can't get it to work. I've even tried the old remove and reinstall approach. This is very aggravating as I've tried everything under the sun that I can think of.|||Got it working:
Under Protocols for SQLEXPRESS and tcp/ip and the ip addresses tab
Tcp dynamic ports – set to blank
Disabled other ips except the loopback
At the bottom, set dynamic ports to blank and the tcp port to 1433
Stopped and restarted the sql server.
