Another Suspect ?

Hi
My database went into suspect mode. I made some space on the drives after I
was unable to add additional log files
sp_add_log_file_recover_suspect_db nestledb_jp_coremart_v1, logfile2,
'D:\MSSQL\Data\db1_logfile2.ldf',
'100MB'
Server: Msg 9004, Level 23, State 1, Line 1
An error occurred while processing the log for database
'NestleDB_JP_CoreMart_V1'.
ALTER DATABASE nestledb_jp_coremart_v1 ADD LOG FILE(NAME = [logfile2],
FILENAME = 'D:\MSSQL\Data\db1_logfile2.ldf', SIZE = 100MB )
Connection Broken
So that didn't work so only way was to make space. So I made space on the
drive and ran the proc and restarted the lot. Nothing.
Thanks for helpHi,
If you have adequate space in hard disk Can you reset the status of the
database using sp_resetstatus system procedure and stop and start the SQL
server service and
see what happends. If the database is still marked suspect please check the
SQl server error log and post us the error.
Incase if the LDF is giving issues, you can start the database by emergency
mode. Update the status column of the suspect database in sysdatabases table
to 32768.
After that you can create a newe database and use DTS to transfer data and
other objects.
Thanks
Hari
SQL Server
"Mal .mullerjannie@.hotmail.com>" <<removethis> wrote in message
news:3BAA266D-93F2-4268-B764-280409FD03E9@.microsoft.com...
> Hi
> My database went into suspect mode. I made some space on the drives after
> I
> was unable to add additional log files
> sp_add_log_file_recover_suspect_db nestledb_jp_coremart_v1, logfile2,
> 'D:\MSSQL\Data\db1_logfile2.ldf',
> '100MB'
> Server: Msg 9004, Level 23, State 1, Line 1
> An error occurred while processing the log for database
> 'NestleDB_JP_CoreMart_V1'.
> ALTER DATABASE nestledb_jp_coremart_v1 ADD LOG FILE(NAME = [logfile2],
> FILENAME = 'D:\MSSQL\Data\db1_logfile2.ldf', SIZE = 100MB )
> Connection Broken
> So that didn't work so only way was to make space. So I made space on the
> drive and ran the proc and restarted the lot. Nothing.
> Thanks for help
>|||The error log, seems there's a bit of a problem :)
I'll have to try this emergenvy startup.
Thanks for help so far
2005-04-01 16:16:24.21 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
2005-04-01 16:16:24.21 server Copyright (C) 1988-2002 Microsoft
Corporation.
2005-04-01 16:16:24.21 server All rights reserved.
2005-04-01 16:16:24.21 server Server Process ID is 1788.
2005-04-01 16:16:24.21 server Logging SQL Server messages in file
'e:\MSSQL\log\ERRORLOG'.
2005-04-01 16:16:24.22 server SQL Server is starting at priority class
'normal'(4 CPUs detected).
2005-04-01 16:16:24.30 server SQL Server configured for thread mode
processing.
2005-04-01 16:16:24.30 server Using dynamic lock allocation. [2500] Lock
Blocks, [5000] Lock Owner Blocks.
2005-04-01 16:16:24.32 server Attempting to initialize Distributed
Transaction Coordinator.
2005-04-01 16:16:26.36 spid3 Starting up database 'master'.
2005-04-01 16:16:26.49 server Using 'SSNETLIB.DLL' version '8.0.760'.
2005-04-01 16:16:26.49 spid5 Starting up database 'model'.
2005-04-01 16:16:26.49 spid3 Server name is 'DEVINCI'.
2005-04-01 16:16:26.49 spid8 Starting up database 'msdb'.
2005-04-01 16:16:26.49 spid9 Starting up database 'pubs'.
2005-04-01 16:16:26.49 spid10 Starting up database 'Northwind'.
2005-04-01 16:16:26.49 spid11 Starting up database
'Nestle_JP_WorkspaceDB_V1'.
2005-04-01 16:16:26.49 spid13 Starting up database
'NestleDB_JP_WebMart_V1'.
2005-04-01 16:16:26.49 spid15 Starting up database
'NestleDB_JP_Update_V1_TN'.
2005-04-01 16:16:26.49 spid14 Starting up database
'NestleDB_JP_WebMart_V1_TN_V1'.
2005-04-01 16:16:26.49 spid16 Starting up database 'NestleDB_JP_Update_V1
'.
2005-04-01 16:16:26.49 spid17 Starting up database
'NestleDB_JP_CoreMart_V1'.
2005-04-01 16:16:26.49 spid12 Starting up database
'Nestle_JP_WorkspaceDB_V2'.
2005-04-01 16:16:26.55 spid12 Analysis of database
'Nestle_JP_WorkspaceDB_V2' (8) is 100% complete (approximately 0 more second
s)
2005-04-01 16:16:26.60 spid13 Analysis of database
'NestleDB_JP_WebMart_V1' (10) is 100% complete (approximately 0 more seconds
)
2005-04-01 16:16:26.60 spid16 Analysis of database
'NestleDB_JP_Update_V1' (17) is 100% complete (approximately 0 more seconds)
2005-04-01 16:16:26.61 spid5 Clearing tempdb database.
2005-04-01 16:16:26.63 spid11 Analysis of database
'Nestle_JP_WorkspaceDB_V1' (7) is 100% complete (approximately 0 more second
s)
2005-04-01 16:16:26.72 server SQL server listening on 192.33.20.218: 1433
.
2005-04-01 16:16:26.72 server SQL server listening on 192.168.234.235:
1433.
2005-04-01 16:16:26.72 server SQL server listening on 127.0.0.1: 1433.
2005-04-01 16:16:26.82 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2005-04-01 16:16:26.82 server SQL Server is ready for client connections
2005-04-01 16:16:27.03 spid5 Starting up database 'tempdb'.
2005-04-01 16:16:27.08 spid5 Analysis of database 'tempdb' (2) is 100%
complete (approximately 0 more seconds)
2005-04-01 16:16:29.47 spid15 Analysis of database
'NestleDB_JP_Update_V1_TN' (15) is 100% complete (approximately 0 more
seconds)
2005-04-01 16:16:32.13 spid17 Analysis of database
'NestleDB_JP_CoreMart_V1' (18) is 0% complete (approximately 56 more seconds
)
2005-04-01 16:16:33.46 spid17 Error: 9004, Severity: 23, State: 1
2005-04-01 16:16:33.46 spid17 An error occurred while processing the log
for database 'NestleDB_JP_CoreMart_V1'..
2005-04-01 16:16:33.47 spid17 Error: 3414, Severity: 21, State: 1
2005-04-01 16:16:33.47 spid17 Database 'NestleDB_JP_CoreMart_V1'
(database ID 18) could not recover. Contact Technical Support..
2005-04-01 16:16:33.49 spid3 Recovery complete.
2005-04-01 16:16:33.50 spid3 SQL global counter collection task is
created.
2005-04-01 16:16:34.10 spid51 Using 'xpsqlbot.dll' version '2000.80.194'
to execute extended stored procedure 'xp_qv'.
2005-04-01 16:16:36.36 spid1 Warning: unable to allocate 'min server
memory' of 3011MB.
"Hari Pra" wrote:

> Hi,
> If you have adequate space in hard disk Can you reset the status of the
> database using sp_resetstatus system procedure and stop and start the SQL
> server service and
> see what happends. If the database is still marked suspect please check th
e
> SQl server error log and post us the error.
> Incase if the LDF is giving issues, you can start the database by emergenc
y
> mode. Update the status column of the suspect database in sysdatabases tab
le
> to 32768.
> After that you can create a newe database and use DTS to transfer data and
> other objects.
>
> Thanks
> Hari
> SQL Server
> "Mal .mullerjannie@.hotmail.com>" <<removethis> wrote in message
> news:3BAA266D-93F2-4268-B764-280409FD03E9@.microsoft.com...
>
>|||Mwuhahaha
I love SQL :P
So problem solved...
What was the problem ...
Some clever person set the transaction log size to a specific limit and "do
not grow automatically" thus even though I did make space it didn't help wit
h
the recovery since the file couldn't grow. I have no idea why I couldn't add
an additional log file though.
So as you said I changed it to emergency mode, fixed the automatically grow
log. Set status back to suspect and then did the restart and it recovered
correctly.
One thing that's not usefull is the fact that when you go into EM you can't
see filegroups and database setttings due to suspect mode. This is a pain
cause the moment I could see that the file didn't grow automatically I could
fix the problem.
Why do SQL disable the properties for viewing once it goes into suspect ?
How do these settings affect data ? assuming data integrity is the ONLY
reason why SQL change mode to suspect to start off with .
Thanks for help.
:)
"Mal" wrote:
> The error log, seems there's a bit of a problem :)
> I'll have to try this emergenvy startup.
> Thanks for help so far
> 2005-04-01 16:16:24.21 server Microsoft SQL Server 2000 - 8.00.760
> (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
> 2005-04-01 16:16:24.21 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2005-04-01 16:16:24.21 server All rights reserved.
> 2005-04-01 16:16:24.21 server Server Process ID is 1788.
> 2005-04-01 16:16:24.21 server Logging SQL Server messages in file
> 'e:\MSSQL\log\ERRORLOG'.
> 2005-04-01 16:16:24.22 server SQL Server is starting at priority class
> 'normal'(4 CPUs detected).
> 2005-04-01 16:16:24.30 server SQL Server configured for thread mode
> processing.
> 2005-04-01 16:16:24.30 server Using dynamic lock allocation. [2500] Loc
k
> Blocks, [5000] Lock Owner Blocks.
> 2005-04-01 16:16:24.32 server Attempting to initialize Distributed
> Transaction Coordinator.
> 2005-04-01 16:16:26.36 spid3 Starting up database 'master'.
> 2005-04-01 16:16:26.49 server Using 'SSNETLIB.DLL' version '8.0.760'.
> 2005-04-01 16:16:26.49 spid5 Starting up database 'model'.
> 2005-04-01 16:16:26.49 spid3 Server name is 'DEVINCI'.
> 2005-04-01 16:16:26.49 spid8 Starting up database 'msdb'.
> 2005-04-01 16:16:26.49 spid9 Starting up database 'pubs'.
> 2005-04-01 16:16:26.49 spid10 Starting up database 'Northwind'.
> 2005-04-01 16:16:26.49 spid11 Starting up database
> 'Nestle_JP_WorkspaceDB_V1'.
> 2005-04-01 16:16:26.49 spid13 Starting up database
> 'NestleDB_JP_WebMart_V1'.
> 2005-04-01 16:16:26.49 spid15 Starting up database
> 'NestleDB_JP_Update_V1_TN'.
> 2005-04-01 16:16:26.49 spid14 Starting up database
> 'NestleDB_JP_WebMart_V1_TN_V1'.
> 2005-04-01 16:16:26.49 spid16 Starting up database 'NestleDB_JP_Update_
V1'.
> 2005-04-01 16:16:26.49 spid17 Starting up database
> 'NestleDB_JP_CoreMart_V1'.
> 2005-04-01 16:16:26.49 spid12 Starting up database
> 'Nestle_JP_WorkspaceDB_V2'.
> 2005-04-01 16:16:26.55 spid12 Analysis of database
> 'Nestle_JP_WorkspaceDB_V2' (8) is 100% complete (approximately 0 more seco
nds)
> 2005-04-01 16:16:26.60 spid13 Analysis of database
> 'NestleDB_JP_WebMart_V1' (10) is 100% complete (approximately 0 more secon
ds)
> 2005-04-01 16:16:26.60 spid16 Analysis of database
> 'NestleDB_JP_Update_V1' (17) is 100% complete (approximately 0 more second
s)
> 2005-04-01 16:16:26.61 spid5 Clearing tempdb database.
> 2005-04-01 16:16:26.63 spid11 Analysis of database
> 'Nestle_JP_WorkspaceDB_V1' (7) is 100% complete (approximately 0 more seco
nds)
> 2005-04-01 16:16:26.72 server SQL server listening on 192.33.20.218: 14
33.
> 2005-04-01 16:16:26.72 server SQL server listening on 192.168.234.235:
> 1433.
> 2005-04-01 16:16:26.72 server SQL server listening on 127.0.0.1: 1433.
> 2005-04-01 16:16:26.82 server SQL server listening on TCP, Shared Memor
y,
> Named Pipes.
> 2005-04-01 16:16:26.82 server SQL Server is ready for client connection
s
> 2005-04-01 16:16:27.03 spid5 Starting up database 'tempdb'.
> 2005-04-01 16:16:27.08 spid5 Analysis of database 'tempdb' (2) is 100%
> complete (approximately 0 more seconds)
> 2005-04-01 16:16:29.47 spid15 Analysis of database
> 'NestleDB_JP_Update_V1_TN' (15) is 100% complete (approximately 0 more
> seconds)
> 2005-04-01 16:16:32.13 spid17 Analysis of database
> 'NestleDB_JP_CoreMart_V1' (18) is 0% complete (approximately 56 more secon
ds)
> 2005-04-01 16:16:33.46 spid17 Error: 9004, Severity: 23, State: 1
> 2005-04-01 16:16:33.46 spid17 An error occurred while processing the lo
g
> for database 'NestleDB_JP_CoreMart_V1'..
> 2005-04-01 16:16:33.47 spid17 Error: 3414, Severity: 21, State: 1
> 2005-04-01 16:16:33.47 spid17 Database 'NestleDB_JP_CoreMart_V1'
> (database ID 18) could not recover. Contact Technical Support..
> 2005-04-01 16:16:33.49 spid3 Recovery complete.
> 2005-04-01 16:16:33.50 spid3 SQL global counter collection task is
> created.
> 2005-04-01 16:16:34.10 spid51 Using 'xpsqlbot.dll' version '2000.80.194
'
> to execute extended stored procedure 'xp_qv'.
> 2005-04-01 16:16:36.36 spid1 Warning: unable to allocate 'min server
> memory' of 3011MB.
>
> "Hari Pra" wrote:
>

Annotations in design mode?

Is there any way to persist Annotations in design mode? I'm considering using them to keep track of measure-group specific state, but I'm worried that every time I re-deploy my cube, I'll lose this info.

Does anyone have experience using Annotations? Are they only exposed via the AMO OM?

In design mode, you can switch to raw XMLA code view by right clicking on the object. You can select "view code" and you'll see XML representation of the object.

You got to be careful modifying the XML directly such that if something goes wrong, you might loose consistency of your object. But on the other hand XML representation gives you power to access any property (such as annotations ) directly without UI.

Again. Be careful with using raw XML code view, but if you feel comfortable with modifying XML, adding new tags you should be able to add annotations to pretty much any object in your database.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||A collegue and I are looking at possibly adding this feature to BIDS through an open source project we are working on at http://www.codeproject.com/BIDSHelper unfortuntately this is not one of the features we have in the pipeline for the first release, but it is one of the things we have on our list of possible features.|||The BIDS helpers look pretty cool, thanks Darren.|||

The ability to edit annotations is finally coded in the BIDS Helper project. See:

http://www.codeplex.com/bidshelper/Wiki/View.aspx?title=Show%20Extra%20Properties&referringTitle=Home

Hope that's helpful.

Annotations in design mode?

Is there any way to persist Annotations in design mode? I'm considering using them to keep track of measure-group specific state, but I'm worried that every time I re-deploy my cube, I'll lose this info.

Does anyone have experience using Annotations? Are they only exposed via the AMO OM?

In design mode, you can switch to raw XMLA code view by right clicking on the object. You can select "view code" and you'll see XML representation of the object.

You got to be careful modifying the XML directly such that if something goes wrong, you might loose consistency of your object. But on the other hand XML representation gives you power to access any property (such as annotations ) directly without UI.

Again. Be careful with using raw XML code view, but if you feel comfortable with modifying XML, adding new tags you should be able to add annotations to pretty much any object in your database.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||A collegue and I are looking at possibly adding this feature to BIDS through an open source project we are working on at http://www.codeproject.com/BIDSHelper unfortuntately this is not one of the features we have in the pipeline for the first release, but it is one of the things we have on our list of possible features.|||The BIDS helpers look pretty cool, thanks Darren.|||

The ability to edit annotations is finally coded in the BIDS Helper project. See:

http://www.codeplex.com/bidshelper/Wiki/View.aspx?title=Show%20Extra%20Properties&referringTitle=Home

Hope that's helpful.

Annotated Mapping Schema

I have a stored procedure that uses the FOR XML EXPLICIT mode to return an xml view of my data. I then insert this xml into another table.
Instead of writing complicated T-SQL with the FOR XML EXPLICIT mode I'd like to use an xsd schema, however I can't find examples that let you apply the transformation in a stored procedure / test it in Query Analyzer. All the examples I've found involve m
apping the schema in the URL or using a SqlXmlCommand object.
Any help would be very much appreciated!
Cheers,
Paul
Mapping Schemas are a client-side technology - actually, they just generate
FOR XML EXPLICIT statements on the server (you can see this by running a
trace when retrieving data with a schema). As such, there's no way to
reference them from within a T-SQL sproc. Sorry!
--
Graeme Malcolm
Principal Technologist
Content Master Ltd.
www.contentmaster.com
www.microsoft.com/mspress/books/6137.asp
"Paul Bibby" <Paul Bibby@.discussions.microsoft.com> wrote in message
news:4B7E0882-5EED-4A7F-987D-125262683276@.microsoft.com...
I have a stored procedure that uses the FOR XML EXPLICIT mode to return an
xml view of my data. I then insert this xml into another table.
Instead of writing complicated T-SQL with the FOR XML EXPLICIT mode I'd like
to use an xsd schema, however I can't find examples that let you apply the
transformation in a stored procedure / test it in Query Analyzer. All the
examples I've found involve mapping the schema in the URL or using a
SqlXmlCommand object.
Any help would be very much appreciated!
Cheers,
Paul

And here is part of the installation log...

I get to the point of starting the services and receive the following message after about 4 minutes of trying to start. I tried in Mixed Mode and Windows Authentication Mode. Message:

TITLE: Microsoft SQL Server 2005 Setup

The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=setup.rll&EvtID=29503&EvtType=sqlsetuplib%5cservice.cpp%40Do_sqlScript%40sqls%3a%3aService%3a%3aWaitForServiceState%40x41d

BUTTONS:

&Retry
Cancel

YOu need do have a look in the WIndows event log or in the log files of SQL Server mentioned. There is a problem starting the service, the message that you provided is just a generic one which doesn′t tell the specific error.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||I can find nothing useful in the Windows event log and I guess I do not understand where the sql server log files are.|||For me its located in here:

C:\Program Files\Microsoft SQL Server\MSSQL.4\MSSQL\LOG

Could be something different for you depending on your installation.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||

here is the log contents of the last attempted installation and of course it timed out while trying to start the service:

2006-05-28 07:37:06.92 Server Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86)

Apr 14 2006 01:12:25

Copyright (c) 1988-2005 Microsoft Corporation

Express Edition with Advanced Services on Windows NT 5.1 (Build 2600: Service Pack 2)

2006-05-28 07:37:06.92 Server (c) 2005 Microsoft Corporation.

2006-05-28 07:37:06.92 Server All rights reserved.

2006-05-28 07:37:06.92 Server Server process ID is 4776.

2006-05-28 07:37:06.92 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.

2006-05-28 07:37:06.94 Server Registry startup parameters:

2006-05-28 07:37:06.94 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf

2006-05-28 07:37:06.94 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG

2006-05-28 07:37:06.94 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf

2006-05-28 07:37:06.94 Server Command Line Startup Parameters:

2006-05-28 07:37:06.95 Server -m SqlSetup

2006-05-28 07:37:06.95 Server SqlSetup

2006-05-28 07:37:06.95 Server -Q

2006-05-28 07:37:06.95 Server -q SQL_Latin1_General_CP1_CI_AS

2006-05-28 07:37:06.95 Server -T 4022

2006-05-28 07:37:06.95 Server -T 3659

2006-05-28 07:37:06.95 Server -T 3610

2006-05-28 07:37:06.95 Server -T 4010

2006-05-28 07:37:06.98 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

2006-05-28 07:37:06.98 Server Detected 1 CPUs. This is an informational message; no user action is required.

2006-05-28 07:40:49.72 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.

2006-05-28 07:40:50.88 Server Database Mirroring Transport is disabled in the endpoint configuration.

2006-05-28 07:59:24.50 Server Service control: stop before startup

|||

Thanks.....

Property(S): DatabaseReplRes.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 = C:\Program Files\Common Files\Microsoft Shared\Database Replication\Resources\
Property(S): DatabaseReplRes1033.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 = C:\Program Files\Common Files\Microsoft Shared\Database Replication\Resources\1033\
Property(S): SqlVerComBin.8B75390F_DF2F_4C2C_92F5_9B83F3B36340 = C:\Program Files\Microsoft SQL Server\90\COM\
Property(S): Ver.8B75390F_DF2F_4C2C_92F5_9B83F3B36340 = C:\Program Files\Microsoft SQL Server\90\
Property(S): SqlVerComBin.889BED4C_E3F4_4943_956C_6FFD882F721F = C:\Program Files\Microsoft SQL Server\90\COM\
Property(S): Ver.889BED4C_E3F4_4943_956C_6FFD882F721F = C:\Program Files\Microsoft SQL Server\90\
Property(S): SqlVerComBin.CC4DBEA7_CD8B_4AAE_A10F_657CBA390BD6 = C:\Program Files\Microsoft SQL Server\90\COM\
Property(S): Ver.CC4DBEA7_CD8B_4AAE_A10F_657CBA390BD6 = C:\Program Files\Microsoft SQL Server\90\
Property(S): SqlVerComBinRes.CC4DBEA7_CD8B_4AAE_A10F_657CBA390BD6 = C:\Program Files\Microsoft SQL Server\90\COM\Resources\
Property(S): SqlVerComBinRes1033.CC4DBEA7_CD8B_4AAE_A10F_657CBA390BD6 = C:\Program Files\Microsoft SQL Server\90\COM\Resources\1033\
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$SQLEXPRESS
Property(S): SqlActionManaged = 3
Property(S): SqlNamedInstance = 1
Property(S): SqlStateManaged = 2
Property(S): RSVirtualDirectoryManager = Reports$SQLEXPRESS
Property(S): SOURCEDIR = d:\69a81902561ca8c7a8df\Setup\
Property(S): SourcedirProduct = {2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}
Property(S): InstallNgenTicks = 110000
Property(S): SQLBROWSERSCMACCOUNT = NT AUTHORITY\NetworkService
Property(S): SQLSCMACCOUNT = NT AUTHORITY\NetworkService
Property(S): DebugClsid.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616 = {84AFA01D-0112-4F29-990C-7A3EECC00498}
Property(S): ProductToBeRegistered = 1
MSI (s) (EC:1C) [08:37:27:207]: Note: 1: 1708
MSI (s) (EC:1C) [08:37:27:207]: Product: Microsoft SQL Server 2005 Express Edition -- Installation failed.

MSI (s) (EC:1C) [08:37:27:227]: Cleaning up uninstalled install packages, if any exist
MSI (s) (EC:1C) [08:37:27:227]: MainEngineThread is returning 1603
MSI (s) (EC:5C) [08:37:27:337]: Destroying RemoteAPI object.
MSI (s) (EC:D8) [08:37:27:337]: Custom Action Manager thread ending.
=== Logging stopped: 5/28/2006 8:37:27 ===
MSI (c) (78:AC) [08:37:27:377]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (78:AC) [08:37:27:377]: MainEngineThread is returning 1603
=== Verbose logging stopped: 5/28/2006 8:37:27 ===

|||What service account are you using for the service. It could be that the service account used doesn′t have the appropiate permissions to start up SQL Server. Change that (e.g. to Local System) and see if a manual startup comes up successfull.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

Analysis Services on the web problems

Hi,

I basically have 2 problems:

1]I am on a client Machine (Win2000 client).This is within the firewall. My SQL Server2000(Mixed mode authentication,Enterprise Edition) and Analysis server are on a Windows 2000 Advnaced Server running with IIS 5.0.This server is outside the firewall. I also have Analysis services installed on machine. I wanted to create a cube on my client machine using the SQL Server 2000 on the machine outsided the firewall.So I did the following.
[a]Created a system DSN , say TRIALDSN, on my client that points to the SQL server,with 'sa' and password as 'admin'.It worked.
[b]Then I went to Analysis services on my client, created a new
Database, and a new Data Source with the DSN name as TRIALDSN.This worked too.And THEN, I right clicked on the Cube directory and said New Cube|Editor. I am getting the message .."Connection to the 'servername-databasename' data source failed.Error:Login failed for user 'sa'.Do you want to retry? with 'Yes' and 'No' options. Can anyone help me with this error....
2]With the same setup as above, I am trying to view the cubes on the server from my client PC. I am stuck with a problem here too. This is what is my requirement.
I need a html/asp page on the server with the cube data,that a user can access from a client machine on the internet and perform drill-downs and anything else he wants. So, this is what I tried out.
On the server outside the firewall: Got the cubes onto Excel.Here I selected the Analysis Server radio button, giving the Analysis server name as the servname(that is the name of the same machine),say "ABC01". I did (and tried without too) give the username and password for the http connections.Got the data onto excel.Then I did a 'Save As Web Page' and got the excel as an html, with all the excel features still retained (although the 3D effects of the charts were lost). I then copied this html file, say, EXAMPLE.htm to the C:\inetpub\wwroot along with the msolap.asp file.
I opened the browser and gave the url for this html and everything was fine.
By the way the IIS settings are as follows:
Integrated Windows Authentication checked
Changed the default IUSR_machinename to Administrator

On the client within the firewall:Opened the browser and typed in the url as follows:
http://IP address of the server/EXAMPLE.htm
I am getting the error "The Pivot Table List 'PivotTable2' could not connect to the data source "cubename".For information about the data source, consult the creator of the file.
0x80040e4d: The operation requested failed due to security problems - the user could not be authenticated.
Some how, the data source property with the value 'ABC01' in the connection string of the html is giving the problem. What should I do?? But the whole point is, I am able to access normal html pages on the server from the client, that is , html pages that do not connect to cubes.
I am desparate for help. Thanks in advance.

AshCould you find the solution. If yes, pls. pls. let me know.

I am having the same error and I need some quick solution. My email: surbha0@.yahoo.com

Thanks a lot in advance,
Saurabh