Cant start report server

Hey all. I'm using SQL server Express and I've installed the Report service. When I go into the reporting services configuration manager and I want to start the service, the system won't let me. Here is the error

System.ServiceProcess.TimeoutException: Time out has expired and the operation has not been completed.
at System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus desiredStatus, TimeSpan timeout)
at ReportServicesConfigUI.Panels.ServerInformationPanel.StartStopServiceTask(Boolean start)

I just can't seem to be able to start the service.

Can you plz help?

Thanks

Hi,

Based on my understanding, this error message is caused by the permission issue. You should take a look at the Report Server logs, and make sure you are configuring locally and you are administrator on the machine. And re-modify your reporting service configuration in the following way:

1. Created ReportService database using Report Service Configuration
2. Edited your personal account to Web Service Account in rsreportserver.config
3. Used rsconfig utility to encrypt the connection and account information
4. Edited your personal account to <processModel userName=" " >

If the problem still exists, you should try the following methods.

Set the Report Server Web service and Report Manager to use the same application pool.

|||

Thank you for your answer. But how can I create a reportservice database if I can't connect to the service?

++ Where do I go to

Set the Report Server Web service and Report Manager to use the same application pool.

Add the security account to the SQLServer2005ReportingServicesWebServiceUser$InstanceName group that you use for the application pool identity.

|||

Hi,

Set the Report Server Web service and Report Manager to use the same application pool.

Add the security account to the SQLServer2005ReportingServicesWebServiceUser$InstanceName group that you use for the application pool identity.

Can't start a job that was created by user A from user B

Hello all,
I have a job I created with user A, but I need user B to be able to execute
this job programatically. I've given user B permission to EXECUTE the
"msdb.dbo.sp_start_job" sproc and the user is able to execute it but with an
error thrown. The following is the error I get when I run it with user B.
This error does not appear when I run it with user A.
The specified @.job_name ('MyJobName') does not exist.
After doing some research by looking at the system sprocs, I found that the
error is thrown from a call made to 'msdb.dbo.sp_verify_job_identifiers'. I
researched that sproc and then found the system code that is throwing the
error, listed below.
-- Check if the job name is ambiguous
IF ((SELECT COUNT(*)
FROM msdb.dbo.sysjobs_view
WHERE (name = @.job_name)) > 1)
BEGIN
RAISERROR(14293, -1, -1, @.job_name, @.name_of_id_parameter,
@.name_of_name_parameter)
RETURN(1) -- Failure
END
I performed a SELECT * query to the sysjobs_view view with user B and 0 rows
were returned. So it appears that the view is filtering the results by user
and the job is not found which is causing the error.
Do you guys know of a way I can make this work? I would appreciate any help.
Thanks!
Johnny
Hi Johnny,
Only members of the sysadmin fixed role or the jobowner can start a job.
HTH
Adam
Adam J Warne, MCDBA
"Johnny" wrote:

> Hello all,
> I have a job I created with user A, but I need user B to be able to execute
> this job programatically. I've given user B permission to EXECUTE the
> "msdb.dbo.sp_start_job" sproc and the user is able to execute it but with an
> error thrown. The following is the error I get when I run it with user B.
> This error does not appear when I run it with user A.
> The specified @.job_name ('MyJobName') does not exist.
> After doing some research by looking at the system sprocs, I found that the
> error is thrown from a call made to 'msdb.dbo.sp_verify_job_identifiers'. I
> researched that sproc and then found the system code that is throwing the
> error, listed below.
> -- Check if the job name is ambiguous
> IF ((SELECT COUNT(*)
> FROM msdb.dbo.sysjobs_view
> WHERE (name = @.job_name)) > 1)
> BEGIN
> RAISERROR(14293, -1, -1, @.job_name, @.name_of_id_parameter,
> @.name_of_name_parameter)
> RETURN(1) -- Failure
> END
>
> I performed a SELECT * query to the sysjobs_view view with user B and 0 rows
> were returned. So it appears that the view is filtering the results by user
> and the job is not found which is causing the error.
> Do you guys know of a way I can make this work? I would appreciate any help.
> Thanks!
> Johnny
>
|||Thanks. I didnt want to do that but I guess I have no choice.
Johnny
"Adam Warne" wrote:
[vbcol=seagreen]
> Hi Johnny,
> Only members of the sysadmin fixed role or the jobowner can start a job.
> HTH
> Adam
> --
> Adam J Warne, MCDBA
>
> "Johnny" wrote:

Cant see stored procedures

Hi,

Can anyone help me. I've created a stored procedure in sql server and I'm trying to run it from my asp.net page. On Database Explorer I can't see it, or any for that matter, however I can see tables in the same schema.

Also I can't see it when I build a table adapter either.

Can anybody help?

Thanks

Sam

My first suspicion is that you didn't succeed in creating the stored procedure as you think you have done. To allay that suspicion, can you see the proc in Sql Server Management Studio?

|||

Yes I can see it and execute it, it works fine through sql server

I'm thinking that it might be because I'm using the express versions of the software sql server studio and visual web developer. Do you think that might be limiting the functionality?

|||

No. That wouldn't limit what you can see in the Database explorer. I've just attached Northwind to SqlExpress, and can see the procs, views etc in DataBase Explorer in VWD.

Try clicking the Refresh button at the top of the Database Explorer panel.

|||

check you master database mybe you created it in default database which is usual master when you open New Query window.If it is true put line below on top of your proceureUSE [DATABASE NAME] GO

|||

As JPazgier mentioned you probably created the proc in the default master db. If so, script out the proc, drop the proc from master db, re-create it in the actual db. If that is not the case and the proc is already in the right database, then check your connection string to see if your application is connecting to the right database.

Can't restore master db!

Hi:
I've got a problem that's causing me headaches! I'm using Veritas Backup Exec to perform my db backups. I've just
recently taken over the DBA responsibilities and one of the first things I've wanted to do is test those backups since
we've never had occassion to use the backups. I have a test system that I'm using and have it configured exactly as the
production system.
After installing MS SQL Server 7 putting on SP4 and all the security patches I try to restore all the databases. I can
get all my databases restored except the master db that contains all my security info. I keep getting the message
"must be in single user mode". I've tried to set the master db into single user mode and there's just no way to do it!!
I've tried using the EM and the sp_dboption. Without that master db restored I'm in deep doo-doo!
Any ideas how I can handle this? Any help/suggestions is greatly appreciated.
TIA
Cathy
SQL Server 7( SP4), NT4.0
Hi,
To restore the master database you have start the SQL server itself in
Single user mode.
1. Stop the MSSQL server and sql agent service
2. Go to command prompt and execute below command,.
sqlservr.exe -c -m
3. Login to sql server using query analyzer and retore the master database.
4. After the restore .. go to old comamnd prompt and press CONTRL and C to
close the old session
5. Go to control panel and start the MSSQL server and Sql agent service.
Note:
I recommend you to restore the master database first followed with other
databases.
Thanks
Hari
MCDBA
"Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in message
news:jamsg0tqoig5fqs15kdonltvlitoiktf3u@.4ax.com...
> Hi:
> I've got a problem that's causing me headaches! I'm using Veritas Backup
Exec to perform my db backups. I've just
> recently taken over the DBA responsibilities and one of the first things
I've wanted to do is test those backups since
> we've never had occassion to use the backups. I have a test system that
I'm using and have it configured exactly as the
> production system.
> After installing MS SQL Server 7 putting on SP4 and all the security
patches I try to restore all the databases. I can
> get all my databases restored except the master db that contains all my
security info. I keep getting the message
> "must be in single user mode". I've tried to set the master db into
single user mode and there's just no way to do it!!
> I've tried using the EM and the sp_dboption. Without that master db
restored I'm in deep doo-doo!
> Any ideas how I can handle this? Any help/suggestions is greatly
appreciated.
> TIA
> Cathy
> SQL Server 7( SP4), NT4.0
|||This method will work. I think Hari copied and pasted the answer directly
from Books Online! I would have provided exactly the same answer. I
probably would have also pointed you at Books Online (within your SQL Server
program group). BACKUP and RESTORE information and examples can be found
there. Knowing how to restore the data that you are backing up is
important. Cathy, you are smart to be doing your research now (instead of
when the entire company is waiting for you to restore the data).
Keith
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:u%23SoMWKeEHA.1764@.TK2MSFTNGP10.phx.gbl...
> Hi,
> To restore the master database you have start the SQL server itself in
> Single user mode.
> 1. Stop the MSSQL server and sql agent service
> 2. Go to command prompt and execute below command,.
> sqlservr.exe -c -m
> 3. Login to sql server using query analyzer and retore the master
database.
> 4. After the restore .. go to old comamnd prompt and press CONTRL and C to
> close the old session
> 5. Go to control panel and start the MSSQL server and Sql agent service.
> Note:
> I recommend you to restore the master database first followed with other
> databases.
> Thanks
> Hari
> MCDBA
>
> "Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in
message
> news:jamsg0tqoig5fqs15kdonltvlitoiktf3u@.4ax.com...
> Exec to perform my db backups. I've just
> I've wanted to do is test those backups since
> I'm using and have it configured exactly as the
> patches I try to restore all the databases. I can
> security info. I keep getting the message
> single user mode and there's just no way to do it!!
> restored I'm in deep doo-doo!
> appreciated.
>
|||Thanks guys for your prompt reply.
I thought I was starting the SQL Server in single user mode: I'm using the command "net start mssqlserver -m"... Is this not correct?
"Keith Kratochvil" wrote:

> This method will work. I think Hari copied and pasted the answer directly
> from Books Online! I would have provided exactly the same answer. I
> probably would have also pointed you at Books Online (within your SQL Server
> program group). BACKUP and RESTORE information and examples can be found
> there. Knowing how to restore the data that you are backing up is
> important. Cathy, you are smart to be doing your research now (instead of
> when the entire company is waiting for you to restore the data).
> --
> Keith
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:u%23SoMWKeEHA.1764@.TK2MSFTNGP10.phx.gbl...
> database.
> message
>
|||No, NET START starts the MSSQLSERVER service, and the -m is a parameter to
NET START, which doesn't take any parameters so it wouldn't know what to do
with it.
You need to run the sqlservr executable, and the pass the -m flag to it as
Hari suggested.
HTH
Kalen Delaney
SQL Server MVP
www.SolidQualityLearning.com
"caeriel" <caeriel@.discussions.microsoft.com> wrote in message
news:9542FB0A-84B5-4DDD-8498-87C5F4A91D4A@.microsoft.com...
> Thanks guys for your prompt reply.
> I thought I was starting the SQL Server in single user mode: I'm using
the command "net start mssqlserver -m"... Is this not correct?[vbcol=seagreen]
> "Keith Kratochvil" wrote:
directly[vbcol=seagreen]
Server[vbcol=seagreen]
found[vbcol=seagreen]
of[vbcol=seagreen]
C to[vbcol=seagreen]
service.[vbcol=seagreen]
other[vbcol=seagreen]
Backup[vbcol=seagreen]
things[vbcol=seagreen]
that[vbcol=seagreen]
my[vbcol=seagreen]
|||Keith: I'm still unable to restore the master database...
I tried starting the server as you & Hari instructed; the server started in single user mode. However, the restore has to be issued from the Veritas software interface. Here's the SQL Server log.
*************************************
================================================== ====================
Job server: Test
Job name: MasterDB NoRecov 8-03
Job started: Tuesday, August 03, 2004 at 10:08:07 AM
Job type: Restore
Job Log: BEX41.txt
================================================== ====================
Drive and media information from media mount:
Robotic Library Name:
Drive Name: Quantum 1
Slot: 0
Media GUID: {2E9659D2-C5B5-43BF-BD2A-502B2E1054E1}
Media Label: Test Wk1 Monday
Overwrite Protection Time Left: None
Append Time Left: Infinite
================================================== ====================
Job Operation - Restore
================================================== ====================
Restoring data to Test .
Storage Media #1: " Media created 8/2/04 08:24:56 PM "
Backup performed on 8/3/04 at 8:12 AM
Backup set #6: " Full Backup "
Restore started on 8/3/04 at 10:10:35 AM.
An error occurred on a query to database master.
^ ^ ^ ^ ^
SQL Server returned the following error message:
RESTORE DATABASE must be used in single user mode when trying to restore the master database.
^ ^ ^ ^ ^
Restore completed on 8/3/04 at 10:13:42 AM.
1 item was skipped.
Processed 0 bytes in 3 minutes and 7 seconds.
Throughput rate: 0.0 MB/min
================================================== ====================
Job ended: Tuesday, August 03, 2004 at 10:14:31 AM
Job completion status: Failed
================================================== ====================
************************************************** **
2004-08-03 09:55:16.51 kernel Microsoft SQL Server 7.00 - 7.00.623 (Intel X86)
Nov 27 1998 22:20:07
Copyright (c) 1988-1998 Microsoft Corporation
Standard Edition on Windows NT 4.0 (Build 1381: Service Pack 6)
2004-08-03 09:55:16.51 kernel Copyright (C) 1988-1997 Microsoft Corporation.
2004-08-03 09:55:16.52 kernel All rights reserved.
2004-08-03 09:55:16.52 kernel Logging SQL Server messages in file 'D:\MSSQL7\log\ERRORLOG'.
2004-08-03 09:55:16.58 kernel initconfig: Number of user connections limited to 32767.
2004-08-03 09:55:16.58 kernel SQL Server is starting at priority class 'normal'(1 CPU detected).
2004-08-03 09:55:16.70 kernel User Mode Scheduler configured for thread processing
2004-08-03 09:55:17.96 server Directory Size: 10801
2004-08-03 09:55:18.05 spid1 Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks
2004-08-03 09:55:18.05 kernel Attempting to initialize Distributed Transaction Coordinator.
2004-08-03 09:55:18.82 spid1 Failed to obtain TransactionDispenserInterface: XACT_E_TMNOTAVAILABLE
2004-08-03 09:55:18.83 spid1 Warning ******************
2004-08-03 09:55:18.83 spid1 SQL Server started in single user mode. Updates allowed to system catalogs.
2004-08-03 09:55:18.84 spid1 Warning ******************
2004-08-03 09:55:18.85 spid1 Starting up database 'master'.
2004-08-03 09:55:18.85 spid1 Opening file D:\MSSQL7\data\master.mdf.
2004-08-03 09:55:18.89 spid1 Opening file D:\MSSQL7\data\mastlog.ldf.
2004-08-03 09:55:18.99 spid1 Loading SQL Server's Unicode collation.
2004-08-03 09:55:19.01 spid1 Loading SQL Server's non-Unicode sort order and character set.
2004-08-03 09:55:19.24 spid1 4 transactions rolled forward in database 'master' (1).
2004-08-03 09:55:19.25 spid1 0 transactions rolled back in database 'master' (1).
2004-08-03 09:55:19.35 spid1 Starting up database 'model'.
2004-08-03 09:55:19.36 spid1 Opening file D:\MSSQL7\DATA\model.mdf.
2004-08-03 09:55:19.43 spid1 Opening file D:\MSSQL7\DATA\modellog.ldf.
2004-08-03 09:55:19.63 spid1 Clearing tempdb database.
2004-08-03 09:55:19.69 spid1 Creating file D:\MSSQL7\DATA\TEMPDB.MDF.
2004-08-03 09:55:19.87 spid1 Closing file D:\MSSQL7\DATA\TEMPDB.MDF.
2004-08-03 09:55:19.97 spid1 Creating file D:\MSSQL7\DATA\TEMPLOG.LDF.
2004-08-03 09:55:19.99 spid1 Closing file D:\MSSQL7\DATA\TEMPLOG.LDF.
2004-08-03 09:55:20.12 spid1 Opening file D:\MSSQL7\DATA\TEMPDB.MDF.
2004-08-03 09:55:20.14 spid1 Opening file D:\MSSQL7\DATA\TEMPLOG.LDF.
2004-08-03 09:55:21.15 spid1 Closing file D:\MSSQL7\DATA\TEMPDB.MDF.
2004-08-03 09:55:21.25 spid1 Closing file D:\MSSQL7\DATA\TEMPLOG.LDF.
2004-08-03 09:55:21.34 spid1 Starting up database 'tempdb'.
2004-08-03 09:55:21.38 spid1 Opening file D:\MSSQL7\DATA\TEMPDB.MDF.
2004-08-03 09:55:21.41 spid1 Opening file D:\MSSQL7\DATA\TEMPLOG.LDF.
2004-08-03 09:55:21.69 spid1 Server name is 'AOATESTBOX'.
2004-08-03 09:55:21.70 kernel Using 'SQLEVN70.DLL' version '7.00.623'.
2004-08-03 09:55:21.71 kernel Using 'OPENDS60.DLL' version '7.00.00.0623'.
2004-08-03 09:55:21.71 ods Using 'SSNMPN70.DLL' version '7.0.623' to listen on '\\.\pipe\sql\query'.
2004-08-03 09:55:21.72 ods Using 'SSMSSO70.DLL' version '7.0.623' to listen on '3180'.
2004-08-03 09:55:21.82 ods Using 'SSMSRP70.DLL' version '7.0.623' to listen on 'AOATESTBOX'.
2004-08-03 09:55:22.68 spid5 Starting up database 'msdb'.
2004-08-03 09:55:22.68 spid5 Opening file D:\MSSQL7\DATA\msdbdata.mdf.
2004-08-03 09:55:22.70 spid6 Starting up database 'pubs'.
2004-08-03 09:55:22.70 spid6 Opening file D:\MSSQL7\DATA\pubs.mdf.
2004-08-03 09:55:22.72 spid7 Starting up database 'Northwind'.
2004-08-03 09:55:22.72 spid7 Opening file D:\MSSQL7\DATA\northwnd.mdf.
2004-08-03 09:55:22.82 spid5 Opening file D:\MSSQL7\DATA\msdblog.ldf.
2004-08-03 09:55:22.85 spid7 Opening file D:\MSSQL7\DATA\northwnd.ldf.
2004-08-03 09:55:22.87 spid6 Opening file D:\MSSQL7\DATA\pubs_log.ldf.
2004-08-03 09:55:23.55 spid1 Recovery complete.
2004-08-03 09:55:23.56 spid1 SQL Server's Unicode collation is:
2004-08-03 09:55:23.57 spid1 'English' (ID = 1033).
2004-08-03 09:55:23.57 spid1 comparison style = 196609.
2004-08-03 09:55:23.58 spid1 SQL Server's non-Unicode sort order is:
2004-08-03 09:55:23.58 spid1 'nocase_850' (ID = 42).
2004-08-03 09:55:23.58 spid1 SQL Server's non-Unicode character set is:
2004-08-03 09:55:23.58 spid1 'cp850' (ID = 2).
2004-08-03 09:57:00.02 spid6 Using 'xpstar.dll' version '1998.11.13' to execute extended stored procedure 'sp_MSgetversion'.
2004-08-03 10:16:44.05 kernel SQL Server shutdown due to Ctrl-C or Ctrl-Break signal.
************************************************** *****
Here's the Veritas log:
************************************************
************************************************
"Keith Kratochvil" wrote:

> This method will work. I think Hari copied and pasted the answer directly
> from Books Online! I would have provided exactly the same answer. I
> probably would have also pointed you at Books Online (within your SQL Server
> program group). BACKUP and RESTORE information and examples can be found
> there. Knowing how to restore the data that you are backing up is
> important. Cathy, you are smart to be doing your research now (instead of
> when the entire company is waiting for you to restore the data).
> --
> Keith
>
> "Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
> news:u%23SoMWKeEHA.1764@.TK2MSFTNGP10.phx.gbl...
> database.
> message
>
|||This may be a problem with Veritas software. Can you get the backup files
from Veritas, and do the restore manually through Query Analyzer?
Restore database master from disk = "C:\whatever"
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Cathy Finnegan" <eliminates_spam_caeriel1@.cablespeed.com> wrote in message
news:jamsg0tqoig5fqs15kdonltvlitoiktf3u@.4ax.com...
> Hi:
> I've got a problem that's causing me headaches! I'm using Veritas Backup
Exec to perform my db backups. I've just
> recently taken over the DBA responsibilities and one of the first things
I've wanted to do is test those backups since
> we've never had occassion to use the backups. I have a test system that
I'm using and have it configured exactly as the
> production system.
> After installing MS SQL Server 7 putting on SP4 and all the security
patches I try to restore all the databases. I can
> get all my databases restored except the master db that contains all my
security info. I keep getting the message
> "must be in single user mode". I've tried to set the master db into
single user mode and there's just no way to do it!!
> I've tried using the EM and the sp_dboption. Without that master db
restored I'm in deep doo-doo!
> Any ideas how I can handle this? Any help/suggestions is greatly
appreciated.
> TIA
> Cathy
> SQL Server 7( SP4), NT4.0
|||Try restoring the backup files to disk using Veritas and then restore the
database using T-SQL executed via Query Analyzer.
RESTORE DATABASE foo FROM DISK = 'x:\foo.bak'
(syntax and examples within Books Online)
Keith
"caeriel" <caeriel@.discussions.microsoft.com> wrote in message
news:B6837C91-9566-4CB1-B3D0-73DB610E6232@.microsoft.com...
> Keith: I'm still unable to restore the master database...
> I tried starting the server as you & Hari instructed; the server started
in single user mode. However, the restore has to be issued from the Veritas
software interface. Here's the SQL Server log.
> *************************************
> ================================================== ====================
> Job server: Test
> Job name: MasterDB NoRecov 8-03
> Job started: Tuesday, August 03, 2004 at 10:08:07 AM
> Job type: Restore
> Job Log: BEX41.txt
> ================================================== ====================
> Drive and media information from media mount:
> Robotic Library Name:
> Drive Name: Quantum 1
> Slot: 0
> Media GUID: {2E9659D2-C5B5-43BF-BD2A-502B2E1054E1}
> Media Label: Test Wk1 Monday
> Overwrite Protection Time Left: None
> Append Time Left: Infinite
> ================================================== ====================
> Job Operation - Restore
> ================================================== ====================
> Restoring data to Test .
> Storage Media #1: " Media created 8/2/04 08:24:56 PM "
> Backup performed on 8/3/04 at 8:12 AM
> Backup set #6: " Full Backup "
> Restore started on 8/3/04 at 10:10:35 AM.
> An error occurred on a query to database master.
> ^ ^ ^ ^ ^
> SQL Server returned the following error message:
> RESTORE DATABASE must be used in single user mode when trying to restore
the master database.
> ^ ^ ^ ^ ^
> Restore completed on 8/3/04 at 10:13:42 AM.
> 1 item was skipped.
>
> Processed 0 bytes in 3 minutes and 7 seconds.
> Throughput rate: 0.0 MB/min
> ================================================== ====================
> Job ended: Tuesday, August 03, 2004 at 10:14:31 AM
> Job completion status: Failed
> ================================================== ====================
> ************************************************** **
> 2004-08-03 09:55:16.51 kernel Microsoft SQL Server 7.00 - 7.00.623
(Intel X86)
> Nov 27 1998 22:20:07
> Copyright (c) 1988-1998 Microsoft Corporation
> Standard Edition on Windows NT 4.0 (Build 1381: Service Pack 6)
> 2004-08-03 09:55:16.51 kernel Copyright (C) 1988-1997 Microsoft
Corporation.
> 2004-08-03 09:55:16.52 kernel All rights reserved.
> 2004-08-03 09:55:16.52 kernel Logging SQL Server messages in file
'D:\MSSQL7\log\ERRORLOG'.
> 2004-08-03 09:55:16.58 kernel initconfig: Number of user connections
limited to 32767.
> 2004-08-03 09:55:16.58 kernel SQL Server is starting at priority class
'normal'(1 CPU detected).
> 2004-08-03 09:55:16.70 kernel User Mode Scheduler configured for thread
processing
> 2004-08-03 09:55:17.96 server Directory Size: 10801
> 2004-08-03 09:55:18.05 spid1 Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks
> 2004-08-03 09:55:18.05 kernel Attempting to initialize Distributed
Transaction Coordinator.
> 2004-08-03 09:55:18.82 spid1 Failed to obtain
TransactionDispenserInterface: XACT_E_TMNOTAVAILABLE
> 2004-08-03 09:55:18.83 spid1 Warning ******************
> 2004-08-03 09:55:18.83 spid1 SQL Server started in single user mode.
Updates allowed to system catalogs.
> 2004-08-03 09:55:18.84 spid1 Warning ******************
> 2004-08-03 09:55:18.85 spid1 Starting up database 'master'.
> 2004-08-03 09:55:18.85 spid1 Opening file D:\MSSQL7\data\master.mdf.
> 2004-08-03 09:55:18.89 spid1 Opening file D:\MSSQL7\data\mastlog.ldf.
> 2004-08-03 09:55:18.99 spid1 Loading SQL Server's Unicode collation.
> 2004-08-03 09:55:19.01 spid1 Loading SQL Server's non-Unicode sort
order and character set.
> 2004-08-03 09:55:19.24 spid1 4 transactions rolled forward in database
'master' (1).
> 2004-08-03 09:55:19.25 spid1 0 transactions rolled back in database
'master' (1).
> 2004-08-03 09:55:19.35 spid1 Starting up database 'model'.
> 2004-08-03 09:55:19.36 spid1 Opening file D:\MSSQL7\DATA\model.mdf.
> 2004-08-03 09:55:19.43 spid1 Opening file D:\MSSQL7\DATA\modellog.ldf.
> 2004-08-03 09:55:19.63 spid1 Clearing tempdb database.
> 2004-08-03 09:55:19.69 spid1 Creating file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:19.87 spid1 Closing file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:19.97 spid1 Creating file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:19.99 spid1 Closing file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:20.12 spid1 Opening file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:20.14 spid1 Opening file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:21.15 spid1 Closing file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:21.25 spid1 Closing file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:21.34 spid1 Starting up database 'tempdb'.
> 2004-08-03 09:55:21.38 spid1 Opening file D:\MSSQL7\DATA\TEMPDB.MDF.
> 2004-08-03 09:55:21.41 spid1 Opening file D:\MSSQL7\DATA\TEMPLOG.LDF.
> 2004-08-03 09:55:21.69 spid1 Server name is 'AOATESTBOX'.
> 2004-08-03 09:55:21.70 kernel Using 'SQLEVN70.DLL' version '7.00.623'.
> 2004-08-03 09:55:21.71 kernel Using 'OPENDS60.DLL' version
'7.00.00.0623'.
> 2004-08-03 09:55:21.71 ods Using 'SSNMPN70.DLL' version '7.0.623' to
listen on '\\.\pipe\sql\query'.
> 2004-08-03 09:55:21.72 ods Using 'SSMSSO70.DLL' version '7.0.623' to
listen on '3180'.
> 2004-08-03 09:55:21.82 ods Using 'SSMSRP70.DLL' version '7.0.623' to
listen on 'AOATESTBOX'.
> 2004-08-03 09:55:22.68 spid5 Starting up database 'msdb'.
> 2004-08-03 09:55:22.68 spid5 Opening file D:\MSSQL7\DATA\msdbdata.mdf.
> 2004-08-03 09:55:22.70 spid6 Starting up database 'pubs'.
> 2004-08-03 09:55:22.70 spid6 Opening file D:\MSSQL7\DATA\pubs.mdf.
> 2004-08-03 09:55:22.72 spid7 Starting up database 'Northwind'.
> 2004-08-03 09:55:22.72 spid7 Opening file D:\MSSQL7\DATA\northwnd.mdf.
> 2004-08-03 09:55:22.82 spid5 Opening file D:\MSSQL7\DATA\msdblog.ldf.
> 2004-08-03 09:55:22.85 spid7 Opening file D:\MSSQL7\DATA\northwnd.ldf.
> 2004-08-03 09:55:22.87 spid6 Opening file D:\MSSQL7\DATA\pubs_log.ldf.
> 2004-08-03 09:55:23.55 spid1 Recovery complete.
> 2004-08-03 09:55:23.56 spid1 SQL Server's Unicode collation is:
> 2004-08-03 09:55:23.57 spid1 'English' (ID = 1033).
> 2004-08-03 09:55:23.57 spid1 comparison style = 196609.
> 2004-08-03 09:55:23.58 spid1 SQL Server's non-Unicode sort order is:
> 2004-08-03 09:55:23.58 spid1 'nocase_850' (ID = 42).
> 2004-08-03 09:55:23.58 spid1 SQL Server's non-Unicode character set is:
> 2004-08-03 09:55:23.58 spid1 'cp850' (ID = 2).
> 2004-08-03 09:57:00.02 spid6 Using 'xpstar.dll' version '1998.11.13' to
execute extended stored procedure 'sp_MSgetversion'.
> 2004-08-03 10:16:44.05 kernel SQL Server shutdown due to Ctrl-C or
Ctrl-Break signal.[vbcol=seagreen]
> ************************************************** *****
> Here's the Veritas log:
> ************************************************
> ************************************************
> "Keith Kratochvil" wrote:
directly[vbcol=seagreen]
Server[vbcol=seagreen]
found[vbcol=seagreen]
of[vbcol=seagreen]
C to[vbcol=seagreen]
service.[vbcol=seagreen]
other[vbcol=seagreen]
Backup[vbcol=seagreen]
things[vbcol=seagreen]
that[vbcol=seagreen]
my[vbcol=seagreen]

Can't register SQL-DMO

Hi, this is an old issue and i've searched for days. I have a vb6 app thats
worked for years on a NT4/SQL7 server using the SQL7 client. We are finally
moving out of mixed mode and upgraded the server to NT2003/SQL 2000.
I upgraded and re-compiled the vb program and installed it on the users PC,
along with the sql2000 client. I would get an error connecting to the sql
2000 server. [Microsoft][ODBC SQL Server Drver][SQL Server]You must upgrade
your SQL Enterprise Manager and SQL-DMO(SQL OLE) to SQL 2000 (SQLDMO) to
connect to this server. Error Code -2147220990
After much research I found that I needed to install/register the SQL-DMO
and found a article (326613) from Microsoft on how to create a distribution
package.
I followed the instructions and the sql-dmo package worked fine, ON some
machines (XP), but I've found that many NT2000 PC's it simply won't install
and register on. It will come back with a HResult -2147024770 failed to
register sqldmo.dll
I've got all the files in the right place, with the .rll files where they
need to be. I can't even manually register the sqldmo.dll file on these
PC's.. The really strange part is if I install the full sql2000 server onto
the PC then the program runs fine. BUT, as soon as I uninstall the server
portion it fails again. I've tried installing both the SQL-2000 client and
client tools but nothing works short of a full SQL server install, Which is
not an option!
The PC's in question are all Compaq/HP EVO's running NT2000, standard fair
stuff, nothing strange on the desktop. All have the lastest updates, patches
and hotfixes.
I know this is an old issue, But does anybody have a clue? I'd hate to
tell my boss that those folks can't run the program unless they upgrade there
PC.
Im not sure if my dev system has service pack 4 or not, I'll have to check.
As far as being compiled with the newest MSVc++ runtime linked
lib,"msvcr71.dll I am using .net 2002 so I guess not. Strange that the
microsoft article (326613) says nothing about this. as far as the rest of
your statement all those files are included and in their correct directory
structure, Per the article I used to create the distribution package.
"Andrea Montanari" wrote:

> hi,
> jcw wrote:
> what files are you "redistributing" in order to install SQL-DMO 2000?
> In my experience, I never failed providing
> ;SQL Server service pack 4 SQL-DMO object has been compiled with the newest
> Microsoft Visual C++ runtime linked library, msvcr71.dll that must be
> redistributed as well;
> ...\WINDOWS\SYSTEM\msvcr71.dll DestDir: WinSys ; sharedfile
> ; not licensed by redist.txt but available after installation of MDAC2.6
> ...\WINDOWS\SYSTEM\odbcbcp.dll; DestDir: WinSys ; sharedfile
> ; not licensed by redist.txt but available after installation of MDAC2.6
> ...\WINDOWS\SYSTEM\sqlwoa.dll ; DestDir: WinSys
> ; not licensed by redist.txt but available after installation of MDAC2.6
> ...\WINDOWS\SYSTEM\sqlwid.dll ; DestDir: WinSys
> ...\Programmi\Microsoft SQL Server\80\Tools\Binn\w95scm.dll; DestDir:
> DestinationFolder\Binn
> ...\WINDOWS\SYSTEM\sqlunirl.dll ; DestDir: WinSys
> ...\Programmi\Microsoft SQL Server\80\Tools\Binn\sqlresld.dll; DestDir:
> DestinationFolder\Binn
> ...\Programmi\Microsoft SQL Server\80\Tools\Binn\sqlsvc.dll; DestDir:
> DestinationFolder\Binn
> ; not licensed by redist.txt but available after installation of MDAC2.6
> ...\Programmi\Microsoft SQL Server\80\Tools\Binn\Resources\1033\sqlsvc.RLL;
> DestDir: DestinationFolder\Binn\Resources\1033
> ; not licensed by redist.txt but available after installation of MDAC2.6
> ...\Programmi\Microsoft SQL Server\80\Tools\Binn\Resources\1033\Sqldmo.rll;
> DestDir: DestinationFolder\Binn\Resources\1033
> ...\Programmi\Microsoft SQL Server\80\Tools\Binn\sqldmo.dll; DestDir:
> DestinationFolder\Binn ; file to be registered via regserver
> DestinationFolder can either be the installation directory of one instance
> of Microsoft SQLServer 2000, like ..\Program Files\Microsoft SQL
> Server\80\Tools, even if no istance of SQL Server has been installed, or the
> installation directory of your application, but the first one is preferred.
> Please do respect the hierarchy \Binn\Resources\1033 (where 1033 specifies
> the language), where needed, in order to grant correct functionality of
> Ole-Automation objects.
> In order to install SQL-DMO components for MSDE 2000, Microsoft Internet
> Explorer 5.5 or higher is required.
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
> -- remove DMO to reply
>
>
|||checked and I did install the SP4.

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 install SQL Server 2005 on vista..

Ok ive tried looking everywhere for a solution but i just cant find one... please help me

I need to install SQL Server 2005 on Vista, but i have issues.

I have installed IIS and its checked in the pre-installation checklist, and the only thing with an exclamation point is the OS which is to be expected.

The issue im having is that when i get to the screen to select the features/components i want to install, they are all disabled apart from "Workstation components, Books online etc..."

Where am i going wrong with this.. I know i need the services pack to install reporting services, but i cant install anything at this point.

A walkthrough or something would really help...

P.S Im running on Vista Ultimate and trying to install SQL Server 2005 Enterprise Edition

Thanks!

Robert Macnair

Perhaps this will shed some light on the problem.

VISTA –Installing SQL Server 2005
http://blogs.msdn.com/sqlexpress/archive/2006/11/15/sql-express-sp2-and-windows-vista-uac.aspx

|||

which edition of Vista u have ? I think the problem is with the edition of Vista.. it looks like SQL SErver 2005 EE is not supported...

Madhu

|||and there was me thinking Ultimate edition would be just that... ultimate . apparently not. Maybe it requires business edition..|||

SQL Server 2005 Enterprise Edition can be only installed on a *server* sku (edition) of Windows. All editions of Vista (yes, Ultimate Edition included) are Windows *clients*, therefore it doesn't allow you to install. To see the system requirements for various SQL Server 2005 editions, please refer to http://www.microsoft.com/sql/prodinfo/sysreqs/default.mspx.

Note the workstation components of SQL Server 2005 are exceptions to the above rule, and can be installed on client Windows. That's why that checkbox is not grayed out in the image you attached.

|||

This is strange, but when I installed SQL Server 2005 (not sure which edition, it came with my Professional-Level MSDN Subscription) on my Windows Vista Ultimate Edition OS, I DID have access to all the options on the installation screen, and they installed. I still have to install SP2, but I did install SP1 (once I turned off almost all my services, especially my Anti-Virus).

But I did notice that I don't have access to the Management Studio (SQL2005's version of SQL2000's Enterprise Manager). I can't find the link for it in my Start->Programs section. I still have to do some searching to see if I can find the executable or console plugin in the SQL Server 2005 installation directory, but I did have the ability to install the entire application on Vista.

If this is not supposed to happen, then this sounds like a bug in either the SQL Server 2005 installer or Windows Vista.

Anyway, just thought I would share my experience with you. I will try to keep you posted if I learn anything new or if I can't get SQL 2005 to work on my Vista.

|||

I am experiencing similar problems. I have Vista Ultimate and I was able to install Visual Studio 2005 professional with its service packs just fine, but I am unable to install SQL Server 2005. Not all, but most of the checkboxes are disabled. I thought the service packs would correct this, but no.

The reason I bought the professional edition of Visual Studio is because I needed SQL Server to do database programming and reporting services. The whole package is useless to me unless I can get SQL Server working.

|||Please see my earlier post - most likely you have SQL Server 2005 Enterprise Edition, which is not supported on Vista.|||

It maybe that SQL express was installed befor you started

Try installing from cmd prompt eg d:\setup SKUUPDATE=1

|||yup that was it. i downloaded sql server developer edition and all's well. cheers for the replies |||Using the Developer edition helped me as well....I was also stumped with the Enterprise Edition. Thanks |||I'm having that exact same issue! so I just need to install SQL dev edition? I'm trying to install enterprise...|||yeah that should work mate.

Cant install SQL Server 2005 on vista..

Ok ive tried looking everywhere for a solution but i just cant find one... please help me

I need to install SQL Server 2005 on Vista, but i have issues.

I have installed IIS and its checked in the pre-installation checklist, and the only thing with an exclamation point is the OS which is to be expected.

The issue im having is that when i get to the screen to select the features/components i want to install, they are all disabled apart from "Workstation components, Books online etc..."

Where am i going wrong with this.. I know i need the services pack to install reporting services, but i cant install anything at this point.

A walkthrough or something would really help...

P.S Im running on Vista Ultimate and trying to install SQL Server 2005 Enterprise Edition

Thanks!

Robert Macnair

Perhaps this will shed some light on the problem.

VISTA –Installing SQL Server 2005
http://blogs.msdn.com/sqlexpress/archive/2006/11/15/sql-express-sp2-and-windows-vista-uac.aspx

|||

which edition of Vista u have ? I think the problem is with the edition of Vista.. it looks like SQL SErver 2005 EE is not supported...

Madhu

|||and there was me thinking Ultimate edition would be just that... ultimate . apparently not. Maybe it requires business edition..|||

SQL Server 2005 Enterprise Edition can be only installed on a *server* sku (edition) of Windows. All editions of Vista (yes, Ultimate Edition included) are Windows *clients*, therefore it doesn't allow you to install. To see the system requirements for various SQL Server 2005 editions, please refer to http://www.microsoft.com/sql/prodinfo/sysreqs/default.mspx.

Note the workstation components of SQL Server 2005 are exceptions to the above rule, and can be installed on client Windows. That's why that checkbox is not grayed out in the image you attached.

|||

This is strange, but when I installed SQL Server 2005 (not sure which edition, it came with my Professional-Level MSDN Subscription) on my Windows Vista Ultimate Edition OS, I DID have access to all the options on the installation screen, and they installed. I still have to install SP2, but I did install SP1 (once I turned off almost all my services, especially my Anti-Virus).

But I did notice that I don't have access to the Management Studio (SQL2005's version of SQL2000's Enterprise Manager). I can't find the link for it in my Start->Programs section. I still have to do some searching to see if I can find the executable or console plugin in the SQL Server 2005 installation directory, but I did have the ability to install the entire application on Vista.

If this is not supposed to happen, then this sounds like a bug in either the SQL Server 2005 installer or Windows Vista.

Anyway, just thought I would share my experience with you. I will try to keep you posted if I learn anything new or if I can't get SQL 2005 to work on my Vista.

|||

I am experiencing similar problems. I have Vista Ultimate and I was able to install Visual Studio 2005 professional with its service packs just fine, but I am unable to install SQL Server 2005. Not all, but most of the checkboxes are disabled. I thought the service packs would correct this, but no.

The reason I bought the professional edition of Visual Studio is because I needed SQL Server to do database programming and reporting services. The whole package is useless to me unless I can get SQL Server working.

|||Please see my earlier post - most likely you have SQL Server 2005 Enterprise Edition, which is not supported on Vista.|||

It maybe that SQL express was installed befor you started

Try installing from cmd prompt eg d:\setup SKUUPDATE=1

|||yup that was it. i downloaded sql server developer edition and all's well. cheers for the replies |||Using the Developer edition helped me as well....I was also stumped with the Enterprise Edition. Thanks |||I'm having that exact same issue! so I just need to install SQL dev edition? I'm trying to install enterprise...|||yeah that should work mate.

Cant install SQL Server 2005 on vista..

Ok ive tried looking everywhere for a solution but i just cant find one... please help me

I need to install SQL Server 2005 on Vista, but i have issues.

I have installed IIS and its checked in the pre-installation checklist, and the only thing with an exclamation point is the OS which is to be expected.

The issue im having is that when i get to the screen to select the features/components i want to install, they are all disabled apart from "Workstation components, Books online etc..."

Where am i going wrong with this.. I know i need the services pack to install reporting services, but i cant install anything at this point.

A walkthrough or something would really help...

P.S Im running on Vista Ultimate and trying to install SQL Server 2005 Enterprise Edition

Thanks!

Robert Macnair

Perhaps this will shed some light on the problem.

VISTA –Installing SQL Server 2005
http://blogs.msdn.com/sqlexpress/archive/2006/11/15/sql-express-sp2-and-windows-vista-uac.aspx

|||

which edition of Vista u have ? I think the problem is with the edition of Vista.. it looks like SQL SErver 2005 EE is not supported...

Madhu

|||and there was me thinking Ultimate edition would be just that... ultimate . apparently not. Maybe it requires business edition..|||

SQL Server 2005 Enterprise Edition can be only installed on a *server* sku (edition) of Windows. All editions of Vista (yes, Ultimate Edition included) are Windows *clients*, therefore it doesn't allow you to install. To see the system requirements for various SQL Server 2005 editions, please refer to http://www.microsoft.com/sql/prodinfo/sysreqs/default.mspx.

Note the workstation components of SQL Server 2005 are exceptions to the above rule, and can be installed on client Windows. That's why that checkbox is not grayed out in the image you attached.

|||

This is strange, but when I installed SQL Server 2005 (not sure which edition, it came with my Professional-Level MSDN Subscription) on my Windows Vista Ultimate Edition OS, I DID have access to all the options on the installation screen, and they installed. I still have to install SP2, but I did install SP1 (once I turned off almost all my services, especially my Anti-Virus).

But I did notice that I don't have access to the Management Studio (SQL2005's version of SQL2000's Enterprise Manager). I can't find the link for it in my Start->Programs section. I still have to do some searching to see if I can find the executable or console plugin in the SQL Server 2005 installation directory, but I did have the ability to install the entire application on Vista.

If this is not supposed to happen, then this sounds like a bug in either the SQL Server 2005 installer or Windows Vista.

Anyway, just thought I would share my experience with you. I will try to keep you posted if I learn anything new or if I can't get SQL 2005 to work on my Vista.

|||

I am experiencing similar problems. I have Vista Ultimate and I was able to install Visual Studio 2005 professional with its service packs just fine, but I am unable to install SQL Server 2005. Not all, but most of the checkboxes are disabled. I thought the service packs would correct this, but no.

The reason I bought the professional edition of Visual Studio is because I needed SQL Server to do database programming and reporting services. The whole package is useless to me unless I can get SQL Server working.

|||Please see my earlier post - most likely you have SQL Server 2005 Enterprise Edition, which is not supported on Vista.|||

It maybe that SQL express was installed befor you started

Try installing from cmd prompt eg d:\setup SKUUPDATE=1

|||yup that was it. i downloaded sql server developer edition and all's well. cheers for the replies |||Using the Developer edition helped me as well....I was also stumped with the Enterprise Edition. Thanks |||I'm having that exact same issue! so I just need to install SQL dev edition? I'm trying to install enterprise...|||yeah that should work mate.

Cant install SQL Server 2005 on vista..

Ok ive tried looking everywhere for a solution but i just cant find one... please help me

I need to install SQL Server 2005 on Vista, but i have issues.

I have installed IIS and its checked in the pre-installation checklist, and the only thing with an exclamation point is the OS which is to be expected.

The issue im having is that when i get to the screen to select the features/components i want to install, they are all disabled apart from "Workstation components, Books online etc..."

Where am i going wrong with this.. I know i need the services pack to install reporting services, but i cant install anything at this point.

A walkthrough or something would really help...

P.S Im running on Vista Ultimate and trying to install SQL Server 2005 Enterprise Edition

Thanks!

Robert Macnair

Perhaps this will shed some light on the problem.

VISTA –Installing SQL Server 2005
http://blogs.msdn.com/sqlexpress/archive/2006/11/15/sql-express-sp2-and-windows-vista-uac.aspx

|||

which edition of Vista u have ? I think the problem is with the edition of Vista.. it looks like SQL SErver 2005 EE is not supported...

Madhu

|||and there was me thinking Ultimate edition would be just that... ultimate . apparently not. Maybe it requires business edition..|||

SQL Server 2005 Enterprise Edition can be only installed on a *server* sku (edition) of Windows. All editions of Vista (yes, Ultimate Edition included) are Windows *clients*, therefore it doesn't allow you to install. To see the system requirements for various SQL Server 2005 editions, please refer to http://www.microsoft.com/sql/prodinfo/sysreqs/default.mspx.

Note the workstation components of SQL Server 2005 are exceptions to the above rule, and can be installed on client Windows. That's why that checkbox is not grayed out in the image you attached.

|||

This is strange, but when I installed SQL Server 2005 (not sure which edition, it came with my Professional-Level MSDN Subscription) on my Windows Vista Ultimate Edition OS, I DID have access to all the options on the installation screen, and they installed. I still have to install SP2, but I did install SP1 (once I turned off almost all my services, especially my Anti-Virus).

But I did notice that I don't have access to the Management Studio (SQL2005's version of SQL2000's Enterprise Manager). I can't find the link for it in my Start->Programs section. I still have to do some searching to see if I can find the executable or console plugin in the SQL Server 2005 installation directory, but I did have the ability to install the entire application on Vista.

If this is not supposed to happen, then this sounds like a bug in either the SQL Server 2005 installer or Windows Vista.

Anyway, just thought I would share my experience with you. I will try to keep you posted if I learn anything new or if I can't get SQL 2005 to work on my Vista.

|||

I am experiencing similar problems. I have Vista Ultimate and I was able to install Visual Studio 2005 professional with its service packs just fine, but I am unable to install SQL Server 2005. Not all, but most of the checkboxes are disabled. I thought the service packs would correct this, but no.

The reason I bought the professional edition of Visual Studio is because I needed SQL Server to do database programming and reporting services. The whole package is useless to me unless I can get SQL Server working.

|||Please see my earlier post - most likely you have SQL Server 2005 Enterprise Edition, which is not supported on Vista.|||

It maybe that SQL express was installed befor you started

Try installing from cmd prompt eg d:\setup SKUUPDATE=1

|||yup that was it. i downloaded sql server developer edition and all's well. cheers for the replies |||Using the Developer edition helped me as well....I was also stumped with the Enterprise Edition. Thanks |||I'm having that exact same issue! so I just need to install SQL dev edition? I'm trying to install enterprise...|||yeah that should work mate.

Cant install SQL Server 2005 on vista..

Ok ive tried looking everywhere for a solution but i just cant find one... please help me

I need to install SQL Server 2005 on Vista, but i have issues.

I have installed IIS and its checked in the pre-installation checklist, and the only thing with an exclamation point is the OS which is to be expected.

The issue im having is that when i get to the screen to select the features/components i want to install, they are all disabled apart from "Workstation components, Books online etc..."

Where am i going wrong with this.. I know i need the services pack to install reporting services, but i cant install anything at this point.

A walkthrough or something would really help...

P.S Im running on Vista Ultimate and trying to install SQL Server 2005 Enterprise Edition

Thanks!

Robert Macnair

Perhaps this will shed some light on the problem.

VISTA –Installing SQL Server 2005
http://blogs.msdn.com/sqlexpress/archive/2006/11/15/sql-express-sp2-and-windows-vista-uac.aspx

|||

which edition of Vista u have ? I think the problem is with the edition of Vista.. it looks like SQL SErver 2005 EE is not supported...

Madhu

|||and there was me thinking Ultimate edition would be just that... ultimate . apparently not. Maybe it requires business edition..|||

SQL Server 2005 Enterprise Edition can be only installed on a *server* sku (edition) of Windows. All editions of Vista (yes, Ultimate Edition included) are Windows *clients*, therefore it doesn't allow you to install. To see the system requirements for various SQL Server 2005 editions, please refer to http://www.microsoft.com/sql/prodinfo/sysreqs/default.mspx.

Note the workstation components of SQL Server 2005 are exceptions to the above rule, and can be installed on client Windows. That's why that checkbox is not grayed out in the image you attached.

|||

This is strange, but when I installed SQL Server 2005 (not sure which edition, it came with my Professional-Level MSDN Subscription) on my Windows Vista Ultimate Edition OS, I DID have access to all the options on the installation screen, and they installed. I still have to install SP2, but I did install SP1 (once I turned off almost all my services, especially my Anti-Virus).

But I did notice that I don't have access to the Management Studio (SQL2005's version of SQL2000's Enterprise Manager). I can't find the link for it in my Start->Programs section. I still have to do some searching to see if I can find the executable or console plugin in the SQL Server 2005 installation directory, but I did have the ability to install the entire application on Vista.

If this is not supposed to happen, then this sounds like a bug in either the SQL Server 2005 installer or Windows Vista.

Anyway, just thought I would share my experience with you. I will try to keep you posted if I learn anything new or if I can't get SQL 2005 to work on my Vista.

|||

I am experiencing similar problems. I have Vista Ultimate and I was able to install Visual Studio 2005 professional with its service packs just fine, but I am unable to install SQL Server 2005. Not all, but most of the checkboxes are disabled. I thought the service packs would correct this, but no.

The reason I bought the professional edition of Visual Studio is because I needed SQL Server to do database programming and reporting services. The whole package is useless to me unless I can get SQL Server working.

|||Please see my earlier post - most likely you have SQL Server 2005 Enterprise Edition, which is not supported on Vista.|||

It maybe that SQL express was installed befor you started

Try installing from cmd prompt eg d:\setup SKUUPDATE=1

|||yup that was it. i downloaded sql server developer edition and all's well. cheers for the replies |||Using the Developer edition helped me as well....I was also stumped with the Enterprise Edition. Thanks |||I'm having that exact same issue! so I just need to install SQL dev edition? I'm trying to install enterprise...|||yeah that should work mate.

Can't install SQL 2005 server components

I've been trying to install SQL 2005 on my development laptop. So far
I've been able to install all client components, but the setup program
never gives me the option to install the server components. I first
tried with the Enterprise edition. I then found out that Enterprise
doesn't run on Win XP Pro SP2. So I uninstalled everything and tried
again with Developer. In the beginning of the setup process, I get 14
successful checks, zero errors, zero warnings. When I then get into the
feature selection screen, all it shows me is "Client Components" and
"Documentation, Samples and Sample Databases".
Nowhere can I get to the server components. I've tried uninstalling,
reinstalling, with VS2005, without VS2005, but to no avail. Can anyone
help me?
Thanks!
Dirk
How do you start the setup? There's both a client setup and a server setup. I don't have the DVD
here, so safest bet it to use what autorun uses.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<dcdirk@.gmail.com> wrote in message news:1131557740.758696.14810@.o13g2000cwo.googlegro ups.com...
> I've been trying to install SQL 2005 on my development laptop. So far
> I've been able to install all client components, but the setup program
> never gives me the option to install the server components. I first
> tried with the Enterprise edition. I then found out that Enterprise
> doesn't run on Win XP Pro SP2. So I uninstalled everything and tried
> again with Developer. In the beginning of the setup process, I get 14
> successful checks, zero errors, zero warnings. When I then get into the
> feature selection screen, all it shows me is "Client Components" and
> "Documentation, Samples and Sample Databases".
> Nowhere can I get to the server components. I've tried uninstalling,
> reinstalling, with VS2005, without VS2005, but to no avail. Can anyone
> help me?
> Thanks!
> Dirk
>
|||Hi Tibor,
I loaded the files from the downloaded ISO files (CD1 and CD2) into a
directory on my harddisk. I simply run the setup program. I did follow
your suggestion, though, and ran splash.hta, which is what would get
run through autorun. The options I have there under "Install" are: 1)
Tools, Books Online, and samples only 2) Run the SQL Native Client
Installation Wizard
SQL Native Client Install wizzard reinstalls, but still no server
components...
Dirk
|||OK, it looks like I found what the problem was. I burned the ISO images
to CD instead of to the harddrive, and now the server components
actually show up during install...