Problem processing cube

I am getting the error:

Warning 2 Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: B@. - key@. of Dimension: Brcledger from Database: Misys, Cube: Misys 1, Measure Group: Brcledger, Partition: Brcledger, Record: 24163. 0 0

I have read that this is caused by a referential integrity problem however, the fact table is the dimension table, and the joint primary key is definitely unique. There doesn't seem to be anything special about record number 24163 So why can i not process my cube?

Martin

Just incase it is any help.. the other error message which comes up I have pasted here:

Warning 1 Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_brcledger, Column: B_x0040_, Value: 0; Table: dbo_brcledger, Column: key_x0040_, Value: 474142463032485130310000000C. 0 0

SELECT *
FROM brcledger
WHERE (key@. = '474142463032485130310000000C')

Returns 1 result

|||

You have a situation when Analysis Server cannot find a key in the dimension while processing partition.

I would guess you might have problems with dimension process that lead to partition processing errors.

Try re-process your Brcledger dimension change processing options to report and stop on every error.

After you fix dimension problems you should be able to process your partitions without a problem.

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

|||

I have the same problem but it only occurs when i define my dimension as a time dimension. ]

Also my fact table is a view which gets it's surrgate keys by joining to the dimension tables in its definiton. This might be connected but the cube processes fine with the same data source, fact table, dimensions etc as long as i dont define the dimension as a time dimension.

Also the value of the attribute keys it cant find is always zero '0'. There are the same number of errors in the processing as there are nulls in the key column of the fact table. So i assume the nulls are being converted to 0 and then the referential integrity goes.....

Please help,

thanks,

Problem installing SSQL Server 2000 client tools

Hi,

I'm trying to re-install SQL Server 2000 Desktop Engine and
SQL Server client tools. I have succesfully re-installed the desktop engine,
but I am getting the following error message when attempting to re-install the
client tools.

"Setup has detected an existing client tools only installation.
Please use the maintenance mode to add client components"

Unfortunately the Upgrade/Add/Remove option is greyed out as
an install option.

I attempted the registry hive rebuild option and the install appeared
to succeed. However, I cannot access any tools (Enterprise Manager
comes up with the message "The selected file cannot be found").

At this point, the desktop engine appears in Add/Remove programs
Window, but no other SQL Server components.

Any help very much appreciated!

Eric Yeoman.
Eventually solved the problem by manually uninstalling SQL Server;

http://support.microsoft.com/kb/290991/#4

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!