Cannot Register Sql Server Database

We have SQL Server installed on a Windows 2000 server machine. I have a cop
y of Sql Server Personal Addition - Client tools on my computer. When I ope
n the SQL Server Enterprise manager and try perform an New SQL Server Regist
ration, I get the following
error: Login Failed for user '(null)'. Reason: Not associated with a truste
d SQL Server Connection. I am using windows authentication.
I am able to connect to other sql server databases on other servers.
I also cannot connect to the server via ODBC. I get the error: Unable to lo
cate database server. Verify that the database server name you entered is c
orrect.
I am running microsoft XP / Microsoft SQL Server 2000 service pack 3a is on
the server.Hi,
Are you using Domain user id to login to your machine, if yes then check the
SQL server that you have given access to sql server.
How to check.
In Enterprise Manager, Security option, Check wheather ur login is there
with reqired previlages.
Thanks
Hari
MCDBA
"Allan Latts" <alatts@.yaoo.com> wrote in message
news:B571755C-B3AA-4ED1-94D9-FE11B0B8EE3E@.microsoft.com...
> We have SQL Server installed on a Windows 2000 server machine. I have a
copy of Sql Server Personal Addition - Client tools on my computer. When I
open the SQL Server Enterprise manager and try perform an New SQL Server
Registration, I get the following error: Login Failed for user '(null)'.
Reason: Not associated with a trusted SQL Server Connection. I am using
windows authentication.
> I am able to connect to other sql server databases on other servers.
> I also cannot connect to the server via ODBC. I get the error: Unable to
locate database server. Verify that the database server name you entered is
correct.
> I am running microsoft XP / Microsoft SQL Server 2000 service pack 3a is
on the server.

Cannot Re-attach SQL Server

I was attempting to use the Copy Database Wizard, and halfway through
the connection was broken. The database was unattached by the wizard,
and now when I try and reattach it I keep getting Error 5105 about the
path to the ndf file being incorrect. It is correct, I even pasted it
into Explorer but SQL just cannot find it. Any ideas?
Thanks.Hi
You do not say how you are attaching this, but try using sp_attach_db in
Query analyser if you are using Enterprise Manager to do this.
John
"cbsd.james" wrote:

> I was attempting to use the Copy Database Wizard, and halfway through
> the connection was broken. The database was unattached by the wizard,
> and now when I try and reattach it I keep getting Error 5105 about the
> path to the ndf file being incorrect. It is correct, I even pasted it
> into Explorer but SQL just cannot find it. Any ideas?
> Thanks.
>

Cannot Re-attach SQL Server

I was attempting to use the Copy Database Wizard, and halfway through
the connection was broken. The database was unattached by the wizard,
and now when I try and reattach it I keep getting Error 5105 about the
path to the ndf file being incorrect. It is correct, I even pasted it
into Explorer but SQL just cannot find it. Any ideas?
Thanks.Hi
You do not say how you are attaching this, but try using sp_attach_db in
Query analyser if you are using Enterprise Manager to do this.
John
"cbsd.james" wrote:
> I was attempting to use the Copy Database Wizard, and halfway through
> the connection was broken. The database was unattached by the wizard,
> and now when I try and reattach it I keep getting Error 5105 about the
> path to the ndf file being incorrect. It is correct, I even pasted it
> into Explorer but SQL just cannot find it. Any ideas?
> Thanks.
>sql

Cannot Open User Default Database. Login Failed

Yesterday was not my best day. I disconnected my database to make a copy of it and forgot to reconnect it before closing SQL Server 2000.

Now when I try ot access the database I get message.

Cannot Open User Default Database. Login Failed

Is there a way to attach the database again or a work around for this?

Thanks in advance for your help!You should be able to get an admin to change your default database to pubs, or northwind. Then you would be able to log on, anyway. I am not sure if you would be able to re-attach the database without an admin, though.|||Use the osql.exe utility to run sp_defaultdb and change the default database.sql

Cannot install Microsoft SQL Server 2005 Express Edition x86

I recently (yesterday) installed a fresh copy of Windows XP with Service Pack 2 applied.

I proceeded with Visual Studio 2005 Express Editions installation straight away.

But I cannot install Microsoft SQL Server 2005 Express Edition x86.

I choose to install Microsoft SQL Server 2005 Express Edition x86 component along with every component of visual studio but it simply would not install.

In the end, after the installation of each complete is complete, I simply get an error message saying that Microsoft SQL Server 2005 Express Edition x86 failed to install.

What is the problem?

First take a look at the following file: %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\log\summary.txt. This should point you to which component failed and the specific log file for the component. When you open the component log file search for "Value 3" (this is a Windows Installer code for the error section). Take a look at +/- 10 lines for the error.

If the summary.txt file doesn't provide any clues, take a look at: %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\log\files\*_core(local).txt - open the most recent one if there are multiple. Go to the end of the file and you should find some clues as to why the installation failed.

|||

I looked. There were three errors and all of them said that installation cannot be done to a compressed drive

--

Error : SQL Server Setup cannot install files to the compressed or encrypted folder: C:\Program Files\Microsoft SQL Server\. To continue, make sure that your installation directories are not compressed or encrypted, or specify a different directory, and then run SQL Server Setup again.

--

I'll remove drive compression and try again.

Thanks for help!

|||

I am having the same problem - cannot install SQL Server Express, I looked in the file you mentioned to the other fellow and it says:

D43QNW81 : SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.

but I HAVE removed all components except a thing called Enterprise Library June 2005, and thaat one will not un-install without dot net framework 1.1

is that it? do I have to go ALL the way back?

any help will be much appreciated, I installed the whole works in a Virutal machine and now I am trying to install it on my base machine (because the Virtual one is too slow)

|||

David,

You can take a look at the latest *_core(local).log file to see which old component it's detecting. The log files can be found here: %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\log\files

If you email me directly at dtjones@.microsoft.com I can send you a clean up script. The script isn't supported but we've had good luck with it.

Cheers,
Dan

cannot insert data from one table to another

Hello:
All I want to do is simply copy a column of data from one table to another.
The first time I tried it, I got that blame "cannot insert duplicate primary
KEY constraint" business or whatever. So, I decided to create a duplicate
table (backup table). I did that sucessfully. The point is that I created
a
backup table of the table that I want to copy into so that I could get aroun
d
this error.
I got around that error. But, now, when I try to copy the column from a
table into this backup table, I get a message saying that it cannot insert
the value "NULL" into some other column in the table that I do not care abou
t
anyway.
Is there any way to get around these errors? I just want to copy data from
one column for goodness sakes!!!
Thanks!
childofthe1980sThere is no way for anyone to help unless you provide quite a bit more
information. The error messages are symptoms, but to understand them
required the entire picture.
So, show the table structures (including those pesky keys), and show
what the data looks like, and describe more precisely what you are
trying to accomplish. Before and after views of the data help a lot.
Roy
On Sun, 26 Feb 2006 10:18:26 -0800, "childothe1980s"
<childothe1980s@.discussions.microsoft.com> wrote:

>Hello:
>All I want to do is simply copy a column of data from one table to another.
>The first time I tried it, I got that blame "cannot insert duplicate primar
y
>KEY constraint" business or whatever. So, I decided to create a duplicate
>table (backup table). I did that sucessfully. The point is that I created
a
>backup table of the table that I want to copy into so that I could get arou
nd
>this error.
>I got around that error. But, now, when I try to copy the column from a
>table into this backup table, I get a message saying that it cannot insert
>the value "NULL" into some other column in the table that I do not care abo
ut
>anyway.
>Is there any way to get around these errors? I just want to copy data from
>one column for goodness sakes!!!
>Thanks!
>childofthe1980s|||"childothe1980s" <childothe1980s@.discussions.microsoft.com> wrote in message
news:3C895F9B-8A38-4991-AD42-9B43F5EDFCB8@.microsoft.com...
> Hello:
> All I want to do is simply copy a column of data from one table to
> another.
> The first time I tried it, I got that blame "cannot insert duplicate
> primary
> KEY constraint" business or whatever. So, I decided to create a duplicate
> table (backup table). I did that sucessfully. The point is that I
> created a
> backup table of the table that I want to copy into so that I could get
> around
> this error.
> I got around that error. But, now, when I try to copy the column from a
> table into this backup table, I get a message saying that it cannot insert
> the value "NULL" into some other column in the table that I do not care
> about
> anyway.
> Is there any way to get around these errors? I just want to copy data
> from
> one column for goodness sakes!!!
> Thanks!
> childofthe1980s
DDL and sample data please if you expect a full working solution. See:
http://www.aspfaq.com/etiquette.asp?id=5006
In your INSERT you have to supply a value for the non-nullable columns that
don't have defaults.
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--

Cannot get write permissions to a folder

I have a server ser1 which has the sql server running under the
security context of the local admin.Whn i try to copy the backup files
from this server to a network share it acnnot access the share unless
the sever has all authenticated user write permisssions.On setting the
auditing on we found that ser1$ uis the account which is trying to
write to the share.My question is as follows:- what is the difference
between the domaonname\ser1 and domainname\ser1$ account.I cannot see
this ser1$ account in the domain so I caaanot give it permissions.Is
there a way I could get to this account and give it permissions to
tighter up the security?
Thanks in anticipation.
AjayI'm not a network adminstrator, but I tried the same thing before and it
doesn't work. If you want SQL to have access to network resources it has to
run under a domain account. Then you can grant permissions to that account
on the network share you are trying to access. You will either need to setup
sql server to run under a domain account or have sql server write the backup
locally and schedule a job that can run with domain credentials to copy the
backup to the network share.
Mark
"Ag" <ajaygarg1962@.gmail.com> wrote in message
news:1154617829.443666.306270@.i42g2000cwa.googlegroups.com...
>I have a server ser1 which has the sql server running under the
> security context of the local admin.Whn i try to copy the backup files
> from this server to a network share it acnnot access the share unless
> the sever has all authenticated user write permisssions.On setting the
> auditing on we found that ser1$ uis the account which is trying to
> write to the share.My question is as follows:- what is the difference
> between the domaonname\ser1 and domainname\ser1$ account.I cannot see
> this ser1$ account in the domain so I caaanot give it permissions.Is
> there a way I could get to this account and give it permissions to
> tighter up the security?
> Thanks in anticipation.
>
> Ajay
>|||Mark Miller wrote:
> I'm not a network adminstrator, but I tried the same thing before and it
> doesn't work. If you want SQL to have access to network resources it has to
> run under a domain account. Then you can grant permissions to that account
> on the network share you are trying to access. You will either need to setup
> sql server to run under a domain account or have sql server write the backup
> locally and schedule a job that can run with domain credentials to copy the
> backup to the network share.
> Mark
> "Ag" <ajaygarg1962@.gmail.com> wrote in message
> news:1154617829.443666.306270@.i42g2000cwa.googlegroups.com...
> >I have a server ser1 which has the sql server running under the
> > security context of the local admin.Whn i try to copy the backup files
> > from this server to a network share it acnnot access the share unless
> > the sever has all authenticated user write permisssions.On setting the
> > auditing on we found that ser1$ uis the account which is trying to
> > write to the share.My question is as follows:- what is the difference
> > between the domaonname\ser1 and domainname\ser1$ account.I cannot see
> > this ser1$ account in the domain so I caaanot give it permissions.Is
> > there a way I could get to this account and give it permissions to
> > tighter up the security?
> >
> > Thanks in anticipation.
> >
> >
> > Ajay
Thanks Mark for the response:-
Here is what I notices and I was able to resolve the issue:-
ser1$ is the computername account which is trying to acces a directory
whenever the sql server uses a local admin account.We can resolve this
in three ways:-
1.Give the network share permissions for the the
domainname/computername account in this case domainname/compuetname$ .
2.Change sql servr to use a domain account means chaning the apps to
use the domain acocunt a non starteer in my enviormment as the apps are
owned by the vendors.
3.Use a proxy account for the sql server agent so that even if sql runs
on a local admin account the proxy account would enable the agent to
use a doain account.
Thanks for your response.
Ajay
> >|||Ag wrote:
> Mark Miller wrote:
>> I'm not a network adminstrator, but I tried the same thing before and it
>> doesn't work. If you want SQL to have access to network resources it has to
>> run under a domain account. Then you can grant permissions to that account
>> on the network share you are trying to access. You will either need to setup
>> sql server to run under a domain account or have sql server write the backup
>> locally and schedule a job that can run with domain credentials to copy the
>> backup to the network share.
>> Mark
>> "Ag" <ajaygarg1962@.gmail.com> wrote in message
>> news:1154617829.443666.306270@.i42g2000cwa.googlegroups.com...
>> I have a server ser1 which has the sql server running under the
>> security context of the local admin.Whn i try to copy the backup files
>> from this server to a network share it acnnot access the share unless
>> the sever has all authenticated user write permisssions.On setting the
>> auditing on we found that ser1$ uis the account which is trying to
>> write to the share.My question is as follows:- what is the difference
>> between the domaonname\ser1 and domainname\ser1$ account.I cannot see
>> this ser1$ account in the domain so I caaanot give it permissions.Is
>> there a way I could get to this account and give it permissions to
>> tighter up the security?
>> Thanks in anticipation.
>>
>> Ajay
> Thanks Mark for the response:-
> Here is what I notices and I was able to resolve the issue:-
> ser1$ is the computername account which is trying to acces a directory
> whenever the sql server uses a local admin account.We can resolve this
> in three ways:-
> 1.Give the network share permissions for the the
> domainname/computername account in this case domainname/compuetname$ .
> 2.Change sql servr to use a domain account means chaning the apps to
> use the domain acocunt a non starteer in my enviormment as the apps are
> owned by the vendors.
This is just plain wrong. Changing the account that the SQL Server and
SQL Agent services run under has absolutely nothing to do with the
logins use by applications to connect to SQL databases. If you want to
access network resources from within SQL, this is how you do it. Change
the MSSQLSERVER and SQLSERVERAGENT services to run as a domain user, and
grant share permissions to that domain user.
> 3.Use a proxy account for the sql server agent so that even if sql runs
> on a local admin account the proxy account would enable the agent to
> use a doain account.
> Thanks for your response.
>
> Ajay
>
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy McKibben wrote:
> Ag wrote:
> > Mark Miller wrote:
> >> I'm not a network adminstrator, but I tried the same thing before and it
> >> doesn't work. If you want SQL to have access to network resources it has to
> >> run under a domain account. Then you can grant permissions to that account
> >> on the network share you are trying to access. You will either need to setup
> >> sql server to run under a domain account or have sql server write the backup
> >> locally and schedule a job that can run with domain credentials to copy the
> >> backup to the network share.
> >>
> >> Mark
> >>
> >> "Ag" <ajaygarg1962@.gmail.com> wrote in message
> >> news:1154617829.443666.306270@.i42g2000cwa.googlegroups.com...
> >> I have a server ser1 which has the sql server running under the
> >> security context of the local admin.Whn i try to copy the backup files
> >> from this server to a network share it acnnot access the share unless
> >> the sever has all authenticated user write permisssions.On setting the
> >> auditing on we found that ser1$ uis the account which is trying to
> >> write to the share.My question is as follows:- what is the difference
> >> between the domaonname\ser1 and domainname\ser1$ account.I cannot see
> >> this ser1$ account in the domain so I caaanot give it permissions.Is
> >> there a way I could get to this account and give it permissions to
> >> tighter up the security?
> >>
> >> Thanks in anticipation.
> >>
> >>
> >> Ajay
> >
> > Thanks Mark for the response:-
> >
> > Here is what I notices and I was able to resolve the issue:-
> >
> > ser1$ is the computername account which is trying to acces a directory
> > whenever the sql server uses a local admin account.We can resolve this
> > in three ways:-
> >
> > 1.Give the network share permissions for the the
> > domainname/computername account in this case domainname/compuetname$ .
> > 2.Change sql servr to use a domain account means chaning the apps to
> > use the domain acocunt a non starteer in my enviormment as the apps are
> > owned by the vendors.
> This is just plain wrong. Changing the account that the SQL Server and
> SQL Agent services run under has absolutely nothing to do with the
> logins use by applications to connect to SQL databases. If you want to
> access network resources from within SQL, this is how you do it. Change
> the MSSQLSERVER and SQLSERVERAGENT services to run as a domain user, and
> grant share permissions to that domain user.
>
> > 3.Use a proxy account for the sql server agent so that even if sql runs
> > on a local admin account the proxy account would enable the agent to
> > use a doain account.
> >
> > Thanks for your response.
> >
> >
> > Ajay
> >
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Maybe i did not explain it right:- AT the sql end changing the sql
server to use the domain service accoutn would make the sql server run
on a domain account but the DSn which is configurd to use the local
admin account and use IIS has been configured to use the local admin by
defualt(that is what irt chooses) SO CHANING THE SECURITY CONTEXT OF
THE SQL SERVER SERVICE AND THE SQL AGENT SERICE WOULD MEAN THAT I
CHANGE THE DSN OF ALL THE APPLICATIONS WHICH ARE CONFIGURED TO LOGIN
USING NT ATHENTICATION AND LOCAL ADMIN account on the box.Surprisingly
most apps reside on the same box as the sql server and use the Local
Admin account and are configured to use a dsn /logins odf the local
account on sql server.
This is diiifcult as it entails coordinatig with vendors and so I wold
not wat to go with this option.

Cannot get write permissions to a folder

I have a server ser1 which has the sql server running under the
security context of the local admin.Whn i try to copy the backup files
from this server to a network share it acnnot access the share unless
the sever has all authenticated user write permisssions.On setting the
auditing on we found that ser1$ uis the account which is trying to
write to the share.My question is as follows:- what is the difference
between the domaonname\ser1 and domainname\ser1$ account.I cannot see
this ser1$ account in the domain so I caaanot give it permissions.Is
there a way I could get to this account and give it permissions to
tighter up the security?
Thanks in anticipation.
AjayI'm not a network adminstrator, but I tried the same thing before and it
doesn't work. If you want SQL to have access to network resources it has to
run under a domain account. Then you can grant permissions to that account
on the network share you are trying to access. You will either need to setup
sql server to run under a domain account or have sql server write the backup
locally and schedule a job that can run with domain credentials to copy the
backup to the network share.
Mark
"Ag" <ajaygarg1962@.gmail.com> wrote in message
news:1154617829.443666.306270@.i42g2000cwa.googlegroups.com...
>I have a server ser1 which has the sql server running under the
> security context of the local admin.Whn i try to copy the backup files
> from this server to a network share it acnnot access the share unless
> the sever has all authenticated user write permisssions.On setting the
> auditing on we found that ser1$ uis the account which is trying to
> write to the share.My question is as follows:- what is the difference
> between the domaonname\ser1 and domainname\ser1$ account.I cannot see
> this ser1$ account in the domain so I caaanot give it permissions.Is
> there a way I could get to this account and give it permissions to
> tighter up the security?
> Thanks in anticipation.
>
> Ajay
>|||Mark Miller wrote:[vbcol=seagreen]
> I'm not a network adminstrator, but I tried the same thing before and it
> doesn't work. If you want SQL to have access to network resources it has t
o
> run under a domain account. Then you can grant permissions to that account
> on the network share you are trying to access. You will either need to set
up
> sql server to run under a domain account or have sql server write the back
up
> locally and schedule a job that can run with domain credentials to copy th
e
> backup to the network share.
> Mark
> "Ag" <ajaygarg1962@.gmail.com> wrote in message
> news:1154617829.443666.306270@.i42g2000cwa.googlegroups.com...
Thanks Mark for the response:-
Here is what I notices and I was able to resolve the issue:-
ser1$ is the computername account which is trying to acces a directory
whenever the sql server uses a local admin account.We can resolve this
in three ways:-
1.Give the network share permissions for the the
domainname/computername account in this case domainname/compuetname$ .
2.Change sql servr to use a domain account means chaning the apps to
use the domain acocunt a non starteer in my enviormment as the apps are
owned by the vendors.
3.Use a proxy account for the sql server agent so that even if sql runs
on a local admin account the proxy account would enable the agent to
use a doain account.
Thanks for your response.
Ajay[vbcol=seagreen]|||Ag wrote:
> Mark Miller wrote:
> Thanks Mark for the response:-
> Here is what I notices and I was able to resolve the issue:-
> ser1$ is the computername account which is trying to acces a directory
> whenever the sql server uses a local admin account.We can resolve this
> in three ways:-
> 1.Give the network share permissions for the the
> domainname/computername account in this case domainname/compuetname$ .
> 2.Change sql servr to use a domain account means chaning the apps to
> use the domain acocunt a non starteer in my enviormment as the apps are
> owned by the vendors.
This is just plain wrong. Changing the account that the SQL Server and
SQL Agent services run under has absolutely nothing to do with the
logins use by applications to connect to SQL databases. If you want to
access network resources from within SQL, this is how you do it. Change
the MSSQLSERVER and SQLSERVERAGENT services to run as a domain user, and
grant share permissions to that domain user.

> 3.Use a proxy account for the sql server agent so that even if sql runs
> on a local admin account the proxy account would enable the agent to
> use a doain account.
> Thanks for your response.
>
> Ajay
>
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Tracy McKibben wrote:
> Ag wrote:
> This is just plain wrong. Changing the account that the SQL Server and
> SQL Agent services run under has absolutely nothing to do with the
> logins use by applications to connect to SQL databases. If you want to
> access network resources from within SQL, this is how you do it. Change
> the MSSQLSERVER and SQLSERVERAGENT services to run as a domain user, and
> grant share permissions to that domain user.
>
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Maybe i did not explain it right:- AT the sql end changing the sql
server to use the domain service accoutn would make the sql server run
on a domain account but the DSn which is configurd to use the local
admin account and use IIS has been configured to use the local admin by
defualt(that is what irt chooses) SO CHANING THE SECURITY CONTEXT OF
THE SQL SERVER SERVICE AND THE SQL AGENT SERICE WOULD MEAN THAT I
CHANGE THE DSN OF ALL THE APPLICATIONS WHICH ARE CONFIGURED TO LOGIN
USING NT ATHENTICATION AND LOCAL ADMIN account on the box.Surprisingly
most apps reside on the same box as the sql server and use the Local
Admin account and are configured to use a dsn /logins odf the local
account on sql server.
This is diiifcult as it entails coordinatig with vendors and so I wold
not wat to go with this option.