Adding a new Instance to a patched SSRS2008 installation give "Attempted to read or write protected memory"
Tuesday, January 29, 2013 5:24 PM
I'm trying to install a new instance to an existing SQL Server 2008 R2 Standard installation (under Windows 2008 R2 SP1).
The existing installation has four instances, which were built at the same time and then patched to CU12. The proces followed is:
Run setup.exe as Administrator.
Setup support files install OK.
Choose "New Installation or Shared Features".
Choose "SQL Server Feature Installation".
Choose Database, Reporting Services and Management Tools as components.
Name the instance and choose destination.
Choose Mixed Mode, specify a password and an SQL Administrator.
Install Native Mode Default Configuration.
The isntallation then fails with "Attempted to read or write protected memory". Can anyone offer any guidance?
The full message in the Summary_UKWORKRS2008_20130124_154516.txt file in C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130124_154516 shows:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: System.AccessViolationException
Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
DisableWatson = true
at Microsoft.SqlServer.Chainer.Infrastructure.MsiNativeMethods.MsiOpenPackageEx(String szPackagePath, UInt32 dwOptions, UInt32& hProduct)
at Microsoft.SqlServer.Configuration.MsiExtension.InstallPackage.RunMsiCore(String commandLine)
at Microsoft.SqlServer.Configuration.MsiExtension.InstallPackage.RunMsiWithRetry(String commandline)
at Microsoft.SqlServer.Configuration.MsiExtension.InstallPackage.RunMsi(IEnumerable`1 commandLineProps)
at Microsoft.SqlServer.Configuration.SetupExtension.MSIInstallerEngine.InstallPackage(PackageId pkg, InstallAction pkgAction)
at Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallAction.Execute(String actionId, TextWriter errorStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
- Edited by Ian Smith Workplace Tuesday, January 29, 2013 5:27 PM
Friday, February 01, 2013 2:53 AMModerator
Thank you for your question.
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
Thank you for your understanding and support.
TechNet Community Support
Wednesday, February 06, 2013 2:24 PM
Thanks for the information provided.
Could you please post the Detail.Txt?
If not the entire detail.txt, then you can search for this text "Attempted to read or write protected memory. This is often an indication that other memory is corrupt" in Detail.Txt. Post the entire log which is logged after the above message.
Wednesday, February 13, 2013 2:14 AMModerator
Did you solve the issue? If you find out the root cause finally, you can share your solutions and mark it as answer, it will be very beneficial for other community members who have similar questions.
If the problem is not solved, please share the detail log file which locate in C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130124_154516. It is benefit for us to do further analysis. You can send the log to us by the following E-mail address?
TechNet Community Support