No Failover and client crashes ODBC DSN Setting for Failover in connection String

We have set up Mirroring with a witness server and everything works fine when we failover from the SQL Management console.

However, if we failover when our Maccola client is connected, the client blows up - clearly because it can no longer connect to the database.

The ODBC DSN used by the Maccola client shows a checkbox for the 'select a failover server' but the checkbox is grayed out.

Also the summary of settings for the DSN at the end of the wizard reveals that the failover to server (y/N) option is set to N.

The default setting for this DSN is 'populate the remaining values by querying the server' but it doesn't appear to be getting the settings for failover from the server or any other interactive DSN settings either. The server is clearly set for mirroring.

Another suspicious item is that the DSN cannot connect to the server with SA permissions, even though the server is set to mixed security and we use the correct authentication.

Is it possible that the client MACHINE is not authenticating with the domain or sql server properly. We are logged into the client with the domain account that is the SQL admin account on the sql server box.

We should be able to interact with the sql server settings through the ODBC DSN on the client shoulnd't we?

Are we missing a service pack on the client?

Thanks,

Kimball

Have you referred to Maccola vendor in this case about the compatibility, I would guess this is to with that drivers.

No Failover and client crashes ODBC DSN Setting for Failover in connection String

We have set up Mirroring with a witness server and everything works fine when we failover from the SQL Management console.

However, if we failover when our Maccola client is connected, the client blows up - clearly because it can no longer connect to the database.

The ODBC DSN used by the Maccola client shows a checkbox for the 'select a failover server' but the checkbox is grayed out.

Also the summary of settings for the DSN at the end of the wizard reveals that the failover to server (y/N) option is set to N.

The default setting for this DSN is 'populate the remaining values by querying the server' but it doesn't appear to be getting the settings for failover from the server or any other interactive DSN settings either. The server is clearly set for mirroring.

Another suspicious item is that the DSN cannot connect to the server with SA permissions, even though the server is set to mixed security and we use the correct authentication.

Is it possible that the client MACHINE is not authenticating with the domain or sql server properly. We are logged into the client with the domain account that is the SQL admin account on the sql server box.

We should be able to interact with the sql server settings through the ODBC DSN on the client shoulnd't we?

Are we missing a service pack on the client?

Thanks,

Kimball

Have you referred to Maccola vendor in this case about the compatibility, I would guess this is to with that drivers.

No Data-Driven Subscription button

I have created a report and published it on the reporting server. My connection is working, and I have followed the steps in the BOL tutorial for "Defining a Data-Driven Subscription" i.e. Credentials stored securely on report server, using windows credentials when connecting to the data source. When I click on "Subscriptions", I only see "New Subscriptions". However, when I look at other reports (not even created by me), I see the option to create data driven subscriptions. Can somebody tell me what I need to do to see this?I got it; the report cannot be in the "My Reports" folder.

No connection to local SQL Server when no network connection

Hi !
We are using Windows XP,
ADO.NET in our application (programming language: C#),
MS SQL Server 2000.
The computer is a SONY notebook.
SQL server is running on the same machine as the application.
The application has worked in many, many cases under W2K and even XP.
But on that computer it doesn't work:
When there is no network connection,
then the application CANNOT connect to our DB.
On the other hand, Enterprise Manager CAN connect.
When we plug in the network and restart the computer,
then the application CAN connect.
However, SQL Server is running locally !
The connection string for connecting our app to the database is something
like:
sqlConnection.ConnectionString =
"packet size=4096;user id=BIS;persist security info=false;initial
catalog=BIS; server=(local)";
How can we fix that problem ?
Your kind help would be appreciated.
Peter
I have had similar issues - am not sure why though.
However,I seem to be able to connect by either using the (local) or the
actual PC name - it just seems to change its behaviour depending on the
network connectivity status.
Hope this is of some help.
LeMuppet
lemuppet
Posted via http://www.webservertalk.com
View this thread: http://www.webservertalk.com/message411117.html

No connection to local SQL Server when no network connection

Hi !
We are using Windows XP,
ADO in our application,
MS SQL Server 2000.
(Programming language: Delphi 5;
ADO components: from Adonis;
The computer is a SONY notebook).
SQL server is running on the same machine as the application.
The application has worked in many, many cases under W2K and even XP.
But on that computer it doesn't work:
When there is no network connection, then the application CANNOT connect to
our DB.
On the other hand, Enterprise Manager CAN connect.
When we plug in the network and restart the computer, then the application
CAN connect.
However, SQL Server is running locally !
The connection string for connecting our app to the database is something
like:
'Provider=SQLOLEDB.1; Password="";Persist Security Info=True;User
ID=Bis;Initial Catalog=BIS;Data Source=127.0.0.1'
How can we fix that problem ?
Is this a problem of MS SQL Server administration ?
Your kind help would be appreciated.
PeterThe soluition is to use named pipes to connect as
Enterprise manager will if IP: 127.0.0.1 cannot connect.
Change your connection string to :
'Provider=SQLOLEDB.1; Password="";Persist Security
Info=True;User
ID=Bis;Initial Catalog=BIS;Data Source=(local)'
This should fix the problem.
>--Original Message--
>Hi !
>We are using Windows XP,
>ADO in our application,
>MS SQL Server 2000.
>(Programming language: Delphi 5;
> ADO components: from Adonis;
> The computer is a SONY notebook).
>SQL server is running on the same machine as the
application.
>The application has worked in many, many cases under W2K
and even XP.
>But on that computer it doesn't work:
>When there is no network connection, then the application
CANNOT connect to
>our DB.
>On the other hand, Enterprise Manager CAN connect.
>When we plug in the network and restart the computer,
then the application
>CAN connect.
>However, SQL Server is running locally !
>The connection string for connecting our app to the
database is something
>like:
> 'Provider=SQLOLEDB.1; Password="";Persist Security
Info=True;User
>ID=Bis;Initial Catalog=BIS;Data Source=127.0.0.1'
>How can we fix that problem ?
>Is this a problem of MS SQL Server administration ?
>Your kind help would be appreciated.
>Peter
>
>.
>|||> Change your connection string to :
> 'Provider=SQLOLEDB.1; Password="";Persist Security
> Info=True;User
> ID=Bis;Initial Catalog=BIS;Data Source=(local)'
It worked.
Thanks a lot !

No connection to local SQL Server when no network connection

The soluition is to use named pipes to connect as
Enterprise manager will if IP: 127.0.0.1 cannot connect.
Change your connection string to :
'Provider=SQLOLEDB.1; Password="";Persist Security
Info=True;User
ID=Bis;Initial Catalog=BIS;Data Source=(local)'
This should fix the problem.

>--Original Message--
>Hi !
>We are using Windows XP,
>ADO in our application,
>MS SQL Server 2000.
>(Programming language: Delphi 5;
> ADO components: from Adonis;
> The computer is a SONY notebook).
>SQL server is running on the same machine as the
application.
>The application has worked in many, many cases under W2K
and even XP.
>But on that computer it doesn't work:
>When there is no network connection, then the application
CANNOT connect to
>our DB.
>On the other hand, Enterprise Manager CAN connect.
>When we plug in the network and restart the computer,
then the application
>CAN connect.
>However, SQL Server is running locally !
>The connection string for connecting our app to the
database is something
>like:
> 'Provider=SQLOLEDB.1; Password="";Persist Security
Info=True;User
>ID=Bis;Initial Catalog=BIS;Data Source=127.0.0.1'
>How can we fix that problem ?
>Is this a problem of MS SQL Server administration ?
>Your kind help would be appreciated.
>Peter
>
>.
>
> Change your connection string to :
> 'Provider=SQLOLEDB.1; Password="";Persist Security
> Info=True;User
> ID=Bis;Initial Catalog=BIS;Data Source=(local)'
It worked.
Thanks a lot !

No connection limitation with SQL Express 2005?

MSDE had the limitation of 25 concurrent connections.
It seems that SQL Express 2005 doesn't have this limitation. Is that
correct? Does Express support as many connections as the "full" SQL 2005
server?"the friendly display name"
<thefriendlydisplayname@.discussions.microsoft.com> wrote in message
news:A0E3673D-E984-4EFA-82C2-1A51E6D38945@.microsoft.com...
> MSDE had the limitation of 25 concurrent connections.
No it didn't. It had a query governor which throttled performance after 5
concurrent workloads.

> It seems that SQL Express 2005 doesn't have this limitation. Is that
> correct?
Yes.

>Does Express support as many connections as the "full" SQL 2005
> server?
Yes. Althought SQL Server Express Edition is limited to 1GB of RAM and 1CPU
which will impose some limit on the number of users it can serve.
David|||Hi
And to add, there are no SQL Server limits, but if you run on Windows 2000
Pro or Windows XP, the OS has a limit of number of incoming network
connection it accepts, and that is 10.
On Server editions of the OS's, there are no limits.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:uxhcKhs5FHA.1864@.TK2MSFTNGP12.phx.gbl...
> "the friendly display name"
> <thefriendlydisplayname@.discussions.microsoft.com> wrote in message
> news:A0E3673D-E984-4EFA-82C2-1A51E6D38945@.microsoft.com...
> No it didn't. It had a query governor which throttled performance after 5
> concurrent workloads.
>
> Yes.
>
> Yes. Althought SQL Server Express Edition is limited to 1GB of RAM and
> 1CPU which will impose some limit on the number of users it can serve.
> David
>|||> And to add, there are no SQL Server limits, but if you run on Windows 2000
> Pro or Windows XP, the OS has a limit of number of incoming network
> connection it accepts, and that is 10.
IIRC, that is Redirector connections, not socket connections. Has anyone
tried more then 10 sql connections on XP?
William Stacey [MVP]sql

No connection limitation with SQL Express 2005?

MSDE had the limitation of 25 concurrent connections.
It seems that SQL Express 2005 doesn't have this limitation. Is that
correct? Does Express support as many connections as the "full" SQL 2005
server?"the friendly display name"
<thefriendlydisplayname@.discussions.microsoft.com> wrote in message
news:A0E3673D-E984-4EFA-82C2-1A51E6D38945@.microsoft.com...
> MSDE had the limitation of 25 concurrent connections.
No it didn't. It had a query governor which throttled performance after 5
concurrent workloads.
> It seems that SQL Express 2005 doesn't have this limitation. Is that
> correct?
Yes.
>Does Express support as many connections as the "full" SQL 2005
> server?
Yes. Althought SQL Server Express Edition is limited to 1GB of RAM and 1CPU
which will impose some limit on the number of users it can serve.
David|||Hi
And to add, there are no SQL Server limits, but if you run on Windows 2000
Pro or Windows XP, the OS has a limit of number of incoming network
connection it accepts, and that is 10.
On Server editions of the OS's, there are no limits.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:uxhcKhs5FHA.1864@.TK2MSFTNGP12.phx.gbl...
> "the friendly display name"
> <thefriendlydisplayname@.discussions.microsoft.com> wrote in message
> news:A0E3673D-E984-4EFA-82C2-1A51E6D38945@.microsoft.com...
>> MSDE had the limitation of 25 concurrent connections.
> No it didn't. It had a query governor which throttled performance after 5
> concurrent workloads.
>> It seems that SQL Express 2005 doesn't have this limitation. Is that
>> correct?
> Yes.
>>Does Express support as many connections as the "full" SQL 2005
>> server?
> Yes. Althought SQL Server Express Edition is limited to 1GB of RAM and
> 1CPU which will impose some limit on the number of users it can serve.
> David
>|||> And to add, there are no SQL Server limits, but if you run on Windows 2000
> Pro or Windows XP, the OS has a limit of number of incoming network
> connection it accepts, and that is 10.
IIRC, that is Redirector connections, not socket connections. Has anyone
tried more then 10 sql connections on XP?
--
William Stacey [MVP]

No connection limitation with SQL Express 2005?

MSDE had the limitation of 25 concurrent connections.
It seems that SQL Express 2005 doesn't have this limitation. Is that
correct? Does Express support as many connections as the "full" SQL 2005
server?
"the friendly display name"
<thefriendlydisplayname@.discussions.microsoft.com> wrote in message
news:A0E3673D-E984-4EFA-82C2-1A51E6D38945@.microsoft.com...
> MSDE had the limitation of 25 concurrent connections.
No it didn't. It had a query governor which throttled performance after 5
concurrent workloads.

> It seems that SQL Express 2005 doesn't have this limitation. Is that
> correct?
Yes.

>Does Express support as many connections as the "full" SQL 2005
> server?
Yes. Althought SQL Server Express Edition is limited to 1GB of RAM and 1CPU
which will impose some limit on the number of users it can serve.
David
|||Hi
And to add, there are no SQL Server limits, but if you run on Windows 2000
Pro or Windows XP, the OS has a limit of number of incoming network
connection it accepts, and that is 10.
On Server editions of the OS's, there are no limits.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:uxhcKhs5FHA.1864@.TK2MSFTNGP12.phx.gbl...
> "the friendly display name"
> <thefriendlydisplayname@.discussions.microsoft.com> wrote in message
> news:A0E3673D-E984-4EFA-82C2-1A51E6D38945@.microsoft.com...
> No it didn't. It had a query governor which throttled performance after 5
> concurrent workloads.
> Yes.
>
> Yes. Althought SQL Server Express Edition is limited to 1GB of RAM and
> 1CPU which will impose some limit on the number of users it can serve.
> David
>
|||> And to add, there are no SQL Server limits, but if you run on Windows 2000
> Pro or Windows XP, the OS has a limit of number of incoming network
> connection it accepts, and that is 10.
IIRC, that is Redirector connections, not socket connections. Has anyone
tried more then 10 sql connections on XP?
William Stacey [MVP]

No connection could be made because the target machine actively refused it

Hi,

I have successfully created a project (using VS.Net 2003 and SQL Server Analysis Services 2000) which is dynamically retrieving dimensions, levels, and members, and i generating and executing a query as per user needs and requirements. However when I tried to deploy the project on another machine, even though the apps is running fine, and the query getting generated, when its trying to show the data in the report-display page using ADOMD.Net, the following error was shown.

No connection could be made because the target machine actively refused it

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[SocketException (0x274d): No connection could be made because the target machine actively refused it]

System.Net.Sockets.Socket.Connect(EndPoint remoteEP) +307

System.Net.Sockets.TcpClient.Connect(IPEndPoint remoteEP) +24

System.Net.Sockets.TcpClient.Connect(IPAddress address, Int32 port) +81

Microsoft.AnalysisServices.AdomdClient.XmlaClient.GetTcpClient(ConnectionInfo connectionInfo) +208

[AdomdConnectionException: A connection cannot be made. Ensure that the server is running.]

Microsoft.AnalysisServices.AdomdClient.XmlaClient.GetTcpClient(ConnectionInfo connectionInfo) +384

Microsoft.AnalysisServices.AdomdClient.XmlaClient.OpenTcpConnection(ConnectionInfo connectionInfo) +51

Microsoft.AnalysisServices.AdomdClient.XmlaClient.Connect(ConnectionInfo connectionInfo, Boolean beginSession) +398

Microsoft.AnalysisServices.AdomdClient.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.AdomdConnection+IXmlaClientProviderEx.ConnectXmla() +124

Microsoft.AnalysisServices.AdomdClient.AdomdConnection.ConnectToXMLA(Boolean createSession, Boolean isHTTP) +144

Microsoft.AnalysisServices.AdomdClient.AdomdConnection.Open() +601

cubicdimension.Reportdisp.Page_Load(Object sender, EventArgs e) in E:\Inetpub\wwwroot\cubicdimension\Reportdisp.aspx.vb:65

System.Web.UI.Control.OnLoad(EventArgs e) +67

System.Web.UI.Control.LoadRecursive() +35

System.Web.UI.Page.ProcessRequestMain() +731

May I mention here, that the computer where I tried deploying, has SQL Server 2000 as well as SQL Server 2005. I tried reinstalling MSXML, but the computer already has a higher version of MSXML.

Any help in this regard would be appreciated.

Best Wishes.

Check Programs/SQL Server 2005/ Configuration tools/SQL Server Surface Area Configuration.

In "Surface Area Configuration for services and connection", you click on the service and remote connections.

See that you have local and remote connections activated.

HTH

Thomas Ivarsson

No connection could be made because the target machine actively refused it

Hello,

I am not sure if this is the right forum.

This is the first time that I have seen this error,

No connection could be made because the target machine actively refused it

I have a web app that when some one inserts text in a text box and clicks a button it creates a new web page and a new table in the database. Up until this point it has always worked. A datalist returns the data. In the datalist there is a hyperlink that when clicked takes the client to the new webpage. But for some reason it is not working now and that is the error above.

I am lost. Any help appreciated.

Thanks Matt

I figured it out.

Thanks

Matt

No connection

Hello,

New development machine with Sql Server Express and Visual Web Developer.

I created a database then tried to connect from a test page on localhost and it worked. Then I tried from the internet domain and could not. So under the

Surface Area Configuration, I change the Remote Connections to Using both TCP/IP and named pipes and restarted the Database Engine. But

I still could not connect. So I restarted the machine. Now I can't view the page on localhost either. I can view a different web page so the Web server is

working.

I get the following as the exception:Error reading the database: Cannot open user default database. Login failed.Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.

My connection string is: "Data Source=.\SQLEXPRESS;Integrated Security=True;AttachDBFilename=|DataDirectory|Externalresearch.mdf;User Instance=True"

Any suggestions?

Okay I found out why. If I have Web Developer open (with the database connection open) I cannot connect from the browser. But

if I close Web Developer then I can connect from the browser (ie, view my test page).

Is this because it's the same machine that I am both viewing the web page and hosting Sql server (ie, the user can only be used once)?

|||

Hi,

It's a little strange that it says you're using the Network Service to connect to SQL Server.

Are you connecting to the SQL Server through Internet with the windows authentication? If so, that's not supported, since the windows identity cannot be passed through internet.

|||

Kevin,

Everything including the database is on one machine. I'm using Windows authentication. So when I'm in Visual developer and connect

to the database, my web page (again hosted on the same machine) cannot connect to the database. It's a new installation of everything

with defaults setup. How can I work on the database while my web pages can still access the database? I just downloaded Managament

Studio Express, will this do?

Thanks for any help

|||

Hi,

Yes, you can use Management Studio to grant database access permission to the Network Service account.

By default, it does not have permission to the SQL Server. After granting the access, it will be working fine, I think.

sql

No Client Protocols Enabled yet I can still get a DSN connection to SQL Server 2005

Perplexed...Why am I able to get a connection to my SQL Server from an
Access 2003 database via DSN linked SQL server db table without a
common protocol between the client and server? Could it be that the
client does have TCP/IP or Named Pipes enabled but they are just not
showing up in the cliconfg.exe utility as such? Help!Clients have always TCP/IP and/or Named Pipes enabled. This setting is for
the server, not for the client tools.
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
"lacdn76" <dakarpiak@.yahoo.com> wrote in message
news:1175526801.931586.126790@.y66g2000hsf.googlegroups.com...
> Perplexed...Why am I able to get a connection to my SQL Server from an
> Access 2003 database via DSN linked SQL server db table without a
> common protocol between the client and server? Could it be that the
> client does have TCP/IP or Named Pipes enabled but they are just not
> showing up in the cliconfg.exe utility as such? Help!
>

No Client Protocols Enabled yet I can still get a DSN connection to SQL Server 2005

Perplexed...Why am I able to get a connection to my SQL Server from an
Access 2003 database via DSN linked SQL server db table without a
common protocol between the client and server? Could it be that the
client does have TCP/IP or Named Pipes enabled but they are just not
showing up in the cliconfg.exe utility as such? Help!
Clients have always TCP/IP and/or Named Pipes enabled. This setting is for
the server, not for the client tools.
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
"lacdn76" <dakarpiak@.yahoo.com> wrote in message
news:1175526801.931586.126790@.y66g2000hsf.googlegr oups.com...
> Perplexed...Why am I able to get a connection to my SQL Server from an
> Access 2003 database via DSN linked SQL server db table without a
> common protocol between the client and server? Could it be that the
> client does have TCP/IP or Named Pipes enabled but they are just not
> showing up in the cliconfg.exe utility as such? Help!
>

No .Fill method in Data Adapter

I am developing a Smart Device project for my Symbol MC9000 Windows Mobile
handheld. I am trying to make a simple connection to a SQL server. My proble
m
is my Data Adapter object does not have a .FILL method as it always has in
normal C# desktop apps.
I also noticed I cannot do a dataadapter object.dispose() either (i.e da.
Dispose(); )
Am I missing something or is this development environment for mobile just
that limited?
The intellisense only shows the following methods/properties for the da
object.
.DeleteCommand, .InsertCommand, .RowUpdated, .RowUpdating, .SelectCommand,
and .UpdateCommand.
That all it lists. Do I need to install something maybe?
I have never done a mobile app so this is all new to me.
Any help would be greatly appreciated.
Below is some of the code I am developing just to make the connection.
David
// Connection String for MSSQL Server
string Connection_String = "Initial Catalog=WINSTSDB;Data
Source=DB2ML350;workstation id=Symbol_MC9000w;packet size=4096;integrated
security=SSPI";
// Setup SQL Connection object
SqlConnection dbConn = new SqlConnection( Connection_String );
// Create Data Adapter object with SQL statement.
SqlDataAdapter da = new SqlDataAdapter("SELECT * FROM RackTemp WHERE SID =
'" + strSidcode + "'",dbConn);
// Define a Data Table object
System.Data.DataTable WinstisTable = new DataTable();
try
{
// Pull in data into data table object named WinstisTable
conn.Open();
da.Fill( WinstisTable );
}
catch(Exception exc)
{
MessageBox.Show(exc.Message.ToString(),"Error",MessageBoxButtons.OK,
MessageBoxIcon.Exclamation);
}
finally
{
// Close connection
conn.Close();
}
Message posted via http://www.webservertalk.comDavid C via webservertalk.com wrote:
> I am developing a Smart Device project for my Symbol MC9000 Windows
> Mobile handheld. I am trying to make a simple connection to a SQL
> server. My problem is my Data Adapter object does not have a .FILL
> method as it always has in normal C# desktop apps.
>
You might be better off posting this to a csharp or adonet newgroup. It's
somewhat offtopic here, and you are less likely to get a response than you
would in a relevant dotnet group (all the .Net groups have the word "dotnet"
in their names).
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.|||I guess because it is about SQL Connectivity that it might apply here. I wil
l
post on DotNetForums.com to see if some may help me.
David
Bob Barrows [MVP] wrote:
>You might be better off posting this to a csharp or adonet newgroup. It's
>somewhat offtopic here, and you are less likely to get a response than you
>would in a relevant dotnet group (all the .Net groups have the word "dotnet
"
>in their names).
Message posted via http://www.webservertalk.com

No "(local)" server name in servers list for SQL Server 2005

I have a new install of SQL SERVER 2005 on a new machine.
When I am using Visual Studio 2005 Server Explorer "Add connection" dialog
or MS Access ADE Connection "Data Link Properties", there is no (local)
entry in drop-down "server Name" list. However the actual server name is
listed and I can use it for successful connection.
My main problem is that I am trying to get from SourceSafe a big Access ADE
project and it complains that it is not able to connect to (local) server for
almost each form/report.
Is the "(local)" server removed in SQL SERVER 2005 by design or it is a
problem with my installation?
If it is a setup problem, how can I add (local) to the list of available
servers?
By the way,when I manually typed "(local)" server name, VS 2005 "add
connection" accepted it , but ADE Connection "Data Link Properties" reported
"Sql Server doesn't exist or access is denied"
Michael Freidgeim.
<a href="http://links.10026.com/?link=http://geekswithblogs.net/mnf/">
My Blog: http://geekswithblogs.net/mnf/
</a>
I was able to fix the problem. ADE Connection "Data Link Properties" accepts
manually typed "(local)" after I changed the following:
1. In SQL Server 2005 Configuration Manager selected "SQL server 2005
Network Configuration/Protocols for MSSQLSERVER" and enabled "Tcp/IP".
Note that "SQL Native Client Configuration/Client Configuration" had already
"Tcp/IP" enabled.
2. Restarted SQL Server service.
Michael Freidgeim.
<a href="http://links.10026.com/?link=http://geekswithblogs.net/mnf/">
My Blog: http://geekswithblogs.net/mnf/
</a>
"Michael Freidgeim" wrote:

> I have a new install of SQL SERVER 2005 on a new machine.
> When I am using Visual Studio 2005 Server Explorer "Add connection" dialog
> or MS Access ADE Connection "Data Link Properties", there is no (local)
> entry in drop-down "server Name" list. However the actual server name is
> listed and I can use it for successful connection.
> My main problem is that I am trying to get from SourceSafe a big Access ADE
> project and it complains that it is not able to connect to (local) server for
> almost each form/report.
> Is the "(local)" server removed in SQL SERVER 2005 by design or it is a
> problem with my installation?
> If it is a setup problem, how can I add (local) to the list of available
> servers?
> By the way,when I manually typed "(local)" server name, VS 2005 "add
> connection" accepted it , but ADE Connection "Data Link Properties" reported
> "Sql Server doesn't exist or access is denied"
> Michael Freidgeim.
> <a href="http://links.10026.com/?link=http://geekswithblogs.net/mnf/">
> My Blog: http://geekswithblogs.net/mnf/
> </a>

No "(local)" server name in servers list for SQL Server 2005

I have a new install of SQL SERVER 2005 on a new machine.
When I am using Visual Studio 2005 Server Explorer "Add connection" dialog
or MS Access ADE Connection "Data Link Properties", there is no (local)
entry in drop-down "server Name" list. However the actual server name is
listed and I can use it for successful connection.
My main problem is that I am trying to get from SourceSafe a big Access ADE
project and it complains that it is not able to connect to (local) server fo
r
almost each form/report.
Is the "(local)" server removed in SQL SERVER 2005 by design or it is a
problem with my installation?
If it is a setup problem, how can I add (local) to the list of available
servers?
By the way,when I manually typed "(local)" server name, VS 2005 "add
connection" accepted it , but ADE Connection "Data Link Properties" reporte
d
"Sql Server doesn't exist or access is denied"
Michael Freidgeim.
<a href="http://links.10026.com/?link=http://geekswithblogs.net/mnf/">
My Blog: http://geekswithblogs.net/mnf/
</a>I was able to fix the problem. ADE Connection "Data Link Properties" accept
s
manually typed "(local)" after I changed the following:
1. In SQL Server 2005 Configuration Manager selected "SQL server 2005
Network Configuration/Protocols for MSSQLSERVER" and enabled "Tcp/IP".
Note that "SQL Native Client Configuration/Client Configuration" had already
"Tcp/IP" enabled.
2. Restarted SQL Server service.
Michael Freidgeim.
<a href="http://links.10026.com/?link=http://geekswithblogs.net/mnf/">
My Blog: http://geekswithblogs.net/mnf/
</a>
"Michael Freidgeim" wrote:

> I have a new install of SQL SERVER 2005 on a new machine.
> When I am using Visual Studio 2005 Server Explorer "Add connection" dialog
> or MS Access ADE Connection "Data Link Properties", there is no (local)
> entry in drop-down "server Name" list. However the actual server name is
> listed and I can use it for successful connection.
> My main problem is that I am trying to get from SourceSafe a big Access AD
E
> project and it complains that it is not able to connect to (local) server
for
> almost each form/report.
> Is the "(local)" server removed in SQL SERVER 2005 by design or it is a
> problem with my installation?
> If it is a setup problem, how can I add (local) to the list of available
> servers?
> By the way,when I manually typed "(local)" server name, VS 2005 "add
> connection" accepted it , but ADE Connection "Data Link Properties" repor
ted
> "Sql Server doesn't exist or access is denied"
> Michael Freidgeim.
> <a href="http://links.10026.com/?link=http://geekswithblogs.net/mnf/">
> My Blog: http://geekswithblogs.net/mnf/
> </a>

Newbie: SQL Server connection, help needed

Needs some help, I recently recieved an evaluation copy of SQL Server2000
and I have installed it on a WindowsXPsp2 machine. I have updated to SQL
Server to
service pack3 and installed .net as well. I am still having connection
problems. I am
trying to setup an ODBC connection from another XP and win2000 machines.
Connection failed:
SQLState: '28000'
SQL Server Error 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
'rick'. Reason: Not associated with a trusted SQL Server connection.
I have already checked for Windows Authentication being enabled on the
server.
Of course the ODBC connection works locally.
'preciate any help
thanks
Hi
"Not associated with a trusted SQL Server connection" means that your
credentials passed do not match those with rights in the databases.
You need an NT Domain to use trusted security (except on the local machine).
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"rick" <rmsingh@.rogers.com> wrote in message
news:eHqmDTdEFHA.392@.TK2MSFTNGP14.phx.gbl...
> Needs some help, I recently recieved an evaluation copy of SQL Server2000
> and I have installed it on a WindowsXPsp2 machine. I have updated to SQL
> Server to
> service pack3 and installed .net as well. I am still having connection
> problems. I am
> trying to setup an ODBC connection from another XP and win2000 machines.
> Connection failed:
> SQLState: '28000'
> SQL Server Error 18452
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
> 'rick'. Reason: Not associated with a trusted SQL Server connection.
> I have already checked for Windows Authentication being enabled on the
> server.
> Of course the ODBC connection works locally.
> 'preciate any help
> thanks
>

Newbie: SQL Server connection, help needed

Needs some help, I recently recieved an evaluation copy of SQL Server2000
and I have installed it on a WindowsXPsp2 machine. I have updated to SQL
Server to
service pack3 and installed .net as well. I am still having connection
problems. I am
trying to setup an ODBC connection from another XP and win2000 machines.
Connection failed:
SQLState: '28000'
SQL Server Error 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user
'rick'. Reason: Not associated with a trusted SQL Server connection.
I have already checked for Windows Authentication being enabled on the
server.
Of course the ODBC connection works locally.
'preciate any help
thanksHi
"Not associated with a trusted SQL Server connection" means that your
credentials passed do not match those with rights in the databases.
You need an NT Domain to use trusted security (except on the local machine).
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"rick" <rmsingh@.rogers.com> wrote in message
news:eHqmDTdEFHA.392@.TK2MSFTNGP14.phx.gbl...
> Needs some help, I recently recieved an evaluation copy of SQL Server2000
> and I have installed it on a WindowsXPsp2 machine. I have updated to SQL
> Server to
> service pack3 and installed .net as well. I am still having connection
> problems. I am
> trying to setup an ODBC connection from another XP and win2000 machines.
> Connection failed:
> SQLState: '28000'
> SQL Server Error 18452
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed fo
r user
> 'rick'. Reason: Not associated with a trusted SQL Server connection.
> I have already checked for Windows Authentication being enabled on the
> server.
> Of course the ODBC connection works locally.
> 'preciate any help
> thanks
>