Hi,
I'm having some difficulty creating a system DSN on a
win2K machine for connecting to a SQL 2000 server. I'm not
sure if this may be a better question for the windows
group, but... Anyway, when I go through the odbc setup in
windows, the DSN does not appear in the list of system
dsn's that are already created. I begin to create it, and
it says it already exists, "overwrite?". (this is because
I have already tried creating it with that name, and am
using the same dsn name. If I use a new name, I don't get
the "already exists" message, but the following problem
still occurs.) I do so, and continue through creating the
dsn and successfully testing the connection. When I
finish the creation, the dsn name still does not appear in
the list of system dsn's. Is this a corrupt odbc database
on the win2K machine? I have no idea!!! PS I am tryiing
to create it with local Administrator priveledges.
Any help would be appreciated.
Thanks
David
Check the permissions on the following registry key:
HKLM\Software\ODBC\ODBC.INI
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||I'm also experiencing the same problem. I've checked the permissions on the related key in the registry, and have given Full Permission to all users, but to no avail. Any other suggestions?
************************************************** ********************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...
Showing posts with label connecting. Show all posts
Showing posts with label connecting. Show all posts
Tuesday, March 20, 2012
Cannot Create System DSN
Hi,
I'm having some difficulty creating a system DSN on a
win2K machine for connecting to a SQL 2000 server. I'm not
sure if this may be a better question for the windows
group, but... Anyway, when I go through the odbc setup in
windows, the DSN does not appear in the list of system
dsn's that are already created. I begin to create it, and
it says it already exists, "overwrite?". (this is because
I have already tried creating it with that name, and am
using the same dsn name. If I use a new name, I don't get
the "already exists" message, but the following problem
still occurs.) I do so, and continue through creating the
dsn and successfully testing the connection. When I
finish the creation, the dsn name still does not appear in
the list of system dsn's. Is this a corrupt odbc database
on the win2K machine? I have no idea!!! PS I am tryiing
to create it with local Administrator priveledges.
Any help would be appreciated.
Thanks
DavidCheck the permissions on the following registry key:
HKLM\Software\ODBC\ODBC.INI
Rand
This posting is provided "as is" with no warranties and confers no rights.|||I'm also experiencing the same problem. I've checked the permissions on the
related key in the registry, and have given Full Permission to all users, bu
t to no avail. Any other suggestions?
****************************************
******************************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET
resources...
I'm having some difficulty creating a system DSN on a
win2K machine for connecting to a SQL 2000 server. I'm not
sure if this may be a better question for the windows
group, but... Anyway, when I go through the odbc setup in
windows, the DSN does not appear in the list of system
dsn's that are already created. I begin to create it, and
it says it already exists, "overwrite?". (this is because
I have already tried creating it with that name, and am
using the same dsn name. If I use a new name, I don't get
the "already exists" message, but the following problem
still occurs.) I do so, and continue through creating the
dsn and successfully testing the connection. When I
finish the creation, the dsn name still does not appear in
the list of system dsn's. Is this a corrupt odbc database
on the win2K machine? I have no idea!!! PS I am tryiing
to create it with local Administrator priveledges.
Any help would be appreciated.
Thanks
DavidCheck the permissions on the following registry key:
HKLM\Software\ODBC\ODBC.INI
Rand
This posting is provided "as is" with no warranties and confers no rights.|||I'm also experiencing the same problem. I've checked the permissions on the
related key in the registry, and have given Full Permission to all users, bu
t to no avail. Any other suggestions?
****************************************
******************************
Sent via Fuzzy Software @. http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET
resources...
Thursday, March 8, 2012
Cannot create a connection to data source 'dsInvent'
I get this error message when connecting through IE to a report. We have a
sepererate Report Server and the database to which we are reporting from.
When I go to the report server logged on using the same account as my
workstation I can access the report. I have tried making it a shared data
source with the same problem.
The report does work if I enter my credentials and select use Integrated
Security in Report Manager/Properties/Data Sources. Is this required and the
only way to make it work? This would seem to be a pain cause every time a
user changes thier password you would need to change it there as well.
TIA,
SteveAre you trying to connect to SQL Server 2000 database, and are you in an
Active Directory domain?
You should be able to
- Create a AD usergroup with all the users that are supposed to view the
reports
- Add this group as a login to SQL Server, and give it Read access to the
datasource
- Set up your datasource in Report Manager as Windows NT Integrated Security
This way it should pick up the user name of the user logged in on the
machine, check the AD properties of this user, and use them against the SQL
Server, which will give the users the data they are entitled to see in the
database.
Alternatively, set up your datasource using "Credentials stored securely..."
and use a SQL Server login that have the right access rights in your SQL
Server database.
Kaisa
"Steve Wofford" <IntraRELY@.yahoo.com> wrote in message
news:%23zjMHQpBGHA.3936@.TK2MSFTNGP12.phx.gbl...
>I get this error message when connecting through IE to a report. We have a
>sepererate Report Server and the database to which we are reporting from.
> When I go to the report server logged on using the same account as my
> workstation I can access the report. I have tried making it a shared data
> source with the same problem.
> The report does work if I enter my credentials and select use Integrated
> Security in Report Manager/Properties/Data Sources. Is this required and
> the only way to make it work? This would seem to be a pain cause every
> time a user changes thier password you would need to change it there as
> well.
> TIA,
> Steve
>|||We are using:
Reporting Server 2005 (Seperate Server)
Reporting Database - 2000
Reporting Data Database - 2000 (This is where the report data will be
pulled from)
My account is a domain admin and all system belong to this same domain. I
can execute the query the report uses w/in Query Analyzer and can run the
report from VS. When I logon locally to the report server, I can run the
report as well.
However, when I run the report from the same sysetm I dev the report using
VS, I cannot view the report data in IE, however the report is displayed w/o
data. The report runs when I enter my credentials and select use Integrated
Security in Report Manager/Properties/Data Sources.
the problem is that I didnt think this should be the case. why isnt my
security information persisting to the report data.
"Kaisa M. Lindahl" <kaisaml@.hotmail.com> wrote in message
news:emdy%2325BGHA.1092@.TK2MSFTNGP09.phx.gbl...
> Are you trying to connect to SQL Server 2000 database, and are you in an
> Active Directory domain?
> You should be able to
> - Create a AD usergroup with all the users that are supposed to view the
> reports
> - Add this group as a login to SQL Server, and give it Read access to the
> datasource
> - Set up your datasource in Report Manager as Windows NT Integrated
> Security
> This way it should pick up the user name of the user logged in on the
> machine, check the AD properties of this user, and use them against the
> SQL Server, which will give the users the data they are entitled to see in
> the database.
> Alternatively, set up your datasource using "Credentials stored
> securely..." and use a SQL Server login that have the right access rights
> in your SQL Server database.
> Kaisa
>
> "Steve Wofford" <IntraRELY@.yahoo.com> wrote in message
> news:%23zjMHQpBGHA.3936@.TK2MSFTNGP12.phx.gbl...
>>I get this error message when connecting through IE to a report. We have a
>>sepererate Report Server and the database to which we are reporting from.
>> When I go to the report server logged on using the same account as my
>> workstation I can access the report. I have tried making it a shared data
>> source with the same problem.
>> The report does work if I enter my credentials and select use Integrated
>> Security in Report Manager/Properties/Data Sources. Is this required and
>> the only way to make it work? This would seem to be a pain cause every
>> time a user changes thier password you would need to change it there as
>> well.
>> TIA,
>> Steve
>
sepererate Report Server and the database to which we are reporting from.
When I go to the report server logged on using the same account as my
workstation I can access the report. I have tried making it a shared data
source with the same problem.
The report does work if I enter my credentials and select use Integrated
Security in Report Manager/Properties/Data Sources. Is this required and the
only way to make it work? This would seem to be a pain cause every time a
user changes thier password you would need to change it there as well.
TIA,
SteveAre you trying to connect to SQL Server 2000 database, and are you in an
Active Directory domain?
You should be able to
- Create a AD usergroup with all the users that are supposed to view the
reports
- Add this group as a login to SQL Server, and give it Read access to the
datasource
- Set up your datasource in Report Manager as Windows NT Integrated Security
This way it should pick up the user name of the user logged in on the
machine, check the AD properties of this user, and use them against the SQL
Server, which will give the users the data they are entitled to see in the
database.
Alternatively, set up your datasource using "Credentials stored securely..."
and use a SQL Server login that have the right access rights in your SQL
Server database.
Kaisa
"Steve Wofford" <IntraRELY@.yahoo.com> wrote in message
news:%23zjMHQpBGHA.3936@.TK2MSFTNGP12.phx.gbl...
>I get this error message when connecting through IE to a report. We have a
>sepererate Report Server and the database to which we are reporting from.
> When I go to the report server logged on using the same account as my
> workstation I can access the report. I have tried making it a shared data
> source with the same problem.
> The report does work if I enter my credentials and select use Integrated
> Security in Report Manager/Properties/Data Sources. Is this required and
> the only way to make it work? This would seem to be a pain cause every
> time a user changes thier password you would need to change it there as
> well.
> TIA,
> Steve
>|||We are using:
Reporting Server 2005 (Seperate Server)
Reporting Database - 2000
Reporting Data Database - 2000 (This is where the report data will be
pulled from)
My account is a domain admin and all system belong to this same domain. I
can execute the query the report uses w/in Query Analyzer and can run the
report from VS. When I logon locally to the report server, I can run the
report as well.
However, when I run the report from the same sysetm I dev the report using
VS, I cannot view the report data in IE, however the report is displayed w/o
data. The report runs when I enter my credentials and select use Integrated
Security in Report Manager/Properties/Data Sources.
the problem is that I didnt think this should be the case. why isnt my
security information persisting to the report data.
"Kaisa M. Lindahl" <kaisaml@.hotmail.com> wrote in message
news:emdy%2325BGHA.1092@.TK2MSFTNGP09.phx.gbl...
> Are you trying to connect to SQL Server 2000 database, and are you in an
> Active Directory domain?
> You should be able to
> - Create a AD usergroup with all the users that are supposed to view the
> reports
> - Add this group as a login to SQL Server, and give it Read access to the
> datasource
> - Set up your datasource in Report Manager as Windows NT Integrated
> Security
> This way it should pick up the user name of the user logged in on the
> machine, check the AD properties of this user, and use them against the
> SQL Server, which will give the users the data they are entitled to see in
> the database.
> Alternatively, set up your datasource using "Credentials stored
> securely..." and use a SQL Server login that have the right access rights
> in your SQL Server database.
> Kaisa
>
> "Steve Wofford" <IntraRELY@.yahoo.com> wrote in message
> news:%23zjMHQpBGHA.3936@.TK2MSFTNGP12.phx.gbl...
>>I get this error message when connecting through IE to a report. We have a
>>sepererate Report Server and the database to which we are reporting from.
>> When I go to the report server logged on using the same account as my
>> workstation I can access the report. I have tried making it a shared data
>> source with the same problem.
>> The report does work if I enter my credentials and select use Integrated
>> Security in Report Manager/Properties/Data Sources. Is this required and
>> the only way to make it work? This would seem to be a pain cause every
>> time a user changes thier password you would need to change it there as
>> well.
>> TIA,
>> Steve
>
Wednesday, March 7, 2012
Cannot connect w/ Java app but can connect w/ .Net app - SQL Server Express 2005
I'm having a problem connecting with a Java application but I CAN connect using my .Net application - the user name and password are the same for both (using the same database on SQL Server Express 2005).
<init-param>
<param-name>DBUser</param-name>
<param-value>sa</param-value>
</init-param>
<init-param>
<param-name>DBPwd</param-name>
<param-value>myPasswd</param-value>
</init-param>.
The error I get is: "com.microsoft.sqlserver.jdbc.SQLServerException: Cannot open database "CORNERS" requested by the login. The login failed." An interesing note - I get the same message if the database is not running.
SQL Server Express 2005 is installed in mixed mode.
Here is my connection string in the .Net appplication: <add key="connectString" value="Server=(local);UID=sa;PWD=myPasswd;Database=CORNERS" />.
These are my values in my Java app web.xml -
<init-param>
<param-name>DBDriver</param-name>
<param-value>com.microsoft.sqlserver.jdbc.SQLServerDriver</param-value>
</init-param>
<init-param>
<param-name>DBURL</param-name> <param-value>jdbc:sqlserver://localhost\sqlexpress:1055;databaseName=CORNERS</param-value>
<init-param>
<param-name>DBUser</param-name>
<param-value>sa</param-value>
</init-param>
<init-param>
<param-name>DBPwd</param-name>
<param-value>myPasswd</param-value>
</init-param>.
And yes, the port is 1055 - I checked to find it.
I am using Microsoft SQL Server 2005 JDBC Driver 1.0 (sqljdbc_1.0.809.102).
Does anyone have any idea what is wrong so that the login fails in the Java application but works in the .Net application?
Mostlikely, you have a syntax error in your connection string.
jdbc:sqlserver://localhost\sqlexpress:1055;databaseName=CORNERS
please refer to http://msdn2.microsoft.com/en-us/library/ms378428.aspx
you can try
jdbc:sqlserver://localhost:1055;databaseName=CORNERS,
|||I tried your suggestion and it does not work. I get the same error. I tried many different variations of the connection string and none of them have worked.I think it is important to note that I get this error even if the database is NOT running.
This leads me to believe it's a problem with the driver. I have the sqljdbc.jar located in my Tomcat\common\lib directory. Is this incorrect?|||Can you get a trace with FINEST level turned on?|||How do I turn the trace on? And to the finest level? And will this make a difference considering that I get the same message whether or not the database is actually running?|||
I'm having a similar problem. However I am using context.xml to define the connection pool as:
<Resource name="jdbc/SqlServerLocal"
auth="Container"
type="javax.sql.DataSource"
username="PortalUser"
password="********"
driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver"
url="jdbc:sqlserver://servername\\SQLEXPRESS:1433"
maxActive="10"
maxIdle="4"
maxWait="100" />
and this works on my Windows development machine... but when I ftp the *.war file to the Linux server, I get the following message:
Cannot load JDBC driver class 'com.microsoft.sqlserver.jdbc.SQLServerDriver'
I put the 'sqljdbc.jar' file in the /common/lib path for both installations.
|||Adisciullo,
Please refer to the following site for information regarding turning tracing on:
http://msdn2.microsoft.com/en-us/library/ms378517.aspx
Please post the results so we can further diagnose this.
Additionally, does this problem also reproduce with the v1.1 driver. You can find it at: http://www.microsoft.com/downloads/details.aspx?FamilyId=6D483869-816A-44CB-9787-A866235EFC7C&displaylang=en
Thanks,
Jaaved Mohammed
Saturday, February 25, 2012
Cannot Connect using IP to Clustered Named Instance
I am having trouble connecting when using the IP address to a named
instanced using dynamic port assignments and hosted on a 2K3 cluster (even
when at the console on the node hosting the SQL instance). I receive "SQL
Server does not exist or access denied". There are no entries created in
the event log. I am able to connect with no problems using the instance
name. I'm attempting to connect usingQuery Analyzer. Any ideas?
Thanks!
______________________________________
Michael DiGiuseppe
Technical Services - Enterprise
North Carolina Department of Transportation
Century Center - Building B
______________________________________
E-mail correspondence to and from this address
may be subject to North Carolina Public Records
Law "NCGS.Ch.132" and may be disclosed to
third parties by an authorized state official.
Hi Michael,
In order to connect to a Named Instance you need to either:
a. Supply the Servername\InstanceName
b. Supply the Servername, port
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||It seems that you have trouble connecting through TCP/IP. Verify in event log that SQL is listening on TCPIP and not only on Shared Memory / Named Pipes.
To verify that this is a problem from QueryAnalyzer try to connect with tcp:ServerName\InstanceName. If it isn't work then server is not listening on TCP at all...
post back after this and we will see what then...
Rgds
Sinisa Perovic
|||Thanks for the help.
Thanks!
______________________________________
Michael DiGiuseppe
Technical Services - Enterprise
North Carolina Department of Transportation
Century Center - Building B
______________________________________
E-mail correspondence to and from this address
may be subject to North Carolina Public Records
Law "NCGS.Ch.132" and may be disclosed to
third parties by an authorized state official.
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:51hmVwbIEHA.3636@.cpmsftngxa06.phx.gbl...
> Hi Michael,
> In order to connect to a Named Instance you need to either:
> a. Supply the Servername\InstanceName
> b. Supply the Servername, port
>
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>
instanced using dynamic port assignments and hosted on a 2K3 cluster (even
when at the console on the node hosting the SQL instance). I receive "SQL
Server does not exist or access denied". There are no entries created in
the event log. I am able to connect with no problems using the instance
name. I'm attempting to connect usingQuery Analyzer. Any ideas?
Thanks!
______________________________________
Michael DiGiuseppe
Technical Services - Enterprise
North Carolina Department of Transportation
Century Center - Building B
______________________________________
E-mail correspondence to and from this address
may be subject to North Carolina Public Records
Law "NCGS.Ch.132" and may be disclosed to
third parties by an authorized state official.
Hi Michael,
In order to connect to a Named Instance you need to either:
a. Supply the Servername\InstanceName
b. Supply the Servername, port
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||It seems that you have trouble connecting through TCP/IP. Verify in event log that SQL is listening on TCPIP and not only on Shared Memory / Named Pipes.
To verify that this is a problem from QueryAnalyzer try to connect with tcp:ServerName\InstanceName. If it isn't work then server is not listening on TCP at all...
post back after this and we will see what then...
Rgds
Sinisa Perovic
|||Thanks for the help.
Thanks!
______________________________________
Michael DiGiuseppe
Technical Services - Enterprise
North Carolina Department of Transportation
Century Center - Building B
______________________________________
E-mail correspondence to and from this address
may be subject to North Carolina Public Records
Law "NCGS.Ch.132" and may be disclosed to
third parties by an authorized state official.
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:51hmVwbIEHA.3636@.cpmsftngxa06.phx.gbl...
> Hi Michael,
> In order to connect to a Named Instance you need to either:
> a. Supply the Servername\InstanceName
> b. Supply the Servername, port
>
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>
cannot connect to the database using sa or a new login
Hi,
I have problem connecting to any of the databases on the local machine using
the "sa" or any of the logins that I had created and gave database access. I
have SQL Server 2000 Developer Edition installed on XP Professional OS.
I am getting the following error:
Java.sql.SQLException: []Login failed for user ‘sa’. Reason: Not XXX
ociatied
with a trusted SQL Server connection
I have never seen this error message.
I have the same SQL Server 2000-Developer edition installed on this other XP
Professional system and there is no problem with connecting to any of its
local machine databases.
Please help!
Thank you,
--
MitraThe error indicates you are trying to access the server with
SQL logins but the server is configured for Windows
Authentication only. So try changing the Authentication mode
to SQL Server and Windows.
You can find this by right clicking on the server in
Enterprise Manager, select properties and go to the security
tab.
-Sue
On Wed, 17 Nov 2004 14:48:02 -0800, "mitra"
<mitra@.discussions.microsoft.com> wrote:
>Hi,
>I have problem connecting to any of the databases on the local machine usin
g
>the "sa" or any of the logins that I had created and gave database access.
I
>have SQL Server 2000 Developer Edition installed on XP Professional OS.
>I am getting the following error:
>Java.sql.SQLException: []Login failed for user sa. Reason: Not associ
atied
>with a trusted SQL Server connection
>I have never seen this error message.
>I have the same SQL Server 2000-Developer edition installed on this other X
P
>Professional system and there is no problem with connecting to any of its
>local machine databases.
>Please help!
>Thank you,|||Hi,
You change the authentication process from "Windows only" to "SQL+Windows"
with the following steps :
1- stop MSSQLServer service
2- edit the value
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer\LoginMode to
assign it the value 2.
3- Restart the service
Note : the value LoginMode can be
1 for Windows authenticaton
2 for Mixed authentication
Rgds,
Chris
"mitra" <mitra@.discussions.microsoft.com> wrote in message
news:7A3CF1D3-892B-4054-8B72-FED592BE3FC7@.microsoft.com...
> Hi,
> I have problem connecting to any of the databases on the local machine
using
> the "sa" or any of the logins that I had created and gave database access.
I
> have SQL Server 2000 Developer Edition installed on XP Professional OS.
> I am getting the following error:
> Java.sql.SQLException: []Login failed for user 'sa'. Reason: Not
associatied
> with a trusted SQL Server connection
> I have never seen this error message.
> I have the same SQL Server 2000-Developer edition installed on this other
XP
> Professional system and there is no problem with connecting to any of its
> local machine databases.
> Please help!
> Thank you,
> --
> Mitra
I have problem connecting to any of the databases on the local machine using
the "sa" or any of the logins that I had created and gave database access. I
have SQL Server 2000 Developer Edition installed on XP Professional OS.
I am getting the following error:
Java.sql.SQLException: []Login failed for user ‘sa’. Reason: Not XXX
ociatied
with a trusted SQL Server connection
I have never seen this error message.
I have the same SQL Server 2000-Developer edition installed on this other XP
Professional system and there is no problem with connecting to any of its
local machine databases.
Please help!
Thank you,
--
MitraThe error indicates you are trying to access the server with
SQL logins but the server is configured for Windows
Authentication only. So try changing the Authentication mode
to SQL Server and Windows.
You can find this by right clicking on the server in
Enterprise Manager, select properties and go to the security
tab.
-Sue
On Wed, 17 Nov 2004 14:48:02 -0800, "mitra"
<mitra@.discussions.microsoft.com> wrote:
>Hi,
>I have problem connecting to any of the databases on the local machine usin
g
>the "sa" or any of the logins that I had created and gave database access.
I
>have SQL Server 2000 Developer Edition installed on XP Professional OS.
>I am getting the following error:
>Java.sql.SQLException: []Login failed for user sa. Reason: Not associ
atied
>with a trusted SQL Server connection
>I have never seen this error message.
>I have the same SQL Server 2000-Developer edition installed on this other X
P
>Professional system and there is no problem with connecting to any of its
>local machine databases.
>Please help!
>Thank you,|||Hi,
You change the authentication process from "Windows only" to "SQL+Windows"
with the following steps :
1- stop MSSQLServer service
2- edit the value
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MS
SQLServer\MSSQLServer\LoginMode to
assign it the value 2.
3- Restart the service
Note : the value LoginMode can be
1 for Windows authenticaton
2 for Mixed authentication
Rgds,
Chris
"mitra" <mitra@.discussions.microsoft.com> wrote in message
news:7A3CF1D3-892B-4054-8B72-FED592BE3FC7@.microsoft.com...
> Hi,
> I have problem connecting to any of the databases on the local machine
using
> the "sa" or any of the logins that I had created and gave database access.
I
> have SQL Server 2000 Developer Edition installed on XP Professional OS.
> I am getting the following error:
> Java.sql.SQLException: []Login failed for user 'sa'. Reason: Not
associatied
> with a trusted SQL Server connection
> I have never seen this error message.
> I have the same SQL Server 2000-Developer edition installed on this other
XP
> Professional system and there is no problem with connecting to any of its
> local machine databases.
> Please help!
> Thank you,
> --
> Mitra
Friday, February 24, 2012
Cannot connect to SQL server with NT groups
Hi.
Have problems connecting to SQL server with NT group authentication.
Get error 4064: Error connecting to user default database.
There's no problems connecting with NT users og SQL users.
SQL2000 + Windows2000 both running latest service packs. All SP have been reinstalled.
The server suddenly stopped accepting NT group logins. It have been running for 1 year with no problems - 4 days ago it started generating this error.
Any ideas anyone?Talk to the network guys...something changed...
Have problems connecting to SQL server with NT group authentication.
Get error 4064: Error connecting to user default database.
There's no problems connecting with NT users og SQL users.
SQL2000 + Windows2000 both running latest service packs. All SP have been reinstalled.
The server suddenly stopped accepting NT group logins. It have been running for 1 year with no problems - 4 days ago it started generating this error.
Any ideas anyone?Talk to the network guys...something changed...
Cannot connect to SQL server after setting user connections to 1
I have a problem connecting to SQL Server 2005. After I set "user
connections" to 1 and restarted sql service, I cannot connect to server
anymore. Do you have maybe any suggestion how to set "user connection" back
to 0? It's a SQL Server 2005 Standard with SP1 in two node cluster.
Thanks!
BogdanDisconnect the network to make sure nobody can log in and then set SQL Agent
to manual start to make sure it doesn't grab your only connection. Also
look for any other services that might be grabbing the connection. Stop and
start the SQL service and see if you can get in. Good luck.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Bogdan" <Bogdan@.discussions.microsoft.com> wrote in message
news:2418A056-42A7-43CB-984B-E60A84BB124C@.microsoft.com...
>I have a problem connecting to SQL Server 2005. After I set "user
> connections" to 1 and restarted sql service, I cannot connect to server
> anymore. Do you have maybe any suggestion how to set "user connection"
> back
> to 0? It's a SQL Server 2005 Standard with SP1 in two node cluster.
> Thanks!
> Bogdan|||Note - this assumes you are running SQL Server 2000. If you are running SQL
Server 2005 you can use the administration connection to get in.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:ev2PsHaZGHA.1200@.TK2MSFTNGP03.phx.gbl...
> Disconnect the network to make sure nobody can log in and then set SQL
> Agent to manual start to make sure it doesn't grab your only connection.
> Also look for any other services that might be grabbing the connection.
> Stop and start the SQL service and see if you can get in. Good luck.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Bogdan" <Bogdan@.discussions.microsoft.com> wrote in message
> news:2418A056-42A7-43CB-984B-E60A84BB124C@.microsoft.com...
>
connections" to 1 and restarted sql service, I cannot connect to server
anymore. Do you have maybe any suggestion how to set "user connection" back
to 0? It's a SQL Server 2005 Standard with SP1 in two node cluster.
Thanks!
BogdanDisconnect the network to make sure nobody can log in and then set SQL Agent
to manual start to make sure it doesn't grab your only connection. Also
look for any other services that might be grabbing the connection. Stop and
start the SQL service and see if you can get in. Good luck.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Bogdan" <Bogdan@.discussions.microsoft.com> wrote in message
news:2418A056-42A7-43CB-984B-E60A84BB124C@.microsoft.com...
>I have a problem connecting to SQL Server 2005. After I set "user
> connections" to 1 and restarted sql service, I cannot connect to server
> anymore. Do you have maybe any suggestion how to set "user connection"
> back
> to 0? It's a SQL Server 2005 Standard with SP1 in two node cluster.
> Thanks!
> Bogdan|||Note - this assumes you are running SQL Server 2000. If you are running SQL
Server 2005 you can use the administration connection to get in.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:ev2PsHaZGHA.1200@.TK2MSFTNGP03.phx.gbl...
> Disconnect the network to make sure nobody can log in and then set SQL
> Agent to manual start to make sure it doesn't grab your only connection.
> Also look for any other services that might be grabbing the connection.
> Stop and start the SQL service and see if you can get in. Good luck.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Bogdan" <Bogdan@.discussions.microsoft.com> wrote in message
> news:2418A056-42A7-43CB-984B-E60A84BB124C@.microsoft.com...
>
Sunday, February 19, 2012
Cannot connect to SQL instance without port information
Hi all,
More likely this is a change in your environment. You don't say which
version of SQL Server you are using, but with SQL 2005 I think the
requirement is that the Browser service is running. On SQL 2000, you
need to be able to access port 1434 on UDP.
>
More likely this is a change in your environment. You don't say which
version of SQL Server you are using, but with SQL 2005 I think the
requirement is that the Browser service is running. On SQL 2000, you
need to be able to access port 1434 on UDP.
>
In both cases, firewalls may get in the way.
>
>
Is there a reason you can't connect using Server\Instance type syntax?
I'm having some trouble with connecting to SQL server instance lately
without adding a port number. I used to be able to always connect to
instance without having to input SQLSERVER,portnumber. However now
this is not the case. I doing this through an ADO connection object,
and creating the connection string. Does anyone know if there was a
recent Microsoft update or patch that would've cause this to stop
allowing me to connect to a SQL instance without having to put in the
port information? Thanks.Flash08 (stuart.karp@.gmail.com) writes:
Quote:
Originally Posted by
I'm having some trouble with connecting to SQL server instance lately
without adding a port number. I used to be able to always connect to
instance without having to input SQLSERVER,portnumber. However now
this is not the case. I doing this through an ADO connection object,
and creating the connection string. Does anyone know if there was a
recent Microsoft update or patch that would've cause this to stop
allowing me to connect to a SQL instance without having to put in the
port information? Thanks.
More likely this is a change in your environment. You don't say which
version of SQL Server you are using, but with SQL 2005 I think the
requirement is that the Browser service is running. On SQL 2000, you
need to be able to access port 1434 on UDP.
In both cases, firewalls may get in the way.
--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Erland Sommarskog <esquel@.sommarskog.sewrote in
news:Xns996556346440Yazorman@.127.0.0.1:
Quote:
Originally Posted by
Flash08 (stuart.karp@.gmail.com) writes:
Quote:
Originally Posted by
>I'm having some trouble with connecting to SQL server instance lately
>without adding a port number. I used to be able to always connect to
>instance without having to input SQLSERVER,portnumber. However now
>this is not the case. I doing this through an ADO connection object,
>and creating the connection string. Does anyone know if there was a
>recent Microsoft update or patch that would've cause this to stop
>allowing me to connect to a SQL instance without having to put in the
>port information? Thanks.
>
More likely this is a change in your environment. You don't say which
version of SQL Server you are using, but with SQL 2005 I think the
requirement is that the Browser service is running. On SQL 2000, you
need to be able to access port 1434 on UDP.
>
In both cases, firewalls may get in the way.
>
>
Is there a reason you can't connect using Server\Instance type syntax?
Cannot connect to SQL Express from my Application
Hey everyone, I'm having trouble connecting to my sql express instance through my vb.net application. I can connect to it from Visual Studio and the management tools, but get an error when connection with a connection string. What should my connection string look like? I'm using the a default SQLEXPRESS instance.
Can you try connection string like this "server=.\\SQLExpress;Trusted_Connection=true;"
|||I mean "server=.\SQLExpress;Trusted_Connection=true;"|||no luck so far. Just timeouts.. aarrrrr.Thursday, February 16, 2012
Cannot Connect to SQL 2000 on Win2k3 Server
I am having great difficulty connecting to my sql box, I
vpn'd in from work and connected via remote desktop,
setup the SQL connection locally, and connected fine,
which I am wondering if it was cause I was VPN'd in, but
I disconnected from remote desktop and was still able to
hit my sql server in enterprise manager. Then when I got
home tonight, logged on my XP machine and I cannot get my
sql registration to connect.
SQL Server does not exist or access denied ConnectionOpen
(Connect()
I have no idea what this means...I am just learning SQL
so this is all new to me...please help...I am on a home
network behind a linksys router, both my XP box and the
Win2k3 box are behind the router which has a dynamic ip
for the XP box, and a static one for the 2k3 box.On Windows 2003, if there are any instances of SQL Server installed that
are not on SP3 or higher, TCP will be disabled (there will be messages in
the event logs indicating this). In that case remote connections would fail
because by default clients try to connect with TCP. Upgrade all instances
on the box to SP3 then retry connecting. You can also try to connect from
the remote machines using named pipes (add np: before the machine\instance
in your connection string).
328306 INF: Potential Causes of the "SQL Server Does Not Exist or Access
http://support.microsoft.com/?id=328306
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
vpn'd in from work and connected via remote desktop,
setup the SQL connection locally, and connected fine,
which I am wondering if it was cause I was VPN'd in, but
I disconnected from remote desktop and was still able to
hit my sql server in enterprise manager. Then when I got
home tonight, logged on my XP machine and I cannot get my
sql registration to connect.
SQL Server does not exist or access denied ConnectionOpen
(Connect()
I have no idea what this means...I am just learning SQL
so this is all new to me...please help...I am on a home
network behind a linksys router, both my XP box and the
Win2k3 box are behind the router which has a dynamic ip
for the XP box, and a static one for the 2k3 box.On Windows 2003, if there are any instances of SQL Server installed that
are not on SP3 or higher, TCP will be disabled (there will be messages in
the event logs indicating this). In that case remote connections would fail
because by default clients try to connect with TCP. Upgrade all instances
on the box to SP3 then retry connecting. You can also try to connect from
the remote machines using named pipes (add np: before the machine\instance
in your connection string).
328306 INF: Potential Causes of the "SQL Server Does Not Exist or Access
http://support.microsoft.com/?id=328306
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
Cannot connect to server
Hi,
I am using sql server 2005 sp1 developer edtion. I have looked at the install logs and all ok, but when connecting to my server (LAPTOP) i get the following error below. I have not changed any of the xml config file, if anyone can help me i would be very grateful.
Thanks in advance
kered
TITLE: Connect to Server
Cannot connect to LAPTOP.
ADDITIONAL INFORMATION:
The type initializer for 'System.Data.SqlClient.SqlConnection' threw an exception. (System.Data)
The type initializer for 'System.Data.SqlClient.SqlConnectionFactory' threw an exception. (System.Data)
The type initializer for 'System.Data.SqlClient.SqlPerformanceCounters' threw an exception. (System.Data)
Configuration system failed to initialize (System.Configuration)
Unrecognized configuration section Runtime. (C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\SqlWb.exe.Config line 2) (System.Configuration)
BUTTONS:
OK
Are you using any application or tool to connect your server?
Check whether SQL Server services are started.
|||Hi, Satya SKJ
I am not using a tool or application to connect to my server just opening sql server and trying to connect. I have uninstalled and installed a again same problem. I have also stopped and started sql serveices.
kered
|||can u paste the file
(C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\SqlWb.exe.Config )
content here
there may be problem in that
open this file in IExploere.
copy the XML COntent & paste here
|||Hi,
Thanks for everones help i have now worked out my problem i had a problem with sp1.
kered
Tuesday, February 14, 2012
Cannot connect to OLAP database using Credential Stored in report server
Hi guys,
I'm having problem regarding connecting to OLAP Database when I use the Credential stored in the Report Server. When I tried using the Credential stored in the Report Server connecting to OLTP database, It works fine.
Below is the error I'm geting when connecting to OLAP Database.
There are several reasons why the connection could fail. I recommend to check the report server logfile for more information on the exception from the data provider, or enable remote errors (see: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=230593&SiteID=1) to turn on detailed errors for all users.
-- Robert
Cannot connect to Named Instance
I'm having trouble connecting to a named instance on a SQL 2000 EE cluster
(Windows 2003). I have no problems connecting to the first virtual server by
name or IP address, but I can only connect to the named instance by using
the IP address and specifying a port (192.168.0.1, 1434).
I can connect to the named instance by IP or name from both cluster nodes,
the problem only arises with remote clients. The client machine I am testing
from is running Windows XP SP2, MDAC 2.8
Thanks in advance,
Curtis
Curtis O. Bouknight wrote:
> I'm having trouble connecting to a named instance on a SQL 2000 EE cluster
> (Windows 2003). I have no problems connecting to the first virtual server by
> name or IP address, but I can only connect to the named instance by using
> the IP address and specifying a port (192.168.0.1, 1434).
> I can connect to the named instance by IP or name from both cluster nodes,
> the problem only arises with remote clients. The client machine I am testing
> from is running Windows XP SP2, MDAC 2.8
>
1433 is the default sql port. The problem could be with the udp listener
which tells the client where the instance is running.
when you installed the named instance you created an alias on both nodes.
Did you remove these, and if so does the sql agent connect with lpc or is it
still using named pipes? If so clean the registry
HKLM\SOFTWARE\Microsoft\MSSQLServer\Client\SuperSo cketNetLib\LastConnect
and restart sql agent and see it fail?
Are both sqlservices running as local admin?
Hans
|||Welcome to my world.
This issue has been ongoing for me with Microsoft for almost a year now.
They have bounced around from it being a SQL Problem, to a network problem,
back to a SQL Problem, now they are looking at an OS problem. If you call
support, be ready to take system dumps, netstats, captures, etc...
One thing you can do to "verify" that you have the problem is to take a
tasklist and a netstat -aon on each node, then match the PID's up. One will
not have a listener on UDP 1434, and the other will. We had the same
scenario for quite some time, then suddenly the other node started exhibiting
the same behavior. We now tell customers to just go directly to the TCP/IP
port for both nodes to solve any confusion down the way.
js
"Curtis O. Bouknight" wrote:
> I'm having trouble connecting to a named instance on a SQL 2000 EE cluster
> (Windows 2003). I have no problems connecting to the first virtual server by
> name or IP address, but I can only connect to the named instance by using
> the IP address and specifying a port (192.168.0.1, 1434).
> I can connect to the named instance by IP or name from both cluster nodes,
> the problem only arises with remote clients. The client machine I am testing
> from is running Windows XP SP2, MDAC 2.8
> Thanks in advance,
> Curtis
>
>
>
(Windows 2003). I have no problems connecting to the first virtual server by
name or IP address, but I can only connect to the named instance by using
the IP address and specifying a port (192.168.0.1, 1434).
I can connect to the named instance by IP or name from both cluster nodes,
the problem only arises with remote clients. The client machine I am testing
from is running Windows XP SP2, MDAC 2.8
Thanks in advance,
Curtis
Curtis O. Bouknight wrote:
> I'm having trouble connecting to a named instance on a SQL 2000 EE cluster
> (Windows 2003). I have no problems connecting to the first virtual server by
> name or IP address, but I can only connect to the named instance by using
> the IP address and specifying a port (192.168.0.1, 1434).
> I can connect to the named instance by IP or name from both cluster nodes,
> the problem only arises with remote clients. The client machine I am testing
> from is running Windows XP SP2, MDAC 2.8
>
1433 is the default sql port. The problem could be with the udp listener
which tells the client where the instance is running.
when you installed the named instance you created an alias on both nodes.
Did you remove these, and if so does the sql agent connect with lpc or is it
still using named pipes? If so clean the registry
HKLM\SOFTWARE\Microsoft\MSSQLServer\Client\SuperSo cketNetLib\LastConnect
and restart sql agent and see it fail?
Are both sqlservices running as local admin?
Hans
|||Welcome to my world.
This issue has been ongoing for me with Microsoft for almost a year now.
They have bounced around from it being a SQL Problem, to a network problem,
back to a SQL Problem, now they are looking at an OS problem. If you call
support, be ready to take system dumps, netstats, captures, etc...
One thing you can do to "verify" that you have the problem is to take a
tasklist and a netstat -aon on each node, then match the PID's up. One will
not have a listener on UDP 1434, and the other will. We had the same
scenario for quite some time, then suddenly the other node started exhibiting
the same behavior. We now tell customers to just go directly to the TCP/IP
port for both nodes to solve any confusion down the way.
js
"Curtis O. Bouknight" wrote:
> I'm having trouble connecting to a named instance on a SQL 2000 EE cluster
> (Windows 2003). I have no problems connecting to the first virtual server by
> name or IP address, but I can only connect to the named instance by using
> the IP address and specifying a port (192.168.0.1, 1434).
> I can connect to the named instance by IP or name from both cluster nodes,
> the problem only arises with remote clients. The client machine I am testing
> from is running Windows XP SP2, MDAC 2.8
> Thanks in advance,
> Curtis
>
>
>
Sunday, February 12, 2012
Cannot connect to Local SQL Server
I am having trouble connecting to my local sql server from either the Server
Explorer or vb.net code. The problem is connected to the Norton Internet
Security 2005 Firewall as when I disable Norton everything works and if
Norton is enabled but the PC is not plugged into the network it also works.
When I am connected to the network the Firewall does pop up asking whether
or not I want to allow my vb.net program to access a DNS. I have tried using
localhost, the hardcoded IP of my machine, and my machine name (the usual
method) without any success. It is as if Visual Studio always tries to
resolve the machine name and cannot. VB6 programs ,dbArtisan, and SQL
Enterprise Manager all work fine at the same time Visual Studio/VB.Net does
not.
Any ideas?
Thanks,
Mark Lewis
mdlewis@.mdlewis.com
P.S I am using the latest production/old Visual Studio and SQL Server on XP
with all SP applied.here's an idea: configure the Norton product so that your machine can access
DNS.
-- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik
Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
"Mark Lewis" <mdlewis@.mdlewis.com> wrote in message
news:u$P2swmHFHA.3336@.TK2MSFTNGP10.phx.gbl...
>I am having trouble connecting to my local sql server from either the
>Server Explorer or vb.net code. The problem is connected to the Norton
>Internet Security 2005 Firewall as when I disable Norton everything works
>and if Norton is enabled but the PC is not plugged into the network it also
>works.
> When I am connected to the network the Firewall does pop up asking whether
> or not I want to allow my vb.net program to access a DNS. I have tried
> using localhost, the hardcoded IP of my machine, and my machine name (the
> usual method) without any success. It is as if Visual Studio always tries
> to resolve the machine name and cannot. VB6 programs ,dbArtisan, and SQL
> Enterprise Manager all work fine at the same time Visual Studio/VB.Net
> does not.
> Any ideas?
> Thanks,
> Mark Lewis
> mdlewis@.mdlewis.com
> P.S I am using the latest production/old Visual Studio and SQL Server on
> XP with all SP applied.
>|||Resubmitting this with my new MSDN Alias.
Thanks,
Mark Lewis
mdlewis@.mdlewis.com
"Mark Lewis" <mdlewis@.mdlewis.com> wrote in message
news:u$P2swmHFHA.3336@.TK2MSFTNGP10.phx.gbl...
>I am having trouble connecting to my local sql server from either the
>Server Explorer or vb.net code. The problem is connected to the Norton
>Internet Security 2005 Firewall as when I disable Norton everything works
>and if Norton is enabled but the PC is not plugged into the network it also
>works.
> When I am connected to the network the Firewall does pop up asking whether
> or not I want to allow my vb.net program to access a DNS. I have tried
> using localhost, the hardcoded IP of my machine, and my machine name (the
> usual method) without any success. It is as if Visual Studio always tries
> to resolve the machine name and cannot. VB6 programs ,dbArtisan, and SQL
> Enterprise Manager all work fine at the same time Visual Studio/VB.Net
> does not.
> Any ideas?
> Thanks,
> Mark Lewis
> mdlewis@.mdlewis.com
> P.S I am using the latest production/old Visual Studio and SQL Server on
> XP with all SP applied.
>|||Resubmitting this with my new MSDN Alias to qualify for support.
Thanks and sorry about the double post,
Mark Lewis
mdlewis@.mdlewis.com
"Mark Lewis" <mdlewis@.mdlewis.com> wrote in message
news:u$P2swmHFHA.3336@.TK2MSFTNGP10.phx.gbl...
>I am having trouble connecting to my local sql server from either the
>Server Explorer or vb.net code. The problem is connected to the Norton
>Internet Security 2005 Firewall as when I disable Norton everything works
>and if Norton is enabled but the PC is not plugged into the network it also
>works.
> When I am connected to the network the Firewall does pop up asking whether
> or not I want to allow my vb.net program to access a DNS. I have tried
> using localhost, the hardcoded IP of my machine, and my machine name (the
> usual method) without any success. It is as if Visual Studio always tries
> to resolve the machine name and cannot. VB6 programs ,dbArtisan, and SQL
> Enterprise Manager all work fine at the same time Visual Studio/VB.Net
> does not.
> Any ideas?
> Thanks,
> Mark Lewis
> mdlewis@.mdlewis.com
> P.S I am using the latest production/old Visual Studio and SQL Server on
> XP with all SP applied.
>
Explorer or vb.net code. The problem is connected to the Norton Internet
Security 2005 Firewall as when I disable Norton everything works and if
Norton is enabled but the PC is not plugged into the network it also works.
When I am connected to the network the Firewall does pop up asking whether
or not I want to allow my vb.net program to access a DNS. I have tried using
localhost, the hardcoded IP of my machine, and my machine name (the usual
method) without any success. It is as if Visual Studio always tries to
resolve the machine name and cannot. VB6 programs ,dbArtisan, and SQL
Enterprise Manager all work fine at the same time Visual Studio/VB.Net does
not.
Any ideas?
Thanks,
Mark Lewis
mdlewis@.mdlewis.com
P.S I am using the latest production/old Visual Studio and SQL Server on XP
with all SP applied.here's an idea: configure the Norton product so that your machine can access
DNS.
-- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik
Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
"Mark Lewis" <mdlewis@.mdlewis.com> wrote in message
news:u$P2swmHFHA.3336@.TK2MSFTNGP10.phx.gbl...
>I am having trouble connecting to my local sql server from either the
>Server Explorer or vb.net code. The problem is connected to the Norton
>Internet Security 2005 Firewall as when I disable Norton everything works
>and if Norton is enabled but the PC is not plugged into the network it also
>works.
> When I am connected to the network the Firewall does pop up asking whether
> or not I want to allow my vb.net program to access a DNS. I have tried
> using localhost, the hardcoded IP of my machine, and my machine name (the
> usual method) without any success. It is as if Visual Studio always tries
> to resolve the machine name and cannot. VB6 programs ,dbArtisan, and SQL
> Enterprise Manager all work fine at the same time Visual Studio/VB.Net
> does not.
> Any ideas?
> Thanks,
> Mark Lewis
> mdlewis@.mdlewis.com
> P.S I am using the latest production/old Visual Studio and SQL Server on
> XP with all SP applied.
>|||Resubmitting this with my new MSDN Alias.
Thanks,
Mark Lewis
mdlewis@.mdlewis.com
"Mark Lewis" <mdlewis@.mdlewis.com> wrote in message
news:u$P2swmHFHA.3336@.TK2MSFTNGP10.phx.gbl...
>I am having trouble connecting to my local sql server from either the
>Server Explorer or vb.net code. The problem is connected to the Norton
>Internet Security 2005 Firewall as when I disable Norton everything works
>and if Norton is enabled but the PC is not plugged into the network it also
>works.
> When I am connected to the network the Firewall does pop up asking whether
> or not I want to allow my vb.net program to access a DNS. I have tried
> using localhost, the hardcoded IP of my machine, and my machine name (the
> usual method) without any success. It is as if Visual Studio always tries
> to resolve the machine name and cannot. VB6 programs ,dbArtisan, and SQL
> Enterprise Manager all work fine at the same time Visual Studio/VB.Net
> does not.
> Any ideas?
> Thanks,
> Mark Lewis
> mdlewis@.mdlewis.com
> P.S I am using the latest production/old Visual Studio and SQL Server on
> XP with all SP applied.
>|||Resubmitting this with my new MSDN Alias to qualify for support.
Thanks and sorry about the double post,
Mark Lewis
mdlewis@.mdlewis.com
"Mark Lewis" <mdlewis@.mdlewis.com> wrote in message
news:u$P2swmHFHA.3336@.TK2MSFTNGP10.phx.gbl...
>I am having trouble connecting to my local sql server from either the
>Server Explorer or vb.net code. The problem is connected to the Norton
>Internet Security 2005 Firewall as when I disable Norton everything works
>and if Norton is enabled but the PC is not plugged into the network it also
>works.
> When I am connected to the network the Firewall does pop up asking whether
> or not I want to allow my vb.net program to access a DNS. I have tried
> using localhost, the hardcoded IP of my machine, and my machine name (the
> usual method) without any success. It is as if Visual Studio always tries
> to resolve the machine name and cannot. VB6 programs ,dbArtisan, and SQL
> Enterprise Manager all work fine at the same time Visual Studio/VB.Net
> does not.
> Any ideas?
> Thanks,
> Mark Lewis
> mdlewis@.mdlewis.com
> P.S I am using the latest production/old Visual Studio and SQL Server on
> XP with all SP applied.
>
Cannot connect to Local SQL Server
I am having trouble connecting to my local sql server from either the Server
Explorer or vb.net code. The problem is connected to the Norton Internet
Security 2005 Firewall as when I disable Norton everything works and if
Norton is enabled but the PC is not plugged into the network it also works.
When I am connected to the network the Firewall does pop up asking whether
or not I want to allow my vb.net program to access a DNS. I have tried using
localhost, the hardcoded IP of my machine, and my machine name (the usual
method) without any success. It is as if Visual Studio always tries to
resolve the machine name and cannot. VB6 programs ,dbArtisan, and SQL
Enterprise Manager all work fine at the same time Visual Studio/VB.Net does
not.
Any ideas?
Thanks,
Mark Lewis
mdlewis@.mdlewis.com
P.S I am using the latest production/old Visual Studio and SQL Server on XP
with all SP applied.
here's an idea: configure the Norton product so that your machine can access
DNS.
-- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik
Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
"Mark Lewis" <mdlewis@.mdlewis.com> wrote in message
news:u$P2swmHFHA.3336@.TK2MSFTNGP10.phx.gbl...
>I am having trouble connecting to my local sql server from either the
>Server Explorer or vb.net code. The problem is connected to the Norton
>Internet Security 2005 Firewall as when I disable Norton everything works
>and if Norton is enabled but the PC is not plugged into the network it also
>works.
> When I am connected to the network the Firewall does pop up asking whether
> or not I want to allow my vb.net program to access a DNS. I have tried
> using localhost, the hardcoded IP of my machine, and my machine name (the
> usual method) without any success. It is as if Visual Studio always tries
> to resolve the machine name and cannot. VB6 programs ,dbArtisan, and SQL
> Enterprise Manager all work fine at the same time Visual Studio/VB.Net
> does not.
> Any ideas?
> Thanks,
> Mark Lewis
> mdlewis@.mdlewis.com
> P.S I am using the latest production/old Visual Studio and SQL Server on
> XP with all SP applied.
>
|||Resubmitting this with my new MSDN Alias.
Thanks,
Mark Lewis
mdlewis@.mdlewis.com
"Mark Lewis" <mdlewis@.mdlewis.com> wrote in message
news:u$P2swmHFHA.3336@.TK2MSFTNGP10.phx.gbl...
>I am having trouble connecting to my local sql server from either the
>Server Explorer or vb.net code. The problem is connected to the Norton
>Internet Security 2005 Firewall as when I disable Norton everything works
>and if Norton is enabled but the PC is not plugged into the network it also
>works.
> When I am connected to the network the Firewall does pop up asking whether
> or not I want to allow my vb.net program to access a DNS. I have tried
> using localhost, the hardcoded IP of my machine, and my machine name (the
> usual method) without any success. It is as if Visual Studio always tries
> to resolve the machine name and cannot. VB6 programs ,dbArtisan, and SQL
> Enterprise Manager all work fine at the same time Visual Studio/VB.Net
> does not.
> Any ideas?
> Thanks,
> Mark Lewis
> mdlewis@.mdlewis.com
> P.S I am using the latest production/old Visual Studio and SQL Server on
> XP with all SP applied.
>
|||Resubmitting this with my new MSDN Alias to qualify for support.
Thanks and sorry about the double post,
Mark Lewis
mdlewis@.mdlewis.com
"Mark Lewis" <mdlewis@.mdlewis.com> wrote in message
news:u$P2swmHFHA.3336@.TK2MSFTNGP10.phx.gbl...
>I am having trouble connecting to my local sql server from either the
>Server Explorer or vb.net code. The problem is connected to the Norton
>Internet Security 2005 Firewall as when I disable Norton everything works
>and if Norton is enabled but the PC is not plugged into the network it also
>works.
> When I am connected to the network the Firewall does pop up asking whether
> or not I want to allow my vb.net program to access a DNS. I have tried
> using localhost, the hardcoded IP of my machine, and my machine name (the
> usual method) without any success. It is as if Visual Studio always tries
> to resolve the machine name and cannot. VB6 programs ,dbArtisan, and SQL
> Enterprise Manager all work fine at the same time Visual Studio/VB.Net
> does not.
> Any ideas?
> Thanks,
> Mark Lewis
> mdlewis@.mdlewis.com
> P.S I am using the latest production/old Visual Studio and SQL Server on
> XP with all SP applied.
>
Explorer or vb.net code. The problem is connected to the Norton Internet
Security 2005 Firewall as when I disable Norton everything works and if
Norton is enabled but the PC is not plugged into the network it also works.
When I am connected to the network the Firewall does pop up asking whether
or not I want to allow my vb.net program to access a DNS. I have tried using
localhost, the hardcoded IP of my machine, and my machine name (the usual
method) without any success. It is as if Visual Studio always tries to
resolve the machine name and cannot. VB6 programs ,dbArtisan, and SQL
Enterprise Manager all work fine at the same time Visual Studio/VB.Net does
not.
Any ideas?
Thanks,
Mark Lewis
mdlewis@.mdlewis.com
P.S I am using the latest production/old Visual Studio and SQL Server on XP
with all SP applied.
here's an idea: configure the Norton product so that your machine can access
DNS.
-- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik
Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
"Mark Lewis" <mdlewis@.mdlewis.com> wrote in message
news:u$P2swmHFHA.3336@.TK2MSFTNGP10.phx.gbl...
>I am having trouble connecting to my local sql server from either the
>Server Explorer or vb.net code. The problem is connected to the Norton
>Internet Security 2005 Firewall as when I disable Norton everything works
>and if Norton is enabled but the PC is not plugged into the network it also
>works.
> When I am connected to the network the Firewall does pop up asking whether
> or not I want to allow my vb.net program to access a DNS. I have tried
> using localhost, the hardcoded IP of my machine, and my machine name (the
> usual method) without any success. It is as if Visual Studio always tries
> to resolve the machine name and cannot. VB6 programs ,dbArtisan, and SQL
> Enterprise Manager all work fine at the same time Visual Studio/VB.Net
> does not.
> Any ideas?
> Thanks,
> Mark Lewis
> mdlewis@.mdlewis.com
> P.S I am using the latest production/old Visual Studio and SQL Server on
> XP with all SP applied.
>
|||Resubmitting this with my new MSDN Alias.
Thanks,
Mark Lewis
mdlewis@.mdlewis.com
"Mark Lewis" <mdlewis@.mdlewis.com> wrote in message
news:u$P2swmHFHA.3336@.TK2MSFTNGP10.phx.gbl...
>I am having trouble connecting to my local sql server from either the
>Server Explorer or vb.net code. The problem is connected to the Norton
>Internet Security 2005 Firewall as when I disable Norton everything works
>and if Norton is enabled but the PC is not plugged into the network it also
>works.
> When I am connected to the network the Firewall does pop up asking whether
> or not I want to allow my vb.net program to access a DNS. I have tried
> using localhost, the hardcoded IP of my machine, and my machine name (the
> usual method) without any success. It is as if Visual Studio always tries
> to resolve the machine name and cannot. VB6 programs ,dbArtisan, and SQL
> Enterprise Manager all work fine at the same time Visual Studio/VB.Net
> does not.
> Any ideas?
> Thanks,
> Mark Lewis
> mdlewis@.mdlewis.com
> P.S I am using the latest production/old Visual Studio and SQL Server on
> XP with all SP applied.
>
|||Resubmitting this with my new MSDN Alias to qualify for support.
Thanks and sorry about the double post,
Mark Lewis
mdlewis@.mdlewis.com
"Mark Lewis" <mdlewis@.mdlewis.com> wrote in message
news:u$P2swmHFHA.3336@.TK2MSFTNGP10.phx.gbl...
>I am having trouble connecting to my local sql server from either the
>Server Explorer or vb.net code. The problem is connected to the Norton
>Internet Security 2005 Firewall as when I disable Norton everything works
>and if Norton is enabled but the PC is not plugged into the network it also
>works.
> When I am connected to the network the Firewall does pop up asking whether
> or not I want to allow my vb.net program to access a DNS. I have tried
> using localhost, the hardcoded IP of my machine, and my machine name (the
> usual method) without any success. It is as if Visual Studio always tries
> to resolve the machine name and cannot. VB6 programs ,dbArtisan, and SQL
> Enterprise Manager all work fine at the same time Visual Studio/VB.Net
> does not.
> Any ideas?
> Thanks,
> Mark Lewis
> mdlewis@.mdlewis.com
> P.S I am using the latest production/old Visual Studio and SQL Server on
> XP with all SP applied.
>
cannot connect to datasource foodmart in analysis services
hi,
I'm connecting to my server in another machine through
analysis services. i'm using SQL server enterprise
edition with analysis services and sp3 and sp3a. while
connecting to the datasource in food mart in the server
machine , i'm getting an error that connection to the
datasource is not done. i cant understand wht the problem
is ? its working fine in the server machine and i chked
the connection there . its ok. working and
connected .whts the problem in the client machine while
connecting to the server ? shd i need to change any
settings ?
can anyone help me to sort out this problem ?
Thanks in AdvanceIf you have Analysis Services SP3 on the server (which is a separate
install from SQL sp3 or sp3a) then you must also have Analysis Services SP3
on the client machines.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
I'm connecting to my server in another machine through
analysis services. i'm using SQL server enterprise
edition with analysis services and sp3 and sp3a. while
connecting to the datasource in food mart in the server
machine , i'm getting an error that connection to the
datasource is not done. i cant understand wht the problem
is ? its working fine in the server machine and i chked
the connection there . its ok. working and
connected .whts the problem in the client machine while
connecting to the server ? shd i need to change any
settings ?
can anyone help me to sort out this problem ?
Thanks in AdvanceIf you have Analysis Services SP3 on the server (which is a separate
install from SQL sp3 or sp3a) then you must also have Analysis Services SP3
on the client machines.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
cannot connect to datasource foodmart in analysis services
hi,
I'm connecting to my server in another machine through
analysis services. i'm using SQL server enterprise
edition with analysis services and sp3 and sp3a. while
connecting to the datasource in food mart in the server
machine , i'm getting an error that connection to the
datasource is not done. i cant understand wht the problem
is ? its working fine in the server machine and i chked
the connection there . its ok. working and
connected .whts the problem in the client machine while
connecting to the server ? shd i need to change any
settings ?
can anyone help me to sort out this problem ?
Thanks in Advance
If you have Analysis Services SP3 on the server (which is a separate
install from SQL sp3 or sp3a) then you must also have Analysis Services SP3
on the client machines.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
I'm connecting to my server in another machine through
analysis services. i'm using SQL server enterprise
edition with analysis services and sp3 and sp3a. while
connecting to the datasource in food mart in the server
machine , i'm getting an error that connection to the
datasource is not done. i cant understand wht the problem
is ? its working fine in the server machine and i chked
the connection there . its ok. working and
connected .whts the problem in the client machine while
connecting to the server ? shd i need to change any
settings ?
can anyone help me to sort out this problem ?
Thanks in Advance
If you have Analysis Services SP3 on the server (which is a separate
install from SQL sp3 or sp3a) then you must also have Analysis Services SP3
on the client machines.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
Friday, February 10, 2012
cannot connect to a named instance via TCP/IP
Are you connecting to your office through VPN or is your
firewall just configured to allow you to access port 1433?
If it is the latter, you must configure your firewall to
allow you access on the port that the named instance is
listening on (each instance has its own port and only the
default instance will be listening on 1433). You can
find the port the named instance is using by looking at
the TCP/IP properties for the instance in the server
network utility.
Hope this helps.
Tim
office.
sql server, say SQL_instance1.
named instance from my home workstation. Therefore, I
have already set a portmapping (1433) on my company
firewall and use the IP address, say 61.88.17.3, to
connect the sql server at my home.
the EM and the error message is "SQL server not found or
access denied". I am sure the login name and password is
correct and the firewall setting is correct also (Since I
can use telnet to connect the server, the command is :
telnet 61.88.17.3 1433).
remote sql server in my workstation EM.
I use 1433 for my named instance and the I have configured the firewall to a
llow 1433.
I even try to configure the firewall to allow all TCP/IP, but I still cannot
connect to my SQL server.
-- Tim Richardson wrote: --
Are you connecting to your office through VPN or is your
firewall just configured to allow you to access port 1433?
If it is the latter, you must configure your firewall to
allow you access on the port that the named instance is
listening on (each instance has its own port and only the
default instance will be listening on 1433). You can
find the port the named instance is using by looking at
the TCP/IP properties for the instance in the server
network utility.
Hope this helps.
Tim
sql server, say SQL_instance1.
named instance from my home workstation. Therefore, I
have already set a portmapping (1433) on my company
firewall and use the IP address, say 61.88.17.3, to
connect the sql server at my home.
the EM and the error message is "SQL server not found or
access denied". I am sure the login name and password is
correct and the firewall setting is correct also (Since I
can use telnet to connect the server, the command is :
telnet 61.88.17.3 1433).
firewall just configured to allow you to access port 1433?
If it is the latter, you must configure your firewall to
allow you access on the port that the named instance is
listening on (each instance has its own port and only the
default instance will be listening on 1433). You can
find the port the named instance is using by looking at
the TCP/IP properties for the instance in the server
network utility.
Hope this helps.
Tim
quote:
>--Original Message--
>Hi all,
>I have a SQL server running on a WIN2k server at my
office.
quote:
>I have an application running on a named instance of the
sql server, say SQL_instance1.
quote:
>Due to some reason, I have to connect to the SQL server
named instance from my home workstation. Therefore, I
have already set a portmapping (1433) on my company
firewall and use the IP address, say 61.88.17.3, to
connect the sql server at my home.
quote:
>However, I find that I cannot register the sql server at
the EM and the error message is "SQL server not found or
access denied". I am sure the login name and password is
correct and the firewall setting is correct also (Since I
can use telnet to connect the server, the command is :
telnet 61.88.17.3 1433).
quote:
>Anyone know how to solve this problem '
>I use the following connection string to register the
remote sql server in my workstation EM.
quote:thx for your reply.
>61.88.17.3\SQL_instance1
>Thank in advance
>Regards,
>ong
>.
>
I use 1433 for my named instance and the I have configured the firewall to a
llow 1433.
I even try to configure the firewall to allow all TCP/IP, but I still cannot
connect to my SQL server.
-- Tim Richardson wrote: --
Are you connecting to your office through VPN or is your
firewall just configured to allow you to access port 1433?
If it is the latter, you must configure your firewall to
allow you access on the port that the named instance is
listening on (each instance has its own port and only the
default instance will be listening on 1433). You can
find the port the named instance is using by looking at
the TCP/IP properties for the instance in the server
network utility.
Hope this helps.
Tim
quote:
>--Original Message--
>Hi all,
office.[QUOTE]
>I have an application running on a named instance of the
sql server, say SQL_instance1.
quote:
>Due to some reason, I have to connect to the SQL server
named instance from my home workstation. Therefore, I
have already set a portmapping (1433) on my company
firewall and use the IP address, say 61.88.17.3, to
connect the sql server at my home.
quote:
>However, I find that I cannot register the sql server at
the EM and the error message is "SQL server not found or
access denied". I am sure the login name and password is
correct and the firewall setting is correct also (Since I
can use telnet to connect the server, the command is :
telnet 61.88.17.3 1433).
quote:
>Anyone know how to solve this problem '
remote sql server in my workstation EM.[QUOTE]
>61.88.17.3\SQL_instance1
>ong
>.
>
Cannot connect remotely to SQLExpress via SQL Server Management Studio Express
Hi all,
I'm having a little trouble connecting to a SQLExpress instance on a remote domain using SQL Server Management Studio Express.
I've read that by default the program is set up locally only, so have edited the Surface Area Configuration. It only gives me the option to edit 'Services and Connections' on the localhost, but have edited the Remote Connections to use TCP/IP and Named Pipes.
In the Management Studio, I enter the server name, and login credentials. On the Connection Properties tab I changed the network protocol to TCP/IP though everytime I attempt to connect I get the following error message:
Any help would be greatly appreciated.
Rich
Hello,
Does this help you?http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx
Regards,
Louis
|||Hmm, I followed the steps through, the only difference seemed the firewall exceptions which I have now edited, but still get the same error message.
Any ideas?
|||from the client machine, can you ping the database server? Can you log the denial on the sql server box when you connect to it?
|||How would I go about doing this?
Cheers
Subscribe to:
Posts (Atom)