Problem scheduling processing

When I manually run the IS packages to load the data warehouse and then process the dimensions and cubes, everything works fine.

When I schedule the packages as jobs, eventually the data goes wrong. The jobs are scheduled in the correct order.

Any ideas?

Thanks.

If I get your description right, the SSIS packages are not executed in the correct order. Is that so?

For one you can use serveral other ways to process your dimensions and cubes: You can use ascmd command line utility to process exactly the cubes and dimensions. Then wou can schedule a SQL agent job to run ascmd.

You can also use SQL Agent jobs directly to send processing commands to Analysis Serivces.

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

|||

eventually the data goes wrong.

What do you mean by "goes wrong" is it possible that it is just not updated, or not fully updated?

One common trap when scheduling jobs is that usually the scheduled instance runs under a different user account. You should double check that this account has all the appropriate priviledges. Sometimes logging on to your workstation with the same account that the SQL Agent is running under and running the packages interactively can help to highlight any issues. You might find things like network drive mappings are not the same, or privileges to access other databases are not the same your own account, or even that the account in question does not have rights to process the SSAS database.

PROBLEM RESTORE [URGENT]

Mrs,

I'm having a serious problem while trying to restore a database backup. Before concluding the process, the following error apear's:

MICROSOFT SQL - DMO (ODBC SQLSTATE: 42000) The media family on device “d:\backup\dbprinc.bak” is incorrectly formed. This SQL Server cannot process media family. RESTORE DATABASE is terminating abnormally.

When I try “to attach” the database, the following message apear's: LOADING…. but the tables didn't open. I'll be grateful if somebody could help me, because I need to restore this database urgently.

Att.

Jess Augusto / Brazil

hope you are not restoring /attaching SQL Server 2005 database to SQL Server 2000 ... pse post the version and edition of the source and target

Madhu

|||

Sorry,

is Sql Server 2000 SP4.

Tanks

|||

The first message indicates that the file DBPRINC.BAK is not in the format of a TSQL backup. This could indicate that the file is corrupted or that it was produced by something other than TSQL backups.

I'm not sure why you would attempt to ATTACH a backup file.

Can you tell us how the file DBPRINC.BAK was produced? That will help us understand how to proceed.

Problem Replication With DTS

I have transactional replication with DTS in SQL 2000.
In the initial snapshop i got de next error (trasnlate fron de spanish) " The process found invalid column date in the bcp file -path-".
I review the bcp file but i didn't found spacial characters. In order to discard DTS problems, the DTS had only the defult transformations that the SQL creates for it.
The problem does not appear when i don't use DTS with the same data and conditions.
Somebody has anay idea about this error?
Thank you.
what was the error number?
I am afraid your English is too poor for me to understand (and my Spanish is
too bad as well) what you are trying to do and what the problem is. Can you
post this in Spanish for me, and I'll have it translated into English and
then post back in Spanish?
cul era el nmero del error? Estoy asustado que su ingls es demasiado
pobre para que entienda lo que usted est intentando hacer y cules es el
problema. Puede usted fijar esto en espaol para m, y m voluntad para
tenerla traducida a ingls y despus para fijarla detrs en espaol?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Rsantacruz" <Rsantacruz@.discussions.microsoft.com> wrote in message
news:E6D5EDE0-1481-4FDA-94B6-9C21AA24EB4A@.microsoft.com...
> I have transactional replication with DTS in SQL 2000.
> In the initial snapshop i got de next error (trasnlate fron de spanish) "
The process found invalid column date in the bcp file -path-".
> I review the bcp file but i didn't found spacial characters. In order to
discard DTS problems, the DTS had only the defult transformations that the
SQL creates for it.
> The problem does not appear when i don't use DTS with the same data and
conditions.
> Somebody has anay idea about this error?
> Thank you.
|||Thank you for your time Hilary and sorry for my English.
I have the next Transactional replication problems:
1) I performed transactional replication to Oracle subscriber.
The subscriber was configured using Micrososft OLE DB provider for Oracle, because I need to use DTS to transform the data before applying it to Oracle.
In the initial snatshop I got error (windows error) with distrib.exe:
The instruction at '<address>' referenced memory at '<address>'.
The memory could not be "read"
Click OK to terminate the program.
This problem appears with a table with a few rows. The only that I saw in the bcp file is that, there is some char(255) fields with blanks (like char(13), or returns in Word), when I removed some of this blanks from the bcp file and restart the synchro
nization the things go fine.
When I do the same replication of the same data to SQL subscriber it's fine too.
2) The second problem with other table that I got: having the same conditions as described previously
In the initial snatshop I got error (replication error)
"The process encountered invalid column data in bcp file -PATH-"
Not error number and nothing more in the error description.
And the same, when I saw the bcp file and cut some blanks in field (character field) the things go fine.
With SQL subscriber, it's fine too.
I did not use DTS in this case but the result is the same.
I reinstalled SQL SP3 and Win2000 SP4 and I got the same result.
I don't know if there is a some deficiency with OLE DB providers when you used them with replication.
If you know how to resolve this problem, please say me.
Thank yoo for your time, and sorry for this long post.

Problem processing cubes in example Adventure Works DW

Hi,

I've installed the sample databases, and I am trying to process the cubes in the sample.

I keep getting errors like this, for cube "adventure Works":

Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_DimCustomer, Column: AddressLine1, Value: 8011 Mcnutt Ave. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Customer of Dimension: Customer from Database: Adventure Works DW, Record: 1024.

I have set processing to ignore errors, but the cube is never successfully processed.

What can I do to get the cube processed?

Hi John,

Could you please check that you have installed the right AdventureWorksDW relational DB, and that your AdventureWorksDW AS DB's datasource points to it.

YL

|||

Yan,

The "Adventure Works DW" AS DB datasource points to the "AdventureWorksDW" database installed as sample (on the same machine), going by the connection string.

How can I check that I have the "right" AdventureWorksDW?

John

|||

John,

If you installed the sample Adventure Works DW successfully, and verified that the relational DB is also installed and no records in it were removed, the processing should work.

Yan

|||

I've fixed the problem. I had SS 2000 installed as my default instance and 2005 as a named instance and it appears that was the source of the problem. I've had to uninstall both, then reinstall only 2005, but the sample is now working.

Problem processing cubes in example Adventure Works DW

Hi,

I've installed the sample databases, and I am trying to process the cubes in the sample.

I keep getting errors like this, for cube "adventure Works":

Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_DimCustomer, Column: AddressLine1, Value: 8011 Mcnutt Ave. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Customer of Dimension: Customer from Database: Adventure Works DW, Record: 1024.

I have set processing to ignore errors, but the cube is never successfully processed.

What can I do to get the cube processed?

Hi John,

Could you please check that you have installed the right AdventureWorksDW relational DB, and that your AdventureWorksDW AS DB's datasource points to it.

YL

|||

Yan,

The "Adventure Works DW" AS DB datasource points to the "AdventureWorksDW" database installed as sample (on the same machine), going by the connection string.

How can I check that I have the "right" AdventureWorksDW?

John

|||

John,

If you installed the sample Adventure Works DW successfully, and verified that the relational DB is also installed and no records in it were removed, the processing should work.

Yan

|||

I've fixed the problem. I had SS 2000 installed as my default instance and 2005 as a named instance and it appears that was the source of the problem. I've had to uninstall both, then reinstall only 2005, but the sample is now working.

Problem processing cube partition

I am getting the following error when trying to process a partition, as if
the process is trying to overwrite the database. How can I fix this?

TIA

Error 1 Errors in the metadata manager. The database with the name of
'ACRPROD_OLAP' already exists in the 'MBPENTSQL01R\ACR' server. 0 0

Are you deploying from BIDS? Did you rename a database that was previously deployed? The following post might shed some light. You might check the Name and ID properties of each deployed database and see whether any have the ID of ACRPROD_OLAP regardless of what Name they have.

http://geekswithblogs.net/darrengosbell/archive/2007/06/06/BIDSHelper-DeployMDXScript-feature-enhanced.aspx

Easy fix... delete the conflicting database off the server. More complex fix... instead of renaming a database on the server, backup the database, delete it, then restore it as the new name... that will make sure the new name matches the new ID.

sql

Problem on Cube processing

Hi, all,

Thanks for your kind attention again.

I encountered a strange problem-whenever I process the cube(which is a small cube only, as I have already selected its partitions based on date dimension and the whole cube only with less than 1000 rows records), but I always got the problem which runs out the system drive space and of course resulted in the failure of the processing of the cube. I have actually manually allocated the storage locations which are not on the local system drive? Why did that problem happen and how can I figure it out?

That's really frustrated problem and please give me any advices and help on this if you have have any ideas what is going on for this.

I am looking forward to hearing from you and thanks a lot in advance again.

With best regards,

Yours sincerely,

What AS do you have AS2K or AS2K5?

Please, take attention to the queries that are send to data source sql server. I think you have somewhere cartesian product in your cube design that leads to the data explosion.

|||

Hi,

Thanks for your kind attention.

I am running AS2005. Yes, I have found the cause of the problem, as the fact table where the measure group is from is too big with over million records, thus even though my cube has been partitioned with only less than 1 thousand records, as the processing always need to query into the whole fact table still which thus resulting in the running out of the system drive space (as I am doing some test with my virtual machine at the moment only, which only has a poor system drive storage.)

I have then particularly partiton the fact table with only a small proportion of data for the cube, and now the processing is ok then.

Thanks again.

With best regards,

Yours sincerely,

problem olap process

Hi,
I have a cube in analysis manager. This cube is processed via a DTS in sql server 2000 with an incremental update.
The sql task finishes successfully but there is no data moreover in the cube.
So, I proccess manually the cube with the dialog box "process a cube" and I select Incremental Update : the step finishes successfully but there is still not data moreover!!
I have to process the cube with a full process each time!!
Why that doesn't work?? any ideas??There is no quick way to resolve but you may try review this http://www.databasejournal.com/features/mssql/article.php/1582491 link to troubleshoot the issue.

HTH

Problem installing SQL 2005 Server Express

I have the beta versions installed, got an error:

Microsoft SQL Server 2005 Setup beginning at Wed Aug 16 18:14:14 2006 Process ID : 4668 c:\8c27e35b5d509dc8609c33e266\setup.exe Version: 2005.90.2047.0 Running: LoadResourcesAction at: 2006/7/16 18:14:13 Complete: LoadResourcesAction at: 2006/7/16 18:14:13, returned true Running: ParseBootstrapOptionsAction at: 2006/7/16 18:14:14 Loaded DLL:c:\8c27e35b5d509dc8609c33e266\xmlrw.dll Version:2.0.3609.0 Complete: ParseBootstrapOptionsAction at: 2006/7/16 18:14:14, returned true Running: ValidateWinNTAction at: 2006/7/16 18:14:14 Complete: ValidateWinNTAction at: 2006/7/16 18:14:14, returned true Running: ValidateMinOSAction at: 2006/7/16 18:14:14 Complete: ValidateMinOSAction at: 2006/7/16 18:14:14, returned true Running: PerformSCCAction at: 2006/7/16 18:14:14 Complete: PerformSCCAction at: 2006/7/16 18:14:14, returned true Running: ActivateLoggingAction at: 2006/7/16 18:14:14 Complete: ActivateLoggingAction at: 2006/7/16 18:14:14, returned true Delay load of action "DetectPatchedBootstrapAction" returned nothing. No action will occur as a result. Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions: Condition "EventCondition: __STP_LaunchPatchedBootstrap__4668" returned false. Running: PerformSCCAction2 at: 2006/7/16 18:14:14 Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435 Product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" versioned 9.00.0981 is not compatible with current builds of SQL Server.Expected at least version: 9.00.1399.00 The Product Name is "Microsoft SQL Server 2005 Tools Express Edition Beta 3" Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435 Error: Action "PerformSCCAction2" threw an exception during execution. Return Code: 70032 Message displayed to user SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme. Class not registered. Delay load of action "UploadDrWatsonLogAction" returned nothing. No action will occur as a result.

I ran msiexec /x "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" without the quotes and got the following:

The setup has encounted an unexpected error in datastore. The action is Write_CommitFlag. The error is Unable to write property into cache: "flagCommit" XmRW Error: Failure loading xmlw.dll CheckAllProcedures[] return 2

I have ran the uninstall tool and deleted everything beta, etc from the add and remove list.

I have Visual Studio 2003 installed and SQL 7 and 2000 installed as well. I have now reinstalled all the other express tools and they are not working correctly either, but it may be because I can not get SQL 2005 Server Express installed.

Please help, hindering my school work.

Dee

This indicates that some beta components (files, reg keys, etc) still exist on your machine. Check the core setup log file located at %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files, whose name should be like SQLSetup0001_%machinename%_Core(Local).log. It will tell your the version of the beta components. Try the following steps sequently to remove those beta components.

1. Uninstall any visible Beta components in Add/Remove Program.
2. Remove all registy keys related to the specific Beta version, which you can get from the core log files. You need to search the whole registry tree with regedit command.
3. Kill any Beta services (including SQL, OLAP, SQLAGENT, SQLBROWSER, ...).
4. Reboot the machine.

Thanks,
Sam Lester (MSFT)

|||Under program files\microsoft sql server I have a directory 80, is this part of the beta?|||It is using this product "{2750B389-A2D2-4953-99CA-27C1F2A8E6FD}" and I can not find it anywhere

Problem Installing SP1 in Web Farm

I have some concerns about the install process outlined in the readme for SP1. The readme indicates that the database server (the server hosting the ReportServer database) should be upgraded first.
â'The order in which you apply SP1 is important. You must first apply SP1 to the server that hosts the report server database (this updates the database format to the SP1 version). Once you update the database, you can update the report server nodes in any order.â'
My infrastructure looks like this ->
Server 1 & 2 : 2 node NLB running Reporting Services
Server 3: SQL Server 2000 server hosting the ReportServer database (no RS components)
When I install SP1 on the database server (it is not running any RS components â' just hosting the ReportServer database) the install fails with the following error ->
â'The upgrade patch cannot be installed by the windows installer services because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program.â'
When the install on the database server failed, I went ahead and installed SP1 on the servers running Reporting Services â' The install completed and Reporting Services shows the appropriate version number (8.00.878.00) but I didnâ't see any splash screens indicating that the database was being upgraded (as I have when I have applied SP1 on machines running both SQL Server and Reporting Services).
Has anyone had a similar experience upgrading the database server, either in a web farm scenario or a two-server (RS: Server1, SQL: Server2) scenario?
Has anyone successfully implemented SP1 on a SQL Server that is not running any RS components?
Thanks,
MarkThe readme seems to be a little confusing. You can only run setup on
machines that RS is installed on, because your DB resides on a separate
machine you do not need to run SP1 setup on this machine.
Here is a good way to upgrade SP1 on a farm.
Turn off the other nodes (turn off IIS and the ReportServer windows service)
Run SP1 install on the one machine that still has IIS and the ReportServer
service running. This will upgrade the DB.
Hitting the vroot for this machine should now work
For each machine in the farm:
Turn on IIS and the ReportServer service
Run sp1 setup
Ensure machine is working properly
Following these steps you will be able to upgrade your farm.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mark Barker" <MarkBarker@.discussions.microsoft.com> wrote in message
news:CAF2DC91-11C5-4E76-8ED9-FC99824E6D9F@.microsoft.com...
> I have some concerns about the install process outlined in the readme for
SP1. The readme indicates that the database server (the server hosting the
ReportServer database) should be upgraded first.
> "The order in which you apply SP1 is important. You must first apply SP1
to the server that hosts the report server database (this updates the
database format to the SP1 version). Once you update the database, you can
update the report server nodes in any order."
> My infrastructure looks like this ->
> Server 1 & 2 : 2 node NLB running Reporting Services
> Server 3: SQL Server 2000 server hosting the ReportServer database (no RS
components)
> When I install SP1 on the database server (it is not running any RS
components - just hosting the ReportServer database) the install fails with
the following error ->
> "The upgrade patch cannot be installed by the windows installer services
because the program to be upgraded may be missing, or the upgrade patch may
update a different version of the program."
> When the install on the database server failed, I went ahead and installed
SP1 on the servers running Reporting Services - The install completed and
Reporting Services shows the appropriate version number (8.00.878.00) but I
didn't see any splash screens indicating that the database was being
upgraded (as I have when I have applied SP1 on machines running both SQL
Server and Reporting Services).
> Has anyone had a similar experience upgrading the database server, either
in a web farm scenario or a two-server (RS: Server1, SQL: Server2) scenario?
> Has anyone successfully implemented SP1 on a SQL Server that is not
running any RS components?
> Thanks,
> Mark
>|||Thanks Daniel
So even though I donâ't see an â'upgrading databaseâ?¦â' dialog box during SP1 install on the first node â' I can assume that the upgrade has taken place?
Is there anything I can check in the ReportServer db to confirm?
Thanks,
Mark
"Daniel Reib [MSFT]" wrote:
> The readme seems to be a little confusing. You can only run setup on
> machines that RS is installed on, because your DB resides on a separate
> machine you do not need to run SP1 setup on this machine.
> Here is a good way to upgrade SP1 on a farm.
> Turn off the other nodes (turn off IIS and the ReportServer windows service)
> Run SP1 install on the one machine that still has IIS and the ReportServer
> service running. This will upgrade the DB.
> Hitting the vroot for this machine should now work
> For each machine in the farm:
> Turn on IIS and the ReportServer service
> Run sp1 setup
> Ensure machine is working properly
> Following these steps you will be able to upgrade your farm.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Mark Barker" <MarkBarker@.discussions.microsoft.com> wrote in message
> news:CAF2DC91-11C5-4E76-8ED9-FC99824E6D9F@.microsoft.com...
> > I have some concerns about the install process outlined in the readme for
> SP1. The readme indicates that the database server (the server hosting the
> ReportServer database) should be upgraded first.
> >
> > "The order in which you apply SP1 is important. You must first apply SP1
> to the server that hosts the report server database (this updates the
> database format to the SP1 version). Once you update the database, you can
> update the report server nodes in any order."
> >
> > My infrastructure looks like this ->
> >
> > Server 1 & 2 : 2 node NLB running Reporting Services
> > Server 3: SQL Server 2000 server hosting the ReportServer database (no RS
> components)
> >
> > When I install SP1 on the database server (it is not running any RS
> components - just hosting the ReportServer database) the install fails with
> the following error ->
> >
> > "The upgrade patch cannot be installed by the windows installer services
> because the program to be upgraded may be missing, or the upgrade patch may
> update a different version of the program."
> >
> > When the install on the database server failed, I went ahead and installed
> SP1 on the servers running Reporting Services - The install completed and
> Reporting Services shows the appropriate version number (8.00.878.00) but I
> didn't see any splash screens indicating that the database was being
> upgraded (as I have when I have applied SP1 on machines running both SQL
> Server and Reporting Services).
> >
> > Has anyone had a similar experience upgrading the database server, either
> in a web farm scenario or a two-server (RS: Server1, SQL: Server2) scenario?
> >
> > Has anyone successfully implemented SP1 on a SQL Server that is not
> running any RS components?
> >
> > Thanks,
> > Mark
> >
>
>

Problem install SQL Server Desktop Engine

I'm in the process of attempting to install Microsoft SQL Server Desktop Engine on my computer in support of an email program call Mailloop6. I've tried going through their tech support but they haven't been able to figure it out.

I'm running Windows XP with SP1 upgrade on a DSL connection.

When I installed the program the first time, I got the following error:

"Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information."

The program obviously wouldn't install. I contacted the vendor and they sent a version with a batch file. Same result. I removed all the appropriate registry entries between installs and removed all the data files as well.

I've tried installing the program using the free MDSE download from the MS site with the following result:

"A Strong SA password is required for security reasons. Please use SAPWD switch to supply the same. Refer to readme for more details. Setup will now exit."

Here's the error log that I got after attempting to install:

2004-02-25 19:31:42.55 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)

2004-02-25 19:31:42.55 server Copyright (C) 1988-2002 Microsoft Corporation.
2004-02-25 19:31:42.55 server All rights reserved.
2004-02-25 19:31:42.55 server Server Process ID is 3404.
2004-02-25 19:31:42.55 server Logging SQL Server messages in file 'C:Program FilesMicrosoft SQL ServerMSSQL$MAILLOOP6LOGERRORLOG'.
2004-02-25 19:31:42.56 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2004-02-25 19:31:42.60 server SQL Server configured for thread mode processing.
2004-02-25 19:31:42.60 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2004-02-25 19:31:42.63 spid3 Warning ******************
2004-02-25 19:31:42.63 spid3 SQL Server started in single user mode. Updates allowed to system catalogs.
2004-02-25 19:31:42.63 spid3 Starting up database 'master'.
2004-02-25 19:31:42.91 server Using 'SSNETLIB.DLL' version '8.0.766'.
2004-02-25 19:31:42.94 spid5 Starting up database 'model'.
2004-02-25 19:31:43.24 server SQL server listening on 152.163.0.0: 4113.
2004-02-25 19:31:43.24 server SQL server listening on 172.16.1.33: 4113.
2004-02-25 19:31:43.24 server SQL server listening on 127.0.0.1: 4113.
2004-02-25 19:31:43.25 spid3 Server name is 'MONSTERMAILLOOP6'.
2004-02-25 19:31:43.25 spid3 Skipping startup of clean database id 5
2004-02-25 19:31:43.25 spid3 Skipping startup of clean database id 6
2004-02-25 19:31:43.25 spid3 Starting up database 'msdb'.
2004-02-25 19:31:43.56 spid5 Clearing tempdb database.
2004-02-25 19:31:44.13 spid5 Starting up database 'tempdb'.
2004-02-25 19:31:44.17 spid3 Recovery complete.
2004-02-25 19:31:44.17 spid3 SQL global counter collection task is created.
2004-02-25 19:31:44.19 spid3 Warning: override, autoexec procedures skipped.
2004-02-25 19:31:47.75 server SQL server listening on TCP, Shared Memory, Named Pipes.
2004-02-25 19:31:47.75 server SQL Server is ready for client connections
2004-02-25 19:31:57.97 spid3 SQL Server is terminating due to 'stop' request from Service Control Manager.

Any thoughts on this would be very much appreciated!Originally posted by betteru
I'm in the process of attempting to install Microsoft SQL Server Desktop Engine on my computer in support of an email program call Mailloop6. I've tried going through their tech support but they haven't been able to figure it out.

I'm running Windows XP with SP1 upgrade on a DSL connection.

When I installed the program the first time, I got the following error:

"Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information."

The program obviously wouldn't install. I contacted the vendor and they sent a version with a batch file. Same result. I removed all the appropriate registry entries between installs and removed all the data files as well.

I've tried installing the program using the free MDSE download from the MS site with the following result:

"A Strong SA password is required for security reasons. Please use SAPWD switch to supply the same. Refer to readme for more details. Setup will now exit."

Here's the error log that I got after attempting to install:

2004-02-25 19:31:42.55 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)

2004-02-25 19:31:42.55 server Copyright (C) 1988-2002 Microsoft Corporation.
2004-02-25 19:31:42.55 server All rights reserved.
2004-02-25 19:31:42.55 server Server Process ID is 3404.
2004-02-25 19:31:42.55 server Logging SQL Server messages in file 'C:Program FilesMicrosoft SQL ServerMSSQL$MAILLOOP6LOGERRORLOG'.
2004-02-25 19:31:42.56 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2004-02-25 19:31:42.60 server SQL Server configured for thread mode processing.
2004-02-25 19:31:42.60 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2004-02-25 19:31:42.63 spid3 Warning ******************
2004-02-25 19:31:42.63 spid3 SQL Server started in single user mode. Updates allowed to system catalogs.
2004-02-25 19:31:42.63 spid3 Starting up database 'master'.
2004-02-25 19:31:42.91 server Using 'SSNETLIB.DLL' version '8.0.766'.
2004-02-25 19:31:42.94 spid5 Starting up database 'model'.
2004-02-25 19:31:43.24 server SQL server listening on 152.163.0.0: 4113.
2004-02-25 19:31:43.24 server SQL server listening on 172.16.1.33: 4113.
2004-02-25 19:31:43.24 server SQL server listening on 127.0.0.1: 4113.
2004-02-25 19:31:43.25 spid3 Server name is 'MONSTERMAILLOOP6'.
2004-02-25 19:31:43.25 spid3 Skipping startup of clean database id 5
2004-02-25 19:31:43.25 spid3 Skipping startup of clean database id 6
2004-02-25 19:31:43.25 spid3 Starting up database 'msdb'.
2004-02-25 19:31:43.56 spid5 Clearing tempdb database.
2004-02-25 19:31:44.13 spid5 Starting up database 'tempdb'.
2004-02-25 19:31:44.17 spid3 Recovery complete.
2004-02-25 19:31:44.17 spid3 SQL global counter collection task is created.
2004-02-25 19:31:44.19 spid3 Warning: override, autoexec procedures skipped.
2004-02-25 19:31:47.75 server SQL server listening on TCP, Shared Memory, Named Pipes.
2004-02-25 19:31:47.75 server SQL Server is ready for client connections
2004-02-25 19:31:57.97 spid3 SQL Server is terminating due to 'stop' request from Service Control Manager.

Any thoughts on this would be very much appreciated!

with the desktop edition the setup does not work in windows! you must exit to dos and on the directory where you've installed msde you must write:
setup.exe /qb+ instancename= something sapwd=your password|||I did not know that - the tech support for the software didn't mention a single thing about exiting to DOS. I will definitely give that a try.

Thanks!