i think this feature is so crappy compare to the one from 2000.
Because once you create the linked server you are not able to see the tables as you can do it on 2000.
how do you expect someone to query the tables if its not there.
Has anyone run into the issue of installing SP1 on a 2003 R2 server?
I have seen a post or two on other sites but I cannot seem to find them again.
Install goes great up until it comes to the upgrading of SSIS (Integration Services).
At that point is fails with the error of:
A recently applied update, KB913090, failed to install.
This is a dialog box that I hit the "send error report" button. It then goes to the upgrading of the Client Components (CC) and fails with the same error message of:
A recently applied update, KB913090, failed to install.
The ugrade the continues after I hit the same "send error report"button.
ALL of the other steps complete with SUCESSFULLY. Only the SSIS and Client Components show a failed status in the Installation Prog
In the Installation Complete screen, I can highlight both the SSIS and CC and see an additional error of:
Unable to install Windows Installer MSP file
I then can hit the View Log button (which I have done for the SSIS step) and see the error log but I am having a tough time making heads or tails of it.
I have attached the output from the SSIS error log below.
I have a couple of questions:
1. Is the install of SP1 good for all the other steps that completed successfully
2. Has anyone had issues with installing SP1 on a Windows 2003 R2 server? I have installed SP1 on other Windows 2003 servers NOT running R2 and it ran like a champ.
Thanks ALL!
====== ERROR LOG FROM SSIS UPGRADE ============================================
01/07/2007 19:23:23.247 ================================================================================
01/07/2007 19:23:23.247 Hotfix package launched
01/07/2007 19:23:23.747 Product discovery successfully completed during the install process for DTS
01/07/2007 19:23:23.762 SP Level check successfully completed during the install process for DTS
01/07/2007 19:23:23.778 Product language check successfully completed during the install process for DTS
01/07/2007 19:23:23.793 Product version check successfully completed during the install process for DTS
01/07/2007 19:23:23.825 Command-line instance name check completed during the install process
01/07/2007 19:23:23.840 Baseline build check completed during the install process
01/07/2007 19:28:41.393 Attempting to install instance: DTS
01/07/2007 19:28:41.408 Attempting to install target: AUS02DB13
01/07/2007 19:28:41.440 Attempting to check for locked files: sqlrun_dts.msp
01/07/2007 19:28:41.502 Attempting to check for locked files: \AUS02DB13g$2fe15a257eaedfc36c121fc912HotFixDTSFilessqlrun_dts.msp
01/07/2007 19:28:41.518 Creating MSP locked file check log at: C:WINDOWSHotfixDTS9LogsDTS9_Hotfix_KB913090_sqlrun_dts.msp.out
01/07/2007 19:28:48.799 MSP returned 1602: The user cancels installation.
01/07/2007 19:28:49.017 Successfully checked file: \AUS02DB13g$2fe15a257eaedfc36c121fc912HotFixDTSFilessqlrun_dts.msp
01/07/2007 19:28:49.033 Successfully opened registry key: SystemCurrentControlSetControlSession Manager
01/07/2007 19:28:49.064 Successfully read registry key: PendingFileRenameOperations
01/07/2007 19:28:49.080 Multi-string values:
01/07/2007 19:28:49.096 ??g:a4be8c9b1bce3ffa869bbb5137
01/07/2007 19:28:49.111 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerShared9.0.2047.0
C:Program FilesMicrosoft SQL ServerShareddbghelp.dll
01/07/2007 19:28:49.127 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerSharedSqlDumper.exe
01/07/2007 19:28:49.142 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerSharedSqlDumper.exe
01/07/2007 19:28:49.158 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerSharedSqlDumper.exe
01/07/2007 19:28:49.174 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerSharedsqlsqm.exe
01/07/2007 19:28:49.205 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSBinndtsinstall.exe
01/07/2007 19:28:49.221 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsResourcesmsmdsrv.rll
01/07/2007 19:28:49.236 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsResourcesmsmdsrv.rll
01/07/2007 19:28:49.252 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsResourcesmsmdsrv.rll
01/07/2007 19:28:49.267 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsmsmdlocal.dll
01/07/2007 19:28:49.283 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsmsmdlocal.dll
01/07/2007 19:28:49.299 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsmsmdlocal.dll
01/07/2007 19:28:49.314 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponents9.0.2047.0
C:Program FilesMicrosoft SQL ServerSharedmsmdlo~1.dll
01/07/2007 19:28:49.330 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServerCe.Dts.Provider9.0.242.0__89845dcd8080cc91Microsoft.SqlServerCe.Dts.Provider.dll
01/07/2007 19:28:49.361 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.DataStorage9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.DataStorage.dll
01/07/2007 19:28:49.377 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.CustomControls9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.CustomControls.dll
01/07/2007 19:28:49.392 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.WizardFramework9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.WizardFramework.dll
01/07/2007 19:28:49.408 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.AnalysisServices.Xmla9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.XMLA.dll
01/07/2007 19:28:49.424 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.OlapEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.OlapEnum.dll
01/07/2007 19:28:49.439 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSTasksenMicrosoft.SqlServer.ActiveXScriptTask.xml
01/07/2007 19:28:49.455 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.ActiveXScriptTaskUtil9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.ActiveXScriptTaskUtil.dll
01/07/2007 19:28:49.470 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.ActiveXScriptTaskUtil9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.ActiveXScriptTaskUtil.dll
01/07/2007 19:28:49.486 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.ActiveXScriptTaskUtil9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.ActiveXScriptTaskUtil.dll
01/07/2007 19:28:49.517 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.ActiveXScriptTask9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.ActiveXScriptTask.dll
01/07/2007 19:28:49.533 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSBinnMicrosoft.SqlServer.ActiveXScriptTaskUtil.dll
01/07/2007 19:28:49.549 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSTasksMicrosoft.SqlServer.ActiveXScriptTask.dll
01/07/2007 19:28:49.580 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.DataTransformationServices.Controls9.0.242.0__89845dcd8080cc91Microsoft.DataTransformationServices.Controls.DLL
01/07/2007 19:28:49.595 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSBinnDTSWizard.exe
01/07/2007 19:28:49.611 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5SDKAssembliesMicrosoft.SqlServer.TxScript.dll
01/07/2007 19:28:49.627 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsMicrosoft.SqlServer.TxScript.dll
01/07/2007 19:28:49.642 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.TxScript9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.TxScript.dll
01/07/2007 19:28:49.674 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxSampling.dll
01/07/2007 19:28:49.689 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxSampling.dll
01/07/2007 19:28:49.705 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxSampling.dll
01/07/2007 19:28:49.720 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxRowCount.dll
01/07/2007 19:28:49.752 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxRowCount.dll
01/07/2007 19:28:49.767 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxRowCount.dll
01/07/2007 19:28:49.783 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.Dts.DtsClient9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.Dts.DtsClient.dll
01/07/2007 19:28:49.799 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.DataReaderDest9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.DataReaderDest.dll
01/07/2007 19:28:49.814 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSBinnMicrosoft.SqlServer.Dts.DtsClient.dll
01/07/2007 19:28:49.830 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsMicrosoft.SqlServer.DataReaderDest.dll
01/07/2007 19:28:49.830 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSTasksenMicrosoft.SqlServer.TransferSqlServerObjectsTask.xml
01/07/2007 19:28:49.845 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.TransferSqlServerObjectsTask9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.TransferSqlServerObjectsTask.dll
01/07/2007 19:28:49.877 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSTasksMicrosoft.SqlServer.TransferSqlServerObjectsTask.dll
01/07/2007 19:28:49.892 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSTasksenMicrosoft.SqlServer.TransferStoredProceduresTask.xml
01/07/2007 19:28:49.908 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSTasksenMicrosoft.SqlServer.TransferLoginsTask.xml
01/07/2007 19:28:49.924 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSTasksenMicrosoft.SqlServer.TransferJobsTask.xml
01/07/2007 19:28:49.939 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSTasksenMicrosoft.SqlServer.TransferErrorMessagesTask.xml
01/07/2007 19:28:49.970 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSTasksenMicrosoft.SqlServer.TransferDatabasesTask.xml
01/07/2007 19:28:49.986 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSTasksMicrosoft.SqlServer.TransferStoredProceduresTask.dll
01/07/2007 19:28:50.002 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSTasksMicrosoft.SqlServer.TransferLoginsTask.dll
01/07/2007 19:28:50.002 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSTasksMicrosoft.SqlServer.TransferJobsTask.dll
01/07/2007 19:28:50.033 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSTasksMicrosoft.SqlServer.TransferErrorMessagesTask.dll
01/07/2007 19:28:50.033 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSTasksMicrosoft.SqlServer.TransferDatabasesTask.dll
01/07/2007 19:28:50.049 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSTasksMicrosoft.SqlServer.TransferObjectsTask.dll
01/07/2007 19:28:50.064 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.TransferStoredProceduresTask9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.TransferStoredProceduresTask.dll
01/07/2007 19:28:50.080 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.TransferLoginsTask9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.TransferLoginsTask.dll
01/07/2007 19:28:50.095 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.TransferJobsTask9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.TransferJobsTask.dll
01/07/2007 19:28:50.111 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.TransferErrorMessagesTask9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.TransferErrorMessagesTask.dll
01/07/2007 19:28:50.111 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.TransferDatabasesTask9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.TransferDatabasesTask.dll
01/07/2007 19:28:50.127 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.TransferObjectsTask9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.TransferObjectsTask.dll
01/07/2007 19:28:50.142 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.DtsTransferProvider9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.DtsTransferProvider.dll
01/07/2007 19:28:50.158 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.TableTransferGeneratorTask9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.TableTransferGeneratorTask.dll
01/07/2007 19:28:50.174 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSBinnMicrosoft.SqlServer.DtsTransferProvider.dll
01/07/2007 19:28:50.189 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSTasksMicrosoft.SqlServer.TableTransferGeneratorTask.dll
01/07/2007 19:28:50.189 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxTermExtraction.dll
01/07/2007 19:28:50.205 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxTermExtraction.dll
01/07/2007 19:28:50.220 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxTermExtraction.dll
01/07/2007 19:28:50.236 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxTermLookup.dll
01/07/2007 19:28:50.252 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxTermLookup.dll
01/07/2007 19:28:50.267 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxTermLookup.dll
01/07/2007 19:28:50.283 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSBinnResources.90.2047.0
E:MSSQLMSSQLSS2K5DTSBinnResourcesdts.rll
01/07/2007 19:28:50.283 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSBinnResourcesdtsconn.rll
01/07/2007 19:28:50.299 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSBinnResourcesdtsconn.rll
01/07/2007 19:28:50.314 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSBinnResourcesdtsconn.rll
01/07/2007 19:28:50.330 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSForEachEnumeratorsenMicrosoft.SqlServer.ForEachAdoEnumerator.xml
01/07/2007 19:28:50.345 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSForEachEnumeratorsenMicrosoft.SqlServer.ForEachSMOEnumerator.xml
01/07/2007 19:28:50.377 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSConnectionsenMicrosoft.SqlServer.ManagedConnections.xml
01/07/2007 19:28:50.392 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSBinnDTSPipelinePerf.dll
01/07/2007 19:28:50.408 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSBinnResourcesdtspipeline.rll
01/07/2007 19:28:50.408 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSBinnResourcesdtspipeline.rll
01/07/2007 19:28:50.424 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSBinnResourcesdtspipeline.rll
01/07/2007 19:28:50.439 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSTasksenMicrosoft.SqlServer.FtpTask.xml
01/07/2007 19:28:50.455 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.FtpTask9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.FtpTask.dll
01/07/2007 19:28:50.470 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSTasksMicrosoft.SqlServer.FtpTask.dll
01/07/2007 19:28:50.486 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSTasksenMicrosoft.SqlServer.ExecProcTask.xml
01/07/2007 19:28:50.517 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSTasksenMicrosoft.SqlServer.SendMailTask.xml
01/07/2007 19:28:50.549 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSTasksenMicrosoft.SqlServer.MSMQTask.xml
01/07/2007 19:28:50.580 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.MSMQUtil9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.MSMQUtil.dll
01/07/2007 19:28:50.595 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.MSMQUtil9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.MSMQUtil.dll
01/07/2007 19:28:50.595 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.MSMQUtil9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.MSMQUtil.dll
01/07/2007 19:28:50.611 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.MSMQTask9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.MSMQTask.dll
01/07/2007 19:28:50.627 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSBinnMicrosoft.SqlServer.MSMQUtil.dll
01/07/2007 19:28:50.642 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSBinnMicrosoft.SqlServer.MSMQUtil.dll
01/07/2007 19:28:50.658 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSBinnMicrosoft.SqlServer.MSMQUtil.dll
01/07/2007 19:28:50.674 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSTasksMicrosoft.SqlServer.MSMQTask.dll
01/07/2007 19:28:50.689 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxMulticast.dll
01/07/2007 19:28:50.705 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxMulticast.dll
01/07/2007 19:28:50.705 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxMulticast.dll
01/07/2007 19:28:50.720 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsCommandDest.dll
01/07/2007 19:28:50.736 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsCommandDest.dll
01/07/2007 19:28:50.752 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsCommandDest.dll
01/07/2007 19:28:50.767 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxFileInserter.dll
01/07/2007 19:28:50.767 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxFileInserter.dll
01/07/2007 19:28:50.799 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxFileInserter.dll
01/07/2007 19:28:50.845 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxFileExtractor.dll
01/07/2007 19:28:50.845 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxFileExtractor.dll
01/07/2007 19:28:50.861 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxFileExtractor.dll
01/07/2007 19:28:50.877 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxLineage.dll
01/07/2007 19:28:50.892 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxLineage.dll
01/07/2007 19:28:50.908 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxLineage.dll
01/07/2007 19:28:50.924 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxUnPivot.dll
01/07/2007 19:28:50.924 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxUnPivot.dll
01/07/2007 19:28:50.955 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxUnPivot.dll
01/07/2007 19:28:50.955 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponents.90.2047.0
E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxPivot.dll
01/07/2007 19:28:50.970 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxMergeJoin.dll
01/07/2007 19:28:50.986 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxMergeJoin.dll
01/07/2007 19:28:51.002 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxMergeJoin.dll
01/07/2007 19:28:51.017 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponents.90.2047.0
E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxUnAll.dll
01/07/2007 19:28:51.033 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxSort.dll
01/07/2007 19:28:51.033 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxSort.dll
01/07/2007 19:28:51.049 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxSort.dll
01/07/2007 19:28:51.064 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxSplit.dll
01/07/2007 19:28:51.080 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxSplit.dll
01/07/2007 19:28:51.080 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxSplit.dll
01/07/2007 19:28:51.095 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxLookup.dll
01/07/2007 19:28:51.111 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxLookup.dll
01/07/2007 19:28:51.127 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxLookup.dll
01/07/2007 19:28:51.142 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxGroupDups.dll
01/07/2007 19:28:51.158 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxGroupDups.dll
01/07/2007 19:28:51.158 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxGroupDups.dll
01/07/2007 19:28:51.174 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxDerived.dll
01/07/2007 19:28:51.189 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxDerived.dll
01/07/2007 19:28:51.205 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxDerived.dll
01/07/2007 19:28:51.220 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxDataConvert.dll
01/07/2007 19:28:51.236 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxDataConvert.dll
01/07/2007 19:28:51.252 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxDataConvert.dll
01/07/2007 19:28:51.267 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxCopyMap.dll
01/07/2007 19:28:51.267 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxCopyMap.dll
01/07/2007 19:28:51.283 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxCopyMap.dll
01/07/2007 19:28:51.299 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxCharMap.dll
01/07/2007 19:28:51.314 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxCharMap.dll
01/07/2007 19:28:51.330 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxCharMap.dll
01/07/2007 19:28:51.345 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxBestMatch.dll
01/07/2007 19:28:51.345 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxBestMatch.dll
01/07/2007 19:28:51.361 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxBestMatch.dll
01/07/2007 19:28:51.377 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxAgg.dll
01/07/2007 19:28:51.392 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxAgg.dll
01/07/2007 19:28:51.408 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsTxAgg.dll
01/07/2007 19:28:51.424 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSTasksenMicrosoft.SqlServer.XmlTask.xml
01/07/2007 19:28:51.439 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5dtsBinnatchparser90.dll
01/07/2007 19:28:51.455 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.SQLTask9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.SQLTask.dll
01/07/2007 19:28:51.470 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSBinnSQLTaskConnections.dll
01/07/2007 19:28:51.470 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSBinnSQLTaskConnections.dll
01/07/2007 19:28:51.486 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSBinnSQLTaskConnections.dll
01/07/2007 19:28:51.502 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSTasksMicrosoft.SqlServer.SQLTask.dll
01/07/2007 19:28:51.533 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsSqlDest.dll
01/07/2007 19:28:51.549 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsSqlDest.dll
01/07/2007 19:28:51.580 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsSqlDest.dll
01/07/2007 19:28:51.595 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5SDKAssembliesMicrosoft.SqlServer.ScriptTask.dll
01/07/2007 19:28:51.595 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.ScriptTask9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.ScriptTask.dll
01/07/2007 19:28:51.611 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSTasksMicrosoft.SqlServer.ScriptTask.dll
01/07/2007 19:28:51.627 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsRecordSetDest.dll
01/07/2007 19:28:51.642 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsRecordSetDest.dll
01/07/2007 19:28:51.658 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsRecordSetDest.dll
01/07/2007 19:28:51.674 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsRawSource.dll
01/07/2007 19:28:51.674 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsRawSource.dll
01/07/2007 19:28:51.705 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsRawSource.dll
01/07/2007 19:28:51.705 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsRawDest.dll
01/07/2007 19:28:51.720 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsRawDest.dll
01/07/2007 19:28:51.736 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsRawDest.dll
01/07/2007 19:28:51.752 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSTasksenMicrosoft.SqlServer.ASTasks.xml
01/07/2007 19:28:51.767 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.ASTasks9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.ASTasks.dll
01/07/2007 19:28:51.783 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSTasksMicrosoft.SqlServer.ASTasks.dll
01/07/2007 19:28:51.799 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsOleDbSrc.dll
01/07/2007 19:28:51.799 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsOleDbSrc.dll
01/07/2007 19:28:51.830 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsOleDbSrc.dll
01/07/2007 19:28:51.845 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsOleDbDest.dll
01/07/2007 19:28:51.845 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsOleDbDest.dll
01/07/2007 19:28:51.861 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsOleDbDest.dll
01/07/2007 19:28:51.892 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsFlatFileDest.dll
01/07/2007 19:28:51.908 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsFlatFileDest.dll
01/07/2007 19:28:51.908 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsFlatFileDest.dll
01/07/2007 19:28:51.924 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsFlatFileSrc.dll
01/07/2007 19:28:51.955 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsFlatFileSrc.dll
01/07/2007 19:28:51.955 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsFlatFileSrc.dll
01/07/2007 19:28:51.970 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSTasksenMicrosoft.SqlServer.FileSystemTask.xml
01/07/2007 19:28:51.986 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.FileSystemTask9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.FileSystemTask.dll
01/07/2007 19:28:52.017 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSTasksMicrosoft.SqlServer.FileSystemTask.dll
01/07/2007 19:28:52.033 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSBinnExecPackageTask.dll
01/07/2007 19:28:52.049 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSTasksenMicrosoft.SqlServer.DmQueryTask.xml
01/07/2007 19:28:52.064 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.DMQueryTask9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.DmQueryTask.dll
01/07/2007 19:28:52.064 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSTasksMicrosoft.SqlServer.DmQueryTask.dll
01/07/2007 19:28:52.095 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSTasksenMicrosoft.SqlServer.BulkInsertTask.xml
01/07/2007 19:28:52.111 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BulkInsertTaskConnections9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.BulkInsertTaskConnections.dll
01/07/2007 19:28:52.127 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BulkInsertTaskConnections9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.BulkInsertTaskConnections.dll
01/07/2007 19:28:52.142 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BulkInsertTaskConnections9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.BulkInsertTaskConnections.dll
01/07/2007 19:28:52.158 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.BulkInsertTask9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.BulkInsertTask.dll
01/07/2007 19:28:52.174 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSBinnMicrosoft.SqlServer.BulkInsertTaskConnections.dll
01/07/2007 19:28:52.189 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSTasksMicrosoft.SqlServer.BulkInsertTask.dll
01/07/2007 19:28:52.205 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSTasksenMicrosoft.SqlServer.WMIEWTask.xml
01/07/2007 19:28:52.220 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSTasksenMicrosoft.SqlServer.WMIDRTask.xml
01/07/2007 19:28:52.236 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSTasksenMicrosoft.SqlServer.WebServiceTask.xml
01/07/2007 19:28:52.252 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.WebServiceTask9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.WebServiceTask.dll
01/07/2007 19:28:52.267 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.MaintenancePlanTasks9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.MaintenancePlanTasks.dll
01/07/2007 19:28:52.283 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSTasksMicrosoft.SqlServer.WebServiceTask.dll
01/07/2007 19:28:52.299 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSTasksMicrosoft.SqlServer.MaintenancePlanTasks.dll
01/07/2007 19:28:52.314 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsResourcesdtspipeline.rll
01/07/2007 19:28:52.330 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsResourcesdtspipeline.rll
01/07/2007 19:28:52.345 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsResourcesdtspipeline.rll
01/07/2007 19:28:52.345 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsexceldest.dll
01/07/2007 19:28:52.377 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsexceldest.dll
01/07/2007 19:28:52.392 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsexceldest.dll
01/07/2007 19:28:52.392 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsexcelsrc.dll
01/07/2007 19:28:52.408 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsexcelsrc.dll
01/07/2007 19:28:52.439 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsexcelsrc.dll
01/07/2007 19:28:52.439 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsMicrosoft.SqlServer.XMLSrc.dll
01/07/2007 19:28:52.455 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSPipelineComponentsMicrosoft.SqlServer.ADONETSrc.dll
01/07/2007 19:28:52.470 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.XmlSrc9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.XMLSrc.dll
01/07/2007 19:28:52.486 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.ADONETSrc9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.ADONETSrc.dll
01/07/2007 19:28:52.502 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.PipelineHost9.0.242.0__89845dcd8080cc91Microsoft.SQLServer.PipelineHost.dll
01/07/2007 19:28:52.517 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSBinnDTSPipeline.dll
01/07/2007 19:28:52.533 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.ForEachNodeListEnumerator9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.ForEachNodeListEnumerator.dll
01/07/2007 19:28:52.549 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.ForEachSMOEnumerator9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.ForEachSMOEnumerator.dll
01/07/2007 19:28:52.564 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32DTEParseMgd9.0.242.0__89845dcd8080cc91DTEParseMgd.dll
01/07/2007 19:28:52.580 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32DTEParseMgd9.0.242.0__89845dcd8080cc91DTEParseMgd.dll
01/07/2007 19:28:52.595 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32DTEParseMgd9.0.242.0__89845dcd8080cc91DTEParseMgd.dll
01/07/2007 19:28:52.595 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSBinn.90.2047.0
E:MSSQLMSSQLSS2K5DTSBinnDTSComEx.dll
01/07/2007 19:28:52.611 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSBinndtsmsg.dll
01/07/2007 19:28:52.642 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSBinnDTSLog.dll
01/07/2007 19:28:52.642 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSBinn.90.2047.0
E:MSSQLMSSQLSS2K5DTSBinnDtsUt.dll
01/07/2007 19:28:52.658 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSBinnDTS.dll
01/07/2007 19:28:52.674 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSBinn.90.2047.0
E:MSSQLMSSQLSS2K5DTSBinnDTEParsM.dll
01/07/2007 19:28:52.705 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5DTSBinn.90.2047.0
E:MSSQLMSSQLSS2K5DTSForEachEnumeratorsNodeList.dll
01/07/2007 19:28:52.705 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSForEachEnumeratorsForEachFileEnumerator.dll
01/07/2007 19:28:52.720 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSForEachEnumeratorsForEachFileEnumerator.dll
01/07/2007 19:28:52.736 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSForEachEnumeratorsForEachFileEnumerator.dll
01/07/2007 19:28:52.752 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSForEachEnumeratorsMicrosoft.SqlServer.ForEachSMOEnumerator.dll
01/07/2007 19:28:52.767 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5DTSBinnMsDtsSrvr.exe
01/07/2007 19:28:52.783 Failed to read version information for the following file: C:Program FilesMicrosoft.NETADOMD.NETenMicrosoft.AnalysisServices.AdomdClient.xml
01/07/2007 19:28:52.799 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft.NETADOMD.NETMicrosoft.AnalysisServices.AdomdClient.dll
01/07/2007 19:28:52.814 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.AnalysisServices.AdomdClient9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.AdomdClient.dll
01/07/2007 19:28:52.830 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerSharedmsasxpress.dll
01/07/2007 19:28:52.845 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerSharedmsasxpress.dll
01/07/2007 19:28:52.861 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerSharedmsasxpress.dll
01/07/2007 19:28:52.877 Failed to read version information for the following file: E:MSSQLMSSQLSS2K5ToolsBinnResources
E:MSSQLMSSQLSS2K5ToolsBinnResourcessqlcm.xml
01/07/2007 19:28:52.877 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5ToolsBinnResourcesSqlManager.rll
01/07/2007 19:28:52.908 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5ToolsBinnResourcesSqlManager.rll
01/07/2007 19:28:52.924 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5ToolsBinnResourcesSqlManager.rll
01/07/2007 19:28:52.939 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5ToolsinnSqlManager.dll
01/07/2007 19:28:52.939 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5ToolsinnSqlManager.dll
01/07/2007 19:28:52.970 Failed to read associated hotfix build information for the following file: E:MSSQLMSSQLSS2K5ToolsinnSqlManager.dll
01/07/2007 19:28:52.986 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerSharedsqlsvcsync.dll
01/07/2007 19:28:52.986 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerSharedsqlsvcsync.dll
01/07/2007 19:28:53.002 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerSharedsqlsvcsync.dll
01/07/2007 19:28:53.017 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerSharedsqlsecacctchg.dll
01/07/2007 19:28:53.033 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerSharedsqlsecacctchg.dll
01/07/2007 19:28:53.049 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerSharedsqlsecacctchg.dll
01/07/2007 19:28:53.064 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerSharedsqlftacct.dll
01/07/2007 19:28:53.064 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerSharedsqlftacct.dll
01/07/2007 19:28:53.095 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerSharedsqlftacct.dll
01/07/2007 19:28:53.111 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerSharedisacctchange.dll
01/07/2007 19:28:53.111 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerSharedisacctchange.dll
01/07/2007 19:28:53.127 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerSharedisacctchange.dll
01/07/2007 19:28:53.158 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerSharedsvrenumapi.dll
01/07/2007 19:28:53.174 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerSharedsvrenumapi.dll
01/07/2007 19:28:53.189 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerSharedsvrenumapi.dll
01/07/2007 19:28:53.189 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerShared.90.2047.0
C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.Rmo9.0.242.0__89845dcd8080cc91Rmo.dll
01/07/2007 19:28:53.205 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.AnalysisServices9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.DLL
01/07/2007 19:28:53.236 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.DataWarehouse.Interfaces9.0.242.0__89845dcd8080cc91Microsoft.DataWarehouse.Interfaces.DLL
01/07/2007 19:28:53.252 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.RegSvrEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.RegSvrEnum.dll
01/07/2007 19:28:53.252 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll
01/07/2007 19:28:53.267 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll
01/07/2007 19:28:53.299 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll
01/07/2007 19:28:53.299 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.ServiceBrokerEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.ServiceBrokerEnum.dll
01/07/2007 19:28:53.314 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.WmiEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.WmiEnum.dll
01/07/2007 19:28:53.330 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.SqlEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.SqlEnum.dll
01/07/2007 19:28:53.345 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.SmoEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.SmoEnum.dll
01/07/2007 19:28:53.361 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.Smo9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.Smo.dll
01/07/2007 19:28:53.377 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerSharedSqlSAC.exe
01/07/2007 19:28:53.392 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerSharedMicrosoft.SqlSac.Public.dll
01/07/2007 19:28:53.392 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.msxml6_interop6.0.0.0__89845dcd8080cc91Microsoft.SqlServer.msxml6_interop.dll
01/07/2007 19:28:53.517 Attempting to install file: sqlrun_dts.msp
01/07/2007 19:28:53.548 Attempting to install file: \AUS02DB13g$2fe15a257eaedfc36c121fc912HotFixDTSFilessqlrun_dts.msp
01/07/2007 19:28:53.564 Creating MSP install log file at: C:WINDOWSHotfixDTS9LogsDTS9_Hotfix_KB913090_sqlrun_dts.msp.log
01/07/2007 19:28:53.580 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller
01/07/2007 19:28:53.580 Failed to read registry key: Debug
01/07/2007 19:29:48.375 MSP returned 1603: A fatal error occurred during installation.
01/07/2007 19:29:48.672 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller
01/07/2007 19:29:48.687 Failed to read registry key: Debug
01/07/2007 19:29:48.687 Unable to install MSP file: \AUS02DB13g$2fe15a257eaedfc36c121fc912HotFixDTSFilessqlrun_dts.msp
01/07/2007 19:29:48.703 The following exception occurred: Unable to install Windows Installer MSP file Date: 01/07/2007 19:29:48.703 File: depotsqlvaultsetupmainsetupsqlsesqlsedllcopyengine.cpp Line: 856
01/07/2007 19:29:48.750
01/07/2007 19:29:48.765 Product Status Summary:
01/07/2007 19:29:48.781 Product: SQL Server Native Client
01/07/2007 19:29:48.797 SQL Server Native Client (RTM ) - Success
01/07/2007 19:29:48.812
01/07/2007 19:29:48.828 Product: Setup Support Files
01/07/2007 19:29:48.844 Setup Support Files (RTM ) - Success
01/07/2007 19:29:48.844
01/07/2007 19:29:48.859 Product: Database Services
01/07/2007 19:29:48.875 Database Services (SP1 2047 ENU) - Success
01/07/2007 19:29:48.890
01/07/2007 19:29:48.906 Product: Integration Services
01/07/2007 19:29:48.922 Integration Services (SP1 ENU) - Failure
01/07/2007 19:29:48.937 Details: Unable to install Windows Installer MSP file
01/07/2007 19:29:48.953
01/07/2007 19:29:48.969 Product: Client Components
01/07/2007 19:29:48.969 Client Components (SP1 2047 ENU) - Not Applied
01/07/2007 19:29:48.984
01/07/2007 19:29:49.015 Product: MSXML 6.0 Parser
01/07/2007 19:29:49.062 MSXML 6.0 Parser (RTM ) - Not Applied
01/07/2007 19:29:49.078
01/07/2007 19:29:49.094 Product: SQLXML4
01/07/2007 19:29:49.109 SQLXML4 (RTM ) - Not Applied
01/07/2007 19:29:49.109
01/07/2007 19:29:49.140 Product: Backward Compatibility
01/07/2007 19:29:49.156 Backward Compatibility (RTM ) - Not Applied
01/07/2007 19:29:49.156
01/07/2007 19:29:49.172 Product: Microsoft SQL Server VSS Writer
01/07/2007 19:29:49.187 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
01/07/2007 19:29:49.203
I am in need of some answers on SS2K5 Encryption and possible issues when used in a clustered(replicated) configuration as well as having the encryption work on a Test/UAT configuration.
Here is the scenerio:
ServerA - is the Primary/Active server in a NeverFail cluster. NeverFail is a replication method like MS Clustering is except NF replicates the server to EXACT mirrors of each other.
ServerA has lets say 2 client DBs (actually we have 10-20 but for simplicity we will say 2.)
ServerB is the Secondary/Passive node.
First question is ... what issues may I run into if I encrypt the 2 clients needed data in the DBs and we then have a failover. I figure we should not see an issue if NeverFail is replicating everything including the machines SIDs.
Now for the second question:
We also have a Test/UAT server that we restore backups from the production clusters. On this server we have upwards of 60+ DBs from 8 different NeverFail clusters.
What are the issues that I may encounter in this scenerio?
I thought that each server generates its own master key per instance of SQL Server.
SO how will I bring that master key over to the Test/UAT server and use it knowing I will also need to have the other 7 master keys from the other 7 clusters?
I am sure this initial post will generate more conversation and probably will need more details on my behalf but I wanted to start out simple and dive into this issue.
Thanks ALL!
Morning,
Here is my scenario:
I have a SQL Server 2000 server with 10 clients.
Each client has 5 Full-Text Catalogs. For ease of explanation let€™s call the FTCs C1 thru C5.
Now each client€™s FTCs are named the SAME. So each client has FTCs named C1, C2, C3, C4 and C5.
I need to move the clients to our new SQL Server 2005 Enterprise server.
I can backup up the DB using the native SQL Server 2000 backup command but that of course does not back up the FTCs.
So once I restore the client DB over to the new SS2K5 server, how do I re-enable the FTCs and rebuild them so that they are the same as what was over on the SS2K server.
Also, after the first client is complete, will I run into a duplicate FTC error when I try to recreate the subsequent clients on the server since they all have the same named FTCs?
If so, how do I overcome this event?
Thanks for any and all help!
I've been doing some testing on the SAN/Disk subsystem over the past few days. I've run into something that is bugging me though. Hopefully someone here has run into the same thing or can answer.
*All LUNs have been created with default selects.
Test 1:
LUN1 (H:) - Created partition with diskmanager in win2003.
LUN2 (I:) - Created partition with diskpart and aligned the sectors at 64k.
Formatted both disks to have 4k in the allocation units.
Created a new blank DB on each disk.
With Profiler running, I ran a bulk insert for both disks and also ran a "Select count(*), Sum(total) from tableA" for both databases and cleared the proc cache inbetween.
Profiler showed the reads and writes io for the import and selects as a the same number (468721 reads and 312182 writes).
Test 2:
Deleted partitions
LUN1 (H:) - Created partition with diskmanager in win2003.
LUN2 (I:) - Created partition with diskpart and aligned the sectors at 64k.
Formatted both disks to have 8k in the allocation units.
Created a new blank DB on each disk.
With Profiler running, I ran a bulk insert for both disks and also ran a "Select count(*), Sum(total) from tableA" for both databases and cleared the proc cache inbetween.
Profiler showed the reads and writes io for the import and selects as a the same number (468721 reads and 312182 writes).
Test 3:
Same as test 2 but formatted with 64k allocation units.
So here is my question: Shouldn't the I/O go down or at least change if you change the allocation unit size for the disk?
Thanks,
Daniel
Hello.
Our software applications require the sa login to be enabled. We have a .NET (C#) installation application that installs our software applications.
So, is there any way that we can programmatically enable the sa login for SQL Server 2005? Ideally, we'd like to code this into our installation application.
Thanks.
I have a couple of tables set up with column level tracking and using the "Subscriber Always Wins" conflict resolver.
I am still trying to work out why there is a conflict as the only updates to these rows happen at the subscriber.
What I am finding is that a conflict occurs and there appears to be a delay between the conflict being recognised and then resolved.
The reason I know there is a delay is because this is playing havoc with a data extract that relies on the updates from the subscriber.
For instance, I have a job on which the status is changed. That status change triggers an extract via BizTalk to another system. BizTalk, via an SQL adapter extracts the data from the server and I find that some of it is missing in the extract.
I go and look into the database at the raw data and find that the data is in fact there.
I have certain triggers running which set up export flags in the database to say this data should be exported. This works perfectly when there are no conflicts.
In each case where data has not been extracted, a conflict occurs.
Is there any way to guarantee that the conflict will be resolved at the same time as the synchronisation is complete - i.e. within the same transaction?
I thought replication was supposed to be a single transaction - you get it all or you get nothing.
I'm interested to hear from anyone who has experienced this behaviour.
Thanks
Hi Settled into the new giggero now. Since I have moved here we have upgraded our 4 SQL Servers to 2005 64 bit. All 2 proc dual core hyper threaded with 4GB RAM. Windows 2003. SQL Server compatibility level is 90. SP 1 and the CTP for SP2 are installed. We are hanging on with sp2. Maxdop is 0 (but has been tried on 2). Up to a score or so databases per machine, between 8 and 300 GB in size. Offline, reasonably heavy duty ETL batch processing. Since upgrading we have had trouble with the CPUs intermittently maxing out at 100% usage. This is when intensive routines are run. We know that many of these routines are crappy (SELECT... INTO creating tables with 10s or 100s of millions of rows, cursors etc.) and we are rewriting the code. Estimated time of completion of code review and rewrite is end of next year so we can't wait that long. The same poor code ran (albeit slowly) in SS2k but is causing the server to lock up now it is being run on SS2k5. Symptoms include connection attempts timing out, routines running very slowly. Existing connections can continue to make requests but these are very slow. If we get on the box the CPUs are at a never wavering 100% utilisation. This continues until intervention is taken, often restarting the service. We have left a maxed out box alone over a weekend and it was still in the same state when we came in on Monday. Nothing to glean from the error logs (AFAIK). Obviously the long term fix is to get the code sorted but this is an ongoing process (in fact it is one of the reasons I was hired). Our immediate concern is to get the servers back up to the sort of performance we were realising before we upgraded. Does anyone have any ideas?As ever eternal gratitude and a crate of virtual beer for any help :D
View 11 Replies View Related
DML T-SQL works fine. But When I try to run SELECT query with joins that involves large tables (1.5 mil rows in each) in 2 databases, it instantly goes into "runnable" status and never finishes. It never finishes even when I have top 1 clause included. When I run insert or update that involves same tables, it works just fine.
Server facts:
W2003
SS 2K5 SP2
Db Comp level 90 (for all db)
MAXODP = 1 (8 processor box)
Recently moved databases from server that had SS 2000.
When this query was running on box with SS 2000, it took about a minute to finish, but it completed.
I already tried: changing MAXODP settings, using OPTION (maxdop 1) etc.
Anything else I can try.
Hi,
The problem I have is this:
I have installed SQL Server 2005 Enterprise Edition on a W2K3 server that already has a SQL Server 2000 default instance installed. The installation appears to be a success. The problem is that having installed the client tools, and trying to connect, I get the following error message in a dialog:
"Cannot connect server SERVERNAMEINSTANCENAME
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: SQL Network Interfaces, error: 26 - Error Locating
Server/Instance Specified)(Microsoft SQL Server)"
The funny thing is that I can connect to the SQL Server 2000 default instance that is on that server.
So it's obviously not a connection problem per se at my end i.e. bad dns etc which might stop me resolving the server name.
Googling for this error text gives the following advice on various web sites:
1. Check that the remote server allows connections.
It does, as other colleagues in my team have successfully installed the tools and can connect with no problems.
2. Check that the SQL Browser service is running.
It is, as without this running, my colleagues would not be able to connect either.
3. Open SQL Server Configuration Manager. Select "SQL Server 2005 Network Configuration | Protocols for MSSQLSERVER" then enable the protocols you need.
The required protocol (TCP/IP) is enabled. Named pipes is also enabled, although I don't think that we're using that. And shared memory is also enabled by default.
4. Open the firewall and add exceptions for sqlbrowser.exe or UDP port
1434
There is no firewall running at either end of the connection and as mentioned I can connect to the SS2K default instance.
5. Make sure that the server machine is reachable.
I can connect to the SS2K default instance so it must be reachable. I can't see that I would need to change any configuration settings as my colleagues are using exactly the same default settings for their connections and they work fine.
The only thing that I have done differently is that I originally installed the client tools using someone else's privileged account as I didn't have admin rights on my box. The client tools didn't work, so I got admin rights to my box, uninstalled the client tools and then reinstalled them using my account. Still no luck. Not sure if something is still hanging around after the uninstallation that would cause me a problem.
To help, I've also filled out the following questionnaire:
[1] Client side:
> What is the connection string in you app or DSN?
There isn't one. I'm trying to connect from the SQL Server Management Studio | 'Connect to Server' dialog.
> If client fails to connect, what is the client error messages?
"Cannot connect server Y
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: SQL Network Interfaces, error: 26 - Error Locating
Server/Instance Specified)(Microsoft SQL Server)"
Is the client remote or local to the SQL server machine? Remote
Can you ping your server? YES
Can you telnet to your SQL Server? YES
What is your client database provider? [SNAC | MDAC | ADO.NET1.0 | ADO.NET2.0| other (please specify] N/A
What is your client application? SQL Management Studio
Is your client computer in the same domain as the Server computer? Different domains
What protocol the client enabled? [Shared Memory | TCPIP | Named Pipes]. All 3 protocols are enabled
Do you have aliases configured that match the server name portion of your connection string? No
Do you select force encryption on server and/or client? No
[2] Server side:
What is the MS SQL version? SQL Server 2005
What is the SKU of MS SQL? Enterprise
What is the SQL Server Protocol enabled? [Shared Memory | TCPIP | Named Pipes ]. All 3
Does the server start successfully? YES. Other people can connect to the same instance.
If SQL Server is a named instance, is the SQL browser enabled? YES
What is the account that the SQL Server is running under? Domain Account
Do you make firewall exception for your SQL server TCP port if you want connect remotely through TCP provider? N/A. Firewall not running.
Do you make firewall exception for SQL Browser UDP port 1434? N/A. Firewall not running.
What tool or Application are you using to connect to SQL Server SQL Server Management Studio
[3] Platform:
What is the OS version? Windows 2003 (Server side), Windows XP Pro Version 2002 SP 2
Do you have third party antivirus, anti-spareware software installed? Symantec AntiVirus
[4] Misc:
If you have certificate configuration issue: N/A
Has anybody else come across this problem, as I've run out of ideas.
Many thanks,
Hi ,
On my Desktop i registered Production Server in Enterprise Manager
on that Server if i go to SecurityLinked Servers
There is another Server is already mapped, when i am trying to see the Tables under that one of the
Linked Server i am getting the Error message saying that
"Error 17 SQL Server does not exist or access denied"
if i went to Production Server location and if i try to see the tables i am able to see properly, no problems
why i am not able to see from my Desk top
i am using the sa user while mapping the Production Server on my DESKTOP using (ENTERPRISE MANAGER)
And i check the Client Network Utility in the Alias using Named Pipe only, i changed to TCP/IP still same problem
What might the Problem how can i see the Tables in Linked Server from my DESKTOP
Thanks
I am using Linked Server in SQL Server 2008R2 connecting to a couple of Linked Servers.
I was able to connect Linked Servers, but I cannot point to a specific database in a Linked Server, also, I cannot rename Linked Server's name.
How to point the linked server to a specific database? How to rename the Linked Server?
The following is the code that I am using right now:
USE [master]
GO
EXEC master.dbo.sp_addlinkedserver
   @server = N'Machine123Instance456',
   @srvproduct=N'SQL Server' ;
GO
EXEC sp_addlinkedsrvlogin 'Machine123Instance456', 'false', NULL, 'username', 'password'Â Â
Is there a way to bypass the syntax checking when adding a stored procedure via a script?
I have a script that has a LINKed server reference (see below) .
INSERT
INTO ACTDMSLINKED.ACTDMS.DBO.COILS ..etc.
ACTDMSLINKED does not exist at the time I need to add the stored procedure that references it.
PLEASE to not tell me to add the LINK and then run the script. This is not an option in this scenerio.
Thanks,
Terry
Hi
I have created a linked server from SQL Server 2005 (SP 1) to SQL Service 2000 (SP 4) with a sql server login that is available on both servers but with different passwords and permissions.
I am getting the following error while accessing the linked server in management studio based on the scenario given below ;
------ Error Message Starts
OLE DB provider "SQLNCLI" for linked server "(SQL Server 2000 instance name)" returned message "Communication link failure".
Msg 10054, Level 16, State 1, Line 0
TCP Provider: An existing connection was forcibly closed by the remote host.
Msg 18456, Level 14, State 1, Line 0
Login failed for user 'abc'.
------ Error Message Ends
Consider login name is abc.
Now this login abc has sysadmin rights on sql server 2005.
The same login abc has only db_datareader rights on sql server 2000 on just one database and is not associated with any fixed server role.
I have configured the linked server using the following options;
1. I have tried impersonating login from SQL Server 2005 to SQL Server 2000 .
2. I have also tried specifying remote login / password option.
Anyone having any idea, would be of great help.
Regards,
Salman Shehbaz.
i did "Linked server" between To Servers , and it's Working.
---------------------------
For Example :
Server 1 =S1.
Server = S2.
i create table in S1 : name = TblS1
i create same table in S2 : name TblS2
and i create trigger(name tr_cpD) From S1 in TblS1 For send data To TblS2 in S2
/****************** trigger Code ***************
CREATE TRIGGER dbo.tr_cpD
ON dbo.TblS1
AFTER INSERT
AS
BEGIN
SET NOCOUNT ON;
insert into [S2].[dbname].[dbo].[TblS2] Select ID,Name from insertedEND
**************************************************
result is :
Msg 7399, Level 16, State 1, Procedure tr_cpD, Line 14
The OLE DB provider "SQLNCLI" for linked server "S2" reported an error. The provider did not give any information about the error.
Msg 7312, Level 16, State 1, Procedure tr_cpD, Line 14
Invalid use of schema or catalog for OLE DB provider "SQLNCLI" for linked server "S2". A four-part name was supplied, but the provider does not expose the necessary interfaces to use a catalog or schema.
how i can execute this trigger
Can I connect from a SQL Server 2005 database to a SQL Server 2000 database, without establishing a linked server connection.
I need to fire a SELECT query on a SQL Server 2000 database, but don't want to add it as a linked server. Is there any way I can do this or its not possible??
I have a Sybase Adaptive Server Enterprise server which I need to set up as a linked server in SQL Server 2005. The Sybase server is version 12.5.2, and the Sybase ODBC driver version is 4.20.00.67. I have already installed the Sybase client software on the server.
I also created a SystemDSN on the SQL Server to connect to the Sybase server. I tested the connection and it was able to connect.
I ran the following code to create the linked server:
<code>
EXEC master.dbo.sp_addlinkedserver @server = N'LinkedServerName', @srvproduct=N'Sybase', @provider=N'MSDASQL', @datasrc=N'Sybase System DSN', @provstr=N'"Provider=Sybase.ASEOLEDBProvider;Server Name=servername,5000;Initial Catalog=databasename;User Id=username;Password=password"'
</code>
I then ran sp_tables_ex to make sure I could view the tables in the Sybase database. Here is the error message I get:
<code>
OLE DB provider "MSDASQL" for linked server "LinkedServerName" returned message "[DataDirect][ODBC Sybase Wire Protocol driver]Error parsing connect string at offset 13. ".
Msg 7303, Level 16, State 1, Procedure sp_tables_ex, Line 41
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "LinkedServerName".
</code>
Any ideas what is happening here?
I was trying to figure out what the OPENQUERY Syntax is to Insert into SQL Server Table from Oracle Linked Server.
View 7 Replies View RelatedWe have oracle linked server created on one of the sql server 2008 standard , we are fetching data from oracle and updating some records in sql server . Previously its working fine but we are suddenly facing below issue.
Below error occurred during process .
OLE DB provider "OraOLEDB.Oracle" for linked server "<linkedservername>" returned message "".
Msg 7346, Level 16, State 2, Line 1
Cannot get the data of the row from the OLE DB provider "OraOLEDB.Oracle" for linked server "<linked server name>".
I'm trying to link SQL Server 2000 sp3 to SQL 2005 64 bit. I keep getting Error 17 sql server does not exist or access denined. I tried adding remote user mapping and chaning the linked server properties to "Be made using this security context" without any success.
Any help is appreciated.
I receive the following error message when I run a distributed query against a loopback linked server in SQL Server 2005:
The Microsoft Distributed Transaction Coordinator (MS DTC) has cancelled the distributed transaction.
To resolve this problem, I was told that running a distributed query against a loopback linked server is not supported in SQL Server 2005. And I am suggested to use a remote server definition (sp_addserver) instead of a linked server definition to resolve this problem. (Although this is only a temporary resolution, which will deprecate in Katmai)
However, I run into another problem when I use the remote server definition. I receive the following error message:
Msg 18483, Level 14, State 1, Line 1
Could not connect to server 'ServerNameSQL2005' because '' is not defined as a remote login at the server. Verify that you have specified the correct login name.
Could anyone please help me out?
(I include the reproduce steps for the first error message, followed by my resolution that generates the second error message)
======
Reproduce steps for the first error message
======
On the ComputerAInstanceA instance, run the following statement to create a database and a table:
CREATE DATABASE DatabaseA
GO
USE DatabaseA
GO
CREATE TABLE TestTable(Col1 int, Col2 varchar(50))
GO
INSERT INTO TestTable VALUES (1, 'Hello World')
GO
On the ComputerBInstanceB instance, run the following statement to create a database and a table:
CREATE DATABASE DatabaseB
GO
USE DatabaseB
GO
CREATE TABLE TestTable (Col1 int, Col2 varchar(50))
GO
On the ComputerAInstanceA instance, create a linked server that links to the ComputerBInstanceB instance. Assume the name of the linked server is LNK_ServerB.
On the ComputerBInstanceB instance, create a linked server that links to the ComputerAInstanceA instance. Assume the name of the linked server is LNK_ServerA.
On the ComputerBInstanceB instance, run the following statement:
USE DatabaseB
GO
CREATE PROCEDURE InsertA AS
BEGIN
SELECT * from LNK_ServerA.DatabaseA.dbo.TestTable
END
GO
On the ComputerAInstanceA instance, run the following statement:
USE DatabaseA
GO
INSERT INTO TestTable
EXEC LNK_ServerB.DatabaseB.dbo.InsertA
GO
Then I receive the first error message.
=======
My resolution that generates the second error message
=======
On the ComputerBInstanceB instance, run the following statement:
sp_addserver 'ComputerAInstanceA'
GO
sp_serveroption 'ComputerAInstanceA', 'Data Access', 'TRUE'
GO
USE DatabaseB
GO
CREATE PROCEDURE InsertA AS
BEGIN
SELECT * FROM [ComputerAInstanceA].DatabaseA.dbo.TestTable
END
GO
On the ComputerAInstanceA instance, run the following statement:
USE DatabaseA
GO
INSERT INTO TestTable
EXECUTE [ComputerBInstanceB].[DatabaseB].[dbo].[InsertA]
GO
Then I receive the second error message.
I have the linked server connection created and works perfectly well. I mean I am able to see the tables while I am on my database.
how do I write a SQL statement to reference the linked server ?
I tried the following:
Select top 100 * from casmpogdbspr1.MPOG_Collations.dbo.AsaClass_Cleaned
Then I get the error message....
Msg 7314, Level 16, State 1, Line 1
The OLE DB provider "SQLNCLI10" for linked server "casmpogdbspr1" does not contain the table ""MPOG_Collations"."dbo"."AsaClass_Cleaned"". The table either does not exist or the current user does not have permissions on that table.
Using a 32-Bit SQL Server 2008 Express on my LOCAL PC. I downloaded the Advantage 8.1 OLE DB Provider and created a linked server to a REMOTE Advantage 8.1 database server. There is no data dictionary on the Advantage server.
Here is my linked server:
EXEC master.dbo.sp_addlinkedserver @server = N'1xx.1xx.xx.1xx', @srvproduct=N'Advantage', @provider=N'Advantage OLE DB Provider', @datasrc=N'1xx.1xx.xx.1xxeccET', @provstr=N'servertype=ads_local_server;tabletype=ads_cdx;'--tabletype=’ADS_ADT’ (this test works too)
EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname=N'1xx.1xx.xx.1xx',@useself=N'False',@locallogin=Null,@rmtuser='adssys',@rmtpassword=Null
Testing the link succeeds with above. Using “ads_REMOTE_server” instead of “ads_local_server” and the test fails. Here is my problem, using the following queries will not work. Perhaps it’s a permissions issue? When I specify my local credentials for the remote server in the linked server it still does not work.
SELECT * FROM OPENQUERY([1xx.1xx.xx.1xx], 'SELECT * FROM ActType')
OLE DB provider "Advantage OLE DB Provider" for linked server "1xx.1xx.xx.1xx" returned message "Error 7200: AQE Error: State = HY000; NativeError = 5004; [Extended Systems][Advantage SQL][ASA] Error 5004: Either ACE could not find the specified file, or you do not have sufficient rights to access the file. Table name: ActType SELECT * FROM ActType".
Msg 7321, Level 16, State 2, Line 2
An error occurred while preparing the query "SELECT * FROM ActType" for execution against OLE DB provider "Advantage OLE DB Provider" for linked server "1xx.1xx.xx.1xx".
A recent SharePoint upgrade has rendered several views obsolete. I am redefining them so that our upper level executive reports show valid data.(yes, I know that doing anything to sharepoint could cause MS to deny support, having said that, this is something I've inherited and need to fix, pronto) The old view was created like so:
USE [AHMC]
GO
/****** Object: View [dbo].[vwSurgicalVolumes] Script Date: 09/04/2015 09:28:03 ******/
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE VIEW [dbo].[vwSurgicalVolumes] AS
SELECT
[code]....
As I said, this view is used in a report showing surgical minutes.SharePoint is now on a new server, which is linked differently (distributed?) I've used OPENQUERY to get my 'new' query to work;
SELECT *
FROM OPENQUERY ([PORTALWEBDB], 'SELECT
--AllLists
AL.tp_ID AS ALtpID
,AL.tp_WebID as altpwebid
,AL.tp_Title AS ALTitle
[code]....
My data (ie surgical minutes, etc) seems to be in the XML column, AUD.tp_ColumnSet . So I need to parse it out and convert it to INT to maintain consistency with the previous view. How do I do this within the context of the view definition?Here is a representation of the new and old view data copied to excel :
<datetime1>2014-08-14T04:00:00</datetime1><float1>2.000000000000000e+000</float1><float2>4.190000000000000e+002</float2><float3>1.600000000000000e+001</float3><float4>8.110000000000000e+002</float4><sql_variant1 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:sqltypes="http://schemas.microsoft.com/sqlserver/2004/sqltypes"
[Code] ....
can't format it to make it look decent. InHouseCases =2, InHouseMinutes=419, OutPatientCases =16, OutPatientMinutes=1230. This corresponds to the new data I can see in the XML column; 2.000000000000000e+000 is indeed 2 and 4.190000000000000e_002 is indeed 419.
I have an Excel sheet that is dynamically updated (through DDE) and I want to import this data to a table in SQL Server 2005. Using SQL Server Management Studio to configure an Excel data source as a linked server.
(http://support.microsoft.com/kb/306397/EN-US/)
Following the first 5 steps should let me acces the table (but I cannot view the data in SQL Server 2005). However, I could not find how to export the data into an existing table. Does anyone know how or can give a pointer to document describing how to do this?
Hi,
I have a msaccess linked server that I use to execute sql 2000 stored procedures from a front end in adp (access data project) format without any problem, if it is used on the same machine where the sql server resides (with any user logged on). In any other machine on the local network where I also need to use it, I get an ole/db error message saying that the microsoft jet database engine can not open the file because it's allready opened exclusivly or because it do not has permissions. I created the linked server with both UNC and normal path with the same result.
Thank's for all the help/clues you can give me.
i want to run a transaction across mulitpule instances of sqlserver with out linked server.distributed trnasaction can do it with link server , can it do it with out linked server.
View 4 Replies View RelatedHi,
I would like to join two tables: one on a local server which I have admin access to and another server which I only have read access. The local table is very small, but the remote table is very large.
If I look at Query Analyzer's execution plan, it appears that the join will be done locally (i.e. the entire table is transferred from the remote server and then joined to my local table). Is there a way to create a temp table using linked servers, transfer my small local table to the remote server and then perform the join on the remote server? In the past, I have been able to use openquery to restrict the data to a small subset that is transferred but the local table is a little too large for that.
I appreciate any advice / guidance anyone can offer me!
Hi all,
I have the following select that is designed to compare values on parallel servers.SELECT TA1.EPS, TA1.Sales, TA1.Income, TA1.EarningsReportDate,TA2.EPS, TA2.Sales, TA2.Income, TA2.EarningsReportDate
FROM TradeAnalysis.dbo.SalesIncome_Quarterly AS TA1
FULL OUTER JOIN L_TA_MIRROR.TradeAnalysis.dbo.SalesIncome_Quarterl y AS TA2
ON ((TA1.OSID = TA2.OSID) AND (TA1.QtrYear = TA2.QtrYear) AND (TA1.QuarterNo = TA2.QuarterNo))
WHERE(BINARY_CHECKSUM(TA1.EPS, TA1.Sales, TA1.Income, TA1.EarningsReportDate) <>
BINARY_CHECKSUM(TA2.EPS, TA2.Sales, TA2.Income, TA2.EarningsReportDate))Disregard the full outer join, it is necessary in the full select, I have just pared it down to show here and for testing. A standard join will also have the same result.
The trouble is that the comparison (the BINARY_CHECKSUM) is failing on the EarningsReportDate column, which is defined on BOTH servers in DUPLICATE databases as a smalldatetime.
The data is actually the same in both rows of each table (as is all the other data being compared). What I am seeing is that the select returns milliseconds on the LINKED server (the L_TA_MIRROR reference), but not on the local database?
for example,
Local server data returned in above select is 2000-01-28 00:00:00
Linked server data returned in above select is 2000-01-28 00:00:00.000
Wassup with THAT? If I remove the date from the select/comparison, it says everything matches, so I am pretty sure this is the culprit that is causing the BINARY_CHECKSUM comparison to fail.
Is there some setting that I need to put on the Linked Server reference that says "treat this as the smalldatetime data type it IS, dammit!"????
I can get by the issue if I replace the date reference in the linked server part of the select with CAST(TA2.EarningsReportDate AS smalldatetime) but why do I have to do this?
Yes, I am SURE both servers have the column in question defined as a smalldatetime, as running the same select on either server causes the same failure, but only when referencing the LINKED server column.
I wonder if it possible to move data from tables on a linked server to a "normal database"?
Name linked server: Covas
Name table on linked server: tblCountries
Name field: cntCountryName
Name "normal" database: CovasCopy
Name "normal" table: Countries (or dbo.Countries)
Name "normal" field: Country
This is just a test setup. I figure that if I get this working the rest will be easier.
My current query:
select * from openquery(COVAS,'
INSERT INTO CovasCopy.dbo.Countries(Country)
SELECT cntCountryName FROM db_covas.tblCountries;')
Here is my Problem:
1. I have sql 2008 R2 running on my LocalHost.
2. Created Data Base [Customer].
3. Created Linked Server [CUSTOMERLINK] USING Microsoft Jet 4.0 to link to Drive F:Data which has DBF files in it.
4. Create dbo.Customer_Upload Table.
5. INSERT INTO [Customer].[dbo].[Customer_UpLoad]
([Name],[Email])
SELECT
NAME,EMAIL
FROM [CUSTOMERLINK]...[CUS]
All this works fine. I can even put it in to an After Insert Trigger on another table and it works.
My problem is that I need this to work in a scheduled job.
F:Data is just a folder with files in it.
This info is from a Restaurant POS system and I need to update it every night.
I have tried every which way to to setup the security issue as there isn't any login security on the folder and SqlServerAgent wants security.
I have a sproc that will generate a dynamic call (and this must be done in a stored procedure),... Anyway the dynamic call I am having problems with is that I need to dynamically create a statement to backup a database. It works as long as the database is on the same server / instance as the stored procedure. I want to be able to from server/instance A create a command that does a backup of a database that is on server B. I just can't figure out the syntax for a database backup where the database is on another server.
Trying something like [ServerName].[DatabaseName] does not work...
We are upgrading from SQL 2008R2 to SQL2014 but we have discovered that a couple of our applications are not supported on 2014. We'd like to keep one 2008R2 server and one 2014 server until we have time to upgrade the applications and move everything to the new server. The problem is we have custom code in some of the 2014 databases that access tables in the 2008 databases.
I know we can easily do cross server joins by using a linked server, but it would be a huge undertaking to find all that code and add a linked server name in front of every table, stored procedure, etc. So my question is, is there any way to move a database to a different server and still be able to access it without having to qualify the object names with a linked server? Is there some kind of server/database synonym that can be setup that would be recognized by all databases?