Not A Trusted Connection

I set up my SQLExpress server using Windows Authentication only. Now when I
try to create a user account using Username and Password, the connection
returns the error: Not a trusted connection. Does this have something to do
with my previous server setup or is there a general setting somewhere I need
to change?
Regards,
Fred Chateau
http://hotelmotelnow.com
Never mind... I found the setting.
Regards,
Fred Chateau
http://hotelmotelnow.com
"Fred Chateau" <webmaster@.hotelmotelnow.com> wrote in message
news:u323BNenHHA.588@.TK2MSFTNGP06.phx.gbl...
>I set up my SQLExpress server using Windows Authentication only. Now when I
>try to create a user account using Username and Password, the connection
>returns the error: Not a trusted connection. Does this have something to do
>with my previous server setup or is there a general setting somewhere I
>need to change?
> --
> Regards,
> Fred Chateau
> http://hotelmotelnow.com
>

Not A Trusted Connection

I set up my SQLExpress server using Windows Authentication only. Now when I
try to create a user account using Username and Password, the connection
returns the error: Not a trusted connection. Does this have something to do
with my previous server setup or is there a general setting somewhere I need
to change?
Regards,
Fred Chateau
http://hotelmotelnow.comNever mind... I found the setting.
Regards,
Fred Chateau
http://hotelmotelnow.com
"Fred Chateau" <webmaster@.hotelmotelnow.com> wrote in message
news:u323BNenHHA.588@.TK2MSFTNGP06.phx.gbl...
>I set up my SQLExpress server using Windows Authentication only. Now when I
>try to create a user account using Username and Password, the connection
>returns the error: Not a trusted connection. Does this have something to do
>with my previous server setup or is there a general setting somewhere I
>need to change?
> --
> Regards,
> Fred Chateau
> http://hotelmotelnow.com
>

not a trusted connection

I never had this problem between two WIN2k servers.
I have a new Win2003(XP) server with SQL 2000 and an old Win2k server
with SQL 7. I'm trying to run a query for data from a table on 7 joined
to a table on 2000 inserting into a table on 2000.
Regardless of which server hosts the query I get an error about user
'null' not being a trusted SQL server connection. Same error whether I
run the query in QAnalyser or DTS.
I have admin rights on both servers and both DBMs.
I DON'T have a domained network; windows networking. Since I've done
things between the 7 server and my dev server (W2k/SQL2000) I'm guessing
it's something to do with a stricter W2003 and seperate, but same
username, identities on each local machine.
Can anybody tell me what the next step is?
thx
md
*** Sent via Developersdex http://www.codecomments.com ***Not a lot of information on the error but I'm guess you are
using a linked server that is set up to use the current
users security context. And you are logging into SQL Server
using windows authentication.
It's not clear from which box you are initiating this from.
Even if it was initiated from SQL 2000, sounds like you
would still need to use a SQL login for the linked server.
-Sue
On Tue, 13 Sep 2005 14:58:37 -0700, M D <mardukes@.aol.com>
wrote:

>I never had this problem between two WIN2k servers.
>I have a new Win2003(XP) server with SQL 2000 and an old Win2k server
>with SQL 7. I'm trying to run a query for data from a table on 7 joined
>to a table on 2000 inserting into a table on 2000.
>Regardless of which server hosts the query I get an error about user
>'null' not being a trusted SQL server connection. Same error whether I
>run the query in QAnalyser or DTS.
>I have admin rights on both servers and both DBMs.
>I DON'T have a domained network; windows networking. Since I've done
>things between the 7 server and my dev server (W2k/SQL2000) I'm guessing
>it's something to do with a stricter W2003 and seperate, but same
>username, identities on each local machine.
>Can anybody tell me what the next step is?
>thx
>md
>*** Sent via Developersdex http://www.codecomments.com ***

noob to SSIS package configure and deploy

Hi there

I am fairly new to SSIS, I got my package running fine in my development environment with the connection managers (connecting to 3 databases on the same server, with username and password, not Integrated security) and all.

The problem comes in when i want to deploy my package or execute it outside of the development environment.

When I execute the .dtsx file in my project it brings up the Execute Package Utility and I just click Execute, thinking it should work, but not, any ideas?

So I read some of the forums and got looking into the configuration file, suppose that it does not carry the connection manager settings thru, but dam that still doesn't work for me?

The whole idea is that I will be executing the package from my C# code, so does my package have to be just on the server in a folder or does it have to be installed in the db? which is best?

Hope anyone can help me!!

Thanks
Jamie

If the error you are getting is a failure to connect to the database, the problem is in the password not being stored in the package. If you search the forum for connection strings and configurations, you'll see a number of different solutions to this.

If that's not the problem, please include the error message that you are receiving.

Nonstop datasource connection

Does anyone out there have any ideas on the best way to connect in integration services to a nonstop sql database running on a tandem computer? We have some odbc drivers that have proven to be problematic and slow to use. What oledb products I can find apparently come with something that's around $36K per processor to buy. Thanks.

Try the data access forum

https://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=87&SiteID=1

-Jamie

Non-Default SQL Server Port

Using Visual Studio .NET 2005 and I cannot make a database connection in sever explorer to a SQL server that listens on a non-default port. I can do this with VS .NET 2003, but not 2005. Please assist.Please help on this.|||

What is the version of the SQL Server?

Does the SQL Server and the connection application run on the same machine or on two different machines?

What protocols are enabled on the SQL Server?

What connection string does the application use?

Depending on your connection string you may need to start the SQL Browser service on the machine running SQL Server.

|||

SQL Server 2000
SQL Server 2000 and Visual Studio .NET 2005 are on seperate boxes.
SQL Server is listening on a non-default port (9696).
Just trying to connect to the database in server explorer.

NON DOMAIN AND DOMAIN CONNECTION

Hi all,

it happen to me a strange problem:

i have a mdb file (in Access 2K) with SQL Server 2K linked tables who
runs on a workstation which is on a different domain that the SQL
Server. It works.

If i create a mdb file from a workstation which is a the domain of the
SQL Server and then i run it a my non-domain workstation i have error
message:

Login failed for user '(null)'. Reason: Not associated with a trusted
SQL Server connection

But if i reattached my tables it works.

If someone have an idea...

PS: same ODBC on both machinesRavieR (principle@.caramail.com) writes:
> it happen to me a strange problem:
> i have a mdb file (in Access 2K) with SQL Server 2K linked tables who
> runs on a workstation which is on a different domain that the SQL
> Server. It works.
> If i create a mdb file from a workstation which is a the domain of the
> SQL Server and then i run it a my non-domain workstation i have error
> message:
> Login failed for user '(null)'. Reason: Not associated with a trusted
> SQL Server connection

I'm nor sure that I followed the confiuguration exactly, but trusted
connections in workgroups is usually an iffy thing. For instance, at
home I have a non-domain workstation, on which I run a non-domain
virtual machine where I have the beta version of SQL 2005. From the
host machine I cannot conenct with trusted connection to SQL2005 on
the virtual machine, but not the other way round.

I think you need to be logged with the same username on both, and the
two users need to have the same password.

You may be better off with SQL authentication in this case.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Non- Admin connection

I am testing an Access Database on network workstations with linked tables
to SQL Server. I set up a DSN and have no problem logged in as myself with
Admin rights to the server. But when I login as a user with no admin rights
I am denied access with this message:
Connection failed:
SQL Server State '28000'
SQL Server Error: 18456
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
'dayoubunc1\Sales'.
The network server is Windows 2003 Server, the workstation is Windows 2000
Pro and the SQL Server is a runtime version which came with a Veratis backup
system.
The purpose of moving the tables to SQL Server is security. A user can
steal an Access backend, so I don't want the user to have admin rights to
use the DB. What can I do.
Thanks and God Bless,
Mark A. Sam
Are you sure that it is related to admin rights? Maybe you just need to add a user named "Sales" to
the SQL Server permissions?
"Mark A. Sam" <msam@.Plan-It-Earth.Net> wrote in message
news:u2oqViHmFHA.3448@.TK2MSFTNGP12.phx.gbl...
>I am testing an Access Database on network workstations with linked tables
> to SQL Server. I set up a DSN and have no problem logged in as myself with
> Admin rights to the server. But when I login as a user with no admin rights
> I am denied access with this message:
> Connection failed:
> SQL Server State '28000'
> SQL Server Error: 18456
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
> 'dayoubunc1\Sales'.
>
> The network server is Windows 2003 Server, the workstation is Windows 2000
> Pro and the SQL Server is a runtime version which came with a Veratis backup
> system.
> The purpose of moving the tables to SQL Server is security. A user can
> steal an Access backend, so I don't want the user to have admin rights to
> use the DB. What can I do.
> Thanks and God Bless,
> Mark A. Sam
>
|||Hello Scot,
I don't know how I would do that. I opened Enterprise manager and tried to
add a new user but the Network users weren't available. I am very
inexperienced with SQL Server, but I think I recall from another client db
that the users network users were listed. And thinking about they, they had
many users who only had to log in and the DB worked, even through terminal
service sessions. It seems as though I only set up the DSNs on those
workstations.
God Bless,
Mark
|||I tried adding full Control to the user for the SQL Server Folder as well as
the database folder, but it didn't get me any further. Authenticated Users
also have access to the SQL Folder.
Could it me that it is a Run Time Version (that is what I was told) of SQL
Server? Does the client need to purchase the full version?

Non- Admin connection

I am testing an Access Database on network workstations with linked tables
to SQL Server. I set up a DSN and have no problem logged in as myself with
Admin rights to the server. But when I login as a user with no admin rights
I am denied access with this message:
Connection failed:
SQL Server State '28000'
SQL Server Error: 18456
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user
'dayoubunc1\Sales'.
The network server is Windows 2003 Server, the workstation is Windows 2000
Pro and the SQL Server is a runtime version which came with a Veratis backup
system.
The purpose of moving the tables to SQL Server is security. A user can
steal an Access backend, so I don't want the user to have admin rights to
use the DB. What can I do.
Thanks and God Bless,
Mark A. SamAre you sure that it is related to admin rights? Maybe you just need to add
a user named "Sales" to
the SQL Server permissions?
"Mark A. Sam" <msam@.Plan-It-Earth.Net> wrote in message
news:u2oqViHmFHA.3448@.TK2MSFTNGP12.phx.gbl...
>I am testing an Access Database on network workstations with linked tables
> to SQL Server. I set up a DSN and have no problem logged in as myself with
> Admin rights to the server. But when I login as a user with no admin righ
ts
> I am denied access with this message:
> Connection failed:
> SQL Server State '28000'
> SQL Server Error: 18456
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed fo
r user
> 'dayoubunc1\Sales'.
>
> The network server is Windows 2003 Server, the workstation is Windows 2000
> Pro and the SQL Server is a runtime version which came with a Veratis back
up
> system.
> The purpose of moving the tables to SQL Server is security. A user can
> steal an Access backend, so I don't want the user to have admin rights to
> use the DB. What can I do.
> Thanks and God Bless,
> Mark A. Sam
>|||Hello Scot,
I don't know how I would do that. I opened Enterprise manager and tried to
add a new user but the Network users weren't available. I am very
inexperienced with SQL Server, but I think I recall from another client db
that the users network users were listed. And thinking about they, they had
many users who only had to log in and the DB worked, even through terminal
service sessions. It seems as though I only set up the DSNs on those
workstations.
God Bless,
Mark|||I tried adding full Control to the user for the SQL Server Folder as well as
the database folder, but it didn't get me any further. Authenticated Users
also have access to the SQL Folder.
Could it me that it is a Run Time Version (that is what I was told) of SQL
Server? Does the client need to purchase the full version?

NOD32 - SQL 2000 connection error - DNS?

Well its always developer vs administrators, and for the life of me why wont they listen...? However now I must and hopefully someone can help. My need for this resolve is not to change the software which works, but to enlighten the administrators as to possible NOD32 conflicts, or perhaps another issue which I've missed.

In the following scenario I am stumped, and have never heard of anything like it.

The server (DNS (win2003) & sql 2000 sp3) has NOD32 enterprise running, my apps have been running on this environment for the last 3 years, however, for the last year and since NOD32 has been installed, a few very strange incidents have occurred.

1. Whenever this error occurs, users fail to connect to SQL server, the server connection string has to be altered from either server name to the server IP or vice versa. This is an intermittent occurance and can be anything from a few days to a few weeks between occurances.

To limit connectivity issues to a particular protocol, SQL only uses tcp/ip on port 1433. LMhost dont resolve any of these issues either.

2. Twice since the NOD32 installation (I do hope I am not blaming them unneccessarily) SQL communications has degraded over a period of time till a complete halt, (By degraded I mean point 1 above becomes more and more repetitive).

What I found is that when local network users no longer function, my terminal services users were still operational, the local network users could'nt comunicate via native drivers or odbc. In other words the drivers were functional in local only environment. The data server resides behind the linux firewall hence no port blocking is setup of the data sever.

My solution was to reinstall sp3, however does not explain the above errors,

If I am missing something, pray do tell, customer blames administrator, administrator blames me, I gotta blame someone or offer a solution cos hell knows no administrator is ever at fault.

In advance, excuse the digs if you're an administrator and many thanks

GDR...stumped!

There are many reports that some antivirus softwares are not compatible with sqlservr.exe. To prove this theory, can you try the following and log the result when your server is operational and malfunctioning. One of

(1) "ping servername" "ping serveripaddress", "ping -a sereripaddress",

(2) "telnet servername/serveripaddress 1433".

If any of above does not work, or the ipaddress is changed over the course, you should find if disable/uninstall NOD32 would help solve your problem.

|||It looks like Nod32 limits the number of concurrent tcp connections. searth "Nod32 limit connection" you can find some hint. It's strange that changing the server name to IP address (vice versa) can solve the problem for a period.
What's the SQL error msg when you see the problem? When you see the problem, do all users from any machine on local network fail, or just fail on the server?|||

TCP/IP is still intact on the server, all ping or telnet responses are ok, it seems as if it is down to the drivers operating (somehow...) in a local mode when the problem presents itself.

The only problem with disabling the antivirus, as we know, users will infect the systems even be it inadvertantly. Another consideration is, I now have to wait till the next connection failure, and since the service pack has just been applied a week ago, I do not know when the next failure is going to be, so how long do we keep the antivirus off-line.

I have read an article on another resource that when installing NOD32 Ver2, the application binds to port1433, so I am checking logs for when the anti-virus updates (not the virus files but the application), perhaps there in lies a problem, there is a registry fix for this problem however when checking the reg, all is in line with the fix.

Thanks for the reply, but still in a bind....

|||

Hi, I thought you were on to something there, then I remembered, there is also a .net app using remoting, the server side components handle all sql connections and route information/data/results etc back to the calling client, I wont go too far into that, but what this means is it is not a tcp connection limit as this application still functions, also is the fact that this app uses native drivers like my app does.

Getting back to my strange theory that it is as if the drivers are operational but local only. Also to support this, remember that the terminal server users remain operational, although only after ammending the server name to ip or vice versa.

I know I have mentioned this before, but when all the users could no longer connect, from a local network machine, I tried odbc directly and all to no avail, the only thing I did'nt try was to place the application components into a COM+ environment. Yet again this will only be a work around for an issue that has not been resolved.

|||

Were you be able to run my recommended ping and telnet from any of your client machine when your client failed to connect to the sqlserver? Your post give me impression that you did not have chance so far yet. Also if you could share out the error message when your client start to fail, it will be of great help too.

Since both teminal server user and sqlserver user need to switch the server name to IP or vice versa in order to connect properly, I don't think sql server is the culprit. You might find fast solution by followup with your system admin and the NOD32 on this issue.

|||

The ping and telnet test were carried out before I had SP3 reinstalled (tests done by admin), In terms of the SQL error, its the standard connection error : [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

As for NOD32 help with this, I have accessed their Forums and have found only one solution, uninstall NOD32, this according to my clients administrator is not an option. Unfortunately, the admin is of the mindset it can only be my app, although it worked fine and works fine on several other networks (all before admins existence at said problematic company.) If no solution is possible I will withdraw my software. The admin is also of the mind set that I should write a tcp databroker to work around this problem, yet again a work around and in this case to save the admin... as we all know a rewrite is not always possible when it comes down to application size etc etc etc.

Besides a VB6/.Net remoting hybrid would be simpler to write than trying to implement and reinvent the wheel when it comes to socket security, data encryption etc.

Thanks for the reply none the less....Still Stumped...

GDR

|||

Since you are getting, [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied, and you are using TCP with default 1433 port, I would expect the winsock connect "(Connect()).]" to the server was failing. I am confused how "telnet servername 1433" could work. To uncover why your app is failing, you might want to experiment with ETW tracing, http://blogs.msdn.com/sql_protocols/archive/2006/08/04/688396.aspx. You can experiment it out. You need to use MDAC2.8 and add {BD568F20-FCCD-B948-054E-DB3421115D61} 0x00000000 0 DBNETLIB.1 in your ctrl.guid file.

|||

Many thanks however, perhaps we should simplify before we start stripping whats working,

1. Occasional connection errors occur, swop name and IP and OK again.

2. After prolonged connection errors, eventually all network comms fail, but not on the local machine, terminal server users still get to function, however may have to swop ip and name in app connection settings.

when point 2 has occured even ODBC fails to connect to server from network client, although c# remoting app on network client functions, this I can attribute to the connection taking place by the component on the server environment and that making the actual connection, which suggests tcp to be in working order else neither terminal services or remoting objects would function.

Somehow I keep coming back to driver/port external influence on these as too many other processes that rely on tcp remain functioning. I have installed (as a test) sql redis on some clients to ensure latest sql client connectivity tools, also SP4 on server.

Dont know what else to say except thanx for the input, I will be looking at the ETW trace and reply if results are favourable.

Thanx again.

|||

Many thanks all for your input, the problem has'nt shown itself in the last few weeks however, now that this post has gone out its probably due to occur shortly...(murphy's law). If the problem arises again I will start resume with this thread.

I dont know if it was the service packs that resolved the issue, but all is quiet on the western front.

No trusted SQl connection

Hello,
I am using the MSDE from Visual Studio.NET. I can access the SQL Server from
the server explorer only if I am logged into 2000 as administrator (I
installed MSDE using admin). If I try to connect from another login on the
same machine, I get the following error "Login failed. Not associated with a
trusted SQL Server connection". Any ideas?
Thanks,
Rick
hi Rick,
"rick_md" <rick_mc_806@.msn.com> ha scritto nel messaggio
news:CrqdnTC2aJqMiPLcRVn-qA@.comcast.com
> Hello,
> I am using the MSDE from Visual Studio.NET. I can access the SQL
> Server from the server explorer only if I am logged into 2000 as
> administrator (I installed MSDE using admin). If I try to connect
> from another login on the same machine, I get the following error
> "Login failed. Not associated with a trusted SQL Server connection".
> Any ideas?
that means that your non admin Windows account is not a regitered and
authorizated login to access SQL Server...
you have to log in as administrator and grant all non admin Windows account
privilege to access SQL Server
have a look at
http://support.microsoft.com/default...N-US;q325003#8
a good article about security you should read can be found at
http://support.microsoft.com/default...b;en-us;325022
we are here referring to Windows authentication...
if you like to log in in your MSDE instance using SQL Server authentication,
providing "User" and "pasword" credential, you have to modify the
authentication mode to Mixed mode..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

no trust connection

hi every one
i having i workstation with running in windows 98, now i want link it to the SQL server which are in windows 2000. when i try to link it the following error message " no associate trust SQL Server Connection". Can i know how to settle this problem
thanks in advanceare you trying to connect to the server using windows integrated
authentication? If so, make sure you're logged on to the domain in your
workstation before trying to connect to sql server. You might want to try to
connect using standard authentication (i.e using sa or another login) just
to verify you can connect to the server successfully. If this doesn't work,
make sure you can get to the server through tcp port 1433 (sql server port);
this can be tested using the following command:
telnet servername 1433
--
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 Programming by Example
"how" <how_world@.hotmail.com> wrote in message
news:7A83A2A1-FE31-4439-B87D-2D50FE705A30@.microsoft.com...
> hi every one
> i having i workstation with running in windows 98, now i want link it to
the SQL server which are in windows 2000. when i try to link it the
following error message " no associate trust SQL Server Connection". Can i
know how to settle this problem
> thanks in advance
>|||Hi,
Windows 98 will only support SQL server Authentication.
So while linking from SQL 2000, use SQL server Login credentials.
Thanks
Hari
MCDBA
"how" <how_world@.hotmail.com> wrote in message
news:7A83A2A1-FE31-4439-B87D-2D50FE705A30@.microsoft.com...
> hi every one
> i having i workstation with running in windows 98, now i want link it to
the SQL server which are in windows 2000. when i try to link it the
following error message " no associate trust SQL Server Connection". Can i
know how to settle this problem
> thanks in advance
>|||when i using window intergrate authentication that can sucess link to the SQL server, but when i using the SQL authentication it fail at the end so what should i do now.
how to open the port 1433 '
thanks in advance|||is there a firewall between the client and the server? If they are in the
same network you don't have to open ports or anything.
--
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 Programming by Example
"how" <anonymous@.discussions.microsoft.com> wrote in message
news:D6026E6E-7EE4-4739-A280-9EA3BAD30032@.microsoft.com...
> when i using window intergrate authentication that can sucess link to the
SQL server, but when i using the SQL authentication it fail at the end so
what should i do now.
> how to open the port 1433 '?
> thanks in advance|||what error are you getting?
--
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 Programming by Example
"how" <anonymous@.discussions.microsoft.com> wrote in message
news:1256EDE4-FAA1-4A10-BF29-AAD182FBC94A@.microsoft.com...
> that r not any firewall install in that server, i just format and
reinstall the window for that server. so waht action i can take
> thanks in advance|||are you saying you get this error when trying to connect to sql server using
STANDARD authentication? It's weird, that error shows up when you can't
connect to sql but using integrated authentication.
--
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 Programming by Example
"how" <anonymous@.discussions.microsoft.com> wrote in message
news:85BAB5CE-BD59-4559-A7E1-1ED4A36596BE@.microsoft.com...
> it also show "no associate trust SQL Server Connection"

no trust connection

hi every one
i having i workstation with running in windows 98, now i want link it to the
SQL server which are in windows 2000. when i try to link it the following e
rror message " no associate trust SQL Server Connection". Can i know how to
settle this problem
thanks in advanceare you trying to connect to the server using windows integrated
authentication? If so, make sure you're logged on to the domain in your
workstation before trying to connect to sql server. You might want to try to
connect using standard authentication (i.e using sa or another login) just
to verify you can connect to the server successfully. If this doesn't work,
make sure you can get to the server through tcp port 1433 (sql server port);
this can be tested using the following command:
telnet servername 1433
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 programming by Example
"how" <how_world@.hotmail.com> wrote in message
news:7A83A2A1-FE31-4439-B87D-2D50FE705A30@.microsoft.com...

quote:

---

> hi every one
> i having i workstation with running in windows 98, now i want link it to

---

the SQL server which are in windows 2000. when i try to link it the
following error message " no associate trust SQL Server Connection". Can i
know how to settle this problem

quote:

---

> thanks in advance
>

---

|||Hi,
Windows 98 will only support SQL server Authentication.
So while linking from SQL 2000, use SQL server Login credentials.
Thanks
Hari
MCDBA
"how" <how_world@.hotmail.com> wrote in message
news:7A83A2A1-FE31-4439-B87D-2D50FE705A30@.microsoft.com...

quote:

---

> hi every one
> i having i workstation with running in windows 98, now i want link it to

---

the SQL server which are in windows 2000. when i try to link it the
following error message " no associate trust SQL Server Connection". Can i
know how to settle this problem

quote:

---

> thanks in advance
>

---

|||when i using window intergrate authentication that can sucess link to the SQ
L server, but when i using the SQL authentication it fail at the end so what
should i do now.
how to open the port 1433 '?
thanks in advance|||is there a firewall between the client and the server? If they are in the
same network you don't have to open ports or anything.
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 programming by Example
"how" <anonymous@.discussions.microsoft.com> wrote in message
news:D6026E6E-7EE4-4739-A280-9EA3BAD30032@.microsoft.com...

quote:

---

> when i using window intergrate authentication that can sucess link to the

---

SQL server, but when i using the SQL authentication it fail at the end so
what should i do now.

quote:

---

> how to open the port 1433 '?
> thanks in advance

---

|||that r not any firewall install in that server, i just format and reinstall
the window for that server. so waht action i can take
thanks in advance|||what error are you getting?
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 programming by Example
"how" <anonymous@.discussions.microsoft.com> wrote in message
news:1256EDE4-FAA1-4A10-BF29-AAD182FBC94A@.microsoft.com...

quote:

---

> that r not any firewall install in that server, i just format and

---

reinstall the window for that server. so waht action i can take

quote:

---

> thanks in advance

---

|||it also show "no associate trust SQL Server Connection"|||are you saying you get this error when trying to connect to sql server using
STANDARD authentication? It's weird, that error shows up when you can't
connect to sql but using integrated authentication.
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 programming by Example
"how" <anonymous@.discussions.microsoft.com> wrote in message
news:85BAB5CE-BD59-4559-A7E1-1ED4A36596BE@.microsoft.com...

quote:

---

> it also show "no associate trust SQL Server Connection"

---

No sqlclient database, how to run script to create?

After installed SQL Server 2005 with Management Studio, I found that there i
s
no any local server. So when the studio opened, no any server connection and
no any sqlclient database in local machine. May I run some script to create
the local server and sqlclient databse, if yes, where is the script, and how
to run? Else, have to re-install SQL Server 2005, and what install option is
missed?
Thanks.Hello,
Just go to SQL Server setup program and choose Database Services and
continue the install.
Before doing this go see the SQL server and see the DATA and LOG folder is
created. If yes open the latest Errorlog file from Log folder and
see Server name and try registering using that in management studio.
Thanks
Hari
"FD" <FD@.discussions.microsoft.com> wrote in message
news:421B3416-1AE9-4AFF-A853-6BCC8A04A797@.microsoft.com...
> After installed SQL Server 2005 with Management Studio, I found that there
> is
> no any local server. So when the studio opened, no any server connection
> and
> no any sqlclient database in local machine. May I run some script to
> create
> the local server and sqlclient databse, if yes, where is the script, and
> how
> to run? Else, have to re-install SQL Server 2005, and what install option
> is
> missed?
> Thanks.

No sqlclient database, how to run script to create?

After installed SQL Server 2005 with Management Studio, I found that there is
no any local server. So when the studio opened, no any server connection and
no any sqlclient database in local machine. May I run some script to create
the local server and sqlclient databse, if yes, where is the script, and how
to run? Else, have to re-install SQL Server 2005, and what install option is
missed?
Thanks.
Hello,
Just go to SQL Server setup program and choose Database Services and
continue the install.
Before doing this go see the SQL server and see the DATA and LOG folder is
created. If yes open the latest Errorlog file from Log folder and
see Server name and try registering using that in management studio.
Thanks
Hari
"FD" <FD@.discussions.microsoft.com> wrote in message
news:421B3416-1AE9-4AFF-A853-6BCC8A04A797@.microsoft.com...
> After installed SQL Server 2005 with Management Studio, I found that there
> is
> no any local server. So when the studio opened, no any server connection
> and
> no any sqlclient database in local machine. May I run some script to
> create
> the local server and sqlclient databse, if yes, where is the script, and
> how
> to run? Else, have to re-install SQL Server 2005, and what install option
> is
> missed?
> Thanks.