Having trouble installing SQl Server 2005

I am having trouble installing SQL Server 2005 on a new machine at a hosted company. I am only installing the minimum, SQL Databaes Services. It errors out at the end and says see log. I have installed SQl 2005 10 times with no problem at other locations. The service won't even start it says error 3 path unkown. If I look for the path it shows in the service it hasn't been created, the files and directories were not created at that directory location. I tried to install bot as a Domain Admin and Local Admin accounts.

Here THe summary Log., Core(local) and Core Log files below.

Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows Server 2003 family, Standard Edition Service Pack 1 (Build 3790)
Time : Tue Mar 20 02:48:40 2007
Machine : CATCSAP021211
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_CATCSAP021211_SQLSupport_1.log
--
Machine : CATCSAP021211
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_CATCSAP021211_SQLNCLI_1.log
--
Machine : CATCSAP021211
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_CATCSAP021211_OWC11_1.log
--
Machine : CATCSAP021211
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_CATCSAP021211_SqlWriter_1.log
--
Machine : CATCSAP021211
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_CATCSAP021211_BackwardsCompat_1.log
--

SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.

Time : Tue Mar 20 02:50:13 2007

List of log files:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_CATCSAP021211_Core(Local).log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_CATCSAP021211_SQLSupport_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_CATCSAP021211_SQLNCLI_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_CATCSAP021211_OWC11_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_CATCSAP021211_SqlWriter_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_CATCSAP021211_BackwardsCompat_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_CATCSAP021211_MSXML6_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_CATCSAP021211_Datastore.xml
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_CATCSAP021211_.NET Framework 2.0.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_CATCSAP021211_Core.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_CATCSAP021211_.NET Framework 2.0 LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_CATCSAP021211_.NET Framework Upgrade Advisor.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_CATCSAP021211_.NET Framework Upgrade Advisor LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_CATCSAP021211_.NET Framework Windows Installer.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_CATCSAP021211_.NET Framework Windows Installer LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_CATCSAP021211_Support.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_CATCSAP021211_SCC.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0016_CATCSAP021211_WI.log

Core(local)

Microsoft SQL Server 2005 Setup beginning at Mon Mar 19 19:49:04 2007
Process ID : 1300
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2007/2/19 19:49:4
Complete: LoadResourcesAction at: 2007/2/19 19:49:4, returned true
Running: ParseBootstrapOptionsAction at: 2007/2/19 19:49:4
Loaded DLL:C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\xmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2007/2/19 19:49:4, returned true
Running: ValidateWinNTAction at: 2007/2/19 19:49:4
Complete: ValidateWinNTAction at: 2007/2/19 19:49:4, returned true
Running: ValidateMinOSAction at: 2007/2/19 19:49:4
Complete: ValidateMinOSAction at: 2007/2/19 19:49:4, returned true
Running: PerformSCCAction at: 2007/2/19 19:49:4
Complete: PerformSCCAction at: 2007/2/19 19:49:4, returned true
Running: ActivateLoggingAction at: 2007/2/19 19:49:4
Complete: ActivateLoggingAction at: 2007/2/19 19:49:4, returned true
Running: DetectPatchedBootstrapAction at: 2007/2/19 19:49:4
Complete: DetectPatchedBootstrapAction at: 2007/2/19 19:49:4, returned true
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__1300" returned false.
Action "BeginBootstrapLogicStage" will be skipped due to the following restrictions:
Condition "Setup is running locally." returned true.
Running: PerformDotNetCheck2 at: 2007/2/19 19:49:4
Complete: PerformDotNetCheck2 at: 2007/2/19 19:49:4, returned true
Running: InvokeSqlSetupDllAction at: 2007/2/19 19:49:4
Loaded DLL:C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\sqlspars.dll Version:2005.90.1399.0
<Func Name='DwLaunchMsiExec'>
Examining 'sqlspars' globals to initialize 'SetupStateScope'
Opening 'MachineConfigScope' for [CATCSAP021211]
Trying to find Product Code from command line or passed transform
If possible, determine install id and type
Trying to find Instance Name from command line.
No Instance Name provided on the command line
If possible, determine action
Machine = CATCSAP021211, Article = WMIServiceWin32OSWorking, Result = 0 (0x0)
Machine = CATCSAP021211, Article = WMIServiceWin32CompSystemWorking, Result = 0 (0x0)
Machine = CATCSAP021211, Article = WMIServiceWin32ProcessorWorking, Result = 0 (0x0)
Machine = CATCSAP021211, Article = WMIServiceReadRegWorking, Result = 0 (0x0)
Machine = CATCSAP021211, Article = WMIServiceWin32DirectoryWorking, Result = 0 (0x0)
Machine = CATCSAP021211, Article = WMIServiceCIMDataWorking, Result = 0 (0x0)
Machine = CATCSAP021211, Article = XMLDomDocument, Result = 0 (0x0)
Machine = CATCSAP021211, Article = Processor, Result = 0 (0x0)
Machine = CATCSAP021211, Article = PhysicalMemory, Result = 0 (0x0)
Machine = CATCSAP021211, Article = DiskFreeSpace, Result = 0 (0x0)
Machine = CATCSAP021211, Article = OSVersion, Result = 0 (0x0)
Machine = CATCSAP021211, Article = OSServicePack, Result = 0 (0x0)
Machine = CATCSAP021211, Article = OSType, Result = 0 (0x0)
Machine = CATCSAP021211, Article = iisDep, Result = 0 (0x0)
Machine = CATCSAP021211, Article = AdminShare, Result = 0 (0x0)
Machine = CATCSAP021211, Article = PendingReboot, Result = 0 (0x0)
Machine = CATCSAP021211, Article = PerfMon, Result = 0 (0x0)
Machine = CATCSAP021211, Article = IEVersion, Result = 0 (0x0)
Machine = CATCSAP021211, Article = DriveWriteAccess, Result = 0 (0x0)
Machine = CATCSAP021211, Article = COMPlus, Result = 0 (0x0)
Machine = CATCSAP021211, Article = ASPNETVersionRegistration, Result = 0 (0x0)
Machine = CATCSAP021211, Article = MDAC25Version, Result = 0 (0x0)
*******************************************
Setup Consistency Check Report for Machine: CATCSAP021211
*******************************************
Article: WMI Service Requirement, Result: CheckPassed
Article: MSXML Requirement, Result: CheckPassed
Article: Operating System Minimum Level Requirement, Result: CheckPassed
Article: Operating System Service Pack Level Requirement, Result: CheckPassed
Article: SQL Compatibility With Operating System, Result: CheckPassed
Article: Minimum Hardware Requirement, Result: CheckPassed
Article: IIS Feature Requirement, Result: CheckPassed
Article: Pending Reboot Requirement, Result: CheckPassed
Article: Performance Monitor Counter Requirement, Result: CheckPassed
Article: Default Installation Path Permission Requirement, Result: CheckPassed
Article: Internet Explorer Requirement, Result: CheckPassed
Article: Check COM+ Catalogue, Result: CheckPassed
Article: ASP.Net Registration Requirement, Result: CheckPassed
Article: Minimum MDAC Version Requirement, Result: CheckPassed
<Func Name='PerformDetections'>
0
<EndFunc Name='PerformDetections' Return='0' GetLastError='0'>
<Func Name='DisplaySCCWizard'>
CSetupBootstrapWizard returned 1
<EndFunc Name='DisplaySCCWizard' Return='0' GetLastError='183'>
Loaded DLL:C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\sqlsval.dll Version:2005.90.1399.0
<EndFunc Name='DwLaunchMsiExec' Return='0' GetLastError='0'>
Complete: InvokeSqlSetupDllAction at: 2007/2/19 19:51:1, returned true
Running: SetPackageInstallStateAction at: 2007/2/19 19:51:1
Complete: SetPackageInstallStateAction at: 2007/2/19 19:51:1, returned true
Running: DeterminePackageTransformsAction at: 2007/2/19 19:51:1
Complete: DeterminePackageTransformsAction at: 2007/2/19 19:51:3, returned true
Running: ValidateSetupPropertiesAction at: 2007/2/19 19:51:3
Complete: ValidateSetupPropertiesAction at: 2007/2/19 19:51:3, returned true
Running: OpenPipeAction at: 2007/2/19 19:51:3
Complete: OpenPipeAction at: 2007/2/19 19:51:3, returned false
Error: Action "OpenPipeAction" failed during execution.
Running: CreatePipeAction at: 2007/2/19 19:51:3
Complete: CreatePipeAction at: 2007/2/19 19:51:3, returned false
Error: Action "CreatePipeAction" failed during execution.
Action "RunRemoteSetupAction" will be skipped due to the following restrictions:
Condition "Action: CreatePipeAction has finished and passed." returned false.
Running: PopulateMutatorDbAction at: 2007/2/19 19:51:3
Complete: PopulateMutatorDbAction at: 2007/2/19 19:51:3, returned true
Running: GenerateRequestsAction at: 2007/2/19 19:51:3
SQL_Engine = 3
SQL_Data_Files = 3
SQL_Replication = 3
SQL_FullText = 3
SQL_SharedTools = 3
SQL_BC_DEP = 3
Analysis_Server = -1
AnalysisDataFiles = -1
AnalysisSharedTools = -1
RS_Server = -1
RS_Web_Interface = -1
RS_SharedTools = -1
Notification_Services = -1
NS_Engine = -1
NS_Client = -1
SQL_DTS = -1
Client_Components = 3
Connectivity = 3
SQL_Tools90 = 3
SQL_WarehouseDevWorkbench = 3
SDK = 3
SQLXML = 3
Tools_Legacy = 3
TOOLS_BC_DEP = 3
SQL_Documentation = 3
SQL_BooksOnline = 3
SQL_DatabaseSamples = -1
SQL_AdventureWorksSamples = -1
SQL_AdventureWorksDWSamples = -1
SQL_AdventureWorksASSamples = -1
SQL_Samples = -1
Complete: GenerateRequestsAction at: 2007/2/19 19:51:4, returned true
Running: CreateProgressWindowAction at: 2007/2/19 19:51:4
Complete: CreateProgressWindowAction at: 2007/2/19 19:51:4, returned true
Running: ScheduleActionAction at: 2007/2/19 19:51:4
Complete: ScheduleActionAction at: 2007/2/19 19:51:4, returned true
Skipped: InstallASAction.11
Skipped: Action "InstallASAction.11" was not run. Information reported during analysis:
No install request found for package: "sqlsupport", referred by package: "as", install will be skipped as a result.
Skipped: InstallASAction.18
Skipped: Action "InstallASAction.18" was not run. Information reported during analysis:
No install request found for package: "owc11", referred by package: "as", install will be skipped as a result.
Skipped: InstallASAction.22
Skipped: Action "InstallASAction.22" was not run. Information reported during analysis:
No install request found for package: "bcRedist", referred by package: "as", install will be skipped as a result.
Skipped: InstallASAction.9
Skipped: Action "InstallASAction.9" was not run. Information reported during analysis:
No install request found for package: "msxml6", referred by package: "as", install will be skipped as a result.
Skipped: InstallDTSAction
Skipped: Action "InstallDTSAction" was not run. Information reported during analysis:
No install request found for package: "dts", install will be skipped as a result.
Skipped: InstallDTSAction.11
Skipped: Action "InstallDTSAction.11" was not run. Information reported during analysis:
No install request found for package: "sqlsupport", referred by package: "dts", install will be skipped as a result.
Skipped: InstallDTSAction.12
Skipped: Action "InstallDTSAction.12" was not run. Information reported during analysis:
No install request found for package: "sqlncli", referred by package: "dts", install will be skipped as a result.
Skipped: InstallDTSAction.18
Skipped: Action "InstallDTSAction.18" was not run. Information reported during analysis:
No install request found for package: "owc11", referred by package: "dts", install will be skipped as a result.
Skipped: InstallDTSAction.22
Skipped: Action "InstallDTSAction.22" was not run. Information reported during analysis:
No install request found for package: "bcRedist", referred by package: "dts", install will be skipped as a result.
Skipped: InstallDTSAction.9
Skipped: Action "InstallDTSAction.9" was not run. Information reported during analysis:
No install request found for package: "msxml6", referred by package: "dts", install will be skipped as a result.
Skipped: InstallNSAction
Skipped: Action "InstallNSAction" was not run. Information reported during analysis:
No install request found for package: "ns", install will be skipped as a result.
Skipped: InstallNSAction.11
Skipped: Action "InstallNSAction.11" was not run. Information reported during analysis:
No install request found for package: "sqlsupport", referred by package: "ns", install will be skipped as a result.
Skipped: InstallNSAction.12
Skipped: Action "InstallNSAction.12" was not run. Information reported during analysis:
No install request found for package: "sqlncli", referred by package: "ns", install will be skipped as a result.
Skipped: InstallNSAction.18
Skipped: Action "InstallNSAction.18" was not run. Information reported during analysis:
No install request found for package: "owc11", referred by package: "ns", install will be skipped as a result.
Skipped: InstallNSAction.22
Skipped: Action "InstallNSAction.22" was not run. Information reported during analysis:
No install request found for package: "bcRedist", referred by package: "ns", install will be skipped as a result.
Skipped: InstallNSAction.9
Skipped: Action "InstallNSAction.9" was not run. Information reported during analysis:
No install request found for package: "msxml6", referred by package: "ns", install will be skipped as a result.
Skipped: InstallRSAction.11
Skipped: Action "InstallRSAction.11" was not run. Information reported during analysis:
No install request found for package: "sqlsupport", referred by package: "rs", install will be skipped as a result.
Skipped: InstallRSAction.18
Skipped: Action "InstallRSAction.18" was not run. Information reported during analysis:
No install request found for package: "owc11", referred by package: "rs", install will be skipped as a result.
Skipped: InstallRSAction.22
Skipped: Action "InstallRSAction.22" was not run. Information reported during analysis:
No install request found for package: "bcRedist", referred by package: "rs", install will be skipped as a result.
Running: InstallSqlAction.11 at: 2007/2/19 19:51:4
Installing: sqlsupport on target: CATCSAP021211
Complete: InstallSqlAction.11 at: 2007/2/19 19:51:5, returned true
Running: InstallSqlAction.12 at: 2007/2/19 19:51:5
Installing: sqlncli on target: CATCSAP021211
Complete: InstallSqlAction.12 at: 2007/2/19 19:51:6, returned true
Running: InstallSqlAction.18 at: 2007/2/19 19:51:6
Installing: owc11 on target: CATCSAP021211
Complete: InstallSqlAction.18 at: 2007/2/19 19:51:13, returned true
Running: InstallSqlAction.21 at: 2007/2/19 19:51:13
Installing: sqlwriter on target: CATCSAP021211
Complete: InstallSqlAction.21 at: 2007/2/19 19:51:18, returned true
Running: InstallSqlAction.22 at: 2007/2/19 19:51:18
Installing: bcRedist on target: CATCSAP021211
Complete: InstallSqlAction.22 at: 2007/2/19 19:51:28, returned true
Running: InstallSqlAction.9 at: 2007/2/19 19:51:28
Installing: msxml6 on target: CATCSAP021211
Error: MsiOpenDatabase failed with 110
Failed to install package
The installation source for this product is not available. Verify that the source exists and that you can access it.
Error: MsiOpenDatabase failed with 110 for MSI {5A710547-B58E-488B-828D-CA9A25A0533C}
Setting package return code to: 1612
Complete: InstallSqlAction.9 at: 2007/2/19 19:51:28, returned false
Error: Action "InstallSqlAction.9" failed during execution. Error information reported during run:
Target collection includes the local machine.
Invoking installPackage() on local machine.
Running: InstallToolsAction.11 at: 2007/2/19 19:51:28
Installing: sqlsupport on target: CATCSAP021211
Complete: InstallToolsAction.11 at: 2007/2/19 19:51:33, returned true
Running: InstallToolsAction.12 at: 2007/2/19 19:51:33
Installing: sqlncli on target: CATCSAP021211
Complete: InstallToolsAction.12 at: 2007/2/19 19:51:34, returned true
Running: InstallToolsAction.13 at: 2007/2/19 19:51:34
Installing: PPESku on target: CATCSAP021211
Complete: InstallToolsAction.13 at: 2007/2/19 19:53:48, returned true
Running: InstallToolsAction.18 at: 2007/2/19 19:53:48
Installing: owc11 on target: CATCSAP021211
Complete: InstallToolsAction.18 at: 2007/2/19 19:53:51, returned true
Running: InstallToolsAction.20 at: 2007/2/19 19:53:51
Installing: BOL on target: CATCSAP021211
Complete: InstallToolsAction.20 at: 2007/2/19 19:55:37, returned true
Running: InstallToolsAction.22 at: 2007/2/19 19:55:37
Installing: bcRedist on target: CATCSAP021211
Complete: InstallToolsAction.22 at: 2007/2/19 19:55:40, returned true
Error: Action "InstallToolsAction.9" failed during execution. Error information reported during run:
Action: "InstallToolsAction.9" will be marked as failed due to the following condition:
Condition "Package "9" either passed when it was last installed, or it has not been executed yet" returned false. Condition context:
Prereq package will be failed due to the previous installation attempt returning: 1612
Installation of package: "msxml6" failed due to a precondition.
Action "InstallSqlAction" will return false due to the following preconditions:
Condition "Action: InstallSqlAction.9 has finished and failed." returned true.
Installation of package: "sql" failed due to a precondition.
Step "InstallSqlAction" was not able to run.
Skipped: InstallNSAction.10
Skipped: Action "InstallNSAction.10" was not run. Information reported during analysis:
No install request found for package: "sqlxml4", referred by package: "ns", install will be skipped as a result.
Running: InstallToolsAction.10 at: 2007/2/19 19:55:40
Installing: sqlxml4 on target: CATCSAP021211
Complete: InstallToolsAction.10 at: 2007/2/19 19:55:44, returned true
Skipped: RepairForBackwardsCompatRedistAction
Skipped: Action "RepairForBackwardsCompatRedistAction" was not run. Information reported during analysis:
Action: "RepairForBackwardsCompatRedistAction" will be skipped due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Error: Action "UninstallForMSDE2000Action" failed during execution. Error information reported during run:
Action: "UninstallForMSDE2000Action" will be marked as failed due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Installation of package: "patchMSDE2000" failed due to a precondition.
Error: Action "UninstallForSQLAction" failed during execution. Error information reported during run:
Action: "UninstallForSQLAction" will be marked as failed due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Installation of package: "patchLibertySql" failed due to a precondition.
Action "InstallToolsAction" will return false due to the following preconditions:
Condition "Action: InstallToolsAction.9 has finished and failed." returned true.
Installation of package: "tools" failed due to a precondition.
Step "InstallToolsAction" was not able to run.
Skipped: InstallASAction
Skipped: Action "InstallASAction" was not run. Information reported during analysis:
No install request found for package: "as", install will be skipped as a result.
Skipped: InstallRSAction
Skipped: Action "InstallRSAction" was not run. Information reported during analysis:
No install request found for package: "rs", install will be skipped as a result.
Skipped: UninstallForRS2000Action
Skipped: Action "UninstallForRS2000Action" was not run. Information reported during analysis:
Action: "UninstallForRS2000Action" will be skipped due to the following condition:
Condition "Action: InstallRSAction was skipped." returned true.
Running: ReportChainingResults at: 2007/2/19 19:55:44
Error: Action "ReportChainingResults" threw an exception during execution.
One or more packages failed to install. Refer to logs for error details. : 1612
Error Code: 0x8007064c (1612)
Windows Error Text: The installation source for this product is not available. Verify that the source exists and that you can access it.

Source File Name: sqlchaining\sqlchainingactions.cpp
Compiler Timestamp: Thu Sep 1 22:23:05 2005
Function Name: sqls::ReportChainingResults::perform
Source Line Number: 3097

- Context --
sqls::HostSetupPackageInstallerSynch::postCommit
sqls::HighlyAvailablePackage::preInstall
sqls::HighlyAvailablePackage::manageVsResources
sqls::Host
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0012_CATCSAP021211_.NET Framework 2.0.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0012.cab" Error Code : 2
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0012_CATCSAP021211_.NET Framework 2.0 LangPack.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0012.cab" Error Code : 2
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0012_CATCSAP021211_.NET Framework Upgrade Advisor.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0012.cab" Error Code : 2
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0012_CATCSAP021211_.NET Framework Upgrade Advisor LangPack.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0012.cab" Error Code : 2
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0012_CATCSAP021211_.NET Framework Windows Installer.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0012.cab" Error Code : 2
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0012_CATCSAP021211_.NET Framework Windows Installer LangPack.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0012.cab" Error Code : 2
Running: UploadDrWatsonLogAction at: 2007/2/19 19:56:20
Message pump returning: 1612

Core.log

Microsoft SQL Server 2005 Setup beginning at Mon Mar 19 19:48:44 2007
Process ID : 1864
\\Catcsdc021209\SQL\DISC1\setup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2007/2/19 19:48:44
Complete: LoadResourcesAction at: 2007/2/19 19:48:44, returned true
Running: ParseBootstrapOptionsAction at: 2007/2/19 19:48:44
Loaded DLL:\\Catcsdc021209\SQL\DISC1\xmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2007/2/19 19:48:44, returned true
Running: ValidateWinNTAction at: 2007/2/19 19:48:44
Complete: ValidateWinNTAction at: 2007/2/19 19:48:44, returned true
Running: ValidateMinOSAction at: 2007/2/19 19:48:44
Complete: ValidateMinOSAction at: 2007/2/19 19:48:44, returned true
Running: PerformSCCAction at: 2007/2/19 19:48:44
Complete: PerformSCCAction at: 2007/2/19 19:48:44, returned true
Running: ActivateLoggingAction at: 2007/2/19 19:48:44
Complete: ActivateLoggingAction at: 2007/2/19 19:48:44, 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__1864" returned false.
Running: PerformSCCAction2 at: 2007/2/19 19:48:44
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Loaded DLL:C:\WINDOWS\system32\msi.dll Version:3.1.4000.2435
Complete: PerformSCCAction2 at: 2007/2/19 19:48:44, returned true
Running: PerformDotNetCheck at: 2007/2/19 19:48:44
Complete: PerformDotNetCheck at: 2007/2/19 19:48:44, returned true
Running: ComponentUpdateAction at: 2007/2/19 19:48:44
Complete: ComponentUpdateAction at: 2007/2/19 19:49:3, returned true
Running: DetectLocalBootstrapAction at: 2007/2/19 19:49:3
Complete: DetectLocalBootstrapAction at: 2007/2/19 19:49:3, returned true
Running: LaunchLocalBootstrapAction at: 2007/2/19 19:49:3
Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run:
"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe" finished and returned: 1612
Aborting queue processing as nested installer has completed
Message pump returning: 1612

Thanks for any Help

Don

I am trying to install evaluation version and i am having the same problem.I ran the sqleval.exe, after downloading the file from microsoft website, but i dont see the sql enterprise component.Please let me know which one should i download , am i doing something wrong by not configuring the server properly.

sql

Having Trouble Installing Reporting Services

i am having some trouble installing SQl server Reporting Services.
well, in order to install the reporting services i have to install
Service
Pack 3a.
so through my installation of package 3a i am encoutering some trouble.
i was able to comlete the first part of the installation i receive

this error message: Instance name specified is invalid

so, my question is: once you have SQL Server installed, where can you
go to find the name of the instance
and once i find it, can i rename it?
i originally installed SQL Server a while ago. during the setup, i do
not recall a particular name i might have given it.<ajackson@.icstars.org> wrote in message
news:1111796152.315471.297270@.o13g2000cwo.googlegr oups.com...
>i am having some trouble installing SQl server Reporting Services.
> well, in order to install the reporting services i have to install
> Service
> Pack 3a.
> so through my installation of package 3a i am encoutering some trouble.
> i was able to comlete the first part of the installation i receive
> this error message: Instance name specified is invalid
> so, my question is: once you have SQL Server installed, where can you
> go to find the name of the instance
> and once i find it, can i rename it?
> i originally installed SQL Server a while ago. during the setup, i do
> not recall a particular name i might have given it.

See questions 12, 13 and 28. You can't rename an instance - you have to
install another one with the correct name, move your databases to it, and
then remove the original one.

http://support.microsoft.com/defaul...6&Product=sql2k

Simon

having trouble getting reporting services installed properly

Hi,
I am running Windows 2000 and VS 2003.
I installed Reporting Services with service pack 2.
When I type: in http://reportserver/reports I get an access denied 403 error.
When I go into IIS Manager and look for the Report folder properties I can't
find the Reports virtual directory. It does not exist.
So, how is it when I goto http://reportserver/reports I get a 403 error and
not a 404: File not found error.
The service is run as the executable: reportingservicesservice.exe
(discovered this through internet searches) on the machine, but when I search
for it, I can't find the file.
I have created a report and successfully viewed it in the VS 2003 Report
Designer, but the reporting services and Report Manager don't exist.
I do have this directory with lots of files, but I don't seem to have the
start page for Reporting Manaer anywhere on my system.
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services
Could someone please advise.
Thank You
ChrisDid you open the reportning services configuration manager (new with 2005)
and configure the 2 folders. In 2005 it doesnt automatically create the 2
virtual folders, you have to explicitly create them through the configuration
manager.
Go to reporting services configuration (it should be somewhere in your
"START --> All programs") and connect to your report server, and make sure
the virtual directory tabs are green checked. If not set them
"Chris" wrote:
> Hi,
> I am running Windows 2000 and VS 2003.
> I installed Reporting Services with service pack 2.
> When I type: in http://reportserver/reports I get an access denied 403 error.
> When I go into IIS Manager and look for the Report folder properties I can't
> find the Reports virtual directory. It does not exist.
> So, how is it when I goto http://reportserver/reports I get a 403 error and
> not a 404: File not found error.
> The service is run as the executable: reportingservicesservice.exe
> (discovered this through internet searches) on the machine, but when I search
> for it, I can't find the file.
> I have created a report and successfully viewed it in the VS 2003 Report
> Designer, but the reporting services and Report Manager don't exist.
> I do have this directory with lots of files, but I don't seem to have the
> start page for Reporting Manaer anywhere on my system.
> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services
> Could someone please advise.
> Thank You
> Chris|||Hi Nagini,
I am not using SQL Server 2005, I am using SQL Server 2000.
Thanks
Chris
"Nagini Indugula" wrote:
> Did you open the reportning services configuration manager (new with 2005)
> and configure the 2 folders. In 2005 it doesnt automatically create the 2
> virtual folders, you have to explicitly create them through the configuration
> manager.
> Go to reporting services configuration (it should be somewhere in your
> "START --> All programs") and connect to your report server, and make sure
> the virtual directory tabs are green checked. If not set them
> "Chris" wrote:
> > Hi,
> >
> > I am running Windows 2000 and VS 2003.
> >
> > I installed Reporting Services with service pack 2.
> >
> > When I type: in http://reportserver/reports I get an access denied 403 error.
> >
> > When I go into IIS Manager and look for the Report folder properties I can't
> > find the Reports virtual directory. It does not exist.
> >
> > So, how is it when I goto http://reportserver/reports I get a 403 error and
> > not a 404: File not found error.
> >
> > The service is run as the executable: reportingservicesservice.exe
> > (discovered this through internet searches) on the machine, but when I search
> > for it, I can't find the file.
> >
> > I have created a report and successfully viewed it in the VS 2003 Report
> > Designer, but the reporting services and Report Manager don't exist.
> >
> > I do have this directory with lots of files, but I don't seem to have the
> > start page for Reporting Manaer anywhere on my system.
> >
> > C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services
> >
> > Could someone please advise.
> >
> > Thank You
> >
> > Chris

Having trouble deploying a report

I've installed SQL Server 2005 express SP2 with SQL Server Reporting
Services, along with the Business Intelligence Development Studio from
the SQL Server Express Toolkit SP2. I've created a reports project
and a simple report that I'm trying to deploy. When I try to deploy,
I get prompted for a username and password. I've tried all the
username and password for this computer combinations I can think of,
but it doesn't recognize any of them. I have the virtual directory for
the SQL Reports set to 'integrated windows'. Any ideas about what I'm
missing?
-MichaelOn Jan 19, 7:07 pm, michael.sle...@.gmail.com wrote:
> I've installed SQL Server 2005 express SP2 with SQL Server Reporting
> Services, along with the Business Intelligence Development Studio from
> the SQL Server Express Toolkit SP2. I've created a reports project
> and a simple report that I'm trying to deploy. When I try to deploy,
> I get prompted for a username and password. I've tried all the
> username and password for this computer combinations I can think of,
> but it doesn't recognize any of them. I have the virtual directory for
> the SQL Reports set to 'integrated windows'. Any ideas about what I'm
> missing?
> -Michael
Have you created at least one user account in the Report Manager? If
you haven't, you will want to create a user account with at least
Browser privileges in the Report Manager, preferably set to your
current windows domain account (i.e., DOMAIN_NAME\UserName). Also, if
you are using Firefox or some other non-IE browser, the authentication
window always pops up. If this doesn't help, you may need to evaluate
the security on the Reports and ReportServer virtual directories in
IIS. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||Why not uploading the report using report manager?
http://localhost/reportS
Then "Upload Report"
See if you get an error message there, possibly more specific and post this
here.
Regards
Ralf Stofer
"EMartinez" wrote:
> On Jan 19, 7:07 pm, michael.sle...@.gmail.com wrote:
> > I've installed SQL Server 2005 express SP2 with SQL Server Reporting
> > Services, along with the Business Intelligence Development Studio from
> > the SQL Server Express Toolkit SP2. I've created a reports project
> > and a simple report that I'm trying to deploy. When I try to deploy,
> > I get prompted for a username and password. I've tried all the
> > username and password for this computer combinations I can think of,
> > but it doesn't recognize any of them. I have the virtual directory for
> > the SQL Reports set to 'integrated windows'. Any ideas about what I'm
> > missing?
> >
> > -Michael
>
> Have you created at least one user account in the Report Manager? If
> you haven't, you will want to create a user account with at least
> Browser privileges in the Report Manager, preferably set to your
> current windows domain account (i.e., DOMAIN_NAME\UserName). Also, if
> you are using Firefox or some other non-IE browser, the authentication
> window always pops up. If this doesn't help, you may need to evaluate
> the security on the Reports and ReportServer virtual directories in
> IIS. Hope this helps.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>|||On Jan 21, 2:35 pm, Ralf Stofer <RalfSto...@.discussions.microsoft.com>
wrote:
> Why not uploading the report using report manager?http://localhost/reportS
> Then "Upload Report"
> See if you get an error message there, possibly more specific and post this
> here.
> Regards
> Ralf Stofer
> "EMartinez" wrote:
> > On Jan 19, 7:07 pm, michael.sle...@.gmail.com wrote:
> > > I've installed SQL Server 2005 express SP2 with SQL Server Reporting
> > > Services, along with the Business Intelligence Development Studio from
> > > the SQL Server Express Toolkit SP2. I've created a reports project
> > > and a simple report that I'm trying to deploy. When I try to deploy,
> > > I get prompted for a username and password. I've tried all the
> > > username and password for this computer combinations I can think of,
> > > but it doesn't recognize any of them. I have the virtual directory for
> > > the SQL Reports set to 'integrated windows'. Any ideas about what I'm
> > > missing?
> > > -Michael
> > Have you created at least one user account in the Report Manager? If
> > you haven't, you will want to create a user account with at least
> > Browser privileges in the Report Manager, preferably set to your
> > current windows domain account (i.e., DOMAIN_NAME\UserName). Also, if
> > you are using Firefox or some other non-IE browser, the authentication
> > window always pops up. If this doesn't help, you may need to evaluate
> > the security on the Reports and ReportServer virtual directories in
> > IIS. Hope this helps.
> > Regards,
> > Enrique Martinez
> > Sr. Software Consultant
In order to upload a report via the Report Manager, the items I
mentioned above need to be in place beforehand.
Regards,
Enrique Martinez
Sr. Software Consultant

Having Problem With installation

Hi:
I have already installed QSL 2005 on a win 2003 machine. The installation was without erroe or something but when I open services I do not see any sql in there and when I open the management interface there is no machine detected there. Would you please help me to run this software. When in the management tool I try to connect to the server this is the error I get:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)

and when I try to surface area configuration this is my error message:

No SQL Server 2005 components were found on the specified computer. Either no components are installed, or you are not an administrator on this computer. (SQLSAC)

Thanks

Go to Add/Remove Programs from the Control Pannel. You should find an entry for "Microsoft SQL Server 2005" select it and click "Change" Once the dialog comes up you should see a "Report" button, click it. This will show you all of the SQL Server 2005 features installed. Copy and Paste this back to this thread.|||

===================================

No SQL Server 2005 components were found on the specified computer. Either no components are installed, or you are not an administrator on this computer. (SQLSAC)
=================================

and my SQL SErver says no instance has been found or installed on ur PC... i tried installing and uninstalling this atleast 4 times...i need help... i am encountering the same problem on another machine tooo...plzzz help me out

The configuration of two machines on which SQL servers produce this ERROR are

p4 2.4 Ghz, 512 MB ram, 845 intel original motherboard ,52 x cd R/W 80 gb HDD

AMD Athlon 64 Bit 3000 +, 512 MB ram, Asus motherboard ,52 x cd R/W 80 gb HDD

Operating System installed on two machines are ~~~> Windows XP 2002 Service pack 2

REport File is as follows

System Configuration Check

- WMI Service Requirement (Success)
Messages
* WMI Service Requirement
* Check Passed

- MSXML Requirement (Success)
Messages
* MSXML Requirement
* Check Passed

- Operating System Minimum Level Requirement (Success)
Messages
* Operating System Minimum Level Requirement
* Check Passed

- Operating System Service Pack Level Requirement. (Success)
Messages
* Operating System Service Pack Level Requirement.
* Check Passed

- SQL Server Edition Operating System Compatibility (Warning)
Messages
* SQL Server Edition Operating System Compatibility
* Some components of this edition of SQL Server are not supported on this operating system. For details, see 'Hardware and Software Requirements for Installing SQL Server 2005' in Microsoft SQL Server Books Online.

- Minimum Hardware Requirement (Warning)
Messages
* Minimum Hardware Requirement
* The current system does not meet the minimum hardware requirements for this SQL Server release. For detailed hardware and software requirements, see the readme file or SQL Server Books Online.

- IIS Feature Requirement (Success)
Messages
* IIS Feature Requirement
* Check Passed

- Pending Reboot Requirement (Success)
Messages
* Pending Reboot Requirement
* Check Passed

- Performance Monitor Counter Requirement (Success)
Messages
* Performance Monitor Counter Requirement
* Check Passed

- Default Installation Path Permission Requirement (Success)
Messages
* Default Installation Path Permission Requirement
* Check Passed

- Internet Explorer Requirement (Success)
Messages
* Internet Explorer Requirement
* Check Passed

- COM Plus Catalog Requirement (Success)
Messages
* COM Plus Catalog Requirement
* Check Passed

- ASP.Net Version Registration Requirement (Success)
Messages
* ASP.Net Version Registration Requirement
* Check Passed

- Minimum MDAC Version Requirement (Success)
Messages
* Minimum MDAC Version Requirement
* Check Passed

|||For the error msg you're getting it sounds like you're attempting to install the Enterprise Edition on Windows XP SP2. Enterprise Edition is not supported on Windows XP - only Windows 2000 Server and Windows 2003 Server.|||

Hi Bobby62,

Your error "No SQL Server 2005 components were found on the specified computer" can be caused if you installed SQL Server 2005 using Disc 2 of 2. I actually did this myself accidentally. I didn't realize there were two "Premium Technologies" CD's (those shiny discs are hard to read)! So I had accidentally done the installation from disc 2. The setup process appeared legit, when in fact it only installed the client apps.

In short, make sure you're installing SQL 2005 from disc 1 of 2.

Regards,

Doug

Having Problem With installation

Hi:
I have already installed QSL 2005 on a win 2003 machine. The installation was without erroe or something but when I open services I do not see any sql in there and when I open the management interface there is no machine detected there. Would you please help me to run this software. When in the management tool I try to connect to the server this is the error I get:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)

and when I try to surface area configuration this is my error message:

No SQL Server 2005 components were found on the specified computer. Either no components are installed, or you are not an administrator on this computer. (SQLSAC)

Thanks

Go to Add/Remove Programs from the Control Pannel. You should find an entry for "Microsoft SQL Server 2005" select it and click "Change" Once the dialog comes up you should see a "Report" button, click it. This will show you all of the SQL Server 2005 features installed. Copy and Paste this back to this thread.|||

===================================

No SQL Server 2005 components were found on the specified computer. Either no components are installed, or you are not an administrator on this computer. (SQLSAC)
=================================

and my SQL SErver says no instance has been found or installed on ur PC... i tried installing and uninstalling this atleast 4 times...i need help... i am encountering the same problem on another machine tooo...plzzz help me out

The configuration of two machines on which SQL servers produce this ERROR are

p4 2.4 Ghz, 512 MB ram, 845 intel original motherboard ,52 x cd R/W 80 gb HDD

AMD Athlon 64 Bit 3000 +, 512 MB ram, Asus motherboard ,52 x cd R/W 80 gb HDD

Operating System installed on two machines are ~~~> Windows XP 2002 Service pack 2

REport File is as follows

System Configuration Check

- WMI Service Requirement (Success)
Messages
* WMI Service Requirement
* Check Passed

- MSXML Requirement (Success)
Messages
* MSXML Requirement
* Check Passed

- Operating System Minimum Level Requirement (Success)
Messages
* Operating System Minimum Level Requirement
* Check Passed

- Operating System Service Pack Level Requirement. (Success)
Messages
* Operating System Service Pack Level Requirement.
* Check Passed

- SQL Server Edition Operating System Compatibility (Warning)
Messages
* SQL Server Edition Operating System Compatibility
* Some components of this edition of SQL Server are not supported on this operating system. For details, see 'Hardware and Software Requirements for Installing SQL Server 2005' in Microsoft SQL Server Books Online.

- Minimum Hardware Requirement (Warning)
Messages
* Minimum Hardware Requirement
* The current system does not meet the minimum hardware requirements for this SQL Server release. For detailed hardware and software requirements, see the readme file or SQL Server Books Online.

- IIS Feature Requirement (Success)
Messages
* IIS Feature Requirement
* Check Passed

- Pending Reboot Requirement (Success)
Messages
* Pending Reboot Requirement
* Check Passed

- Performance Monitor Counter Requirement (Success)
Messages
* Performance Monitor Counter Requirement
* Check Passed

- Default Installation Path Permission Requirement (Success)
Messages
* Default Installation Path Permission Requirement
* Check Passed

- Internet Explorer Requirement (Success)
Messages
* Internet Explorer Requirement
* Check Passed

- COM Plus Catalog Requirement (Success)
Messages
* COM Plus Catalog Requirement
* Check Passed

- ASP.Net Version Registration Requirement (Success)
Messages
* ASP.Net Version Registration Requirement
* Check Passed

- Minimum MDAC Version Requirement (Success)
Messages
* Minimum MDAC Version Requirement
* Check Passed

|||For the error msg you're getting it sounds like you're attempting to install the Enterprise Edition on Windows XP SP2. Enterprise Edition is not supported on Windows XP - only Windows 2000 Server and Windows 2003 Server.|||

Hi Bobby62,

Your error "No SQL Server 2005 components were found on the specified computer" can be caused if you installed SQL Server 2005 using Disc 2 of 2. I actually did this myself accidentally. I didn't realize there were two "Premium Technologies" CD's (those shiny discs are hard to read)! So I had accidentally done the installation from disc 2. The setup process appeared legit, when in fact it only installed the client apps.

In short, make sure you're installing SQL 2005 from disc 1 of 2.

Regards,

Doug

Having 2 CALCULATE statements no longer works after installing SP2!!!

I received the following email from a collegue of mine:

I think we may have found an issue with SQL SERVER 2005 SP2

1. Some of the Analysis Services Properties when you click the advanced tab are missing!

2. The MDX scrip behaviour is not the same.

In our cubes we had two CALCULATE statements - first to aggregate the data as normal, then some code to calculate MTD and YTD figures and then another CALCULATE statement. This enabled us to calculate percentages later on in the script without having to sum up all the data at leaf levels first.

With SP2, this no longer works!!! All our percentages are now being added up (like all other measures) which is clearly wrong!

I am not sure how to deal with this. Do we need to inform the clients not to upgrade to SP2 OR can Microsoft resolve this?

Any ideas?

Actually, two CALCULATE statements are the same as one CALCULATE statement w.r.t. aggregating data. The only difference could be if you have unary operators/custom rollups etc. So I suspect the use of two CALCULATE in your scenario was redundant. There is probably something else going on. If you will paste your MDX Script here, perhaps somebody will be able to figure it out.|||Thanks for the reply Mosha. I will get my collegue to post an example.|||

Hello Mosha,

Attached is the MDX Script.

All it does is - FIRST calculates MTD and YTD values

Then calcualtes some percentages.

Prior to Service Pack 2, these percentage calculations displayed correct number when MTD was selected on the FLOW dimension.

Post Service Pack 2, its seems that the percentages are getting calculated first and then the MTD logic is being applied resulting in the addition of all percentages from the lowest level which is not the desired behaviour.

I have tried removing the second calculate statement and it still does not work in sp2.

thanks for your help.

/*
The CALCULATE command controls the aggregation of leaf cells in the cube.
If the CALCULATE command is deleted or modified, the data within the cube is affected.
You should edit this command only if you manually specify how the cube is aggregated.
*/
CALCULATE;

/* Calculate Values for Flow Dimension */
SCOPE([Flow].[KeyFlow].&[MTD]);
THIS = (Sum(PeriodsToDate([Period].[Calendar].[Month],[Period].[Calendar].CurrentMember),([Measures].CurrentMember, [Flow].[KeyFlow].&[P])));
END SCOPE;

SCOPE([Flow].[KeyFlow].&[YTD]);
THIS = (Sum(PeriodsToDate([Period].[Calendar].[Year],[Period].[Calendar].CurrentMember),([Measures].CurrentMember, [Flow].[KeyFlow].&[P])));
END SCOPE;

/*Calculate again for the flow calculations to aggregate */
CALCULATE;

/*Scope Total Traffic */
SCOPE([Measure Type].[Measure Type].[Measure].&[14]);
[Measures].[Dealership Measure Value]= [Measure Type].[Measure Type].[Measure].&[1] + [Measure Type].[Measure Type].[Measure].&[2] + [Measure Type].[Measure Type].[Measure].&[3];
END SCOPE;

/*Scope %Leads From Traffic */
SCOPE([Measure Type].[Measure Type].[Measure].&[16]);
[Measures].[Dealership Measure Value]=
CASE [Measure Type].[Measure Type].[Measure].&[14]
WHEN 0 THEN null
WHEN null THEN null
ELSE [Measure Type].[Measure Type].[Measure].&[4]/[Measure Type].[Measure Type].[Measure].&[14]
END;
END SCOPE;

|||IN THIs MDX Script, the second CALCULATE does nothing and can be safely removed with either SP2 or SP1 or RTM. The problem is somewhere else. It does look like a regression in SP2 to me, because according to this script, it really should compute percentages after MTD and YTD. I recommend opening a case with product support.|||

Just to add to the issue.

The percentages are not even added up. I am not sure what values it is calculating. We will raise a call with support.

Punita

|||I am having a problem with MTD() and YTD() after installing SP2. I have had to repair alot of queries since we went to SP2. I replaced the MTD and YTD functions with the PeriodsToDate() function and I was back in business. Hope that helps.

have a win 2003 server,sql server 2000 8.00.194

I wanted to install SQL Server 2000 Reporting Services. For this i need to
install service pack 3a for sql server 2000. When I try to install sql
server 2000 sp3a I get the following error:
Setup was unable to validate the logged on user. Press Retry to enter
another option, or Cancel to exit setup.
what is the problem here and whats the solution?
i got a few pointers from http://www.aspfaq.com/show.asp?id=2440. i tried
all but the problem still exists
This problem occurs when an open local shared memory connection is pending
when the Setup program starts. When you install SQL Server 2000 SP4, the
Setup program stops the SQL Server 2000 services. If a local shared memory
connection is pending, the local shared memory listener does not successfully
start after the SQL Server 2000 services are restarted.
When the application or service that has the local shared memory connection
is on the same computer as an instance of SQL Server, Microsoft Windows
interprocess communication (IPC) components are used for the connection.
Local named pipes and local shared memory are examples of Windows IPC
components. For example, you may experience this problem if you installed
Microsoft SQL Server 2000 Reporting Services on the same computer that is
running SQL Server.
for Solution see below...
http://support.microsoft.com/default.aspx/kb/891085
"deepakr" wrote:

> I wanted to install SQL Server 2000 Reporting Services. For this i need to
> install service pack 3a for sql server 2000. When I try to install sql
> server 2000 sp3a I get the following error:
> Setup was unable to validate the logged on user. Press Retry to enter
> another option, or Cancel to exit setup.
> what is the problem here and whats the solution?
> i got a few pointers from http://www.aspfaq.com/show.asp?id=2440. i tried
> all but the problem still exists
>
|||The problem occurs when I install SQL Server 2000 SP3a. I have not installed
the Reporting services yet.
"Vishal Gandhi" wrote:
[vbcol=seagreen]
> This problem occurs when an open local shared memory connection is pending
> when the Setup program starts. When you install SQL Server 2000 SP4, the
> Setup program stops the SQL Server 2000 services. If a local shared memory
> connection is pending, the local shared memory listener does not successfully
> start after the SQL Server 2000 services are restarted.
> When the application or service that has the local shared memory connection
> is on the same computer as an instance of SQL Server, Microsoft Windows
> interprocess communication (IPC) components are used for the connection.
> Local named pipes and local shared memory are examples of Windows IPC
> components. For example, you may experience this problem if you installed
> Microsoft SQL Server 2000 Reporting Services on the same computer that is
> running SQL Server.
> for Solution see below...
> http://support.microsoft.com/default.aspx/kb/891085
>
> "deepakr" wrote:

have a win 2003 server,sql server 2000 8.00.194

I wanted to install SQL Server 2000 Reporting Services. For this i need to
install service pack 3a for sql server 2000. When I try to install sql
server 2000 sp3a I get the following error:
Setup was unable to validate the logged on user. Press Retry to enter
another option, or Cancel to exit setup.
what is the problem here and whats the solution?
i got a few pointers from http://www.aspfaq.com/show.asp?id=2440. i tried
all but the problem still existsThis problem occurs when an open local shared memory connection is pending
when the Setup program starts. When you install SQL Server 2000 SP4, the
Setup program stops the SQL Server 2000 services. If a local shared memory
connection is pending, the local shared memory listener does not successfull
y
start after the SQL Server 2000 services are restarted.
When the application or service that has the local shared memory connection
is on the same computer as an instance of SQL Server, Microsoft Windows
interprocess communication (IPC) components are used for the connection.
Local named pipes and local shared memory are examples of Windows IPC
components. For example, you may experience this problem if you installed
Microsoft SQL Server 2000 Reporting Services on the same computer that is
running SQL Server.
for Solution see below...
http://support.microsoft.com/default.aspx/kb/891085
"deepakr" wrote:

> I wanted to install SQL Server 2000 Reporting Services. For this i need to
> install service pack 3a for sql server 2000. When I try to install sql
> server 2000 sp3a I get the following error:
> Setup was unable to validate the logged on user. Press Retry to enter
> another option, or Cancel to exit setup.
> what is the problem here and whats the solution?
> i got a few pointers from http://www.aspfaq.com/show.asp?id=2440. i tried
> all but the problem still exists
>|||The problem occurs when I install SQL Server 2000 SP3a. I have not installed
the Reporting services yet.
"Vishal Gandhi" wrote:
[vbcol=seagreen]
> This problem occurs when an open local shared memory connection is pending
> when the Setup program starts. When you install SQL Server 2000 SP4, the
> Setup program stops the SQL Server 2000 services. If a local shared memory
> connection is pending, the local shared memory listener does not successfu
lly
> start after the SQL Server 2000 services are restarted.
> When the application or service that has the local shared memory connectio
n
> is on the same computer as an instance of SQL Server, Microsoft Windows
> interprocess communication (IPC) components are used for the connection.
> Local named pipes and local shared memory are examples of Windows IPC
> components. For example, you may experience this problem if you installed
> Microsoft SQL Server 2000 Reporting Services on the same computer that is
> running SQL Server.
> for Solution see below...
> http://support.microsoft.com/default.aspx/kb/891085
>
> "deepakr" wrote:
>sql

have a win 2003 server,sql server 2000 8.00.194

I wanted to install SQL Server 2000 Reporting Services. For this i need to
install service pack 3a for sql server 2000. When I try to install sql
server 2000 sp3a I get the following error:
Setup was unable to validate the logged on user. Press Retry to enter
another option, or Cancel to exit setup.
what is the problem here and whats the solution?
i got a few pointers from http://www.aspfaq.com/show.asp?id=2440. i tried
all but the problem still existsThis problem occurs when an open local shared memory connection is pending
when the Setup program starts. When you install SQL Server 2000 SP4, the
Setup program stops the SQL Server 2000 services. If a local shared memory
connection is pending, the local shared memory listener does not successfully
start after the SQL Server 2000 services are restarted.
When the application or service that has the local shared memory connection
is on the same computer as an instance of SQL Server, Microsoft Windows
interprocess communication (IPC) components are used for the connection.
Local named pipes and local shared memory are examples of Windows IPC
components. For example, you may experience this problem if you installed
Microsoft SQL Server 2000 Reporting Services on the same computer that is
running SQL Server.
for Solution see below...
http://support.microsoft.com/default.aspx/kb/891085
"deepakr" wrote:
> I wanted to install SQL Server 2000 Reporting Services. For this i need to
> install service pack 3a for sql server 2000. When I try to install sql
> server 2000 sp3a I get the following error:
> Setup was unable to validate the logged on user. Press Retry to enter
> another option, or Cancel to exit setup.
> what is the problem here and whats the solution?
> i got a few pointers from http://www.aspfaq.com/show.asp?id=2440. i tried
> all but the problem still exists
>|||The problem occurs when I install SQL Server 2000 SP3a. I have not installed
the Reporting services yet.
"Vishal Gandhi" wrote:
> This problem occurs when an open local shared memory connection is pending
> when the Setup program starts. When you install SQL Server 2000 SP4, the
> Setup program stops the SQL Server 2000 services. If a local shared memory
> connection is pending, the local shared memory listener does not successfully
> start after the SQL Server 2000 services are restarted.
> When the application or service that has the local shared memory connection
> is on the same computer as an instance of SQL Server, Microsoft Windows
> interprocess communication (IPC) components are used for the connection.
> Local named pipes and local shared memory are examples of Windows IPC
> components. For example, you may experience this problem if you installed
> Microsoft SQL Server 2000 Reporting Services on the same computer that is
> running SQL Server.
> for Solution see below...
> http://support.microsoft.com/default.aspx/kb/891085
>
> "deepakr" wrote:
> > I wanted to install SQL Server 2000 Reporting Services. For this i need to
> > install service pack 3a for sql server 2000. When I try to install sql
> > server 2000 sp3a I get the following error:
> >
> > Setup was unable to validate the logged on user. Press Retry to enter
> > another option, or Cancel to exit setup.
> >
> > what is the problem here and whats the solution?
> >
> > i got a few pointers from http://www.aspfaq.com/show.asp?id=2440. i tried
> > all but the problem still exists
> >

Hardware Specifications

Is there any documented

hardware specification for Analysis Services 2005/2000? This is one question asked frequently to me by people implementing AS 2005. I could not find any documents on this. It would be great if any recommendations are available on this.

Thanks,

S Suresh

Such information is often provided by hardware vendors.

For instance;
http://h18004.www1.hp.com/products/servers/software/microsoft/sqlserver2005.html?jumpid=reg_R1002_USEN
www.dell.com/sql

You can also take a look at the existing case studies like Project REAL http://www.microsoft.com/sql/solutions/bi/projectreal.mspx
see what are the data sizes and what hardware used.

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

Hanging or lockup issue with SQL Server and Terminal Services 2000 on NT 4 Domain Server

Hi all,

Have a situation that my company has never run across before. Client
is running NT4 for the domain server, using terminal services 2000 and
running an application with a SQL Server backend and they are
experiencing locking problems. Once one person gets locked out then
everyone trying to access that tables is also locked out as a result.
It is not specific to a certain User, or module within the
application. It's not a specific time of the day (like when a backup
would be running) and sometimes it's in the middle of the night when
there are actually less Users on the system.

We have 500 customers using this application. Most are using SQL
Server backend, alot of the newer customers are using Terminal
Services, and the number of Users is not accessive as compared to our
other customers. THe only difference is that I do not specifically
know of another client with an NT4 Domain server in the mix.

We actually switched to SQL Server as the recommended back end due to
locking issues using SQLBase because SQL Server is row locking and
SQLBase is page locking. Since making this change we have stopped
seeing the locking for years until now. Is this a SQLServer issue or
issue with the NT Domain server?

Anyone have any ideas?

Thanks
A"ACP" <Akzsurtep@.aol.com> wrote in message
news:f8ce0b90.0409271213.66baade5@.posting.google.c om...
> Hi all,
> Have a situation that my company has never run across before. Client
> is running NT4 for the domain server, using terminal services 2000 and
> running an application with a SQL Server backend and they are
> experiencing locking problems. Once one person gets locked out then
> everyone trying to access that tables is also locked out as a result.
> It is not specific to a certain User, or module within the
> application. It's not a specific time of the day (like when a backup
> would be running) and sometimes it's in the middle of the night when
> there are actually less Users on the system.
> We have 500 customers using this application. Most are using SQL
> Server backend, alot of the newer customers are using Terminal
> Services, and the number of Users is not accessive as compared to our
> other customers. THe only difference is that I do not specifically
> know of another client with an NT4 Domain server in the mix.
> We actually switched to SQL Server as the recommended back end due to
> locking issues using SQLBase because SQL Server is row locking and
> SQLBase is page locking. Since making this change we have stopped
> seeing the locking for years until now. Is this a SQLServer issue or
> issue with the NT Domain server?
> Anyone have any ideas?
> Thanks
> A

It's hard to say what's going on without more information - what version of
MSSQL do you have and which OS is it running on? What is the application and
how does it connect to MSSQL (ODBC, OLE DB)? Also, since it used to work
fine, has anything changed recently such as a new servicepack installation?

As for the locking itself, what do you mean that someone is "locked out"? Do
you mean their connection times out, that they're the victim of a deadlock,
or something else? Have you checked what sp_who2 and sp_lock say about which
connections are blocked and what objects are locked by the blocking
connection(s)? Is there anything unusual in the MSSQL log at the time the
problem happens?

It sounds like one connection locks a table, then doesn't release it
(perhaps an uncommitted transaction - you can check with DBCC OPENTRAN), but
you will have to look into what the connection is actually doing when the
issue occurs.

Simon|||It's definitely a lock on the SQL Server database. The problem is it
is across the board as far as what Users are doing when it happens.
It is grabbing a lock on a table and then locking others out in a
chain reaction. But it's difficult to pinpoint since it's happening
to Users performing different transactions and hitting different
tables in the database. So I'll check using sp_lock and try and
narrow it down a little more. And then I'll look into the option of
using DBCC OPENTRAN if I can narrow it down.

Thanks for the help|||http://www.sommarskog.se/sqlutil/aba_lockinfo.html

This may be of some help to you.

Akzsurtep@.aol.com (ACP) wrote in message news:<f8ce0b90.0409291713.3d7cd6a@.posting.google.com>...
> It's definitely a lock on the SQL Server database. The problem is it
> is across the board as far as what Users are doing when it happens.
> It is grabbing a lock on a table and then locking others out in a
> chain reaction. But it's difficult to pinpoint since it's happening
> to Users performing different transactions and hitting different
> tables in the database. So I'll check using sp_lock and try and
> narrow it down a little more. And then I'll look into the option of
> using DBCC OPENTRAN if I can narrow it down.
> Thanks for the help

Handling Data Integrity Issues in SQL2000

Hello,
I’m looking for some help with analysis services.
I ahve a very simple fact table which has 2 columns
Account Number and Investment Objective.
Fact table
Account Number Investment Objective
12345678 A
22222222 A
33333333 B
44444444 X
A dimension is needed for the investment objective
So I have a lookup table which is
Value Description
A Growth
B No-Growth
There is not an X value in the lookup table so when I look at the count for
accounts I only get 3. The account 44444444 never shows up.
Is there a way to have 44444444 or any other account that might get a value
not in the lookup table to fall into an ‘Unknown’ type description?
I understand the best way to solve is to make sure I have a value in the
lookup table for every value that is in the investment objective fact, the
problem is I cant control what might get added to it, and we want to be able
to have an unknown description and have everything that falls out of the
range of the lookup go into that. This will allow the users of the cube to
find the bad entries and fix them.
Of course this is sample data and the real tables have millions of records
and 100’s of columns, but I think the basic concept applies.
Any help or a direction to go in would be greatly appreciated. BTW this is
SQL2000
ThanksHello AppDev,
I am assuming you are using a Star schema in a SQL Server database
somewhere. The Star Schema is used as a basis for the OLAP cube you
are creating.
Remember Analysis Services requires all dimension records to be unique
and fact records to have a relationship with all dimensions. This means
Fact records that do not have a correlating dimension record will not
appear in your cube. (This only happens when you included dimensions
that do not have a relationship with all fact records)
There is a quick solution to this. Create an 'Unknown' record in
your dimension table. When populating the fact table you can return the
unknown surrogate key value to join to the unknown dimension record.
This will make unknown records appear in your cube.
Hope this helps
Myles Matheson
Data Warehouse Architect|||(microsoft.public.sqlserver.olap is a better newsgroup for a posting like
this, but here goes)
My first gut feel is that you should not be allowing this to occur. This is
basic RI between a fact table and the dimension. You should be processing
your dimension to pickup additions prior to processing the fact table. This
will ensure that this doesn't occur if RI is in-place on the RDBMS.
The row is disappearing from the fact table because the default SQL
statement is an inner join between the fact table and the dimension table.
Thus the row will not be returned to Analysis Services at all . . . we
simply don't see it. The RDBMS eliminates it before we get it.
In SQL2K, you best option is to create an UNKNOWN member in the base
dimension and then load your fact data through a view. In the view use a
CASE clause with an EXISTS and replace the FK being returned based on
whether or not that key exists. If it doesn't exist, then return the UNKNOWN
member.
In SQL2K5, the system supports an unknown member directly and you can load
data w/ an error configuration which tells it to assign invalid FKs with the
system generated unknown member directly.
--
Dave Wickert [MSFT]
dwickert@.online.microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"appdevtech" <appdevtech@.online.nospam> wrote in message
news:44BBA514-66F1-4FDD-A0D2-11E6BB6D2F13@.microsoft.com...
> Hello,
> I'm looking for some help with analysis services.
> I ahve a very simple fact table which has 2 columns
> Account Number and Investment Objective.
> Fact table
> Account Number Investment Objective
> 12345678 A
> 22222222 A
> 33333333 B
> 44444444 X
> A dimension is needed for the investment objective
> So I have a lookup table which is
> Value Description
> A Growth
> B No-Growth
> There is not an X value in the lookup table so when I look at the count
> for
> accounts I only get 3. The account 44444444 never shows up.
> Is there a way to have 44444444 or any other account that might get a
> value
> not in the lookup table to fall into an 'Unknown' type description?
> I understand the best way to solve is to make sure I have a value in the
> lookup table for every value that is in the investment objective fact, the
> problem is I cant control what might get added to it, and we want to be
> able
> to have an unknown description and have everything that falls out of the
> range of the lookup go into that. This will allow the users of the cube
> to
> find the bad entries and fix them.
> Of course this is sample data and the real tables have millions of records
> and 100's of columns, but I think the basic concept applies.
> Any help or a direction to go in would be greatly appreciated. BTW this
> is
> SQL2000
> Thanks
>|||Thanks Dave,
My gut feeling is to fix the RI issues first also, but in this case I can
use the cube to identify the issues, versus catching the data during import
then writing a report to notify the users of the inconsistent data.
When you say "create an UNKNOWN member in the base dimension” do you mean
adding an additional record to my dimension table?
Value Description
A Growth
B No-Growth
X Unknown
Then in the view if it does not exist, return X(Unknown)?
"Dave Wickert [MSFT]" wrote:

> (microsoft.public.sqlserver.olap is a better newsgroup for a posting like
> this, but here goes)
> My first gut feel is that you should not be allowing this to occur. This i
s
> basic RI between a fact table and the dimension. You should be processing
> your dimension to pickup additions prior to processing the fact table. Thi
s
> will ensure that this doesn't occur if RI is in-place on the RDBMS.
> The row is disappearing from the fact table because the default SQL
> statement is an inner join between the fact table and the dimension table.
> Thus the row will not be returned to Analysis Services at all . . . we
> simply don't see it. The RDBMS eliminates it before we get it.
> In SQL2K, you best option is to create an UNKNOWN member in the base
> dimension and then load your fact data through a view. In the view use a
> CASE clause with an EXISTS and replace the FK being returned based on
> whether or not that key exists. If it doesn't exist, then return the UNKNO
WN
> member.
> In SQL2K5, the system supports an unknown member directly and you can load
> data w/ an error configuration which tells it to assign invalid FKs with t
he
> system generated unknown member directly.
> --
> Dave Wickert [MSFT]
> dwickert@.online.microsoft.com
> Program Manager
> BI SystemsTeam
> SQL BI Product Unit (Analysis Services)
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
> "appdevtech" <appdevtech@.online.nospam> wrote in message
> news:44BBA514-66F1-4FDD-A0D2-11E6BB6D2F13@.microsoft.com...
>
>|||Hello Myles,
For example, you could add a new record in the dimension table with
"value"="unknown". You could create a view fact1 and use this as the fact
table when you create a cube
create view fact1 as
select f.AccountNumber,
case when exists (select d.value from dim1 d where d.value=f.objectvalue )
then f.[Investment Objective]
else 'unknown'
end
as InvestmentObjective,
f.number
from fact f
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
| Thread-Topic: Handling Data Integrity Issues in SQL2000
| thread-index: AcVzZJNkPr6fSXC8RMqPvlgseXtMiA==
| X-WBNR-Posting-Host: 12.155.246.10
| From: "examnotes" <appdevtech@.online.nospam>
| References: <44BBA514-66F1-4FDD-A0D2-11E6BB6D2F13@.microsoft.com>
<#BtbY5rcFHA.1324@.tk2msftngp13.phx.gbl>
| Subject: Re: Handling Data Integrity Issues in SQL2000
| Date: Fri, 17 Jun 2005 10:47:05 -0700
| Lines: 98
| Message-ID: <6CC7E76E-3E1C-49BE-B976-71D0D694B5AB@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 8bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.datawarehouse
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.datawarehouse:1828
| X-Tomcat-NG: microsoft.public.sqlserver.datawarehouse
|
| Thanks Dave,
| My gut feeling is to fix the RI issues first also, but in this case I can
| use the cube to identify the issues, versus catching the data during
import
| then writing a report to notify the users of the inconsistent data.
|
| When you say "create an UNKNOWN member in the base dimension” do you
mean
| adding an additional record to my dimension table?
|
| Value Description
| A Growth
| B No-Growth
| X Unknown
|
| Then in the view if it does not exist, return X(Unknown)?
|
| "Dave Wickert [MSFT]" wrote:
|
| > (microsoft.public.sqlserver.olap is a better newsgroup for a posting
like
| > this, but here goes)
| >
| > My first gut feel is that you should not be allowing this to occur.
This is
| > basic RI between a fact table and the dimension. You should be
processing
| > your dimension to pickup additions prior to processing the fact table.
This
| > will ensure that this doesn't occur if RI is in-place on the RDBMS.
| >
| > The row is disappearing from the fact table because the default SQL
| > statement is an inner join between the fact table and the dimension
table.
| > Thus the row will not be returned to Analysis Services at all . . . we
| > simply don't see it. The RDBMS eliminates it before we get it.
| >
| > In SQL2K, you best option is to create an UNKNOWN member in the base
| > dimension and then load your fact data through a view. In the view use
a
| > CASE clause with an EXISTS and replace the FK being returned based on
| > whether or not that key exists. If it doesn't exist, then return the
UNKNOWN
| > member.
| >
| > In SQL2K5, the system supports an unknown member directly and you can
load
| > data w/ an error configuration which tells it to assign invalid FKs
with the
| > system generated unknown member directly.
| > --
| > Dave Wickert [MSFT]
| > dwickert@.online.microsoft.com
| > Program Manager
| > BI SystemsTeam
| > SQL BI Product Unit (Analysis Services)
| > --
| > This posting is provided "AS IS" with no warranties, and confers no
rights.
| >
| >
| > "appdevtech" <appdevtech@.online.nospam> wrote in message
| > news:44BBA514-66F1-4FDD-A0D2-11E6BB6D2F13@.microsoft.com...
| > > Hello,
| > > I'm looking for some help with analysis services.
| > >
| > > I ahve a very simple fact table which has 2 columns
| > > Account Number and Investment Objective.
| > >
| > > Fact table
| > > Account Number Investment Objective
| > > 12345678 A
| > > 22222222 A
| > > 33333333 B
| > > 44444444 X
| > >
| > > A dimension is needed for the investment objective
| > > So I have a lookup table which is
| > >
| > > Value Description
| > > A Growth
| > > B No-Growth
| > >
| > > There is not an X value in the lookup table so when I look at the
count
| > > for
| > > accounts I only get 3. The account 44444444 never shows up.
| > > Is there a way to have 44444444 or any other account that might get a
| > > value
| > > not in the lookup table to fall into an 'Unknown' type description?
| > >
| > > I understand the best way to solve is to make sure I have a value in
the
| > > lookup table for every value that is in the investment objective
fact, the
| > > problem is I cant control what might get added to it, and we want to
be
| > > able
| > > to have an unknown description and have everything that falls out of
the
| > > range of the lookup go into that. This will allow the users of the
cube
| > > to
| > > find the bad entries and fix them.
| > >
| > > Of course this is sample data and the real tables have millions of
records
| > > and 100's of columns, but I think the basic concept applies.
| > >
| > > Any help or a direction to go in would be greatly appreciated. BTW
this
| > > is
| > > SQL2000
| > > Thanks
| > >
| >
| >
| >
|

Handling Data Integrity Issues in SQL2000

Hello,
I’m looking for some help with analysis services.
I ahve a very simple fact table which has 2 columns
Account Number and Investment Objective.
Fact table
Account NumberInvestment Objective
12345678A
22222222A
33333333B
44444444X
A dimension is needed for the investment objective
So I have a lookup table which is
ValueDescription
AGrowth
BNo-Growth
There is not an X value in the lookup table so when I look at the count for
accounts I only get 3. The account 44444444 never shows up.
Is there a way to have 44444444 or any other account that might get a value
not in the lookup table to fall into an ‘Unknown’ type description?
I understand the best way to solve is to make sure I have a value in the
lookup table for every value that is in the investment objective fact, the
problem is I cant control what might get added to it, and we want to be able
to have an unknown description and have everything that falls out of the
range of the lookup go into that. This will allow the users of the cube to
find the bad entries and fix them.
Of course this is sample data and the real tables have millions of records
and 100’s of columns, but I think the basic concept applies.
Any help or a direction to go in would be greatly appreciated. BTW this is
SQL2000
Thanks
Hello AppDev,
I am assuming you are using a Star schema in a SQL Server database
somewhere. The Star Schema is used as a basis for the OLAP cube you
are creating.
Remember Analysis Services requires all dimension records to be unique
and fact records to have a relationship with all dimensions. This means
Fact records that do not have a correlating dimension record will not
appear in your cube. (This only happens when you included dimensions
that do not have a relationship with all fact records)
There is a quick solution to this. Create an 'Unknown' record in
your dimension table. When populating the fact table you can return the
unknown surrogate key value to join to the unknown dimension record.
This will make unknown records appear in your cube.
Hope this helps
Myles Matheson
Data Warehouse Architect
|||(microsoft.public.sqlserver.olap is a better newsgroup for a posting like
this, but here goes)
My first gut feel is that you should not be allowing this to occur. This is
basic RI between a fact table and the dimension. You should be processing
your dimension to pickup additions prior to processing the fact table. This
will ensure that this doesn't occur if RI is in-place on the RDBMS.
The row is disappearing from the fact table because the default SQL
statement is an inner join between the fact table and the dimension table.
Thus the row will not be returned to Analysis Services at all . . . we
simply don't see it. The RDBMS eliminates it before we get it.
In SQL2K, you best option is to create an UNKNOWN member in the base
dimension and then load your fact data through a view. In the view use a
CASE clause with an EXISTS and replace the FK being returned based on
whether or not that key exists. If it doesn't exist, then return the UNKNOWN
member.
In SQL2K5, the system supports an unknown member directly and you can load
data w/ an error configuration which tells it to assign invalid FKs with the
system generated unknown member directly.
Dave Wickert [MSFT]
dwickert@.online.microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
This posting is provided "AS IS" with no warranties, and confers no rights.
"appdevtech" <appdevtech@.online.nospam> wrote in message
news:44BBA514-66F1-4FDD-A0D2-11E6BB6D2F13@.microsoft.com...
> Hello,
> I'm looking for some help with analysis services.
> I ahve a very simple fact table which has 2 columns
> Account Number and Investment Objective.
> Fact table
> Account Number Investment Objective
> 12345678 A
> 22222222 A
> 33333333 B
> 44444444 X
> A dimension is needed for the investment objective
> So I have a lookup table which is
> Value Description
> A Growth
> B No-Growth
> There is not an X value in the lookup table so when I look at the count
> for
> accounts I only get 3. The account 44444444 never shows up.
> Is there a way to have 44444444 or any other account that might get a
> value
> not in the lookup table to fall into an 'Unknown' type description?
> I understand the best way to solve is to make sure I have a value in the
> lookup table for every value that is in the investment objective fact, the
> problem is I cant control what might get added to it, and we want to be
> able
> to have an unknown description and have everything that falls out of the
> range of the lookup go into that. This will allow the users of the cube
> to
> find the bad entries and fix them.
> Of course this is sample data and the real tables have millions of records
> and 100's of columns, but I think the basic concept applies.
> Any help or a direction to go in would be greatly appreciated. BTW this
> is
> SQL2000
> Thanks
>
|||Thanks Dave,
My gut feeling is to fix the RI issues first also, but in this case I can
use the cube to identify the issues, versus catching the data during import
then writing a report to notify the users of the inconsistent data.
When you say "create an UNKNOWN member in the base dimension” do you mean
adding an additional record to my dimension table?
Value Description
A Growth
B No-Growth
X Unknown
Then in the view if it does not exist, return X(Unknown)?
"Dave Wickert [MSFT]" wrote:

> (microsoft.public.sqlserver.olap is a better newsgroup for a posting like
> this, but here goes)
> My first gut feel is that you should not be allowing this to occur. This is
> basic RI between a fact table and the dimension. You should be processing
> your dimension to pickup additions prior to processing the fact table. This
> will ensure that this doesn't occur if RI is in-place on the RDBMS.
> The row is disappearing from the fact table because the default SQL
> statement is an inner join between the fact table and the dimension table.
> Thus the row will not be returned to Analysis Services at all . . . we
> simply don't see it. The RDBMS eliminates it before we get it.
> In SQL2K, you best option is to create an UNKNOWN member in the base
> dimension and then load your fact data through a view. In the view use a
> CASE clause with an EXISTS and replace the FK being returned based on
> whether or not that key exists. If it doesn't exist, then return the UNKNOWN
> member.
> In SQL2K5, the system supports an unknown member directly and you can load
> data w/ an error configuration which tells it to assign invalid FKs with the
> system generated unknown member directly.
> --
> Dave Wickert [MSFT]
> dwickert@.online.microsoft.com
> Program Manager
> BI SystemsTeam
> SQL BI Product Unit (Analysis Services)
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "appdevtech" <appdevtech@.online.nospam> wrote in message
> news:44BBA514-66F1-4FDD-A0D2-11E6BB6D2F13@.microsoft.com...
>
>
|||Hello Myles,
For example, you could add a new record in the dimension table with
"value"="unknown". You could create a view fact1 and use this as the fact
table when you create a cube
create view fact1 as
select f.AccountNumber,
case when exists (select d.value from dim1 d where d.value=f.objectvalue )
then f.[Investment Objective]
else 'unknown'
end
as InvestmentObjective,
f.number
from fact f
Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
| Thread-Topic: Handling Data Integrity Issues in SQL2000
| thread-index: AcVzZJNkPr6fSXC8RMqPvlgseXtMiA==
| X-WBNR-Posting-Host: 12.155.246.10
| From: "=?Utf-8?B?YXBwZGV2dGVjaA==?=" <appdevtech@.online.nospam>
| References: <44BBA514-66F1-4FDD-A0D2-11E6BB6D2F13@.microsoft.com>
<#BtbY5rcFHA.1324@.tk2msftngp13.phx.gbl>
| Subject: Re: Handling Data Integrity Issues in SQL2000
| Date: Fri, 17 Jun 2005 10:47:05 -0700
| Lines: 98
| Message-ID: <6CC7E76E-3E1C-49BE-B976-71D0D694B5AB@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 8bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.datawarehouse
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.datawarehouse:1828
| X-Tomcat-NG: microsoft.public.sqlserver.datawarehouse
|
| Thanks Dave,
| My gut feeling is to fix the RI issues first also, but in this case I can
| use the cube to identify the issues, versus catching the data during
import
| then writing a report to notify the users of the inconsistent data.
|
| When you say "create an UNKNOWN member in the base dimension” do you
mean
| adding an additional record to my dimension table?
|
| Value Description
| A Growth
| B No-Growth
| X Unknown
|
| Then in the view if it does not exist, return X(Unknown)?
|
| "Dave Wickert [MSFT]" wrote:
|
| > (microsoft.public.sqlserver.olap is a better newsgroup for a posting
like
| > this, but here goes)
| >
| > My first gut feel is that you should not be allowing this to occur.
This is
| > basic RI between a fact table and the dimension. You should be
processing
| > your dimension to pickup additions prior to processing the fact table.
This
| > will ensure that this doesn't occur if RI is in-place on the RDBMS.
| >
| > The row is disappearing from the fact table because the default SQL
| > statement is an inner join between the fact table and the dimension
table.
| > Thus the row will not be returned to Analysis Services at all . . . we
| > simply don't see it. The RDBMS eliminates it before we get it.
| >
| > In SQL2K, you best option is to create an UNKNOWN member in the base
| > dimension and then load your fact data through a view. In the view use
a
| > CASE clause with an EXISTS and replace the FK being returned based on
| > whether or not that key exists. If it doesn't exist, then return the
UNKNOWN
| > member.
| >
| > In SQL2K5, the system supports an unknown member directly and you can
load
| > data w/ an error configuration which tells it to assign invalid FKs
with the
| > system generated unknown member directly.
| > --
| > Dave Wickert [MSFT]
| > dwickert@.online.microsoft.com
| > Program Manager
| > BI SystemsTeam
| > SQL BI Product Unit (Analysis Services)
| > --
| > This posting is provided "AS IS" with no warranties, and confers no
rights.
| >
| >
| > "appdevtech" <appdevtech@.online.nospam> wrote in message
| > news:44BBA514-66F1-4FDD-A0D2-11E6BB6D2F13@.microsoft.com...
| > > Hello,
| > > I'm looking for some help with analysis services.
| > >
| > > I ahve a very simple fact table which has 2 columns
| > > Account Number and Investment Objective.
| > >
| > > Fact table
| > > Account Number Investment Objective
| > > 12345678 A
| > > 22222222 A
| > > 33333333 B
| > > 44444444 X
| > >
| > > A dimension is needed for the investment objective
| > > So I have a lookup table which is
| > >
| > > Value Description
| > > A Growth
| > > B No-Growth
| > >
| > > There is not an X value in the lookup table so when I look at the
count
| > > for
| > > accounts I only get 3. The account 44444444 never shows up.
| > > Is there a way to have 44444444 or any other account that might get a
| > > value
| > > not in the lookup table to fall into an 'Unknown' type description?
| > >
| > > I understand the best way to solve is to make sure I have a value in
the
| > > lookup table for every value that is in the investment objective
fact, the
| > > problem is I cant control what might get added to it, and we want to
be
| > > able
| > > to have an unknown description and have everything that falls out of
the
| > > range of the lookup go into that. This will allow the users of the
cube
| > > to
| > > find the bad entries and fix them.
| > >
| > > Of course this is sample data and the real tables have millions of
records
| > > and 100's of columns, but I think the basic concept applies.
| > >
| > > Any help or a direction to go in would be greatly appreciated. BTW
this
| > > is
| > > SQL2000
| > > Thanks
| > >
| >
| >
| >
|