Can't start SQL Server Agent

Hello,
When I try to start SQL Server Agent I get a message "An error 1049 - (The
service did not start due to a logon failure) while performing this service
operation on the SQLServerAgent service."
I am logged on to the machine as Administrator and SQL Server has a login
for Servername\Administrator.
I can perform data manipulation operations with no problems. I have not had
this problem on other servers before.
Any help would be appreciated.
RagnarHello,
Go to the COntrol Panel, Services, SQL Server Agent -- Go to Logon option
and chnage it to Local System Account and try restarting.
If it works fine then use a domain account and specify the password and
restrt the service.
I recommend you to start SQL Server and SQL Server Agent using the same
login account.
Thanks
Hari
"Ragnar Midtskogen" <ragnar_ng@.newsgroups.com> wrote in message
news:%23EzZ4wQYHHA.588@.TK2MSFTNGP06.phx.gbl...
> Hello,
> When I try to start SQL Server Agent I get a message "An error 1049 - (The
> service did not start due to a logon failure) while performing this
> service operation on the SQLServerAgent service."
> I am logged on to the machine as Administrator and SQL Server has a login
> for Servername\Administrator.
> I can perform data manipulation operations with no problems. I have not
> had this problem on other servers before.
> Any help would be appreciated.
> Ragnar
>|||Thank you Hari,
The logon was set as Administrator, so I just reset the password and that
solved the problem.
By the way, the SQL Server Agent properties shows startup account as being
Administrator and it also shows that the connection should use Windows
authentication.
I am a little confused as to what the difference is between the startup and
the connect properties, but as long as it works I am happy.
Ragnarsql

Can't start SQL Server Agent

Hello,
When I try to start SQL Server Agent I get a message "An error 1049 - (The
service did not start due to a logon failure) while performing this service
operation on the SQLServerAgent service."
I am logged on to the machine as Administrator and SQL Server has a login
for Servername\Administrator.
I can perform data manipulation operations with no problems. I have not had
this problem on other servers before.
Any help would be appreciated.
Ragnar
Hello,
Go to the COntrol Panel, Services, SQL Server Agent -- Go to Logon option
and chnage it to Local System Account and try restarting.
If it works fine then use a domain account and specify the password and
restrt the service.
I recommend you to start SQL Server and SQL Server Agent using the same
login account.
Thanks
Hari
"Ragnar Midtskogen" <ragnar_ng@.newsgroups.com> wrote in message
news:%23EzZ4wQYHHA.588@.TK2MSFTNGP06.phx.gbl...
> Hello,
> When I try to start SQL Server Agent I get a message "An error 1049 - (The
> service did not start due to a logon failure) while performing this
> service operation on the SQLServerAgent service."
> I am logged on to the machine as Administrator and SQL Server has a login
> for Servername\Administrator.
> I can perform data manipulation operations with no problems. I have not
> had this problem on other servers before.
> Any help would be appreciated.
> Ragnar
>
|||Thank you Hari,
The logon was set as Administrator, so I just reset the password and that
solved the problem.
By the way, the SQL Server Agent properties shows startup account as being
Administrator and it also shows that the connection should use Windows
authentication.
I am a little confused as to what the difference is between the startup and
the connect properties, but as long as it works I am happy.
Ragnar

Can't start SQL Server Agent

Hello,
When I try to start SQL Server Agent I get a message "An error 1049 - (The
service did not start due to a logon failure) while performing this service
operation on the SQLServerAgent service."
I am logged on to the machine as Administrator and SQL Server has a login
for Servername\Administrator.
I can perform data manipulation operations with no problems. I have not had
this problem on other servers before.
Any help would be appreciated.
RagnarHello,
Go to the COntrol Panel, Services, SQL Server Agent -- Go to Logon option
and chnage it to Local System Account and try restarting.
If it works fine then use a domain account and specify the password and
restrt the service.
I recommend you to start SQL Server and SQL Server Agent using the same
login account.
Thanks
Hari
"Ragnar Midtskogen" <ragnar_ng@.newsgroups.com> wrote in message
news:%23EzZ4wQYHHA.588@.TK2MSFTNGP06.phx.gbl...
> Hello,
> When I try to start SQL Server Agent I get a message "An error 1049 - (The
> service did not start due to a logon failure) while performing this
> service operation on the SQLServerAgent service."
> I am logged on to the machine as Administrator and SQL Server has a login
> for Servername\Administrator.
> I can perform data manipulation operations with no problems. I have not
> had this problem on other servers before.
> Any help would be appreciated.
> Ragnar
>|||Thank you Hari,
The logon was set as Administrator, so I just reset the password and that
solved the problem.
By the way, the SQL Server Agent properties shows startup account as being
Administrator and it also shows that the connection should use Windows
authentication.
I am a little confused as to what the difference is between the startup and
the connect properties, but as long as it works I am happy.
Ragnar

Cant run SQL Server 2000 Developer on XP MCE

I started with SQL Server 2005 Express and created a database. Due to circumstances I needed SS 2000. Uninstalled SS 2005 and installed SS 2000 without incident. I already had SS 2000 Enterprise Manager running with other client databases registered.

When I went to Ent Mgr and tried to register my new SS 2000 instance, I got this error: "A connection could not be established to LOYDSLAPTOP. Reason: SQL Server does not exist or access denied. ConnectionOpen (Connect()). Please verify the server is running and check your SQL Server registration properties (by right-clicking on the LOYDSLAPTOP node) and try again."

I have verified that the following services are both running: MSSQL$SQLSERVER2000 and SQLAgent$SQLSERVER2000.

I am certain that I used the sa user with password originally entered when I installed SS 2000 when I tried to register/connect to the local instance of SS. Plus I also tried to connect using the domain user and password entered when I installed SS and got the same error message.

What am I doing wrong? What do I need to change?

Thanks for any help anyone can offer.Shouldn't you use MSCE to run MSSQL SERV 2000 in Windows XP ?|||Not sure what you mean. I googled MSCE and all I got were misspellings of MCSE, or perhaps that is a previous certification from Microsoft. I called MS tech support and they told me that Win XP MCE was not a supported OS, so I guess I'm hosed on that.

Thanks anyway for trying.|||Sorry for the typo, I meant MSDE, and I can tell you it works. I use it on my xp.

http://www.microsoft.com/downloads/details.aspx?familyid=413744D1-A0BC-479F-BAFA-E4B278EB9147&displaylang=en|||Ortho,

Thanks for the info. That would have been a great suggestion. I am going to try and get the vendor to take back the SQL Server 2000 Developer Edition and trade it for a 2005 DE. I have already uninstalled the SS 2000 and reinstalled 2005 Express. Also, the hosting company was gracious enough to move us to a SS 2005 server and the backup file I created previously with 2005 Express worked beautifully, so I guess my problems are solved - except for getting my client's costs for the SS 2000 DE put to better use.

Thanks again for the help.|||2005 Express is the equivalent of MSDE but in 2005 version.

Can't register SQL Server locally due to Login problems

Hello,
I had installed SQL Server 2000 locally on my machine and I had 2 security
logins: -
1. sa - default database was set to dbTest
2. mydomain\myusername - default database was set to dbTest
The thing is, "dbTest" was deleted due to some testing and now when I try
to connect to my SQL Server with Enterprise Manager, Login fails as the
default database is missing.
Is there a way I can register back my server ?
Thanks,
Sam.
Message posted via http://www.sqlmonster.com
You can try connecting via osql.exe (a command line tool) and issue the
appropriate command to change the default database (using sp_defaultdb).
or
You can try modifying your shortcut to Query Analyzer to something like
this:
"C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\isqlw.exe" -SYourMachineNameHere -Usa -PTheSApwdGoesHer
e -dtempdb
I use the modified shortcut method to connect to a specific server and
connect to a specific database. However I don't know if you will be able to
do this if the user's default database is unavailable.
Keith
"Sameer Premji via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:3c315b71f1a74a548e1b9c93ad0da038@.SQLMonster.c om...
> Hello,
> I had installed SQL Server 2000 locally on my machine and I had 2 security
> logins: -
> 1. sa - default database was set to dbTest
> 2. mydomain\myusername - default database was set to dbTest
> The thing is, "dbTest" was deleted due to some testing and now when I try
> to connect to my SQL Server with Enterprise Manager, Login fails as the
> default database is missing.
> Is there a way I can register back my server ?
> Thanks,
> Sam.
> --
> Message posted via http://www.sqlmonster.com
|||The shortcut didn't work.
How do I use osql.exe because double-clicking on it, vanishes and what is
the statement ?
Message posted via http://www.sqlmonster.com
|||Since osql is a command line tool you need to
Start | Run | cmd <enter>
osql /? <enter>
Keith
"Sameer Premji via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:2313ae62041a424caca786036f7b4385@.SQLMonster.c om...
> The shortcut didn't work.
> How do I use osql.exe because double-clicking on it, vanishes and what is
> the statement ?
> --
> Message posted via http://www.sqlmonster.com

Can't register SQL Server locally due to Login problems

Hello,
I had installed SQL Server 2000 locally on my machine and I had 2 security
logins: -
1. sa - default database was set to dbTest
2. mydomain\myusername - default database was set to dbTest
The thing is, "dbTest" was deleted due to some testing and now when I try
to connect to my SQL Server with Enterprise Manager, Login fails as the
default database is missing.
Is there a way I can register back my server ?
Thanks,
Sam.
Message posted via http://www.droptable.comYou can try connecting via osql.exe (a command line tool) and issue the
appropriate command to change the default database (using sp_defaultdb).
or
You can try modifying your shortcut to Query Analyzer to something like
this:
"C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\isqlw.exe" -SYourMachineNameHere -Usa -PTheSApwdGoesHer
e -dtempdb
I use the modified shortcut method to connect to a specific server and
connect to a specific database. However I don't know if you will be able to
do this if the user's default database is unavailable.
Keith
"Sameer Premji via droptable.com" <forum@.droptable.com> wrote in message
news:3c315b71f1a74a548e1b9c93ad0da038@.SQ
droptable.com...
> Hello,
> I had installed SQL Server 2000 locally on my machine and I had 2 security
> logins: -
> 1. sa - default database was set to dbTest
> 2. mydomain\myusername - default database was set to dbTest
> The thing is, "dbTest" was deleted due to some testing and now when I try
> to connect to my SQL Server with Enterprise Manager, Login fails as the
> default database is missing.
> Is there a way I can register back my server ?
> Thanks,
> Sam.
> --
> Message posted via http://www.droptable.com|||The shortcut didn't work.
How do I use osql.exe because double-clicking on it, vanishes and what is
the statement ?
Message posted via http://www.droptable.com|||Since osql is a command line tool you need to
Start | Run | cmd <enter>
osql /? <enter>
Keith
"Sameer Premji via droptable.com" <forum@.droptable.com> wrote in message
news:2313ae62041a424caca786036f7b4385@.SQ
droptable.com...
> The shortcut didn't work.
> How do I use osql.exe because double-clicking on it, vanishes and what is
> the statement ?
> --
> Message posted via http://www.droptable.com

Can't register SQL Server locally due to Login problems

Hello,
I had installed SQL Server 2000 locally on my machine and I had 2 security
logins: -
1. sa - default database was set to dbTest
2. mydomain\myusername - default database was set to dbTest
The thing is, "dbTest" was deleted due to some testing and now when I try
to connect to my SQL Server with Enterprise Manager, Login fails as the
default database is missing.
Is there a way I can register back my server ?
Thanks,
Sam.
--
Message posted via http://www.sqlmonster.comYou can try connecting via osql.exe (a command line tool) and issue the
appropriate command to change the default database (using sp_defaultdb).
or
You can try modifying your shortcut to Query Analyzer to something like
this:
"C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\isqlw.exe" -SYourMachineNameHere -Usa -PTheSApwdGoesHer
e -dtempdb
I use the modified shortcut method to connect to a specific server and
connect to a specific database. However I don't know if you will be able to
do this if the user's default database is unavailable.
--
Keith
"Sameer Premji via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:3c315b71f1a74a548e1b9c93ad0da038@.SQLMonster.com...
> Hello,
> I had installed SQL Server 2000 locally on my machine and I had 2 security
> logins: -
> 1. sa - default database was set to dbTest
> 2. mydomain\myusername - default database was set to dbTest
> The thing is, "dbTest" was deleted due to some testing and now when I try
> to connect to my SQL Server with Enterprise Manager, Login fails as the
> default database is missing.
> Is there a way I can register back my server ?
> Thanks,
> Sam.
> --
> Message posted via http://www.sqlmonster.com|||The shortcut didn't work.
How do I use osql.exe because double-clicking on it, vanishes and what is
the statement ?
--
Message posted via http://www.sqlmonster.com|||Since osql is a command line tool you need to
Start | Run | cmd <enter>
osql /? <enter>
--
Keith
"Sameer Premji via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:2313ae62041a424caca786036f7b4385@.SQLMonster.com...
> The shortcut didn't work.
> How do I use osql.exe because double-clicking on it, vanishes and what is
> the statement ?
> --
> Message posted via http://www.sqlmonster.com

Can't pull the subscription

The process could not read file
'd:\sql_data\MSSQL\ReplData\unc\...\20050324084140 \snapshot.pre' due to OS
error 3.
What is going on?
Wack
This message will self destruct.
Looks like you set your snapshot folder to be a local path ("d:\...")
instead of a UNC path (\\mybox\d$\sql_data\MSSQL\ReplData). You specify the
default snapshot folder when you configure your publisher/distributor but
can override this value when you create a publication.
"Ray Lewis" <dav5489@.hotmail.com> wrote in message
news:enypHuHMFHA.3420@.tk2msftngp13.phx.gbl...
> The process could not read file
> 'd:\sql_data\MSSQL\ReplData\unc\...\20050324084140 \snapshot.pre' due to OS
> error 3.
> What is going on?
> --
> Wack
> --
> This message will self destruct.
>
|||The snapshots are going to the correct place, I.E, Server X = Distributor,
Server Y = Publisher, Server Z = Subscriber.
Server Y takes a snapshot of the db and stores it on Server X. Server Z,
however, can't get to the snapshot to replicate.
Wack
This message will self destruct.
"Mike Jansen" <mjansen_nntp@.mail.com> wrote in message
news:uJ4nJ7JMFHA.1300@.TK2MSFTNGP10.phx.gbl...
> Looks like you set your snapshot folder to be a local path ("d:\...")
> instead of a UNC path (\\mybox\d$\sql_data\MSSQL\ReplData). You specify
the[vbcol=seagreen]
> default snapshot folder when you configure your publisher/distributor but
> can override this value when you create a publication.
> "Ray Lewis" <dav5489@.hotmail.com> wrote in message
> news:enypHuHMFHA.3420@.tk2msftngp13.phx.gbl...
OS
>

can't move file for full-text index

Hi,
I need to move the file for my full-text catalog to a different drive due to
space issues. I've tried the following:
ALTER DATABASE mailarchivedec05
MODIFY FILE (NAME = MailArchiver3, filename = 'F:\FTDATA')
But get an error:
Server: Msg 5037, Level 16, State 1, Line 1
MODIFY FILE failed. Do not specify physical name.
According to the posting below I should take the database first offline, but
that gives a different error message about the db being offline.
http://www.microsoft.com/technet/community/newsgroups/dgbrowser/en-us/default.mspx?query=full-text+alter&dg=&cat=en-us-technet-sqlserv&lang=en&cr=US&pt=261BA873-F3AB-420E-96D6-E3004596A551&catlist=328BAFD2-1A81-4558-B1DE-B6EB49F31B7E&dglist=&ptlist=&exp=&sloc=en-us
Any other ideas? Thanks.
Panos.
Yes, it should be the logical name. Here is an example of how to do it.
1) determine the logical name of your full-text catalog file. Issue
the following command:
SELECT name FROM SYS.DATABASE_FILES WHERE TYPE_DESC='FULLTEXT'
Note the value returned in the name column. This is your logical name for
your full-text catalog. It will look something like this:
sysft_MyCatalogName where MyCatalogName is the name of your catalog.
2) Issue the below command:
ALTER DATABASE database_name SET OFFLINE
3) Stop Full-Text Search
4) Move the full-text catalog to the new location
5) Restart Full-Text Search
6) Issue the below command:
ALTER DATABASE database_name MODIFY FILE ( NAME = logical_name , FILENAME =
'new_path')
Where new_path is the new path to where you have moved your catalog.
7) Issue the below command:
ALTER DATABASE database_name SET ONLINE
You are now ready to query your full-text catalogs again.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Panos Stavroulis." <PanosStavroulis@.discussions.microsoft.com> wrote in
message news:CAB627A0-C3AE-44B7-B12F-F1D98643E6F6@.microsoft.com...
> Hi,
> I need to move the file for my full-text catalog to a different drive due
> to
> space issues. I've tried the following:
> ALTER DATABASE mailarchivedec05
> MODIFY FILE (NAME = MailArchiver3, filename = 'F:\FTDATA')
> But get an error:
> Server: Msg 5037, Level 16, State 1, Line 1
> MODIFY FILE failed. Do not specify physical name.
> According to the posting below I should take the database first offline,
> but
> that gives a different error message about the db being offline.
> http://www.microsoft.com/technet/community/newsgroups/dgbrowser/en-us/default.mspx?query=full-text+alter&dg=&cat=en-us-technet-sqlserv&lang=en&cr=US&pt=261BA873-F3AB-420E-96D6-E3004596A551&catlist=328BAFD2-1A81-4558-B1DE-B6EB49F31B7E&dglist=&ptlist=&exp=&sloc=en-us
> Any other ideas? Thanks.
> Panos.
|||Hilary,
It still doesn't work. By the way I am using 2000 not 2005, does it make any
difference? For example the command SELECT name FROM SYS.DATABASE_FILES
WHERE TYPE_DESC='FULLTEXT'
does't work. But I am sure I have the right logical name for my index.
I've managed to physically move the files as in step 4 but when the issue
the alter database command I still get the same error message. It doesn't
also like it when the database is offline, gives me an error.
Any other ideas? Thanks.
Panos.
"Hilary Cotter" wrote:

> Yes, it should be the logical name. Here is an example of how to do it.
> 1) determine the logical name of your full-text catalog file. Issue
> the following command:
> SELECT name FROM SYS.DATABASE_FILES WHERE TYPE_DESC='FULLTEXT'
> Note the value returned in the name column. This is your logical name for
> your full-text catalog. It will look something like this:
> sysft_MyCatalogName where MyCatalogName is the name of your catalog.
> 2) Issue the below command:
> ALTER DATABASE database_name SET OFFLINE
> 3) Stop Full-Text Search
> 4) Move the full-text catalog to the new location
> 5) Restart Full-Text Search
> 6) Issue the below command:
> ALTER DATABASE database_name MODIFY FILE ( NAME = logical_name , FILENAME =
> 'new_path')
> Where new_path is the new path to where you have moved your catalog.
> 7) Issue the below command:
> ALTER DATABASE database_name SET ONLINE
> You are now ready to query your full-text catalogs again.
>
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Panos Stavroulis." <PanosStavroulis@.discussions.microsoft.com> wrote in
> message news:CAB627A0-C3AE-44B7-B12F-F1D98643E6F6@.microsoft.com...
>
>
|||I did not realize you were using SQL 2000. In this case follow these steps:
http://support.microsoft.com/kb/240867
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Panos Stavroulis." <PanosStavroulis@.discussions.microsoft.com> wrote in
message news:153D7F5D-76C4-45D2-835B-B0AB382DDD7B@.microsoft.com...[vbcol=seagreen]
> Hilary,
> It still doesn't work. By the way I am using 2000 not 2005, does it make
> any
> difference? For example the command SELECT name FROM SYS.DATABASE_FILES
> WHERE TYPE_DESC='FULLTEXT'
> does't work. But I am sure I have the right logical name for my index.
> I've managed to physically move the files as in step 4 but when the issue
> the alter database command I still get the same error message. It doesn't
> also like it when the database is offline, gives me an error.
> Any other ideas? Thanks.
> Panos.
>
> "Hilary Cotter" wrote:
|||That worked fine. Thanks.
"Hilary Cotter" wrote:

> I did not realize you were using SQL 2000. In this case follow these steps:
> http://support.microsoft.com/kb/240867
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Panos Stavroulis." <PanosStavroulis@.discussions.microsoft.com> wrote in
> message news:153D7F5D-76C4-45D2-835B-B0AB382DDD7B@.microsoft.com...
>
>

Cant modify sp_admessage - Internals Mystery!!! Please Help!!!

Due to legacy issues we want to modify sp_addmessage. I am able to open it it up change the code I want to add but it wont compile.

All I am doing is changing:

-- Must be ServerAdmin to manage messages
if is_srvrolemember('serveradmin') = 0
begin
raiserror(15247,-1,-1)
return (1)
end

To this code:

if (not (is_srvrolemember('sysadmin') = 1)) and ((@.severity > 18) or
(rtrim(upper(@.with_log)) = 'TRUE'))
begin
raiserror(15042,-1,-1)
return (1)
end

When we recompile I get:

Msg 102, Level 15, State 1, Procedure sp_addmessage, Line 99
Incorrect syntax near '%'.
Msg 102, Level 15, State 1, Procedure sp_addmessage, Line 131
Incorrect syntax near '%'.
Msg 102, Level 15, State 1, Procedure sp_addmessage, Line 135
Incorrect syntax near '%'.
Msg 102, Level 15, State 1, Procedure sp_addmessage, Line 136
Incorrect syntax near '%'.
Msg 102, Level 15, State 1, Procedure sp_addmessage, Line 152
Incorrect syntax near '%'.
Msg 102, Level 15, State 1, Procedure sp_addmessage, Line 156
Incorrect syntax near '%'.

When we goto that line I see:

EXEC %%ErrorMessage(ID = @.msgnum).Lock(Exclusive = 1)

What is the "%%" doing - Does this make it impossible to modify?

Thanks,

Andy

In SQL SERVER 2005, majority of the system stored procedures including sp_addmessage exist in the read only resource database. You cannot modify them.

If you are creating your own procedure you cannot the "%%" syntax. This syntax is a hook to call functions inside the sqlservr.exe binary and is not available for user procedures.

Are you trying to restrict the roles that can call sp_addmessage ?

|||

Hi,

I have a similar problem, but want to solve it different.

Problem: sp_addmessage can only be called by sysadmin or serveradmin. But also normal users (with ddladmin/security/read/writer-role) should be able to call sp_addmessage.

Possible solution: I wrote a wrapper-procedure sp__addmessage which calls sp_addmessage with more rights:

create procedure sp__addmessage

(@.msgnum int, @.severity smallint, @.msgtext nvarchar(510),

@.lang sysname )

WITH execute as OWNER

AS

select 'I am ' + suser_name(), user_name()

exec sp_addmessage @.msgnum, @.severity, @.msgtext, @.lang

go

I create this procedure (sa__addmessage) as sa and grant execution to a user. When the user executes this function it is displayed, 'I am sa dbo' bit the execution of sp_addmessage is not permitted:

Msg 15247, Level 16, State 1, Procedure sp_addmessage, Line 18

User does not have permission to perform this action.

Has anybody an idea how to give the user permissions to execute sp_addmessage?

Cheers, Manuel

Can''t install the client components, error raised

Hi,

when I try to install the client components I receive this error:

Upgrade failed due to the following error. The error code is:

-2147467259. Message: Unspecified error

I think the problem is during the upgrade of the report server components.

my computer has the SQL 2005 client components installed but I have just uninstall these components.

I'll try on a second computer , the first one is Vista, the second is XP SP2.

I have opened a connect issue around this error including the complete log.

thanks for your guides.

For info:

the same steps on an XP SP2 station works fine.

(removing SQL 2005 client components and then installing SQL 2008 client components)

|||

In the katmai site has a document speaking that before you install katmai,remove the workstation components of Sql Server 2005...

4.3.3 Installing SQL Server "Katmai" Removes Support for DTS in SQL Server 2005 Integration Services Packages

For this CTP release, you must uninstall SQL Server 2005 Workstation Components before installing the SQL Server "Katmai" Workstation Components. Uninstalling the SQL Server 2005 Workstation Components removes three Integration Services components: the SQL Server 2005 version of the Execute DTS 2000 Package task and two supporting assemblies. These three Integration Services components support backward compatibility between SQL Server 2005 and SQL Server 2000 Data Transformation Services (DTS). Without these three components, SQL Server 2005 packages and tools that require DTS support will not run.

However, SQL Server "Katmai" Integration Services includes a version of the Execute DTS 2000 task and the two supporting assemblies. Therefore, you can upgrade SQL Server 2005 packages that require DTS support to the SQL Server "Katmai" format by opening them in the SQL Server "Katmai" version of Business Intelligence Development Studio, and then running those packages as SQL Server "Katmai" packages.

|||

I have removed everything from SQL 2005 and the error still here only on my Vista station.

I try to install each client component 1 by 1 and the error is raised when I try to install the BIDS (dev studio) component.

The server components can be installed without any issue.

|||Willgart,

On the succesful xp installation (where you un-installed the S2K5 client bits first), did you have CLR 2.0 installed on that box?

The reason I'm asking is that from my tests, it fails if you have CLR 2.0 installed when you do the Katmai installation, and Vista does have CLR 2.0 installed by default (iirc), but not xp.

Niels
|||I got the same "Upgrade failed due to the following error. The error code is:

-2147467259. Message:Unspecified error" message. I had uninstalled the SQL 2005 programs. Win XP SP2, VS 2005, Office 2007. I ran it from servers\splash.hta. This was the last Product, Workstation Components, Books Online and Development Tools. Any ideas?

The last page of the log is:

Property(S): SqlDefaultWebSite = /W3SVC/1
Property(S): SqlASPNETInstalled = 1
Property(S): SqlCOMPlusInstalled = 1
Property(S): RSPREREQUISITECHECKED = 1
Property(S): RSSqlPoolLimit = 100
Property(S): RSGUIDVALUE = {4a8abfef-1c99-4619-be39-8545354bd776}
Property(S): RemoveFeatureList = Client_Components,Connectivity,SQL_Tools,SQL_WarehouseDevWorkbench,SDK,SQLXML,Tools_Legacy,TOOLS_BC_DEP,SQL_Documentation,SQL_Samples,SQL_BooksOnline,SQL_DatabaseSamples
Property(S): SqlOriginalMachineName = 06LP201
Property(S): Namechecksumcommon_32 = Developer Edition
Property(S): SqlSubDir = \MSSQL
Property(S): EditionTypechecksumcommon_32 = Developer Edition
Property(S): Namechecksumtools = Developer Edition
Property(S): EditionTypechecksumtools = Developer Edition
Property(S): ValidMOFInstanceName = 1
Property(S): ROOTDRIVE = D:\
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): RSVirtualDirectoryServer = ReportServer
Property(S): RSVirtualDirectoryManager = Reports
Property(S): SOURCEDIR = C:\Temp\SQL Server Katmai Developer Edition X86, English\tools\Setup\
Property(S): SourcedirProduct = {D6251ACA-3FD4-49D1-8FCF-182B980B19E3}
Property(S): HxDs_Tmp_3643236F_FC70_11D3_A536_0090278A1BB8 = C:\DOCUME~1\ccook\LOCALS~1\Temp\HxC0D.tmp
Property(S): HxDs_Tmp_Hash_3643236F_FC70_11D3_A536_0090278A1BB8 = B40B0DC6C3C19C68E0101E0E2A647F0C3A18F6
Property(S): InstallNgenTicks = 2310000
Property(S): ProductToBeRegistered = 1
MSI (s) (088) [10:44:52:780]: Note: 1: 1708
MSI (s) (088) [10:44:52:780]: Product: Microsoft SQL Server "Katmai" Tools -- Installation failed.

MSI (s) (088) [10:44:52:820]: Cleaning up uninstalled install packages, if any exist
MSI (s) (088) [10:44:52:820]: MainEngineThread is returning 1603
MSI (s) (08:60) [10:44:52:931]: Destroying RemoteAPI object.
MSI (s) (08:2C) [10:44:52:931]: Custom Action Manager thread ending.
=== Logging stopped: 6/8/2007 10:44:52 ===
MSI (c) (8C:70) [10:44:52:971]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (8C:70) [10:44:52:971]: MainEngineThread is returning 1603
=== Verbose logging stopped: 6/8/2007 10:44:52 ===

|||

Hi,

As Willgart wrote database engine is installed without any problem.

But the client components seems to create problem during the installation.

I worked some on installing the client components of Katmai on Windows Server 2008 Beta3.

You can read my experience on installing the client components of Katmai at my blog http://www.kodyaz.com/blogs/software_development_blog/archive/2007/06/10/567.aspx

As a short brief I uninstalled the workstation tools of SQL2005, restart and then run the msi package from \tools\setup\sqlrun_tools.msi

This method successfully installed the client tools of Katmai side by side a SQL2005 instance.

Eralper

http://www.kodyaz.com

|||

I have allready try this method to install the client components but I suffer the same error.

|||

This problem usually occurs if you have Microsoft Visual Studio 8 installed in a non-default location.

Please confirm if you have VS8 installed in a non-default location. If so, setup cannot find the following file and causes this problem:

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\devenv.exe.config

If you put the missing file there and retry, setup should succeed.

|||

yes!

copying the file is the solution, I can successfully install the client components on my Vista station.

thanks.

|||

Well....

the installation was done, but none of the visual studio components works fine!

everytim I try to open a solution or create a new one I receive a lot of error (component not found and VS ask me to disable the non working component)

so it's certainly related to my VS setup which is not in the c: folder.

so I'll wait for the next release.

|||

Hi,

I had the same problem with installing the workstation components, but I tried to install the system on clean new VirualPC Windows Server 2003 SP1 nothing else installed....

BUT!: I installed .NET framework 2.0 and the .NET Framework 2.0 SDK before SQL-Server 2008 !!!!

After removing SDK, installation finished successfully !!!

Hope that helps!

|||I first assumed that it was problems with <SQL Server 2000 DTS Designer Components> but I don't think that was the main reason for this error message.
I can confirm that there are some problems installing SQL Server 10.0.1019 components when Microsoft .Net Framework 2.0 allready is installed (with patch).
I tried to install SQL server several times with same error messange until I uninstalled exsisting .Net Framework installation. It seems that components want to use the .Net Framework 2.0 that is bundled with SQL server.|||

Hi people! This is my first post here, with the same problem that the rest of you, except that my platform is Windows Server 2008 B3. I can install the DB engine but can't install client tools... any ideas? Tip: i've already installed Sharepoint Services v3.0 (with its own database engine... maybe the problem come from there....)

Agustín

Can't install the client components, error raised

Hi,

when I try to install the client components I receive this error:

Upgrade failed due to the following error. The error code is:

-2147467259. Message: Unspecified error

I think the problem is during the upgrade of the report server components.

my computer has the SQL 2005 client components installed but I have just uninstall these components.

I'll try on a second computer , the first one is Vista, the second is XP SP2.

I have opened a connect issue around this error including the complete log.

thanks for your guides.

For info:

the same steps on an XP SP2 station works fine.

(removing SQL 2005 client components and then installing SQL 2008 client components)

|||

In the katmai site has a document speaking that before you install katmai,remove the workstation components of Sql Server 2005...

4.3.3 Installing SQL Server "Katmai" Removes Support for DTS in SQL Server 2005 Integration Services Packages

For this CTP release, you must uninstall SQL Server 2005 Workstation Components before installing the SQL Server "Katmai" Workstation Components. Uninstalling the SQL Server 2005 Workstation Components removes three Integration Services components: the SQL Server 2005 version of the Execute DTS 2000 Package task and two supporting assemblies. These three Integration Services components support backward compatibility between SQL Server 2005 and SQL Server 2000 Data Transformation Services (DTS). Without these three components, SQL Server 2005 packages and tools that require DTS support will not run.

However, SQL Server "Katmai" Integration Services includes a version of the Execute DTS 2000 task and the two supporting assemblies. Therefore, you can upgrade SQL Server 2005 packages that require DTS support to the SQL Server "Katmai" format by opening them in the SQL Server "Katmai" version of Business Intelligence Development Studio, and then running those packages as SQL Server "Katmai" packages.

|||

I have removed everything from SQL 2005 and the error still here only on my Vista station.

I try to install each client component 1 by 1 and the error is raised when I try to install the BIDS (dev studio) component.

The server components can be installed without any issue.

|||Willgart,

On the succesful xp installation (where you un-installed the S2K5 client bits first), did you have CLR 2.0 installed on that box?

The reason I'm asking is that from my tests, it fails if you have CLR 2.0 installed when you do the Katmai installation, and Vista does have CLR 2.0 installed by default (iirc), but not xp.

Niels
|||I got the same "Upgrade failed due to the following error. The error code is:

-2147467259. Message:Unspecified error" message. I had uninstalled the SQL 2005 programs. Win XP SP2, VS 2005, Office 2007. I ran it from servers\splash.hta. This was the last Product, Workstation Components, Books Online and Development Tools. Any ideas?

The last page of the log is:

Property(S): SqlDefaultWebSite = /W3SVC/1
Property(S): SqlASPNETInstalled = 1
Property(S): SqlCOMPlusInstalled = 1
Property(S): RSPREREQUISITECHECKED = 1
Property(S): RSSqlPoolLimit = 100
Property(S): RSGUIDVALUE = {4a8abfef-1c99-4619-be39-8545354bd776}
Property(S): RemoveFeatureList = Client_Components,Connectivity,SQL_Tools,SQL_WarehouseDevWorkbench,SDK,SQLXML,Tools_Legacy,TOOLS_BC_DEP,SQL_Documentation,SQL_Samples,SQL_BooksOnline,SQL_DatabaseSamples
Property(S): SqlOriginalMachineName = 06LP201
Property(S): Namechecksumcommon_32 = Developer Edition
Property(S): SqlSubDir = \MSSQL
Property(S): EditionTypechecksumcommon_32 = Developer Edition
Property(S): Namechecksumtools = Developer Edition
Property(S): EditionTypechecksumtools = Developer Edition
Property(S): ValidMOFInstanceName = 1
Property(S): ROOTDRIVE = D:\
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): RSVirtualDirectoryServer = ReportServer
Property(S): RSVirtualDirectoryManager = Reports
Property(S): SOURCEDIR = C:\Temp\SQL Server Katmai Developer Edition X86, English\tools\Setup\
Property(S): SourcedirProduct = {D6251ACA-3FD4-49D1-8FCF-182B980B19E3}
Property(S): HxDs_Tmp_3643236F_FC70_11D3_A536_0090278A1BB8 = C:\DOCUME~1\ccook\LOCALS~1\Temp\HxC0D.tmp
Property(S): HxDs_Tmp_Hash_3643236F_FC70_11D3_A536_0090278A1BB8 = B40B0DC6C3C19C68E0101E0E2A647F0C3A18F6
Property(S): InstallNgenTicks = 2310000
Property(S): ProductToBeRegistered = 1
MSI (s) (088) [10:44:52:780]: Note: 1: 1708
MSI (s) (088) [10:44:52:780]: Product: Microsoft SQL Server "Katmai" Tools -- Installation failed.

MSI (s) (088) [10:44:52:820]: Cleaning up uninstalled install packages, if any exist
MSI (s) (088) [10:44:52:820]: MainEngineThread is returning 1603
MSI (s) (08:60) [10:44:52:931]: Destroying RemoteAPI object.
MSI (s) (08:2C) [10:44:52:931]: Custom Action Manager thread ending.
=== Logging stopped: 6/8/2007 10:44:52 ===
MSI (c) (8C:70) [10:44:52:971]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (8C:70) [10:44:52:971]: MainEngineThread is returning 1603
=== Verbose logging stopped: 6/8/2007 10:44:52 ===

|||

Hi,

As Willgart wrote database engine is installed without any problem.

But the client components seems to create problem during the installation.

I worked some on installing the client components of Katmai on Windows Server 2008 Beta3.

You can read my experience on installing the client components of Katmai at my blog http://www.kodyaz.com/blogs/software_development_blog/archive/2007/06/10/567.aspx

As a short brief I uninstalled the workstation tools of SQL2005, restart and then run the msi package from \tools\setup\sqlrun_tools.msi

This method successfully installed the client tools of Katmai side by side a SQL2005 instance.

Eralper

http://www.kodyaz.com

|||

I have allready try this method to install the client components but I suffer the same error.

|||

This problem usually occurs if you have Microsoft Visual Studio 8 installed in a non-default location.

Please confirm if you have VS8 installed in a non-default location. If so, setup cannot find the following file and causes this problem:

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\devenv.exe.config

If you put the missing file there and retry, setup should succeed.

|||

yes!

copying the file is the solution, I can successfully install the client components on my Vista station.

thanks.

|||

Well....

the installation was done, but none of the visual studio components works fine!

everytim I try to open a solution or create a new one I receive a lot of error (component not found and VS ask me to disable the non working component)

so it's certainly related to my VS setup which is not in the c: folder.

so I'll wait for the next release.

|||

Hi,

I had the same problem with installing the workstation components, but I tried to install the system on clean new VirualPC Windows Server 2003 SP1 nothing else installed....

BUT!: I installed .NET framework 2.0 and the .NET Framework 2.0 SDK before SQL-Server 2008 !!!!

After removing SDK, installation finished successfully !!!

Hope that helps!

|||I first assumed that it was problems with <SQL Server 2000 DTS Designer Components> but I don't think that was the main reason for this error message.
I can confirm that there are some problems installing SQL Server 10.0.1019 components when Microsoft .Net Framework 2.0 allready is installed (with patch).
I tried to install SQL server several times with same error messange until I uninstalled exsisting .Net Framework installation. It seems that components want to use the .Net Framework 2.0 that is bundled with SQL server.|||

Hi people! This is my first post here, with the same problem that the rest of you, except that my platform is Windows Server 2008 B3. I can install the DB engine but can't install client tools... any ideas? Tip: i've already installed Sharepoint Services v3.0 (with its own database engine... maybe the problem come from there....)

Agustín

Cant import an Access table due to null values.

Question: Why would I not be able to import an Access 97 table in
which some records have null values in fields that allow null values?

Wouldn't the table's design be imported first, bringing the columns'
"allow nulls" attribute with it?

I'm dealing with both text and numeric columns. Not all columns
containing nulls cause an error.

Thanks,

Bob C."Bob C." <bcanavan@.bmghomes.com> wrote in message
news:2e5623fb.0402201301.4098061b@.posting.google.c om...
> Question: Why would I not be able to import an Access 97 table in
> which some records have null values in fields that allow null values?
> Wouldn't the table's design be imported first, bringing the columns'
> "allow nulls" attribute with it?
> I'm dealing with both text and numeric columns. Not all columns
> containing nulls cause an error.
> Thanks,
> Bob C.

It's hard to say (at least for me) what the issue may be without more
information. In particular, how are you importing the table, and what is the
exact error message you see? Also, which version of SQL Server are you using
as the target for the import? If you're using the upsizing wizard, you may
want to post this in an Access newsgroup as well, as it's an Access tool,
not an MSSQL one.

Simon|||Thanks, Simon.

I'm using DTS to import to SQL2k. Sorry for not posting that
information.

It turns out that only two of the columns in my Access table were
affected, and they both disallowed nulls. This attribute was one I
set after the Access database had been in production awhile, and the
db manager asked that nulls for those columns be blocked. I think
what happened was that nulls already in those columns were
grandfathered(strange that I wasn't warned when I set the "allow
nulls" attribute to false), and the new table structure in SQL2k
correctly carried over the attribute - tripping over the grandfathered
nulls when I tried to import them.

Thanks for your help.

Bob C.