.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

MS Sql 2005 Connection issue

Posted By:      Posted Date: September 24, 2010    Points: 0   Category :Sql Server

Dear All,

I am facing an issue while connecting to MsSql2005 through my Application. The server is installed on my local machine itself. If I am using the name of my machine in the connection string like - Data Source=hostname\sqlexpress;Initial Catalog=test;Max Pool Size=500;Integrated Security=True;as

then in that case it is working fine. but if I am using ipaddress in place hostname in the connection string then in that case it is throwing 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: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.)'


I have checked the ip address of my machine and it is the same which I am providing in the connection string. I have checked the SQL Server Configuration Manager  and TCP/IP is enabled there for the IP address of the machine. I have allowed the remote connections for the DB server also.

Please suggest me some more trouble shooting steps which can be done from my side

View Complete Post

More Related Resource Links

SQL Server Express 2005 connection timeout issue.

Client: Sql Sever Management Studio Express 2005 (SSMSE) on Vista Server: Sql Server 2005 Express on Windows Server 2008 Standard When I first try to log into SSMSE from the client machine, the login operation times out. When I retry, the login succeeds almost immediately. If I close the app and re-open it, the same thing happens. This appears to be infinitely repeatable. I am able to reproduce this behavior using SQLCMD.exe. Here's the error: "Timeout expired. The timeout elapsed prior to completion of the operation or the server is not responding. (Microsoft SQL Server)" The technical details reference Error Number -2 What may be unique or tricky about this client's network is that it's a mixture of IPv4 and IPv6. I believe the server is configured for both, but honestly the networking side of things is outside of my expertise. Has anyone else experienced a problem like this? I'm looking for some troubleshooting tips and of course a flat-out answer :-). Thank you in advance for your time and expertise - I hope I've broken the problem down to its simplest form. Will.

connection to SQL Server files (*.mdf) require SQL server express 2005 to function properly.


I dont have the SQL EXPRESS installed instead I have SQL Standard Edition.

 I have two SQL Server instances installed.

 1- UserLT (this is sql 2000)
2- UserLT\SQL2005 (this is SQL 2005 named instance)

But when i try to add a database to my VS website project I get the following error:

Connection 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: go.microsoft.com/fwlink/?linkId=4925

I went in Tools>Opetions>DataBase tools>Data Connection>Sql Server Instance Name (blank for default)

and changed the "SQLEXPRESS" to "USERLT\SQL2005".

But I still get the same error message. Any ideas how i can resolve this issue?

Instance and Default connection properties on SQL Server 2005

We had a sql server fail and I have been having troubles.  I compared the connection properties on the server properties and noticed that multiple default settings are no longer set.  So I'm wondering if during the failure these could have some gotten flipped.  DB's that worked all of a sudden don't work and we had to migrate to a different instance.  I have never changed any of the setings below and wonder what impact they would have if I changed them back to the default of an installed instance? ansi warning is checked ansi padding is checked ANSI NULLS is checked arithmetic abort is checked quoted identified is checked No Count is checked concat null yields null is checked Could anyone tell me how clearing these checked options will impact my db?   -- Paul Bergson MVP - Directory Services MCITP: Enterprise Administrator MCTS, MCT, MCSE, MCSA, Security+, BS CSci 2008, Vista, 2003, 2000 (Early Achiever), NT4 http://www.pbbergs.com    Twitter @pbbergs Please no e-mails, any questions should be posted in the NewsGroup This posting is provided "AS IS" with no warranties, and confers no rights.

SQL 2005 migration issue

Hey everyone, I do not know anything about SQL, so hopefully someone can help me out. Installed SQL 2005 on a new server.  Restored a database from SQL7. The database I restored is called "train" for example and in that database is a user called "train_user" I cannot connect to the obdc data source using this "train_user".  I do not know if the password didn't carry over during the migration and don't even know how to check or change this password.  I don't know if this user needs certain privileges to be able to access the SQL server?  They are the db owner of the database that I restored.  The application I am trying to launch gives me the odbc error.  This info is stored in an ini file.  If I change this info to sa, then I can access the application. If I need to provide more info, I can do that, but hopefully someone understands what is going on or what I need to do to fix it. Here is the error code:  Error: 18456, Severity: 14, State: 5.

Kerberos issue with SQL Reporting Services 2005 on Server 2003 R2

Hi Guys,apologies if this is the incorrect forum, so moderators, feel free to move it to SQL/IIS/SharePoint as appropriate... [Windows Server Security moderator pushed me this direction]I have a test environment that I'm trying to get SQL Reporting Services 2005 SP3 working in integrated mode with SharePoint 2007 SP2.The environment is all in VMWare, running Server 2003 R2 x86 and is layed out like this:SERVER A:AD/DNS/DHCPSERVER B:SQL 2005 SP3 CU8SERVER C:SharePoint 2007 SP2 Dec 09 CU- Central admin on port 9000- SSP on port 9001- MySite on port 81- Main Content on port 80SQL Reporting Services 2005 SP3 CU8- Reporting Service website on port 82SERVER D:SharePoint 2007 SP2 Dec 09 CU- Central admin on port 9000- SSP on port 9001- MySite on port 81- Main Content on port 80SQL Reporting Services 2005 SP3 CU8- Reporting Service website on port 82Through the use of DNS and (SharePoint) Alternate Access Names, SERVER D is used to deliver the Main Content in SharePoint and the Reporting Service website.  SERVER C is used to deliver the Central Admin, SSP and MySite.I've set up SPN's for the SharePoint App Pools, using the following: [main content] setspn -S HTTP/SERVERA DOMAIN\AppPoolUserA setspn -S HTTP/SERVERA.FQDN DOMAIN\AppPoolUserA setspn -S HTTP/SERVERB DOMAIN\AppPoolUserA setspn -S HTTP/SERVERB.FQDN DOMAIN\AppPoolUserA [repor

Connection to SQL Server 2005 Express?

Hi all, I've been reading other posts for awhile now and I can't figure out what I'm doing wrong. I'm a Web Developer and not a DBA. I have SQL Server 2005 Express installed on my machine and it's working just fine. I also have the Management Studio Express CTP installed and working. I'm trying to connect to a database using a username and password (from ColdFusion Server which is working fine for external Oracle and Access databases, so that's not an issue), so I set up the server to allow mixed mode authentication. I can log in to the Management Studio using Windows authentication OR the username and password without any issues. I have TCP/IP enabled in the Configuration Manager and enabled. This seems like a ridiculous question, but I need to know the servername, port, username and password to connect to the database. I'm trying all combinations of things but nothing's working. If I put in as the server, 1433 as the port, and use the username and password that worked in Management Studio I get this: java.sql.SQLException: [Macromedia][SQLServer JDBC Driver]Error establishing socket. Connection refused: connect The root cause was that: java.sql.SQLException: [Macromedia][SQLServer JDBC Driver]Error establishing socket. Connection refused: connect If I use MACHINENAME\SQLEXPRESS I get this: java.sql.SQLException: [Macromedia][SQLServer

Getting the Error: 0xC001000E at : The connection "" is not found. SQL 2005

After doing some looking I noticed this was included in the SP3 for SQL 2005. We have had this service pack installed for a while now but we are still randomly getting this error. Some packages will run fine for a long time and then all of the sudden start giving this error even though the package was successful. Any ideas? Thanks, Donnie

How to change connection string of a pivot table pointing to SSAS 2005 cube using excel 2003?

Hi All,I am not sure if I should have posted this query to Excel 2003 forum. But posting it here as it applies to SSAS 2005 as well.Ok, let me give the background before I tell the actual problem.We have users on ABC domain and the SSAS server is also on ABC domain. Users on this domain can acess the excel pivots by connecting to cube to browse the data. They leave the Userid & password field blank while they setup the connection string and it works fine. Thanks to windows authentication that takes the credentials of user logged in. Let's say I have two users A and B, they login to ABC domain with their own windows ids.  Now when user A creates a excel file having a cube pivot and then sends this file to user B, user B can refresh and modify the same excel file (he can select new measures to pivot, new hierarchies in filters and so on).Now, let's say I have another user, user C. He has excel 2003 installed on his PC and cannot migrate to excel 2007. He is on different domain XYZ but have a valid windows userid on domain ABC. The domain ABC & XYZ can not be setup to have trusted relationship. Now, when user A sends the same excel file to user C. When user C opens the file and try to refresh it or try to modify the pivot by selecting/deselecting any elements, he gets below error prompt:" An error was encountered in the transport layer." and "Errors in the

ODBC connection to SQL Server 2005 Standard (on windows xp) with Windows authentication does NOT wor

I reviewed lots of postings, still could not find an answer. If I choose Windows authentication: - with TCP/IP and "Dynamically determine port" checked, I get the following error "The user is not associated with a trusted SQL Server connection; - with Named Pipes, Server Name & Pipe Name as "VSAXAONG", I get two errors, one after the other on the same pop-up:       Connection failed  SQL State 01000  SQL Server Error 1385 [Microsoft] [ODBC SQL Server Driver] [Named Pipes] ConnectionOpen (Connect()).       Connection failed  SQL State 08001 SQL Server Error 17 [Microsoft] [ODBC SQL Server Driver] [Named Pipes] SQL Server does not exist or access denied. If I choose SQL Server authentication and fill in the password - the ODBC connection works fine. I have to say that I created two different logins on the server, one for Windows authentication, and one for SQL Server authentication - both for the same Windows user name. I would appreciate any help I can get on this.  Thank you all in advance.

Issue with transactional replication on SQL 2005 SP3 using row filters with bit columns

We recently upgraded from SQL 2000 to SQL 2005 SP3 and I am noticing something that I think is a bug with replication from a publication that has an article in it with row filters.  It seems to be that if the row filter has columns that are bit datatype and that column is updated on the publisher to cause the row filter to exclude it, it is not removed from the subscriber.  If you update a column that is part of the row filter that is not a bit datatype it works as expected.  I can reproduce this in a test environment with a small base table.  In production this is resulting in an occasional 20598 error "The row was not found at the Subscriber when applying the replicated command". Is anyone aware of a hotfix that addresses this? I can think of a few work arounds but the table is rather large and I really would like to avoid having to pull replication, re-snap or changing datatypes on the base table etc. Any suggestions are greatly appreciated.  Thanks!

Issue in SMO DB transfer from SQL 2005 EE to SQL 2008 EE SP1

Hi All, I am transferring DB from SQL Server 2005 EE to SQL 2008 EE SP1 using SQL Server SMO. I am using the TransferData method of Transfer object. I am facing a problem where it creates the DB on 2008 instance but does not create any table, view and procedures. This is not getting reproduced every time. The error that caught in code reads below:   ERROR : errorCode=-1073548784 description=Executing the query "CREATE TABLE [dbo].[table1]( [ParamKe..." failed with the following error: "The log for database 'sadb20052008' is not available. Check the event log for related error messages. Resolve any errors and restart the database.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly. helpFile= helpContext=0 idofInterfaceWithError={C81DFC5A-3B22-4DA3-BD3B-10BF861A7F9C} For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.   I checked the SQL Server logs and it is reading as below. I enabled the deadlock logging by setting the SQL Server service startup parameters to -T1204, -T1205, -T3605 and found the log as given below. How can I debug it to find the root cause and resolve it?   2010-04-06 16:50:28.31 spid7s Deadlock encountered .... Printing deadlock information 201

Issue with Enable and Disable Parameters in SSRS 2005

Hi Guys, I am currently facing an issue with Enabling and Disabling Parameters in SSRS 2005. Here is my scenario. I am having the following 4 parameters - ParamType (has values 1,2,3), ParamMonth, ParamStartDate, ParamEndDate Now What I want is When I select ParamType = 1 and 2 then ParamMonth should be enabled and ParamStartDate and ParamEndDate should be disabled. When I select ParamType = 3 then ParamStartDate and ParamEndDate should be enabled and ParamMonth should be disabled. I have done google search on this issue and found out that this is not possible at run time. Is there any alternative for this issue? If the above is not possible, I would like to get atleast in this way : When I select ParamType = 1 and 2 then ParamMonth should show the values (from dataset named MonthDataSet and default should be the latest Month) and ParamStartDate and ParamEndDate should show as NULL. When I select ParamType = 3, then I need to enter ParamStartDate and ParamEndDate values manually or pick via datepicker and ParamMOnth should show as NULL. I am not sure whether this is possible or not....but just trying to get in some way. Here is the query used in MonthDataSet : Select Month_Code, Month_Name from MonthTable. Thanks

Character spacing issue SSRS 2005 custom font

Hello together, we are facing a strange character spacing issue in SSRS 2005 SP3 (Version 9.00.4035.00). As we export the report to a pdf file, we get unwanted spaces between each character. The report uses custom fonts. Is there any known issue related to this? I appreciate your help. Thanks!  Kind regards Moritz Mars

Cannot create a connection to data source !!!! SSRS 2005

I cannot get this error resolve either for myself or any users, and I'm actually part of the Admin group!  Furthermore, a user with whom I'm tring allow to view this report keeps getting prompted for their windows username and password.  I thought that since this datasource was set to Windows Authentification that it would just pass it through? I'm pulling my hair out at this point: Screen Shots: http://www.webfound.net/datasource_connection.jpg http://www.webfound.net/datasource_connection2.jpg http://www.webfound.net/datasource_connection3.jpg Also As far as I know, I've given sufficient permissions to the right logins and right users on my SQL Databases and related stored procs that the datasets (not datasource) run An error has occurred during report processing. Cannot create a connection to data source 'datasourcename'. For more information about this error navigate to the report server on the local server machine, or enable remote errors

upgrade sql 2005 to 2008 issue

i am trying to upgrade sql server 2005 Enterprise edition sp2 to Sql server 2008 R2 Data center Edition on a windows 2003 Enterprise edition SP2. Up gradation fails to give 'FeatureUpgradeMatrixCheck' error. any ideas ? i don't find much online. I would like to upgrade ::: [Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86)     Enterprise Edition on Windows NT 5.2  ] to [Microsoft SQL Server 2008 R2 (RTM)   Data Center Edition ] possible ? thx, jason

IO queuing issue after migration from 2005 to 2008

Hi,   Are there any functional changes to the number of outstanding IOs to a LUN from 2005 to SQL 2008? 2008 seems to have a limit of 128 outstanding IOs to a DB volume where SQL 2005 does not. I am struggling to find any SQL tuning parameters that would impact how the db can read/write to disk? Help/comments appreciated.    

SQL Server 2005 Cluster failover issue

Hi All, I'm fequently experience Cluster failover issue. The cluster tries to failover and it fails back. Because of this the SQL server is getting restarted and this is a bugging issue during business hours. The following are the System event logs, Cluster resource 'SQL Server' in Resource Group 'Production' failed. The SQL Server Agent (MSSQLSERVER) service was successfully sent a stop control. The SQL Server Agent (MSSQLSERVER) service entered the stopped state. The SQL Server (MSSQLSERVER) service was successfully sent a stop control. The SQL Server (MSSQLSERVER) service entered the stopped state. The SQL Server (MSSQLSERVER) service was successfully sent a start control. The SQL Server (MSSQLSERVER) service entered the running state. The Cluster Service brought the Resource Group "Production" online.    The following are the application event logs, The client was unable to reuse a session with SPID 131, which had been reset for connection pooling. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message. [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed [sqsrvres] printODBCError: sqlstate = HYT00; native error = 0; message = [Microsoft][SQL Native Client]Query timeout expired [sqsrvres] OnlineThread: QP is not online. The client was unable
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend