May 8, 2013 at 5:17 am
Hi,
Error is: Could not load file or assembly 'Microsoft.SqlServer.Configuration.WizardFramework, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The module was expected to contain an assembly manifest.
I have looked everywhere for assistance on this but just cannot get it right. I have reloaded the OS even 🙂 Summary file contents below.
------------------------------------------------
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): 1150839443
Exit facility code: 1176
Exit error code: 27283
Exit message: Could not load file or assembly 'Microsoft.SqlServer.Configuration.WizardFramework, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The module was expected to contain an assembly manifest.
Start time: 2013-05-08 13:09:18
End time: 2013-05-08 13:15:14
Requested action: RunRules
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130508_130906\Detail_GlobalRules.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.1600.1%26EvtType%3d0x6083527E%400x16A19545
Machine Properties:
Machine name: DB
Machine processor count: 4
OS version: Windows Server 2003
OS service pack: Service Pack 2
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 0
Installation location: E:\x64\setup\
Installation edition: ENTERPRISE
User Input Settings:
ACTION: RunRules
CONFIGURATIONFILE:
ENU: True
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES:
HELP: False
IACCEPTSQLSERVERLICENSETERMS: False
INDICATEPROGRESS: False
INSTANCENAME: <empty>
PASSPHRASE: *****
QUIET: False
QUIETSIMPLE: False
RULES: GlobalRules
UIMODE: Normal
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130508_130906\ConfigurationFile.ini
Detailed results:
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: The rule result report file is not available.
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: System.BadImageFormatException
Message:
Could not load file or assembly 'Microsoft.SqlServer.Configuration.WizardFramework, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The module was expected to contain an assembly manifest.
Data:
DisableWatson = true
Stack:
at System.RuntimeTypeHandle._GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark, Boolean loadTypeFromPartialName)
at System.RuntimeTypeHandle.GetTypeByName(String name, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark)
at System.RuntimeType.PrivateGetType(String typeName, Boolean throwOnError, Boolean ignoreCase, Boolean reflectionOnly, StackCrawlMark& stackMark)
at System.Type.GetType(String typeName)
at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceFactoryService.CreateActionHandler(ActionHandlerInfo actionHandlerInfo, String formType)
at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceFactoryService.Create(String moniker)
at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceService.Start(String moniker)
at Microsoft.SqlServer.Configuration.UIExtension.StartAction.ExecuteAction(String actionId)
at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
May 9, 2013 at 2:47 am
anyone?
May 13, 2013 at 3:16 am
All I can say is that I have done this many times and it should work.
If you want to use Filestream you will need to install KB 937444, but otherwise the SQL Enterprise media should have all the components you need to install on Windows 2003.
Sometimes the install will fail on a very slow server but this is normally shown in service start failures or non-existant paths in the error messages. Your problem seems to be a simple install issue.
You say you have reinstalled Windows. Is it worth getting a new copy of the SQL install media in case what you have is corrupted.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
May 13, 2013 at 3:41 am
3rd time lucky. Media was an issue
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply