Server 2008 R2 SP1 - Software install - Error 1935 HRESULT:0x800736B5

I'm working on an error installing a product on Windows Server 2008 R2 SP1 machines. The server has been acting as a file server for months with no problems. The application requires .net 3.5 and .net 4 client profile to be installed. I'm able to pass the
prerequists portion of the installation but eventually the software halts near completion with the error
Error: 1935.An error occurred during the installation of assembly component {106BBB06-46FA-8A99-8361C13A0C}.
HRESULT: 0x800736B5.
I've found a couple articles that reference this article
http://answers.microsoft.com/en-us/windows/forum/windows_vista-windows_programs/error-1935an-error-occurred-during-the/7105ee7e-ab45-4bd2-b5db-a3e9002f7f9e , which I've tried with no success.
The other article I found was
http://answers.microsoft.com/en-us/office/forum/office_2007-office_install/error-code-1935-during-installation-on-windows-7/daee32ef-58f0-4d24-a1e0-8bfdab66185f which again I found no success with.
The weird thing about this error is that I cant find anything useful from the event viewer. Does anyone have any thoughts on this?
Thank you in advance!

Hi,
Thanks for posting in the forum.
Before going further, would you please let me know what the product you want to install on the server is? At this time, you could try to disable the anti-virus program first if it is installed
on the server. Then please try to reinstall the two version of .Net Framework and Visual C++ 2005 / 2008 Redistributable Package to see if the issue could be resolved.
Hope this helps.
Best Regards,
Andy Qi
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

This feature can only be installed on a server running SQL Server 2008 R2 SP1 or later ERROR

Attempting to install MBAM 2.5, and the SQL Server I have available for the install is SQL Server 2008 R2 SP2; the databases installed correctly, but when I run the Reports install it suddenly doesn't like my SQL anymore. The error says I need to install
SQL Server 2008 R2 SP1, SQL Server 2012 SP1, or later - and the server is already at that level.
Any idea of how to progress without needing to wipe out SQL and upgrading everything to 2012 R2? I really need to get this running ASAP, so I'm hoping there's a tip that will allow me to get the install to complete.

Added note: When I check the mbam setup logs in event viewer, I get the following error:
IsSupportedSqlVersion: The SQL version is not supported - 10.50.1600.1.
Checking the version in SQL Management Studio shows:
select @@VERSION
Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64)

Windows Server 2008 R2 SP1 - BSOD Stop Error 0x00000050 RDPWD.SYS

Hi all,
I have been struggling with a BSOD for the past 5 weeks and have scoured the web trying in vain to find someone else with the same issue.
Environment:
8 x 2008 R2 SP1 Windows Servers (8Gb RAM, 25Gb HDD) with Remote Desktop Services Roles installed, running as part of an RDS Farm. All Servers are VM Guests (hardware version 7) running on VMware vSphere v4.1.0-260247 Hosts (Dell
PowerEdge R710 - 128Gb RAM). Our vSphere 'farm' has 5 Hosts that connect to our EMC SAN via iSCSI with multipath routes.
Each RDS Server is load balanced via a Connection Broker, and each server has the same set of software / vm hardware installed. In a nutshell, each has Symantec Endpoint Protection v11.0.5002.333, Symantec Altiris v7.0, Microsoft Office 2007 as well as
other various software essential to these servers.
Symptoms:
Randomly throughout the day, one (or more) of the RDS Servers will crash with a BSOD more often than not with "caused by driver ntoskrnl.exe" sometimes with "cng.sys" and once with "ksecpkg.sys". So far in the 5 weeks I have had 90 crashes. Yesterday
all 8 of the RDS Servers crashed at some point throughout the day.
On a typical BSOD, it says:
The problem seems to be caused by the following file: ntoskrnl.exe
PAGE_FAULT_IN_NONPAGED_AREA
Technical Information:
*** STOP: 0x00000050 (0xfffffa800c153284, 0x0000000000000001, 0xfffff880053dc0c9, 0x0000000000000000)
*** ntoskrnl.exe - Address 0xfffff8000169ac40 base at 0xfffff8000161e000 DateStamp 0x4e02aaa3
Using BlueScreenView it says "caused by address: ntoskrnl.exe+7cc40" nearly every time.
I have analysed as best I could using Microsoft WinDbg, and this is the output of a typical mini-dump file:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [\\hqrds01\c$\Windows\Minidump\030112-19359-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Program Files\Debugging Tools for Windows (x64)\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: Server, suite: TerminalServer
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`01609000 PsLoadedModuleList = 0xfffff800`0184e670
Debug session time: Thu Mar 1 09:14:00.921 2012 (UTC + 0:00)
System Uptime: 0 days 21:31:41.950
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                        Bugcheck Analysis
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffa800be83284, 1, fffff8800576f0c9, 0}
Could not read faulting driver name
Probably caused by : RDPWD.SYS ( RDPWD!memcpy+1d9 )
Followup: MachineOwner
1: kd> !analyze -v
*                        Bugcheck Analysis
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa800be83284, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff8800576f0c9, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800018b8100
fffffa800be83284
FAULTING_IP:
RDPWD!memcpy+1d9
fffff880`0576f0c9 668901          mov     word ptr [rcx],ax
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR: 0x50
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800bf70a80 -- (.trap 0xfffff8800bf70a80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000023d rbx=0000000000000000 rcx=fffffa800be83284
rdx=ffffffffffe7e63b rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800576f0c9 rsp=fffff8800bf70c18 rbp=0000000000000001
r8=000000000000001c r9=fffff8a0033401e8 r10=fffff8a0033401e8
r11=fffffa800be83268 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
RDPWD!memcpy+0x1d9:
fffff880`0576f0c9 668901          mov     word ptr [rcx],ax ds:0c40:fffffa80`0be83284=????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800016319fc to fffff80001685c40
STACK_TEXT:
fffff880`0bf70918 fffff800`016319fc : 00000000`00000050 fffffa80`0be83284 00000000`00000001 fffff880`0bf70a80 : nt!KeBugCheckEx
fffff880`0bf70920 fffff800`01683d6e : 00000000`00000001 fffffa80`0be83284 00000000`00000000 fffff8a0`0be85820 : nt! ?? ::FNODOBFM::`string'+0x4611f
fffff880`0bf70a80 fffff880`0576f0c9 : fffff880`057547cf 00000000`00000000 00000000`00000022 00000000`00000002 : nt!KiPageFault+0x16e
fffff880`0bf70c18 fffff880`057547cf : 00000000`00000000 00000000`00000022 00000000`00000002 fffff880`0576c99d : RDPWD!memcpy+0x1d9
fffff880`0bf70c20 fffff880`0576c9fc : fffff8a0`0f938010 00000000`00000022 00000000`00000019 00000000`00000002 : RDPWD!SM_MCSSendDataCallback+0x303
fffff880`0bf70c60 fffff880`0576b354 : fffff880`0bf70da0 fffff8a0`033401e8 00000000`00000000 fffff880`0576abfd : RDPWD!HandleAllSendDataPDUs+0x188
fffff880`0bf70d10 fffff880`0576af64 : 00000000`00000031 fffffa80`0bd01895 00000006`0000001f fffff880`05739079 : RDPWD!RecognizeMCSFrame+0x28
fffff880`0bf70d50 fffff880`029ba1f8 : fffff8a0`03345000 fffffa80`0bae6e80 fffffa80`0a5c0e60 fffff880`05737e00 : RDPWD!MCSIcaRawInputWorker+0x3d4
fffff880`0bf70df0 fffff880`057378d0 : 00000000`00000000 fffff880`0bf70f10 fffff880`0bf70f08 00000000`00000000 : termdd!IcaRawInput+0x50
fffff880`0bf70e20 fffff880`05736d85 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tssecsrv!CRawInputDM::PassDataToServer+0x2c
fffff880`0bf70e50 fffff880`057367c2 : fffffa80`088e8a28 fffffa80`00000000 00000000`00000031 fffff800`00000000 : tssecsrv!CFilter::FilterIncomingData+0xc9
fffff880`0bf70ef0 fffff880`029ba1f8 : fffff880`009b8180 00000000`00000001 00000000`00000000 00000000`00000000 : tssecsrv!ScrRawInput+0x82
fffff880`0bf70f60 fffff880`0572c4c5 : fffffa80`088e8a10 fffffa80`0bd01658 00000000`00000000 fffffa80`088e8a10 : termdd!IcaRawInput+0x50
fffff880`0bf70f90 fffff880`029baf3e : fffffa80`0bd01620 fffffa80`0c100420 fffffa80`0bd4b450 fffffa80`0973b9b0 : tdtcp!TdInputThread+0x465
fffff880`0bf71810 fffff880`029b9ae3 : fffffa80`09d902b0 fffffa80`0973b9b0 fffffa80`093d8520 fffffa80`0bd4b450 : termdd!IcaDriverThread+0x5a
fffff880`0bf71840 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : termdd!IcaDeviceControlStack+0x827
STACK_COMMAND: kb
FOLLOWUP_IP:
RDPWD!memcpy+1d9
fffff880`0576f0c9 668901          mov     word ptr [rcx],ax
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: RDPWD!memcpy+1d9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: RDPWD
IMAGE_NAME: RDPWD.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7ab45
FAILURE_BUCKET_ID: X64_0x50_VRF_RDPWD!memcpy+1d9
BUCKET_ID: X64_0x50_VRF_RDPWD!memcpy+1d9
Followup: MachineOwner
The RDS servers are set to reboot automatically, and after a period of 5 minutes or so, the users can reconnect and log back in. On a typical day each server will have around 10 people RDP'd in to them.
The Users connecting to the RDS Servers included XP laptops/desktops and IGEL UD-120-LX Thin Terminals. The XPs have SP3 installed and are fully patched via Symantec Altiris.
Things I have tried:
- Analyse the dump-files (as per above).
- I have tracked each user logging on to the RDS Farm (via batch scripts) and tried to determine if this is caused by the same individual(s) but it appears random.
- Check to see if the crashing Virtual Machine is running on a specific host, but it has happened on all Hosts.
- Check to see if there was anything specific that happened on the day that the crashes started. There were about 5 new poeple introduced to the RDS Farm at that time, but there were using (a) client machines that had been used previously elsewhere with
no issues, (b) software that had been used previously, (c) in a remote location that had previous users using RDS, (d) have not been logged on to a RDS Server when it has crashed.
- Updated Windows Server 2008 R2 SP1 to the latest patches (as of Feb 2012).
- Turned on Verifier (using recommended settings), and then analysed dump-files with the same reference to rdpwd.sys.
- Fixed the Memory Resource Reservation in vSphere to the full 8Gb for all these RDS Servers (so that the memory is not shared at all).
- Ran MEMTEST on a VM Guest with the full 8Gb RAM, on a couple of the ESX Hosts.
- Changed the VMTools Video Driver to the SVGA II driver from the Standard VGA Driver.
- Ran a full AV Scan (using SEP).
- Isolated the Printer Drivers using the Printer Management MMC.
- Ran sfc /scannow of all RDS Servers and rebooted.
The mini-dump file mentioned above is here:https://skydrive.live.com/redir.aspx?cid=48f471f287af2349&resid=48F471F287AF2349!105&parid=48F471F287AF2349!103
I hope someone can help, as what hair I have left (from pulling it out) is turning grey!
Andy

*                        Bugcheck Analysis
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa800c153284, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff880053dc0c9, If non-zero, the instruction address which referenced the bad memory
   address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800018cd100
fffffa800c153284
FAULTING_IP:
RDPWD!memcpy+1d9
fffff880`053dc0c9 668901          mov     word ptr [rcx],ax
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR: 0x50
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800aa48a80 -- (.trap 0xfffff8800aa48a80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000001ff rbx=0000000000000000 rcx=fffffa800c153284
rdx=ffffffffffee6b8b rsi=0000000000000000 rdi=0000000000000000
rip=fffff880053dc0c9 rsp=fffff8800aa48c18 rbp=0000000000000001
r8=000000000000001c r9=fffff8a0123923a8 r10=fffff8a0123923a8
r11=fffffa800c153268 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
RDPWD!memcpy+0x1d9:
fffff880`053dc0c9 668901          mov     word ptr [rcx],ax ds:8c40:fffffa80`0c153284=????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800016469fc to fffff8000169ac40
STACK_TEXT:
fffff880`0aa48918 fffff800`016469fc : 00000000`00000050 fffffa80`0c153284 00000000`00000001 fffff880`0aa48a80 : nt!KeBugCheckEx
fffff880`0aa48920 fffff800`01698d6e : 00000000`00000001 fffffa80`0c153284 00000000`00000000 fffff8a0`10919830 : nt! ?? ::FNODOBFM::`string'+0x4611f
fffff880`0aa48a80 fffff880`053dc0c9 : fffff880`053c17cf 00000000`00000000 00000000`00000022 00000000`00000002 : nt!KiPageFault+0x16e
fffff880`0aa48c18 fffff880`053c17cf : 00000000`00000000 00000000`00000022 00000000`00000002 fffff880`053d999d : RDPWD!memcpy+0x1d9
fffff880`0aa48c20 fffff880`053d99fc : fffff8a0`10cf30d0 00000000`00000022 00000000`00000019 00000000`00000002 : RDPWD!SM_MCSSendDataCallback+0x303
fffff880`0aa48c60 fffff880`053d8354 : fffff880`0aa48da0 fffff8a0`123923a8 00000000`00000000 fffff880`053d7bfd : RDPWD!HandleAllSendDataPDUs+0x188
fffff880`0aa48d10 fffff880`053d7f64 : 00000000`00000031 fffffa80`0c039de5 00000006`0000001f fffff880`053a6079 : RDPWD!RecognizeMCSFrame+0x28
fffff880`0aa48d50 fffff880`012c01f8 : fffff8a0`12393000 fffffa80`0bb7aa60 fffffa80`0b81e9c0 fffff880`053a4e00 : RDPWD!MCSIcaRawInputWorker+0x3d4
fffff880`0aa48df0 fffff880`053a48d0 : 00000000`00000000 fffff880`0aa48f10 fffff880`0aa48f08 fffffa80`0c039ba8 : termdd!IcaRawInput+0x50
fffff880`0aa48e20 fffff880`053a3d85 : fffff880`01716890 fffffa80`0c0327e8 00000000`00000000 00000000`00000000 : tssecsrv!CRawInputDM::PassDataToServer+0x2c
fffff880`0aa48e50 fffff880`053a37c2 : fffffa80`0c16e598 fffffa80`00000000 00000000`00000031 fffff800`00000000 : tssecsrv!CFilter::FilterIncomingData+0xc9
fffff880`0aa48ef0 fffff880`012c01f8 : fffff880`009b8180 00000000`00000001 00000000`00000000 00000000`00000000 : tssecsrv!ScrRawInput+0x82
fffff880`0aa48f60 fffff880`052994c5 : fffffa80`0c16e580 fffffa80`0c039ba8 00000000`00000000 fffffa80`0c16e580 : termdd!IcaRawInput+0x50
fffff880`0aa48f90 fffff880`012c0f3e : fffffa80`0c039b70 fffffa80`0acccf20 fffffa80`0a95c450 fffffa80`0abf9620 : tdtcp!TdInputThread+0x465
fffff880`0aa49810 fffff880`012bfae3 : fffffa80`0c0a6560 fffffa80`0abf9620 fffffa80`087eee80 fffffa80`0a95c450 : termdd!IcaDriverThread+0x5a
fffff880`0aa49840 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : termdd!IcaDeviceControlStack+0x827
STACK_COMMAND: kb
FOLLOWUP_IP:
RDPWD!memcpy+1d9
fffff880`053dc0c9 668901          mov     word ptr [rcx],ax
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: RDPWD!memcpy+1d9
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: RDPWD
IMAGE_NAME: RDPWD.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7ab45
FAILURE_BUCKET_ID: X64_0x50_VRF_RDPWD!memcpy+1d9
BUCKET_ID: X64_0x50_VRF_RDPWD!memcpy+1d9
Followup: MachineOwner
Bug Check Code 0x50:http://msdn.microsoft.com/en-us/library/windows/hardware/ff559023%28v=vs.85%29.aspx
Please start by that:
Update all possible drivers
Uninstall all unused programs
Disable all security softwares you have
Run chkdsk /r /f and sfc /scannow
Run memtest86+ to check if all is okay with your RAM. If an error was detected then replace the faulty RAM or contact your manufacturer Technical Support
If this does not help then upload MEMORY.DMP file (You can zip it and divide it using 7-ZIP) using Microsoft Skydrive and post a link here.
You can also contact Microsoft CSS for assistance.
This
posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Microsoft
Student Partner 2010 / 2011
Microsoft
Certified Professional
Microsoft
Certified Systems Administrator: Security
Microsoft
Certified Systems Engineer: Security
Microsoft
Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Microsoft
Certified Technology Specialist: Windows 7, Configuring
Microsoft
Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations
Microsoft
Certified IT Professional: Enterprise Administrator
Microsoft Certified IT Professional: Server Administrator
Microsoft Certified Trainer

Error when try to install exchange Server 2013 in windows server 2008 R2 Sp1

Hi
I'm getting these errors while trying to install Microsoft Exchange Server 2013 on my Windows Server 2008 R2 SP1 the user i'm using is the Administrator and it is already a member of "Enterprise
Admins" and "Schema Admins"
in my organization there is 6 Exchange server 2013 in 3 site windows server 2012 in this case
I have to install exchange 2013 in windows Server 2008 r2 sp1
the functional level 2008 R2 I getting these errors please help.
Errors:
This computer doesn't belong to a valid Active Directory site. Check the site and subnet definitions.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.InvalidADSite.aspx
Error:
A reboot from a previous installation is pending. Please restart the system and then rerun Setup.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.RebootPending.aspx
Error:
There is a pending reboot from a previous installation of a Windows Server role or feature. Please restart the computer and then run Setup again.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.PendingRebootWindowsComponents.aspx
Error:
You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFrontendTransportFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailboxFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClientAccessFirstInstall.aspx
Error:
You must use an account that's a member of the Organization Management role group to install the first Mailbox server role in the topology.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifiedMessagingFirstInstall.aspx
Error:
Setup encountered a problem while validating the state of Active Directory: Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites or by replication latency. See the Exchange setup log for more
information on this error.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx
Error:
Either Active Directory doesn't exist, or it can't be contacted.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx

I think it's from subnet in site and services
have 3 site A,B,C and new site is "D"I have problem in "D" site
A subnet is 10.33.50.0/24 AD 2012 ,exchange 2013
B subnet is 10.35.50.0/24 AD 2012 ,exchange 2013
C subnet is 10.36.50.0/24 AD 2012 ,exchange 2013
D subnet is 10.100.100.0/25 AD 2008 ,exchange 2013 error when install it
find event error
The description for Event ID 6 from source MSExchange CmdletLogs cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair
the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
test-SetupPrerequisites
{Roles={LanguagePacks, Bridgehead, ClientAccess, UnifiedMessaging, Mailbox, FrontendTransport, Cafe}, LanguagesAvailableToInstall=True, DomainController=, CustomerFeedbackEnabled=True, ExchangeVersion=15.0.847.32, LanguagePackDir=D:\Exchange
Server Software, SufficientLanguagePackDiskSpace=True, ADInitError=Setup encountered a problem while validating the state of Active Directory: Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites
or by rep, ScanType=PrecheckInstall, LanguagePackVersioning=True, HostingDeploymentEnabled=False, TargetDir=C:\Program Files\Microsoft\Exchange Server\V15, SetupRoles={LanguagePacks, AdminTools, Bridgehead, ClientAccess, UnifiedMessaging, Mailbox, FrontendTransport,
Cafe}}

Getting error while trying to install ADRMS role on Windows Server 2008 R2 SP1.

Hello,
I am trying to install ADRMS on Windows Server 2008 R2 SP1 (This machine also has domain controller and Exchange Server 2010 SP3 installed). But I am getting following error:
Install-ADRMS : The configuration object is read only, because it has been committed by a call to ServerManager.CommitChanges().
If write access is required, use ServerManager to get a new reference. at Microsoft.Web.Administration.Configuration.SetDirty()
Not sure what is causing this error. Any help to solve it would be appreciated.
Thanks.
Jigar Mehta

Hello,
I am trying to install ADRMS on Windows Server 2008 R2 SP1 (This machine also has domain controller and Exchange Server 2010 SP3 installed). But I am getting following error:
Install-ADRMS : The configuration object is read only, because it has been committed by a call to ServerManager.CommitChanges().
If write access is required, use ServerManager to get a new reference. at Microsoft.Web.Administration.Configuration.SetDirty()
Not sure what is causing this error. Any help to solve it would be appreciated.
Thanks.
Jigar Mehta

Unable to Install Windows Server 2012 on Windows Server 2008 R2 SP1 Hyper-V

My attempts to install are failing with a message "Windows cannot install required files. The file may be corrupt or missing....Error code: 0x800705070".
I am posting this on the Wondows 2012 Server forum but I have had exactly the same problem as described below with Windows 2008 R2 SP1.
As the title says this is on a Windows Server 2008 R2 SP1 host with all current updates. I have downloaded the ISO file from a Technet subscription file twice, once by direct download and once by the Akamai downloader. The virtual disk is connected with
the default IDE driver. I mounted both installation images as ISOs, located on a file system on the host server. I have tried installs by deleting the VM and recreating both the VM and a new virtual disk, re-using a previously created virtual disk, and
deleting the partitions in a previously created virtual disk, and executing the format command, and then attempting the install.
I have exactly the same problem trying to create a Windows Server 2008 R2 SP1 VM on the same host OS. With those attempts, I downloaded the Technet subscription iso 4 or 5 times, and burned one to a DVD which I attached to the created VM. Same
error message.
The virtual machines and virtual disks I created and used were all located on an RAID5 array, on a builtin Intel RAID controller using Intel Rapid Storage Technology software version 11.2.0.1066. The host Windows Server 2008 R2 SP1 uses this file system
but the OS is installed on a dedicated drive (C).
I had previously created a guest VM with Windows Server 2008 R2 (several months worth of updates ago) without drama.
I have spent hours reading forums and blog articles on this. A common response is to download the iso another time, and/or burn it to a DVD instead of mounting an iso image. Although I didn't do the later yet with 2012 Server, but I have done these
other steps attempting to install Windows 2008 Server SP1. The install process takes a while (not to mention doing multiple downloads). Given this seems to be a common recommended remedy, and indeed based on posts does seem to eliminate the problem is some
cases, why doesn't somebody change the Microsoft installer program so it does a thorough integrity check at the beginning of the install process?

Jeff,
After the exercise of Windows 2012 Server successfully installing (as I described above) I also successfully installed Windows 2008 R2 on Hyper-V. From my standpoint, I have eliminated the problem (which isn't the same as correcting the problem).
The answer to your specific question regarding Hyper-V support is that the motherboard I am using, an Asus P5Q, is not supported by Windows 2008 R2 because it doesn't use ECC memory, and the vendor doesn't say it supports Windows 2008. But I am sure you
know the motherboard vendors often don't test older motherboards with newer software versions. It appears that in specifying ECC memory Microsoft is trying to protect users of Windows Server from hurting themselves, not saying the software won't run.
Having said that, my suspicion in the beginning was, and still is, that it was some variable(s) left in an unknown state in the Hyper-V environment, which was why after trying to install Windows 2008 R2 several times I tried Windows 2012 which resulted in
the same error, and then encountered the same error trying to install Windows 7 on the same Hyper-V installation. The specific Hyper-V Windows 2008 R2 server had run without any operating problems for months before I started having trouble, and although it
had been quite a while since I had created VMs, that process used to work. The hardware didn't change. What changed was applying updates through Microsoft Update, and a few access control rights I changed, and at least I think, I set back to their original
value.
So in short, no, my hardware isn't supported by Windows 2008 Server. Two, your assertion that you are running the same software configuration that I am is very unlikely to be true. There are an extremely large number of things which are different between
your test system and mine, such as which Windows 2008 components are installed, what updates were installed and in what order they were installed, and what other third party software each of us is running, and between AD, and all the features, a large number
of potential differences in ACLs, options, etc. and I don't for a minute think this particular problem was caused by the underlying hardware.
I do appreciate your taking the time to try to help me, and I hope there is one thing you and I could agree on. Microsoft could pretty easily make it much easier to isolate problems. In this day and age reporting hex error codes (as opposed to doing the
table lookup in the error handling proc), and not providing more diagnostic information seems to me to be almost quaint. And in this case Microsoft can dismiss my problems on the grounds it was all on unsupported hardware. Unfortunately, I think they
are missing an opportunity to make their software better, because in my opinion what I encountered there are a set of conditions which will cause installations to fail that aren't going to get corrected.

Unable to install SQL server 2008 r2 standard edition on windows server 2008 r2 sp1

I am unable to install sql server 2008 r2 standard edition on windows server 2008 r2 sp1.
On the Setup Support Files page, choose Install this step I don't get any other window i.e. nothing happens I waited for 5-10 min. Then I checked the log file.
Final result:                  Failed: see details below
Exit code (Decimal):           -2068053929
Exit facility code:            1212
Exit error code:               87
Exit message:                  Failed: see details below
Start time:                    2014-03-18 14:59:31
End time:                      2014-03-18 15:00:25
=== Verbose logging started: 3/19/2014 9:45:47 Build type: SHIP UNICODE 5.00.7601.00 Calling process: E:\SQL Server 2008 R2 Standard\x64\setup100.exe ===
MSI (c) (10:34) [09:45:47:496]: Note: 1: 2203 2: E:\SQL Server 2008 R2 Standard\x64\redist\watson\dw20sharedamd64.msi 3: -2147287038
MSI (c) (10:34) [09:45:47:496]: MsiOpenPackageEx is returning 2.
=== Verbose logging stopped: 3/19/2014 9:45:47 ===
Please help As i am running out of time as i have to upgrade TFS for that first step is to install SQL server.

Hello,
The following are a few things you can try:
Copy the media to the local disk drive, unzip it (in case you are installing from an ISO file, and run SQL Server setup from there.
Try to unregister and register the Windows Installer with the following two commands:
msiexec /unregister
msiexec /regserver
Try to use Process Monitor to log the detailed error produced when the installation of dw20sharedamd64.msi fails. You can download Process Monitor from the following link:
http://technet.microsoft.com/en-us/sysinternals/bb896645
Share with us the error captured by Process Monitor.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Oracle 11g R2 install problem on Windows Server 2008 R2 SP1

Hi all,
Trying to install the Oracle 11g R2 database onto Windows Server 2008 R2 SP1.
I get as far as running the setup and a black window flashes up on the screen and disappears.
The log files only show the following:
Using paramFile: C:\Temp\database\install\oraparam.ini
Checking monitor: must be configured to display at least 256 colors. Actual 65536 Passed
The number of files bootstrapped for the jre is 0.
The number of files bootstrapped for the oui is 0.
I've tried running setup -debug from the command line but no further information is logged.
Any help in troubleshooting further is appreciated.

That is the complete log file. No error messages or further information is given.
I'm not sure how to check:
Statement of Direction: Oracle Database 11g Release 2 – Microsoft Windows 7 and Windows Server 2008 R2 [ID 867040.1]
I have checked on:
http://docs.oracle.com/cd/E11882_01/install.112/e24283/toc.htm
The server meets all the hardware requirements. The default file share is accessible and it is running a supported browser. The installer is being run with Admin rights. I'm not sure what else I need to check.

How to install bo xi 3.1 on windows server 2008 r2 sp1 (virtual machine )

HI GUYS --
operating system: I am trying to install Business Objects into a virtual computer which has a windows server 2008 R2 SP1 operating system. I installed version BO XI 3.1 and I also installed Service pack 3 and Service pack 4. I installed liveoffice usual way. Whenever I try to design xcelsius and dashboard, I got some errors. In order to fix these errors, I followed SAP notes step by step. However, It didnt help me at all. I also tried to install by looking at install guide and supported platform documents, but I get an error each time of doing that. I can write each error over here. I also opened a link over here. Check out the link please to see the errors how to display webi docs. in liveoffice?
My main question is this.
Are there anybody who works operating system windows server 2008 R2 SP1 and this installed into the virtual machine? If so, Is it worked by doing which installations exactly?
Note; Business Objects tools work very well (infoview, cmc, web intelligencei and the others work without problems at QAAWS BO XI 3.1, but they have been given cluster error at BO XI 3.1 SP3) . In addition, port server settings have been installed based on the installion guide. If you give me any information other than whatever I said, I appreciate that. I also point out something. If I dont get any message which I attached a sample when I try to operate life office. In this situation I cant see either my documets or web documents in infoview)
[http://imageshack.us/photo/my-images/3/sorunc.jpg/|http://imageshack.us/photo/my-images/3/sorunc.jpg/]

Hi SYaGCi,
Denis is right this is actually documented in the Supported Platforms Documentation:
"Windows 7 and Windows Server 2008 R2 are new platform support additions in Service Pack 3 which are only available for support on the SP3 full release install of SAP BusinessObjects Enterprise. The SP3 patch only release of SAP BusinessObjects Enterprise does not provide support for these two new platforms."
Kind regards,
John

Get-Hotfix InstalledOn property not returning hotfix installed Date and Time on Windows Server 2008 SP2 but works on Windows Server 2008 R2 SP1

Hi,
I am working on a validation script to get the list of hotfixes installed on Domain Controllers every month as part of our monthly DC patching process. I have been successful in getting these details for DC's with (Windows Server 2008
R2 SP1, Powershell v2.0) using the below command.
Get-HotFix -cn $computer | Select-Object PSComputerName,HotFixID,Description,InstalledBy,InstalledOn | where InstalledOn -ge (Get-Date -Day 1 -Format d) | FT -AutoSize
I execute the above from a jump box with powershell v4.0 (Server 2008 R2)
However, when I try the same command from the jump box to query DC's with (Server 2008 SP2, powershell v2.0). It doesn't return the InstalledOn date and time. It was giving error for the InstalledOn property and hence I renamed it to $_.InstalledOn. Now
I don't get error but still no details displayed for InstalledOn property.
I tried using the below, as could see on few forums that this might resolve the issue. I also tried removing the "where" part but still no installation date returned.
Get-HotFix -cn $computer | Select-Object HotFixID, Description, InstalledBy, @{l="InstalledOn";e={[DateTime]::Parse($_.psbase.properties["installedon"].value,$([System.Globalization.CultureInfo]::GetCultureInfo("en-US")))}}
| where {$_.InstalledOn -ge (Get-Date -Day 1 -Format d)} | FT -AutoSize
Have tried this locally on the 2008 SP2 DC but still not working. Please advise what is going wrong?
Note: If I execute the below command locally on the 2008 SP2 DC, I am getting the InstalledOn output. However, when executed from the jump box with powershell v4.0 (Server 2008 R2) to query
the same 2008 SP2 DC, it just gives the prompt again without any error or output. This behavior is consistent for other 2008 SP2 DC's in the environment.
Get-HotFix -cn $computer | Select-Object HotfixID,Description,InstalledBy,InstalledOn | where {$_.InstalledOn -ge (Get-Date -Day 1 -Format d)} | FT -AutoSize

Hi jrv, I have already tried the Win32_QuickFixEngineering option, which doesn't work either. Apologies for not mentioning the workarounds that I have already tried.
Get-Hotfix seems to be just a wrapper for Win32_QuickFixEngineering as per the below article. (http://technet.microsoft.com/en-us/library/hh849836.aspx)
I have seen a mention of using the WU ActiveX control on few forums, but was too lazy to read it through.
After rigorous testing, it makes me realize that somewhere the Get-Hotfix dates formatting\comparison isn't working.

Side by Side error on Windows Server 2008 R2 SP1

Hello!
I want to install SAP 4.7 Ex2 on windows Server 2008 R2 Sp1. I installed java 1.4.2.24 and oracle 11g before.
Now i tried to install the 4.7 system on the server. But in step "create or reregister sap services" i get an error.
The sap log shows me this error:
FSL-06002 Error 14001: The application could not be started, the Side by Side configuration is invalid
In Windows error log i got this message.
Fehler beim Generieren des Aktivierungskontextes fu00FCr "C:\usr
sap\DN2\sys\exe\run\sapstartsrv.exe. Die abhu00E4ngige Assemblierung
"Microsoft.VC80.MFC,processorArchitecture="AMD64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.4053"
konnte nicht gefunden werden. Verwenden Sie fu00FCr eine detaillierte Diagnose das Programm "sxstrace.exe
Error Code: 33
It installed vcredist 2005/ 2005 SP1. An i installed .NetFX3.5 (with versions 2.0-3.5) and .NetFx 4.0. The Error ist still exists.
Yesterday i installed windows Server new, but i got the same error again.
I don`t know what to do now, please help me.
Kind regards
Sebastian

> Fehler beim Generieren des Aktivierungskontextes fu00FCr "C:\usr
> sap\DN2\sys\exe\run\sapstartsrv.exe. Die abhu00E4ngige Assemblierung
> "Microsoft.VC80.MFC,processorArchitecture="AMD64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.4053"
> konnte nicht gefunden werden. Verwenden Sie fu00FCr eine detaillierte Diagnose das Programm "sxstrace.exe
And just as information:
German Windows servers are not supported, you should install a US English version.
Markus

AppFabric crashes IIS Manager when Powershell 4 is installed (Server 2008 R2 SP1)

When Powershell 4 is installed on a Server 2008 R2 SP1 box with AppFabric 1.1, IIS Manager will fail.
If you go to IIS Manager and plus open the node for your server (to look at your sites or app pools) you get an error like the following:
Description:
Stopped working
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: inetmgr.exe
Problem Signature 02: 7.5.7600.16385
Problem Signature 03: 4a5bd0a5
Problem Signature 04: System.Management.Automation
Problem Signature 05: 1.0.0.0
Problem Signature 06: 4ce7c787
Problem Signature 07: 106d
Problem Signature 08: a6
Problem Signature 09: PUYL1YSRBZLI4302TJNBZ1HF4QQMYKVP
OS Version: 6.1.7601.2.1.0.272.7
Locale ID: 1033
If you look at the application event log, you will also see:
IISMANAGER_CRASH
IIS Manager terminated unexpectedly.
Exception:System.Management.Automation.CmdletInvocationException: The method or operation is not implemented. ---> System.NotImplementedException: The method or operation is not implemented.
   at Microsoft.ApplicationServer.Management.Tools.PowershellHost.NoConsolePSRawUserInterface.get_BufferSize()
   at System.Management.Automation.Internal.Host.InternalHostRawUserInterface.get_BufferSize()
   at Microsoft.PowerShell.Commands.Internal.Format.ConsoleLineOutput.get_ColumnNumber()
   at Microsoft.PowerShell.Commands.Internal.Format.OutCommandInner.ProcessOutOfBandPayload(FormatEntryData fed)
   at Microsoft.PowerShell.Commands.Internal.Format.OutCommandInner.ProcessPayload(FormatEntryData fed, OutputContext c)
   at Microsoft.PowerShell.Commands.Internal.Format.OutCommandInner.ProcessObject(PSObject so)
   at Microsoft.PowerShell.Commands.Internal.Format.OutCommandInner.ProcessRecord()
   at Microsoft.PowerShell.Commands.Internal.Format.FrontEndCommandBase.ProcessRecord()
   at System.Management.Automation.CommandProcessor.ProcessRecord()
   --- End of inner exception stack trace ---
   at System.Management.Automation.Internal.PipelineProcessor.DoStepItems(Object input, Hashtable errorResults, Boolean enumerate)
   at Microsoft.PowerShell.Commands.Internal.Format.CommandWrapper.Process(Object o)
   at Microsoft.PowerShell.Commands.Internal.Format.SubPipelineManager.Process(PSObject so)
   at Microsoft.PowerShell.Commands.Internal.Format.OutputManagerInner.ProcessRecord()
   at Microsoft.PowerShell.Commands.Internal.Format.FrontEndCommandBase.ProcessRecord()
   at System.Management.Automation.CommandProcessor.ProcessRecord()
If you then uninstall AppFabric 1.1, everything starts working again. I need Powershell 4 with AppFabric 1.1. Any ideas?
I wonder if the below breaking change in Powershell 4 is causing the issue:
In Windows PowerShell 4.0, if a module uses the DefaultCommandPrefix key in its manifest, or if the user imports a module with the Prefix parameter, the ExportedCommands property of the module shows the commands in the module with the prefix. When you run
the commands by using the module-qualified syntax ModuleName\CommandName, the command names must include the prefix.

We didn't have this issue with Powershell 4.0, but with Server 2008 R2 SP1 and AppFabric 1.1. The solution for us was to install the
Upgrade Readiness Tool. No problems with Inetmgr and Clr20R3 after the hotfix was applied.

Is WMF3 or WMF4 supported in Exchange 2010 SP3 UR5 installed on Server 2008 R2 SP1?

We'd like to upgrade WMF (aka powershell) on our Exchange 2010 servers but I haven't been able to find any updated information on support with the most recent servicepack/update rollup.
Is installing WMF3 or WMF4 supported on Server 2008 R2 SP1 w/ Exchange 2010 SP3 UR5?

WindowsPowerShell 3.0 is supported. Haven't seen 4.0 running for exchange 2010 on 2008 R2
http://blogs.technet.com/b/heyscriptingguy/archive/2013/11/30/weekend-scripter-wmf-powershell-and-exchange-server-compatibility.aspx
http://blog.crayon.no/blogs/janegil/archive/2013/11/17/how_2D00_to_2D00_install_2D00_windows_2D00_powershell_2D00_4_2D00_0.aspx
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
Gulab,
Where did you read that WMF3 is supported on Exchange 2010 SP3 on Server 2008 R2?
Neither of the links you pasted suggest that and in fact explicitly say "There has been no testing with ExchangeServer 2010 SP3 and WMF 3.0 installed on Windows Server 2008 R2."
My Bad, that was TYPO...
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

"A severe error occurred on the current command. The results, if any, should be discarded." + Full-text-index Sql Server 2008 R2 SP1

Hello.
I have a problem with SQL Server 2008 R2 SP1:
I have a table with the full-text index-activated on 3 fields of type nvarchar.
When I try to open a transaction (ex: BEGIN TRAN {inserts} COMMIT) to insert multiple rows, I get the following error: "A severe error occurred on the current command ...".
I checked the Sql Server Logs and the Event Viewer on the machine, but nothing was logged.
I found a workaround: disable full-text-index => Do stuff => enable full-text-index, but this is very annoying (especially when i use the Data Compare to update that table on the Development Environment).
Help!!!

I concur with Tom. Upgrade to SP3. This may resolve the issue.
Since you say that there is nothing in the SQL Server errorlog, this may be an API issue. Try running the same commands through the command-line tools SQLCMD or OSQL to see how this turns out.
Erland Sommarskog, SQL Server MVP, [email protected]

Does installing Desktop Experience on Windows Server 2008 R2 SP1 slow down the server / increase processor usage?

Hello.
I'm running a tekkit classic (Minecraft) Server on a dedicated server I got from OVH, Im just wondering - Im currently using ClamAV for an antivirus, But I would like windows defender.
Im wondering if installing Desktop Experience on my dedi would increase processor usage or slow down the dedi even slightly.
System Specs:
RAM: 32GB DDR3 ECC 1600MHz
CPU: Intel Xeon E3-1245v2
HDD: 2x2TB SATA (Both used, specified as different drives)
OS: Windows Server 2008 R2 SP1
Theres only 1 indev tekkit server currently running on there, Im getting 0-5% processor usage. I may be setting up more modpack servers - but im wondering if installing desktop experience would increase the processor usage or slow the dedi down.
Thanks.
Joseph

Hi Joseph,
This is the forum for Microsoft BizTalk Server, you've asked your question in the wrong forum.
I suggest posting your question in the Windows Server forum
http://social.msdn.microsoft.com/Forums/en-US/home#forum=winserver2008appcompatabilityandcertification&filter=alltypes&sort=lastpostdesc&content=Search
Glenn Colpaert - MCTS BizTalk Server - Blog : http://blog.codit.eu

Server 2008 R2 SP1 - Software install - Error 1935 HRESULT:0x800736B5

Similar Messages

Maybe you are looking for