Error message when you try to install SQL Server 2008 if the path of the SQL Server 2008 installation media contains a number sign (#) character: “Could not load file or assembly ‘<Path>\Mi …
Symptoms
When you try to install Microsoft SQL Server 2008 from a local path or from a network path, you receive the following error message:
Could not load file or assembly 'Path\Microsoft.SQL.Chainer.PackageData.dll' or one of its dependencies. The system cannot find the file specified.This issue occurs if the path of the SQL Server 2008 installation media contains a number sign (#) character.
Additionally, the following error message is logged in the Detail_GlobalRules.txt file:
Date Time Slp: Log provider 'Microsoft.SqlServer.Chainer.Infrastructure.LogProviderFile' has been registered
Date Time Slp: Log provider 'Microsoft.SqlServer.Chainer.Infrastructure.LogProviderStatus' has been registered
Date Time Slp: Received request to add the following file to Watson reporting: C:\Documents and Settings\Administrator\Local Settings\Temp\tmpDC5.tmp
Date Time Slp: The following is an exception stack listing the exceptions in outermost to innermost order
Date Time Slp: Inner exceptions are being indented
Date Time Slp:
Date Time Slp: Exception type: Microsoft.SqlServer.Chainer.Infrastructure.ChainerInfrastructureException
Date Time Slp:Message:
Date Time Slp:Could not load file or assembly '<Path>\Microsoft.SQL.Chainer.PackageData.dll' or one of its dependencies. The system cannot find the file specified.
Date Time Slp:Stack:
Date Time Slp:at Microsoft.SqlServer.Chainer.Infrastructure.ExtensionService.RegisterExtension(String extensionId, String name, String path)
Date Time Slp:at Microsoft.SqlServer.Chainer.Setup.Setup.LoadPackageXML(ServiceContainer context)
Date Time Slp:at Microsoft.SqlServer.Chainer.Setup.Setup.Run()
Date Time Slp:at Microsoft.SqlServer.Chainer.Setup.Setup.Start()
Date Time Slp:at Microsoft.SqlServer.Chainer.Setup.Setup.Main()
Date Time Slp:Inner exception type: System.IO.FileNotFoundException
Date Time Slp:Message:
Date Time Slp:Could not load file or assembly <Path>\Microsoft.SQL.Chainer.PackageData.dll' or one of its dependencies. The system cannot find the file specified.
Date Time Slp:Stack:
Date Time Slp:at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
Date Time Slp:at System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
Date Time Slp:at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
Date Time Slp:at System.Reflection.Assembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte[] hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, StackCrawlMark& stackMark)
Date Time Slp:at System.Reflection.Assembly.LoadFrom(String assemblyFile)
Date Time Slp:at Microsoft.SqlServer.Chainer.Infrastructure.ExtensionService.RegisterExtension(String extensionId, String name, String path)
Date Time Slp: The following exception occurred while preparing status logs during Watson failure processing: /Datastore/InputSettings
Date Time Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\DateTime\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
Date Time Slp: Sco: Unable to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\DateTime\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_, Win32 error 2
Date Time Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\DateTime\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
Date Time Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\DateTime\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
Date Time Slp: Sco: Unable to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\DateTime\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_, Win32 error 2
Date Time Slp: Could not load file or assembly '<Path>\Microsoft.SQL.Chainer.PackageData.dll' or one of its dependencies. The system cannot find the file specified.
Date Time Slp: Watson bucket for exception based failure has been created
Date Time Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
Date Time Slp: Sco: Attempting to open registry subkey Software\Microsoft\PCHealth\ErrorReporting\DW\Installed
Date Time Slp: Sco: Attempting to get registry value DW0200
Date Time Slp: Submitted 1 of 1 failures to the Watson data repository
Date Time Slp:
Date Time Slp: ----------------------------------------------------------------------
Date Time Slp:
Date Time Slp: Error result: -2068774911
Date Time Slp: Result facility code: 1201
Date Time Slp: Result error code: 1
Resolution
This issue occurs because the Setup program cannot load an assembly from the path of the SQL Server 2008 installation media if the pathcontains a number sign (#) character.
Volatile Fields
Software built on the .NET framework is subject to many optimisations. Some optimisation is performed when compiling your program or library in Visual Studio or using the command-line compiler. Other optimisations are applied when executing the compiled intermediate language (IL) code. These vary according to the type of processor used to run the program. In many situations these optimisations lead to faster code or smaller programs without any noticeable side effects.
One optimisation that can have side effects relates to publicly visible fields in classes or structures. When you request the value of such a field the program normally performs a non-volatile read. This type of read can be optimised to improve the performance of the program. For example, the processor may choose to read the value from memory earlier than expected, and potentially in a different order than specified, in preparation for its later use. This may move the value to the processor's cache memory, where it can be accessed more quickly than from the main memory, or to its registers for yet faster performance. In single-threaded code these changes are unnoticeable.
When you are creating a multithreaded application or one that uses parallel programming code, non-volatile reads can present a problem. To illustrate this, consider the following program:
Software Testing – Quality Assurance Interview Questions
What is Gray-box testing?
Gray-box testing is the combination of White-box and Black-box
Difference between blackbox testing and whitebox testing
Black box testing - Testing a system without having specific knowledge .
whitebox testing - Testing a system with knowing the internal logic.
What isWhite box testing?
White box testing is opposite to Black box it requires internal know how of how the logic flows. As this testing needs know how of the internal structure it can only be done programmers. Unit testing is one of the ways of doing White box testing in which programmers use NUNIT or JNUIT to test each class individually. White box testing can be done by programmer by either stepping through the code or testing the classes and components in isolation.
What is black box testing
Black box testing is also termed as functional testing. It ignores how the internal
functionality of a system works and depends only what are the outputs on specified
inputs. Source code availability is not an important in back box testing. Black box testing is mostly to ensure that it meets the user functionality.
